The types of project resources described in this document can be used in projects for building applications with RunMyProcess DigitalSuite.
A web interface is a user front end of a DigitalSuite application. It provides a device-independent way for end users to interact with the application on a PC, tablet, or mobile.
In a web interface, you can define a web page to launch a process and/or web pages for manual process tasks carried out by end users. A web interface allows you to group the web pages displayed to the users of a given process. It can contain as many web pages as required.
The WebModeler is the DigitalSuite Studio module for designing and testing web interfaces. For details, refer to WebModeler.
A process captures your application's business logic. This business logic is represented as a process flow. It is modelled based on the industry standard Business Process Modelling Notation (BPMN) and executed by the DigitalSuite platform at runtime in response to events initiated by end users or systems.
A process can be launched through a web interface and can be composed of any number of connected steps depending on the business logic mapped.
The ProcessModeler is the DigitalSuite Studio module for designing, developing, and testing your application's business logic. For details, refer to ProcessModeler.
A collection is a custom database that is created, populated, and managed in support of the applications. It can store any kind of data, for example on customers, products, or assets. It provides a defined data storage for a customer account.
When you create a collection, you create separate data for each execution mode. This ensures that Live data is never mixed with Test or Acceptance data.
Collections can be created and updated in the Project Configuration module. For additional details, refer to the Developer Guide.
A composite API (CAPI) is a project resource used 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 composite API is triggered by calling its API. The composite API's execution is never paused. This implies, for example, that a composite API cannot contain manual tasks for an end user. Due to the fact that the composite API's execution part is not persisted, a composite API is quicker than a process at run time.
Composite APIs can be created and updated in the Project Configuration module. For additional details, refer to Composite API.
A custom list is a static list of reference information that can be reused throughout your application. You can use it, for example, in web interfaces for validation or drop-down lists, checkboxes, or radio buttons.
Custom lists can be created and updated in the Project Configuration module.
Providers and Connectors
A provider represents an external system, for example, Salesforce, that provides services to be integrated into an application. A connector is the project resource that connects enterprise or web services offered by a provider with an application. It simplifies and speeds up the integration of the application with the external system.
A provider can group multiple connectors that are available at the same web address. Each connector is offered by a single provider.
A connector allows you to perform automated activities within a process. Each process itself is also represented as a connector that uses a pre-built default provider. These connectors cannot be modified since they are the web service representations of your processes.
If you want to reuse a specific provider and associated connectors across projects, it is recommended that you create a specific project for it. For example, creating a separate project for an email provider allows you to reuse it across all projects that require an email provider. Without a separate project, this is not possible since a project resource can only be attached to one project.
DigitalSuite provides an extensive library of pre-built connectors together with the tools necessary to create your own connectors. Providers and connectors are configured in the Project Configuration module. For information on how to use pre-built connectors in your projects, refer to the Connector Library.
Versioned files can either be uploaded to the DigitalSuite platform or created directly in the Project Configuration module with an integrated editor.
Versioned files must be distinguished from files that are independent of project versions. Like versioned files, these files are stored with your project on the DigitalSuite platform but they do not hold code or data for the application. For example, such files can be uploaded via a web interface to a running process request, downloaded from a web service, or created by end users during process execution.
Reports are a special type of project resource. They are not building blocks of an application, but rather a means of monitoring the application at run time.
Two types of reports are distinguished for different needs:
- A process report provides a visual representation of the execution of a process request. The path taken by the process request is shown, along with any errors that occurred during execution. The report lists the process requests that meet the report's criteria. You can drill down on each request to view its visual representation in the console. For more information, refer to Process Console.
- A web interface report visualizes statistical and data-related information on web interface instances launched by the application. A launched web interface is a web interface that has been used to launch a process, or within manual tasks of a launched process.