- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2018 07:52 AM
We have a UI Policy set up so that when a "Salary" amount is entered in a field, two other fields become mandatory. When a Salary amount is entered in the list view (by double-clicking and saving on the cell), it pops up the two new mandatory fields. Is there any way to change the order that these two new fields display in the popup?
Solved! Go to Solution.
- Labels:
-
User Interface (UI)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2018 06:42 AM
HI Beccad,
That;s right, it's not only driven by dependencies, UI policies are also considered in this list-edit popup.
After digging into this and some testing, to me it seems that there are multiple factors at play which determine the ultimate order of field display,
however my guts feeling is that the default display order comes from the UI policy actions in their sys_id order against the given fields of the table.
But again, this may be overriden by field dependencies or multiple UI Policies controlling the same field, etc.
Below example is the incident table list edit:
and the UI policy actions (ORDERBYsys_id) at play on incident table:
In conclusion, I would suggest that if the order of the fields really matters, restrict the list-edit action and get the users to open the record and populate the form directly.
Please let me know if this helped,
Cheers,
Andras
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2018 06:42 AM
HI Beccad,
That;s right, it's not only driven by dependencies, UI policies are also considered in this list-edit popup.
After digging into this and some testing, to me it seems that there are multiple factors at play which determine the ultimate order of field display,
however my guts feeling is that the default display order comes from the UI policy actions in their sys_id order against the given fields of the table.
But again, this may be overriden by field dependencies or multiple UI Policies controlling the same field, etc.
Below example is the incident table list edit:
and the UI policy actions (ORDERBYsys_id) at play on incident table:
In conclusion, I would suggest that if the order of the fields really matters, restrict the list-edit action and get the users to open the record and populate the form directly.
Please let me know if this helped,
Cheers,
Andras
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2018 01:45 PM
You were right, the UI Policy Actions were evaluated in order by their sys_id. I made copies of my UI Policy Actions until I got results with sys_id's that were in the order that I wanted, and the fields now appear in the list in the order that I want. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2018 07:58 AM
Interesting question! Never tried this before
Since this is dictated by a UI Policy I think the first thing I'd try is seeing if altering the Order of the UI Policy Actions had any effect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2018 08:26 AM
I checked for that, but it doesn't look like UI Policy Action have an Order field...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2018 02:52 PM
Dang. That was my only idea.