Here’s a brief description of the deployment workflows available to you:
The Standard workflow lets you deploy assets when the last task is complete, or defer deployment, for example to a nightly batch operation.
The Early Staged workflow lets you preview assets on a staging server before deploying them to a production site. The assets are checked in before deployment to the staging server.
The Late Staged workflow lets you preview assets on a staging server before deploying them to a production site, just as you can in the Early Staged workflow. In this model, however, the assets are locked and not checked in until after deployment to production. This behavior means that the changes you make to an asset cannot be accessed for editing by another user until after deployment.
Note: It is recommended that you use the Standard or Late Staged workflows ordinarily and Early Staged workflow only when the others don’t meet your needs.
For a detailed explanation of the tasks and task actions provided by ATG Merchandising workflows, see the descriptions for their Content Administration counterparts in the Project Workflows section in the Adapting Workflows to Content Management Projects chapter of the ATG Content Administration Programming Guide. The ATG Content Administration versions of these workflows include Author and Review Content tasks that are present in commerce workflows, but not in the ATG Merchandising deployment workflows.
