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

Invoke "formSetting" button on click of next button

Abishk

Hi Everyone,
-->I am working in ccstd.. When the user fills in data and clicks next button, he should be prompted with the "form settings" popup.
-->On click of the next event i am trying to call the "form settings" button using the folowing command windows.open(iw-cc/command/iw.formspub.settings) but it gives me an error saying parameter curdir_vpathis missing..
-->I need to know what parameters do i need to give along with the command to invoke "form settings" functionality on click of next button..

I would highly appreciate any help.. I really need this to work and i cant get this from any manuals.. Thanks

Teamsite 7.1 Windows 2003 Platform

Find more posts tagged with

Comments

Abishk

Ya i got it working..

Adam Stoller

Ya i got it working..

That's nice - suppose you post the details of how you got it working so that other's who might follow will be able to learn something from you.

birt db write back.zip

Abishk

That's nice - suppose you post the details of how you got it working so that other's who might follow will be able to learn something from you.

Ya sure.. Actually what i did was i checked the code behind the page and i realised on click of the "form settings" button the following command:- top.getDCFrame(self).postSettingsForm("opener.top._dcWin.datacapture_buttonframe.settingsCallback"); was getting called. so i made the use of it in my code.

Adam Stoller

Ya sure.. Actually what i did was i checked the code behind the page and i realised on click of the "form settings" button the following command:- top.getDCFrame(self).postSettingsForm("opener.top._dcWin.datacapture_buttonframe.settingsCallback"); was getting called. so i made the use of it in my code.

Okay - but keep in mind that those functions are NOT part of the official API and thus could change, without notice, when you next upgrade. I.e. it's not officially supported - so document the **** out of it.

Abishk

Okay - but keep in mind that those functions are NOT part of the official API and thus could change, without notice, when you next upgrade. I.e. it's not officially supported - so document the **** out of it.

Thanks adam... i'll keep that in mind..