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; } } }

ContentInstance modified status

Venkat_Ramamurthy

Hi All,

We have a requirement to update a field data in the ContentInstance whenever there is a change in the ContentInstance has occured. We have used a Pre-Persistence update Listener for this, but the problem is the listener is getting called even when they click on the 'Approve' button. We dont need this.

Is there a way to check/find whether the CI has been modified or not in the listener through API?Any help on this is much appreciated. Thanks in advance.

Thanks and Regards,

TRV

Find more posts tagged with

Comments

David_Stiles

The only supported approach for doing this is to re-fetch the CIfrom within the pre-persistence listener and compare whatever fields you are interestedin with the values of the CI being persisted in order to detect changes. Butyou need to consider any performance impact of always doing this with everycommit. Persistence will indeed occur for any change made to a CI, and yourpersistence event listener will be called for changes to a variety of thingsbeyond just the fields you care about or approval status. But ideally, theoperation of your listener should be idempotent so that it doesn’t reallymatter if it runs even when not needed, and then you wont have to perform there-fetch of the CI.

From: eLink Entry:Discussion Group - Web Experience Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Sunday, August 07, 2011 9:01 PM
To: eLink Recipient
Subject: ContentInstance modified status

ContentInstance modified status

Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 2011/08/07 21:59

Hi All,

Is there a way to check/find whether the CI has been modified or not in the listener through API?Any help on this is much appreciated. Thanks in advance.

Thanks and Regards,

TRV

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

Namit_Gupta

Hi,

You can use the following code in your listener’sprepersistence.update event to update any field whenever there is a content update.

ManagedObject objMgdObj = objEvent.retrieveManagedObject();

ContentInstance objCI = (ContentInstance)objMgdObj;

AttributeData var = objCI.getAttribute(XML-NAME-OF-ATTRIBUTE);

objCI.setAttribute(var, value);

Please let me know in case you need any further information.

Thanks & Regards,
Namit Gupta | TCS
Enterprise Content Management Team
Work: +91 22 67782452
Mail: ng627@chrysler.com

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Monday, August 08, 2011 7:11 PM
To: eLink Recipient
Subject: RE ContentInstance modified status

RE ContentInstance modified status

Posted bydstiles (Stiles, David) On 2011/08/08 09:40

The only supported approach for doing this is to re-fetch the CI from within the pre-persistence listener and compare whatever fields you are interested in with the values of the CI being persisted in order to detect changes. But you need to consider any performance impact of always doing this with every commit. Persistence will indeed occur for any change made to a CI, and your persistence event listener will be called for changes to a variety of things beyond just the fields you care about or approval status. But ideally, the operation of your listener should be idempotent so that it doesn’t really matter if it runs even when not needed, and then you wont have to perform the re-fetch of the CI.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Sunday, August 07, 2011 9:01 PM
To: eLink Recipient
Subject: ContentInstance modified status

ContentInstance modified status

Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 2011/08/07 21:59

Hi All,

Is there a way to check/find whether the CI has been modified or not in the listener through API?Any help on this is much appreciated. Thanks in advance.

Thanks and Regards,

TRV

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

David_Stiles

The question here isn’t about *how* to make the update.But if you’re using this code exactly as is then you need to add a check of thetype of object in the event. You can’t blindly cast every event object toContentInstance.

From: eLink Entry:Discussion Group - Web Experience Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Monday, August 08, 2011 8:54 AM
To: eLink Recipient
Subject: RE RE ContentInstance modified status

RE RE ContentInstance modified status

Posted by ng627@chrysler.com (Gupta, Namit) On 2011/08/08 09:51

Hi,

You can use the following code in your listener’s prepersistence.update event to update any field whenever there is a content update.

ManagedObject objMgdObj = objEvent.retrieveManagedObject();

ContentInstance objCI = (ContentInstance)objMgdObj;

AttributeData var = objCI.getAttribute(XML-NAME-OF-ATTRIBUTE);

objCI.setAttribute(var, value);

Please let me know in case you need any further information.

Thanks & Regards,
Namit Gupta | TCS
Enterprise Content Management Team
Work: +91 22 67782452
Mail: ng627@chrysler.com

RE ContentInstance modified status

Posted by dstiles (Stiles, David) On 2011/08/08 09:40

The only supported approach for doing this is to re-fetch the CI from within the pre-persistence listener and compare whatever fields you are interested in with the values of the CI being persisted in order to detect changes. But you need to consider any performance impact of always doing this with every commit. Persistence will indeed occur for any change made to a CI, and your persistence event listener will be called for changes to a variety of things beyond just the fields you care about or approval status. But ideally, the operation of your listener should be idempotent so that it doesn’t really matter if it runs even when not needed, and then you wont have to perform the re-fetch of the CI.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Sunday, August 07, 2011 9:01 PM
To: eLink Recipient
Subject: ContentInstance modified status

ContentInstance modified status

Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 2011/08/07 21:59

Hi All,

Is there a way to check/find whether the CI has been modified or not in the listener through API?Any help on this is much appreciated. Thanks in advance.

Thanks and Regards,

TRV

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

Namit_Gupta

Hi David,

I agree with you. In order to check that thing we can use the following code to achieve this thing;

String strContentType =””;

ManagedObject objMgdObj = objEvent.retrieveManagedObject();

If(objMgdObj instanceof ContentInstance)

{

ObjectType ot = mo.getObjectTypeRef().getObjectType();

this.strContentType = ot.getData().getName();

if(strContentType.equalsIgnoreCase(“CTD NAME”)

{

ContentInstance objCI = (ContentInstance)objMgdObj;

AttributeData var = objCI.getAttribute(XML-NAME-OF-ATTRIBUTE);

objCI.setAttribute(var, value);

}

Thanks & Regards,
Namit Gupta | TCS
Enterprise Content Management Team
Work: +91 22 67782452
Mail: ng627@chrysler.com

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Monday, August 08, 2011 7:43 PM
To: eLink Recipient
Subject: RE RE RE ContentInstance modified status

RE RE RE ContentInstance modified status

Posted bydstiles (Stiles, David) On 2011/08/08 10:10

The question here isn’t about *how* to make the update. But if you’re using this code exactly as is then you need to add a check of the type of object in the event. You can’t blindly cast every event object to ContentInstance.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Monday, August 08, 2011 8:54 AM
To: eLink Recipient
Subject: RE RE ContentInstance modified status

RE RE ContentInstance modified status

Posted by ng627@chrysler.com (Gupta, Namit) On 2011/08/08 09:51

Hi,

You can use the following code in your listener’sprepersistence.update event to update any field whenever there is a content update.

ManagedObject objMgdObj = objEvent.retrieveManagedObject();

ContentInstance objCI = (ContentInstance)objMgdObj;

AttributeData var = objCI.getAttribute(XML-NAME-OF-ATTRIBUTE);

objCI.setAttribute(var, value);

Please let me know in case you need any further information.

Thanks & Regards,
Namit Gupta | TCS
Enterprise Content Management Team
Work: +91 22 67782452
Mail: ng627@chrysler.com

RE ContentInstance modified status

Posted by dstiles (Stiles, David) On 2011/08/08 09:40

The only supported approach for doing this is to re-fetch the CI from within the pre-persistence listener and compare whatever fields you are interested in with the values of the CI being persisted in order to detect changes. But you need to consider any performance impact of always doing this with every commit. Persistence will indeed occur for any change made to a CI, and your persistence event listener will be called for changes to a variety of things beyond just the fields you care about or approval status. But ideally, the operation of your listener should be idempotent so that it doesn’t really matter if it runs even when not needed, and then you wont have to perform the re-fetch of the CI.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Sunday, August 07, 2011 9:01 PM
To: eLink Recipient
Subject: ContentInstance modified status

ContentInstance modified status

Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 2011/08/07 21:59

Hi All,

Is there a way to check/find whether the CI has been modified or not in the listener through API?Any help on this is much appreciated. Thanks in advance.

Thanks and Regards,

TRV

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

Venkat_Ramamurthy

Hi Namit/David,

Thanks for your responses.

Hi David: Thanks for your response... thought something like isDirty()/setDirty() methods would be available....

I need your advice on one approach.

Lets say if I have the entire toXML() in a field in the table(not part of the CTD but part of the DB table of the CTD) through some listener. Then in the pre-persistent update listener before entering into my custom logic I am checking for the toXML() of the content Instance object with the DB table field value. If they are equal, it means there are no changes and I wont execute anything and if they are different I will execute my custom logic.

Do you think this approach will work? Are there any flaws that you can foresee here?

Thanks and Regards,

TRV

David_Stiles

No, this wont work. You’ll just end up with the same problem ofnot knowing what has changed. The only time persistence listeners are executed iswhen commit() is called and generally, the only time that commit() is called iswhen something has changed. And if something has changed then the XML generatedfrom toXML() will be different than it was before commit() was called.Furthermore, if you add columns to a table used for a CT, but you don’t defineattributes in the CT that map to those columns, then you will lose any datastored in those columns when instances of the CI are persisted. The persistencelayer deletes and re-inserts rows as part of the persistence logic and can onlyinsert columns it is aware of through the CT definition.

From: eLink Entry:Discussion Group - Web Experience Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, August 09, 2011 10:34 PM
To: eLink Recipient
Subject: RE RE RE RE ContentInstance modified status

RE RE RE RE ContentInstance modified status

Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 2011/08/09 23:31

Hi Namit/David,

Thanks for your responses.

Hi David: Thanks for your response... thought something like isDirty()/setDirty() methods would be available....

I need your advice on one approach.

Do you think this approach will work? Are there any flaws that you can foresee here?

Thanks and Regards,

TRV

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

Venkat_Ramamurthy

Hi David,
Thanks for your response...

The only time persistence listeners are executed is when commit() is called and generally, the only time that commit() is called is when something has changed.

Venkat: Why then they are called when Approve Button is clicked(without CI field changes)? is this also considered as a change(due to change in CI status)?

And if something has changed then the XML generated from toXML() will be different than it was before commit() was called.

Venkat: so whats the toXML() value here(in pre-persistent listeners) then? is this the value before change or the one with changes?

Furthermore, if you add columns to a table used for a CT, but you don’t define attributes in the CT that map to those columns, then you will lose any data stored in those columns when instances of the CI are persisted. The persistence layer deletes and re-inserts rows as part of the persistence logic and can only insert columns it is aware of through the CT definition.

Venkat :Thanks for this info... If I update the NON-CT field in post-persistence create and post-persistent update listeners then this persistence logic would have been completed right?

Thanks and Regards,
TRV

David_Stiles

Answers inline…

From: eLink Entry:Discussion Group - Web Experience Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, August 10, 2011 4:16 AM
To: eLink Recipient
Subject: RE RE RE RE RE ContentInstance modified status

RE RE RE RE RE ContentInstance modified status

Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 2011/08/10 05:10

Hi David,
Thanks for your response...

David: This is what I explained in my very first response to you. *Any* property of a ManagedObject that can be modified is persisted by calling commit(). Since approval status is a property of each ManagedObject, changes to it are persisted through commit().

And if something has changed then the XML generated from toXML() will be different than it was before commit() was called.

Venkat: so whats the toXML() ! value here(in pre-persistent listeners) then? is this the value before change or the one with changes?

David: The return value of toXML() is based on the in-memory object that the method is called on, so it will contain any changes that have been made. If you were to refetch the object from the database while in your persistence listener then the value of toXML() called on that object will be before changes, so you could compare these two values for differences, but again, *any* changes made to the object will be reflected in that comparison.

Furthermore, if you add columns to a table used for a CT, but you don’t define attributes in the CT that map to those columns, then you will lose any data stored in those columns when instances of the CI are persisted. The persistence layer deletes and re-inserts rows as part of the persistence logic and can only insert columns it is aware of through the CT definition.

Venkat :Thanks for this info... If I update the NON-CT field in post-persistence create and post-persistent update listeners then this persistence logic would have been completed right?

You need to understand that “post-persistence” does not mean “post-transaction”. At the time that post-persistence listeners are called, the current transaction has not been committed yet. If you do not write your updates to the same transaction then you will still lose those changes when the transaction is committed. If the changes you make are written to the same transaction then there is a chance that what you suggest could work, but I would still consider that to be a fragile solution as you would only be relying on current implementation which could change with any given release. And while it may work for your specific use case, this would still fail in general as there are other ways in which your data can be managed, but where these “hidden” fields would not be managed properly by the system. If you really want to take such an approach, it would be best to go ahead and define an attribute on the CT for the column and use the Hidden widget for that attribute.

Thanks and Regards,
TRV

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

Mario_DAnna

You can do something easy to understand in a listener if the change has happened because of a change in the approval status. Get the current managed object using the getManagedObject method and compare its status with the one of the persisted managed object, got as ManagedObject.findByContentManagementId(getManagedObject().getContentManagementId()).
Ciao
Mario

From: eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com>
To: eLink Recipient <devnull@elinkkc.opentext.com>
Sent: Wed Aug 10 11:16:02 2011
Subject: RE RE RE RE RE ContentInstance modified status

RE RE RE RE RE ContentInstance modified status

Posted byvenkat.ramamurthy@seagate.com (Ramamurthy, Venkat)On 2011/08/10 05:10

Hi David,
Thanks for your response... The only time persistence listeners are executed is when commit() is called and generally, the only time that commit() is called is when something has changed.

Venkat: Why then they are called when Approve Button is clicked(without CI field changes)? is this also considered as a change(due to change in CI status)?

And if something has changed then the XML generated from toXML() will be different than it was before commit() was called.

Venkat: so whats the toXML() !value here(in pre-persistent listeners) then? is this the value before change or the one with changes?

Furthermore, if you add columns to a table used for a CT, but you don’t define attributes in the CT that map to those columns, then you will lose any data stored in those columns when instances of the CI are persisted. The persistence layer deletes and re-inserts rows as part of the persistence logic and can only insert columns it is aware of through the CT definition.

Venkat :Thanks for this info... If I update the NON-CT field in post-persistence create and post-persistent update listeners then this persistence logic would have been completed right?

Thanks and Regards,
TRV

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

David_Stiles

Sorry, Mario, but this is not generally true. Approval statuswill change automatically (and not always), and the automatic changes are notperformed until after pre-persistence listeners have executed.

From: eLink Entry:Discussion Group - Web Experience Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, August 10, 2011 9:32 AM
To: eLink Recipient
Subject: Re RE RE RE RE RE ContentInstance modified status

Re RE RE RE RE RE ContentInstance modified status

Posted by mdanna (D'Anna, Mario) On 2011/08/10 10:31

RE RE RE RE RE ContentInstance modified status

Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 2011/08/10 05:10

Hi David,
Thanks for your response...

The only time persistence listeners are executed is when commit() is called and generally, the only time that commit() is called is when something has changed.

Venkat: Why then they are called when Approve Button is clicked(without CI field changes)? is this also considered as a change(due to change in CI status)?

And if something has changed then the XML generated from toXML() will be different than it was before commit() was called.

Venkat: so whats the toXML() ! value here(in pre-persistent listeners) then? is this the value before change or the one with changes?

Furthermore, if you add columns to a table used for a CT, but you don’t define attributes in the CT that map to those columns, then you will lose any data stored in those columns when instances of the CI are persisted. The persistence layer deletes and re-inserts rows as part of the persistence logic and can only insert columns it is aware of through the CT definition.

Venkat :Thanks for this info... If I update the NON-CT field in post-persistence create and post-persistent update listeners then this persistence logic would have been completed right?

Thanks and Regards,
TRV

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

[To post a comment, use the normal reply function]
Topic:	ContentInstance modified status
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

Venkat_Ramamurthy

Thanks David for your quick and valuable response. It was helpful.

Thanks and Regards,

TRV