Skip to main content

#Quick Actions5 debatiendo

Annmarie Baker preguntó en #CPQ

PLEASE ANSWER ONLY IF YOU ACTUALLY KNOW 

WHAT YOU ARE TALKING ABOUT.  ChatGPT and Google did not help. DO NOT PASTE THAT JUNK HERE. Get Answer Leaderboard "points" on someone else's time. 

 

I have the System Admin profile with View All Data and Modify All Data permission.  I cannot see the New Quote button in the header on Opportunity Lightning Pages.  I have a user with a Business profile who also cannot see the button.  I have a different user with a Sales profile who CAN see the button.  In my Sandbox, I switched the blocked user to the Sales profile, logged in as him, and still cannot see the button.  When I log in as the Sales user I can see the button.  I checked different record types in different apps.  The Sales user always sees the button the Business user and Sys Admin never see the button. 

 

All three profiles see the same page layout for each Opportunity Record type.  "New Quote" is a custom create record action on the Opportunity object.  It works for the Sales user with no issues or errors.   

 

"New Quote" is an Action on the Opportunity object.  It is not a Global Action.  I checked the fields on the Action Layout and the predefined fields in the Action.  All three profiles have View permissions on all fields and none of the fields are Read Only for anyone.  The Object of the Action is Opportunity and the target is Quote.  The Record Type is Master.  The Sales and Business profiles have Master as the default Record Type for Quotes.  Sys Admin has Standard as the default Record Type.

 

All three users are Flow users.  All three users are Marketing users.  We all have the Salesforce CPQ User (or Admin) permission set.  We all have the CPQ permission set license.  We all have the CRM permission set license. 

 

The Lightning Page we are seeing i the org default.  When I view the page in the Lightning Editor, I still don't see the "New Quote" button in the header.  There is no filter on the header component.  The same Compact Layout is assigned to all Record Types. 

 

The only CPQ plug in we have is a Product search.   We do not put Quotes in Queues.  We do not use Roles and Hierarchy.

 

What am I missing? 

 

#CPQ  #CPQGurus  #Quotes  #Opportunities  #Pagelayouts  #Lightning App Builder  #User Profiles  #Quick Actions

2 respuestas
  1. 11 sept, 06:48

    I added this to the original post as well, in case someone who knows how to do this reads it:  The Object of the Action is Opportunity and the target is Quote.  The Record Type is Master.  The Sales and Business profiles have Master as the default Record Type for Quotes.  Sys Admin has Standard as the default Record Type.

0/9000

we have finical account with investment record type. we have quick action button call "create service catalog request " this button call flow. 

expected sloution; click on action then the flow calls and check record that have any existing service catalog request with draft request status , if it is true show the error msg like edit the draft and use.  

false-check the flow type and create the service catalog request , show the toast notifaction and action open that new created request. 

actual solution :  the service catalog request is toast msg is coming but the  "your flow finished" msg is poping up and need manual closing and not opening the  service catalog request . 

this working other envirments (sandboxs)only faiing after the winter27 realese  

 

#Financial Services Cloud  #Salesforce Developer  #Flow  #Quick Actions  #Salesforce Admin

2 respuestas
  1. 3 sept, 16:27

    Hi Eeswarini, 

     

    Since this worked before Winter '27 in the same design, this looks like a genuine regression in how the flow's finish behavior is being handled after the release — not a logic error in your flow. 

     

    Background: "YOUR FLOW FINISHED" appears whenever a flow ends without a screen as its last executed element. If your flow's last step is an action (like ShowToast) rather than a screen, Salesforce falls back to this default finish screen. If this wasn't happening before Winter '27 with the exact same flow, something changed in how the platform determines "last executed element" or how quick-action-launched flows auto-close. 

     

    Fixes to try: 

    1. Add a final Screen element at the very end (after ShowToast), with header and footer removed, and use a Navigation-type action (e.g., NavigateToNext or similar Unofficial SF flow action) to auto-continue/close instead of a real screen the user sees. This is the standard workaround regardless of the regression, since it forces flow completion via a screen node rather than relying on default finish behavior. 

    2. Check the Quick Action's flow settings on the record page — Winter '27 changed some Flow/Quick Action finish-behavior defaults; confirm "Reload page after finishing" or the flow's finish handler config still matches your prior sandbox setup. 

    3. Compare flow versions/metadata between the working sandbox and the affected environment — if this environment got the Winter '27 upgrade first, check if a newer flow runtime setting differs. 

     

    Given it's release-tied and reproducible, I'd also open a case referencing "screen flow finish behavior change post-Winter '27" — if this is a genuine platform regression, Salesforce needs it logged to fix it broadly, not just worked around per-flow. 

     

    Reference:

    https://unofficialsf.com/navigate-everywhere-flow-action/

0/9000
3 respuestas
  1. 24 ago, 17:05

    Hey Renuka, 

     

    A record page's actions are a combination of Quick Actions, standard buttons (Edit, Delete, Clone), Chatter actions, and productivity actions, all rendered together in the page-level action menu, but they trace back to different generations of the platform. 

     

    Standard buttons like Edit predate Quick Actions entirely, they're core CRUD operations baked into Salesforce since Classic, tied directly to page layouts and standard controllers. Quick Actions came later (Lightning-era) as a more flexible, declarative framework built for things standard buttons couldn't do well: creating related records, logging calls, launching Flows/LWCs, all without needing a full page navigation. 

     

    Salesforce never migrated Edit/Delete/Clone into the Quick Action framework because they're fundamental object-level behaviors tied to page layout metadata and permissions, not something layered on top. Rebuilding them as Quick Actions would be redundant and risk breaking backward compatibility across every existing org. 

     

    So the short answer: it's not that they overlap by design, it's that Standard Buttons are older, layout-level plumbing, and Quick Actions are a newer, more flexible layer built alongside them, not a replacement for them. 

     

    Reference:

    https://trailhead.salesforce.com/content/learn/modules/lex_migration_customization/lex_migration_customization_actions

0/9000

Good morning!

I was trying to create an action to put on the list view of Accounts, in order to create a new account with a layout showing a few fields. I came to realize that when creating an action which creates a new record, by default it behaves as 'create new child record' so you can only use it when selecting an account on the list view and then clicking the button (otherwise you get an error message). Salesforce support confirmed this is works as designed.

Now my question is: how do I create an action/button that does what I'm looking for? I created a global action to do this from the record page but I want to put one on the list view as well.

#Quick Actions #List Views

5 respuestas
  1. 24 jul 2025, 08:35

    Any OOTB solutions to it? All I can think about is overriding the custom quick action. But nothing from the Standard functionality side.

0/9000

I'm currently facing an issue with displaying a Lightning Web Component (LWC) quick action button on the Task record page.

Here are the details of what I've done:

 

1. LWC Quick Action Creation:

  • I have created a Lightning Web Component for a quick action under the Task object.
  • I updated the XML as shown below:

<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">

    <apiVersion>57.0</apiVersion>

    <isExposed>true</isExposed>

    <targets>

        <target>lightning__RecordAction</target>

    </targets>

    <targetConfigs>

        <targetConfig targets="lightning__RecordAction">

            <actionType>ScreenAction</actionType>

        </targetConfig>

    </targetConfigs>

</LightningComponentBundle>

 

2. Page Layout Configuration:

  1. I have added the button to the page layout under "Salesforce Mobile and Lightning Experience Actions."

Despite following these steps, the quick action button is not visible on the Task record page. I have ensured that the action is available in the "Lightning and Mobile Actions" section of the page layout.

Can anyone help me identify what might be causing this issue or suggest any additional steps to troubleshoot? Your assistance is highly appreciated.

Thank you in advance!

 

#Developers #Lightning Web Components #Quick Actions #Pagelayouts

4 respuestas
  1. 28 nov 2024, 18:00

    I had a similar problem, and found a solution for my case:

    In Service Setup > Channels > Digital Experiences > Settings, make sure the "Use Lightning web components on your record pages in Aura sites" option under "Experience Management Settings" is checked.

0/9000

I am trying to create an action that shows up in the Field Service mobile app that when the user clicks on the action, it takes them to a specific url. I can not get the action to show up on mobile app for service resources to use. I’ve built the action, added it to the page layout and still nothing. Any thoughts?

#Salesforce Field Service #Quick Actions #Custom Action Button
1 comentario
0/9000

With Summer 21', we have the ability to create a Quick Action from a LWC. https://developer.salesforce.com/blogs/2021/05/learn-moar-with-summer-21-lwc-quick-actions.html

https://help.salesforce.com/articleView?id=release-notes.rn_lwc_quick_actions.htm&type=5&release=232

The Quick Action doesn't use any of the HTML I can write in this component :

But I want to include a Spinner. I search for many ideas, creating another component which include just a spinner, but it seems really hard to open and close this component from the first one. I also didn't find any way to call a spinner by the JS without the HTML

There is my code :

 

getAccountReport.js

import { LightningElement, api, track } from 'lwc';

import { ShowToastEvent } from 'lightning/platformShowToastEvent';

import getAccountReport from '@salesforce/apex/WS_Account_Report.getAccountReport';

export default class GetAccountInfosQALWC extends LightningElement

{

@api recordId;

@api invoke() {

//Here i'm sending a Toast message as a workaround

//But I want the spinner starting here

this.showToastMessage(1,'We are getting your report in few seconds...');

getAccountReport({accId : this.recordId })

.then((result) => {

//I want the spinner to stop here

if(result != true && result != 'true'){

this.showToastMessage(1,result);

}

else{

this.showToastMessage(2,'The report was successfully downloaded');

eval("$A.get('e.force:refreshView').fire();");

}

})

.catch((error) => {

console.log(error);

});

}

showToastMessage(fromWho, mess, urlToast) {

var variantToast;

var titleToast;

if(fromWho == 1){

variantToast = 'info';

}

else if(fromWho == 2){

variantToast = 'success';

titleToast = 'Success'

}

const toastMessage = new ShowToastEvent({

title: titleToast,

message: mess,

variant: variantToast,

messageData: [

{

url: urlToast,

label: 'here'

}

]

});

this.dispatchEvent(toastMessage);

}

}

getAccountReport.js-meta.xml

<?xml version="1.0" encoding="UTF-8"?>

<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">

<apiVersion>52.0</apiVersion>

<isExposed>true</isExposed>

<targets>

<target>lightning__RecordAction</target>

</targets>

<targetConfigs>

<targetConfig targets="lightning__RecordAction">

<actionType>Action</actionType>

</targetConfig>

</targetConfigs>

</LightningComponentBundle>

I already tested to put the spinner in the HTML, that's not working.

 

#LWC  #Lightning Web Components  #Quick Actions  #Service Cloud  #New Releases

Thanks you !

4 respuestas
  1. 13 jun 2024, 13:58

    if you dont wanna utilize html,

    You can try add spinner html in slds to dom by js and remove it.

     

    this is demo code

     

    import { LightningElement } from 'lwc';

    export default class SpinnerComponent extends LightningElement {

    addSpinner() {

    const container = this.template.querySelector('.spinner-container');

    const spinnerHTML = `

    <div class="demo-only demo-only_viewport" style="height:6rem;position:relative">

    <div role="status" class="slds-spinner slds-spinner_medium">

    <span class="slds-assistive-text">Loading</span>

    <div class="slds-spinner__dot-a"></div>

    <div class="slds-spinner__dot-b"></div>

    </div>

    </div>`;

    container.innerHTML = spinnerHTML;

    }

    removeSpinner() {

    const container = this.template.querySelector('.spinner-container');

    container.innerHTML = '';

    }

    }

0/9000

Don't judge but we are still using classic. I have a handful of Custom Buttons on Accounts and Leads. It's my understanding that it's best practices to convert these to Quick Actions for lightning. I've done this and they seem to work. 

 

Here's my question.... When I am in classic I only see the buttons, when in Lightning I see both. Is there a way I can edit the page layout etc so that I only see the Actions when I am lightning?

 

It would be MUCH simpler to just leave the custom buttons. What are the downsides to this?

 

#Lightning Experience  #Quick Actions  #Custom URL Button

2 respuestas
  1. 26 feb 2024, 19:20

    To remove one of the buttons while in Lightning Experience, you can remove the button from the Salesforce Mobile and Lightning Experience Actions section. This enables the custom button that works both in Classic and LE to be shown just once. 

    As an alternative way, you can conditionaly render specific buttons by editing the Lightning Record Page: https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_visibility.htm&type=5

    Keep in mind that only custom buttons that execute javascript code are not supported in Lightning Experience

0/9000

Hello everyone,

I know on the first look this seems like an issue which should be doable via the dynamic forms on Lightning Record pages. However, sadly this is not the case for my Problem.

The Problem itself occurs in the Financial Services Cloud. This cloud has a specific component to show insurance policies on the Account (It works like a normal related list but with additional features) This feature takes the actions it provides to users from the Lightning Actions which are defined in the respective page layout.

Now to the actual Problem: We would like to have a specific action available in this component but not on the normal mobile page for insurance policies. So far I have sadly not found a way to separate this.

 

This is the Action we want to have: (Please don't mind the partially German interface)Separate Page Layouts for Mobile and Desktop due to Lightning Actions (SF-FSC)

This is the Action I don't want to see:

20240215_Bug_Action2.pngThanks for any help :)

 

#Mobile  #Pagelayouts  #Quick Actions  #Financial Services Cloud

2 respuestas
  1. 15 feb 2024, 08:32

    @Manoj Nambirajan Sadly I don't think that this will use my actual issue. Even if I include a filter based on device, I need to use the Lightning Actions in the the Page Layout. Reason for this is that I can only define the actions in the component on the Account via the Lightning Actions on the Insurance Policy Page Layout. (It sounds crazy, but sadly this seems to be the way it works)

    And as far as I see it those Lightning Actions don't care for dynamic forms and just show up on the mobile layout anyway. 

0/9000

Hi,

 

I managed to add the action as URL but I opened in a new page, Also I`ve created an aura component but I cant add it to the list view, I want that the screen flow will be opened as a popup and not new page.

 

Any suggestions?

 

Thanks!

 

#Lightning Aura Component #Quick Actions #PopUps

6 respuestas
0/9000