Copy Files to Vault(s) When a Document is Released

This configuration provides Released Document Files to users at remote sites. It requires writing a method which is specified to run on a Lifecycle Transition to the Released state. See Programming Notes – Document Release Transition onEvent Method for an example of that code.

For this configuration, a master vault would typically be used as the main repository, and one replication rule must be set for the master vault, or otherwise for all vaults which might have the only copy of a ‘released’ document file.

• Initiator Type - onEvent
• Filter Method – none, or configured based on the business need. Remember, the filter method is checked before the replication transaction for a file is executed.
• Replication Mode – Scheduled, Delayed, or Immediate, depending on the file type and business need
• Replication Type - Copy
• Is Active - checked
• Replication Time – If Scheduled, set to an off hour. You should consider staggering the replication times for the different rules, so excessive replication transactions are not set to execute all at the same time.
• Timeout – depends on the installation, but a default value of 0100 (one hour) is a good starting point. Large files may require longer Timeout values.
• Label – a unique name for each rule.

And for the two relationships made in the Replication Rule -

• File Types – select the type(s) of files to move.
• Target Vaults – the selected vault(s).