Contingent Values on Task fields

[apgis16]

I understand that contingent values need to be generated in ArcGIS Pro before publishing as a hosted feature layer. However, I want to add some contingent values based on what a user selects for esritask_assignee. Is this possible? If I have field_assignee configured for contigent values, can have the user pick esritask_assignee and then have field_assignee calculate based on that choice, then it triggers the contingent value?

In my scenario, I only have 2 contigencies, one would be ideally using esritask_assignee and task_category (not an esritask default field). The other uses esritask_assignee and task_editor (also a field I made, not an esritask default field)

[ChrisDunn1 · Accepted solution]

Hi @apgis16 ,

While I have not tested this exact scenario, I see no reason why it wouldn't work. Tasks are just features and the task fields are utilized by Field Maps to determine how the task is displayed in the mobile app, but otherwise there isn't anything special about the task fields.

The challenge, as I see it, is that you could end up with a fairly complex configuration - the esritask_assignee field might be used by the task filter determining what's shown on the map, and it's value is also set by the default "Pick Up" button, and then changing the assignee results in the contingent values firing, and if those values then drive another part of the task configuration you could end up with logical loops or unexpected behavior if you haven't mapped everything out very carefully.

As long as you have a full understanding of where every field value comes into play for Tasks and for Contingent Values, I do think this will work for you and unlock some powerful functionality.

Chris

[apgis16]

Hi Chris,

Thank you for your response! And you are right, it is possible but slightly challenging! As you predicted, I was running into some issues with logical loops but I think I finally figured it out. Thanks again!

[ChrisDunn1]

I'm glad it's working for you! There is a detail I missed, it looks like we are blocking the use of contingent value fields in Edit Field actions in the tasks configuration. So in your example, you won't be able to have an edit action target the esritask_assignee field. Practically, this would mean something like the "Pick Up" action that's part of the default tasks configuration would not work. However, you can still edit those fields in the form or in other clients outside of Field Maps, so hopefully that's more in line with your task dispatching and assignment strategy.