Improving Effectiveness of Workflow Notifications. Yogesh Fegade (281) Siddhi-Om Technologies LLC

Transcription

1 Improving Effectiveness of Workflow Notifications Yogesh Fegade (281) Siddhi-Om Technologies LLC

2 About Siddhi-Om Technologies Founded in 2005 PLM Solution Architects & Consultants Located in Houston, Texas Working with Teamcenter/iMAN, NX/UG since

3 Siddhi-Om Technologies Services Offerings Domain of Consultancy Teamcenter products (Engineering, Unified, etc) CAD (NX) Systems design & integration Process automation design & development Database support Windows programming Services programming Network programming Problem solving & troubleshooting General C/C++/Java/.NET/XML/Scripting/SQL 3

4 Summary Workflow process can be quite complex How do you keep up With effective communication This presentation intends to show you just that!! 4

5 Workflow Notifications Who Uses Them 5

6 Notification Handler CR-Notify Does it satisfy the basic requirements of workflow notification Yes, but that s as far as it goes Only 4 report formats are available Review, Rejection, Progress, and Level Fixed notification text for each report format Contains basic information targets, decisions, comments, etc Rarely what the business requires to make it an effective communication tool 6

7 CR-Notify What About What about notification when: Target is added or removed Job is promoted or demoted Job is suspended or resumed Task is reassigned or delegated What about: Defining your own format for body Changing format without code changes Adding critical information related to the job, task, or target to the notification 7

8 Notification Handler late-notification Does it satisfy the basic requirements of overdue task notification Yes, but that s as far as it goes Fixed notification text Contains basic information about the job Rarely what the business requires to make it an effective communication tool 8

9 late-notification What About What about: Escalation of overdue tasks to appropriate superiors when reviewers do not take timely action on an initial reminder What about: Defining your own format for late notification body Changing the format without code changes Adding critical information related to the job, task, or target to the notification 9

10 Enhanced Notification Engine Custom notification engine was developed Comprised of replacement for: CR-Notify handler late-notification handler Task Monitor process 10

11 Notification Engine Short Comings What about notification when: Target is added or removed Job is promoted or demoted Job is suspended or resumed Task is reassigned or delegated 11

12 Notification Engine Solution Feature Ability to send an on specified action When a target is added or removed When a job is promoted or demoted When a job is suspended or resumed When a task is reassigned or delegated Or on any other action defined by the EPM module including user actions No restriction on placement Place it wherever it suits your needs of notification 12

13 Notification Engine Short Comings What about: Defining your own format for an body Ability to change an format without any code change 13

14 Notification Engine Solution Feature Ability to configure body of the notification Create an body as a text dataset template Create unique templates for each type of notification Template for job suspension notification Template for job resumption notification Template for task promotion notification Template for task demotion notification Template for task approval notification Template for task rejection notification Etc. Reconfigure body without any code change 14

15 Notification Engine Short Comings What about: Adding critical information related to the job, task, or target to the notification 15

16 Notification Engine Solution Feature Ability to embed property values in the body Specify property value keys in the template Create seamless body text Property value keys expand to actual property values Embed properties of Task, job, or target objects Any other object related to above Properties could be Attributes, references, runtime properties, compound properties, or relational properties Scalar properties or array properties Integer, float, double, character, string, date, logical or tag 16

17 Notification Engine Short Comings What about: Escalation of overdue tasks to appropriate superiors when reviewers do not take timely action on an initial reminder 17

18 Notification Engine Solution Feature Multiple levels of escalations for late notifications Configure number of escalation levels For each escalation level, specify Recipients Time when escalation level triggers Late notification body template For example: 1 st level send reminder to undecided reviewers 2 nd level send to the reviewer and to the supervisor 3 rd level send to the supervisor and to the manager 4 th level send to the manager and to the VP so on and so forth 18

19 Notification Engine Other Features Multiple options to specify recipients, For example: Responsible party Reviewers of current task or any other task Undecided reviewers Users in a group, users with a role Teamcenter user address Resource pool Distribution list, alias list Combination of above specified in a property of a target Or any combination of above 19

20 Introducing Handler SOT-Notify Argument onaction subject -comment format recipient Value Action upon which notification is to be sent. Useful only when placed under Perform action. Optional. Default subject is job name + task name. This argument value is appended to default subject when provided. Optional with no default. This argument value is added to the top of the body when provided. Name of the notification body template. Recipient of the notification. Multiple arguments allowed to specify multiple recipients. 20

21 Introducing Handler SOT-Late-Notification Argument nlevels basesubject baseformat level<n>recipient level<n>time Value Number of escalation levels configured by the handler. Optional. Default subject is job name + task name. This argument value is appended to default subject when provided. Name of the late notification body template. Recipient of the n th level notification. Multiple arguments allowed to specify multiple recipients. For example: level1recipient, level2recipient, etc. Duration, in minutes, after due date when n th level notification is triggered. For example: level1time, level2time, etc. 21

22 Sample Notification Template 22

23 Sample Notification Property Keys 23

24 Sample Notification Property Keys 24

25 Sample Notification Property Keys 25

26 Sample Notification Property Keys 26

27 Sample Notification Property Keys 27

28 Sample Notification Property Keys 28

29 Sample Notification Property Keys 29

30 Sample Notification Property Keys 30

31 Sample Notification Property Keys 31

32 Sample Notification Property Keys 32

33 Sample Notification Property Keys 33

34 Sample Notification Property Keys 34

35 Sample Notification What Was 35

36 Sample Notification Becomes 36

37 Demo Meet the Process 37

38 Demo Meet the Team 38

39 Demo 39

40 Q & A 40

41 Thank You! Siem ens PLM Connection 2011 Las Vegas, N V May 2-5