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

finish and cancel button disable in TS6 ??

Pratzee

Hi,

is there a way to disable the "Finish" and "Cancel" buttons in the templating interface and add custom buttons ??

Thanx.

Find more posts tagged with

Comments

Migrateduser

Hi,

I am also looking for a reply to this same issue.Can anyone help to solve this.

thanks

Nicholas

check it

kaalraa

Hi there,

Please be more clear ...as you want to remove the buttons from DCT or just want to disable them.

On the former issue... go to the iw-home/httpd/webapps/content_center/WEB-INF/conf/base/ui_wizard.xml and remove the button tags.

On the later issue...
Use this to capture the finish and cancel button of the DCRs onFormInit event

var finish = parent.document.getElementById("iw.base.wizard.finish.button");
var cancel = parent.document.getElementById("iw.base.wizard.cancel.button");

- AKs.... The Shadow

jeetu

Hi AKs,

I tried modifying the file as specified by u (ui_wizard.xml)by removing the Finish button code , but thechange is not reflecting and i could still see the Finish button. Is there anything else to be done along with this change?

Thanks
Jeetyu

Migrateduser

I realize this is an old thread but I wanted to relay what I discovered today:

You can hide the Cancel button per DCT (many organizations don't want to hide the Cancel button across all DCT's) by calling the following line in FormAPI.

parent.document.getElementById("iw.base.wizard.cancel.button").parentNode.parentNode.style.display = 'none';

[size=2]This is entirely DOM-compliant so I don't want to hear anyone tell me that this is a hack. It's not. iw.base.wizard.cancel.button is the tag around the cancel link but going up two levels gives you the table cell, which unfortunately does not have an ID.

I'm referring to TS6.5, by the way. I'm sure there's a wonderful, simple, life-changing way to do this in 6.7 but some of us are still on the "old" platform :-)

Dave
[/size]

Adam Stoller

I realize this is an old thread but I wanted to relay what I discovered today:

You can hide the Cancel button per DCT (many organizations don't want to hide the Cancel button across all DCT's) by calling the following line in FormAPI.

parent.document.getElementById("iw.base.wizard.cancel.button").parentNode.parentNode.style.display = 'none';

[size=2]This is entirely DOM-compliant so I don't want to hear anyone tell me that this is a hack. It's not. iw.base.wizard.cancel.button is the tag around the cancel link but going up two levels gives you the table cell, which unfortunately does not have an ID.

I'm referring to TS6.5, by the way. I'm sure there's a wonderful, simple, life-changing way to do this in 6.7 but some of us are still on the "old" platform :-)

Dave
[/size]

It's a hack ;-)
Seriously though, it's reverse-engineering the DOM path to the Cancel button which is not guaranteed to remain consistent across patches, SP's, and upgrades - so it is unsupported.
However - all things being equal - it is a reasonable "hack" (as opposed to an unreadonable one).
Thanks for posting the info.

Migrateduser

Okay, so I disagree... and this is why:

I haven't played with 6.7 but I believe that this functionality is provided in 6.7 so there is no need to attempt this. That said, I did this today with 6.5 SP2, the next notch down from 6.7. I can't say how far "back" this works but I'm sure it includes several versions. Anyway, if it works on 6.5 SP2 and it's not needed in the subsequent version, it seems that this method (see, I prefer to call it a "method" rather than a "hack" :-) language is a tool -- just watch Fox News and you'll see what I mean), while unsupported by Interwoven, would accomplish the task in whichever [recent] versions necessary, up to 6.7, of course, where it's not needed.

Dave

Johnny

This is entirely DOM-compliant so I don't want to hear anyone tell me that this is a hack.

It's a great trick but there's no point telling people it's not a hack.

A hack anything that interacts with the system in a way that's not covered by public documentation. If it stops working - Interwoven will not support you.

You're using DOM methods but FormAPI is not there to provide access to the DOM - it's just a side affect of using javascript on the client.

As Ghoti said, there's always the chance that the id field or the html structure may change in a future release.

Basically - if you do something and it doesn't work and Interwoven won't help/support you, then it's a hack.

Don't get me wrong - the hack is useful and I use DOM hacks when needed too - but telling people that it's not a hack is just misinformation. They need to be aware of the possible outcomes - regardless of the likelihood or timeframe.