Workflow and DCR versioning. Burning question..

MLee7404

Hello. I didn't know whether this fit as a workflow question or a teamsite question so I posted in both.

We have an environment proposed where the author, and editor
of a workflow can edit/make changes to content.

We also have an environment where the dcr will deploy to a
staging/preview environment.

The ONLY way to version dcr's is to submit for staging/preview.

The problem is...when the author passes their workflow changes in a dcr
to an editor, how can they keep their changes(since submit happens at the end of the workflow).

If the editor makes changes to the DCR, and then the workflow is rejected back to the author, how can the author see their original changes. Because the way it is now, the author's changes will be overwritten by the editors changes.

Would like to hear some best practice solutions regarding this.

Thanks.

Adam Stoller

Hello. I didn't know whether this fit as a workflow question or a teamsite question so I posted in both. We have an environment proposed where the author, and editor of a workflow can edit/make changes to content. We also have an environment where the dcr will deploy to a staging/preview environment. The ONLY way to version dcr's is to submit for staging/preview. The problem is...when the author passes their workflow changes in a dcr to an editor, how can they keep their changes(since submit happens at the end of the workflow). If the editor makes changes to the DCR, and then the workflow is rejected back to the author, how can the author see their original changes. Because the way it is now, the author's changes will be overwritten by the editors changes. Would like to hear some best practice solutions regarding this. Thanks.

One solution is to use multiple branches so that the content can be versioned throughout the creative phase of the process, and then have it copied (updatetask) to the other branch after it has been approved so that it can be versioned for publishing purposes.