Replicate Entries
This activity copies Laserfiche entries from one Laserfiche repository to another Laserfiche repository. See the tokens this activity produces.
Example 1: Trundle, Inc. has a repository for each department. The Human Resources department has its own repository that stores general employee information, but the employee performance reviews are stored in each department’s repository (Sales, Marketing, etc.). You can use this activity to copy a completed performance review from each department’s repository to the Human Resources repository.
Example 2: The city of Trenton has three servers: one WebLink Server that is used to publish documents to the public, and two regular production servers. An employee tags a collection of documents on one of the production servers with a “publish” tag indicating that these documents should be published for public viewing. This activity can take the tagged documents and copy them from the production server to the WebLink Server for public view.
How does this activity look in the Designer Pane?
- Drag it from the Toolbox Pane and drop it in the Designer Pane.
To configure this activity
- Select the activity in the Designer Pane to configure the following property boxes in the Properties Pane.
- Activity Name
- Activity Description
- Entries to Copy
- Destination Repository
- Destination Path
- Destination Volume
Note: If you have more than one connection profile for your workflow definition, the Source Repository property box lets you specify which connection profile this activity will use. The connection profile specified in the Source Repository property box indicates the repository the entries will be copied from.
The Replicate Entries activity produces the following tokens.
| Name | Description | Sample Syntax* |
|---|---|---|
| Destination Folder_Name | The name of the folder the replicated entries were placed in. | %(ReplicateEntries_Destination Folder_Name) |
| Destination Folder_Id | The Laserfiche ID number of the folder the replicated entries were placed in. | %(ReplicateEntries_Destination Folder_Id) |
| Destination Folder_Path | The folder path of the folder the replicated entries were placed in. | %(ReplicateEntries_Destination Folder_Path) |
| Destination Folder_FullPath | The folder path of the folder the replicated entries were placed in, including the folder's name. | %(ReplicateEntries_Destination Folder_FullPath) |
| Destination Folder_Repository | The repository that contains the folder the replicated entries were placed in. | %(ReplicateEntries_Destination Folder_Repository) |
| Destination Folder_Server | The Laserfiche Server that contains the folder the replicated entries were placed in. | %(ReplicateEntries_Destination Folder_Server) |
| Destination Folder_Guid | The GUID (Globally Unique Identifier) of the folder the replicated entries were placed in. | %(ReplicateEntries_Destination Folder_Guid) |
| Created Parent Folder | Whether the Replicate Entries activity created the folder the replicated entries were moved into. This token can have one of two possible values: True or False. | %(ReplicateEntries_Created Parent Folder) |
| Is Empty File | Whether there are files for the activity to copy. This token will have one of two possible values: True or False. It will only be available at runtime, and the Replicate Entries activity will use this token to determine if there are files to import to the new location. | %(ReplicateEntries_Is Empty File) |
*The "ReplicateEntries" portion of the syntax changes to match the activity's name as specified in the Activity Name property box. Note that all non-alphanumeric characters, except underscores, are removed from the name. For example, if you rename the activity Transfer to *Repo_2*, the syntax for the Destination Folder_Id token will be %(TransfertoRepo_2_Destination Folder_Id).
