Welcome to the Decisions Online Training – Decisions 4.0

1. Welcome to the Decisions Online Training – Decisions 4.0 Trainer: Eric Welmerink – Director of Training The Recordings, examples, and slides will be posted next week and an email sent out to all attendees. We welcome any and all feedback. Please email myself (eric@decisions.com) or Kevin our COO (Kevin@decisions.com).

2. Agenda for 4.0 Webinar Day 1: Portal Introduction, Flows Day 2: Forms and Datatypes Day 3: Rules and Process Tracking Day 4: Reports and Dashboards Day 5: Advanced Concepts, Best Practices, Administration

3. Welcome to Decisions Training We understand that Decisions is an intricatepiece of software with many components. During this time, you may encounter questions or want some time with a professional services team member. We fully understand that there will be many questions and encourage you to ask them during QA sessions as well as continue to ask them after the training event. As always, feel free to email support@decisions.com

4. Additional Resources Documents and Forum • http://documentation.decisions.com • http://support.workflow.com/forum/

5. Introduction Course Material • Instructor demonstration with building exercises. • Two Q&A Sessions during the training • At the end of the training, we will have covered the 5 designers and some advanced process building concepts.

6. What is the “Decisions Platform?” Web Based Application • Make process automation routine • What you see is based on what you need to do to perform your job • Contains graphical Designers • Don’t have to be a programmer to have success with the tool

7. Decisions Usage Examples Human Resources User • Add or update employee info • Complete performance review • Approve extended leave request Insurance Specialist • Submit insurance request • Update or suspend insurance policy Hospital Staff • Manage bed inventory Mortgage Company • Perform collections operations and drive call center users through a workflow process to collect on accounts.

8. A Few More Technical Details Presentation layer’s foundation built using HTML! • Client manages presentation, data and logic executed on server • Fast, interactive user experience Host in-house or in the Cloud Decisions has hosting opportunities

9. Built In Additional Features Microsoft System Center • SCCM components for deploying applications SalesForce • Allows for interactions and compilation of steps against Salesforce Enterprise WSDL Flow and Rule Sets • Internal extension of rules to be able to call them in batch with common inputs and outputs. Telephony • Make outbound SMS and Telephony calls • Receive requests and route appropriately

10. App Store – New for 4.0

11. Decisions Portal

12. Role-Based Functions End-User • Working tasks, submitting requests, initiating processes, viewing reports Process Developers (“Designers”) • Designer access • Creates flows, forms, pages, reports, etc. Portal Administrator • Manages users, grants permissions, schedules jobs, portal setup functions

13. Security Authentication by Login • Every user who will run a process needs account • Integration with Active Directory or SSO (*SAML) • Can be “Guest” account Permissions Inherited by Group Membership • All Users, Designers, Administrators • Ability to create own groups

14. Exercise 1 • Log in as admin@decisions.com password = admin • Create a new user: [your initials]@[mycompany].com add your user to the Administrators group • Log out and log back in as your new user

15. Security Portal Settings to enhance security • Admin establishes security questions • User can use questions to reset password • Setting to confirm their email address before access is granted • Minimum password requirements • Expiration of passwords on a set time period • Single Sign On and Active Directory

16. User Password Reset

17. Decisions Folders

18. Folders Most components in Decisions are treated as folders • A standard folder will have base actions, but no ability to create design objects • Can be secured by using permissions and inheritance • A great tool for storage, or organization

19. Designer Projects A special folder for storing design work Entity Types: • Forms • Flows • Reports • Pages • Rules • Truth Tables • Text Merge

20. Exercise 2 • Create Sub-folder under Root folder “Decisions Training”: [your initials] Training Folder • Create another designer sub-folder “Data Mapping Example”

21. Free Training App At the conclusion of the free training event, we will have completed an example app within the Decisions portal. This app will be a user initiated, form based application to request for IT support or new hardware. We will be building this together throughout the 5 days of training.

22. Flows

23. Flows The flow is where we setup and design the automated process Connected components that sequentially execute steps Steps can take in data and output data The “outcome” is the path out of the step See the output using “Browse Data” Debug view to incrementally test

24. Mapping Data In Decisions, there are a couple of different ways to “Get” data into our steps Constant – treat this as a design time constant, no matter what happens in the flow, we will always use this value Select Value – This value currently exists in the flow and is most likely something dynamic. We need to tell the step to use this value that already exists

25. Mapping Data Expose Input – This will take the needed value and make it a required input into the flow Ignore and Null – Ignore will leave the field completely empty, while null will actually pass in a “Null” value (important in service calls and database integrations) Run Convertor Flow – Call another flow that exists in Decisions to convert or “massage” the data

26. Mapping Data Decisions contains a built in “Mapping Editor” • Performs the same exact behaviors as setting it per value, but allows this in a larger visual design environment

27. Mapping Data

28. Exercise 3 Create a basic math example • Grab two steps from the Toolbox > Data > Numbers (e.g. Multiply and Add Numbers) • Set these values to “Constant” • Debug the flow to see the process execute

29. Exercise 4 • Add a “result” to be passed to each outcome using the “Create or Copy” step • Show final “result” in a notification • Practice Mapping Types

30. Advanced Flow Concepts

31. Advanced Toolbox • Catch Outcome • Catch Exception • ForEach Loops • Simulation mode and catch exception on each individual step.

32. Flows – New for 4.0 • New Debug View • Sample Data available for quick testing • Can filter step selector by type of data available to user • New Icons and Customization for the steps

33. Forms

34. Forms Interactive • Most common End • Standard closing message • Continues workflow process Background • Sets appearance of Interactive and End forms

35. Exercise 5 • Create form background for IT Request Process • Create a new Form for inputting Request information and apply our form background.

36. Exercise 5 • Create form for getting the information into the workflow from a form • We will need to gather the following information from the user • Type of instrument to insure (Piano, Guitar, Brass) • Sub Type of Instrument (Acoustic Guitar, Electric Guitar) • Deductible • Location Instrument is Stored • Is instrument stored in hard case • Is instrument played professionally • Purchased Cost of Instrument • Replacement Cost

37. Exercise 5 • Integrate Form into workflow so we can debug to Test the input of information into the form . • Create a Unit Test

38. New for 4.0 - Sub Dialog • Able to Change Data on Sub Dialog • Can pass in data from parent form to sub dialog form

39. New for 4.0 – Additional Features • Ability to Multi-Select Controls and Align (On Canvas) • Quick Add Popup Dialog (Shift Click to Add Label) • Change Control Type with Right Click Action • JS Controls • Debug View shows Visibility and Validation Rules (and Data Flows!) • Repeater Controls • Validations Via Flows • CSS Styling • Adding Controls From Data • Multi Select Dropdown

40. Form Assignment

41. Form Assignment Assigned forms are used to get an external user involved in a process Assignment Type (In Session, Assigned, Guest) Assignment Settings (Name, Action Name, Assign To)

42. Task Escalation Levels of Escalation • Warn • Late • Escalate • Expire

43. Notifications Common notification options • Send Email, Send Notification (pop-up) Notify of task assignment Example notification to use in a flow • Set up notification to requestor when request is approved or denied

44. Exercise 6 Create Assigned Form for someone to review the insurance submission • Set an expiration date 4 weeks in the future • Set a warning date 2 weeks in the future

45. Exercise 7 Send a notification if the task is completed • Create a popup notification to all users in the system if the task is rejected • Send an email to the end user letting them know that their application has been reviewed • (Tip: Use a sub flow to prevent multiple steps in one flow doing the same thing as noted above!)

46. Planning an Application

47. Planning an Application • How does a user start the process? • Which types of users or specific users are involved? • What tasks need to be accomplished? • How does data change at each handoff? • What notifications need to be sent from the process? • Do I need to report on anything? • Do we need a custom data structure?

48. What is a “Data Structure?” Determines organization and storage of data so it can be used efficiently • Custom data structures are NOT required, nor are they appropriate for every project you build • It is easy to go overboard with these Data Structures, so when planning an application it is best to start simple • As always, feel free to ask support for help in deciding.

49. Data Structure Examples An Insurance Policy Entity (=“Object”) • Perform actions on the object like “Cancel Policy” • Add a claim A store • Contains devices • Add, update devices A travel itinerary • Assign agent • Add, remove passengers

50. When to say “Yes” to Custom Data Structure Do you need to report on “process data?” (i.e. data captured by form) Do you want to store your process data to a database? How often is the data going to change and do I need to keep a history of it? Should I be managing this structure?