Introduction

There are various workflow entry points in the CoreOne Suite which each trigger a workflow with a predefined input object as the input. The input of the workflow definitions itself is not strongly typed. This page and the subsequent pages therefore document the workflow entry points and the appropriate input data.

Workflow Entry Points by entity

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.

{
  "activityId": null,
  "correlationId": null,
  "contextId": null,
  "input": {
	  "Data": {
		Id : 5450,
		DisplayName : "Beate Gielsdorf",
		TypeName : "iTsense.Moving.Backend.Services.DmcoreService.Adapters.NHibernate.Servicedmcore.OrganizationUnit",
		ExternalIdentifier: "CHE 367367116"
	  },
	  "Context": {
		  "CoreIdentityId": 3265,
		  "UserId": 17177,
		  "AppCustomerId": 900000
		}
	}
}

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.

DefaultCertificationWorkflow guid:e9773f49cc6c437094a6aa2bb4f80f5e

"Data": {
  certificationId : uint,
  targetObjectId : uint,
  targetObjectTypeId : uint (based on servicedmcore_certification_object_type)
}

"Data": {
  certificationId : 5450,
  targetObjectId : 1,
  targetObjectTypeId : uint (based on servicedmcore_certification_object_type)
}