Jump to content

Recommended Posts

Posted

If an internal user tries to complete an activity assigned to another user they are greeted with the message "The task is currently assigned to 'XXXX', no access allowed". This prevents other users fully taking over a request from the original assignee without 'breaking' the BPM (even if the request is then assigned to another user, the activity stays as being assigned to the original). Can anyone offer any advice on how to overcome this please?

Thanks,

Andrew

Posted

@AWeaire - you can choose to assign the activities (activities associated to a request) to the team that the request is assigned to as opposed to the request owner. As such, any member of the team that the request is assigned to can complete the task.

There is also the alternative of enabling this SM app setting: app.experimental.advancedRequestTaskCompleter . You can read about what this setting does here: https://wiki.hornbill.com/index.php/Service_Manager_Experimental_Features

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...