I have come to a problem when generating new child records on a form via UI action button. Let’s assume we have parent-child datastructure for example DeliveryDetail → DeliveryDetailItem. While standing on one Delivery structure record I want to generate new DeliveryDetailItem records while compying with following rules:
newly generated records will be visible immediatelly after finishing UI action workflow call
all rules on Delivery structure entity must be run after finishing UI action workflow call
newly generated records in DeliveryDetailItem structure entity are not saved, so the whole screen must be saved by pressing Save button
Right click on an entity (e.g. Delivery) and select New > Sequential Workflow Action
ActionType = Workflow
Create a context in your workflow with the same structure as your screen (e.g. DeliveryComplete)
Create a parameter mapping with name of the target context (e.g. DeliveryComplete) and MappedColumn = . (just a single dot). This will pass the current record with all the children will to the target context store.
Process the context store in the way you want (e.g. adding a new detail record using a transformation).
The “.” mapped context will be automatically merged back to your screen. The screen will get dirty and rules will get processed.
I have a “ProtocolTemplate” object with Child rows which represents “Definition of Measured Parameters”
I create my “Protocol” which I fill with predefined “Measured Parameters”
If I change “ProtocolTemplate’s” Parameters “Definition of Measured Parameters”, I want to refresh the list of parameters of “Protocol” by clicking “reload parameters” button.
I would expect:
New parameters are added
Deprecated parameters are deleted
–
In case the delete is not supported, I can imagine to configure “Active” field which would cause the parameters would not be visible anymore in protocol.