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

Question

Question

Using the "Move Entry" task does not move the entry into an existing folder.

Workflow Laserfiche Cloud
Updated February 16, 2023
asked on June 24, 2021

I'm building out a new repository and I would like to be able to move files into specific folders based on a variable (Name usually). However, the way the "Move Entry" task on a workflow is working now, if you tell it to put the document in a folder named x, if there is already a folder named x instead of attempting to put the document in the folder already created, it just makes a new folder. There is no option to merge or not make a folder. (Just terminate the workflow but that still doesn't get the desired result).

 

So, how can I go about inserting a document into a variably named folder with workflow if the move entry task isn't moving the file correctly? Is there something I'm missing?

 

Thank you for your help.

 

P.S. Feature Idea: Merge folder option for Move Entry task and when move/copy folders in the repository.

0 0

Answer

SELECTED ANSWER
replied on July 16, 2021

That's fair. Gentle reminder that these forums are manned by volunteers on a as-time-permits basis. Issues that require a faster turnaround should be directed to Tech Support.

I was answering your original question by describing the functionality. I meant to come back and discuss the updated error information, but time got away from me.

Usually when the duplicate name cannot be reconciled, it's an issue with extra characters in the name, things like new line characters or trailing spaces or other unprintable characters. Where do the first and last name values come from?

You might want to send this issue to your reseller and have them open a case with Tech Support anyway so we can take a look at the actual values.

0 1

Replies

replied on June 24, 2021

Actually, Workflow does use existing folders. If you see multiple folders created, there are usually a few potential causes:

  • ProcessAutomationUser does not have rights to see the existing folder (so when it asks the LFServer if it exists, the server says no and a new folder is created)
  • multiple workflows run at the exact same time and they all attempt to create the folder at the exact same time (this may depend on how you're starting this workflow)
1 0
View 2 previous replies
replied on June 26, 2021

The ProcessAutomationUser has implicit allow on all rights and features, and is assigned all security tags.

There is only one workflow instance running.

In the instance monitor when the Move Entry task sees a duplicate object it gives a message:

"A duplicate object exists. Created the folder 'Redactedlastname, Redactedfirstname (2)' instead of 'Redactedlastname, Redactedfirstname'. Destination Path = \Departments\HR\Employees\No Names] [0299-WF1]"

Which I find makes absolutely no sense because the "Duplicate object" is exactly where I want it to be going.

0 0
replied on July 15, 2021 • Show version history

FYI replying "The problem your having doesn't occur like you're saying" is not helpful.

0 1
SELECTED ANSWER
replied on July 16, 2021

That's fair. Gentle reminder that these forums are manned by volunteers on a as-time-permits basis. Issues that require a faster turnaround should be directed to Tech Support.

I was answering your original question by describing the functionality. I meant to come back and discuss the updated error information, but time got away from me.

Usually when the duplicate name cannot be reconciled, it's an issue with extra characters in the name, things like new line characters or trailing spaces or other unprintable characters. Where do the first and last name values come from?

You might want to send this issue to your reseller and have them open a case with Tech Support anyway so we can take a look at the actual values.

0 1
replied on January 24, 2023

Hi Miruna,

Thanks for the explanation on this, really helpful. I think we're seeing the same issue. We're starting a number of workflows in cloud simultaneously, each workflow acting on one document.

The documents are being filed into a new folder structure and it seems that if two documents are attempted to be moved to a new path (which doesn't already exist) at the same time it creates two folders, one with the correct name and one with the same name + "(2)" at the end.

Does the cloud workflow handle the folder creation slightly differently to the on-premise version? We've used the on-prem version to handle moving thousands of documents in a similar way before and we've never come across this.

Not an issue as such, we'll find a way around it, just wondering why it behaves differently between the cloud and on-premise versions :)

Cheers,
Dan

0 0
replied on February 16, 2023

Any solution or workaround of the multiples folder with (2), (3),..? I have the same issue with a customer who could process up to 100 documents simultaneously.

0 0
replied on June 24, 2021

The ProcessAutomationUser has implicit allow on all rights and features, and is assigned all security tags.

There is only one workflow instance running.

In the instance monitor when the Move Entry task sees a duplicate object it gives a message:

"A duplicate object exists. Created the folder 'Redactedlastname, Redactedfirstname (2)' instead of 'Redactedlastname, Redactedfirstname'. Destination Path = \Departments\HR\Employees\No Names] [0299-WF1]"

Which I find makes absolutely no sense because the "Duplicate object" is exactly where I want it to be going.

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...