When you receive the email, login to Production to deploy it. You will receive an email notifying you when it is ready for deployment. Now grab a coffee because this can take 5-10 mins before it arrives in Production, ready to deploy. Now your flow is on its way to Production. Select the environment we want to upload it to, in this example, we only have one choice: Now you have added your flow, it is ready to upload to production: Note: Any new fields you have created are under the Component Type: “Custom Fields”, page layouts are Page Layouts, Lightning Record Pages are Lightning Pages etc. If you have other components you need to include in this Change Set, add more before proceeding. Note: If your flow is not visible here, go back and check that you have made it active. Select your flow and Add to the Change Set. Select the profiles and add them to the Change Set.įrom the Component Type drop-down list, select Flow Definition: If you are not 100% sure, add ALL profiles, it won’t do any harm if they are not needed, they will not be included in the Change Set. ![]() If you created a new field then the Field Level Security permissions for this new field will need to be included for the relevant profiles. ![]() Give it a name and a useful description of what it contains.īefore you get too excited and forget about any profiles that may need to be updated with this Change Set, add all the profiles that may be impacted. Setup -> Change Sets -> Outbound Change Sets Login to the sandbox to create the Change Set. Make sure your flow is activated and you have thoroughly tested it. Now we have the connection between production and the sandbox, we are ready to prepare our Change Set. There are times when you may want to go both ways – for example it is usually acceptable to develop new reports in production (depends on your company policy) so if you want to have a copy of these reports back in your sandbox, you can use a Change Set to copy these back. You can send Change Sets from your sandbox to production but not the other way around. Go back to the Deployment Settings and you will now see the connection with the green arrow pointing from your sandbox to your production environment, indicating you have a one-way connection. Starting from your production environment, select setup -> Deploy – Deployment settings.Ĭheck the box to “Allow Inbound Changes”. Setup a connection between your sandbox and production Setup a connection between your sandbox and production.Note: You can’t use changesets in a developer org or a trailhead playground as they do not have a connection to a production org. Perhaps you defined some extra custom fields and some page layouts to go with your flow, these can be included in your Change Set too. You can use other paid tools like Gearset and Copado to do the same but if you don’t have these tools then Change Sets will do what you need.Ī Change Set is a package of configuration (metadata) that contains your flow and anything else needed to deploy your new flow into another environment. It’s not until they are all working and tested that you should consider moving them to your production (work environment where you users are using Salesforce on a day-to-day basis).īut how do you move the flow once testing is complete? Using Change Sets is one easy and free option. When developing and testing your new flows, the best practice is to do this in a sandbox (eg a developer sandbox) where it is safe to make mistakes and break things.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |