Creating a flow/subflow does not check if the glide record action was aborted so errors are not shown in the UI (bottom right corner) - Known Error

Creating a flow/subflow does not check if the glide record action was aborted so errors are not shown in the UI (bottom right corner) Description Creating a flow/subflow does not check if the glide record action was aborted so errors are not shown in the UI (bottom right corner). An error that occurs when attempting to create a flow/subflow may not be immediately apparent with a friendly error message.

In FlowGlideRepository.createFlow() after flowRecord.insert() a check on flowRecord.isActionAborted() should be made and if so an exception should be thrown and the POST to flow service should return a 400 Bad Request status rather than 200 OK.

It is done correctly in ActionService and ActionTypeGlideRecordRepo.updateActionType (throws ActionDesignBusinessRuleException). The same pattern should be followed to fix Flow/Subflow.

Steps to Reproduce

1. Create a custom before Insert business rule on the table Flow [sys_hub_flow] with the following details:

Filter Conditions: Flow Type is SubFlow. Script: abortactionCDG(); function abortactionCDG(){ gs.addErrorMessage('You are not allowed to create a subflow'); current.setAbortAction(true); }

2. Create a custom before Insert business rule on the table "Action Type" [sys_hub_action_type_definition] with the following details:

No Filter Conditions are needed. Script: abortactionCDG(); function abortactionCDG(){ gs.addErrorMessage('You are not allowed to create a Flow Action'); current.setAbortAction(true); }

3. Attempt to save an action and observe the error message in the lower right corner.

4. Attempt to save a subflow and observe that there is no error message.

Workaround If you are able to upgrade, review the "Where Found/Fixed" and "Fix Targets" tab of the problem record to determine whether any versions have a planned or permanent fix.