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/cancel

disha

How can we differentiate between Finish button and cancel button on the dcr?

I want to initiate a workflow on the click of finish button. I have used onClose event but i am not able to differentiate that which button is clicked.

Find more posts tagged with

Comments

Adam Stoller

How can we differentiate between Finish button and cancel button on the dcr?

I want to initiate a workflow on the click of finish button. I have used onClose event but i am not able to differentiate that which button is clicked.

What have you tried in terms of your FormAPI code?
What version of TS are you using / What version of the FormAPI manual have you referenced?

For example - in the 6.7.1SP1 FormAPI manual, I believe your answer might be found on page 24 - but since I don't know what you've tried and what you're using, that's about as far as I'm willing to go on the subject at this time.

MAK

How can we differentiate between Finish button and cancel button on the dcr?

I want to initiate a workflow on the click of finish button. I have used onClose event but i am not able to differentiate that which button is clicked.

Here is what you can do ... depending on your version.

var finishButtonClicked=false;
function init()
{
IWEventRegistry.addFormHandler("onSave", saveHandler);
IWEventRegistry.addFormHandler("onClose",handle_close);
}

function saveHandler(button) {
switch (button) {
case IWDatacapture.SAVECLOSE_BUTTON:
finishButtonClicked=true;
break;
}
return true;
}
function handle_close() {
if(finishButtonClicked)
{
start workflow
}
IWDatacapture.close();
return true;
}

UseDataSetAsADataSource.rptdesign

gir

Alternative would be to override the existing finish/cancel javascript function which is called onclick of finish/cancel button to act according to your requirement and calling that function during initialization

function init() {
//override cancel buttion
customCancel();
}

function customCancel() {
try{
//for finish it would be parent.document.getElementById("iw.base.wizard.finish.button");
var cancel = parent.document.getElementById("iw.base.wizard.cancel.button");
cancel.href='javascript&colon;parent.getScriptFrame().customCancelHandler();';
}catch(e){
alert("Cancel button missing!!!");
}
}

function customCancelHandler() {
if(confirm("Do you want to close the form?")) {
top.window.close();
}
}

gir

FYI, If you r calling a cgi script on click of finish keep in mind that the callserver you use through form api is asynchronous and use flags to overcome the issue.

namithapai

Maybe you can also try using the tt_data to launch workflow on "Finish".

You can read more about how to make that work in the Workflow guides or search for "tt_data" in the forums. Here is one such example

http://devnet.interwoven.com/forums_vb/showthread.php?t=25329&forumid=16&highlight=tt_data

PS: I am saying this from experience in using "tt_data" to start the workflow when the dcr "Finish" is clicked.

Maybe it works only for CCPro though. I am not sure about CCstd.

RonaldV

I want to initiate a workflow on the click of finish button.

As Manithapai says: why not go for tt_data? It is much more simple and robust the formapi.