Is it possible to do versioning when user click "OK" or "Apply" button on the content entry form?

What we would like to do is when user click the "OK" or "Apply" button on the content entry from, we need to have create a new version for this content. Is it possible?

How to capture the event that "OK" or "Apply" button is clicked? Is it possible to customize these buttons?

Find more posts tagged with

Comments

Warner_Soditus

that's exactly what a pre/post-persistence listener is for. you're not customizing the buttons, per se, just taking action before/after the item is saved.

however, you probably don't want a version saved for EVERY save of a content item. that can lead to issues. you're probably better to make that part of workflow/publishing or something.

~Warner

Shuai_Hua

Quoted Warner Soditus (warner.soditus@wellsfargo.com) on 2010/08/25 19:19:

that's exactly what a pre/post-persistence listener is for. you're not customizing the buttons, per se, just taking action before/after the item is saved.

however, you probably don't want a version saved for EVERY save of a content item. that can lead to issues. you're probably better to make that part of workflow/publishing or something.

~Warner

Hi Warner

Our user wants to have the versioning when they made a change to content item. But currently there are two ways to make change to the content item. One is user can create/edit the content at the Content Entry Form in the VCM Console. Another is in our custom workflow, we will do some update to the content item by using Vignette API which is ContentInstance.commit()

If we say the pre/post-persistence listener will take action before/after the item is saved then I think it also take action when we use ContentInstance.commit() in the workflow, is it correct?

If it also take action when we use ContentInstance. commit() then it is not met user's requirement.. User only want to make a versioning of the content item before the workflow. So I am asking is there any way to capture the "OK" button action and make a versioning of content item. Not make a versioning when we use ContentInstance .commit() in the workflow.

eLink User

The easiest way might be to add versioning task at the start of your workflow. Assuming that the workflow kicks off when the user has finished editing the content.

Sohail

On Wed, Aug 25, 2010 at 8:21 PM, eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

Is it possible to do versioning when user click "OK" or "Apply" button on the content entry form? ? Posted byshuai.h.hua@seagate.com (Hua, Shuai)On 2010/08/25 20:19
?
Quoted Warner Soditus (warner.soditus@wellsfargo.com) on 2010/08/25 19:19:

that's exactly what a pre/post-persistence listener is for. you're not customizing the buttons, per se, just taking action before/after the item is saved.
however, you probably don't want a version saved for EVERY save of a content item. that can lead to issues. you're probably better to make that part of workflow/publishing or something.
?
~Warner

Hi Warner

If we say the pre/post-persistence listener! will take action before/after the item is saved then I think it also take action when we use ContentInstance.commit() in the workflow, is it correct?

[To post a comment, use the normal reply function]
Topic:	Is it possible to do versioning when user click "OK" or "Apply" button on the content entry form?
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

eLink User

The easiest way might be to add versioning task at the start of your workflow. Assuming that the workflow kicks off when the user has finished editing the content.

Sohail

On Wed, Aug 25, 2010 at 8:21 PM, eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

Is it possible to do versioning when user click "OK" or "Apply" button on the content entry form? ? Posted byshuai.h.hua@seagate.com (Hua, Shuai)On 2010/08/25 20:19
?
Quoted Warner Soditus (warner.soditus@wellsfargo.com) on 2010/08/25 19:19:

that's exactly what a pre/post-persistence listener is for. you're not customizing the buttons, per se, just taking action before/after the item is saved.
however, you probably don't want a version saved for EVERY save of a content item. that can lead to issues. you're probably better to make that part of workflow/publishing or something.
?
~Warner

Hi Warner

If we say the pre/post-persistence listener! will take action before/after the item is saved then I think it also take action when we use ContentInstance.commit() in the workflow, is it correct?

[To post a comment, use the normal reply function]
Topic:	Is it possible to do versioning when user click "OK" or "Apply" button on the content entry form?
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

I think Sohail and I have given you the concepts of how you can achieve what you want. I think you need to ponder your business process and figure out the best way to implement it. I'm not sure I understand what you're trying to do. But, chances are, between listeners and workflow program tasks, you should be able to do what you want to do to meet the business need.