Skip navigation
Toggle Sidebar

Process Deployment History

The table on the Deployments tab displays the history of all of the deployed versions of the selected Process. When you deploy a Process you are effectively taking a snapshot of the Process and all of its dependent components. Each component (Connections, maps, profiles, etc.) used in the Process, and the Process itself, has a component revision number. Each time you click the Deploy Latest Revision of Process button, you are taking the latest revisions of the Process and its components and you are creating and deploying a new version.

For more information on revision history, see Creating and Editing Components

Process Deployment History Table

In the Process Deployment History table there is an Actions icon next to each version. Clicking the version's icon allows you to perform the following actions.

Action Description
Re-deploy this Version Re-deploys the previously deployed Process version as the current version.
Compare Deployment Used to compare a deployed Process version with another version or a version in another Environment.
Copy Deployment (Available only when Environments are enabled.) Copies the deployed Process version to another Environment attached to the Process.
View Component Deployments Shows all components in the deployed Process and their current revision number.


Re-Deploying a Version

Re-deploying a version allows you to deploy an older configuration to an Atom or Environment. This can be used to effectively "roll back" a deployed version that has problems. For example, if you deployed an enhancement that broke a Process, you could quickly re-deploy the previous version to get it running again while you troubleshoot the problem using Test mode.

Re-deploying a previous version lets the Atom use the previous configuration but it does not roll back the current component configuration as you see it on the Build menu. You must perform this step through the component's Revision History. For example, if you deployed a series of mapping changes and then later re-deployed a previous version, the Atom would run without the mapping changes. However, when you edit the map on the Build menu, the changes would still be there.

  • You cannot delete a deployed version. You can negate it only by deploying a new version or re-deploying a previous version.
  • Re-deploying a previous version creates a newly deployed version. For example, if the current deployment is version 5 and you re-deploy version 4, a new version 6 will be created with the same component revisions as were in version 4. The original version is automatically captured in the Notes column.
  • You can re-deploy one of the last 10 deployed versions.

To Re-Deploy a Process Version

  1. On the Deploy menu, select a Process from the Processes list.
    The Process Deployment History list appears on the Deployments tab.
  2. Click the Actions icon next to the version that you want to re-deploy and select Re-Deploy This Version ( ) from the drop-down.
    The Deployment Confirmation dialog opens.
  3. (Optional) Type notes about the re-deployment.
  4. Click OK.
    The re-deployed version appears in the Process Deployment History list with information in the Notes column about which version was re-deployed.


Comparing Deployments

It is helpful to be able to compare two deployed Process versions to identify which components had been modified, added to or removed from the Process between two deployments. It can also be helpful to see which components have been altered since the most recent deployment, by comparing it to the latest revision that is currently in development.

To Compare Two Process Versions

  1. On the Deploy menu, select a Process from the Processes list.
    The Process Deployment History list appears on the Deployments tab.
  2. Click the Actions icon next to the version that you want to compare and select Compare Deployment ( ) from the drop-down.
    The Compare Process Deployments dialog opens with the selected version in the Selected Version field.
  3. In the Compare To field do one of the following:
    Select Latest Revision of Process.
    (Optional) Select an environment from the list.
    Select Version and select a version number from the list.
  4. Click Next.
    The comparison results are displayed. Note that very large Processes may take longer to display.
    Differences in component revisions are highlighted. In the example below, revision 3 of the MyDiskConnection Connection is used in the selected Deployment Version 9 but revision 2 is used in the compared Deployment Version 7. Revision 18 of the Process is used in the selected Deployment Version 9 but revision 15 is used in the compared Deployment Version 7.
  5. (Optional) To select a different Compare To version, click Back and repeat steps 3 and 4.
  6. Click Cancel.


Viewing Deployed Components

You can see details about all of the components that were used in a deployed Process. The details include the component name, type, revision number, name and e-mail address of the person who modified it and the date and time at which the component was modified.

To View or Edit a Deployed Process' Component Details

  1. On the Deploy menu, select a process from the Processes list.
    The Process Deployment History list appears on the Deployments tab.
  2. Click the Actions icon next to the version that you want to view and select View Component Deployments ( ).
    The Components in this Deployment Version dialog opens.
  3. (Optional) Click the View/Edit icon next to a component.
    The component opens on another web page. If this is not the latest revision of the component, a banner at the top warns you of this.
  4. (Optional) Edit the component and click Save and Close.
    If you save this component the latest revision will be overwritten and will no longer be available.
  5. Click Cancel.


Adaptavist Theme Builder Powered by Atlassian Confluence