• Document: RSA Archer Advanced Workflow Overview & Troubleshooting
  • Size: 2 MB
  • Uploaded: 2018-12-05 19:06:38
  • Status: Successfully converted


Some snippets from your converted document:

RSA Archer Advanced Workflow Overview & Troubleshooting 1. Introduction 1.1 Advanced Workflow Notes: Welcome to this Advanced Workflow overview and troubleshooting training. 1.2 Outline Notes: Throughout this training, we will provide an Advanced Workflow overview and how to conduct basic troubleshooting. 1.3 Course Objectives Notes: Upon completion of this course, you should understand the basics of Advanced Workflow and where to start when troubleshooting common errors. 2. Advanced Workflow Overview 2.1 Advanced Workflow Overview Notes: Let’s first explore some basics of Advanced Workflow. 2.2 Advanced Workflow Overview Notes: The Advanced Workflow feature in Archer was newly introduced in version 6.0 and leverages an external engine called Workpoint. Advanced Workflow offers some advantages over the feature- driven workflow: • There is a drag-and-drop interface that allows admins to visually follow the path a record can take, rather than spending a lot of time deconstructing rules and actions. • The final diagram as defined in Archer can be printed for distribution to users. • Task Management is integrated with Advanced Workflow, enabling the automatic creation of task records. Those task records are also automatically closed as the record continues through the workflow process. 2.3 Two Approaches to Automation Notes: At this point, we have two different general approaches to workflow; meaning two different approaches to automating parts of a business process. Pre-6.x processes were automated via feature- driven workflows in which admins were free to add or remove data-driven events and other elements at will. Once built, a feature-driven workflow process can only be viewed as a collection of events, calculations, and so on - there is no clear visual representation of a record’s life through that application or questionnaire. These feature-driven processes are still available; however the Advanced Workflow feature was introduced with its own workflow designer to help admins confidently confirm the paths a record can take through a workflow. Some of the same elements, and a lot of the same concepts, as the feature- driven workflow are used when building out a process with Advanced Workflow. Some of the biggest differences between feature-driven and Advanced Workflow are listed on screen. Feature-driven (Slide Layer) Adv Workflow (Slide Layer) 2.4 Legacy Workflow-Related Features Notes: We want to drive home the point that several of the feature-driven workflow elements are integral to a clean Advanced Workflow build; that this doesn’t mean DDEs are obsolete, or you can never create another subscription notification. These features can be leveraged in conjunction with each other in order to automate a workflow, reduce clicks, and improve the end user experience. 2.5 Using Workpoint Notes: We’ll look at the workflow designer over the next several slides. If you are not yet familiar with Workpoint, please take a moment to review the intro videos linked under the Resources tab. It is also highly recommended that you take our 1-day Advanced Workflow and Navigation course. 2.6 General Process Properties Notes: Let’s be honest, there are lots of settings to remember, so we’ll recap some of that workflow designer functionality over the next few slides. Hover over the Enrollment options on screen to refresh your memory on these general process properties. Note that if no Content Enrollment options are selected, naturally, the record has no way of enrolling into Workflow. Re-Enrollment (Slide Layer) New Records (Slide Layer) Updated Records (Slide Layer) User Initiated (Slide Layer) 2.7 Advanced Workflow Nodes Notes: We have 5 nodes available on the left side of the designer: evaluate content, send notification, update content, user action, and wait for content update. Click each button at the bottom of the screen for more information on each node. Evaluate Content (Slide Layer) Evaluate Content Node The Evaluate Content node is used when the system should evaluate the record’s content against rules you define. The rules make use of if/then kinds of logic scenarios, allowing the process to branch out to a number of possible paths, based on what the user defines within the record. Evaluate Content Nodes require a default transition, which allows the Workflow to progress if all rules governing transitions evaluate to False. Except for error and default transitions, each outgoing transition must be configured with one rule so the record has a clearly defined path based on defined criteria. Send Notification (Slide Layer) Send Notification Node The Send Notification Node is used when the system should send an email to a user at a certain point within the process. Desired emails must first be built out via On Demand Notification Templates from the Admin toolkit. You will receive an error if no notification is selected under Settings. Update Content (Slide Layer) Update Conte

Recently converted files (publicly available):