]project-open[ Workflow Developer Tutorial Part 1
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

]project-open[ Workflow Developer Tutorial Part 1

  • 3,690 views
Uploaded on

The tutorial introduces the basic ]po[ Workflow editor and engine based on a real-world example consisting of a "EDI Development Process" that controls how EDI system integration links are......

The tutorial introduces the basic ]po[ Workflow editor and engine based on a real-world example consisting of a "EDI Development Process" that controls how EDI system integration links are developed and deployed in a Fortune 1000 company.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
3,690
On Slideshare
3,689
From Embeds
1
Number of Embeds
1

Actions

Shares
Downloads
85
Comments
0
Likes
0

Embeds 1

http://www.project-open.org 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ]project-open[ Workflow Overview The basic ]po[ Workflow graphical user interface Start Place Transition End Transition [Not OK] [OK]
  • 2. Tutorial Overview
    • PO-Workflow-Tutorial-1-Overview.ppt This document provides a short overview of the ]project-open[ workflow.
    • PO-Workflow-Tutorial-2-EDI-Example.ppt: The next section guides you step-by-step through a real-world EDI Message workflow scenario.
    • PO-Workflow-Tutorial-3-Cusomizations.ppt The third section deals with the customization of the workflow to implement custom business logic, custom GUI panels and custom assignments.
  • 3. EDI Message Development Example
    • This tutorial uses an EDI development workflow as an example of a complex business process implemented in ]po[
    Working Message QC Approval Solution Support Technical Review QA Business Analyst UA Approval User Acceptance Release to Production MTP Success Project Finished 30 Days Maintenance and Solution Support Approved Project Business Analyst Message “Map” Message Developer Specs OK Report Specs not OK Message Developer Develop Message Check Specs Business Analysis QC Check Internal QC Team QC not OK Message Developer QA not OK UA not OK slow
  • 4. Petri-Net to Model Business Processes
    • To implement a business process, we need to convert it into a Petri-Net.
    • Petri-Nets consist of “places” (bubbles) and “tasks” (rectangles), connected by “arcs”. Arcs can have boolean conditions attached, allowing for loops etc.
    • Petri-Nets workflow behave similar to a status engine, but allow for parallel execution etc.
    Start Business Analysis End Check Specs [Not OK] [OK] Develop Message QC Check [OK] [Not OK] QA Release to Production [OK] 30 days Maintenance [OK] [Not OK] User Acceptance [OK] [OK] [Not OK] [Not OK] [Not OK] User Survey [OK] Resource Assignment Confirmed Project Message Tasks Message Tasks Message Tasks For each task start a WF :
  • 5. Simple Workflow Wizard
    • ]project-open[ includes a “simple workflow wizard” that allows to quickly create linear workflows.
    • The resulting workflows can be further customized to meet complex business requirements.
  • 6. Workflows and Business Objects
    • Workflows are associated with business objects (projects, companies, tasks, tickets, …).
    • You can track the status of the “Project Workflow Graph”. The blue dot represents the current WF status.
  • 7. The Workflow “Inbox”
    • The workflow “Inbox” contains a list of all assigned and otherwise associated workflow tasks in the user’s home page.
    • The inbox also contains the user’s own objects, so a user can track what is happening to his approval requests etc.
    • Inbox fields:
      • Action: The name of the Transition
      • Type: Name of the workflow
      • Status: Status of the underlying object
      • Assignee: Who else is assigned to the current transition?
      • Owner: Owner of the underlying business object
      • Object Name: Name of the underlying business object
      • Relationship: What is the relationship between the current user and the workflow? “Assignment Group” means that the current user is assigned (task), “My Object” means that the underlying biz object has been created by the current user (tracking). Only WF admins can see tasks with relationship “none”.
  • 8. The Workflow “Action Panel”
    • Workflow tasks are shown using a generic workflow panel by default.
    • Pressing “Start task” indicates that user will perform the task. As a result, the task will disappear from the Inbox of other assigned users.
  • 9. The Workflow “Task Done”
    • Once started, the WF panel shows a “Task done” button.
    • Pressing this button the user finishes the task, effectively driving the WF forward to the next transition.
  • 10. Outlook
    • This is the end of document: PO-Workflow-Tutorial-1-Overview.ppt
    • The next section will guide you step-by-step through a real-world workflow scenario: PO-Workflow-Tutorial-2-EDI-Example.ppt
    • The third section will deal with the customization of the workflow to implement custom business logic, custom GUI panels and custom assignments.