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

versioning via listener?

Christine_Howell

Hello,

In order to accomodate different types of users, I'd like to implement versioning that will happen after a content item has been approved, whether by workflow, or manually (strongly frowned upon, but they just won't stop). Currently, we have an 'autoVersion' automated activity in the workflow. I'd like to remove this and use a listener to do the versioning. My question is, what listener event should I 'attach' this to? I am thinking deployment.managedobjectupdate in the management stage. Would this be a good place?

Thanks,
CHowell

Find more posts tagged with

Comments

eLink User

If all approvals are done through workflow, is there a particular reason to implement creating version through a listener?

On Thu, Jan 20, 2011 at 1:32 PM, eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

versioning via listener? ? Posted byhowellc@franklin.edu (Howell, Christine)On 2011/01/20 13:28
?
Hello,

In order to accomodate different types of users, I'd like to implement versioning that will happen after a content item has been approved, whether by workflow, or manually (strongly frowned upon, but they just won't stop).? Currently, we have an 'autoVersion' automated activity in the workflow.? I'd like to remove this and use a listener to do the versioning.? My question is, what listener event should I?'attach' this to?? I?am thinking deployment.managedobjectupdate in the management stage.? Would this be a good place?

Thanks,
CHowell
[To post a comment, use the normal reply function]
Forum: Vignette V7 and V8 Web Content Management
Livelink Server: knowledge-wlweb01

--
Regards,
Sohail Aboobaker.
Accumulate Consulting Inc.
www.letsaccumulate.com.
Ph: 416 907 9050

Warner_Soditus

you definitely wouldn't do this through a deployment event. you need to tie to the managedobject create/update events. if you're on V8, this may all be different, but in the V7 world, I always cautioned folks not to over-version stuff. it really can cause system issues, given how versions are stored and there wasn't an API to remove/archive versions.

~Warner

Christine_Howell

Most of our editors follow the process no problem. It is our main contributor who has more authority, but definitely not on a par with administrators, who has a very persistent habit of publishing from the site and approving the content item(s) in the dialog box that comes up. When approving manually as such, no versioning occurs. This was not an issue until recently when he screwed up in his usual hurried manner and lost the body content somehow. He complained that because there wasn't any versioning (there WOULD have been if he finished his workflow but that takes too long) when he did publish/approve, he couldn't retrieve the previous version. (There was no previous version because all previous versions were unexpectedly cleared out when export/import was done recently). So, I thought I would move the versioning to a listener so it would be versioned upon approval, whether from workflow or manually. Does this make any sense?

Christine_Howell

Quoted Warner Soditus (warner.soditus@wellsfargo.com) on 2011/01/20 14:35:

~Warner

The only event I see related to that is Deployment.ManagedObjectUpdate ( I wouldn't version on create, just update). I would like to version when it has been approved. So I am looking for the right listener. I'm thinking management stage. What events are invoked when a content item has been approved?

CHowell

eLink User

In the scenario below, if the versions were removed due to import/export and this was the first time, the item was being saved (due to dependency on some other item), then it might not have prevented even if it was in listener. The version saved would also have the same blank body (assuming it is written on post-persistence update after checking that status is approved).
?

On Thu, Jan 20, 2011 at 2:30 PM, eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

Re versioning via listener? 2 ? Posted byhowellc@franklin.edu (Howell, Christine)On 2011/01/20 14:26
?
Most of our editors follow the process no problem.? It is our main contributor who has more authority, but definitely not on a par with administrators, who has a very persistent habit of publishing from the site and approving the content item(s) in the dialog box that comes up.? When approving manually as such, no versioning occurs.? This was not an issue until recently when he screwed up in his usual hurried manner and lost the body content somehow.? He complained that because there wasn't any versioning (there WOULD?have been if he finished his workflow but that takes too long) when he did publish/approve, he couldn't retrieve the previous version.? (There was no previous version because all previous versions were unexpectedly cleared out when export/import was done recently).? So, I thought I would move the versioning to a listener so it would be versioned upon approval, whether from workflow or manually.? Does this! make any sense?

?
[To post a comment, use the normal reply function]
Topic: versioning via listener?
Forum: Vignette V7 and V8 Web Content Management
Livelink Server: knowledge-wlweb01

--
Regards,
Sohail Aboobaker.
Accumulate Consulting Inc.
www.letsaccumulate.com.
Ph: 416 907 9050

Christine_Howell

That's all water under the bridge. What I am looking for is, is there an appropriate event to version the updated content? Ideally, we'd like to do that upon approval, but there does not appear to be any events associated with approving the content update. This person just flat out refuses to use the workflow so I am looking for alternatives.

Thanks,
CHowell

On Thu, Jan 20, 2011 at 2:30 PM, eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

Re versioning via listener? 2 Posted by howellc@franklin.edu (Howell, Christine) On 2011/01/20 14:26

Most of our editors follow the process no problem. It is our main contributor who has more authority, but definitely not on a par with administrators, who has a very persistent habit of publishing from the site and approving the content item(s) in the dialog box that comes up. When approving manually as such, no versioning occurs. This was not an issue until recently when he screwed up in his usual hurried manner and lost the body content somehow. He complained that because there wasn't any versioning (there WOULD have been if he finished his workflow but that takes too long) when he did publish/approve, he couldn't retrieve the previous version. (There was no previous version because all previous versions were unexpectedly cleared out when export/import was done recently). So, I thought I would move the versioning to a listener so it would be versioned upon approval, whether from workflow or manually. Does this! make any sense?

[To post a comment, use the normal reply function]
Topic: versioning via listener?
Forum: Vignette V7 and V8 Web Content Management
Livelink Server: knowledge-wlweb01

--
Regards,
Sohail Aboobaker.
Accumulate Consulting Inc.
www.letsaccumulate.com.
Ph: 416 907 9050

David_Stiles

As has already been said, post-persistence events are what youare looking for. These events are what are fired in the VCM when modificationsare made to a given managed object. With respect to persistence, there isnothing particularly special about approving an object. The transaction is stillsimply to change a property and commit/persist the object just as is done withany other updates.

However, that said, this wont really result in the behavior youwant. Post-persistence is not the same as “post-transaction”. Whena post-persistence listener is fired, the current transaction for the committedobject is not yet complete and changes to the object have not yet beenpersisted to the database (they have only been set in the current transaction).But when a version is created, the current state of the object as found in thedatabase is what is written to the saved version. Therefore, if you create aversion within a post-persistence listener, the new version wont include the changesbeing made to the object in the current transaction. Also, if you only want tocreate a version when an object is being approved then another issue you haveis to be able to detect that a persisted object is being approved. The only wayyou can really do this is, within your post-persistence listener, fetch theobject from the database and compare what you fetch to the in-memory objectfrom the persistence event. You can optimize this somewhat by only fetching theobject if the in-memory object is approved, as well as fetching the object fromthe database using topRelationOnly=true. Then when you detect that the approvalstatus is changing from unapproved to approved you could create a version. Ifit happens to be that the only thing changing is approval status, then theversion you create will still be up-to-date enough to be useful. The only thingthe new version wont have is the updated approval status, but this wont matterbecause anytime a version is restored, the approval status of the object isalways left as unapproved anyway.

One other thing, import/export does not remove existingversions. It will only create new versions on import. So if any versions wereremoved it had to be due to something else. That said, import/export can alsobe used to delete objects in the VCM and all versions for an object are deletedwhen the object is deleted.

From: eLink Entry:Vignette V7 and V8 Web Content Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Thursday, January 20, 2011 4:03 PM
To: eLink Recipient
Subject: Re Re versioning via listener? 2

Re Re versioning via listener? 2

Posted by howellc@franklin.edu (Howell, Christine) On 2011/01/20 16:57

On Thu, Jan 20, 2011 at 2:30 PM, eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

Re versioning via listener? 2

Posted by howellc@franklin.edu (Howell, Christine) On 2011/01/20 14:26

Most of our editors follow the process no problem. It is our main contributor who has more authority, but definitely not on a par with administrators, who has a very persistent habit of publishing from the site and approving the content item(s) in the dialog box that comes up. When approving manually as such, no versioning occurs. This was not an issue until recently when he screwed up in his usual hurried manner and lost the body content somehow. He complained that because there wasn't any versioning (there WOULD have been if he finished his workflow but that takes too long) when he did publish/approve, he couldn't retrieve the previous version. (There was no p! revious version because all previous versions were unexpectedly cleared out when export/import was done recently). So, I thought I would move the versioning to a listener so it would be versioned upon approval, whether from workflow or manually. Does this! make any sense?

[To post a comment, use the normal reply function]
Topic:	versioning ! via listener?
! Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

--
Regards,
Sohail Aboobaker.
Accumulate Consulting Inc.
www.letsaccumulate.com.
Ph: 416 907 9050

[To post a comment, use the normal reply function]
Topic:	versioning via listener?
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

Christine_Howell

Thank you, this is very helpful information.

Your explanation about the versioning issue during export/import was spot on. I did delete the contents in order to update the CTD.

Many Thanks,
CHowell

Jesse_Estum

You could probably attach a listener thePrePersistence events and then check the approval state of the incomingCI versus the approval state of the same CI, except fetch it by ContentInstance.findByContentManagementId(...).

From:   "eLink Entry:Vignette V7 and V8 Web Content Management" <v7webcontentmanagement@elinkkc.opentext.com>
To:   "eLink Recipient"<devnull@elinkkc.opentext.com>
Date:   01/20/2011 04:03 PM
Subject:    Re Reversioning via listener? 2

ReRe versioning via listener? 2

Posted by howellc@franklin.edu(Howell, Christine) On 2011/01/20 16:57

That's all water under the bridge. What I am lookingfor is, is there an appropriate event to version the updated content? Ideally,we'd like to do that upon approval, but there does not appear to be anyevents associated with approving the content update. This personjust flat out refuses to use the workflow so I am looking for alternatives.

Thanks,
CHowell

In the scenario below, if the versions were removed dueto import/export and this was the first time, the item was being saved(due to dependency on some other item), then it might not have preventedeven if it was in listener. The version saved would also have the sameblank body (assuming it is written on post-persistence update after checkingthat status is approved).

On Thu, Jan 20, 2011 at 2:30 PM, eLink Entry: VignetteV7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com>wrote:

Reversioning via listener? 2

Posted by howellc@franklin.edu(Howell, Christine) On 2011/01/20 14:26

Most of our editors follow the process no problem. Itis our main contributor who has more authority, but definitely not on apar with administrators, who has a very persistent habit of publishingfrom the site and approving the content item(s) in the dialog box thatcomes up. When approving manually as such, no versioning occurs. This was not an issue until recently when he screwed up in his usualhurried manner and lost the body content somehow. He complained thatbecause there wasn't any versioning (there WOULD have been if he finishedhis workflow but that takes too long) when he did publish/approve, he couldn'tretrieve the previous version. (There was no p! revious version becauseall previous versions were unexpectedly cleared out when export/importwas done recently). So, I thought I would move the versioning toa listener so it would be versioned upon approval, whether from workflowor manually. Does this! make any sense?

[To post a comment, use the normal replyfunction]
Topic:	versioning! via listener?
!	Forum:	VignetteV7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

--
Regards,
Sohail Aboobaker.
Accumulate Consulting Inc.
www.letsaccumulate.com.
Ph: 416 907 9050

[To post a comment, use the normal replyfunction]
Topic:	versioningvia listener?
Forum:	VignetteV7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01