These articles provide a general introduction to the iCM Process Modeller, what it can be used for, and some of the best practices we've developed in our own processes.
When a form that includes file uploads interacts with a workflow process, files are stored using the Filestore Worker and references to them are passed to your process instance.
The Self Service and User Request templates can provide links that allow users to send cancellation messages to process instances that they started. For these links to appear, cancellation needs to be built into the process model.
Rather than use the Self Service or User Requests templates, it's possible to link directly to a user task form using the Forms Service template and a business key as a URL parameter.
As a process instance is executed, some parts are executed in the foreground, others in the background. These jobs are carried out in separate database transactions.
The workflow engine performs certain tasks automatically, like generating business keys, recording history, and setting up message and signal definitions. Understanding when each of these things happen can help with more complex process design and preventing potential problems.