The Maica Release Process
Learn about Maica's Software Release and Upgrade Process
Last updated
Was this helpful?
Learn about Maica's Software Release and Upgrade Process
Last updated
Was this helpful?
When Maica issues a new solution version, a number of artefacts will be published alongside any release, including the following:
We showcase most of Maica's features on our website through a number of that allow you to experience Maica with ease. When a new release is about to be published, we will add any relevant feature videos to so please visit to find out what's new.
Our is the main tool for you to understand how Maica works, both from an end-user and administration perspective. We will update any relevant articles or add new ones to reflect all new features or improvements in Maica to make sure you have access to the on how it works.
Release Notes are an essential part of any Maica release and we will publish these on our as a and downloadable PDF. This will include all required post-installation steps and scripts in case you want to upgrade Maica yourself.
We have a on which we publish almost daily, so please check in for the latest information, updates, and release information. We will post all new releases for your ease of access.
If you are a current Maica client, you will be on our broadcast list so you will receive a special type of broadcast to announce a new release. This will then also includes links to all of the above for your convenience. Look out for these!
The Maica software release and upgrade process is outlined below to ensure clarity across the various tasks and responsibilites that take place during this timeline.
Maica will release a package to its clients only if all of the below have been tested and published:
Software Package
the technical package which will be installed using a URL
Release Notes
Post-Installation Steps
these are usually steps that need to be taken to configure any additional elements that the automated installation process does not address
The next stages look at client-specific customisation that might have been configured by an implementation partner to ensure compatibility with these unique structures. This will involve the following steps/tasks:
The implementation partner will investigate and determine any client-specific post-installation steps or scripts that need to be run. This might involved additional development work to ensure compatibility going forward.
Once this has been completed (via DocuSign), the relevant team members from the implementation partner and the client are allocated to the Maica upgrade project with the following artefacts to be part of the upgrade:
Upgrade Timeline
Upgrade Team Members
Client-specific technical scripts (to be run in the client's Salesforce production instance)
these can be found for reference and will contain a detailed description of all features/bugs fixes/etc introduced as part of any given release
The client is then asked to complete the in which we seek proof that all relevant testing was completed in a reppresentative sandbox to ensure the upgrade will be successful.
to be issued following the upgrade project completion.