Process Modeling¶

Emakin facilitates process development through XML-based process definitions, enabling version control and seamless switching between versions.

These definitions encompass a comprehensive range of components, At its core, pools define the structural elements like process diagrams, tasks, forms, actions,roles, and routes, ensuring clarity and organization.

Development extends to screens for standalone form interfaces and form templates for reusable components, boosting efficiency across workflows. Integration is enhanced through web services and script modules that serve as reusable function libraries.

Decision-making is supported with decision models and decision tables, while a robust data model handles process or form data with XML namespace support.

Developers can also leverage tools like XPath for data evaluation, XQuery for No-SQL database interactions, and JavaScript based custom scripting, complemented by an extensive scripting reference for business operations.

To ensure global accessibility, localization features.

A process definition consist on the following parts:

• Pool - Process Diagram, Tasks, Forms, Actions, Roles, Routes
• Screens - Forms without any process
• Form Templates - Reusable form parts within process
• Web Services - SOAP services
• Script Modules - Reusable function libraries
• Reports - Report definitions
• Decision Models - Business rules
• Data Model - Process or form data
• Databases - Relational database schemas
• Namespaces - Xml namespaces used in the process definition
• Localization - Language translations for the process definition
• Content Types - Externally usable form parts
• Access Scopes - Security scopes for external users
• Documents - Development documentation or notes