Procedure Execution Flow - Action Status
Problem to solve
When modelling, business logics are encapsulated in separate procedures. This has the advantage that they can be called from anywhere without creating redundant logic. With the "call procedure" step, a procedure can call one or more child procedures. There is currently no simple way to return a functional success or failure message to the calling procedure, which could be used to start error handling or cancel the process directly. I will refer to this message as "Action Status".
current Workaround
The current workaround to pass such information from a child procedure to a parent procedure requires the creation of a dedicated data cube. This procedure is cumbersome and error-prone. Especially because the developer has to consider the multi-user capability.
Idea
The developer should therefore be able to define an "action status" for each procedure. This consists of a three-digit numerical code and a descriptive text. When a new procedure is created, the two values "001 - success" and "002 - error" are created automatically. These cannot be deleted or changed. However, the developer has the option of creating further attributes so that the calling procedure can react to the result in a more differentiated way. The developer can specify which "Action Status" is returned by the procedure via a new procedure step "Set Action Status".
If the developer does not make a selection, "001 - success" is always returned.
In the "call Procedure" procedure step, it is then possible to react to the "Action Status" by jumping to a group to be defined or by executing the next step in the current group.
To inform the end user about possible errors, it should be possible to display the current "Action Status" in the "Show Message" procedure step. For example via a datapicker @ActionStatus.
Comments
-
I like the idea and agree that it would further extend the possibility to implement business logics with procedures.
I thought of something similar and just want to link my idea here.
There an idea regarding a procedure status also came up in the comments.I like the idea and agree that it would further extend the possibility to implement business logics with procedures.0
