Configuring Request Modeler
- Vaishnavi Sridhar (Unlicensed)
In the rapidly-developing technological environment, the coding as we know it may not be adequate to develop an application in a quickest possible way and yet, satisfy the application requirements. The Request Modeler is a unique part of Canvas Technology framework that aims to minimize the coding for creating an application or the features within it.
The Request Modeler uses the minimal input and reduces the coding volume by identifying the re-usable codes and integrating them with the appropriate items. This will avoid the repetition of codes to a larger extent and the developer can focus on the resource bundling or manipulation of data as per the business requirement.
The Request Modeler is an automated process that specifies the necessary steps to initiate, modify, approve or reject each request flowing through the application. This will allow you to enable a set of workflow instructions that every request must follow through its cycle. It enables you to assign the actions to be taken when a request is submitted, approved or rejected. Also, the logging and auditing activities are included as a default part of the Request Modeler.
Whenever a request modeling definition is created, apart from the Request Modeler related configurations, the entries in the following database configurations get updated automatically and this saves a lot of valuable time and effort:
- Form definition and form container action mapping
- View and view item definitions with context action
- App definition
- Workspace menu with action
- Events configuration
- Alert configuration
- Audit configuration
- Data source definition
- Validation xml is also generated for the purpose of server side validation of the form data.
Watch the following video for a brief overview on Request Modeler.
Refer the following topics for more details: