Yes. You need to create a design file for the component:
<design:component label="Label For Component">
See the Add a Design Resource to Your Component Bundle section in the dev guide at https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_config_for_app_builder.htm
Application-level events certainly are what Salesforce recommends for the use case of components that will be "App Builder siblings" and need to talk to one another.
I think you won't be able to limit which components see the event, but you can limit which ones respond to it. If I understand correctly your "pitcher" and "receiver" are independent components ...
The best place to get more info on this is the study guide for each of these exams .
The course recommended for App Builder is the same course that was needed for developer exam before .Remember that 401 is not the exam name and it was a course name .
Both the exams focus on the declarative features of the platform .The best place to get what ...
An equivalent to force:navigateToComponent will be released GA as a public API, it's under the category of "Global Components" that is scheduled for this coming release "Winter 17":
We appear to be on track to release "Global Components" around 25 lightning components, interfaces, and ...
SVG support along with document.createElementNS() is coming very soon - already in a scheduled patch branch. I'll double check on the release date but I believe it deploys tommorow night. We've filled in many other gaps in the secure virtual DOM API with more on the way in following patches. Please pardon our dust as we get this dialed in over the next few ...
Although the documentation for VisualEditor.DataRow specifies a generic Object as the value parameter, for it to show on the editor you should transform what you've got into a String.
For example, in:
return new VisualEditor.DataRow(
String.valueOf(standardPricebook.Id) // notice the conversion to String
First, as we all are hopefully aware, the Lightning framework itself is still evolving and isn't completely ...
you're right that this isn't supported yet, and there's no public scheduled roadmap for this (2016-12-29). That said, the use case is clear and obviously useful to a lot of people.
If you've seen John Belo's Advanced Lightning Apps webinar he suggests a pattern that might help you though.
Here's what I would do. I acknowledge that this is not the same as ...
Instead of a visualforce page, use a lightning component that implements="flexipage:availableForAllPageTypes", so it is available on the App Builder. For example:
<aura:component implements="flexipage:availableForAllPageTypes" access="global" >
<img src="http://www.vectortemplates.com/raster/batman/batman-logo-big.gif" width="150"/>
The main difference is that Lightning Apps are outside the main Lightning Experience (LEX) that is Salesforce. Think of them as standalone Visualforce pages. They are used to create a custom Lightning experience that doesn't have the LEX UI.
Lightning App Builder (LAB) is a graphical interface that allows you to compose apps using any number of standard and ...
No, there's no specific interface or event that specifies that you're in preview mode. What you need to do will depend on circumstances. For example, if you're using force:hasRecordId, you might decide to show dummy data if recordId is null. The documentation also states:
Give your required attributes default values. When a component that has required ...
No, you can't modify the DOM outside of your own component. You'd want to write your own component that has both of the other components inside of it so you can control the layout, and place it in section 1 on the layout.
I've got some feedback from Salesforce:
As we all guessed right, this feature is not available yet. (At least in Winter'17 release)
It seems to be on the roadmap to support custom "container" components similar to the Tabs component that allow you to nest components. The standard Tabs component is currently the only option now.
I was not able to find ...
With Winter 18 there are now a couple of features that could cover some of your use cases:
You can now create your own Custom Page
Templates. Custom Page Templates are essentially Lightning
Components with some additional metadata, so you could for example
implement regions that are collapsible.
With the Dynamic Lightning Pages feature, you can define ...
You can implement multiple intefaces for your lightning component and that should allow you to use Single component built everywhere (except for lightning out which requires another app to declare dependencies ).
Here is what I have been doing to use components across everything .
In DESIGN component of lightning component bundle (you can press Ctrl + Shift + 7)
add the label attribute like
<design:component label="Some Another Label">
For custom icon, you need to add the svg code in SVG component (Ctrl + Shift + 8), like one sample which you can copy-paste and try:
<?xml version="1.0" encoding="...
Alright this was actually a pretty simple fix.
Lightning Component fix:
changed the aura:component tag to
VisualForce page fix:
Checked Available for Salesforce mobile apps and Lightning Pages on the VF page.
As mentioned in the other answer, there are different marker interfaces your component must implement for the component to be available in different places of the platform. Some of them are:
force:appHostable for the component to be used as a Lightning
Component Tab in Salesforce1
the component to be available on ...
As you may be aware, In 2015 Salesforce had introduced newer certifications for Developer and Advanced Developers, which now is App builder and Platform Developer 1 & 2.
Quote from Salesforce university:
Our Force.com credentials will begin retiring in July of 2017, so choose the best transition option for you. The retirement process for these ...
I hereby attached the code-Snippet for your reference.
After you created the component:
Go to AppBuilder --> Select HomePage --> The Custom Component that you have created is listed on --> then select that.
<aura:component implements="lightning:homeTemplate" access="global" >
<aura:attribute name="dashboard" type="Aura.Component[...
As per Salesforce docs:
Use a design resource to control which attributes are exposed to
builder tools like the Lightning App Builder, Community Builder, or
Cloud Flow Designer.
So this the main purpose of tool to allow basic customization from end user perspective.
So you can either use aura:attribute but you can't make design:attribute readonly ...
From the documentation for design:attribute, looks like what you are looking for is not supported at the time being.
For Lightning page interfaces, the design resource supports only attributes of type Integer, String, or Boolean.
More details on the documentation here.
There is an elegant solution to filter related lists declaratively. It's written up in full by Doug Ayers, but to summarize, it goes like this.
For each filtered category of Case you want to have, create a new lookup field on Case pointing to Account. Give each one an appropriate related list name, for example, Account_Closed__c, "Cases (Closed)".
Build a ...