Skip to content

Developer Guide

This guide is for process builders who design, integrate, and maintain Emakin solutions. It combines conceptual guidance, process-modeling reference, integration documentation, and worked examples so you can move from design to implementation without switching between unrelated sources.

How to Use This Guide

Choose the section that matches the work you are doing:

  • Process Modeling for process definitions, forms, databases, decision models, and query languages
  • Integration Services for REST services, embedding, and channel web hooks
  • Process Examples for tutorial-style walkthroughs that show complete scenarios
  • Scripting for script concepts and the generated scripting reference entry point

Key Concepts

The following terms appear repeatedly across the guide:

Process

A process is the executable definition of a business flow. It includes the process diagram, forms, data model, decisions, integrations, and other assets required to run the workflow.

Folder

Processes are grouped under folders. Folders control how builders organise start points, reporting locations, and security boundaries for business applications.

Channel

Channels are collaboration spaces where teams communicate, exchange updates, and optionally manage cases.

Case

A case is a trackable work item inside a channel. Cases can carry assignments, deadlines, files, activities, milestones and related process instances.

Process Definition

Most developer-facing configuration in Emakin is stored in the process definition. Process definitions are versioned and can include diagrams, forms, databases, decision models, scripts, services, and supporting assets.

Business Data

Process and form data is primarily carried in XML through the data model. That model can be extended with relational or XML database storage where needed.

Work Item

A work item is the runtime task generated by a process. Work items can be assigned to users, groups, units, or the system itself depending on the process design.

Typical Delivery Flow

Most Emakin solutions are built in the following order:

  1. Model the process structure and its data.
  2. Design the forms and screens.
  3. Add rules, scripts, databases, and integrations.
  4. Test the runtime flow with work items, cases, or embedded forms.
  5. Refine the design through examples, iteration, and versioned updates.