Skip to content

Update Request Task Screen

Key Lesson: In this step, you learn how to adapt the Approve Request task screen so Requesters can review rejection feedback, update the Purchase Request, and resubmit it to the Process.

Create the PurchaseRequestUpdate task screen used by Requesters to review rejection feedback, update a rejected Purchase Request, and resubmit it.

Rather than building this screen from scratch, copy the Approve Request screen and modify the copy for the Requester. For instructions, see Copy the entire screen.

Attention

After copying a screen, review its component references, variables, bindings, expressions, and actions. Unresolved references may appear blank in Lowgile Studio. See Copied Screen References Are Not Updated for more information.
  1. Copy the PurchaseRequestApprove screen and rename the copy PurchaseRequestUpdate.
  2. Configure the screen text label:
PropertyValue
TextYour request has been rejected. Please update and resubmit:
  1. Save your changes before continuing.

The copied screen already contains the variables, embedded PurchaseRequestInclude screen, comment field, and other components created for the Approve Request screen. Reconfigure these components so the Requester can edit the Purchase Request while the Approver’s comment is displayed as read-only.

When configuring the Purchase Request details, leave any properties not specified at their default values.

1. Confirm/Reconfigure the screen variables

Section titled “1. Confirm/Reconfigure the screen variables”
  1. Open the screen’s Variables tab.
  2. Confirm that the request variable is configured as follows:
PropertyValue
Namerequest
ContextInput
Type
This.PurchaseRequest
Default expressionLeave blank
  1. Save your changes before continuing.

2. Reconfigure the Purchase Request details and comment

Section titled “2. Reconfigure the Purchase Request details and comment”
  1. Return to the Layout tab.
  2. Move the embedded PurchaseRequestInclude screen out of the Disable component and place it above the Disable component.
  3. Leave the now empty Disable component in place.
  4. Confirm that the embedded screen is configured as follows:
TabPropertyValue
PropertiesScreenPurchasing.PurchaseRequestInclude
Inputsrequest
screen.request
  1. Save your changes before continuing.

  2. Drag the comment Input component into the empty Disable component.
  3. Configure the comment Input component as follows:
PropertyValue
LabelApprover comment
Binding
screen.request.comment
TypeText Area
  1. Set or confirm the following Disable component properties:
PropertyValue
Disabledtrue
Keep disabled if already disabledChecked
  1. Save your changes before continuing.

The copied screen already contains the submit output. Confirm that it returns the updated Purchase Request to the Process.

  1. Open the screen’s Outputs tab.
  2. Confirm that the submit output is configured as follows:
PropertyValue
Namesubmit
Output type
This.PurchaseRequest
Can drive Process forwardChecked
  1. Save your changes before continuing.

The copied screen contains the Approve and Reject buttons used by the Approver. Replace these controls with a single Resubmit button for the Requester.

  1. Return to the screen’s Layout tab.
  2. Delete the Reject button.
  3. Update the remaining Approve button as follows:
ButtonTabPropertyValue
ResubmitPropertiesPrefix iconsend
TextResubmit
AppearanceColorPrimary
Events → ClickAction type → Ad-hoc action
await output.submit(screen.request)
  1. Leave all other properties at their default values.

  2. Save and close the editor.

Understand screen variables, inputs, outputs, components, and bindings.

Learn how task output values select the next route through a Process.

Review how actions submit updated screen data and trigger task behavior.