Map Dictionary fields in UI Builder and Update the record

Prashanthi10
Giga Contributor

Hi,

 

In Service Operations Workspace, when an approver rejects a request, two custom fields (Rejection Reason and Rejection Details) are shown and captured and are choice fields. The same fields should also be visible and auto-populated in the approval action form configured in UI Builder when the approval record is reopened. How can these fields be correctly mapped and displayed?




4 REPLIES 4

Prashanthi10
Giga Contributor

@Matthew_13 Could you please help with this requirement? Any guidance would be appreciated.

Clear set requirement:

 When an approver rejects a request in Service Operations Workspace the system must capture Rejection Reason and Rejection Details both choice fields and persist them to the database. When the same approval is reopened the UI Builder approval action form must display and auto populate these fields using the previously saved values. The fields must be bound to the same record and table where the rejection values were stored preferably the approval record sysapproval_approver so that values are approval-specific render correct choice labels, and do not carry over to other approvals.

 

@Prashanthi10 - Please mark as Accepted Solution and Thumbs Up if you find Helpful!!

@Prashanthi10 - Hopefully this helped you my Friend; if so please mark as Accepted Solution and Thumbs Up.

Matthew_13
Kilo Sage

Hi there my Friend

You need to bind those two fields to the same record where the reject action actually saved them.

  • If Rejection Reason / Details are on the approval record (sysapproval_approver):

    1. In UI Builder, load the sysapproval_approver record (use the approval sys_id from the route/context).

    2. Put the two fields on the form and set their value bindings to:

      • sysapproval_approver.u_rejection_reason

      • sysapproval_approver.u_rejection_details

    3. Configure the choice components to pull choices from sys_choice for table sysapproval_approver and those elements.

  • If the fields are on the target request/RITM (sc_request / sc_req_item):

    1. Load the sysapproval_approver record first.

    2. Then load the target record using sysapproval_approver.sysapproval as the sys_id.

    3. Bind the fields to:

      • target.u_rejection_reason

      • target.u_rejection_details

    4. Pull choices from sys_choice for the target table/field.

Main point: dont map them manually just make sure the form is reading the same table/fields that were written during Reject and it will auto-populate when the approval is reopened.

 

@Prashanthi10 - Please mark as Accepted Solution and Thumbs Up if you find Helpful!!