Understanding Why and When to Update Skedulo Packages
Get a high level overview around package updates
Overview
Package updates are critical to maintaining a secure, stable, and fully featured Skedulo for Healthcare deployment. This guide explains the importance of keeping packages up to date, and how to determine the right time to update.
Why Update?
Updating Skedulo-managed packages ensures your org:
- Has access to the latest features and product enhancements
- Receives security patches and bug fixes
- Remains compatible with Skedulo platform and Salesforce updates
- Benefits from improved performance and stability
When to Update
Skedulo recommends the following update cadence and triggers:
| Scenario | Action |
| Monthly review | Check for available updates and release notes |
| Prior to go-live | Ensure Production has the latest approved version |
| When notified of a new release | Review and plan Sandbox testing |
| Skipping multiple versions | Review all intermediate release notes carefully |
| Troubleshooting issues | Check if a newer package resolves known problems |
Best Practices
- Always test in Sandbox first to validate stability and compatibility.
- Use custom permission sets rather than editing packaged ones, which can be overwritten.
- Track updates using an internal log or changelog.
Where to find release notes
All release notes can be found by heading to https://www.skedulo.com/release-notes/. On the right hand side, you use the filters to select the packages that are relevant to you and your organisation.
When viewing a release note article, click the ‘Learn More’ button to view the full release notes and access the installation links found at the bottom of the page.