Appendix A: 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 the 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 to the specified location. At the end of the process flow, a native call is used to execute a batch file that creates a log file. This log file contains the details of the excel file 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 a specific task. In this Process Flow, a zip file containing two different text files, is used as a source. Custom Plugin calls a Java code that extracts both the file and concatenates them into a single text file. This file is further converted to excel file and then compressed into a zip file. The current date is appended to the name of the zip file and 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, in text format, is used as a source. Values of the purchase order (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 the 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 (for example, duplicate record) are written to 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 the 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.