|
(→Appendix A: Key Files)
|
(Appended info on import/export)
|
| Line 159: | |||
| = Appendix B: Note on Import/Export Method = | = Appendix B: Note on Import/Export Method = | ||
| + | A lot of customers mistakenly use the import/export option of anthillpro to make "full backups" of their projects, library jobs, etc. While this may seem like a good idea, the fidelity & integrity of projects most likely will become compromised. Therefore it is recommended to do a database backup/clone if trying to copy projects to a new server. Exporting and importing projects is not meant for moving projects around from one server to another. It was included in AnthillPro primarily for debugging off of the production server, mainly for our needs in checking out customer project configurations etc. | ||
| + | = Fidelity/Integrity = | ||
| + | Examples of losses in fidelity and corruption in integrity include ('''''but are not limited to'''''): | ||
| + | * '''Assign Status''' Steps | ||
| + | ** Steps are blanked out upon import; need reset | ||
| + | * '''Life Cycle Model''' Creation | ||
| + | ** If a Life Cycle Model already exists with this name, the exported project's Life Cycle Model information will not be imported | ||
| + | * '''Populate Workspace''' Steps | ||
| + | ** Some newer versions of anthillpro have been known to blank the workspace script upon import of projects that contain a Populate Workspace step | ||
| + | * '''Run Another Workflow''' Steps | ||
| + | ** Steps are blanked out upon import; need reset | ||
| + | * '''Statuses''' Within Life Cycle Model | ||
| + | ** If a status already exists with this name in a Life Cycle Model, the exported project's statuses within its Life Cycle Model information will not be imported | ||
