TAGUI error

we recently migrated from 6.7.1 to 7.3.1 on the RHEL.Lately i noticed that when i try to tag the Content by clicking the Tag option from file menu and trying through add the date through calendar it does it correctly.But when i do it using the TagUI screen as a part of the workflow it throws some strange error.
From the calender.ipl i see that its failing at the below part of snippet.Any suggestions would be apprciated.
[HTML]
function callback()
{
var optionsArray = document.callout_form_2.dateField.value;

if (optionsArray != '')
{
if (!set_datacapture_item_value(optionsArray))
{
alert('Fatal callout error. Did you close the datacapture window?');
}
return true;
}
return false;
}
[/HTML]

Find more posts tagged with

Comments

ranjeeth

Found that its only Occurring when i try to tag multiple files.

Rick Poulin

The problem is likely with "document.callout_form_2.dateField.value". That's an unsafe and unsupported way to access the field. You should be using FormAPI to do this type of stuff. If callout_form_2 is the iframe from your callserver, then your ipl should be printing JS that makes the result available in the top window, e.g. top.myNewOptions = new Array();. Accessing any part of the DOM directly in FormsPub/TagUI is and has always been flaky and unsupported.

Snap 2017-03-06 at 09.33.50.png

Snap 2017-03-06 at 09.36.26.png

ranjeeth

The problem is likely with "document.callout_form_2.dateField.value". That's an unsafe and unsupported way to access the field. You should be using FormAPI to do this type of stuff. If callout_form_2 is the iframe from your callserver, then your ipl should be printing JS that makes the result available in the top window, e.g. top.myNewOptions = new Array();. Accessing any part of the DOM directly in FormsPub/TagUI is and has always been flaky and unsupported.

Hi rpoulin
The suggestion You made makes absolute sense but i was wondering what changed in 7.3.1 or in 7.2.1 because its was working fine in 6.7.1 SP1,just Curious.

OR51L(new).rptdesign

BIRT exception.jpg

ISCBorisB

I was wondering what changed in 7.3.1 [...] because its was working 6.7.1

Among other things, unsupported means "Subject to change without notice".

TS 6.7.1 has been released in 2007. Lots of things changed in 5 years, tagging including.
It'll take you much less time to fix your code than to figure out what changed so that
certain unsupported hack does not work any longer.

DynamicFilterNew.rptdesign

ranjeeth

inorder for the look up to uses the element name with out any file context prefix "fc_****" added the following part and resolved the issue.
This will work if you need tag mutliple files which uses CGI callouts.
[HTML]
var element = '/'+'$element_name';
var api = window.opener.getScriptFrame();
// set the value to the element in the current file context
api.IWDatacapture.getItem(element).setValue(selectedValue);

return true;
[/HTML]