SP1 vs SP2

Hi,

Can anyone out there confirm me is this a known issue, i am facing. Brief is as follows:

I have a server... which has TS6.1 with SP2... on which i ran two commands; one from a js file and other from the cgi file.

js file: IWDatacapture.getItem(\"/COMP\").setReadOnly(false); (working fine)
cgi file: api.IWDatacapture.getItem(\"/COMP\").setReadOnly(false); (working fine)

On other server which has TS6.1 with SP1 and i ran the same commands...

js file: IWDatacapture.getItem(\"/COMP\").setReadOnly(false); (working fine)
cgi file: api.IWDatacapture.getItem(\"/COMP\").setReadOnly(false); (NOT working fine)

Find more posts tagged with

Comments

Migrateduser

On your SP1 version, might there be offending code preceding your setReadOnly that would cause Javascript to stop its processing? Some context would be nice preceding the setReadOnly statement.

kaalraa

Dave,

Both the files... on both of the machines are same...

For making that double sure ... i checked the same and copied over the files from SP2 box to SP1 box.

Thanks,

On your SP1 version, might there be offending code preceding your setReadOnly that would cause Javascript to stop its processing? Some context would be nice preceding the setReadOnly statement.

Migrateduser

I wasn't clear before -- what I mean is this: if you have code prior to setReadOnly that is causing this discrepancy, that would cause Javascript to exit that routine and not return the result you're expecting. However, all we know in DevNet-land is your setReadOnly statement.

So, if you had the following code (on both machines, it doesn't matter):

[color=red]line 10: var something = someFunctionThatOffendsSP1(item);[/color]
...
[color=red]line 20: api.IWDatacapture.getItem("/COMP").setReadOnly(false);[/color]

Your SP2 instance would run through all of the code, no problems. However, your SP1 instance would bug out at the line marked "line 10", above and not run anything from line 11 on. That's why I'm asking for some context.

Otherwise, I'm wondering why you're escaping the quotation marks in getItem(\"/COMP\"). I can't think where this is necessary but it also doesn't seem to me that this would cause a problem, either.

kaalraa

Dave,

As earlier also .. i had understood your comments... no problems on that front. Also to be more clear ... i have debug both files a lot placing alerts in js file and logging line by line in cgi file.

At last... i found that it is moving ahead on both machines pretty well .. without any failure... BUT the only difference is on SP2 machine... it does set read only field.... whereas in SP1 machine... it is giving error as a javascript warning error {'datacapture' is not defined}.

And for surprises.. there is no whole word called as 'datacapture' in both of the files.

Migrateduser

How are you defining "api"? I happen to be on SP1 and I declare it with the following:

api = parent.getScriptFrame();

So, what happens if you were to do "alert(api)" right before your setReadOnly statement? I'm wondering if JS even recognizes it as an object.

kaalraa

I declare it same as you have written... no change in that.

Also as far as object recognising api object is concerned.... it is working fine for other methods and procedures as expected. I am also doing getItem, redraw, setHighlightMode etc.. with in the same function where i am using setReadOnly.

How are you defining "api"? I happen to be on SP1 and I declare it with the following:

api = parent.getScriptFrame();

So, what happens if you were to do "alert(api)" right before your setReadOnly statement? I'm wondering if JS even recognizes it as an object.

Migrateduser

Okay, this is starting to bug me (as I'm sure it's been bugging you for a while). Could you post your DCT and any other applicable code (like this script, for instance) so I can see if I could find anything. The release notes for SP2 don't mention anything about setReadOnly().

kaalraa

Yeah... i have also gone thru Release Notes... and it only says so for the buttons

54773 FormAPI: setReadOnly() doesn’t properly disable buttons on replicant instances.

As per code is concerned... it is a bunch of files interrelated to each other and as per privacy contract ... i am not able to attach that. Sorry on that !!

Okay, this is starting to bug me (as I'm sure it's been bugging you for a while). Could you post your DCT and any other applicable code (like this script, for instance) so I can see if I could find anything. The release notes for SP2 don't mention anything about setReadOnly().

Migrateduser

I understand about the privacy stuff, etc.

I don't find that at all in either the SP1 or SP2 release notes. What page are you on (presumably in the SP2 release notes)?

It sounds like you're doing the right thing giving frequent alerts to debug the code but what about alerting:

alert(api.IWDatacapture.getItem("/COMP").isReadOnly());

Again, I'm still unclear as to why you're escaping the quotation marks.

kaalraa

Dave,

I am looking at Release 6.1.0 Service Pack Version 2 page 25. I will try alerting the readonly command as well.

As far as escaping the quotation marks is concerned it is used... because of the api is being called from a cgi file as:

print "api.IWDatacapture.getItem(\"/COMP\").setReadOnly(false);\n";

I hope ... print command should not have any issues.

I understand about the privacy stuff, etc.

I don't find that at all in either the SP1 or SP2 release notes. What page are you on (presumably in the SP2 release notes)?

It sounds like you're doing the right thing giving frequent alerts to debug the code but what about alerting:

alert(api.IWDatacapture.getItem("/COMP").isReadOnly());

Again, I'm still unclear as to why you're escaping the quotation marks.

Migrateduser

OH, I'm sorry. For whatever reason, I thought you were referring to 6.5 even though you very clearly stated that you were on 6.1. Your usage of the escape character makes complete sense when you put it in context, but I'm afraid there's not much more I can say about this issue. I don't have a 6.1 box to test stuff out on and I think you'll get what you need by using excessive JS alerts.

Please post the solution when (not if, but when) you find out what the problem is.

Dave

kaalraa

Thanks Dave,

Anyways ... i will definitely let you know the solution.....

OH, I'm sorry. For whatever reason, I thought you were referring to 6.5 even though you very clearly stated that you were on 6.1. Your usage of the escape character makes complete sense when you put it in context, but I'm afraid there's not much more I can say about this issue. I don't have a 6.1 box to test stuff out on and I think you'll get what you need by using excessive JS alerts.

Please post the solution when (not if, but when) you find out what the problem is.

Dave

Adam Stoller

As far as escaping the quotation marks is concerned it is used... because of the api is being called from a cgi file as:

print "api.IWDatacapture.getItem(\"/COMP\").setReadOnly(false);\n";

For future reference - I'd recommend using the q{} or qq{} syntax like:

print qq{api.IWDatacapture.getItem("/COMP").setReadOnly(false);\n};

as it makes it much easier to have embedded quotes within the string you're printing - especially if you need both single and double quotes within the string:

print qq{Isn't this "nice"?\n};

(Note: you can use other delimeters besides '{}' - like '()', '||', etc)

As for the problem at hand - can you create a simplified version of the DCT and JS files that replicate the behavior you're seeing? If so - you should be able to (a) post it and (b) submit it to IWOV Support.

kaalraa

All,

Resolved the issue... may be it is about SP or what ... not aware... but it worked after reordering of the commands.

Earlier order:
setReadOnly
setValid
setFocus

Changed Order:
setValid
setFocus
setReadOnly

Now this is working on both machines with SP1 and SP2. Cheers !!

piesum.rptdesign