Process Template Migration

It is good practice to define a migration process for controlling how AgilePoint workflows and process changes to these workflows are promoted to production, since this can affect system performance and reliability. In AgilePoint, a user needs to be authenticated and have permission to 'publish' an AgilePoint process to an AgilePoint Server – e.g.  development, testing, staging, production. Therefore, IT could be the only one enabled to 'publish' (or promote) the changed process to the production server after performing final validation, etc.  It is recommended that the designer publish to the non-production environment using Envision and have IT promote the tested process definition to production using the deploying XML file via AgilePoint Enterprise Manager.  This ensures that the process definition that was tested is exactly what IT promotes to production.