Request Capture

The data captured needs to be taken through a processing sequence before transferring it to the target data source.
The three categories of requests supports by the Request Modeler are:

• Transaction
• Library or data maintenance

• Service request
  
  

  You can use your own customized workflow as a Request Category in Request Modeler. For more information on using the workflow as a Request Category, refer Configuring Requests using a Workflow and Creating Requests using a Workflow. For detailed information on configuring child requests using Request Modeler, refer Configuring Child Requests using Request Modeler. 

The common patterns observed across the above mentioned request categories are listed as follows:

• Need to capture the request and take it through multiple states.
• Need to invoke services of different modules as part of the request processing sequence.
• Automatic audit/notification support as request flows through states.
• Cutting across functionality lines, the behavior of a request within the category is consistent.