Terms and concepts

1 A-E | 2 F-J | 3 K-O | 4 P-T | 5 U-Z

Terminology definition and explanation of key concepts as used in the context of Emakin and the business applications built with its low-code development platform.

A-E

Business Process

A business process, also referred to as a business method, can be understood as a grouping of structured and related actions or tasks serving a particular purpose, which upon completion result in fulfilling a service or delivering a product for a customer, either internal or external.

Business Process Management Systems (BPMS)

Business Process Management Systems (BPMS) are comprehensive software platforms that enable organisations to design, implement, monitor, and optimise their business processes. These systems provide tools for mapping out end-to-end processes, automating repetitive tasks, managing workflow execution, and analysing performance metrics to identify improvement opportunities.

Case Management

Case Management refers to the process of handling, coordinating, and managing all aspects of a case—from initiation to resolution—within a system. It encompasses tracking case progress, managing related documents and data, assigning tasks to appropriate team members, and implementing workflows to ensure efficient case progression.

Emakin

Emakin is a business process management system (BPMS) for enterprises, with powerful customisation capabilities and advanced collaboration features, focused on user productivity and an enabler of continuous business improvement.

F-J

Instance

An Instance, refers to a specific occurrence or execution of a workflow process. Each instance represents a single, operational run-through of the defined workflow, starting from initiation and moving through various stages or tasks until completion. It is created every time a process is triggered. This could be due to a user action, such as submitting a form, or an automated event, like reaching a scheduled date. Instances are used to track the progress, status, and data of individual workflows, allowing for detailed monitoring, analysis, and management of each unique process execution within the system.

K-O

Low-Code

Low-Code is a software development approach that minimises the need for manual coding, enabling faster delivery of applications through graphical user interfaces and configuration instead of traditional hand-coded computer programming.

No-Code

No-Code is a software development approach that enables users to create applications and workflows without writing any traditional computer code. This methodology relies on visual development environments where users can design and build applications by using drag-and-drop interfaces, pre-built templates, and configurable elements.

P-T

U-Z

Worklist

A list of work items to be performed or completed; an agenda.