Advanced Workflow

Agenda 1. Understanding the Overall Architecture 2. Setting up Outlook for Workflow 3. Launching Workflow from Applications 4. Getting data into SyteLine 5. Simple scripting 6. Custom Roles 7. XML forms 8. Web Workflow

Agenda 1. Understanding the Overall Architecture –Launching from SyteLine 6 –“Red” Flow Button –Posting to SyteLine

Client Workflow Appserver SyteLine DB Exchange ServerIcomXpress Server Outlook SyteLine Workflow Launch

Client Workflow Appserver SyteLine DB Exchange Server Outlook “Red” Flow Button

SyteLine Frontstep Processing Queue Listener MSMQ Processing Queue Posting Queue Reply Queue Workflow App Server Exchange Server SyteLine Inbox Agent (Exchange Agent) Frontstep Posting Queue Listener IcomXpress Server Post Step Transaction Processor Frontstep Processing Queue Listener SyteLine Posting 1. A posting Workflow is initiated from SyteLine. A temporary table is populated with data from the GUI screen and passed to the Workflow App Server. 9. The Frontstep Processing Queue Listener Service is also responsible for listening to the Reply Queue. When the message from the Workflow App Server dropped in the Queue, the Processing Queue Listener uses the Exchange message ID to access the message and update the Workflow Task response to either ‘Success’ or ‘Failure’. The posting Step is then completed. 8. The Frontstep Posting Queue Listener Service then picks up the XML and calls the Proxy generated dll on the Workflow App Server, which posts the information back to SyteLine. The Workflow App Server responds with either a message and/or an error code and puts that in the Reply Queue 7. This information is passed to the Symix Transaction Processor Service. Here it is converted to XML and is dropped into the Posting Queue 6. The Frontstep Processing Queue Listener takes the message ID and logs into Exchange to retrieve the message data. 5. On the SyteLine inbox is an Exchange Agent (SyteLine Inbox Agent) - a script that runs when a new message is delivered to the SyteLine inbox. Next it takes the Exchange Message ID and all the key fields from the data and passes them to the Processing Queue 4. The Exchange Server places a task message in the SyteLine Inbox 3. A Posting step initiates the rest of the actions. The SyteLine inbox is recognized as the recipient of the message. 2. The Workflow App Server logs into Exchange, finds the folder with the correct template and initiates the flow through the IcomXpress Server.

Posting Components Transaction Processor Progress AppServers –Workflow, Database MAPI Manager (*Messaging Application Program Interface) Inbox Agent MSMQ (*MicroSoft Message Queuing) –Processing, Posting, Reply Queue Processing Queue Listener Posting Queue Listener

Agenda Setting up Outlook for Workflow –Workflow Task Inbox, Rules Wizard –Out of Office Assistant –Column Headings Workflow Status fields Application Data

Agenda Launching Workflow from Applications –SyteLine GUI Screens (*Graphical User Interface) –Progress (Non-GUI SyteLine screens) –MS Excel –MS Word –Active Link Transaction Manager

Agenda Getting data to SyteLine –Application Data requirements ‘~’ AppData SyteLine Inbox

Agenda Simple scripting and/or Generic Progress API –VB Scripting AssignAlias AssignPartIDFromItem Sub AssignPartIDFromItem Set objSLTag= ApplicationDataList.Item("item_item") Set objStdTag= ApplicationDataList.Add("PartID", 8, objSLTag.value, "Added by 'AssignAlias' script") End Sub

Agenda Custom Roles –Use of –Building –Assigning Progress VB Script

Agenda XML forms –Use of –Building

Web Workflow Why –Extend Workflow beyond four walls –Interface with 3 rd party systems Sending Tasks –Delivery Options: URL Responding to Tasks

Agenda Group discussion –adding value during an implementation –Possible Topics: Stream-lining a business process with workflow Controlling the flow and manipulation of data What process/procedure do we attack first

Thank You Questions ? ? ? Steven Feril ph fax