Overview
Bizagi features an OData service which handles aspects of the Experience design.
Through the Processes URI, you CAN handle data related to the Processes of a user as described at Processes data.
This section describes how to create cases for a given process.
Resource URL
Start WITH the following URL:
[your_bizagi_project_url]/odata/data/processes([ID_process])/start
Customizations:
•[ID_process]: The GUID of a specific process as returned when invoking the Processes data.
•[your_bizagi_project_url]: The URL where end users access the Bizagi Work Portal.
For an on-premises Bizagi project, the URL would be:
https://[your_server]/[your_project]/odata/data/processes([ID_process])/start
For Automation Service projects, the URL would be:
https://[project_environment]-[your_project]-[your_company].bizagi.com/odata/data/processes([ID_process])/start
Example
To start a new case, invoke the URL described above using an HTTP POST.
Consider including the following JSON structure in the body to send parameters:
{
"startParameters": [
{
"xpath": "[xpath_name]",
"value": "[value_for_xpath]"
}
]
}
Customizations:
•[xpath_name]: The exact Xpath expected by parameters of that Relevant process.
•[value_for_xpath]: The value you want to set to the Xpath parameter.
If you have more than one parameter, use:
{
"startParameters": [
{
"xpath": "[xpath1_name]",
"value": "[value_for_xpath1]"
},
{
"xpath": "[xpath2_name]",
"value": "[value_for_xpath2]"
}
]
}
If no parameters are expected, use:
{
"startParameters": [
]
}
|
Parameters are taken from the process' start form. If no start form is defined, parameters are blank. |
The following image illustrates data in the body you can send in an HTTP POST and the response you obtain indicating the case number of the created case (in the returned value):
Specific formats
Refer to the following for specific use cases:
•To filter the search with parameters, consult the notes for the different data types at Values and formats for data types.
•To dynamically obtain business values that you may need as input parameters to start a new process, refer to Related entities services.
•To dynamically obtain the columns you need to fill out to send when creating records in a collection, refer to Columns in collections.
•To learn how to comply to the format expected when sending dates, files and images or Boolean fields, refer to Sending input parameters.