DCR refresh

I edit a DCR by clicking on edit link. I have a callout button

[HTML]

[/HTML]

I do some activities in the CGI. Once I say submit the CGI should close by refreshing DCR.

I am able to close CGI (:-))). But stuck with refreshing DCR, how can I do that any ideas ?

I tried with (opener.top.datacapture.refreshForm() and with (alert(parent.window.opener.top.getScriptFrame().IWDatacapture);//.refreshForm()
No success.

[size=2]Thanks,
[/size]

opener.top.datacapture.refreshForm(); is the correct syntax. Something else is probably happening (or not happening)
so that your DCR stays visually unchanged. What are you trying to do? How do you modify DCR prior to issuing refresh?

opener.top.datacapture.refreshForm(); is the correct syntax. Something else is probably happening (or not happening)
so that your DCR stays visually unchanged. What are you trying to do? How do you modify DCR prior to issuing refresh?

Inside Chooser.cgi? I have two select boxes say A and B. In "A" I populate with some existing items from the DCR, and in "B" I give some items which user can include dynamically into DCR by pushing from B select box to A select box.

I am able to add New List ( those he takes from

to the DCR. I need to refresh the DCR form, once the CGI closes by doing all manipulation. So that the User can seenew items which he has added dynamically.

Hope I have explained my requirement !

Thanks for your Help !!.

Ok. Long story short, here is what I've read so far:

>> I am able to add New List...to the DCR.
>> I tried with opener.top.datacapture.refrefreshForm();... No success.

If you are able to modify your Opener (DCR), why would you need a refresh? What is the problem manifestation?
What's wrong?

Ok. Long story short, here is what I've read so far:

>> I am able to add New List...to the DCR.
>> I tried with opener.top.datacapture.refrefreshForm();... No success.

If you are able to modify your Opener (DCR), why would you need a refresh? What is the problem manifestation?
What's wrong?

I add Empty items, once the user submits the CGI, the DCR has to be refreshed to appear those new items into the DCR form and the user has to fill in whatever he wants into newly included fields.

Ok. Long story short, here is what I've read so far:

I am able to add New List...to the DCR.

I mean I add empty DCR Items where user can fill in some data by refreshing DCR form once my CGI closes.

>> I tried with opener.top.datacapture.refrefreshForm();... No success.

with this DCR form is not getting refreshed.

If you are able to modify your Opener (DCR), why would you need a refresh?

To avoid user's manually refreshing DCR form once my CGI closes.

I hope, now the things are clear why I need refresh or reload.

I add Empty items, once the user submits the CGI, the DCR has to be refreshed to appear those new items into the DCR form and the user has to fill in whatever he wants into newly included fields.

What do you mean by adding empty items?
Are these items that are part of the DCT or are you trying to modify the DCT via your callout?
Are these individual items or instances of replicants?
Can you provide a more detailed / contextual use-case scenario?

What do you mean by adding empty items?
Are these items that are part of the DCT or are you trying to modify the DCT via your callout?
Are these individual items or instances of replicants?
Can you provide a more detailed / contextual use-case scenario?

Let me explain in clear

1. I have DCT ready inside a category/datatype
2. I create DCR using some ipl with filled data in it.
3. I send above DCR link to the user via email to edit that DCR
4. I give option to the user to add few more empty items (fields) to the DCR on callout of a button.
5. To give empty fields (input text boxes) I have a .xml files stored in a folder
6. On click of above button in a select box I populate file names (The fields which he wants to include inside his DCR) by reading above folder. He selects some labels (file names) which he wants to include.
7. Once he clicks Populate on CGI, I add empty fields to the DCR which I have created using above ipl like [HTML] [/HTML].
8. To do this I collect all the file names (labels) which the user has selectd in the CGI in a variable inside CGI.
9. Using DOM parser I add these new nodes to DCR xml as said above (Empty fields) in the Backend.
10. Once all is done user should be able to see all these empty fields to fill inside his DCR. For this purpose I want to refresh DCR once I populate DCR with new empty fields.

Now I have implemented whole stuff, when I refresh by pressing (F5) function key. I am able to see those empty fields (items) inside DCR. I have DCT coded accordingly.

I don't want users to press F5 every time they include their needed empty fields, insted I want to refresh the DCR programatically.

I hope I am clear now.

Thanks for the help!

7. Once he clicks Populate on CGI, I add empty fields to the DCR which I have created using above ipl like ...

Fish already asked that but you did not answer. So, let me reiterate:

Does your CGI callout modify DCT (not DCR, DCT!) as well?
Are inserted empty items instances of some replicant(s)?

...7. Once he clicks Populate on CGI, I add empty fields to the DCR which I have created using above ipl like [HTML] [/HTML].

In this example - is width defined in the DCT - or are you trying to add an element that is not defined in the DCT?

If width is defined - you shouldn't have to add it - it should be available.
If width is not defined - you cannot add it in a supported manner because the DCT - which is used to render the contents of the DCR doesn't know anything about it.
(note: If you physically add it the DCR without adding it to the DCT - it will get removed the next time you save the DCR)

It sounds very much like you're trying to provide ad-hoc on-the-fly DCT modifications through the DCR using a callout to provide the interface. It's an interesting, but questionable, idea. If you really want to do this it means you have to allow the callout to not only modify the DCR, but to modify the DCT as well - and you could quite possibly "break" the DCT and thereby not be able to edit any of its DCRs - and then there's the potential question about PT code and FormAPI code which might need to be dynamically modified as well.... sounds like a big can-o-worms to me ... If I understood what you wanted correctly, I suggest you seriously re-think it.

Fish already asked that but you did not answer. So, let me reiterate:

Does your CGI callout modify DCT (not DCR, DCT!) as well?

I modify only DCR not DCT. DCT is ready with all fields which are needed.

Are inserted empty items instances of some replicant(s)?[/QUOTE] No.

W,r,t my post I am done with all stuff Like DCT, adding empty fields (no value in it) to DCR, handling all stuff which I need using JS (I mean hidding fields which i don't want). To make availability of those empty fields, which I have added to DCR, I am refreshing DCR window manually. I don't want our users to refresh manually, instead I want to achieve through programatically inside my CGI.

And, I am not adding any empty fields to DCR which are not defined in the DCT. I am adding only those fields which have been defined inside datacapture.cfg.

Everything is working just I need to refresh DCR once callout is done (before or after CGI closes).

Thanks You!

I modify only DCR not DCT. DCT is ready with all fields which are needed.
Are inserted empty items instances of some replicant(s)?
No.

W,r,t my post I am done with all stuff Like DCT, adding empty fields (no value in it) to DCR, handling all stuff which I need using JS (I mean hidding fields which i don't want). To make availability of those empty fields, which I have added to DCR, I am refreshing DCR window manually. I don't want our users to refresh manually, instead I want to achieve through programatically inside my CGI.

And, I am not adding any empty fields to DCR which are not defined in the DCT. I am adding only those fields which have been defined inside datacapture.cfg.

Everything is working just I need to refresh DCR once callout is done (before or after CGI closes).

Thanks You!

I'm still confused. If the fields are already defined in the DCT - are they simply "hidden" and your callout is being used to make them "visible"?

If that's the case - how are they hidden? hard-coded in the DCT or dynamically hidden on form loading via FormAPI?

If the former - then FormAPI might make them visible, but they'll be hidden the next time you load or refresh the window.

If the latter - it should be trivial to have your CGI issue the correct FormAPI code to make them visible.

I'm still confused. If the fields are already defined in the DCT - are they simply "hidden" and your callout is being used to make them "visible"?

Callout does nothing w,r,t DCT. It only adds empty fields like,
foreach my $list (@newAdditionList ) {
my $itemNode = $root->createElement("item");
$itemNode->setAttributeNode($root->createAttribute("name"));
$itemNode->setAttribute("name",$list);
my $AddValueNode = $root->createElement("value");
my $textNode = $root->createTextNode("yes");
$AddValueNode->appendChild($textNode);
$itemNode->appendChild($AddValueNode);
$innerValueNodeItem->appendChild($itemNode);
} where $list is the new list of fieds which the user wants to add to DCR from the backend. My question is how can refresh my DCR to show them up ?

If that's the case - how are they hidden? hard-coded in the DCT or dynamically hidden on form loading via FormAPI?

My DCT is ::
[HTML]

Performance - Rating Specific

[/HTML]
Syntax might be incorrect purposely I have removed. Here test.pl adds 10 DCT items. I create my DCR from a perl program in a workflow, while doing so out of 10 depending upon some condition I include only few items out of 10. When the email goes to author containing edit link to this new DCR, he edits to fill in values. He will will see only those items which the perl program has included depending upon some condition, rest will be hidden using FormAPI.

Now my callout comes, if the user wants few more out of 10 other than those which have been included from perl program. He selects few which he wants and says include. I include them from the backend to DCR, now he should be able to see them inside DCR form. Now its happening on press of F5 (refresh) function key. I want to refresh of reload via my CGI, so that once the CGI closes user should have new fileds available in the DCR form.

If the former - then FormAPI might make them visible, but they'll be hidden the next time you load or refresh the window
If the latter - it should be trivial to have your CGI issue the correct FormAPI code to make them visible

When I say alert(opener.top.datacapture) it alets with [object object]. I mean two object array. Don't know much about this.

Thanks,

Callout does nothing w,r,t DCT. It only adds empty fields like,[ ... ] where $list is the new list of fieds which the user wants to add to DCR from the backend. My question is how can refresh my DCR to show them up ?

My DCT is ::[HTML]

Performance - Rating Specific

[/HTML] Syntax might be incorrect purposely I have removed. Here test.pl adds 10 DCT items. I create my DCR from a perl program in a workflow, while doing so out of 10 depending upon some condition I include only few items out of 10. When the email goes to author containing edit link to this new DCR, he edits to fill in values. He will will see only those items which the perl program has included depending upon some condition, rest will be hidden using FormAPI.

If your inline dynamically determines which of the 10 fields to add (e.g.: A and B but not C through J) - and your CGI allows someone to "add" H - it won't work - the DCT that was generated with the inline script doesn't know anything about H.

The inline script should insert all 10 fields and the FormAPI code should hide C through J - then your CGI can make any one of those fields visible again.

How you make the initial FormAPI code savvy enough to only mark the desired fields visible or invisible based on prior-to-form-initialization logic I'm not sure ... a callServer script might do it - but as that's asynchronous it could prove tricky getting the timing right. You might be able to inject extra parameters into the URL used for launching the edit session and then in the FormAPI code access those parameters from the URL (this would seem the way to go, but I've never attempted it, so I'm not sure).

In either case, you'd probably want the FormAPI to only mark those fields as invisible if they don't already contain a value -or- mark them visible if they do contain a value (depending on whether you hide or expose them dynamically on loading the form)

Once you get this working - the code in your CGI changes from modifying the DOM to manipulating the visibility of fields of data already in the DOM, and you won't have to worry about the refresh - it should happen automatically.

Thinking about it some more - if you programmatically build the DCR prior to it ever being edited (i.e. it's never really New Form, it's Edit DCR) - then you can programmatically add the N-of-10 fields you want exposed initially with an empty string for value (

not

) and your FormAPI code can check all 10 of the items and if they have a value (even just a space) mark them visible, otherwise mark them invisible.

I suggest you think about this a bit more and see if you can re-engineer your design in a manner as suggested above (or similar)

The problem was little different. I found a solution to my problem. Once I am done with all operation inside callout CGI. I call a JavaScript function(newDCRWindow) which is defined inside DCT. The code of the function is

[HTML]
function newDCRWindow() {
var server = window.location.hostname;
var path = "http://" + server + "/iw-cc/command/iw.group.ccpro.edit?vpath=";
var dcrPath = IWDatacapture.getDCRPath();
var fullPath = path + dcrPath;
window.open(fullPath);
top.window.close();
return true;
}
[/HTML]

Here I am reloading entire DCR in edit mode by closing previously opened same DCR. Through this I am able make my newly added fields editable (visible).

The problem I am facing is top.window.close() or IWDatacapture.close() shows a confirm message asking "yes" or "no" to close. How can avoid this ?

I did make some search in google did not find any way to aviod that confirm message, if any one can help will be great help.

Thanks,

Without commenting on the merits of your approach in general I would recommend to modify your code slightly.

Note that it's not just couple lines shorter. Changes make your code more portable. Various TS Environments
like Development, UAT, Production and whatnot may have different settings. That includes protocols (http/https),
non-standard iwwebd Ports (not only 80/443) and so on. Modified code will work in all this cases without any changes.
Another change I've made is the use of supported CC URL Edit instead of hacked ccpro command Id that you used.

function newDCRWindow() {
   var fullPath = '/iw-cc/edit?vpath=' + IWDatacapture.getDCRPath();
   window.open(fullPath);
   top.window.close();
   return true;
}

The problem I am facing is top.window.close() or IWDatacapture.close() shows a confirm message asking "yes" or "no" to close. How can avoid this ?

Who's asking, TS or Browser? In other words, is your message

    Do you want to close the Form? (Yes | No)
OR
    The Web page you are viewing is trying to close the Window.
    Do you want to close this Window? (Yes | No)