UI Policies Not Applying Correctly for Case Variables
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Team,
We need to ensure that variables are initialized when a case is created or transferred between services via the agent workspace, similar to how it operates through the ESC portal.
To achieve this, we're using a Business Rule that triggers when the case created in agent workspace and initialize variables belongs to Record producer associated to that service. However, the UI policies do not function as expected, unlike when a case is created in the ESC portal.
For the service "Corrective Action Manager Support", we have four variables. Out of these, three are hidden in the catalog view, and one is hidden in the case view.
Case HRC2291274 was created via the ESC portal, while Case HRC2291279 was created in the agent workspace. Using this Business Rule "InsertVariablesOnCase", we are injecting the variables forcefully. Is there an out-of-the-box feature to retrieve the default variables without using this business rule? Please advise.
In the HR case , you see the extra question "Please provide a detailed description of your support needs" that should not be visible as per the UI policy "Hide Fields in Target Record"
As highlighted in the red box in the screenshot, some fields should not be visible per the UI policies "Hide Fields in Catalog" and "Hide Fields in Target Record" specified for the record producers.
Our requirement is I want to generate the record producer variables if the case is created through the Agent workspace , those variables should be working as similarly (applying UI policies as well) when you submit the case with record producer from the portal.
Now with Business Rule "InsertVariablesOnCase" we are able to see the variables but UI policies are not applying on these variables.
Let me know is there any other way we can achieve.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Please configure the UI Policies using the false condition rather than writing them based on the true condition.
For example, suppose you want to hide the field ‘x’ when the Category is ‘c’.
Instead of writing the condition as Category is ‘c’ → Visible = false for field ‘x’,
write it as Category is not ‘c’ → Visible = true for field ‘x’.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
It would be helpful to see how the UI Policies that are not applying in this case are configured via screenshots like this
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Yes, we are having the UI policies these are not working.
