Question

Need help creating a Workflow to Replicate entries without changing the folder ID

Workflow

Updated November 26, 2014

asked on November 25, 2014

I have created a workflow that looks for new entries in repository folders and if found copies the new entry to a different repository including the entries original path. It is set so if the path doesn't exist then create it.

My problem is that the workflow is ignoring that the folder already exists and is copying the path and entries adding a (2) to the end.

Any help would be greatly appreciated.

0 0

Replies

replied on November 26, 2014

It is not possible to keep the same entry IDs in the new repository.

0 0

replied on November 26, 2014

To clarify - I realize there will be a new entry IDs in the new repository but once they are there I do not want them to change. My issue is that the replication is recreating the folder path when the path already exists in the new repository. Is this a bug or a flaw in my workflow.

0 0

replied on November 26, 2014

Can you provide an example of what you are meaning? How does it remake something that is there?

0 0

replied on November 26, 2014

How is the security set up in the new repository? Does the user in the Workflow connection profile for the destination repository automatically get full rights to these new folders?

0 0

replied on November 26, 2014

To clarify for Deb, she has a public repository that gets exposed via weblink. The purpose of this public repository (via weblink) is to house documents for the regular public website. That said, the public website has numerous hard links over to specific LaserFiche document and folders via their respective IDs.

As you can gather, it's extremely important that LaserFiche Document and Folder ID's do not change during any process including workflows, else links to them on the public website become dead very quickly.

So to conclude, how does one perform a periodic file replication from various other LF repositories over to the public LF repository without the risk of ID's changing and other anomalies such as folder duplication (2)(3)(4)(Etc.) occurring as Deb stated above?

0 0

replied on November 26, 2014

The folder paths will be merged if the user in the connection profile has rights to see the folders in the new repository as well as create documents in them.

If you are seeing duplicated entries, double-check security on the original ones.

1 0

You are not allowed to follow up in this post.

Question

Question

Need help creating a Workflow to Replicate entries without changing the folder ID

Replies

Sign in to reply to this post.