![]() STEP I: Manifest(package.xml) file creation If you already have the manifest file(package.xml), then you can directly get started with the Step III Our deployment process would include following 3 steps We would be considering a scenario here, where we RETRIEVE code base from a Source organization and DEPLOY it to a Target organization using unpackaged manifest file (package.xml) One of the lesser known deployment methodology which can come handy in case of absence of all the client utilities is deployment through Salesforce Workbench ![]() Some of the examples are Eclipse, ANT migration / Jenkins tools. Salesforce does provide multiple ways for deploying your code base/metadata from one org to another. ![]() ![]() Also it is assumed that the end-user does have ADMIN rights on both the Source and the Target org. Note: This post is targeted for a generally rare scenario where the deployment operations team/ individual does not have Client IDEs like Eclipse or utilities like ANT migration / Jenkins tool (which do require ANT/JDK setup on the system and henceforth mentioned as CLIENT UTILITIES in the blog) for deployment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |