Use Action Results Instead of Variable Data Objects

Experience has shown that the concept of using variables to store data before using it elsewhere (like in conditions) is not easy to adopt for users without automation or programming background. Starting from Creator 2.3, the Creator modelling language has been extended and simplified by allowing direct use results of input actions that produce data (like fill form, receive message, custom input actions, etc) if input action and data use are in the same activity diagram (see Creator Manual section Creating Models with Conformiq Creator > Activity Node > Actions). In other words it enables to model data flows and handling without variable definitions.

Note that variable data objects still need to be used in cases data has to be stored in one activity diagram and then used in another activity diagram. Also use of action results does impact readability: There is currently no visual indication in the source action that its action results are being used elsewhere.