Introduction
Each workflow that is being triggered within There are various workflow entry points in the CoreOne Suite has which each trigger a workflow with a predefined input object stored in as the input
variable and some static properties dependent on the workflow endpoint that you are calling such as ActivityId
, CorrelationId
and ContextId
. The input of the workflow definitions itself is not strongly typed. This page and the subsequent pages therefore documents document the most common workflow triggers entry points and their the appropriate input
data structure..
Workflow Entry Points by entity
Page Tree | ||||
---|---|---|---|---|
|
Test your workflows by using the API
You can test your workflows by emulating the workflow entry point through the API. Please make sure that you check the appropriate Swagger documentation for the endpoint that you are calling. For example if you would like to trigger a Workflow Definition, the input will look as shown below. The ActivityId
, CorrelationId
and ContextId
are used by the trigger endpoint and has a variable called input
. Inside of that input
you have to put the appropriate input for your specific workflow.
...
The input itself always has a Data
and a Context
section. The first contains the actual input data and the later the information about who is executing this workflow.pagetree
DefaultCertificationWorkflow guid:e9773f49cc6c437094a6aa2bb4f80f5e
Workflow Type Name (Id) | - | ||
Configured on | - | ||
Description | Invoked from the CertificationTask - when object needs recertification - the workflow Guid is defined in task parameters | ||
Data structure |
| ||
Example |
| ||
C# class name |
|