Modeling is used to create the templates for automating content-based business processes.
The Modeling Application is where all models are created and edited. They are stored in projects that can be deployed by the Admin Application when the templates are complete.
The Modeling Application is accessed using the
/modeling URL, for example
Models are the components that make up a project. The types of model available to use within a project are:
- Processes are the collection of components that are used to build and represent business processes using BPMN 2.0 specification.
- Forms are used to capture data into specially designed field types such as text, date, file uploads and multiple choice radio buttons. They are filled in by users of an application.
- Connectors are used to handle interactions with external systems as part of a process. This includes actions such as retrieving, generating, updating and storing content in the Content Services repository, sending emails and utilizing services such as AWS Comprehend, Textract, Rekognition and Lambda functions.
- Decision tables are used to manage business decisions within process workflows.
- User interfaces set the end user interface for users to interact with content, tasks and processes for the project.
- Scripts are used to execute a custom script as part of a process
- Triggers are used to define a set of event criteria. When the event criteria specified in the trigger is met, the event is published and an action containing a payload is kicked off.
- Content models describe how data should be stored in the repository and the metadata that can be associated to the content and folders within that model.