If you want to automate a Processing step to, for example, obtain the number of characters and the hash value, you have to write scripts using a [Script Task]. If you need to use the same [Script Task] in different places you should consider packaging the script as an [Add-on XML]. (Service-Task Addon)
1. Overview of the Advantages of Creating Addon XML (Packaging)
- a. Aspects of IT skill requirements (compared with a Script Task)
A flow designer who does not have script knowledge should be capable of workflow automation as well.
- b. Aspects of the modelling cost (compared with Script Task)
There will be no need to write the same script repeatedly.
- The boundary between the IT Department's and the Process owner's responsibilities should be considered
- Go to M415: Adding an Auto-Step to be Used in a Workflow App for more info on how to import a pre-existing [Addon XML]
2. Creating a Custom Add-on XML
- The process for creating a custom add-on is explained in "Sending a Text Message in the Middle of Workflow Using SMS – Service Task Add-on version"
- Please refer to "R4160: Addon-XML config format" for the add-on XML format specifications
- The script section is subject to the same constraints as Script Tasks (e.g., a maximum execution time of 30 seconds, a limit of 10 HTTP requests per automated processing step)
Related Articles
- Add-on Auto-Steps" (Collection of Implementation Samples for Auto-Steps)