One way synchronization scenarios

A: Work.

B: Production.

1. Content creators create and edit content on A.
2. Content managers or approvers sync the content to B.
   Content is published with a publication and expiration date.

The following flowchart depicts the scenario:

A: Work.

B: Staging

C: Production.

1. Content creators create and edit content on A.
2. After the work on A is completed, content creators or approvers sync the content to staging environment B.
3. QAs, content approvers, or managers proofread and test the content on B.
   • If everything is OK, content is synced from A to C.
   • If problems are found, corrections are done on A and content is synced from A to C.

NOTE: Syncing the content from A to C, guaranties full synchronization.

The following flowchart depicts the scenario:

You have the following environments:

A: Work.

B: Staging.

C: Production.

1. Content creators create and edit content on A.
2. After the work on A is completed, content creators or approvers sync the content to staging environment B.
3. QAs, content approvers, or managers proofread and test the content on B.
   • If everything is OK, content is synced from B to C.
   • If problems are found, QAs, content approvers or managers perform one of the following:
     • Make the corrections themselves on B and sync from B to C.
     • Corrections are done by content creators on A and then synced again on B.

NOTE: In this scenario, A and C are not synchronized. This has to be done manually on a defined periods of time.

The following flowchart depicts the scenario: