Skip to main content

#Approval Actions1 diskutiert mit

Hi Salesforce Community,

 

We have a requirement to capture a Site Visit confirmation (Picklist field - Yes/No) from the approver before they approve a Salesforce Opportunity. We are currently using a

Classic Approval Process

and want to provide this input directly on the Approval Request screen, without requiring users to navigate back to the Opportunity record. 

 

We have explored the standard Salesforce configuration and encountered the following limitations: 

 

  1. Conditional Visibility: Lightning App Builder does not appear to support component visibility rules on the standard Approval Request Lightning Record Page. 

     

  2. LWC/Flow Placement: We could not find a supported way to add an LWC or Screen Flow exclusively to the Approval Request screen with conditional visibility based on the related Opportunity. We would also like to understand  

     

  3. Editable Fields: Fields displayed on the standard Approval Request screen appear to be read-only. Is there a supported way to make a custom picklist editable directly on this screen? 

     

  4. Approve Button Customization: Is it possible to customize or override the standard Approve button to capture additional input before processing the approval? 

     

  5. Custom Actions or Buttons: The Approval Request object does not appear to expose the usual custom button/action creation options available on standard Salesforce objects.

Our expected behavior:

  • Display the Site Visit (Yes/No) field only when the related Opportunity meets all these conditions:
    • Stage = Qualified
    • Record Type = Booking
    • Status = Pending Approval
  • Allow the approver to select Yes/No and click Approve on the same screen.
  • Allow approval only when the answer is Yes; block approval when the answer is No or blank.
  • Preserve the existing Classic Approval Process and its Manager → Branch Manager approval sequence.
  • Provide a user-friendly experience on both desktop and mobile.

Questions:

  1. Is there a supported Salesforce configuration or customization approach to achieve this directly on the standard Approval Request screen?
  2. Can an LWC, Screen Flow, or custom action be embedded in the Approval Request page and interact with the existing approval work item?
  3. If this is not supported on the standard page, what is the recommended approach for integrating custom input with a Classic Approval Process without forcing users to navigate between screens?
  4. Has anyone implemented a similar solution using LWC, Apex, or another supported Salesforce extension?

We are specifically looking for a solution that modifies the existing standard Approval Request screen

, rather than asking users to open a separate custom approval page or navigate back and forth between the Opportunity and approval screens. 

 

Any official documentation, technical guidance, or working implementation examples would be greatly appreciated.

 

Hi Salesforce Community, We have a requirement to capture a Site Visit confirmation (Picklist field - Yes/No) from the approver before they approve a Salesforce Opportunity.image.pngimage.png

 

 

 

 

#Sales Cloud  #Approval Rules Setup  #Approval Actions  #Approval Record  #Salesforce Developer  #Salesforce Admin

Will flow every replace approval actions? And for that matter will there ever be a way to have my automation logic using only one solution? Approvals use workflow actions, Process Builder uses email alerts that can only use classic email templates and flow is off on its own abut doesn't have the same features as Process Builder or Workflow (scheduled workflow visibility). There is also no way to organize flows to control the order of execution yet which with the way flow is progressing this could become an even bigger challenge than now.

1 Kommentar
  1. 23. Sept. 2020, 19:20

    1) Hopefully (Some small work has begun on this already, but it's a big project)

    2) Realistically no, but that's a rough goal we have

    3) Flow is the Future and we recommend using it when possible over other tools

    4) The team's working on the best way to address save order logic: ease of debugging, consistency of execution, etc