Skip to content

Process Modeling

An Emakin process definition is a self-contained XML package encompassing all requirements necessary to execute a business process. This definition integrates a comprehensive array of components that ensure clarity, organization, and full functionality.

At its core, Pools define the fundamental structural elements, including Process Diagrams, Tasks, Forms, Actions, Roles, and Routes.

Development capabilities extend to Screens, which provide standalone form interfaces that can function as simple user interfaces or reporting dashboards without being directly tied to a process. Form Templates offer reusable components that can be embedded within forms to maintain consistency and accelerate development.

Integration with external systems is enhanced through Web Services and Script Modules. These serve as libraries of reusable functions that can be invoked within processes or exposed as RESTful web services.

Decision-making within processes is robustly supported by Decision Models and Decision Tables, enabling complex business logic. A powerful Data Model manages all process and form data, complete with XML Namespace support.

Developers can also leverage advanced tools and capabilities such as XPath for efficient data evaluation, XQuery for interacting with No-SQL databases, and custom JavaScript-based scripting. An extensive Scripting Reference is available to aid in the implementation of complex business operations.

Some processes may necessitate the use of custom-defined relational databases, referred to as schemas, to store and retrieve process-specific data. These tables can serve various purposes, such as lookup tables for display in list controls (e.g., dropdowns, radio buttons) or for storing core business data for reporting and analytical purposes.

To ensure global accessibility and usability, Emakin incorporates comprehensive Localization features.

A process definition is fundamentally composed of the following integral parts:

  • Pool - Defines the core process structure, including the Process Diagram, Tasks, Forms, Actions, Roles, and Routes.
  • Screens - Provides standalone form interfaces independent of a specific process.
  • Form Templates - Reusable components designed for embedding within forms.
  • Web Services - Definitions for SOAP-based service integrations.
  • Script Modules - Libraries of reusable functions for scripting logic.
  • Reports - Definitions for various process-related reports.
  • Decision Models - Encapsulates business rules and logic.
  • Data Model - Defines the structure for process and form data.
  • Databases - Specifies relational database schemas used by the process.
  • Namespaces - Manages XML namespaces utilized within the process definition.
  • Localization - Contains language translations for the process definition's elements.
  • Content Types - Defines externally usable parts of forms or documents.
  • Access Scopes - Specifies security scopes for external user access.
  • Documents - Stores development documentation or notes pertinent to the process.