×

Please give details of the problem

Skip to content

Instances

When an application is run on DigitalSuite, instances of its web interfaces, processes, and composite APIs are created and executed. The instances of processes are referred to as process requests.

Process requests and web interface instances are persisted in DigitalSuite and can thus, for example, be debugged easily and monitored in reports. By contrast, the instances of composite APIs are not persisted.

Process Requests

Process requests are created, launched, and executed on the DigitalSuite platform in response to start events, which are initiated by end users or systems. This can be in one of the following ways:

  • Manually by a user from a web interface
  • Automatically by a process listener defined for a web interface
  • By an email sent to a predefined email address in DigitalSuite
  • At specific times and intervals defined in a schedule
  • When a condition evaluated by a composite API is met
  • By a subprocess activity in another process
  • By a direct web service call (POST request), often from a connector

Each process request is launched in a specific execution mode. It is persisted with a unique ID and always has a specific status.

DigitalSuite provides tools and features to:

  • Create process reports which list process requests in a variety of ways and according to different criteria.
  • Monitor the execution of process requests.
  • Relaunch process requests at specific steps, for example, after fixing errors that caused the requests to fail. Before relaunching a request, runtime parameters and the status of individual steps can be changed as required.
  • Display the messages and schedules used to launch process requests.
  • Update running process requests to a new version of their process.

Administrators can delete process requests in any execution mode. DigitalSuite itself never removes requests launched in the Live execution mode. Requests in Test and Acceptance mode are deleted automatically after a certain period of time (see Execution Limits).

Web Interface Instances

Instances of web interfaces and their screens are created and opened when users start the application or access manual tasks in their personalized environment in web browsers or RunMyApp.

Web interface instances are persisted with a unique ID in the following cases:

  • The web interface instance has launched a process request.
  • The web interface instance was launched by a process request, usually to complete a manual task.
  • A Save as draft button included in the web interface instance was clicked at least once.
  • At least one file was uploaded by means of the Upload widget included in the web interface instance.

Web interface instances which have been persisted can be listed and displayed in web interface reports.

Composite API Instances

Like process requests, composite API instances are created, launched, and executed on the DigitalSuite platform in response to start events, which are initiated by end users or systems. This can be in one of the following ways:

  • Manually by a user from a web interface
  • Automatically by a composite API listener defined for a web interface
  • By an email sent to a predefined email address in DigitalSuite
  • At specific times and intervals defined in a schedule
  • By a Connector/Composite API activity in a process
  • When a condition evaluated by another composite API is met
  • By a direct web service call (POST request).

In contrast to process requests, the instances of composite APIs are not persisted. For this reason, it is not possible to list them in reports, or to monitor or control their execution in the same way as with process requests.