The Maica Release Process

Learn about Maica's Software Release and Upgrade Process

All Maica releases are published on our website here. It is our aim to release new versions of Maica every quarter depending on complexity of new features and other factors that may impact on this timeline.

The Maica Release Process

When Maica issues a new solution version, a number of artefacts will be published alongside any release, including the following:

Interactive Feature videos

We showcase most of Maica's features on our website through a number of interactive videos 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 this site so please visit to find out what's new.

Knowledge Base articles

Our Knowledge Base 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 latest information on how it works.

Release Notes

Release Notes are an essential part of any Maica release and we will publish these on our website as a page and downloadable PDF. This will include all required post-installation steps and scripts in case you want to upgrade Maica yourself.

LinkedIn Post

We have a Maica LinkedIn profile on which we publish almost daily, so please check in for the latest information, updates, and release information. We will post all new releases here for your ease of access.

Broadcast Email

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 Upgrade Process

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.

1. Maica will release a package to its clients only if all of the below have been tested and published:

   1. Software Package

      1. the technical package which will be installed using a URL

   2. Release Notes

      1. these can be found here for reference and will contain a detailed description of all features/bugs fixes/etc introduced as part of any given release

   3. Post-Installation Steps

      1. these are usually steps that need to be taken to configure any additional elements that the automated installation process does not address

It is important to note that the above will only ever be applicable to the core package. In other words, these steps will ensure compatibility with the native Maica package only and any client-specific customisations will be looked at as part of the next stages of the upgrade process.

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:

1. 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.

2. The client is then asked to complete the Maica Upgrade Agreement in which we seek proof that all relevant testing was completed in a reppresentative sandbox to ensure the upgrade will be successful.

3. 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:

   1. Upgrade Timeline

   2. Upgrade Team Members

   3. Client-specific technical scripts (to be run in the client's Salesforce production instance)

   4. Acceptance Certificate to be issued following the upgrade project completion.

Once an upgrade is completed, Maica takes responsibility for any resulting application defects and will address these as the highest priority but will not be responsible for any resulting data integrity issues nor any customisations not implemented directly by the implementation partner that might impact the performance of Maica in the client’s environment.