Improve the visuals and definitions for when using custom assignment

Great! For assignment like in my example, the LawyerID would come from something like the process launch UI where a menu of appropriate recipients could be provided.

Thanks again for your ideas and feedback!

That provided solution seems to work exactly as we want, tested assignTo/assignBack, as well as the organization API at bpmrest-ui, and it can correctly provide a list of possible assignees.

One additional drawback i found, is that the referred user in "LawyerID" is not required to be a member of TEAM:Legal to be able to be assigned the task, so a user could complete a task they arent authorized to, but thats a downside that already exist with the assignTo JS API, which i assume this functionality uses in the background

The only downside now is the "where used" functionality, so our improvement idea could probably be changed to "Improve the visuals and definitions for when using custom assignment". For us the best solution, instead of using custom, would be if there existed an option stated as:

Direct assignment:
JS/bindable variable for userName
JS/Bindable team for return
JS/Bindable team for fallback if userName isnt a valid user or a member in the provided team

Hi. Actually you can preset both the user and the return to team. Here is an example I tried:

tw.local.activityProperties.LawyerID.value!="" ? "USER:"+tw.local.activityProperties.LawyerID.value+";TEAM:Legal" : "TEAM:Legal"

Note the semicolon between the USER and the TEAM. With that, the "Return to Team" option should be available.

Hi Dave. The method you mentioned has a few drawback.

First, it doesnt follow the pattern we currently use, where we use swim-lane assignments for the alloted teams to the tasks. If we in the script could write tw.local.reserved.length == 8 ? "USER:"+tw.local.reserved : "TEAM:LANE_ASSIGNMENT" or something, it would be a decent enough solution. By deciding the team with a String instead, we lose the "Where used" functionality, and force artifact names (the team) to be written as unsearchable strings. The same problem occur if you instead of dragging out service flows, instead call services by using tw.system.executeServiceByName("MyService"), with searchability and where used being broken.

Secondly, by using Custom assignment as such, we lose the functionality of returning the task back to the system, if the user for example is on vacation, and we want to automate a service that returns these types of tasks. The original team assignment is never set, since the task was autoassigned to a user, and as such cannot be return to something that is never set.

So for a solution, we would prefer a combination between lane assignment and if a variable contains a valid user_name, autoassign to that user AFTER the initial lane assignment is done, so the task can be properly returned

Hello! What about the approach to set the "Assignments" option of the task to "Custom" and add some script like "USER:"+tw.local.preferredUserID