Skip to main content

Salesforce1 Simulator for Google Chrome

Salesforce 1 Simulator for Google Chrome 

 Salesforce 1 Simulator allows you to view and test drive your SF1 Apps using different devices.

 Make sure you have Google chrome installed before following the next steps.

 http://www.google.com/chrome/ 

 And you should have a Salesforce Account with Salesforce 1 access properly configured.

 http://www.salesforce.com/salesforce1/rolloutguide/gettingstarted.jsp

 Step 1  - Download the Salesforce1 Simulator :

 Go to this link and install the simulator

 https://chrome.google.com/webstore/detail/salesforce1-simulator/cknbjckicenodbiaejbmkjhldffonggp



Step 2  - Open Salesforce 1 Simulator from Google Chrome apps.



  • Click the Apps icon In the bookmarks bar. If you don't see the Apps icon, right-click the bookmarks bar and click Show Apps Shortcut.



  • Click the Salesforce 1 app to open it.

    •


    Step 3  - Connect to your org with your credentials.



    Step 4  - Test your Apps.

     Once you log in you can access all your SF1 mobile apps right from your browser.


    If you have a touch monitor in your PC you will be able to test the touch events like swipe from to left in a list view.




    Use the button on the center to switch devices.

    Table view:






    Comments

    Post a Comment

    Popular posts from this blog

    Salesforce ListView as a Home Page component.

    Display ListView as a Home Page component. In this show an example to use the a pex:enhancedList  VisualForce component in order to display a ListView in a VisualForce Page, and then embed this as a Home Page component. The final result should be something like this: Step 1: Create a ListView I suggest doing this with a ListView, as we left the control of which records list will be filtered to Administrators or End users. First step its to create a list view with the data that you want to show: Step 2: Create a VisualForce Page  Go to  Setup -> Build --> Develop --> Pages --> New. And create a new Page with this sniped of code: The page is using an  enhancedList Visualforce Component, for more details about this component here is the documentation: http://www.salesforce.com/us/developer/docs/pages/index_Left.htm#CSHID=pages_compref_composition.htm|StartTopic=Content%2Fpages_compref_composition.htm|SkinName=webhelp   The par
    3 comments
    Read more

    How to ByPass and Apex Triggers and Avoid Loops

    How to ByPass and Apex Triggers and Avoid Loops Sometimes, when developing a trigger from some reasons we need to by pass the a trigger, may, as I mentioned in my previous post " System.LimitException: Too many SOQL queries: 101 ", sometimes we have loops in our triggers logic.  In Other occasions we just want to bypass because records were processed previously. Our first approach for bypassing its to execute an SOQL query to see if record need to be processed or use fields in the object. trigger TriggerTest on User (before insert. before update) { //First go to Database Set ids = Trigger.newMap.keySet(); List relatedObjs = [SELECT Id,Name FROM relatedObject__c WHERE parent__c in :ids]; //Here check which users need to be processed. List UsersToProcess = new List (); for(User usr: Trigger.new){ //Use the values on relatedObjs to validate UsersToProcess.add(usr); } //Process the records if(UsersToProcess.size() > 0){
    Post a Comment
    Read more

    Dynamic Section on a VisualForce Page

    This will be an small example to show how to create dynamic content inside a Visual Force Page, particularly in a table. Additionally the idea that I wan to introduce here its the use of a Wrapper Class , This class will help us to control the User Interface behavior without having the need to have a new field (Persistent data) back into the database. This we we can "Wrap" the database information into another object, use it in the Interface and them just save back the important information. Something important to consider when using a wrapper class, its there is not automatic field type binding in the VisualForce page to not persistent objects, therefore we need to use fields like "<apex:inputText  /> " Instead of  <apex:inputField /> and validate the format of the data that we collect from the view. The requirements: Have a table that show basic account information. When the checkbook "Configure SLA" its selected allow user to chang
    Post a Comment
    Read more