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

Question

Question

Workflow compare Status between Laserfiche documents and MYSQL database

asked on May 14, 2013 Show version history

Hi, I need some help building a workflow that can compare Status' between the documents in Laserfiche to their data in MySQL. Then email any Status' that do not match. There would need to be some tricks in there as the Status name in Laserfiche would need to be modified to match a Status Code in our database.

 

For example:

The Contract Number will be required to match each document.

Search our MySQL database for certain Status type code (A, F, S, O) do not include other codes (about 5 of them).

Then use the Contract Numbers for those Status' to Search Laserfiche.

To compare that the Status' match, the Laserfiche Status' need to be modified from words to a code (eg Application Rec'd->F, Accepted->A, Outstanding->O, Signoffs->O, Settled->S).

Non Matching Status Codes to be emailed.

Not sure if you can help create a sample workflow for us? I am struggling with this one.

 

Kind Regards

0 0

Answer

APPROVED ANSWER
replied on May 30, 2013

Presales isn't really designed to create sample workflows like this, but we're more than happy to help you with any areas of difficulty that you're having! It sounds like you're having trouble getting started, so I would suggest creating a metadata field for the status codes. Then create a workflow will likely contain the following:

 

1) A "Find Entries" activity that will pull the documents that you want to compare

2) A "Retrieve Field Values" activity where you will retrieve the status code from the metadata field that you created

3) A "query data" activity where you retrieve all the document names and status codes for each document.

4) A routing decision (This will likely be inside of a "For each entry" activity) that will have 2 branches:

a) One will be satisfied when the document name is matched in the database (Also in the "For Each Entry")

I) Another routing decision that will have 2 branches (Also in the "For Each Entry")

i) One will be satisfied when the status code of the document matches the status code in the database

ii) The other will handle documents whose status code doesn't match

b) The other will handle exceptions if the document name isn't found in the database

 

Hopefully this is enough to get you started! The configuration of each activity will be up to you due to the fact that we aren't aware of how the system is set up and the exact details of each activity. If you run into any problems or if you have any more questions, feel free to let us know!

0 0

Replies

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

Sign in to reply to this post.