Many Points in a single Escalation should be allowed to use the same Action Group

The main Escalation Condition and Escalation Point Conditions are just ALN fields. This means they have a character limitation between 2 and 4 thousand characters. Sometimes, a properly formatted query can bump against those limits. One Escalation design option is to put the common conditions in the Escalation Condition and then put cohesive groups of sub-conditions in Escalation Point Conditions, making it easier to maintain those groups of sub-conditions. However, Maximo does not allow a given Action Group to be invoked by more than one Point within an Escalation -- a limitation that seems quite arbitrary.

One customer has workflow assignments that need to be auto-accepted when certain conditions are met, to keep the status and assignment of the parent in sync with the state of the tasks. The SQL for the Escalation works really well to check for the wfassignment to AUTOACCEPT in the main condition and then have a point for each parent status and its expected task statuses. However, the action in all these cases is the same, so they need to set the Action Group for the Escalation Points to be the same (WFACCEPT). But Maximo blocks this, insisting instead that they have duplicate Action Groups that just call the same Action, creating development and maintenance overhead.

To replicate the problem I want resolved, follow these steps:
1. Load an existing Escalation, like INCCLOSE in a MaxDemo database.
2. Copy the Action Group from Escalation Point 1.
3. Click New Row on the Escalation Points table.
4. Paste the Action Group in the field for the new row.
Expected Result: No error
Actual Result: Error: "This is a duplicate line." when the line is not a duplicate, just this Action Group has been reused on this Escalation.