When the end user fills the form, the data gets stored in the respective table after the request is approved. There may be scenarios where you may want the approved requests to be displayed as an app in a grid view. In such cases, Canvas felt the need to provide an option to the end user to edit or delete the requests based on the user entitlements by accessing them through the grid. For this, the liveEdit API has been implemented. The end user can edit or delete requests on the click of a row on the grid, button, and link or through a context menu configured in the app. In case of button click, developers must ensure to capture and pass the correct grid row data to the liveEdit API.
In case the custom form container is used, then explicit wiring is needed to proceed with the live edit or delete sequence. The wiring can be done using the executeAction API. For information on custom action wiring, refer API to Wire Custom Actions in the Self-designed Forms or Form Container to the Request Model Actions section.
For information on , refer form, app, and menu creation, refer the Expert Studio Dev Guide available in Unmail > Canvas Technology > Documents > Release 18.1.0.0.
The following screen shot is of the Employee Details app which displays the approved requests submitted by the end users through the EMP_DETAILS_FORM.
Edit and Delete menus have been configured in the app.
Let us assume a scenario where a user wants to change the mobile number. The user accesses the form by clicking the Edit menu on the grid and the self-designed form launches with the request details.
The user edits the Mobile number and submits the request for approval.
- Sample code used for editing a record by Edit menu
...