nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to get DTree.ModifyDate to reflect changes in Document Content only

Leena_Lintunen_(lintule_-_(deleted))

Currently ModifyDate in DTree seems to get updated when any of the events CREATE, ADDVERSION, PERMCHANGE or ATTRCHANGE are recorded in DtreeAudit for a document.If only the events (CREATE, ADDVERSION) would cause Dtree ModifyDate to be updated, it would better reflect changes in the document contents.How could this be done?What is the logic or purpose behind showing ModifyDate for the events PERMCHANGE or ATTRCHANGE as these events are of no interest to the enduser?-Carl Grandell-

Find more posts tagged with

Comments

eLink User

Message from Magnus S?lg? via eLinkIsn't attributes changes when you change the Meta data ( Change categories) ???>From an user point of view a update of Metadata COULD be important and also MAYBE should make a change in the modify date.My opinion is that it not a bug and it is rather logical but as always with document management it depends what kind of information you handle.If you do an attribute change updating categories ( see Knowledgebase article 2334574 )without adding a new version you will get a date change in the column displayed in theout-of-the-box Livelink interface (Dtree.modify) BUT if you look in the Info/version tabon the document date created for that version which I assume is the date Carl is looking for. Carl my suggestion is that you change Livelink so that you instead display that time/date.One way of changing the layout is a module from Open Text PS called Category View. Contact person Jan Spengler. I think it is not supporting displaying version createdate.We have also done some changes like displaying thumbnails etc. for documents with renditions. That is controlled by categories on folders.RegardsMagnus S?lg?magnus@ids.seID Application+46-8-7046349Ps. referred articleKnowledgebase article 2334574https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=2334574&objAction=ArticleViewPss. the small test I did with creating an Event Permissions Changed did not change the Dtree.modifydate

John_Shoun

This has been a very consistent complaint and source of confusion for our users. We would also like an option so that the change date is tied to the document version.The other poster is correct that it may be 'logical' when you consider the total document management (any change to metadata or permissions is a change to the document), but the problem is that this goes against the most common user expectation.Users expect Livelink to behave similar to what they experience on the desktop (Microsoft Windows 95/98/NT/2000). The document date only changes when the file content is modified, not when any other feature is modified (attributes, user fields, or permissions). While this may not be 'correct' from a doc management perspective it is what they are accustomed to. You are fighting an uphill battle when you try to change this view. It will become more of a support problem when users try to use Livelink desktop and the Livelink and desktop environment look the same, but behave differently.

eLink User

Message from Magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Then the only way forward I see is to build a module that stops changes to Dtree.Modify when a change in a category is done

Regards

Magnus S?lg?

magnus@ids.se

+46-8-7046349