Reusing activity implementations


Activity implementations can be used in different transaction pathways. Using fewer activity implementations allows for a better understanding of your configurations. However, if an activity implementation changes, each transaction pathway that uses it needs to be generated and deployed (when required). If an activity implementation is used only in a single model, then any modification to that activity implementation affects only that model.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*