You are viewing limited content. For full access, please sign in.

Question

Question

Starting Rules for New Repository on Same Server is NOT Working

asked on July 28, 2022

I built a workflow in one repository and have copied it and updated it for the new repository on the same server. I set 'Get Metadata From' dropdown in the Starting rules configuration to reflect the new repository and published.

The starting rule kicks off the WF just fine in the original repository but does NOT work for the second repository.

I have done mega research here in LF Answers and cannot, for the life of me, figure out what I'm doing wrong.

My starting rule has the correct Repository defined:

I have 3 set up for:  Entry Copied, Entry Moved, and Entry Created. None of the work. The login to the new repository set up within the workflow is successful:

BTW, this is for two repositories on the test server. I have the same exact issue happening on the production server too!

0 0

Answer

SELECTED ANSWER
replied on July 28, 2022

OK, spoke with IS/IT guy. Rebooted both workflow services:  Laserfiche Workflow and Laserfiche Workflow Subscriber. Voila! It now works as expected. When in doubt, reboot!

0 0

Replies

replied on July 28, 2022

Hi Gloria,

Has this 2nd repository been configured for Workflow Subscriber to monitor it? That's done in the Workflow Configuration Manager.

0 0
replied on July 28, 2022 Show version history

Both repositories reside on the same server and the server is listed under Montioring > Subscribers. UPDATE:  When I open it, yes, I do see both repositories. Is it case-sensitive I wonder? I'm going to trying something.

0 0
SELECTED ANSWER
replied on July 28, 2022

OK, spoke with IS/IT guy. Rebooted both workflow services:  Laserfiche Workflow and Laserfiche Workflow Subscriber. Voila! It now works as expected. When in doubt, reboot!

0 0
replied on July 28, 2022

One thing to keep in mind: rules take about 30 seconds after publishing to go live on the Subscriber.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.