The glossary defines the central terms relevant to RunMyProcess.
- API Listener
- Composite API
- Custom List
- Custom Widget
- Easy Builder
- Enterprise Process Store
- Execution Mode
- Manual Task
- Process Request
- Process Report
- Web Interface
- Web Interface Instance
- Web Interface Report
An API listener is configured within a web interface to listen for a certain event. When the event occurs, the listener triggers a composite API, a process or a connector.
An application in RunMyProcess is composed of one or more projects which perform a specific task. An application allows you to launch a process through a Web page hosted on the RunMyProcess platform. The applications you are allowed to access can be found in the Enterprise Process Store.
The basket is part of the Enterprise Process Store. It shows end users the complete set of tasks they have outstanding across all applications.
A collection is a custom database you create, populate, and manage in support of your applications. It can store important data, for example on customers, products, or assets.
A connector is a project resource that simplifies the integration of your application with external systems. RunMyProcess provides an extensive library of pre-built connectors together with the tools necessary to create your own.
A composite API (CAPI) is a project resource that you use to implement API-accessible business logic or data integrations. It refers to a sequence of tasks that run synchronously. The tasks' execution path is not persisted.
A custom list enables you to create a static list of reference information that can be reused in multiple screens throughout your application, for example, for drop-down lists or validation.
A custom widget is a user interface that has been created and can be added to the palette of drag-and-drop widgets available to your developers. It is essentially a re-usable web interface.
Easy Builder is a simplified environment for non-technical people to automate straightforward business workflows.
EnterpriseConnect is a technology used to access on premise services. It is essentially a secured tunnel between the RunMyProcess platform and your local network.
Enterprise Process Store
The Enterprise Process Store contains all the applications you build within your account. It is the central app store where end users can access their applications and tasks.
An application’s execution mode denotes the environment in which the application runs. RunMyProcess offers three isolated environments: Test, Acceptance, and Live.
Apache FreeMarker is a template engine for transforming and preparing data in a particular format (e.g. XML).
A lane represents a scope of responsibility for tasks within a process. For example, different tasks may be handled by distinct roles, departments, or systems.
A manual task is a type of process step. The step is assigned to a user role or to a specific person. The step must be manually completed in order to move forward in the process.
A measure defines process data that you explicitly tag within your application as key metrics for gauging business process performance. A measure is used for monitoring processes. It allows you to track KPIs in your reports.
OAuth2 refers to the OAuth 2.0 protocol, the industry-standard protocol for authentication and authorization. It enables third-party applications to delegate user authentication and access limited user account information.
An organization describes the structure of a company and its subsidiaries. Several organizations can be used to distinguish partners or clients involved in specific tasks of a process.
A process captures your application's business logic. It is modelled using Business Process Modelling Notation (BPMN) and executed by the platform at runtime in response to user- or system-initiated events.
A process request is an instance that is created in RunMyProcess when a process is launched.
A process report provides a visual representation of process execution. It shows which path a process request takes and highlights any errors during execution.
A project organizes all resources related to a specific solution and manages their joint lifecycle through versioning.
A provider represents an external system (e.g. Salesforce) that can be integrated in your application by RunMyProcess. Providers form the basis for organizing connectors.
A role is defined for an organization. Each role has its own function within the organization. A user can belong to any number of roles.
RunMyApp is a mobile app for Android, iOS, and Windows that provides a container for RunMyProcess applications to make use of the standard capabilities of smart devices such as camera or GPS.
A screen is a web page that belongs to a web interface. In a web interface, you can create as many screens as necessary. A screen can be used to launch a process or be used within a manual task.
A version allows you to 'freeze' projects so that you can deploy, manage, and rollback deployed applications based on a specific set of project resources. Only one version of a project can be live.
A Web interface is the user front end of a RunMyProcess application. It provides a device-independent way for end users to interact with your application on a PC, tablet, or mobile.
Web Interface Instance
A Web interface instance is created in RunMyProcess when a Web interface is submitted during process execution by the platform at runtime.
Web Interface Report
A Web interface report visualizes statistical and data-related information on Web interface instances launched by your application.
A widget is a standard user interface design component. Developers use widgets to quickly design forms and user interfaces using drag-and-drop.