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

Question

Question

Changing a field value with an SDK application is not always seen by WF Subscriber

Updated May 27, 2015
asked on May 13, 2015

The following SDK code which changes a field value on an entry is not seen by the Workflow Subscriber.

I have to use the LF Client to manually change the field before my Wait Condition is met.

The way I know this is that I see the workflow is waiting on Wait for Entry Change. After I manually update the field to Ready, then back to Exported in the client the Workflow moves on. There is no errors in the subscriber log and I have tried restarting the subscriber.

 

                Fields.LockObject(Lock_Type.LOCK_TYPE_WRITE);
                Fields.set_Field("MarkedForExport", "Exported");
                Fields.Update();

 

0 0

Replies

replied on May 13, 2015

Are you unlocking the document? Notifications are not sent out until the entry is unlocked. Did you check if the entry change appears in the Subscriber Trace?

Also, are you sure your starting rule is not excluding this user?

0 0
View 3 previous replies
replied on May 13, 2015 • Show version history

I can reference back to the document I used but the program was built a year ago and was working until yesterday morning with this entry. I will check that out, and also look into the Trace, I don't think I have used the subscriber Trace yet. 

 

No luck yet. I am sure my SDK application is working properly as thousands of entries have since been updated by it and the subscriber caught every one of them. I am curious to see what the Trace shows but I have very little time to review it since it only keeps a couple hours worth of data. Didn't see an option to increase the size under the log file settings tab.

0 0
replied on May 14, 2015

The Subscriber Trace only loads the last 1000 entries, but the logs are persistent. They accummulate under C:\ProgramData\Laserfiche\WF\ServerData\SubscriberLogs\<machine name>. You'll have to un-zip them, but then you can load a log through File\Open in the Trace.

0 0
replied on May 14, 2015 • Show version history

What does it mean if there is a huge gap in these logs? The subscriber was asleep? I just received another report of workflows not kicking off, and sure enough a huge gap in the subscriber logs.

0 0
replied on May 15, 2015

What do you mean by "huge gap"?

0 0
replied on May 27, 2015

There is a gap of time (about 3 hours) where the logs show there was no activity. Yet there are documents in the system with last modified dates within the 3 hour period. The 3 hour gap makes no sense, except that Windows Updates were running at that time. My instinct is to tell the customer that Windows Updates may conflict with the subscribers visisbility of changes but I don't have any substantial evidence of this.

0 0
replied on May 27, 2015

Windows updates are unlikely to have an impact. If the Subscriber couldn't communicate with the Laserfiche Server or the Workflow Server you would see it in the log. The Subscriber only evaluates the event types that match its enabled starting rules, so it's possible that during that period of time there weren't any. Or the Subscriber service was off.

That's just guessing, the log files may give you a better idea of what was going on.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...