Jump to content

Recommended Posts

Posted

We use the sort of nodes below for authorisation but in the two cases of where an Authoriser is already on leave at the point of Activity creation or the Authoriser was present but goes away without authorising, we end-up having a manual detect/re-assign/chase workload.

Does anyone out there have a way around this; either in ensuring we only assign approval activities to present staff or to detect them going on leave and flag for exception or even re-assign?

image.thumb.png.332626505f6d4fc54e3cd85c4d2c401d.png

Posted

Hi @Berto2002

This looks like its for Change, we also have authorisers but have set a lifespan, so if there is no response the task expires.

image.png.a3b1330ed0a0b46a36c6189eff011ce4.png

You can then have a decision node to deal with this, eg.  Approve if expired, Rejected or Manual action.

Nasim

 

Posted

@nasimg that's one way around it I guess. Do you then have workflow that picks-up the expiry? What do you do then in workflow? How do you detect it was department or role A that expired so it needs another one of that team or level?

Posted

Yes decision node picks up expired task, we set it to approve (although you could decide to reject).

Sorry about the below BPM, complicated as we have multiple organisations with different approvers.

image.thumb.png.54147b41c6331e0a20d481f4d42d5290.png

Posted

OK so that's a assumed or tacit approval. I guess we would have a delegate possibly. Do you know if it's possible to set approval by role instead of individual?

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...