Performance impact of DOCU tabs on XML export/import

Discussion created by Michael_Lowry on Jan 23, 2018
Latest reply on Jan 23, 2018 by Pete Wirfs
We use an [DEAD LINK https://community.automic.com/discussion/comment/31392/#Comment_31392]automated system to deploy batches of AE objects from one environment to another. Users are not permitted to make changes in the TEST or PROD environment, but must instead edit the batch in DEV and then use the deployment system to promote the batch to TEST & PROD.

We are evaluating the idea of using an additional XML DOCU tab to store object-level metadata for each object when it is deployed to the TEST or PROD environment. Examples of things we might want to store in this DOCU tab include:
  • Deployment ID, date & time
  • Deployer name & email address
  • Link to deployment log
A structured documentation tab seems like a straightforward way of adding this sort of object-level metadata. Before we go to far down this path though, I thought I would ask if anyone else had done something similar. We are particularly interested to know whether having an additional DOCU tab on each object noticeably impacts performance of XML exports & imports. Thanks in advance for any input!