- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
11-24-2022 10:06 AM - edited 11-24-2022 10:10 AM
We all like navigating to table list via table_name.list<enter> and we love to do it via /table_name<enter> *
In the case of the Action Assignments table, there are two caveats that this article tries to address!
So when creating new records in the Declarative Action Assignment table (sys_declarative_action_assignment) using a handy shortcut is not your best option!
In case you do, you'll probably see something like the one below.
No New button?! what is going on, an ACL issue?
When looking into this, it turns out that the New UI Action, specific for this table, has a scripted condition. This hides it when the default view is selected.
After figuring this out and changing a view we do get the New button!
Good, let's try it, and fill in the form!
After filling in the form and saving it, we get the message:
The following mandatory fields are not filled in: Action Model
But that is a field not on the form?!
With /tn > form fields * an or /uh * we can easily see this is a hidden field on the form, but what's going on?
Well it turns out that when you use the navigator to open the table list for example:
All > Playbook Experience > Actions > Activity Actions
This includes a query parameter to filter the action model to only show the ones of type Playbook Card
Now when creating the new button from here will result in prefilling the Action Model field with Playbook Card, so when we now fill in and save the record, everything will work as expected.
So the moral of the story?!
Action Assignments are used in the platform in various ways, each with a Form View and Action Model reference.
Be sure to use the navigator to search and click the appropriate option to make sure you're able to create the record in the right way!
Bonus tip: With the new SN Utils navigator search*, you can get a quick idea of what the different use cases are.
Use /all table_name
The all will narrow down to only the all section, excluding (most of) history, favorites, etc.
This implementation of the search also includes the table name of the URL.
so including that gives a nice overview of all occurrences of items that link to that specific table list or view in the navigator.
In the below example, we can get an overview of the different variations where Declarative Action Assignments are leveraged.
*) These are references to SN Utils functions. I am the author of SN Utils!
- 4,281 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
It's Really amazing and Helpful Articles
Thanks a lot @Arnoud Kooi
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thanks for the great article @Arnoud Kooi .
Another thing i have noticed is, it seems there is not module where the action model is a 'Form'. i am using the insert and stay on the existing record for this. Is there something i am missing?