Now Mobile Displaying Base Task State Values Instead of Customized Extended Table States (Incident,

mravulakolu
Tera Contributor
We have configured Now Mobile and enabled the application. Under XXX, we added a condition where the Assignment Group is one of our dynamic groups and the Assigned To field is empty. We also retained the out-of-box (OOB) filters.
When a user clicks the “Assign to Me” button from the top corner in Now Mobile, the task is successfully assigned and appears in My Task List. We additionally configured an “XXX" action and included the following fields:ITSM
  • State
  • Assignment Group
  • Assigned To
However, we are currently seeing only the default State values from the base Task table in the mobile app.
Our environment has customized State values configured separately for the following extended tables:
  • Incident
  • RITM
  • HR Case
These customized states are working correctly in the platform UI, but they are not appearing in Now Mobile. Instead, the mobile app is displaying the default Task table state choices.
It appears that the mobile configuration may be referencing the base Task table rather than the extended tables (Incident, RITM, HR Case), resulting in the custom state values not being reflected.
We would like guidance on:
  1. How to ensure Now Mobile references the correct extended table state choices instead of the base Task table.
  2. Whether separate mobile configurations/actions must be created for each extended table (Incident, RITM, HR Case).
  3. If there are any additional configurations (Mobile UI Policies, Client Scripts, or app republishing steps) required to make the customized state values visible in Now Mobile.
Kindly advise on the recommended approach to ensure our customized state values are displayed correctly in the mobile application.
0 REPLIES 0