Process Management
This article demonstrates how you can use the Raptor Process Management functionalities in F&O to build your custom workflow logic.
Using Actor Integration
The Process Management solution includes support for actors, which can be accessed via the ProcessInstanceActorsTable entity. Below is how to use this integration to retrieve actor information for a specific imported invoice.
Entity Details
Entity Name:
EXAProcessInstanceActorsTableEntityPublic Collection Name:
ProcessInstanceActorsTablePublic Entity Name:
ProcessInstanceActorsTable
HTTP Request Example
When a process is started, you can create an HTTP request to retrieve the list of actors associated with a specific imported invoice. Use the following format:
dataAreaId: The corresponding legal entity.
RefTableName: Always
EXAPurchInvoiceImported.IdentifierId: The unique number of the imported invoice (this is the document number).
Example Response
The response will contain detailed information about the actors related to the specified invoice, including their personnel numbers, names, and primary email addresses:
Response Details
The response includes the following information for each actor:
Personnel Number: Unique identifier for the worker.
Name: The full name of the worker.
Primary Email Address: The worker's primary email address, sourced from their contact information in the system.
This data allows you to track which actors are involved in the process and provides easy access to their contact details for further communication.
Using History Integration
The Process Management solution includes support for process history, which allows you to track changes and log actions during the flow of a process. The process history can be accessed and updated through HTTP requests.
Entity Details
Entity Name:
EXAProcessInstanceHistoryTableEntityPublic Collection Name:
ProcessInstanceHistoryTablesPublic Entity Name:
ProcessInstanceHistoryTable
Process History Creation
When a process is started, you can create a process history record externally by sending an HTTP request with a JSON payload in the request body. This enables you to log the change or action associated with the process.
HTTP Request Example
To create a history record, send a POST request to the following endpoint:
Example Request Payload
Below is an example of the JSON payload that you would include in the body of the POST request. This example represents a record in the process history:
Explanation of Payload Fields:
CreatedDateTime: The timestamp when the history record is created.
Status: The current status of the process at the time the record is created (e.g., "Process Started", "Process Completed").
ActualUser: The user who triggered the action or change.
Comment: Any additional notes or details about the action or status.
By using this HTTP request and JSON payload, you can programmatically create process history records from external systems like Power Platform or AgilePoint.
When you query the ProcessInstanceHistoryTable entity, you will receive a response that includes details about the process history records. Below is an example of the HTTP response that you would receive:
Last updated