Forum Replies Created

Viewing 101 - 110 of 110 posts
  • Piyush

    Member
    April 27, 2016 at 10:49 am

    Thanks Suyash..

    • This reply was modified 5 years, 9 months ago by  Piyush.
  • Piyush

    Member
    April 27, 2016 at 8:37 am

    Thanks.

  • Piyush

    Member
    April 26, 2016 at 4:09 pm

    Thanks Shafali it really helpful.

  • Piyush

    Member
    April 26, 2016 at 11:39 am
  • Piyush

    Member
    April 26, 2016 at 8:07 am
  • Piyush

    Member
    April 26, 2016 at 6:04 am

    Hi ,

    You can specify when logging the case whether the issue is in production or sandbox, but I do not think it is possible to log a case without having a production login.

    Thanks.

  • Piyush

    Member
    April 25, 2016 at 11:10 am

    Hello Danna,

    Here is the code from my test app. My use case was in context of the Accounts and contacts but it should apply to any object. As far as my understanding when ever an object is saved then the current view is refreshed. This is visible by the spinner that is displayed over the top panel of the object. I added a handler to my component that uses the force:refreshView (https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/ref_force_refreshView.htm) and just recalled my init method but could call another method if need be. This basically ensured that any time the object that was hosting the component was refreshed that my component would also refresh as well.

    Here is the Component Code:

    <aura:component controller="editRecordSimulationController"
    implements="force:appHostable,flexipage:availableForAllPageTypes,force:hasRecordId,force:hasSObjectName">
    <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
    <aura:dependency resource="markup://force:editRecord" type="EVENT" />
    <aura:handler event="force:refreshView" action="{!c.doInit}" />
    <aura:attribute name="recordId" type="string" />
    <aura:attribute name="accType" type="String" />
    <aura:attribute name="accObj" type="account" default="{ sObjectType: 'Account'}"/>
    <ui:inputText label="Record Id" value="{!v.recordId}" required="true"/>
    <ui:button class="btn" label="Submit" press="{!c.setOutput}"/>

    <br />
    <br />
    <br />
    Account Type: <ui:outputText value="{!v.accObj.Type}" />
    </aura:component>

    Here is my Controller Code:

    ({
    doInit : function(component, event, helper) {
    var recordId = component.get("v.recordId");
    var action = component.get("c.getTypeFromAccount");
    action.setParams({
    recordId: recordId
    });
    action.setCallback(this, function(response){
    var state = response.getState();
    if (state === "SUCCESS") {
    var acc = response.getReturnValue();
    component.set("v.accType", acc.Type);
    component.set("v.accObj", acc)
    }
    });

    $A.enqueueAction(action);
    },
    setOutput : function(component, event, helper) {
    var editRecordEvent = $A.get("e.force:editRecord");
    editRecordEvent.setParams({
    "recordId": component.get("v.recordId")
    });
    editRecordEvent.fire();
    }
    })

    Here it the APEX controller code:

    public class editRecordSimulationController {

    @AuraEnabled
    public static Account getTypeFromAccount(string recordId)
    {
    Account acc = [select Name, Type from Account Where Id = :recordId limit 1];
    return acc;
    }
    }

  • Piyush

    Member
    April 25, 2016 at 11:06 am

    Hello Hazel,

    This is a standard Salesforce functionality currently we can not disable the Opening Sequence. When you move from classic interface to lightning Experience then in the background lightning interface is loaded and  you have to watch the butterfly flap it's wings on your window.

  • Piyush

    Member
    April 25, 2016 at 10:47 am

    Hello Danna,
    I don't think you will need to worry about Canvas App being embedded in your Visualforce for passing through lightning ready certification for your application. Since canvas app is essentially a mashup with external system, you don't have to match CSS with lightning design system.

    For lightning Ready Certification, here are key things SFDC looks in your application:

    1. Use SLDS Design Systems for CSS in your Visualforce. This is mandatory. With Bootstrap I doubt you will be able to certify your app to lightning ready. There is significant difference in both Frameworks. SLDS uses SVGs for icons.
    2. Test for supported browsers. (IE, Firefox, Chrome, Safari)
    3. Make sure your app is responsive and at a viewport minimum of 1024px wide and a maximum of 1920px wide. Make sure that your app responds elegantly when the left-hand nav opens and closes.
    4. Do use the new Salesforce Sans typeface. It should not be accompanied by any other typeface, with the exception of your logotype.
    5. Try to Align with Basic Page Layouts like salesforce Edit, List view and Detail View on Lightning experience.

    In short your App should be functional in Lightning Experience and the CSS should match as closely as possible to Lightning Experience.

    • This reply was modified 5 years, 9 months ago by  Piyush.
  • Piyush

    Member
    April 25, 2016 at 10:42 am

    Hello Hazel ,

    Follow this link for deploying lightning Component and pages from Sandbox to Prod.

    https://blogs.perficient.com/salesforce/2015/12/22/deploy-community-builder-templates-in-3-simple-steps/

     

Viewing 101 - 110 of 110 posts