Is your feature request related to a problem? Please describe.
It is currently possible to chain actions within a sfpegAction configuration to execute an action when
another has succeeded (or failed). However, this is quite basic and it is not possible to leverage data
returned by the first action in the chain.
Describe the solution you'd like
Various use cases apply:
execute a record creation action (e.g. via LDS with no form) and redirect the user to the created record
execute a first Apex action to fetch a token and use this token within the URL of a later navigation action
execute a first control Apex action and trigger different actions if successful or depending on the actual exception raised.
Describe alternatives you've considered
Main option would be to support a new RES merge token within sfpegMergeUtl representing
data returned by an action, which would be progressively evaluated/reevaluated after each prior action.
In addition to basic next and error chaining properties, the idea would be also to set add a condition property, e.g. to determine which if an / which action should be triggered.
Additional context
The objective is to keep this feature simple. Any complex logic would be preferably implemented
in a Flow triggered via a Flow popup action.
Is your feature request related to a problem? Please describe. It is currently possible to chain actions within a sfpegAction configuration to execute an action when another has succeeded (or failed). However, this is quite basic and it is not possible to leverage data returned by the first action in the chain.
Describe the solution you'd like Various use cases apply:
Describe alternatives you've considered Main option would be to support a new RES merge token within sfpegMergeUtl representing data returned by an action, which would be progressively evaluated/reevaluated after each prior action.
In addition to basic next and error chaining properties, the idea would be also to set add a condition property, e.g. to determine which if an / which action should be triggered.
Additional context The objective is to keep this feature simple. Any complex logic would be preferably implemented in a Flow triggered via a Flow popup action.