Skip to main content

Looking for help based on user feedback regarding our access workflows.

Currently we utilize a workflow with 3 stages:

-Stage 1: Two tasks for initial account reservation and ad setup

-Stage 2: Additional application setup driven purely by dynamic tasks (potentially up to 23)

-Stage 3: Final setup for a dynamic task if the user is a physician/clinician

-Stage 4: Empty stage to complete process

 

What we’re wanting to figure out is a way for us to not need all of these tasks in a workflow that is so linear and can potentially drag out the provisioning process given the sheer volume that can occur. AN idea was had to offer users ability to bundle an application access request that doesn’t generate a dynamic task but a single standalone request to the applicaiton owner. This way the overall process isnt impaired and the affected/reporting user can get a clear notification for whatever specific application access has been provisioned.

Has anyone done something similar that isn’t a workflow but bundling standalone forms they could give me an example of that has been successful? Pros/Cons?

 

I’m happy to entertain a call if anyone is willing.

Thanks,

Mitch

Be the first to reply!

Reply