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

Question

Question

Workflow to Move documents to RMS

asked on March 30, 2015 Show version history

Hi all,

I have the following folder structure on LF.

We are want to create a workflow which moves folders/ documents from each root department from LF and move them to RMS on a yearly basis, such that these documents will be stored in a record folder with respect to the year of archival. Please see attached file.

However, we are planning to manually create the respective year in RMS or wondering if the creation of the years can be included in the workflow as well.

Thanks to reply.

Regards,

Sheila

0 0

Replies

replied on April 1, 2015

If you're looking to move every entry from the respective folders, the workflow is pretty simple, just iterate through the departments, through the folders within the departments, then move each each entry using a path like "\RMS\%(ForEachDepartment_CurrentEntry_Name)\%(Year)\%(ForEachDepartmentFolder_CurrentEntry_Name)\."

This workflow assumes your RMS is within the same repository and on the Root level, so I added a conditional sequence to check if the current department is a record or not. If you only wanted to move certain entries, then before the Move activity add a conditional so only the documents you want moved will go.

RMS_WF.png
RMS_WF.png (13.3 KB)
1 0
replied on April 2, 2015

Thanks Kevin for the workflow design. However, can we have the configuration for each activity?

 

Thanks to revert back.

Kind Regards,

Sheila

 

0 0
replied on April 2, 2015

I only showed the general because the configuration specifics will depend on your specific requirements.

The Get Year token should retrieve the year you want to use - if you're running this workflow on Jan 1, 2015 for 2015 then you would use take the current date token and use a date format of yyyy. If you're doing it for a different year (AKA running on December 31, 2014 for 2015) then you'll need to do the above but also add in a date token calculator. 

The first Find Entries will find all departments in the Root Directory (in the folder with ID 1). The conditional sequence would be to filter out any non-departments (such as the RMS by specifying "Entry: Name doesn't equal RMS" for example). For each of those, find the folders inside (using find entries, entry_currentID from For Each Entry). 

Finally, move each of those to the RMS by creating a path from all of the entries you found and the year- \RMS\%(ForEachDepartment_CurrentEntry_Name)\%(Year)\%(ForEachDepartmentFolder_CurrentEntry_Name)\ - If you can set the move to create a folder if it doesn't exist.

However, bear in mind you'll probably have to adjust it to work for your specific case. To test it, you could create a small folder structure inside your repository and point the first find entries to that new "root". I hope that gives you enough of a start to put together your own, personalized workflow!

1 0
replied on May 11, 2015

Hi all,

I have a folder structure which is as follows in the attached document.

I want to create a record folder (i.e. Administration, Human Resource,Finance) automatically by moving these folders  as well as contents of LF folder to my record series.

Can I please have a workflow definition and its configuration?

 

Thanks to advise

 

Kind Regards,

Sheila

 

0 0
replied on May 11, 2015

Sheila,

We cannot post workflow definitions on a public site as they contain personal information. We can answer questions and provide direction, but not write the workflow for you. If you need custom work done for your workflow, please contact your regional manager about rates and availability.

0 0
replied on May 13, 2015

Hi Miruna,

 

I was able to create a record folder (i.e. Administration, Human Resource,Finance) automatically by moving these folders  as well as contents of LF folder to my record series.

But, now I want to get the 'Year' part(i.e 2015) from a Date field (i.e 12/05/2015) and then create the respective 'Year' (i.e 2015) folder under a defined folder(for e.g: Management). It will be in the following structure: Management-> '2015'.

 

Thanks to advise.

Kind Regards,

Sheila

 

0 0
replied on May 13, 2015

See the help file for date formatting.

0 0
replied on June 1, 2015

Hi Sheila, 

I took a look at the workflow definition you sent to Presales, and saw your concern about a shortcut being created twice.  Below are a few general issues you'll want to address.  In my testing, I saw the shortcut problem resolved after making the following changes:

1.  If your intent is to have this workflow run for each document returned by your Find Entries activity, you need to make sure the rest of your activities reference that activity properly properly.  

You would do this by moving the rest of the activities into the For Each Entry loop you have in the definition.  Then you'd have the activities within the loop use the Current Entry of the For Each loop.  Kevin's response above gives a good example of this.

You will also want to use the %(ForEachEntry_CurrentEntry_Path) token as the destination of your shortcut.  

2.  Within your Conditional Sequence, your Create Entry activity simply creates a folder, when it seems you wanted the document to move as well, judging by the description you wrote for the Conditional Sequence.  You need to use a Route Entry to Folder activity to do this.  

Workflow can automatically create the destination folder if it doesn't exist yet.  Take a look at the section Action > To configure the Actions tab to learn how to configure this.

3.  You can use regular expressions and formatting directly on a token by using the Token Editor, as opposed to having separate activities.  

After doing the above, I ran the workflow and it created a single shortcut for each document whose date received was set to today.  Below is a screenshot of the modified configuration:

I hope all this helps.  As you build, the Laserfiche Workflow Help Files will be very useful.  There's good documentation for each activity as well as guidance for configuration.

1 0
replied on March 30, 2015

Are you asking if it's possible or how to do it? Workflow can create folder for you based on information you read from the document.

0 0
replied on March 30, 2015

Hi All,

Thanks for the reply, Miruna. Yes I want to know how we can achieve this using workflow. Any possible solution to do this?

Workflow should move the documents to RMS according to the defined folder structure on LF and then create the respective years as record folder for each underneath department. 

 

Kind Regards,

Sheila

0 0
replied on May 18, 2015

Hi Miruna,

Thanks for your help. I tried to create the folder as per the help file provided and it works.

I would like to add below conditions in my workflow.

If DateReceived= TODAY then Move Entries to my newly created folder.

Which activity must I use to do the above date comparison. Note that DateReceived is a date field added in all documents?

Thanks to advise

Kind Regards,

Sheila

 

 

0 0
replied on May 18, 2015

So you want to find all documents received "today" and move them to this folder? Or do you move each document as it's created and then want to wait until the DateReceived field is filled in?

0 0
replied on May 18, 2015

Hi Miruna,

The DateReceived field is a compulsory metadata field defined in a template.

Now, I want to add a condition which will check if the DateReceived=TODAY and move these documents to my RMS folder. Please advise which activity could be used and how to add the condition.

Infact, I am using the DateReceived field as a test and henceforth, I will be using an ExpiryDate as a condition for document archival. Moreover, the same validation rule will apply for the ExpiryDate.

 

Thanks

Kind Regards,

Sheila

0 0
replied on May 21, 2015

Ok, so then you can run a scheduled workflow that run once a day, searches for all entries where the field equals %(date) and moves them to the record folder.

0 0
replied on May 22, 2015

Hi Miruna,

Yes. Yesterday I was discussing with a colleague and we agreed that the workflow will run on a scheduled date and time. Thanks a lot for your confirmation :).

Kind Regards,

Sheila 

0 0
replied on May 31, 2015

Hi,

 I want to keep a shortcut of my document in its original folder once the document has moved to RMS

I am having an issue when creating shortcut of a document, 2 copies of shortcut are being created. I have used the route entry to folder activity name.

Thanks to reply

Kind Regards,

Sheila

0 0
replied on June 1, 2015

Did you check out your workflow instances to see who makes the second shortcut?

1 0
replied on June 9, 2015

Hi Caroline,

I have eliminated some activities as you mentioned. But I am still having issue as 2 or 3 copies of shortcut documents are created. I have noticed that for every department that is found under the Registry folder, the number of shortcut documents is dependent on these. Can I please get some advice where I did go wrong?

Thanks to reply.

0 0
replied on July 1, 2015

Hi,

I want to move these documents based on a workflow scheduler. I have added the schedule rule which runs on a daily basis and conditions have been created : Entry Type=Document and Path=\name.

However, I can see this is working. But when I run the workflow for a particular document, it works.

Thanks to advise

Kind Regards,

Sheila

0 0
replied on July 1, 2015

Schedules don't allow for conditions, it sounds like you have 2 separate starting rules: a schedule and a condition starting rule. You'll have to run a Find Entries or Search in your workflow to find the documents you want to move.

0 0
replied on July 1, 2015

Hi Miruna,

Thanks a lot.

Is there any other configuration that is required to schedule the workflow? I have only created a starting rule with the day and time (i.e it should repeat daily at 4pm).

How will I monitor if the workflow has been run correctly?

 Regards,

Sheila

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

Sign in to reply to this post.