Process Start Event

The Start Event allows you to configure the way the process will be triggered. There are several ways that a process can be launched - through the submission of a form, by meeting a condition, by an email or by a timer. To view or edit the configuration of a process start event, click on the event in your process design and choose to edit it by clicking on the pencil. The pop up window is divided into two taps - one for the start event and one for the output variables.

Table of Contents

Process Start Event
- 1 Event
- 2 Output variables

1 Event

The Event tab is where you can configure the start event. It has the following fields:

Field Name	Description
Name	The Name of the task - this is defaulted to 'Start'.
ID	The unique ID of the task. The ID is generated and cannot be modified.
Event type	The event type is `START`, this cannot be modified.
Trigger	Choose the trigger for launching the process; each option is described bellow.

1.1 Web Trigger

After choosing "None" from the Trigger options to specify that the process can be triggered by a POST request (i.e. a web service call) or a RunMyProcess Web Interface, the following configuration options are made available:

Field Name	Description
Redirect to	This allows you to choose a web interface or an HTML file that will be sent as a result when the process has started successfully.
Description	A description of the task.

A process can be started through the submission of a basic HTML form (if the process is public); all parameters sent will be available as the initial parameters of your process. Here is an example:

<html>
<form name="RMP" method="POST" action="https://live.runmyprocess.com/live/${customer_id}/process/${process_id}">
<input name="IDENTIFIER" value="a" />
<input name="HASH" value="${my_hash}" />
<input name="OPERATIONTYPE" value="payment" />
<input name="CLIENTIDENT" value="${client_id}" />
<input type="submit" name="ok" value="RMP" />
</form>
</html>

1.2 Message Trigger

After choosing "Message" from the Trigger options to specify that the process can be triggered by an email, the following additional configuration options are available:

Field Name	Description
Message box address	This is the email address used to launch the process. In the Live environment, clicking on will copy the email address to the clipboard, it can then be pasted into this field. The format of the email address is: `process+{customerid}.{processid}.{key}@runmyprocess.com` to launch the process in Live state and `process+{customerid}.{processid}.{key}.TEST@runmyprocess.com` to launch the process in Test state. Please note that when launching your process in Test, the last saved version of the process will be used as process versioning is not available in Test. The mailbox is pulled every five minutes.
Map subject to	Specify which process input variable (see: Process Input tab) will contain the subject (object) of the email.
Map content to	Specify which process input variable (see: Process Input tab) will contain the content (message) of the email.
Map cc to	Specify which process input variable (see: Process Input tab) will contain any email addresses that were specified in the CC field of the email that triggered the process. The email addresses will be held in a JSON array e.g `["Thibault Granie <tgranie@runmyprocess.com>","Maria Thomas <mthomas@runmyprocess.com>"]`
Map reply-to	Specify which process input variable (see: Process Input tab) will contain the reply-to attribute from the email that triggered the process. This can be used to send an email to this person later in the process.
Map attachment to	Specify which process input variable (see: Process Input tab) will contain the id of the attachment files downloaded to the RunMyProcess server. If there are several attachments, the variable will be an array of IDs.
Parsing format	If you want RunMyProcess to parse the content of your email before injecting it into a "Map content to" variable, choose a different content format to the default one (Text).
Use HTML format if exists	Check this box if you want the HTML body of the email to be mapped to your "Map content to" variable.
Description	A description of the task.

For security reasons, the sender of the email (from) must belong to the lane of the event start (with the exception of public processes).

1.3 Timer Trigger

The timer trigger enables the process to be scheduled to launch itself automatically at a predefined frequency.

After choosing "Timer" from the Trigger options, the following configuration options are made available:

Field Name	Description
Start Date	Specify the date and time on which to start the scheduling of the process. Click "Now" if you want the scheduling process to start immediately.
Repetitions Number	The number of repetitions. Click "Unlimited" if you want the process scheduling to loop indefinitely.
Delay between reps	Specify any delay you require between launches of the process - the default is one day.
Description	A description of the task.

As an example, if you would like to schedule a process to launch automatically every day at 11am; set the Start Date to be today's date and the time to be 11am, set the Repetitions Number to be Unlimited and the Delay to be one day.

A process can only be launched by a Timer when it is used in a project version in Live state.

Scheduling will become effective after you have saved a version of the scheduled process and released it into the Production environment.

The period of a timer can be set up to a year (365 days).

Please note that the time is displayed in the user's local timezone but is stored in Coordinated Universal Time (UTC). This can cause confusion during the change from / to Daylight Saving Time as the server scheduler does not take into account the change. If you experience problems with your scheduled process following a time change, we recommend that you amend the start date of the trigger to a date where the time change has already taken place (e.g. the day after the time change).

1.4 Condition Trigger

After choosing "Condition" from the Trigger options to specify that the process can be triggered if a Condition is met (evaluates to True), the following additional configuration options are available:

Field Name	Description
Execution Frequency (min)	Specify how frequent you want the condition to be evaluated.
Composite API	Specify the Composite API which will evaluate and return the result of the condition (`True` or `False`).
Description	A description of the task.

2 Output variables

This tab allows you to initialize variables at the beginning of the process. You can find more information about output variables here.