Configuring Child Requests using Request Modeler

Canvas now enables you to configure child requests using Request Modeler. You can now map the child requests to the parent requests to initiate quick and viable processing of requests.

Child Request Mapping enables the chaining of multiple requests and you can create several children requests for the same parent request. The main advantage lies in Business Key mapping configurations, which pave the way for chaining multiple children requests to the same parent request. Even additional children requests can be mapped to the existing children requests, and the parent request will have multiple mapped children requests. Moreover, parent and children tables can be mapped to both parent and children requests so as to ensure that the chaining of requests remains intact.

Child Request Mapping serves the purpose of streamlining the workflow management. On mapping the children requests to the parent request, the need for initiating multiple requests is eliminated, and moreover, the efficiency of child request mapping configurations lies in request chaining process.

Let's assume that two requests for two different sets of business data are created. The first one is Customer Details, while the other one is Account Details. Let's consider that the Account Number column is used in providing the Business Key Mapping for the parent request. Since the Account Number column can be used to identify the common patterns of business data, associated with both the requests, the Customer Details request will get assigned as the child request of the Account Details parent request. The Account Number column will get automatically identified on mapping the Customer Details child request to the Account Details parent request by using Child Request Mapping configurations.

Through coding, you can easily add the model data of the child request in the form model of the parent request. By adding the model data of the Customer Details child request to the appropriate JavaScript file of the Account Details parent request modeler form, you can easily specify the relevant business data of the Customer Details child request in the Account Details parent request. You can even format the data of the Customer Details child request and add the formatted data of the Customer Details child request along with the model data of the Account Details parent request in the appropriate JavaScript file of the Account Details parent request modeler form. So, the Account Details parent request, with the mapped Customer Details child request should be initiated in the end application.

Refer the following pages for detailed information on configuring child and parent requests using Request Modeler in Canvas Studio:

• Creating a Child Request
• Creating a Parent Request
• Adding a Button field to the Child Request form
• Launching the Child Request form in the Parent Request form through Event Wiring
• Adding the Model Data of the Child Request in the Parent Request Modeler form
• Initiating the Parent Request in the Application
• Approving the Parent Request in the Application