Overview of CoreView Workflow

Modified on Mon, 28 Mar 2022 at 03:56 AM

I. Overview 

CoreView's Workflow provides organizations with process automation that allows you to work more efficiently. Workflow is an add-on solution that requires that a customer has purchased our CoreAdmin subscription.  Both CoreAdmin and Workflow are part of CoreView’s full SaaS Management Platform. 

 

Our Workflow feature allows IT administrators to turn repetitive management tasks into automated workflows. There are four elements that make up CoreView’s Workflow:

  • Multi-Step Automation - allows the user to take several actions and apply them to an object-based event such as a user being provisioned or de-provisioned.  Approvals allow you to gate check any Multi-Step Automation that occurs. 
  • Approvals - allow you to gate check any Multi-Step Automation that occurs. 
  • Bindings - refers to our ability to provide data transformation against the object a user is creating.  This allows for any formatting or password requirements a user wants to use across their organization.  
  • Filters - determines which user objects workflows can be executed against.  For example, this workflow only applies to USA workers.  

CoreView’s workflow comes with three out of the box templates:

  • Onboarding
  • Provisioning
  • Deprovisioning

II.  The Workflow User Interface

The user interface for Workflow is designed to guide an administrator through the required steps for any workflow.



The input tab allows you to type in your information for the object being created. It is possible to execute the workflow uploading the information from CSV. The workflow tab allows you to see each step of the multi-step automation in a workflow. The user can also add actions to these steps if they need something else besides the seven steps below by using the “add action” button.  

For example, here is the multi-step process for the Onboarding workflow:

  • Owner / Operator Approval - Allows you to start the following steps as long as certain criteria are true.  You can choose the type of users this workflow runs against.  A user can also define which operator or operators gets this notification to perform the workflow.  
  • Create OnCloud User - Creates the new user in the cloud-based on the inputs the user entered in the input tab.  Users can configure any settings or formatting required in the Configure Settings tab.
  • Manage Password - Sets password against the User Principal Name and then force the new user to change password at first login.  
  • Assign License - Allows you to choose the deployment that aligns with the user’s role. For example, the new user should get the full E3 license capabilities minus Yammer.  
  • Manage MFA - Allows you to enable or disable multi-factor authentication.  
  • Mailbox Grant Full Access to Manager - Allows the new user’s manager access to the new user’s mailbox.
  • Send Welcome email - Sends an email saying the workflow process is complete.  

Once these steps have taken place, the user will execute the workflows which entail configuring the input properties for each workflow.

 

 

After a workflow is executed, the user will be able to see the progress by looking at the status area. The status area is where he/she can drill down further into each step of the workflow to see which actions took place and make sure everything is in order.


In recent discussions with our current customers, many have stated that the new workflow automation capabilities within CoreView could reduce the weekly tasks for user provisioning and de-provisioning from 10 to 20 hours down to 10 minutes.  This would save an organization approximately 1,000 hours a year in manual IT admin activities, while also improving quality of service and reducing human errors. 

 

 

 

 

 

 

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us how can we improve this article!

Select atleast one of the reasons

Feedback sent

We apprciate your effort and will try to fix the article