2 Questions for simple LF solution

asked on March 29, 2013 • Show version history

Hello:

2 (hopefully) pretty quick questions:

1) I have some template field values coming in from an ODBC lookup that will bring in a name value: ex. jsmith I want to convert these via a lookup table to more user-friendly values. Can you think of an easy out-of-box way to do this short of adding a lookup table to SQL to query (2nd query) to update a field ?

Can I do this already via field management in LF Admin console such that I can insert the lookup pairs and have it automatically update with the user-friendly lookup value when the data is populated into the field ?

2) I have a situation where I want to have end-user ability to immediately terminate the current workflow, then re-attach the same workflow upon toggling a field. The user will change the assigned rep on a case, then toggle a field for "Update User". This should a) terminate the existing workflow. b) re-attach the same workflow to run (seeing the updated value, of course). Need a workaround because right now, if the 'rep' field gets updated mid-workflow, the workflow just fails (and not gracefully).

What's the easiest way to do this in workflow (using WF8.3). I don't want to have to put routing decisions all over the place to "catch" this field change in my current workflows if i can help it. Would rather be able to trigger the terminate and re-attach simply from update of a "status" field that already exists, even if it is by a rule that attaches a different workflow with a "kill existing WFs" and kick off these x events (basically a copy of the existing workflow).

0 0

APPROVED ANSWER

replied on April 8, 2013 • Show version history

For number 1, the first thing you need is a table that contains the user-friendly values associated with the original value (i.e. jsmith = john smith). You may then be able to build a view that combines the data and run your query on the view. Alternatively, you can join the tables in a custom query in Laserfiche Workflow. Both of these will be more efficient than running two separate queries on separate tables.

For number 2, if I understand you correctly, you want the ability to terminate a currently running instance of a workflow and start a new one on the same document. If that is the case, you should be able to do that using Workflow scripting. When I was asking around for details, one of our developers pointed me to this forum thread that talks about this scenario and includes some sample code. Try that and let us know if you run into any issues.

0 0

Question

Question

2 Questions for simple LF solution

Answer

Replies

Sign in to reply to this post.