Question

Checking document location, moving to a different top level folder based on that location?

Workflow

Updated October 17, 2017

asked on October 17, 2017

Ok first forgive me, I am very new to Workflows. Here is what I am trying to accomplish today.

A document resides in any certain folder, could be 5 folders deep. When tagged, this document needs to be pulled up from it's current folder and placed in a new location based on it's previous location.

Example:

\\Admin Department Records\Billing\2017\Document1

Workflow finds that the file is in top level folder "Admin Department Records", now move to new folder "Admin Department Scanning".

This workflow needs to work on several different departments. So what I have been trying to do is read that top level folder which I accomplished using a token and the split function and using indexing. Now I have that top level folder in a token. Next I am trying to remove the "Records" from that path and insert "Scanning" into the path.

I don't know if it can be done. It works in my head! But I'm not knowledgeable enough to do it in LFWF yet.

0 0

Replies

replied on October 17, 2017

Are all the top level folders always the same structure? Meaning 1) are they all the same number of words? 2) do they always match the pattern of 'department name' Department Records?

0 0

replied on October 17, 2017

To answer your question, no they are not always the same number of words, the department names might have different lengths. They do always end in "Records" or "Incoming Scans".

I do think I got it to work though! Here's the probably wrong and inefficient steps I took:

Step 1 - Reading the top level folder and trimming it down with Split:

Step 2: Removing "Records" from that folder name:

Step 3: Tacking on Incoming Scans to that folder name and moving the file:

0 0

replied on October 17, 2017

It's fine. Though, one minor thing, you're removing the space in front of "records" as well, but not adding it back with "Incoming Scans". So you'll end up with "Admin DepartmentIncoming Scans".

0 0

replied on October 17, 2017 • Show version history

That's what I thought too, but in all my testing I was getting double spaces. Removing that space brought it down to single space. Not sure where it's coming from...

0 0

replied on October 17, 2017

Oh, I see what's going on, you're right, it'll be fine.

You have it as "all values separated by space". So it's "Admin Department Records " (with a trailing space). The trim function does nothing since it's applied before indexing when the space is not there (token modifications are applied in the order listed in the dialog: functions first, then indexing, then formatting and finally regular expressions).

0 0

You are not allowed to follow up in this post.

Question

Question

Checking document location, moving to a different top level folder based on that location?

Replies

Sign in to reply to this post.