@Xtremefaith, sorry, I can't add comment below your post.
I like scriptly deployment and always use ant to deploy, generally, I will use eclipse to build my package.xml
and deploy it by SublimeApex
, however, building the package.xml
by UI is very slowly, sometimes, I just want to deploy lots of components and I can directly write the package.xml
without UI, therefore, in order to improve the efficiency on writing my package.xml
, I made lots of improvement work on how to build package.xml more quickly.
If you are familiar with ant deployment, I think below demo is very helpful for you.
I have posted demo to show how to deploy custom fields or something else by SublimeApex, this demo file is more than 19.5M, when you are opening it, please be patiently.
While this method of copying it directly into production does technically work, it's generally a good idea to deploy it through a change set or another dev tool (Mavens Mate, Eclipse, IDE, Ant, etc.). The advantage of doing this is that all of your test code is run with the new validation rule, so you can see if the new validation rule causes any test failures in your production environment.
Let's say for instance, you have a trigger on your opportunity object that creates a new case if a certain attribute is set. This trigger passes your test code and works well in your production environment. Lets now assume you have a new Validation Rule on the case object that requires a certain combination of fields. Your Opportunity trigger that is creating this case does not set these fields so your trigger will now fail due to this validation rule. If you simply copy and pasted this rule into production, you will now start to have trigger failures on your opportunity object and you may not know why. This is particular important when you have multiple people maintaining an org. So for instance, you as the admin, created this VR, and the developer who maintains the trigger, had no idea.
If you had used a change set to migrate the VR, then your test code would have failed (assuming you have proper test code in place). Then you would know there was an issue with the trigger prior to it being in production and you can work on the trigger to work well with the validation rule.
So in short, will pasting it work, technically, yes. Is it a good practice, no.
I hope this helps.
Best Answer
Finally got the right way!, same certificates can be installed across sandboxes with the the below steps: On the source sandbox
will get downloaded to local system
On target sandbox