Manual post-deployment tasks in production for an Agentforce Health use case
Key Takeaway
After a production release, finish the post-deployment tasks by hand, such as assigning permission sets, before users can use the new feature.
A deployment to a production org doesn't finish the setup, because some steps still have to be done by hand in that org. Teams list these manual steps in a deployment run list and complete them after the release. For an Agentforce Health use case, these steps can include giving users the right permission set licenses and permission sets, and placing components such as Action Launcher on record pages.
How to work through a deployment run list
- Before the release, check the deployment run list for pre-deployment tasks.
- Release the changes to production.
- After the production release, go back to the list and do the post-deployment tasks in the production org.
- After the post-deployment tasks are done, run a quick sanity check in production by using the feature the way a user would.
User access is a typical post-deployment task.
A team deploys a custom object and a custom field for tracking home visit requests. The object is now in production, but the care team can't view it yet. The run list has a post-deployment task for the care team's profile. The admin edits that profile in Setup and gives Read access to the object and field, so the care team can now view them. For the sanity check, the admin creates a home visit request that should send a notification and confirms the email arrives.