Modified Date on move

I have written a script to perform a mass reorganisation of documents using CWS. This involves moving the documents to sub folders of their current location. However, this move causes the Mofified Date to be altered. I realise that this is by design by I wonder if there is any way to prevent the Modified Date from being amended?

Clearly a move in this context is not a modification to the document but would have the unfortunate effect of changing the records management disposal dates.

Thanks

David

Find more posts tagged with

Comments

Pramod Mohandas

As you rightly said, this is how core Content Server handles the move of documents via the GUI – with a change in the Modified Date and going around this design could result in unwarranted issues. You may have to additonally set up an RM disposition dates accordingly so that the change doesn’t affect the moved documents.

eLink User

I am not sure if you are running into some specific RM flags in your livelink. For e.g I had a Document with a "RECORD DATE" of June 3rd 2016.The 'Record Date' of 3rd is arrived because that is when the document was dropped,and it is a convenience feature to set the 'Record Date' on the time of creation.

I performed a "Move" using the GUI and looked at the Record Date.It was still June 3rd 2016.So I re- moved this same object back to where it came from using a WSAPI call It obeyed the Record Date .

Questions to you is

Are you not running RM based on Record Date? perhaps you are running it off "Modified Date" I donot even know if RM allows that?
Have you reached or posted this in RM Forum so they can react to it better.RM module has flags built hither/tither to keep everybody happy so you may find an acceptable solution. They run scenarios like you want,who would not re-classify things after a while...

Here are things in our livelink with RM that I thought was responsible for some things.

Administer Modified Date Triggers ?func=admin.ModifyDate

we have the first one on,which means donot change the ModifyDate on that

Then in Configure Records Management

?func=RecMan.ConfigureRecordsManagement

We have ours to 'Always keep RM Classification' in a Move.If this is set to INHERIT from the new parent then obviously some of the things you run into might happen.

.....appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Tue, Jun 7, 2016 at 9:38 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Modified Date on move Posted byMillitt, DavidOn 06/07/2016 10:35 AM

I have written a script to perform a mass reorganisation of documents using CWS. This involves moving the documents to sub folders of their current location. However, this move causes the Mofified Date to be altered. I realise that this is by design by I wonder if there is any way to prevent the Modified Date from being amended?Clearly a move in this context is not a modification to the document but would have the unfortunate effect of changing the records management disposal dates. ThanksDavid
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: Knowledge Center