Trigger a process
On RunMyProcess, a process can be launched in several ways. Each solution for triggering a process has strong implications on the input variables passed to the process and the link to instances. in this pages, we will review each solution
Schedule a process with a Timer
You can schedule a process : it will be launched automatically at a predefined frequency (@see Process Start Event).
In order to trigger a process with a Timer, you have to configure certain parameters.
(1) Choose Timer as Trigger.
(2) Choose the number of repetitions of launches. Click "Unlimited" if you want the process scheduling to loop indefinitely.
(3) Delay between two launches of the process. Choose the delay between responses days, hours and minutes.
When a process is triggered with timer configuration, initial parameters are not configured.
Trigger a process by email
You can also trigger a process by sending an email to our platform (@see Process Start Event).
(1) Choose Trigger Message
(2) Message box address : Email address to launch the process. You can click on link to copy Live email address needed to launch the process. Format of email address is the following :
process+{customerid}.{processid}@runmyprocess.com to launch process in Live state and
process+{customerid}.{processid}.TEST@runmyprocess.com to launch process in Test state.
(3) You can map the subject of your email to an input variable of the process.
(4) The content of your email can be associated to an input variable of the process.
(5) You can map also the cc field to a variable.
(6) The attachement of your email can be associated to a variable of the process.
You can manage messages through the flex IDE.
(@see Messages Monitoring)
Please note that the user who launches the process must belong to the lane of the process.
Trigger a process from a Web Interface
You can launch a process using a Web Interface.
(1) Create a Button and choose Start Process as Action.
(2) Choose the process you want to launch.
(3) You can define On click action after pushing the button :
- Show pop-up message after pushing the button.
- Close the window opened.
- Show the message and then close the window.
- Redirect to another page.
- Reload the same screen after button pushed.
- Load next screen.
The variables of the web interface will be considered as initial parameters of your process.
This is the most common way to launch a process. Using this solution brings many advantages
- the measures of the process launched will be transmitted to the instances (web interface instanciation)
- globally the process is linked to the instance which means for example that you can retrieve the generated manual task url in the process execution
Subprocesses
In order to factorize tasks, you can include a process in another process. The included process will be called a subprocess.
A subprocess is always launched synchroneously with respect to the main process, which means that the main process will only be resumed once the subprocess execution is over.
A subprocess can be executed as a different process (case by default) or as a nested process.
When a subprocess is confgured as a nested process it means that the subprocess ans the main process will share the same execution context. The parameters will be shared and the history (@see Web Interface History and Comments Widget) too. On the other hand, when a subprocess is not configured as a nested process, one can define precisely which variables are going to be passed from the main process to the subprocess and vice-versa.
Last a launched subprocess will be linked with the launched main process. The main request is said to be the parent of the subrequest.
For more information on subprocess configuration @see Subprocess
Process Listener
A process can be launched from a web interface without being linked to it ( meaning that the measures defined on the process will not be passed to the web interface ) using the process listener feature.
Launching a process as a process listener can also be used to launch several process from the same web interface.
All the variables from the web interface will be passed to the process listener.
A process listener can be configured as shown in the link below (section process listener) : (@see Process Listener).
Trigger a process directly by Web Service
You can trigger a process directly by Web Service.
When done using a connector in a process, it can be considered as aysnchroneous. In this case, the triggered process parent will have no parent to be linked to.
Here is the API to launch a process by web service.
POST https://live.runmyprocess.com/live/${P_customer}/process/${process_id}?P_mode=${execution_mode}&P_version=${version_id}
Content-Type : application/*
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:base="https://live.runmyprocess.com/">
<title>Title</title>
<entry>
<title>Title</title>
<content type="text/base64">${encrypt('BASE64',initial_parameters)}</content>
</entry>
</feed>
with input params a JSON object containing the parameters to be passed to the process
{"my_var_1":"foo","my_var_2":"bar"}
Please give details of the problem