- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2022 01:29 PM
Hello All,
This one has been driving me crazy, it should work in theory but does not, so im curious if ive stumbled upon a bug in the platform. So I have a footer action/action item on an incident record linked to a input form screen. I have two inputs configured like this:
Ive also got two variables set up as database fields to populate their values:
I also have a Mobile Ui Rule in place like so:
In theory this is supposed to onload get the value of the bool and if its true set the other field to be visible, mandatory otherwise it will be hidden. The problem im facing is that the onload here does not work but the onchange does. How can i get around this? Am i missing something here?
Solved! Go to Solution.
- Labels:
-
Mobile Studio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2022 12:40 AM
In case anyone else runs into this issue, the only way i got it to work was by changing the variable type to scripted and setting its value:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2022 01:40 PM
In the onload, may be the condition is not matching. Is the value being set after the form is loaded?
Also, not sure, but can you give order to those UI rule actions with first being mandatory set and then visibility and test it once. Becuase in reverse, mandatory has to become false first before visible going to false.
Mark the comment as a correct answer and also helpful if this has helped to solve the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2022 01:45 PM
The value of the boolean is being set correctly onload, however, the Ui Rule does not think so.
I have also tried to change the order of the ui rule actions but it makes no difference since anyway as i mentioned the onchange works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2022 12:40 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I am so glad you post this issue. I ve been trying to fix my "fail" alert message, when I click submit button in the Mobile Agent App for two weeks. Now, I started with the OOB Edit Incident > Edit Function, which has the "Properties" scroll down to "Edit incident functions " and then scroll down and add in roles if needed. Next, Action Items . This is where I have named the Properties> Data :Table (incidient), Set fields value based on my client requirement. Next, I click the hyperlink open to determine what fields display to accept user inputs. Now, when clicking on this link and brings me to the following "Input form page display" custom page and section follow by inputs that I have selected /edit to meet my client requirements. Next, I believe this is where I noticed my issue . I scroll down to the Mobile UI Rules and there currently two OOB Mobile UI Rules that I have deactivited because it's not part of my requirement . So I created UI Rules for the following: Show Work notes Mandatory when on-hold is selected and I scrolled down to complete the fields: Properties> Settings>Parent Table> Parent>Reverse if False>Condition (state=3^EQ) > Triggers ( onchange). Next, selected the Mobile UI Rule Action, which set the Operation to "Set Mandatory" > Target: work_notes)> Value :true. Next, is the "Set Visibiity" > Target: (work_notes) > Value: true. Now all this has been done. Now, I open the Mobile app > create incident> and submit. Then I find the incident I created and try to edit the incident by clicking on the three dots in the upper right corner. I edit/ change made changes to a few fields to test to see if it work. So. I click submit. Then get a "red FAIL" and the form never submit. I know I given alot of information but I wanted you see how I got here and if anyone could catch where my mistake as I was configure this."
Please veiw scrrenshot
