controlled published assets workflow

EditAsset.bpmn calls votingSubProcess_ControlledPublication.bpmn, and passes form properrties, including “processInstanceId”.
But it seems votingSubProcess_ControlledPublication defines no such form property, hence the reason why it might be simply discarded.

Later in votingSubProcess_ControlledPublication, a function tries to use the variable processInstanceId, which might explain your issue.

You can ask your question on the Latest Marketplace topics - The Data Citizens Community (collibra.com) section of the forum, and maybe @paulo.taylor can help?

I would try to fix this by adding a property “processInstanceId” to the votingSubProcess_ControlledPublication.bpmn start form.

The Controlled Publication workflow is started from the Edit Asset workflow.
This workflow creates a draft asset of the current asset, and appends the name _DRAFT to the end of it.
On the draft asset, a customized version of the voting subprocess is started.
Once the user completes the changes to the draft asset, they click on the button so that the changes can be voted on.
After the voting is complete, the result to communicated back to the original asset through use of the processInstanceId of the Edit Asset workflow.
If the workflow was started properly then the processInstanceId is passed from Edit Asset to the Voting Sub Process.
And when voting is complete, it sends a message to that particular processInstanceId with the results.

How did you start the workflow? and is the error from the draft asset or the original asset?

Reading this thread, to avoid jumping from issue to issue, I would encourage you to book in some time with professional services to help you install the workflow.

Having used the service in the past, I definitely would recommend it.

With regards to your current issue, the votingSubProcess exists as a workflow to be initiated by other workflows. When another workflow initiates the votingSubProcess, it passes values to the form properties you’re seeing. What you’re currently doing is initiating the votingSubProcess manually hence why the values are blank.

As Alvin stated, the votingSubProcess exists as a workflow to be initiated by other workflows, and from the images provided it looks like you are manually calling the votingSubProcess on an asset (which is incorrect).

According to the documentation, after setting up the workflows, in order to start the process, you navigate to the original asset. Then on the original asset, click on the button named ‘Edit Asset’. This is the Edit Asset workflow, which creates the draft, and links to the draft asset, which also calls the votingSubProcess for Controlled Publications on the draft asset, it also passes in the processInstanceId variable which is not something that should be manually passed.

I would also recommend booking a session with Coaching Services to walk you through this if you have any further questions.

Hi all,

thank you for all answers, even if I followed the documentation the SubProcess were called manually and we changed some parts of the code , now it is working.

Have a nice day!

Hande