on 10-28-2021 5:28 PM
Hello community,
i´m calling the start workflow via Rest API. So the initiator of the workflow is the service user of my workflow service.
Now this is a problem when i use a service task with principal propagation on the start event.
So, is it possible to set the initiator of the start event when i´m calling the REST API? f.e. a technical user? or any other suggestions to solve this kind of problem?
thanks and br,
Sudhir
Hi,
you need to check the response body of the request with status 400. There is usually no connection between custom attributes and principal propagation.
Regards,
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sudhir,
you cannot overwrite this information, because it shows the technical ID which has really started the workflow.
You can look for other authentication types to start the workflow, where for example the start user is more appropriate to your scenario. You could authenticate the API call with OAuth2 Password Grant with a technical user for example.
When it comes to the respective information of tasks that have been created within the workflow, you might make use of the "CustomCreatedBy" custom attribute which replaces (but in MyInbox display only) the technical information which user actually started the workflow.
Regards,
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
67 | |
8 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.