Bizagi features an OData service which handles aspects of the Experience design.
Through the Stuff URI, you may handle data regarding the My stuff section for the currently logged on Stakeholder, and you may also part from there to browse actions of records, as described at My Stuff's actions data.
This section describes how to execute a given action from data in My Stuff.
Start off from the following URL:
•[ID_stuff]: The GUID of a specific collection of My stuff as returned when invoking the My Stuff's actions data.
•[ID_value]: The ID of a specific record, as returned when obtaining the My Stuff's actions data.
•[ID_action]: The ID of a specific action, as returned when obtaining the My Stuff's actions data.
•[your_bizagi_project_url]: Corresponds to the URL where end users access the Bizagi Work portal.
For instance for an on-premise Bizagi project, such URL would be:
While for Bizagi PaaS projects, such URL would be:
To trigger an action which starts a new case, the URL described above is invoked by means of an HTTP POST.
Consider including the following JSON structure to send parameters in the body:
•[xpath_name]: The exact xpath as expected by parameters of that process' triggering action.
•[xpath_datatype]: The data type for that xpath as expected by each parameter..
•[value_for_xpath]: The value you want to set to such xpath parameter.
Notice if you have more than 1 parameter, you would use:
Similarly, if no parameters are expected, you would use:
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 (at the returned value):
Notice this other image shows a previous invocation regarding parameters that the action expects (as you would need to send the exact data type and matching Xpath information):
Refer to the following links for specific use cases:
•To filter the search with parameters, consider the notes for the different data types, as described at Values and formats for data types.
•To dynamically obtain business values that you may need as an input parameter to start a new process or complete an activity, 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.