nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Modeler Datasource default value

deepti

Hi,
We are using datasource on GroupTask to populate users dynamically from a xml,however the task is automically assigned to the user which is dispalyed as first default value in the datasouce dropdown list, just because of that other users cannot take the ownership of the task.
Thansk,
Deepti

Find more posts tagged with

Comments

cute_guy

Hi,
We are using datasource on GroupTask to populate users dynamically from a xml,however the task is automically assigned to the user which is dispalyed as first default value in the datasouce dropdown list, just because of that other users cannot take the ownership of the task.
Thansk,
Deepti

Try to keep your first value as empty value ("")

deepti

If empty value is added,no user in group can taske the ownership of task.

Thanks,
Deepti

Adam Stoller

Hi,
We are using datasource on GroupTask to populate users dynamically from a xml,however the task is automically assigned to the user which is dispalyed as first default value in the datasouce dropdown list, just because of that other users cannot take the ownership of the task.
Thansk,
Deepti

I'm a bit confused here - isn't the datasource used to populate a drop-down (or multi-select) list as part of the workflow instantiation? Wouldn't you be able to set it then and have it do "the right thing" as part of the instantiation process? Or are you inserting a CGITask in the midst of your workflow to do the selection post-instantiation?

deepti

Hi,
The selection is not a part of instantiation screen,datasource reads the usernames from some third party xml and users read from that xml should be added to the group task by the datasource.

I hope this answers your question.
Thanks,
Deepti

Adam Stoller

Hi,
The selection is not a part of instantiation screen,datasource reads the usernames from some third party xml and users read from that xml should be added to the group task by the datasource.

I hope this answers your question.
Thanks,
Deepti

I'm still missing something here - a grouptask does not execute a command, so therefore having a datasource (command - yes?) associated with a grouptask does not really make sense to me, unless you are saying that the datasource variable is associated with the sharedby-group or user for the grouptask, in which case the datasource is still to be executed as part of the instantiation process where, I believe, it is usually represented as a single- or multi-select list though I suppose it might be possible to have it fully automated - but then the onus is on you since we don't know what you've coded for this datasource.

I'd suggest adding diagnostic debugging to your datasource code so that you can better understand what it is (or is not) doing - and probably also enable debugging in your WFM so that you can see the instantiated job specification without actually launching the job.