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

Call-out issue

TeamsiteUser

I have a select box with a cgi-callout which actually makes a framework call and opens up a JSP.
When i mention the framework URL from datacapture.cfg using url attribute, the JSP opens up properly

datacapture.cfg entry
url="/iw-mount/default/main/STAGING/frameworkCallout-featured_doc"

But when i try to use the same framework call using Form API, execution of the JSP happens but the JSP does not open up.
Form API changes
IWEventRegistry.addItemHandler("/Details/Featured_Documentation","onCallOut", callFeaturedDocs);

function callFeaturedDocs(){
var server = window.location.hostname;
var objMethod = "featured_doc";
var metaId = IWDatacapture.getItem('/metaId');
var metaIdValue = metaId.getValue();
var params = new Object();
params.productId = metaIdValue;
params.Assoc_Col_Type="Documentation";
timeout = setTimeout('callServerFailed()', 60000);
IWDatacapture.callServer("http://"+server+"/iw-mount/default/main/STAGING/frameworkCallout-"+objMethod , params);

}

Are there any restrictions from using call outs from form API? This has now become a critical issue in our project.

TS version : 6.5

Find more posts tagged with

Comments

Adam Stoller

Not sure - but I think it might help if you post the DCT code for the item:[indent]/Details/Featured_Documentation[/indent]

Frederik

RTFM tst.650a.formapi.pdf

"The target of the [callServer] operation is a hidden frame. The response from the post should be JavaScript that manipulates the form or creates and populates data structures."

which explains why your JSP "doesn't show up".

if you need it to show up, use window.open instead

TeamsiteUser

Thanks!!
One of my issue solved when i used window.open instead of callServer.

But what should be the method to return back to this select box.
Currently i have written it as below but it does not work.(It works when i call it directly from datacapture.cfg)

function writeSelectionsBack(){
var optionsArray = document.callout_form.OrderablePart.options;
opener.top.getScriptFrame().setPartListOptions(optionsArray, "'/Details/Featured_Documentation'");
self.close();
}

setPartListOptions is method in my Form API method as :

function setPartListOptions(options, list) {
var item = IWDatacapture.getItem(list);
var newOptions = new Array();
for (i = 0; i < options.length; i++ ) {
newOptions = new Option(options.text, options.value);
}
item.setOptions(newOptions);
IWDatacapture.redraw();
}

Frederik

try debugging exactly which part of your code fails.

I've never used callServer or the thing you're doing, but I have a sneaking suspicion (a.k.a. a wild guess) that the error could be in your opener.top.... code. What about opener.setPartListOptions(...) ?

Migrateduser

I tend to think that you should stick with callServer. It looks as though, for a pop-up window, you're referencing the DCT properly, i.e. opener.top.getScriptFrame(), but try placing "top.alert" or just "alert" everywhere to see where your code is breaking.

Dave

TeamsiteUser

Two issues:
1> If i use IWDataCapture.callSever(), in that case my JSP does not show up. So i need a way to do it?

2> If i use window.open(), my JSP comes up properly...but write back to DCT is not happening properly. I tried out using options.setPartListOptions() and it gives me 'Permission denied' javascript error. All statements before this statement are getting execurted properly. Its just this line which is giving the error and i have no idea what to use for implementing this functionality.

Frederik

2> If i use window.open(), my JSP comes up properly...but write back to DCT is not happening properly. I tried out using options.setPartListOptions() and it gives me 'Permission denied' javascript error. All statements before this statement are getting execurted properly. Its just this line which is giving the error and i have no idea what to use for implementing this functionality.

I suggest you report this issue to Support. Because all you're doing seems to be documented. The WF doc even states (without further specifics) that you can execute formAPI via the opener call. But an example is missing.

So you could claim this is documented functionality and you don't get it to work the way it's supposed to.

Please report back the answer of Support.

Migrateduser

1> If i use IWDataCapture.callSever(), in that case my JSP does not show up. So i need a way to do it?

2> If i use window.open(), my JSP comes up properly...but write back to DCT is not happening properly. I tried out using options.setPartListOptions() and it gives me 'Permission denied' javascript error. All statements before this statement are getting execurted properly. Its just this line which is giving the error and i have no idea what to use for implementing this functionality.

I strongly recommend using callServer. I suggest that you're not doing the callServer and/or passing the variables properly. All a callServer is is an inline HTTP request but the advantage is that the API makes it possible to carry a special relationship between the callServer, the FormAPI and the DCT. With window.open(), you're on your own and to reverse engineer TS to find the appropriate DOM structure to make it work with window.open() in 6.5 may mean to reengineer that solution when you upgrade to later versions, since IW's DOM model may change. That is, having the spawned window (via window.open()) reference the DCT is not necessarily supported.

Dave

TeamsiteUser

I tried using IWDateCapture.CallServer but the issue was the call-out JSP was not coming up as described previously in this thread.
Do you have a solution to solve that issue?(I would not mind switching to your approach Smiley Happy

)

Migrateduser

Well, what do you mean when you say it wasn't coming up properly? Did it not appear at all? Did it come up with a JSP error? Did it come up with some generic error?

TeamsiteUser

The JSP does not come up at all.. It is documented that when call-out is invoked from Form API, it runs a hidden frame which is the reason why JSP does not show up. This is what even i got to know in this thread itself(you can also refer to Frederik'r reply in this thread)

Migrateduser

Oh, I see -- so you want a UI. You may want to use a callout instead.

TeamsiteUser

For some requirement, i need to call it from Form API instead of datacapture.cfg

Frederik

[...] With window.open(), you're on your own and to reverse engineer TS to find the appropriate DOM structure to make it work with window.open() in 6.5 may mean to reengineer that solution when you upgrade to later versions, since IW's DOM model may change.

I believe you are mistaken.

Read p.34 of tst.650a.formapi.pdf

(quoted) "With FormAPI, much of the need for the CGI callout is eliminated.The template designer can achieve the same functionality more easily and with much greater flexibility in a user script. A user script can open a new window by calling the browser’s open() command, dynamically specifying any URL it needs. This new window can access the user script code and FormAPI methods of its parent window by calling opener()."

Again, I suggest to open a case to Support to ask how exactly the new window can access the user script code using "opener" or "opener()".