- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 09:33 AM - edited 12-12-2023 09:35 AM
Hello, I have conditions to omit the new button on the Related list working, however, I am struggling to configure the workspace view to omit the new button with the same conditions and I do not know where to look. I tried this article but it did not seem to help: How to hide ‘New’ button for a table on Agent Workspace’ related-list when the ‘New’ action is not c...
The record is on the Issue table and I am trying to omnit the new button from the Policy Exception in the Related List
This piece works fine in the classic view:
However in the workspace view the new button shows regardless of the condition:
Where is the record stored and where can I apply the scripted omit that is working in the classic view to apply to the workspace view?
Thank you
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2023 03:18 PM
I was able to solve this. My take back to this was partly from the KB, however, it was a little more complex than the guidance.
There were two key parts and a couple of records to look out for.
The first two records to keep an eye out for are the OOB Global new button record as listed in the KB article and if there is already a record on the table you are trying to set the condition on, both would be located on the table "sys_declarative_action_assignment" with the condition "Action Model" = "Related List".
The first point in my case for the GRC application, there was already a record for the "Policy Exception" table:
What I did was make a copy or insert and stay after I updated the fields, unchecked the "Active" field, and saved the record on the OOB GRC record.
One thing to note at this point: because the Global Record did not have an "Action Exclusion" for the Policy Exception table, the Global New button would take over at this point, so when testing, before creating a new or copying the OOB GRC Action Assignment, the new button was still appearing in the workspace for the Policy Exception related list in the workspace Issue Record.
Within my new record after clicking "Advanced View" in the related links, a condition tab appeared.
From here, upon testing the condition functions the opposite of the Omit script from the List Control.
The condition in List Control is when to hide/omit and the scripted condition in the Related List Action is the condition to show the button on the related list.
With the new Related List Action record I created, I flipped the scripted condition from what I wrote in the omit script field on the List Control. Now the New button will only show when the person viewing the issue is the issue manager and then the button will show.
If there is a more simple way or a better way to accomplish this, please let me know. Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 09:33 PM
go to table "sys_declarative_action_assignment" and lookup records for "Action Model" = "Related List"
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2023 03:18 PM
I was able to solve this. My take back to this was partly from the KB, however, it was a little more complex than the guidance.
There were two key parts and a couple of records to look out for.
The first two records to keep an eye out for are the OOB Global new button record as listed in the KB article and if there is already a record on the table you are trying to set the condition on, both would be located on the table "sys_declarative_action_assignment" with the condition "Action Model" = "Related List".
The first point in my case for the GRC application, there was already a record for the "Policy Exception" table:
What I did was make a copy or insert and stay after I updated the fields, unchecked the "Active" field, and saved the record on the OOB GRC record.
One thing to note at this point: because the Global Record did not have an "Action Exclusion" for the Policy Exception table, the Global New button would take over at this point, so when testing, before creating a new or copying the OOB GRC Action Assignment, the new button was still appearing in the workspace for the Policy Exception related list in the workspace Issue Record.
Within my new record after clicking "Advanced View" in the related links, a condition tab appeared.
From here, upon testing the condition functions the opposite of the Omit script from the List Control.
The condition in List Control is when to hide/omit and the scripted condition in the Related List Action is the condition to show the button on the related list.
With the new Related List Action record I created, I flipped the scripted condition from what I wrote in the omit script field on the List Control. Now the New button will only show when the person viewing the issue is the issue manager and then the button will show.
If there is a more simple way or a better way to accomplish this, please let me know. Thank you