With Winter ‘16, Salesforce introduced Lightning Experience. To provide a more streamlined user experience, you can now use Lightning Components and the Lightning Design System, as well as Visualforce. Using these tools you can create components that are reusable across applications and devices. These new options created an opportunity for customers and partners alike to […]
16 years, 48 product releases, thousands of features, millions of happy users — it's been an incredible journey here at Salesforce. Together with our partners, we've changed business for the better and brought innovation to life.
In our previous blog post, we discussed the fundamentals of the Trialforce technology and its components. If you followed along, you set up your trial infrastructure and ultimately generated your trial template. Now what?
In part one of this series, we covered how to leverage some of the settings from the user’s profile in Salesforce to control the locale settings in angularJS. In part two, we extended that example to include Time Zones and looked at other options for displaying data in the logged in user’s time zone. In this post, we will again leverage the profile settings of the logged in user to display the page content (titles, descriptions, etc. – not data contained in Salesforce objects) in the language selected by the user. We cover two options in this post: how to do the language conversion in angular and how to do it using the Salesforce translation workbench. The POC code leverages the second approach.
In part one of this series, we covered how to leverage some of the settings from the user’s profile in Salesforce to control the locale settings in angularJS. In this post, we will build off that initial example and extend it to cover time zone conversions. This will enable us to see all the data presented to the logged in user in that user’s time zone. This example could be further extended to allow the logged in user to see the data presented in another user’s time zone. An example of this is if an activity, task, or event needs to be assigned to a user in a different time zone, it is created in their time zone, not the time zone of who has created the activity. As long as the correct time zone is pulled from their profile, the new task is created in their time zone using the techniques outlined below.