Continuing on from Part 1, where we defined a data structure to hold our recommendation junction objects, this part will focus on the state management required for the UI.
Salesforce provides a means to configure business hours and holidays in the system. Admin can setup business hours for their company by simply navigating to Setup -> Company Profile -> Business Hours. The business hour configuration ensures that the system is aware of the working hours and accordingly computes target date (such as SLA of cases) and helps you to provide the correct support to your customer.
Yesterday I was having a discussion with one of my colleague over parameter passing techniques in apex programming. He was pretty sure that primitives in apex are passed by values, whereas non-primitive data types are passed by reference. Well, this statement is partially correct.
While Salesforce provides a comprehensive access control framework for objects and field access, sometimes we need to lock down access to certain objects completely, while allowing certain users to access and modify certain fields in certain records of such objects. This could either be because of restrictive business rules or because of the license types your users have. This post explores some intricacies of programmatically allowing users to access and work with such private objects.
Our team's thoughts and insights on all things Salesforce