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

Question

Question

Quick Fields auto corrections possible?

Quick Fields Version 10
Updated July 6, 2018
asked on July 5, 2018

Is there a way to get Quick Fields auto-correct specific common errors in the target fields?

For instance, I have it picking up words in a column to fill in a multi-value field.  There are a number of very common words it will find, however, some of those common words get cut off and I have to manually correct them to ensure searchability.

Can we use the Token Editor (or something) to cause an auto correct?

  • If it finds EQUIPMENT RENTA, then auto correct to EQUIPMENT RENTAL
  • If it finds MACHINERY REPAI, then auto correct to MACHINERY REPAIR
  • If it finds SHARED COMMUNIC, then auto correct to SHARED COMMUNICATIONS
  • etc,

Is so, how would I set this up for numerous corrections?

Thanks!

 

0 0

Answer

SELECTED ANSWER
replied on July 6, 2018 • Show version history

Connie

Instead of applying the field within the for each, just push the value into a multi value token, as Devin stated above.

After you have looped through all values in your original multivalue token and pushed corrected values into a temp multivalue token, you then write the corrected temp multivalue token to the entry (overwriting the original values).

0 0

Replies

replied on July 5, 2018

Try something like this:

  1. Create a new multi-value token
  2. Use the For Each Value activity to iterate over your existing multi-value field
  3. Inside the For Each Value activity, examine each value.
    1. If the value is one that needs to be replaced, place the correct value in the new multi-value token
    2. If the value does not need to be replaced, place the existing value in the new multi-value token.
  4. Set the multi-value field to be the new token that you created.

 


Basically, you are going to build a new set of values, and throw the old ones away. I don't think there is any way to modify multi-value token values in place.

1 0
View 2 previous replies
replied on July 5, 2018

Here is what I created today (with nine different corrections/conditions).  Mine does what I think you're saying yours does.  Is there something I'm not seeing in yours?

0 0
replied on July 5, 2018

It looks like you got it. Sorry, it appeared that you were still having trouble. Is what you came up with working?

0 0
SELECTED ANSWER
replied on July 6, 2018 • Show version history

Connie

Instead of applying the field within the for each, just push the value into a multi value token, as Devin stated above.

After you have looped through all values in your original multivalue token and pushed corrected values into a temp multivalue token, you then write the corrected temp multivalue token to the entry (overwriting the original values).

0 0
replied on July 6, 2018

HA!  SUCCESS!!!

BEFORE    AND AFTER

 

Based on Bert's comments, I

  1. took the activity he crossed off and placed it after the Conditional Decision,
  2. placed a multi value token before the Conditional Decision to hold all the values,
  3. added a branch at the end of the Conditional Decision to catch any values that didn't need correction

 

And it worked!  With some tweaking, of course.  The Machinery Repair below was my test branch.  I'll have to make these corrections to all the other branches now.

And here's the additional branch that was needed to catch (placehold) all the fields that didn't need corrections:

THANKS, GUYS!

0 0
replied on July 6, 2018

Devin, I think you were also trying to describe this solution, but I just wasn't getting it until something Bert said clicked.  Now I see what you were trying to tell me.  

Thanks!

0 0
replied on July 5, 2018 • Show version history

You could probably do what you are after using the Quick Fields Script Editor. It allows you to respond to events and run custom code during your session. We've used it for odd little things like that. I'm not sure, but it might be an addon that you have to purchase.

0 0
replied on July 5, 2018

I've never used the Script Editor, but have often wondered if I should pursue learning what ever I need to so I could use it.  Is it an option you have to buy?  Is it better than using workflow to do the same thing after storing them in LF?

0 0
replied on July 5, 2018 • Show version history

I much prefer to push as much logic as possible into Workflow. It's a lot more flexible. However, we only have QF Agent. There are no users who scan with Quick Fields.

I'd suggest that you do the corrections in Workflow unless you end up needing human eyes on the changes up front.

Do you know how you are ending up with so many fields cut off like that? I couldn't help noticing that they are all getting truncated at 15 characters. Is there something weird about your field that might be doing that?

1 0
replied on July 5, 2018 • Show version history

Thanks, Devin.  I'm going to build the workflow.

The data is being filled in from our Financial software and the programmers have only allowed 15 characters for that column.  I have asked that we contact our software providers and shift some of the allowable spaces on those columns, but I've been told that it isn't an option.  I'm still pretty sure it could be done, however, at the moment I am forced to work with it as it is.

0 0
replied on July 5, 2018

Okay, so it's not a perfect solution, because I can't get WF to just replace PART of ONE of the multi-value fields.  

If I tell the Assign Field Values to REPLACE the VALUES then it replaces all values with just the one part that needed correction.  That is okay if it was only those words in the field, but sometimes it is not.  

I have created tokens to change only the part I want changed, but then I have to decide, "What do I want more?":

  1. Do I want to "Replace Existing Values" (will wipe out all the other field values!) (NO!)
  2. Do I want to "Append to existing values" (will add it, but leave the field value with the uncorrected words) (NOT SO MUCH)

 

See examples below (using MACHINERY REPAI as the piece that needs correcting) that show results of "append" when there was only one original field value (acceptable) and one where there were a number of values (not so acceptable, because sometimes there are hundreds of these multi-value fields on one document and maybe 10-20 of those hundreds of values need changing).

Larger multi-value example (before and after):

After storing in the repository and having Workflow run this correction:

The "Replace" option replaces ALL VALUES!

 

0 0
replied on July 5, 2018

Another example of it ending up with adding too many extra field values (again, this one is an acceptable amount, but many of the documents have far many more of these fields):

0 0
replied on July 5, 2018

I was really hoping that we could have an IF THEN statement in the Token Editor of this Quick Fields activity that could cover multiple variables:

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

Sign in to reply to this post.

Details
Related Posts
Loading ...