Problem: The group Drop-Down form property type is stored as a comma-separated list of group names (booooo!) I would like to use the proposedValues field to restrict the group names available for selection. Some of our group names include commas … which cause the form to complain that certain incorrectly-split group names do not exist I haven’t found a way to successfully “escape” this in the form. Help!

Workflow weirdness: Populating proposedValues for Group Drop-Down | Product Q&A

Workflow weirdness: Populating proposedValues for Group Drop-Down

Problem:

The group Drop-Down form property type is stored as a comma-separated list of group names (booooo!)
I would like to use the proposedValues field to restrict the group names available for selection.
Some of our group names include commas
… which cause the form to complain that certain incorrectly-split group names do not exist

I haven’t found a way to successfully “escape” this in the form.

Help!

Tom Friesen

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

3 comments

Tom Friesen

OP3 years ago · Edited

Collibra Support relayed the following information:

The UUID use in the dropdown is actually a document defect (it’s not supported) so that is going to be updated. As to the name with commas issue, this will also be documented as a known issue but currently Engineering… has no plans to change the code to resolve this.

Based on this, I think the current implementation of Groups is unusable for most institutions if they are needed within workflows.

Disappointed.

Tom Friesen

OP4 years ago · Edited

Thanks for the suggestion, @alvin.useree.

Let’s hope they switch to using UUIDs; specification by anything else is just asking for trouble.

I liked the dynamicEnum suggestion. But the problem is that the dynamicEnum for a drop-down is that it doesn’t appear to support multiValue; the user can only select one value, not multiple.

In the meantime, I’ve raised a ticket on this bug, so hopefully it’ll get some attention in the near future.

alvinuseree

·4 years ago · Edited

Damn, I would have guessed that you could escape the comma using ,

But the same issue persists.

I’d argue it’s a bug to be honest … it does beg the question, why does that form prop use the group name and not the group UUID??

Unfortunately (unless someone can think of a better way) I think your best bet is to either hardcode the groups as an enum or use dynamic enum (booooo indeed)