Overview
The articles below are for new subscribers who are preparing to use a new module or feature. Each page contains information specifically related to enabling the module or feature and preparing it for use. These resources contain:
- what we need from you before Emersion can proceed with enabling the module or feature
- any lead times that are to be expected outside the norm or outside Emersion's control.
These resources also provide guidance on what you need to do once you are notified by Emersion that the module or feature is enabled. Included are:
- the acceptance testing requirements
- configuration instructions
- links to relevant user help content.
Enabling vs Configuring vs Customisation
Enabling a module is a task undertaken by Emersion's onboarding staff. It may comprise single or multiple phases, but most require a level of information gathering. After this process is complete, service providers receive notification that the module is available to your service provider account and ready for configuration or customisation.
Configuring a module is a task that in some cases, Emersion staff must do and in other cases, the service provider must.
- When Emersion staff need to perform some configuration for a module. it will be because there is no option for service providers to perform this task themselves.
- If the service provider needs to configure a module this usually means choosing what settings to use, or defining preferences and options.
Customising a module is a task undertaken by the service provider.
These tasks should be done by Cumulus users with Administrative (full power) access.
Notice of Completion
Once Emersion have finished enabling the module or feature, we will send a Notice Of Completion via the project ticket.
Acceptance Testing
All service providers are required to undertake an acceptance test for all modules and features within seven (7) days from the date of the Notice of Completion and provide Emersion with one of the following:
- Acceptance Notice - a notice that the module or feature passes the acceptance.
- Non-Acceptance Notice - a notice that the module or feature does not pass the acceptance test.
Any non-acceptance notice must include sufficient information to enable Emersion to remedy the issue. Emersion will remediate any issues at no further cost to you. Non-Acceptance Notices received after the conclusion of the acceptance testing period will result in a quote being provided for any remediation activity.
Improvement suggestions, enhancements and requests for additional functionality not already provided in the module are not included in any remediation work arising from a Non-Acceptance Notice.
Implied Acceptance
Where a notice is not supplied, or a non-compliant notice is supplied within seven days from the date of the Notice of Completion, the module or feature will be deemed to have been successfully completed and delivered by Emersion.
Submitting a Notice
Acceptance Notice and Non-Acceptance Notice must be supplied in writing and sent via the correct work request (PRO) ticket.
Acceptance Notices and Non-Acceptance Notices sent outside the ticket system are not compliant. If you are not sure which ticket to update, please call our office for assistance.