What does "Assign to me" UI Action do?
The "Assign to me" UI Action is available on the context menu of the list view of Task and/or its extended tables. It assigns the selected records to the logged in user. An extended table can either use the inherited version from Task or can have its own version by adding a new UI Action that overrides the parent (Task) UI Action.
The Assign to me UI Action on Problem (Task table's extension)
What has changed in Rome for "Assign to me" UI Action?
From Rome, Incident and Problem have overridden the default Task “Assign to me” action to perform validation before assigning the selected records to the user.
Previous behavior (pre-Rome)
-
- There is no validation in the default Task “Assign to me” action.
New behavior (from Rome)
-
- When an assignment group has been set on the record, the “Assign to me” action will only assign the record to the user if they are part of the assignment group. The record will also get assigned to the user if the assignment group is empty, but the assignment group will not be populated in this case.
For this new validation, we have new "Assign to me" UI Actions for Incident and Problem that overrides the default Task "Assign to me" UI Action.
Additionally, in order to implement the above, we had to make changes to Task and its extended table's UI Action:
- We have changed the "Assign to me" Task UI Action > "Action Name" to "task_assign_to_me".
Before: Task UI Action before the changes (pre-Rome)
After: Task UI Action after the changes (Rome)
- The UI Action > “Action Name” is also set to “task_assign_to_me” that allows us to set “Overrides” to empty and still override the default Task behavior on:
-
- Change Task
- Change Request
- Standard Change Proposal
- Universal Request
- Incident (Rome)
- Problem (Rome)
Before: Change Request's UI Action extends Task UI Action by specifying Overrides field, Action name is empty. (pre-Rome)
After: Change Request's UI Action now extends Task UI Action by specifying Action name, Overrides field is empty. (Rome)
How am I impacted?
Since there are additional changes made to the above base Tables, if you have customized the Assign to me UI Action for Task/extended tables, then there could be additional impact as the new changes are not be available with instance upgrade.
- 1. Case: If you have Only customized the Task "Assign to me" UI Action:-
Impact: You will see two entries for extended table's "Assign to me" context menu in the list view. This is because the "Assign to me" Task UI Action in your instance will not be upgraded and would not have the correct Action name. Hence, both the actions are displayed.
Fix: Set the Task table's "Assign to me" UI Action's > "Action Name" to "task_assign_to_me" in order to link the overridden tables and the Task table's "Assign to me" UI Action.
Image illustrating two "Assign to me" UI Action for a Task extended table (Notice the duplicate "Assign to me" actions)
- 2. Case: If you have customized the Task "Assign to me" UI Action and one or more extended table's "Assign to me" UI Action or created custom "Assign to me" UI Actions for any table that extends Task including custom tables :-
Impact: You will see two entries for extended table's "Assign to me" context menu in the list view. This is because we include the "Assign to me" UI Actions for Incident and Problem with Action name populated, the existing extended tables will also exhibit the same double UI action behavior.
Fix: In addition to the Fix for Case#1 for Task, for each of the UI Action for table's extending Task a) Set the "Assign to me" UI Action's > "Action Name" to "task_assign_to_me" and b) Empty out the "Overrides" field.
Post upgrade, ensure that there should be no extended table's "Assign to me" UI Action that has the "Overrides" field populated to the Task table's reference. "Overrides" field should be empty. From Rome, the overriding of the "Assign to me" UI Action would be done based on "Action name" only. The "Overrides" field will no longer be relevant.
- 3. Case: If you have customized the Task table's "Assign to me" UI Action by providing a custom "Action name" :-
Impact: You will see two entries for "Assign to me" UI Action for Incident and Problem context menu in the list view. This is because the UI Actions for Incident and Problem will have a different "Action name" than Task.
Fix: You can set the Action name for both Incident and Problem "Assign to me" UI Action as your Task table's "Assign to me" UI Action name. It is recommended for all Task extending "Assign to me" UI Actions to use the Action name "task_assign_to_me".
- 4. Case: If you have already created new "Assign to me" UI Actions for Incident and/or Problem with some custom behavior :-
Impact: You will see two entries for "Assign to me" UI Action as in addition to your created actions, the newly created actions in Rome will also be displayed.
Fix:
-
-
- If you wish to keep only the old functionality, you can mark the new UI Actions for each table as active = false.
- If you wish to use the new functionality along with your custom behavior, you can incorporate the changes (club them together) in your existing UI Actions
- If you wish to use only the new functionality, you can mark the existing UI Actions as active = false using the new ones only.
-
How can I opt out of the new changes on Incident and Problem table?
In order to continue having the old behaviour for Incident and Problem tables with no validations, you can disable the new "Assign to me" UI Actions for Incident and Problem to inherit the Task's "Assign to me" UI Action.
Where can I find the new UI Actions for Incident and Problem?
You can navigate to "UI Actions" and Filter as All > Name starts with Assign to me > Table = Incident .or. Table = Problem > Action name = task_assign_to_me
Will I be impacted if I have disabled some/all of the overridden "Assign to me" UI Actions for Task?
If you have marked an extended table's "Assign to me" UI Action as inactive, the base actions will not be upgraded with the newer version. If you plan to make them active, then the above steps need to be followed. However, the newly introduced Incident and Problem actions would be displayed with two entries based on whether you have customized Task/extended table's "Assign to me" UI Action.
How do I create a new "Assign to me" UI Action for a table that extends Task?
Any new "Assign to me" UI Action that is to be created for a table which extends Task must use the same "Action name" as on the Task table "Assign to me" UI Action that is "task_assign_to_me". Also, earlier we were using the "Overrides" field to refer to the Task table on the extending table's "Assign to me" UI Action for OOB tables. The same will no longer be used from Rome and the overrides field for "Assign to me" UI Action for extended tables must be left empty.
