As a solution provider, we have many products we have written for our customers. We often integrate these products into various workflows to create a seamless process for our customers. Our software can be configured to post via the 8.3 SDK or the 10.2 SDK. We have noticed that the way document creation happens when using the 8.3 SDK is different than using the 10.2 SDK. Checking to see if anyone else has had similar experiences/issues. An example issue is described below.
Example Issue:
MVi has a product called LaserChecks that captures check information from a core processor and generates the check image and applies the appropriate authorization signature. When the check is completed it is printed and a digital copy is passed to the Laserfiche repository. Depending on the check, a workflow will look to see if this check is for an invoice that may already be in the repository. If so, it will link the check in the checks folder to the invoice in its vendor folder.
Here is the starting rule for the workflow that grabs the check and looks to see if there is a matching invoice in the system
Here is the issue, when using the 8.3 SDK the check is posted as a create event. However, when using the 10.2 SDK the check is posted via two events. The first is a create event that seems to create the placeholder record then a change event that seems to add the image pages and metadata.
Here is the info on two checks posted a minute apart, the one highlighted in blue was posted via the 8.3 SDK and the other two (same entry name) were posted via the 10.2 SDK .
Posting in two steps causes issues with our workflows since we try to just trigger on creation events and they fail because the metadata hasn't been posted yet. We don't want to trigger on change events because someone may come in later and change the check by adding a sticky note, extra field data, or some other action that would then cause the check to go through the workflow and attach again to the invoice. We have also thought about adding a delay in the workflow on create events to wait for the document to be finished in the change event. The issue is, the shortest delay we can put in the workflow is 1 minute. We would like this to be a few seconds rather than a minute or more.
Thoughts on how to make this work a little smother using the 10.2 SDK?