Bizagi features an OData service which handles aspects of the Experience design.
Through the Processes/Cases URI, you may handle cases data related to the pending activities of a user (not stakeholder), as described at Cases from processes data.
This section describes how to query the list of activities of a given case.
Start with the following URL:
•[ID_process]: The GUID of a specific process as returned when invoking the Cases from processes data.
•[ID_case]: The GUID of a specific case as returned when invoking the Cases from processes data.
•[your_bizagi_project_url]: The URL where end users access your Bizagi Work portal.
For an on-premises Bizagi project, the URL would be:
For Automation Service projects, the URL would be:
The following image illustrates how you can send an HTTP GET for this resource:
Returned results include, for each workitem (inside the value element):
•id: The internal identifier (integer) (typically an activity or event instance).
•taskName: The name (string).
•state: The state in terms of: red (overdue/expired), yellow (at risk), or green (on-time).
•SolutionDate: The estimated solution date for the case, as given by the process' SLA.
•@odata.id: The unique URL to access the workitem.
•Parameters: The list of data (attributes) and values that the workitem uses. This array is not empty when the workitem has a form associated to it and its renders are editable and visible.
The parameters include for each attribute:
oXpath: The full Xpath (includes its name).
oName: The name of the attribute.
oType: The data type. For a list of possible values regarding data types in Bizagi, refer to Types of data.
oId: The identifier for the Xpath.
Through the @odata.id property, you can obtain the record's details only, instead of a full list.
For example, use:
For a given workitem, you can send out parameters to complete it (as if clicking Next in the Work portal for that activity or event).
For more information about how to complete workitems, refer to Activities from processes completion data.