Currently, we do an inline set of properties and invoke data transform rule in the connector shape configuration in a flow. Many a time in doing so, we inadvertently hide or introduce business logic which becomes a maintenance challenge and lends an opportunity to sneak a logic errors.

To mitigate such issues, I believe we can have a utility activity @baseclass called “pzApplyDataTransform” a final rule which takes two parameters 1. Activity Name 2. Page Name context in which the Data Transform rule to run. I see some tangible advantage in having this utility activity;

1.       Avoid hiding business logic under the connector shape configuration and make the business logic transparent in the flow-through utility smart shape.

2.       The flow will be descriptive, having inline property sets put in a Data Transform rule.