Hi @StejonatL,

We would need details on how exactly these filters have been set up as well as how assignment is occurring in your system, do you have PSO for instance? Also, the status is Open but does the PersonID return to the assignee field?

Kind regards,

Lee Pinchbeck

Hi Pinchbeck, 

Thanks for your response.

This is the filter code:
 

JL_FILTER_TEAMTASKS - (From FSM Client Scripts)
var fullFilter = stringFormat("task.task_status in (select task_status from task_status where status = 'OP' and task_status <> '{0}') and task.team_id in (select team_id from team_member where person_id = '{1}') and task.person_id is null", getAppParam("REJECTED_TASK_STATUS"), getUserInfo("PersonID"));
return fullFilter;

 

Yes there is a business Rule that Forces the Assignee Field to be blank upon change of status

 

Hi @StejonatL,

That covers how the assignee is removed but how is the assignee added in the first place. It could be that something is triggering a partial reversion of the assignment following the rejection that causes it to get through the filter.

Also, where is the filter applied? Where are you viewing this list? You indicated that the status is assigned but in FSM it says open which suggests this is not in FSM?

Kind regards,

Lee Pinchbeck

The assignee is first assigned through the FSM manager portal. The status is first set from Open to Assigned. The task moves from Team Task to All.

The mobile user then rejects the task. The Status changes to Open and the Assignee becomes blank from the BR.

The task does not move to Team task. Only upon reinitializing is the Task moved to Team Task.

Filter is applied using the Mobile Designer

 

Code in Script is as above.