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

Question

Question

LF Cloud WF - Search Repository for Blank Field Values

asked on April 15, 2022 Show version history

Hello, I have a situation with a customer where they want a certain field filled out on old records that we migrated from their previous document management system into on-prem and now into to the cloud.  Currently, this field is blank for all these records and I can craft a simple search query to identify all these records in the repository.  

However, in cloud workflow the "Search Repository" activity does not allow you to put conditions for a blank field so I can't pull these records the way I need to so it looks like I'll need to use a workaround.

Problem is, the number of documents that we need to process is over 112,000.  So I can't just highlight them all, move them somewhere manually, then have WF just pull entries in that temp folder.

It seems my only option right now would be to have WF search ALL records, retrieve the field value, and if it's blank, assign the field value.  But then we run into the problem that Search Repository only allows 100 docs at a time and Workflows cap out and like 10,000 activities.  

So instead, it looks like I'd have to create a "processed" tag then create a WF that pulls ALL records that don't have this tag, determine if the field value is blank, insert the field value if it is blank, then apply the tag regardless of field condition so it won't come back up in the search the next time the workflow runs.  I'd have to run this workflow like 1,700 times since it can only pull 100 entries at a time OR I'd have to have a repeat loop that re-runs the contained activities a certain amount of times.

It seems to me this is my best option but if anyone else has any other recommendations I'm all ears!

 

Edit 1: 

Well apparently Search Repository can't even search for tags so I guess I'll have to use a field........

 

Edit 2:

Entry field doesn't work ether because the Search Repository activity automatically ignores any documents that don't have that field assigned.  So telling the Search to pull documents with "template X" and also documents where"field Y does not equal PROCESSED" will pull NOTHING if you just created the field and it isn't assigned to any documents.  So I will have add this field to the template as well and then mess with field/template security so nobody other than me and Workflow can even see this field.

Hopefully when this is completed I'll be able to just delete the WF status field after I've completed all of this but since it will have data in it I'm worried it won't let me.....

0 0

Replies

You are not allowed to reply in this post.
replied on April 15, 2022

Well apparently Search Repository can't even search for tags so I guess I'll have to use a field.......man this is annoying!

replied on April 20, 2022

Found this and was worried as I just signed us up for cloud. :)  You can accomplish this by searching the path to where the files are stored and then in a For Each loop have a conditional decision that looks for empty fields.  At least that worked for my use case.

You are not allowed to follow up in this post.

Sign in to reply to this post.