You can execute a process flow either manually or using a particular event.
Executing the Process Flow Manually
To execute the process flow manually, select the process flow from the Manage Process Flow screen and then click Execute. For more information, click here.
Executing the Process Flow using Event
To execute the process flow using an event, do the following:
- Create the required event activity
- Bind the Process Flow with an Event Activity
- Activate Event Activity
Creating Event Activity
An Event is used to define a condition for the process flow to execute it automatically. For example, if you want to execute the process flow when an email from a particular sender or with a particular subject arrives in your mailbox, you need to create a Mail Event activity.
Similarly, if you want process flow to be executed when a record is inserted in a particular table of a database, you need to create a Database Event activity.
To know the list of events that you can create and to know the process of their creation, click here.
Binding Process Flow with Event
To bind the process flow with the event, you need to create an Event Registry. Event Registry defines which process flow is triggered when conditions defined in the event are met. For more information, click here.
Activating Event
After creating the event and binding it with the process flow, activate the event. To activate the event, select the event on the Manage Event screen, and click the Activate link. For more information, click here.
Viewing Process Flow Log
Once your process flow is executed either manually or by an event, you may want to know whether the execution is successful or not. You can see the status of the process flow in the process flow logs.
Automating Complex Business Scenarios
The example explained above is a simple process flow. However, Adeptia Suite enables you to automate more complex business scenarios. It allows you to use:
- Decision node in your process flows.
- Workflow activity, in case you want some human interaction within your business process.
- Web Service Provider activity, if you want to publish your business process as Web Service.
- Web Service Consumer activity, if you want to create a business process which can invoke any third party web service.
- Mail Notification activity, if you want to send an email at any stage of the business process.
- Custom Plugin activity, if you want to use any custom Java logic to process the data.
- Native Service activity, if you want to run any batch or executable program.
Built-In Eval Flows
To demonstrate the advanced features of Adeptia Suite there are six evaluation process flows that are based on some business scenarios. These process flows are explained in the /wiki/spaces/AS/pages/5311431. We highly recommend you to go through the guide and try the process flows. The list of built-in Evaluation Process Flows and their high-level description is as follows:
Data Transformation Process Flow
This sample Process Flow demonstrates the use of different mapping functions to transform the source data into the required format. This Process Flow is used to extract data (Insurance Policy information) from a database source and convert it into an excel format. Conversion of data from database specific format into excel format is done using different mapping functions. After conversion, data is written in an excel file and that excel file is saved into the specified location. At the end of the Process Flow, a native call is used to execute a batch file, which creates a log file. This log file contains the details of the excel file, which is created by the process flow.
Custom Plugin Process Flow
This sample Process Flow demonstrates the use of Custom Plugin and generation of a dynamic file name. Custom Plugin is used to call Java code to perform the specific task. In this Process Flow a zip file, which contains two different text files, is used as a source. Custom Plugin calls a Java code, which extracts both the file and concatenates them into a single text file. This file is further converted into Excel file and then compressed into a zip file. The current date is appended to the name of the zip file, which is then saved in the specified target directory.
Process Designer Process Flow
This Process Flow demonstrates the use of different features of Process Designer. In this Process Flow, a purchase order, which is in text format, is used as a source. Values of the purchase order (such as PO Number, Amount, Company Name, and Item) are separated by a comma (,). A copy of the purchase order is saved into a specified folder. Another copy of the purchase order is sent to either of the Manager or Director of the company through email. If the purchase amount is less than US$ 50,000, the purchase order is sent to the Manager for approval. If the purchase amount is greater than US$ 50,000, the purchase order is sent to the Director for approval.
Process Flow to Process Excel Data
This sample Process Flow demonstrates the use of different features of process designer and complex mapping functions. The Process Flow is triggered on arrival of emails with a different subject. Each mail has an excel file attached to it. The subject of the mail specifies the format of the excel file. Based on the subject of the mail, Decision Node of the Process Flow decides which schema to be used to parse data from the Excel file. For example, if the subject of the email is FORMAT1, Schema1 is used. If the subject of the email is FORMAT2, schema2 is used. After the data is parsed using either of the schemas, mapping rules are applied and data is inserted or updated into one of the two databases. All error records (e.g. duplicate record) are written into a sequential file.
JMS Event Driven Process Flow
This sample Process Flow demonstrates the use of a JMS Event for triggering a Process Flow. The JMS Event is configured to listen for the data (containing real-time stock quotes) from a JMS server. The JMS Event is registered with the Process Flow. JMS Event on receiving the data gets fired, and in turn triggers the Process Flow. The Process Flow receives data from the JMS Event, converts it into database specific format and finally inserts the data into a database server.
Record to Record Service Process Flow
This Process Flow is used to process data of a positional file. Data of the positional file is processed record by record. One record is taken at a time, processed and finally sent to JMS server. After the record is inserted to the JMS server at the target end, an email is sent for acknowledgment, and next record is taken for processing. The whole process continues till all the records of the positional file at the source end are processed and inserted to the JMS server.