Workflow Usage Best Practices

  • Published on
    17-May-2015

  • View
    29.717

  • Download
    2

Transcript

<ul><li> 1. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd.Workflow best practicesAuthor: Roman AgaevDate: Monday, May 14, 2007 -1- </li></ul><p> 2. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. Contents 1 Abstract.......................................................................................................................4 2 Workflow process.......................................................................................................62.1 Workflow process diagram window................................................................62.2 Workflow process properties...........................................................................92.3 Workflow process instance properties...........................................................102.4 Triggers for invocation...................................................................................10 2.4.1 Run Time Events.................................................................................12 2.4.2 Database triggers.................................................................................12 2.4.3 Scripting..............................................................................................132.5 Using workflow..............................................................................................14 2.5.1 Workflow work modes........................................................................14 2.5.2 Useful Business Services....................................................................16 2.5.3 Design example...................................................................................17 2.5.4 Workflow simulation...........................................................................24 2.5.5 Workflow deployment.........................................................................282.6 Asynchronous invocation...............................................................................31 2.6.1 Logging paradigm...............................................................................31 3 Workflow policy.......................................................................................................32 4 Workflow action........................................................................................................33 5 Workflow program....................................................................................................33 6 Workflow Process Manager Component..................................................................34 7 Conclusion.................................................................................................................357.1 Discussion......................................................................................................35 8 Appendixes................................................................................................................35 9 Indexes......................................................................................................................36 -2- 3. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd.Tables Table 1-1: Functional implementation decision points..................................................5 Table 2-2: Useful Business Services............................................................................16 Table 2-3: Design of new Workflow Process (example).............................................17 Table 2-4: Workflow steps names (example)..............................................................19 Table 2-5: Workflow's Siebel operation step's properties values (example)...............20 Table 2-6: Workflow's Siebel operation step's values fro new entry (example)..........22 Table 2-7: Workflow's interactive step properties values (example)...........................23 Table 2-8: Workflow connector's condition definition................................................23 Table 2-9: Simulation of new Workflow Process (example).......................................24 Table 2-10: Workflow deployment (example).............................................................28Figures Figure 1-1: The workflow diagram example (Verify Order/Quote)..............................4 Figure 1-2: Workflow development and deployment lifecycle.....................................6 Figure 2-3: The Workflow process diagrma window with predefined steps capability 7 Figure 2-4: Workflow decision point's condition criteria definition..............................8 Figure 2-5: The example of Workflow's Stop step........................................................9 Figure 2-6: Standard Workflow Process properties example......................................10 Figure 2-7: Expression Workflow Process property example.....................................10 Figure 2-8: Workflow by script execution (server side)..............................................11 Figure 2-9: Workflow policy concept architecture......................................................13 Figure 2-10: Workflow building blocks.......................................................................14 Figure 2-11: New Workflow creation (example).........................................................18 Figure 2-12: Workflow steps creation (example)........................................................19 Figure 2-13: Workflow steps and its descriptive names (example).............................20 Figure 2-14: Workflow's Siebel operation step definiton (example)...........................21 Figure 2-15: Workflow's Siebel operation definition cont. (example)........................22 Figure 2-16: Workflow's Siebel operation definition cont. (example)........................23 Figure 2-17: Workflow's connector definition (example)............................................24 Figure 2-18: Prior simulation activity debugging options definition (example)..........25 Figure 2-19: Workflow's prior simulation properties population (example)...............26 Figure 2-20: Workflow "Wait for simulation in progress" dialog box (example).......26 Figure 2-21: Workflow's simulation view (example)..................................................27 Figure 2-22: Workflow's simulation completion (example)........................................28 Figure 2-23: Workflow's deployment (example).........................................................29 Figure 2-24: Workflow's deployment view (example)................................................30 Figure 2-25: Deployed workflow activation (example)...............................................30 Figure 2-26: Workflow's Run Time Events reload (example).....................................31 Figure 3-27: Workflow Policy architecture.................................................................33 Figure 5-28: Workflow Policy Program supported types............................................33 Figure 5-29: Workflow Policy Program definition......................................................34 -3- 4. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. 1 Abstract The main aim of the document is best workflow practices description and trying to route future implementation via the best way of such a capability usage. Generally workflow is declarative way of system programming when it includes all possibilities for common Siebel features invocation like Business service methods, Siebel internal operations, Inline expressions. The workflow framework provides a powerful way of process design and implementation handling when in fact manages common memory and instruction area for the process evaluation, the memory area allows usage of common parameters across the workflow process instance. The parameters handled as properties within the inbound propertyset of workflow wrapping business service invocator like Workflow Process Manager or EAI Business Integration Manager. The powerful side of workflow in some circumstances may become a disadvantage because of conceptual problem that assembles in terms of process finite property and as consequence potential discontiguity to a cross system processes. The workflow must be considered as capability of sophisticated processes orchestration rather than used as simple cases like field update handler.Figure 1-1: The workflow diagram example (Verify Order/Quote) The following table provides common decision point for evaluation of further implementation step implementation. In fact Siebel allows several approaches when dominant ones are common scripting (browser/server side) within several Siebel's architecture elements: Application, Applet, Business component, Business service and Workflow processing (interactive, service, long-running, 7.0 compatible). -4- 5. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. Table 1-1: Functional implementation decision points Type DescriptionWhen Useful Limitations Workflow Kind of step in a Need a simple Conditional Decision StepWorkflow that articulation ofexpressions lackarbitrates betweenwhether one or support for someone or more more alternative key operatorsalternative branchesactions in flowincluding:in a flow should be takeno AND Each branch out of o ORdecision step haso Order ofone or moreprecedence controlconditions if all(such asevaluate to TRUE parentheses)for the branch theflow will continuedown the branch Scripted Script within a Workflow Undermine Business business servicedecision stepreadability and Services Action step thatsemantics notsimplicity ofevaluates a sufficiently workflow by hidingpotentially complex expressive tologic within aset of inputs and encapsulate decision servicereturns a simplifiedcriteriaoutput that can beevaluated by aworkflow decisionstep OtherOther rule Specializedframeworks that Rule may be leveraged Frameworks directly or indirectlyby a workflowo PersonalizationRuleso Assignment Rules-5- 6. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. The following figure shows common Workflow Process lifecycle:Figure 1-2: Workflow development and deployment lifecycle 2 Workflow process The workflow process consists of several parts: Workflow process diagram window, Workflow process properties, and Workflow process instance properties.2.1 Workflow process diagram window The Workflow process diagram window in fact enables to create a workflow using predefined and bounded step definitions. The following figure shows the Workflow process diagram window with every predefined capability. -6- 7. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. Figure 2-3: The Workflow process diagrma window with predefined steps capability Start the step indicated the workflow start/entry point. At this point all of the process instance properties are populated. Business Service the step allows execution of every possible method within every predefined Business Service. The attention needs to be paid in case of usage cacheable services thanks to disability of service reload during the workflow session. The issue leads to possible non adequate call to desired Business Service method within the workflow instance1. Decision Point the step allows standard decision capability when evaluates expressions of outbound Connectors connected to it. The following figure shows the simple decision point definition. 1The situation may take a place in case of trying to execute several methods of the same cacheable Business Service during the same Workflow Process session-7- 8. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. Figure 2-4: Workflow decision point's condition criteria definition Sub-process the step encapsulates the sub process invocation. Every subprocess like its originator allows predefined and bounded list of potentialworkflow steps. Potentially every workflow may be an origin of hierarchicalinvocation. The possible problem may be encountered when this ability will beabused and over stack error will be raised up thanks to disability of system tohandle a numerous number of started workflow instances within the same leafof processing. The sub process invocation supports inbound and outboundproperties thanks it's wrapping mechanism that provides an ability of usagenon predefined data structure of potential inbound and outbound information. Siebel Operation the step allows an update, insert, and query operation overthe Business Component from the context defined by Business Object chosenwithin the Workflow Process properties. The update operation may handlesingle update as well as multiple one. User Interact the step provides an ability of user server side redirection tothe predefined view based on Business Component from within contextdefined by Business Object property of workflow definition. Such BusinessComponent may be searched by any internal Siebel operation step of byprovision Object Id property at the beginning of process instaciation2. 2 The option is possible only within the interactive mode workflow-8- 9. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. Wait the step allows suspending process execution by predefined period oftime. Stop the step allows termination of process and in some circumstances mayraise an error that led to this behavior.Figure 2-5: The example of Workflow's Stop step End the step indicates the last step within the workflow process instance.The step may not be executed in some circumstances when the WorkflowProcess instance was terminated or got an error and has proceeded viaexception route to a Stop step within the workflow definition. Connector the branch enables connectivity between the steps within theprocess. The connector can be raised up according some condition likepredefined custom or existed method over the business component firing. Thisoperation supported by Run Time Events mechanism3. Exception the branch enables handling of errors that can occur withinexecuted steps. The attention needs to be paid for cases when within thecustom methods of Business Service try, catch paradigm has been used. Theexception can help with handling different edge cases within the processexecution.2.2 Workflow process properties Workflow process properties are set of predefined values that cannot be changed during Workflow Process lifetime. The key properties are: Auto Persist allows saving of workflow state credentials regarding thevalues of Persistence Frequency and Persistence Level properties. Mostlyusable during development stage and allowed over any workflow mode exceptthe Service mode. Workflow Mode the number of supported modes bounded by following list:Service, Interactive, Long Running, and 7.0 Compatible.4 3 The mechanism allows usage of application triggers using simple concept of event participation. 4 In workflows with long running mode the "Auto Persist" property became to be very important thanks to fact, that this functionality allows resuming from its suspension. For further information please refer-9- 10. Ro...</p>

Recommended

View more >