Publishing

When editing a component you can:

• create multiple versions of the component.

• for each version you can manage the Availability in the various environments (DEVELOP, STAGING, PRODUCTION) you have access.

By combining versions and availability, you can follow these steps to publish your components to a PRODUCTION environment.

1. We suggest you to develop your component by using a draft version installed on a DEVELOP environment.
   In this way you can easily debug your code without affecting any production environment.

2. When you complete the development, you can promote the draft version to a public version:
   
   
   

   1. You should promote the draft version to the existing one in case you are making bug fixing or minor update improvements.

   2. In case you are introducing new features with a big impact to your source code or DPS user experience, you should promote the draft to a new version.
      This will allow you to have more control over your code and possibly roll it back to a previous version, if needed.
      

3. In case you have created a new version (e.g. v2), within the Availability page you can define in which environments the new version will be available.

   You should start with STAGING and then PRODUCTION.

4. When you change the availability, the component must be manually installed, and you have to go to the Components page of the environment.

   If the component was already installed, you will find an update, so click the Update button, else the component must be activated.
   
   
   

5. Navigate the DPS where the component version is installed or updated, and check that everything is working fine.

   1. If STAGING, repeat steps 3 and 4 for the PRODUCTION environment.