Vista Digital Platform - Tenant Addons Overview

Introduction

The Tenant Addons allows customisations to be applied to a customer's Vista Digital Platform (previous names "SASS Connect", "Cloud Connect", "Thunderbird Connect").

For Vista Classic (on-premise) deployments, customisations were applied manually by remoting into a server to change files or running scripts directly against the VISTAIT database. With Vista Digital Platform, this level of access is not possible, so instead customisations are applied using the Tenant Addons.

Customisations can include:

• payment connector and their settings
• system settings
• site settings
• connect clients
  • tokens
  • custom permissions
• email templates

Process Summary

1. Create Services site ticket.
2. Branch the Tenant Addon repo.
3. Commit changes (to appropriate environment sub folder)​.
4. Create Pull Request​ (PR) for peer review of changes in Step 3.
   • Wait for PR approval.
5. Add new Version Tag​.
6. Create Cloud Ops Change Request (CR) for an Octopus redeploy (on Services site ticket from Step 1).
   • Get CR approved by your manager.
7. Update Tenants ‘Tenant Addons Nuget Package Version’ variable (in Octopus).
8. Re-deploy (current version of) Tenants release (in Octopus).
   • Confirm changes were successfully applied.
9. Repeat steps 3-8 for each environment, e.g. Sandbox then Live

For details of this process, refer to the 'VDP Customisations AKA Tenant Addon Process SOP' document.

Links

• Onboarding third-parties to Vista Digital Platform (VDP)
• VDP Customisations AKA Tenant Addon Process SOP
• Link to Tenant Addon repos
• Engineering docs on Vista Cloud Tenant Addons