Skip to content

Build the Approve Request Screen

Key Lesson: Build a task Screen that receives Process data, reuses an existing Screen for read-only request details, and returns a decision through a Process-driving output.

Build the PurchaseRequestApprove Screen that Approvers use to review a submitted purchase request. This step builds the Screen only; the next step assigns it to the existing Approve PR User Task.

  1. In Design, under Object Types, select Screen.
  2. Select +.
  3. Enter PurchaseRequestApprove as the Screen ID, then select OK.
  4. Select the default Text component and set Text to Please approve or reject the following request:.
  5. Leave all other properties at their default values.

  6. Save your changes before continuing.

The request input receives the submitted PurchaseRequest from the Process when the task opens.

  1. Open the Screen’s Variables tab.
  2. Select + Add new variable.
  3. Configure the variable as follows:
PropertyValue
Namerequest
ContextInput
Type
This.PurchaseRequest
Default expression(Leave blank)
  1. Save your changes before continuing.

Reuse the PurchaseRequestInclude Screen so the approval Screen displays the same request fields and line items as the Create Screen.

  1. Return to the Layout tab.
  2. From the SCREEN STRUCTURE section of the Components toolbar, drag a Screen component into the main content area below the Text component.

Editor Help

Remember: When dragging a component or variable onto a screen, Lowgile displays a green placeholder indicating where the element can be dropped.
  1. Configure the embedded Screen as follows:
TabPropertyValue
PropertiesScreenPurchasing.PurchaseRequestInclude
Inputsrequest
screen.request
  1. Leave all other properties at their default values.

  2. Save your changes before continuing.

Wrap only the embedded PurchaseRequestInclude Screen in a Disable component. The comment and decision controls added afterward must remain enabled.

  1. Select the embedded PurchaseRequestInclude Screen component.
  2. From the LOGIC section of the Components toolbar, add a Disable component next to it.
  3. Drag the embedded Screen inside the Disable component.
  4. Configure the Disable component as follows:
PropertyValue
Disabledtrue
Keep disabled if already disabledChecked
  1. Leave all other properties at their default values.

  2. Save your changes before continuing.

  1. In the VARIABLES panel, expand screen.request and confirm that comment is available.
  2. From the CORE section of the Components toolbar, add an Input below the Disable component.
  3. Configure the Input as follows:
PropertyValue
LabelApprover comment
Binding
screen.request.comment
TypeText Area
  1. Leave all other properties at their default values.

  2. Save your changes before continuing.

Create the submit output used by the Approve and Reject controls. The decision and comment are passed to the Approve PR task’s output handler after the Screen is connected in the next step.

  1. Open the Screen’s Outputs tab.
  2. Create a new output variable.
  3. Configure the output as follows:
PropertyValue
Namesubmit
Output type
{
  isApproved: boolean
  comment: string
}
Can drive Process forwardChecked
  1. Save your changes before continuing.

  1. Return to the Layout tab.
  2. Add a Layout below the comment Input and set Layout to horizontal in one row.
  3. Add two Button components inside the horizontal Layout.
  4. Configure the buttons as follows:
ButtonTabPropertyValue
ApprovePropertiesPrefix iconthumb_up
PropertiesTextApprove
AppearanceColorPrimary
Events → ClickAction type → Ad-hoc action
output.submit({
  isApproved: true,
  comment: screen.request.comment,
})
RejectPropertiesPrefix iconthumb_down_alt
PropertiesTextReject
AppearanceColorWarn
Events → ClickAction type → Ad-hoc action
output.submit({
  isApproved: false,
  comment: screen.request.comment,
})
  1. Leave all other properties at their default values.

  2. Save and close the editor.

Outcome

PurchaseRequestApprove can display a Process-supplied request without allowing its request fields to be edited. Its comment and decision controls remain enabled and submit the documented decision object.