Restrict Workflow to Single Asset?

Is it possible to restrict a workflow to be available on an asset’s page but not available in a view?

I ask because the OOTB Issue Creation workflow fails when more than one asset is chosen from a view. Because of this, I don’t want the workflow to be visible on a view, but I do want it to be an option on an individual asset’s page.

If it is not possible, I’m interested in any workarounds.

Roger Craig

Posted 3 years ago · Edited 1 year ago·Last reply 2 years ago

5 comments

iljatarans

·2 years ago · Edited

rcraig.agloan.com:

ble on an asset’s page but not available in a view?

I ask because the OOTB Issue Creation workflow fails when more than one asset is chosen from a view. Because of this, I don’t want the workflow to be visible on a view, but I do want it to be an option on an individual asset’s

Removing an option of creating multiple Issues from a view page will not fix out the issue. By default, Issue Creation is a global workflow. I assume you have custom one, or modified one. In this case you need to set behaviour, like you want 1 issue be linked to multiple assets or you want 1 issue per asset? Hopefully that helps

paritoshanand

·3 years ago · Edited

@rcraig.agloan.com You can restrict a workflow by using workflow definitions and applying proper rule and validations on that.

uditgupta1

·3 years ago · Edited

rcraig.agloan.com:

Is it possible to restrict a workflow to be available on an asset’s page but not available in a view?

I ask because the OOTB Issue Creation workflow fails when more than one asset is chosen from a view. Because of this, I don’t want the workflow to be visible on a view, but I do want it to be an option on an individual asset’s page.

If it is not possible, I’m interested in any workarounds.

@rcraig.agloan.com In Collibra, the ability to restrict a workflow to be available on an asset’s page but not available in a view depends on the specific configuration and customization options provided by Collibra. Collibra does not provide a built-in feature to restrict workflows based on the asset’s location within the platform.

However, there might be workarounds you can consider to achieve similar functionality. Here are a couple of potential approaches:

Customization: Collibra offers customization capabilities through its APIs and SDKs. You could develop a custom solution using these tools to control the visibility and availability of workflows based on asset locations. By creating a custom interface or modifying the existing Collibra interface, you could provide a separate workflow option only on an individual asset’s page.
Workflow Conditions: If Collibra’s workflow engine allows for conditions or triggers, you may be able to set up conditions that determine whether the workflow should be available based on the asset’s location. For example, you could configure a condition that checks if the workflow is being accessed from an asset’s page or a view and display or hide the workflow accordingly.

To explore these options further and determine the feasibility of implementing them in your specific Collibra environment, I would recommend reaching out to Collibra’s support team or consulting their documentation for more up-to-date information on customization capabilities and workflow management features.

Former User

·3 years ago · Edited

Why not put a validation script just after clicking on the workflow button and the script computes the count (number of asset ids) and restrict it to 1. If it is more than 1 then throw an error message.

Roger Craig

OP3 years ago · Edited

Thanks for the feedback, @umit.bhargava.rabobank.com. I was just looking for a way to prevent issue all together rather than address it if it occurs, but if this is not possible, I will certainly take your recommended approach.