Skip to main content
Collibra Community logo
  • Community Resources
    • Discussions
    • Adoption Corner
    • FAQ
    • Take a tour
    • Request a demo
    • Community job board
    • Resources
  • Participate
    • Discussions
    • Ideation
  • Learn
    • Customer stories
    • Marketplace
    • Blogs
    • University
    • Knowledge Base
    • Developer Portal
    • Podcast “Data Citizens Dialogues”
    • Collibra Excellence Awards
  • Support
    • Support Portal
    • Documentation
    • Release notes
    • Product resource center
  • User Groups and Events
    • In-Person Events
    • Collibra Customer Events
    • Data Citizens® User Groups
All PostsDiscussionsCommunity ArticlesDiscussions
Leaderboards
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               
Discussions
Collibra Logo Community
  • About Collibra
  • Collibra Platform
  • Blog
  • Careers
  • Partner Program
  • Contact us
© 2026 Collibra. All rights reserved.
  • Privacy and legal
  • Do not sell or share my personal information
© 2026 Collibra. All rights reserved.
  • TagsChevronRightIcon
Workflow Performance
  • Discussion
    Pavan Shukla
    • Developers
             
    Pavan Shukla
    Handling Workflow Triggers with Import API
                                     

    I've configured a workflow with a start event set as 'asset added' and 'status changed.' It triggers perfectly when I manually add an asset or update its status, but it doesn't trigger when assets are imported using the Import API. I've read the documentation mentioning that the Import API bypasses workflow triggers. Given this, I'm seeking advice on the best approach to ensure that workflows trigger appropriately upon asset import.

    2 weeks ago
    0
             
  • Question
    • DevelopersChevronRightIcon
    Populating a drop down

    Has anyone written code they would be willing to share to populate a field in the workflow designer based on the values stored in the attribute? In other words: I have an attribute with about 10 different values (doc, xls, pdf, etc). I have created a form that allows users to pick the value they want to use. Rather than storing the values in collibra AND hard coding them into the form, I figure there has to be a way to read the values from the attribute and place them into the drop down on the form. RIght? thanks

    S Benson
    S Benson
    Posted 1 year ago • Last reply 11 months ago
    7
             
  • Question
    • DevelopersChevronRightIcon
    Preventing Relationship Deletion Until Workflow Completion in Collibra

    Hi everyone, I'm facing an issue with a workflow triggered after a relationship is deleted from a Data Product asset. The goal of the workflow is to prevent certain relationships from being removed. The workflow successfully captures the ID of the deleted relationship ( eventResourceId ). However, when I try to retrieve the type of the deleted relationship using that ID into findRelations , it no longer exists in the system — presumably because the deletion has already been finalized. My question is: Is there a way to delay the actual deletion of the relationship until the workflow completes successfully? Ideally, the relationship should only be removed if the workflow ends without errors or explicitly allows it. Any suggestions or best practices to handle this kind of validation or rollback mechanism would be greatly appreciated. Thanks in advance!

    Miguel Angel Lago Higos
    Miguel Angel Lago Higos
    Posted 1 year ago • Last reply 1 year ago
    3
             
  • Question
    • DevelopersChevronRightIcon
    Creating Explicit Relationships between Communities and "external" Assets

    We have been struggling with the lack of relationships between communities (or domains) and assets located outside of their path. So if we have a "Customer" community and a "Customer" business data domain asset that's located under a "Business Data Domains" community, we would want to go from the one to the other, for example to check the status of the Customer business data domain asset and if it's "active" get the business terms that sit within the Customer community To help with this we've added a "Community Anchor" asset type and use it whenever we want to make the relationship between a Community and an Asset explicit: the "Customer" community has an "Anchor" domain with a "Customer Community Anchor" anchor asset. We can then easily create a relationship between the anchor asset and the business data domain asset. This pattern is especially convenient for workflows that often need to move from the one to the other with confidence. We used to do this by matching names only, and it was not always reliable. Hopefully it might help some people with the same issue but I'm also very curious to hear how you handle this situation? Do you use similar patterns?

    Damien R
    Damien R
    Posted 1 year ago • Last reply 1 year ago
    2
             
  • Question
    • WorkflowChevronRightIcon
    Display Proposed Target Domain Names in Place of IDs

    Modifying the Propose New asset Workflow so that it will show the options for Proposed Target domain in a drop down list. how do I make the Domain name appear instead of the domainID?

    Lian Eloisa Martecio
    Lian Eloisa Martecio
    Posted 1 year ago • Last reply 1 year ago
    1
             
  • Question
    • WorkflowsChevronRightIcon
    Long-Running Workflows?

    Hey there, How bad would it be performance-wise (or otherwise) to have ~150-200 multi-day workflows running at one time? For context, I'm considering whether we should build complex, multi-day approval workflows in Collibra vs. another tool. Coming from an Appian background, my approach has always been to store request state (created, approved, returned for revision, etc.) in a record/database entity, and use "workflows" only to move the request between states (kicking a new workflow off when someone takes action, and completing it when the action is finished & new request state is written to the database). Is this a common practice with Collibra workflows as well? If not, have you seen/heard about any performance issues that may come from hundreds of workflows sitting in memory for days at a time? Thank you!

    Grant Gadomski
    Grant Gadomski
    Posted 1 year ago • Last reply 1 year ago
    1
             
  • Question
    • WorkflowChevronRightIcon
    Long-Running Workflows Performance

    Hey there, How bad would it be performance-wise (or otherwise) to have ~150-200 multi-day workflows running at one time? For context, I'm considering whether we should build complex, multi-day approval workflows in Collibra vs. another tool. Coming from an Appian background, my approach has always been to store request state (created, approved, returned for revision, etc.) in a record/database entity, and use "workflows" only to move the request between states (kicking a new workflow off when someone takes action, and completing it when the action is finished & new request state is written to the database). Is this a common practice with Collibra workflows as well? If not, have you seen/heard about any performance issues that may come from hundreds of workflows sitting in memory for days at a time? Thank you!

    Grant Gadomski
    Grant Gadomski
    Posted 1 year ago • Last reply 1 year ago
    3
             
  • Blog banner
    • Collibra Community TipsChevronRightIcon

    How to Propose New Business Term (Simple Workflow)

             

    How to Propose New Business Term (Simple Workflow) | Collibra Community | Tip Tuesday

    LILY ISAACSON
    LILY ISAACSONPosted 1 year ago
    0
             
  • Question
    • WorkflowChevronRightIcon
    How to import basic "org.apache.poi.*" api in a bpmn file

    Regarding the import errors(WARN c.c.d.w.s.g.v.NonPublicAPIValidator ) we are encountering, I wanted to provide a bit more detail based on a specific workflow example . This workflow has 33 import statements defined. Out of these, we are currently seeing direct import errors for only 3 APIs. 1. import org.apache.poi.xssf.usermodel.XSSFWorkbook(Importing [org.apache.poi.xssf.usermodel.XSSFWorkbook] is not allowed.Category: IMPORT. Critical: false. Is added to allow list: false.) 2. import org.apache.poi.xssf.usermodel.XSSFFont(Importing [org.apache.poi.xssf.usermodel.XSSFFont] is not allowed.Category: IMPORT. Critical: false. Is added to allow list: false.) 3. import org.apache.poi.xssf.usermodel.XSSFCellStyle(Importing [org.apache.poi.xssf.usermodel.XSSFCellStyle] is not allowed. Category: IMPORT. Critical: false. Is added to allow list: false.) Additionally, there are 4 other APIs that are being flagged as Indirectly importing. 4. Indirectly importing [org.apache.poi.xssf.usermodel.XSSFWorkbook] is not allowed. IMPORT. Critical: false. Is added to allow list: false. 5. Indirectly importing [java.io.File] is not allowed. Cause: java.io.File. Category: JAVA_IMPORT. Critical: false. Is added to allow list: false. 6. Indirectly importing [java.io.File.createTempFile] is not allowed. Cause: java.io.File.createTempFile. Category: JAVA_IMPORT. Critical: false. Is added to allow list: false. 7. Indirectly importing [java.io.FileOutputStream] is not allowed. Cause: java.io.FileOutputStream. Category: JAVA_IMPORT. Critical: false. Is added to allow list: false. This observation leads me to believe that the fundamental syntax and the way we are referencing the APIs within the BPMN file are likely correct, as the majority of the imports are being processed without Importing / Indirectly importing errors. Given this, could you please provide guidance on how we should handle the 7 APIs in question (the 3 with direct import warnings and the 4 with indirect import warnings)? Specifically, I'd like to understand: * Where and how we need to declare these 7 APIs within Collibra. * If there are alternative APIs available within the supported Collibra scope that could serve the same purpose for these specific use cases. Understanding the proper declaration method or suitable alternatives will be crucial for us to resolve these issues and ensure the workflow functions as expected while adhering to Collibra's security and stability guidelines.

    monalishapal
    monalishapal
    Posted 1 year ago • Last reply 1 year ago
    1