Generally, operations correspond to specific tasks. For example, a loan approval workflow might include a step for printing payment coupons. An automated process named LoanPrint could complete this step; within LoanPrint, a function named Coupons contains the code to print the coupons. The following are the general tasks necessary to use the Coupons function in a workflow definition:
Name |
Type |
Access (data flow direction) |
---|---|---|
cust_name |
String |
Read |
payment_amount |
Float |
Read |
loan_number |
String |
Write |
In the parameter definitions, Read indicates that a data value that passes from the work item to the operation. Write indicates that a data value is generated by the operation and then passed to the work item.
Name |
Type |
Expression |
---|---|---|
cust_name |
String |
ApplicantName |
payment_amount |
Float |
MonthlyPayment |
loan_number |
String |
LoanNumber |
In the parameter definitions, ApplicantName, MonthlyPayment, and LoanNumber are all data fields defined for the workflow. The above example indicates that the Coupons operation will use the value in the ApplicantName data field as input for the cust_name parameter; similarly, MonthlyPayment will be input for payment_amount. In addition, the LoanNumber data field will hold the value output by the loan_number parameter.