Presentation is loading. Please wait.

Presentation is loading. Please wait.

#CRMUGSummit | #INreno15 #CRMUGSummit WORKFLOWS: GATHERING FORM INFO AND VISUAL STATUS Glen Wolinsky, Miller & Martin PLLC.

Similar presentations


Presentation on theme: "#CRMUGSummit | #INreno15 #CRMUGSummit WORKFLOWS: GATHERING FORM INFO AND VISUAL STATUS Glen Wolinsky, Miller & Martin PLLC."— Presentation transcript:

1 #CRMUGSummit | #INreno15 #CRMUGSummit WORKFLOWS: GATHERING FORM INFO AND VISUAL STATUS Glen Wolinsky, Miller & Martin PLLC

2 #CRMUGSummit | #INreno15  Law firm founded in 1867 in Chattanooga, TN  More than 250 employees – 130+ Attorneys – 50+ Practice areas  Three Locations – Chattanooga, TN – Nashville, TN – Atlanta, GA 2 INTRODUCTIONS

3 #CRMUGSummit | #INreno15  With Miller & Martin since 1999  Lead Applications Developer  BIO: – 2 years of Microsoft Dynamics CRM experince in administration and development – 18+ years of development experience including VB.Net, ASP.Net, HTML, SQL, SSIS, SSRS, Javascript, and RPGII (dating myself) – Develop and maintain centralized practice management systems and integration systems linking to other products 3 INTRODUCTIONS – A BIT ABOUT ME

4 #CRMUGSummit | #INreno15  Use of CRM Workflow – Capability of gathering many items of information using Task Forms during a workflow process. – Providing for distribution of work among groups and individuals in parallel. – Collect item approval from many users concurrently.  Form Tracking – Use of fields to manipulate workflow process. – Use of fields to reflect complete status overview of the workflow process. OUR OBJECTIVES

5 #CRMUGSummit | #INreno15 Review by Multiple Employees  Approve/Reject  Ability to add notes or attachments to each response. Tasks Management  Multiple departments  Most work happening simultaneously (in parallel) across those departments.  Each “form task” consists of multiple items of information and/or feedback BUSINESS NEEDS DEFINED

6 #CRMUGSummit | #INreno15 WORKFLOW DESIGN

7 #CRMUGSummit | #INreno15 EMPLOYEE INTAKE DEMO

8 #CRMUGSummit | #INreno15 8

9 9

10 10

11 #CRMUGSummit | #INreno15 11

12 #CRMUGSummit | #INreno15 12 No “Submit” Button Since the form is not ready for completion. (Firm Role Is missing)

13 #CRMUGSummit | #INreno15 13

14 #CRMUGSummit | #INreno15 14 “Submit” Button Since the form IS ready for completion.

15 #CRMUGSummit | #INreno15 15 Review Items A review item for the new employee has been created for each user in the Employee Review Group.

16 #CRMUGSummit | #INreno15 16

17 #CRMUGSummit | #INreno15 17

18 #CRMUGSummit | #INreno15 18

19 #CRMUGSummit | #INreno15 19

20 #CRMUGSummit | #INreno15 20 Since there was a conflict (or possible conflict), a Conflict Resolution task has been created. The workflow is waiting for that task form to be completed.

21 #CRMUGSummit | #INreno15 21

22 #CRMUGSummit | #INreno15 22 We’re here

23 #CRMUGSummit | #INreno15 23 The task codes match the codes on the task boxes in our workflow drawing.

24 #CRMUGSummit | #INreno15 24 In this case, the workflow WAIT condition is not dependent on an entire task form completion, but on the setting of a single data item. Once the location is verified, the Logistics Track will continue.

25 #CRMUGSummit | #INreno15 25 Here, we only set this one data item and save the task form without completing it. This will allow the WAIT condition in the Logistics Track to continue. Once this happens, you should see the RC1 task created in our tasks list as seen below.

26 #CRMUGSummit | #INreno15 26 We finish these task forms just like our previous “Conflict Resolution” task form. The SUBMIT button only appears when all required task items have been completed.

27 #CRMUGSummit | #INreno15 27 Notice that the Logistics Track finished event though the RC1 task is not completed! After the RC1 task is created, there is no wait in the Logistics Track. The WAIT for the RC1 task is in the IT Track as shown in our flowchart. All the Task Status tracking is done in the Employee Intake record. This is what the workflow watches.

28 #CRMUGSummit | #INreno15 Here, IT1, IT2 and IT4 have all been completed, but IT3 has not been started since RC1 has not been completed.

29 #CRMUGSummit | #INreno15 29 Once RC1 is completed, then IT3 is created. This demonstrates how tracking each Task Form Status in the Employee Intake form lets you control your workflow across multiple child workflows.

30 #CRMUGSummit | #INreno15 30 Once IT3 is complete, the main workflow will continue and then complete the entire process.

31 #CRMUGSummit | #INreno15 QUESTIONS 31

32 #CRMUGSummit | #INreno15  Glen Wolinsky – Email: gwolinsky@millermartin.comgwolinsky@millermartin.com – LinkedIn: www.linkedin.com/in/glenwolinskywww.linkedin.com/in/glenwolinsky – Twitter: @glenwol1  Please fill out your survey.  Contribute! – CRM User Group: www.crmug.comwww.crmug.com 32 THANK YOU!

33 FINAL SLIDE


Download ppt "#CRMUGSummit | #INreno15 #CRMUGSummit WORKFLOWS: GATHERING FORM INFO AND VISUAL STATUS Glen Wolinsky, Miller & Martin PLLC."

Similar presentations


Ads by Google