I have a workflow with 3 main sign off states, each one with multiple people giving approval and in a particular order too.
Each time the document gets an edit, it's bumped back to the beginning of the current sign off state.
I'm finding that documents sometimes get "stuck" in a state, if they are edited and it requires re-approval. The people re-approve it, but than it gets stuck and never escapes. I have to admin transition it to the next state.
ALSO it is not obvious that the document has been edited and approvals are needed again.
EXAMPLE
Document reaches 'Project team sign off' and requires the Project Manager and lead engineer to sign it off, in that order.
It gets PM sign off but then the Lead Engineer points out it needs an update, so the owner edit's the document.
However, the state hasn't changed - it's still in 'Project team sign off' - the fact it requires the PM to sign off again is not obvious from the document - you have to check "pending approvals".
With my problem, it then gets those approvals but stays in 'Project team sign off'
How can I work out what's gone wrong? How could Comala Tech work out what's gone wrong??
-Kev
ANSWER: Updated to 5.9.0 and it fixed a whole bunch of issues for us. UI improvements helped, though still not obvious WHO it's waiting on approval by
Understanding the difference between an approval macro that has
user=&@user1@,@user2@
and
user=@user1@,@user2@
is vital too - the & mandates ALL approve it.
This is all in the docs, just easy to miss
Hi Kev Con, I am having the same issue but have not been able to resolve. Did adding or removing the & solve for you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.