Skip to main content
'Push Upgrades' is a nice feature for Creating & Uploading Patches to customers organization easily. However, there is best practices around this suggested by salesforce which is listed on https://help.salesforce.com/HTViewHelpDoc?id=push_patch_best_practices.htm&language=en_US.

 However, apart from above best practices, there could be scenario, where you might have created a new component say trigger or class. Now, when you create a new version of package and push it to customers organization there are highly likely chances that your customer forget to add access of these new component(s) to desired profiles (except system administrator, since they will get access automatically). 

 In case of manually updating package on customer's organization, they get an option where they are asked to who all you want to give access and then admin can make decision.

 Tip - In case you are using 'Push Upgrade' and if new release is going to have new component, please prepare a check list and share with your customers in advance, so that they can plan accordingly.

Comments

Post a Comment

Popular posts from this blog

Mashup Integration in Salesforce

During preparation for TA certification exam, I came across a word Mashup for integration a number of times. I explored about it and below is description:- Mashups, sometimes called “composites,” are hybrid applications created by bringing together several data sources and Web services to create a new application or to add value to an existing application. Behind the scenes, mashups may require different levels of integration, depending on whether the mashed-up data is only meant to be viewed, whether it can be edited, and whether data is actually transferred between systems. There are three types of mashup:- Client Presentation Mashup - In this type of mashup the integration takes place strictly at the visual level. It makes possible to view data from two or more applications in a browser,  without actually moving data between the applications. Example - Google Maps. Client Service Mashup - As mashups evolve, they are becoming more complex and sophisticated. Client...
16 comments
Read more

Make Calls to PageReference.getContent() in Asynchronous Apex - Winter16

You can now make calls to the getContent() and getContentAsPdf() methods of the PageReference class from within asynchronous Apex such as Batch Apex, Schedulable and Queueable classes, and @future methods. This allows you to design much more flexible and scalable services that, for example, render Visualforce pages as PDF files.
5 comments
Read more

Hierarchical Relationship

Recently, I came across one of requirement where client wanted to have a custom lookup field on User object. This lookup will be on User. Based upon certain criteria, value of this field will go to Manager field. They didn't want update of Manager, but on the basis of some business use case. First impression to me was it will be straight forward to create a lookup on user and then in trigger will check for business use case and update Manager field accordingly. However, when I proceed with creating a look on User object, I couldn't find an option ' Lookup Relationship ' on first screen of 'New Custom Field'.  In fact, I saw only available option ' Hierarchical Relationship ' for creating any sort of relationship. I know most of us know about it. But you can't defer on my opinion that we tend to forget these small stuff. Since, on user you can't have any direct relationship, but only user. Salesforce gives you special relationship data t...
6 comments
Read more