19

I'm afraid you can't. I would like to be able to do it to, at least customize the behavior of the "Save" button, but unfortunately it's not possible. As you said, you need either to put the button inside your component with force:lightningQuickAction, or recreate everything in a component with force:lightningQuickActionWithoutHeader. Solution 1 is easier ...


17

There is a catch in case of cases and work orders objects when it comes to quick actions. In the article under Actions on record pages there is note that says Actions on cases and work orders appear in a different way than on other records. On case and work order records, the page-level action menu contains custom buttons and supported standard ...


13

I asked in the Lightning Trailblazers org62 group about this, a few months ago, and the response we got was that SFDC understands this usecase but do not have an estimate for delivery yet. FWIW, we created a custom component with a button that sits on the lightning page, instead of using a quick action. Initially we displayed a spinner inside the quick ...


12

You can try force:refreshView, which reloads all data for the view. So in addition to $A.get("e.force:closeQuickAction").fire(); add $A.get('e.force:refreshView').fire(); in your setCallback method. ({ handleClick : function(component, event, helper) { var saveLeadAction = component.get("c.leadSave"); saveLeadAction.setCallback(this, ...


8

I've eventually found a solution. The following script has to be included: <script type='text/javascript' src='/canvas/sdk/js/publisher.js'></script> Then use this line to close the Quick Action window: Sfdc.canvas.publisher.publish({ name: "publisher.close", payload:{ refresh: "true" }});


7

Use $A.get("e.force:closeQuickAction").fire();inside your component controller at the necessary place. This line will close the modal box automatically.


6

As you've discovered, you can get force:hasRecordId. Unfortunately, any other fields you want, you have to query for. The easiest way to query for them is with force:recordData; this automatically pulls the data from the cache, when available, and includes the record's name: <aura:component implements="force:hasRecordId,force:lightningQuickAction"> &...


5

Can you re-check this please. Because I tried the exact same code in my org and its working fine. Please check the screen shots - Note - Can you check your component version number once. Mine is 40 and it works fine.


5

I think no matter what kind of Quick Action you do, native or customized, it will always open a modal window in Lightning. You could create a small VisualForce page or Lightning component to add directly to the Lightning page layout, which simply hosts a button that carries out the desired action. That may be the only way to put a one-click action inside ...


5

There is a yet undocumented state property that helps here: this[NavigationMixin.Navigate]({ type: 'standard__objectPage', attributes: { objectApiName: this.type, actionName: 'new' }, state: { nooverride: '1' } });


4

The code I used was fine. I found following Known Issue existing for this same issue and it has been Fixed already in the platform now, and the Close behavior is not consistent with this Event firing from any context. https://success.salesforce.com/issues_view?id=a1p3A0000001CcxQAE&title=lightning-component-which-uses-force-closequickaction-is-working-...


4

Components can only have one controller, so assuming this is a generic utility called all over the place, odds are, no, you won't be able to do this directly. If you look at force:recordData, you'll see that having a "generic" utility component that can interact with a particular service can be a viable design. You'd hook everything up with aura:method, and ...


4

Thanks to Rajesh and Brian for their insight that I've taken on board. My answer here outlines what I plan to do, which is substantially also driven by the large number (around 50) of these buttons that I need to replace. At the server-side a single entry point that dispatches to the existing webservice methods seems a simple way to go: public with sharing ...


4

The force:lightningQuickActionWithoutHeader provides the box with the close button and semi-transparent black background. The slds-modal__container is providing the other semi-transparent black box (the one that goes from top to bottom). The container is not meant to be used in a Quick Action box.


3

The deploying user did not have Marketing User checked in the user's detail page. Therefore, the user didn't have access to Campaigns and could not deploy the create campaign quick action.


3

Just add the below code in your component so that it doesn't show up the modal when you click on the Quick action button <aura:html tag="style"> .slds-backdrop { background: rgba(43, 40, 38, 0) !important; } .slds-fade-in-open { display:none !important; } </aura:html>


3

Indeed, this is not supported in Lightning. In my organization, I mainly overcame this by including the desired logic in a unified Custom HTML email template, and set it as a default for the Email action. Also, I added the recipient list, email subject, FROM, to, cc and bcc fields as formulas in predefined fields on that same Email action. If you'll share ...


3

The reason why it is working when invoked in callback code because there is modal listener ready for the event and then modal listener can close the model. But if you write your logic on doInit ( I assume you are registering with init event) then there is no modal which is listening. So modal will not be able to close. If I am not wrong here you want to ...


3

According to the documentation, you can invoke Quick Actions both via Apex and REST API. https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_class_quickaction_quickactionrequest.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_sobject_quickactions.htm However, I do not think there is a base ...


3

Try this. After few css trick, I managed to fix it myself. This solution override the dialog box height which you mentioned while creating custom action on an object. I hope this will help someone needed. <aura:component implements="force:lightningQuickActionWithoutHeader,force:hasRecordId" controller="MilindTest"> <style> .cuf-content {...


3

The width is fixed. You're meant to create a responsive design that fits in the margins. No css or JavaScript you write can change this.


3

It's by design. As outlined in Set Up Mass Quick Actions: Mass quick action lets your users edit up to 200 records in a list view. You can perform mass quick actions on create and update quick actions on cases, leads, and custom objects in Lightning Experience. To set up mass quick actions, you customize the object’s search layout. So, for now, only ...


3

There are actually 2 bugs in send email quick action functionality. There is no way to set a template, its something which was uncooked and served. Only on Cases does it give you that option. (https://success.salesforce.com/answers?id=9063A000000e6pWQAQ) You will still be able to add that quick-action/Salesforce Mobile and Lightning Experience Action on ...


3

You could use Visualforce with standard list controller. Using a standard list controller is very similar to using a standard controller. First you set the standardController attribute on the component, then you set the recordSetVar attribute on the same component. For example, to associate a page with the standard list controller for accounts, use the ...


3

You won't be able to re-use your existing web service methods directly without having to annotate them with auraEnabled. In this case i only see two options. Use auraEnabled annotation Do a client side call out without even touching apex code.(Which i wouldn't recommend) So i believe you are stuck with option number 1. If you choose option 2. Below are ...


3

This is a expected behaviour from salesforce when feed tracking is enabled for cases or work orders, the page-level action menu on those records contains only custom buttons and supported standard buttons. Quick actions appear on the Chatter tab. workaround:- So in order to not see the action in the feed on Case or Work orders object record, you need ...


3

My understanding of ReadOnly is that they would be able to clone if they have IsCreateable permission, but not delete even if they had the CRUD access, because typically, only the owner or someone above the user in the role hierarchy can delete a record But I usually end up having to verify that via the UI to actually know if that happens. But I think you ...


3

This is a expected behaviour from salesforce when feed tracking is enabled for cases or work orders, the page-level action menu on those records contains only custom buttons and supported standard buttons. Quick actions appear on the Chatter tab. workaround:- So in order to not see the action in the feed on Case or Work orders object record, you ...


3

The quick action mainly introduced for Lightning Experience and mobile app. Yes, you are right, in classic you are limited to adding a quick action to chatter. In Lightning, You can add a quick action on detail page layout by adding it to Salesforce Mobile and Lightning experience action. You can also add a quick action to a list view of Object record. ...


3

Leave the JS button as is, and it'll only show on the Classic layout. Create a Lightning Component Quick Action which will read the value from the record and either display the appropriate message or redirect.


Only top voted, non community-wiki answers of a minimum length are eligible