URIs for Starting BPM Processes
This topic lists the available uniform resource identifiers (URI) that you can use to start BPM processes.
In the table below the following placeholders are used:
-
<vendor>
Vendor name of the development component where the process that is to be started is located (for example, "company.com")
-
<dc-name>
Name of the development component where the process that is to be started is located (for example, "tc~test~dc")
-
<process-technical-name>
Technical name of the process that is to be started
-
<start_data_type_name>
Name of the XSD type that was defined for the process start data at design time
-
<JSON object for start data entity>
JSON object representing an entity for the <start_data_type_name> entity type
| Action | URI | Description |
|---|---|---|
|
Get metadata of the process start data |
GET /bpmodata/startprocess.svc/<vendor>/<dc-name>/<process-technical-name>/$metadata |
The response body provides metadata of the process start data. The returned metadata provides information about the structure of the process start data. |
|
Get information about a process that is to be started |
GET /bpmodata/startprocess.svc/<vendor>/<dc-name>/<process-technical-name>/StartData GET /bpmodata/startprocess.svc/<vendor>/<dc-name>/<process-technical-name>/StartData(vendor='<vendor>',dcName='<dc-name>',processTechnicalName=<process-technical-name>') |
The response body provides information about the process definition of the vendor with the name <vendor>, located in the development component with the name <dc-name>, and with the name <process-technical-name>. |
|
Get process start data |
GET /bpmodata/startprocess.svc/<vendor>/<dc-name>/<process-technical-name>/StartData?$expand=ProcessStartEvent/<start_data_type_name> GET /bpmodata/startprocess.svc/<vendor>/<dc-name>/<process-technical-name>/StartData(vendor='<vendor>',dcName='<dc-name>',processTechnicalName=<process-technical-name>')?$expand=ProcessStartEvent/<start_data_type_name> |
The response body provides the process start data that is needed to start a process for the specific process definition. It contains the process start event and an empty version of the data that is needed to start the process. <start_data_type_name> is the name of the XSD type that was defined for the process start data at design time. |
|
Start a process |
POST /bpmodata/startprocess.svc/<vendor>/<dc-name>/<process-technical-name>/StartData Request Body: {
"ProcessStartEvent": {
"<start_data_type_name>": {
<JSON object for start data entity>
}
}
} |
* The request body should contain an entity for the StartData entity type. The response body contains the process start data of the started process along with the unique identifier of the process instance (ProcessInstanceId) started by the OData service. |
|
Start a process |
POST /bpmodata/startprocess.svc/<vendor>/<dc-name>/<process-technical-name>/ProcessStartEvent Request Body: {
"<start_data_type_name>": {
<JSON object for start data entity>
}
} |
* The request body should contain an entity for the ProcessStartEvent entity type. The response body contains the process start data of the started process. |
|
Start a process |
POST /bpmodata/startprocess.svc/<vendor>/<dc-name>/<process-technical-name>/<start_data_type_name> Request Body: {
<JSON object for start data entity>
} |
* The request body should contain an entity for the <start_data_type_name> entity type. The response body contains the process start data of the started process. |
* To protect modifying requests such as POST against cross-site request forgery (CSRF) attacks, a valid CSRF token is required. Therefore, before you use the POST request you need to request a CSRF token with a GET request containing the header 'X-CSRF-Token' with the value 'Fetch'. Modifying requests without a valid CSRF token are rejected.