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

Question

Question

Filing date different in web client

asked on October 2, 2019

I have a Records Management client that is using a workflow to automatically put the entry in to the correct folder and set the filing date. This works fine.

However, the Web Client shows the filing date as the date from the parent folder. The Windows Client shows the correct filing date that was set by the workflow.

Web Client -

Windows Client

 

Snippet of the workflow

 

Any thoughts or advice will be appreciated

 

Jonathan

0 0

Replies

replied on October 3, 2019 Show version history

What are the versions of the web client and Laserfiche server?

0 0
replied on October 3, 2019

Hi Miruna,

The Web Client is 10.4.1.35 and the Server is 10.4.1 build 350.

Should I log a support case?

 

Jonathan

0 0
replied on October 3, 2019

Hi Miruna,

It seems that the Filing Date is supposed to be inherited from the parent folder? Is there a way to only inherit the Retention Schedule and not the Filing Date?

 

0 0
replied on October 4, 2019

Is the desktop client also on version 10.4.1?

There is no way to inherit the retention schedule and not the filing date. The filing date does not have a meaning on its own outside of cutoff or retention schedules. So if the record is inheriting the retention from its parent record folder, the record individual's filing date is ignored. There was a bug in the 10.4.0 server that allows for saving this setup. 10.4.1 and higher should throw a 9566 error stating  "The filing date cannot be changed on a inherited record." when attempting to set the filing date on a record without a retention schedule applied directly to it.

0 0
replied on October 6, 2019

Hi Miruna,

The Desktop Client is also 10.4.1.

I guess I have circumvented the "The filing date cannot be changed on a inherited record." by setting the individual filing date BEFORE it is moved to the record folder.

I'll have to re-do how the customer will handle their records.

 

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

Sign in to reply to this post.