- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2024 12:40 PM
I am working on modifying our resolution process on the Mobile Agent App. I have added assignment group to the resolution input screen, but I would like to hide it if it is not empty.
I created a Mobile UI Rule, along with a Mobile UI Rule Action that looks like it should be working to me, but it isn't. Any pointers, or if you see any issues, would be awesome. I'm curious if I'm doing the condition wrong?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2024 08:57 AM
I figured out the issue, and might have found a bug in the process. The onLoad call that was created via the Mobile App Builder was not the correct one. It seems like it made a dummy entry. You'll notice in the original screenshot it is not underlined. I had to delete that one, open the trigger selection screen and choose it again...it is now clickable and links to the onLoad trigger entry.
So, everything was setup correctly in my original image, it was just using the wrong onLoad trigger so it wasn't working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2024 02:19 PM
Hi @Community Alums ,
Check the "Reverse if False" and test.
-Thanks,
AshishKMishra
Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2024 06:54 AM
That would have no effect, as the field is already visible...reversing the logic would say to make it visible if it's not empty...which is it's default state. I did try it however. I also reversed the action to true, with reverse if false turned on. Neither test changed the end result...not matter what, the field always shows.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2024 08:57 AM
I figured out the issue, and might have found a bug in the process. The onLoad call that was created via the Mobile App Builder was not the correct one. It seems like it made a dummy entry. You'll notice in the original screenshot it is not underlined. I had to delete that one, open the trigger selection screen and choose it again...it is now clickable and links to the onLoad trigger entry.
So, everything was setup correctly in my original image, it was just using the wrong onLoad trigger so it wasn't working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2024 09:36 AM
good to hear that issue resolved 🙂
Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution