What we're looking to do is give certain users permission to see the
workflow details for a particular application instance via
/aem/dashboard/formdetails.html. The person who initially kicked off an
application instance should be able to see who has approved/rejected/etc
along with their comments, changes to the adaptive form within each
Hello Arun,While that concept seems valid, we only need a single
approval. The idea is that both users A and B see that a task is
pending, they can then claim/process it, and then it moves onto the next
step. I suppose you could assign a task to all users and then go back
and delete those tasks once you have a single approval, but that seems
to be a good deal of overhead and could also introduce concurrency
issues?Please correct me if I misunderstood the scenario that you
pointed me at.Thanks ag...
It appears that work items are internally restricted to the current
assignee. While this is understandable, the drawback is that the
original workflow initiator and 'administrators' don't have access to
see the current state, workflow history view, etc. Is there a way to
easily enable this extra level of oversight for in-flight
processes?Thanks in advance!
It appears that work items can only be assigned to a single
authorizable. We have a situation where multiple assignees are needed,
which could be handled via an ad-hoc group that is created dynamically.
Is there a more efficient way to say that User A or User C can claim
this particular task, without creating 1,000's of different one-off
groups to handle each scenario?Thanks in advance for your help!