buffer for form item in a workflow
Hello, we are pulling in a lot of assets (1000+ items) for generating a dropdown list in one of the form items in our workflow, and are experiencing significant impacts to performance when starting the workflow. I’ve noticed that collibra seems to have some sort of buffer on their list of items outside of a workflow (ex. clicking the “Add” button on a business term to relate it to a data asset, this brings back a long list of items; however, as you scroll down it adds 20 or so more lines of assets to improve performance). Has anyone been able to replicate this in a workflow form item? Thanks!
jackfinegan
Posted 3 years ago · Edited 1 year ago·Last reply 3 years ago
11 comments
Arun Narayanan
·3 years ago · EditedHi,
while using proposed fixed, the asset full name is not displayed in the form. this is an issue when using column assets. Is there any config that can display asset full names along with breadcrumb and display name in the dropdown list in user form with fixed values.
Piotr Pękacz
·3 years ago · Edited@jack.finegan I’d advise to follow Tom Friesen suggestion. This way data aren’t fetched on workflow start what I suspect slows down the process. Unfortunately there’s still no buffer to load up data as you scroll the list, but you can use input to search for any assets.
The buffer you’re interested in are part of workflow designer feature.
Let me know if that helped.
Piotr Pękacz
·3 years ago · EditedMy understanding is you have a script task before the user task with form. In the script task you use api to pull assets and then the result is put as proposed values to term form field. Now you would like to have these results chunked to not list immediately in the form?
How do you notify the performance issue? It takes time to start workflow (time between you press a workflow button and notification the workflow started pops up) or is that the form content is loading up too much time?
jackfinegan
OP3 years ago · EditedThis all happens within the start task, we have a proposedValues:
${utility.toIdCsv(assetApi.findAssets(builders.get(‘FindAssetsRequest’).typeIds(utility.toIdList(‘05b06c22-3a3f-4924-b2ce-573b42d8fd0d’)).domainId(string2Uuid(‘a1c88446-c0ca-462d-8227-9f533c3aa163’)).limit(3000).build()).getResults())}. This is causing the form content to take too much time to load up on workflow start.
Piotr Pękacz
·3 years ago · EditedDo you mind attaching the workflow or any other with minimal reproduction steps so I could have a closer look?
Tom Friesen
·3 years ago · EditedHey Jack…
I’m not sure this will sufficiently improve performance, but why don’t you use the built-in filters in the asset drop-down form, if you’re just restricting on type and domain?
arthurburkhardt
·3 years ago · EditedThere is a bug on the platform: if you want to display sample values without the user typing anything, you have to activate “proposedFixed=true”. If you do, Collibra will truncate the list and only retrieve a limited number of assets (like 100). If you want to have both proposedFixed and a large number of assets, you need to preload the list of assets.
Regardless, those issues might be fixed in the upcoming workflow improvement, with the workflow designer for example. @jack.finegan
Piotr Pękacz
·3 years ago · EditedMy understanding is you have a script task before the user task with form. In the script task you use api to pull assets and then the result is put as proposed values to term form field. Now you would like to have these results chunked to not list immediately in the form?
How do you notify the performance issue? It takes time to start workflow (time between you press a workflow button and notification the workflow started pops up) or is that the form content is loading up too much time?
jackfinegan
OP3 years ago · EditedAttached a copy of the xml from the bpmn file…RequestAssetAccess2.txt (79.6 KB)
This is a modification to the request asset access workflow, so when you click the “Checkout Data Basket” button, there is a delay.
Piotr Pękacz
·3 years ago · EditedHello @jack.finegan ,
let me clarify - main problem here is that having workflow form and form field of type asset, the dropdown doesn’t load up more data as you scroll down the list? If it was there, then you wouldn’t pull that long list in a script?
jackfinegan
OP3 years ago · EditedHi @piotr.pękacz, no the list IS loading the assets, but it is loading them all at one time which is causing significant performance issues (the form takes up to 10 seconds to load). Is there a way to buffer the generation of the form similar to what comes out of the box from collibra on some of the “Add” button dropdown forms?