Which state you should pass processes using XOG.

Document ID : KB000029173
Last Modified Date : 14/02/2018
Show Technical Document Details


Which is the state that you will able to pass processes using XOG?



CA PPM has designed to pass processes with XOG under 'on Draft' mode, in order to prevent possible damages when you pass the information between environments.

If you pass processes in 'Active' or 'On Hold' Mode the most likely that the user never check if the XOG is properly configured.

The processes with 'on Draft' mode state allow you to update XOG before to run it, so if you want to run it, you must change the state first.

Since that the user have one more instance to check if the XOG is properly configured and it could be prevent Errors on the system.



1-If you have attributes in development environment and in production there aren't (or vice versa).

When you use the write XOG on the system that you want to populate, the system will generates error referencing that there is one or more attributes that they don't exist.

2-One of the process are doing an update over a specific's ID or conditions, which in the other environment are different.

This could be generate a data incongruity and many system failures, project with different resources, task with wrong time estimates, finance giving incorrect data, Etc.


So the best practice and the only way to pass processes under XOG is 'on Draft' mode, this mode is the only which you can edit the process.


Additional Information:  

This information Applies to all CA PPM Versions.

For more details About XOG check