• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Issue with helper program not being called on desktop

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Issue with helper program not being called on desktop

    I have a form that calls a helper program on field change to make sure all fields on the form are filled in before enabling a button that allows the user to go to the next screen. most of the fields are populated by default on startup, so the only field that they must put a value into is a timestamp field for clock out time. To simplify this process for the user, i added a button that brings up a popup grid widget with valid times for selection. Once they choose one, it populates the form with the selected time by setting an app variable that the form field is linked to. Now that every field is populated, the helper program should be called due to a form change and it should enable the button to move on. I checked through logging and confirmed that this is working on mobile, but i have to change a different field on desktop for it to actually call the helper program.

  • #2
    What is your full Valence version number?

    Comment


    • #3
      I am currently on the latest version: 6.3.20240627.0

      Comment


      • #4
        Can you give us a sample value that you are setting your app variable to? And just to confirm, the value you are setting it to is NOT the current value of the field?

        Comment


        • #5
          The value is definitely different, the app variable is set to blank by default. the value it is being set to comes from a timestamp data source so for example, it would be '2024-07-16-12.00.00.000000' and i have that value being formatted to show as Tue, Jul 16, 2024 @ 12:00PM

          Comment


          • #6
            We have replicated the issue and are taking a closer look.

            Comment


            • #7
              This will be fixed in the next update.

              Comment

              Working...
              X