Topics on this page

Move product versions across environments

Moving a product version is similar to moving an entire Line of Business (LOB) to a different environment using the configuration export/import feature.

Setting up the environments for the client includes several important tasks:

  • User acceptance testing (UAT) trial/demo site is set up for the client.
  • The client begins their implementation of a LOB on a UAT site.
  • The LOB initially has a single Product Version as Initial Version in Draft status.
  • After the implementation and testing of the configuration, the initial version is published according to the desired effective date.
  • The production site is set up for the client.
  • Export the Product Version from UAT; in this case, there is just one version: Initial Version.
  • Import the Product Version in the production environment.
  • For future rate level changes or fixes, a new version should be created in UAT. Follows the same process for moving it as with the Initial Version.
  • If a change is needed to make in the existing published version, the change first should be made in UAT, tested, and then the same change is made in Production later. Depending on the change, it can cause a premium increase/decrease in midterm endorsements for existing policies.
  • Maintain order of product versions in both environments.

This guide walks through a sample client site and demonstrates how to move product versions across environments. This example client has environments:

  • UAT environment (For example: https://<client name>-uat.britecore.com/)
  • Production environment (For example: https://<client name>-.britecore.com/).

Both sites have the Personal Auto LOB and have all three Product Versions and are expected to be in sync with each other. The requirement is to move Personal Auto Version 4 from the UAT into their Production environment with an effective date of 9/20/2021. To move the latest product version:

  1. Log into the UAT site (For example: https://<client name>-uat.britecore.com/)
  2. In the BriteCore menu, select Lines.
  3. In the Lines of Business list, select the applicable line of business.
  4. On the Line Overview screen, in the Products menu, navigate to and select Personal Auto. Make sure Version 4 is selected in the versions bar.
  5. Map your data to address any changes between the versions. When there is more than one product version, the mapping between versions must be specified for any breaking change; for example, a field that existed in earlier versions got removed in the latest version. The mapping is applied during the transformation process of a risk state when it goes into renewal and its effective date falls to a different version; therefore, mapping must be set up or renewals will fail. In this case, we first need to map the changes before publishing the version since there exists a previous version Version 3. If there are no changes, a message displays stating “No changes that require mapping.”
  6. Update the effective date to the desired one; for our example, 9/20/2021. See Edit a product version.
  7. Publish the Version 4. See Publish a product version.
  8. Select Export Product. You will be taken to the Product Exports page.
  9. Wait for the export to finish, and then a Download link will appear. Select the link and the template will begin downloading to your device. You can also check the export progress from the Django Admin by going to Product Exports. To access the Django Admin panel: 
    1. Login or authenticate via SSO to the desired site. 
    2. Visit the URL, which follows this pattern:<sitename>.britecore.com/lines/django-admin
  10. Log into the Production site (For example: https://<client name>-.britecore.com/).
  11. In the BriteCore menu, select Lines.
  12. Select Import Template and select the file downloaded in Step 9. It may take some time to complete the import depending on the file size. You can also check the import progress from the Django Admin by going to Product Imports.
  13. After the import is done, it is necessary to set the mapping as we did in Step 5. Since we are importing a published version, we can’t access mapping from the UI to set up Version Mapping for the imported version. Do it from the Django Admin panel:
    1. Under Product Mappings, select Add.
    2. Select the desired Product Version.
    3. Copy/paste the mapping from the source environment from where the template was exported.
    4. Select Save.

You have successfully moved product versions across environments.