- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2023 10:39 AM
Hi Community,
Initially i written a UI policy for with same variable for basic requirement, whenever user select Data master is Material will show this Code material will be visible and mandatory
later they asked me change when data master is material and operation is new code material should be Non Material
For that i have written another UI Policy as below
Could you please check and advise it works fine in catalog form but not work in RITM
Thanks & Regards,
Srinivasu
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2023 11:08 AM
You have (at least) 2 Catalog UI Policies that are in conflict with each other. One has an action for this variable to be mandatory, the other has an action for this variable to not be mandatory, so you will get erratic results. Make sure the Order of the one that includes the second condition of Operation is New is a higher number than the Order on the other one. If you can't get a better/complete definition for which values of which variables each other variable should be mandatory or not, then disable both of these and write the conditions in a Catalog Client Script. Structuring it this way may help see where you have undefined or conflicting requirements.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2023 11:08 AM
You have (at least) 2 Catalog UI Policies that are in conflict with each other. One has an action for this variable to be mandatory, the other has an action for this variable to not be mandatory, so you will get erratic results. Make sure the Order of the one that includes the second condition of Operation is New is a higher number than the Order on the other one. If you can't get a better/complete definition for which values of which variables each other variable should be mandatory or not, then disable both of these and write the conditions in a Catalog Client Script. Structuring it this way may help see where you have undefined or conflicting requirements.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2023 11:28 AM
Since both the conditions are referring to the same field it would be better to write a onchange client script on your data master field since that is common to both the conditions.
Also you can change the order and see if it gives you static result as already stated by @Brad Bowman .
You can also uncheck the reverse if false checkbox in the first UI policy as well and keep it checked in second UI Policy to see if it gives static results.