Workflow
Created Nov 18, 2023
54 members
147 discussions
The Workflow topic in the Collibra Community is a space for users to ask questions, share tips, and troubleshoot everything related to building and managing workflows using Collibra’s Workflow Designer. Discussions range from automation triggers and custom scripts to improving task management and UI behavior—ideal for users looking to streamline processes and boost platform efficiency.
- Discussion

Matheus Anitelli
Workflow Started from a Form: How to Associate a Newly Created Asset as the Task's Related Resource?
Hi everyone, I'm facing a workflow design challenge and would appreciate any guidance from those who have implemented similar patterns. Background Originally, our Data Definition workflow was started directly from a Business Term asset page. In that scenario, each user task displayed the asset as the Related Resource in the user's Inbox and task details. Users could immediately understand which asset they were working on and navigate to it easily. We have recently redesigned the process. The new flow is: User launches a workflow from a start form (not from an asset page). The workflow creates a new Initiative asset. The workflow creates relationships between the Initiative and multiple Business Terms. A Call Activity launches a child workflow (Data Definition Process). Users receive tasks within the child workflow. The Problem Because the workflow is initiated from a form rather than from an asset page, the resulting user tasks do not display a Related Resource . The Initiative asset is successfully created and its ID is available throughout the process. I can retrieve the asset and its metadata in Script Tasks without any issue. However, the user tasks still do not show the Initiative as the Related Resource, making it difficult for users to identify which Initiative a task belongs to. What I've Already Tried Passing the Initiative ID through Call Activity input mappings. Passing an item variable through the Call Activity. Recreating the Initiative asset context in the child workflow using: Recreating the Initiative asset context in the child workflow using: UUID initiativeId = string2Uuid(execution.getVariable("initiative")) def initiativeAsset = assetApi.getAsset(initiativeId) Storing the Initiative asset ID and name as workflow variables. The child workflow receives these values correctly, but the Related Resource remains empty. My Question Is it possible to associate a workflow instance or user task with an asset after the workflow has already started , so that the asset appears as the Related Resource in the Inbox? More specifically: Can a workflow started from a global form dynamically set a Related Resource later in the process? Is there a specific workflow variable (such as item , resourceId , etc.) that controls this behavior? Or is the Related Resource only determined at workflow instantiation time when the workflow is launched directly from an asset page? Any recommendations, best practices, or examples would be greatly appreciated. Thanks in advance!
3 weeks agolast reply 2 weeks ago - Discussion

Asif Rasul
- Question