203 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
sfdx-l18n-plugin
Thu, Sep 14th 2017 5
The best way to learn a platform is to use a platform
Fri, Aug 11th 2017 10
Flip Chrome flag to easily inspect TLS certificates (from Chrome 60)
Tue, Aug 8th 2017 3
Developing Salesforce Lightning Components that are visible at design time but not at runtime
Thu, Jun 29th 2017 4
Deploy your own Salesforce Workbench on Heroku at the click of a button
Thu, Jun 22nd 2017 10
Currency conversion in Apex
Tue, Jun 20th 2017 6
Simplifying usage of Salesforce Lightning Design System using NPM and Express
Wed, Jun 14th 2017 5
Top 10
Lightning Components as Quick Actions in Salesforce1 and padding
Wed, Feb 8th 2017 14
Installing TDI v. 7.1 on Windows Server 2012
Wed, May 7th 2014 13
Premaster RSA secret error with 4096-bit encryption in WAS ISC
Sun, Jun 15th 2014 12
Eclipse target platform invalidated by IBM Notes 9.0.1FP4 on Mac
Mon, Jul 20th 2015 11
component.find woes in Salesforce Lightning
Tue, May 2nd 2017 11
IBM Connections application development state of the union - part 6
Wed, Sep 14th 2016 10
Salesforce username/password OAuth flow against a sandbox
Tue, Jan 31st 2017 10
Deploy your own Salesforce Workbench on Heroku at the click of a button
Thu, Jun 22nd 2017 10
The best way to learn a platform is to use a platform
Fri, Aug 11th 2017 10
IBM Notes IBM Connections plugins cannot connect after upgrade to v. 9.0.1FP4 on Mac
Wed, Jul 15th 2015 9


Lightning Components as Quick Actions in Salesforce1 and padding
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
   

Since Winter 17 we have had the option of using a Using Lightning Component as a Quick Action. In the Lightning Experience in a desktop browser the component is shown as a popup (actually a lightbox) in the UI and in Salesforce1 (the Salesforce mobile app) it's more of a modal fullscreen dialog. All this is great. Only thing you have to do is to make your component implement force:lightningQuickAction (all declaratively) and it can be added as a Quick Action. The resulting lightbox / dialog will have a header with the action name and a default Cancel button to close the dialog. Again great but what if you want to name the button something else? Or if you need a custom header? Well there is another interface for this called force:lightningQuickActionWithoutHeader. So far so good. The issue is that while this removes the default header and buttons it doesn't quite cut it in Salesforce1 as the container will still add a default margin around the component. Bummer...

The only way I found to fix this in the component I'm doing now is to add a negative martin on the component itself thereby hacking the UI. The added style is in bold - there is a negative margin to push the UI out of bounds to appear at 0,0 and a width and a height to make sure the header bar looks correctly. I've reported this internally and I hope someone will come up with a fix e.g. a new interface to add this explicitly.

<aura:component implements="force:hasRecordId,force:lightningQuickActionWithoutHeader">
    <div class="slds-modal__header" style="margin: -20px 0 0 -20px; width: 120%; height: 50px">
        <a href="javascript:void(0)" class="slds-float--left" title="back" onclick="{!c.close}">
            <c:svg svgPath="{!'/resource/SLDS221/assets/icons/utility-sprite/svg/symbols.svg#back'}" 
                   category="standard" 
                   size="x-small" 
                   name="back" 
                   strokeColor="#0070D2" 
                   class="slds-icon-text-default" /><span class="slds-assistive-text">Back</span>
        </a>
        <span class="slds-text-heading--small slds-float--left slds-p-left--x-small">Contact Sync</span>
    </div>
    <div>
        UI body...
    </div>
</aura:component>



---------------------
http://lekkimworld.com/2017/02/08/lightning_components_as_quick_actions_in_salesforce1_and_padding.html
Feb 08, 2017
15 hits



Recent Blog Posts
5
sfdx-l18n-plugin
Thu, Sep 14th 2017 1:35p   Mikkel Heisterberg
Today I've published my first plugin to the SalesforceDX CLI. The plugin is called sfdx-l18n-plugin and allows you to change localisation settings for the user in the scratch org you create. You can query the current values, list the available values from the org and set new values. The plugin can return values in plaintext or as JSON for automation. Changing the org to run in Japanese using Japanese locale and the timezone from Tokyo is as easy as: sfdx l18n:user:set -u japanese --locale ja_J
10
The best way to learn a platform is to use a platform
Fri, Aug 11th 2017 3:06p   Mikkel Heisterberg
Wow what a week it's been. First week back from vacation and I'm diving right into a sprint of stuff that needs to be delivered to the customer. My task for the week has been develop a connectivity layer between Salesforce and Dropbox using OAuth. This task has taken me on quite a learning journey. Now I'll call myself quite a seasoned programmer but ever since joining Salesforce 9 months ago I've had to relearn a lot of stuff. A new programming language in Apex, new framework technologies
3
Flip Chrome flag to easily inspect TLS certificates (from Chrome 60)
Tue, Aug 8th 2017 10:57a   Mikkel Heisterberg
As a developer - or a security conscious user - you may want to inspect TLS certificates from time to time. However inspecting them in Chrome is hard as access to the certificate hierarchy dialog has been tucked away in the Developer Tools. Happily Chrome 60 has added a flag to add an easy to reach option back to the TLS dropdown in Chrome. Please note that manually editing Chrome browser flags may mess up your browser - don't say I didn't warn you... In the below video I show you how...
4
Developing Salesforce Lightning Components that are visible at design time but not at runtime
Thu, Jun 29th 2017 7:48p   Mikkel Heisterberg
So this can clearly be labelled as a "Lightning Lesson from the Field". As you start to develop more complicated Salesforce Lightning applications - and why wouldn't you - you as I have done start seeing great power in hidden components. By hidden components I mean components that contribute code or does "something" but which does not have a UI. Thes are very easy to do but have a big drawback as they are also invisible at design time making them near impossible to find the Lightning AppBui
10
Deploy your own Salesforce Workbench on Heroku at the click of a button
Thu, Jun 22nd 2017 8:07a   Mikkel Heisterberg
The other day Salesforce Workbench was having issues. Generally it kept returning errors and SOQL queries took forever and timed out. Now Salesforce Workbech is a LAMP app that runs on Heroku and it turns out it is actually possible to deploy your own instance on Heroku using a simple Heroku Button. To do this simply follow the below steps (you need to have an account but if you don't simply sign up): Go to the project page at https://elements.heroku.com/buttons/jdrishe/salesforce-workbench Cl
6
Currency conversion in Apex
Tue, Jun 20th 2017 7:56p   Mikkel Heisterberg
While waiting for my flight in the lounge tonight I was playing around with currencies in Salesforce because - why not... Conversion between configured currencies are supported in SOQL and Salesforce but only between the configured corporate currency and the users personal currency. But what if you want to convert between an opportunity amount in one currency and into another currency using the configured conversion rates in Salesforce? Well there is no support for this. So as an Apex / SOQL sel
5
Simplifying usage of Salesforce Lightning Design System using NPM and Express
Wed, Jun 14th 2017 12:36p   Mikkel Heisterberg
Using Salesforce Lightning Design System (SLDS) is a great and easy way to add some super nice styling to your app. It comes with some nice defaults and a responsive grid system like other frameworks lige Bootstrap. Where SLDS really shines is of course if you are already using Salesforce (I assume you're already on Lightning right?!!?!?) or if you are going to. And again who isn't. Anyways... Using SLDS makes your apps really look like Salesforce which is nice for Salesforce Lightning Compone
5
Salesforce week 25-27 and finishing this weekly thing...
Mon, May 22nd 2017 6:38a   Mikkel Heisterberg
Wow!! A half year has gone by. Half a year... Where did the time go? Over the last weeks I've gradually noticed that my view on being with Salesforce has shifted from being "something new" to being "how things are". On feeling at home in the organisation and that I know my place. Does new things come up sure but it's feeling less and less like every day brings something new, a new badge or a new process. I've settled into the #Ohana. This is also why I've decided to stop writing these we
5
Salesforce Lightning Component API change
Wed, May 17th 2017 9:49a   Mikkel Heisterberg
As we get closer to Summer 17 we start using difference versions across production instances and sandboxes. This of course also leads to opportunities for differences in API's... I just found one such difference as I'd been developing some Lightning components on Summer 17 and got errors when trying to run them on Spring 17. In Summer 17 you can do the following in a client-side event handler to get the DOM element of the source component: ({ react: function(component, event, helper) { cons
11
component.find woes in Salesforce Lightning
Tue, May 2nd 2017 2:59p   Mikkel Heisterberg
When developing Salesforce Lightning Components you very often use the aura:id attribute on components to tag them and component.find to find them again. This works very well and is documented nicely in the documentation (Finding Components by ID). If however you tag a component using aura:id in an iterator you may not know how many resulting components will be on the page. The component.find method may return undefined (if no matching components), a component instance (if a single match was fou




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition