FormsPublisher DCT - callouts for other DCRs

Adam Stoller · 2014-10-07T17:16:26+00:00

Environment: TS 7.3.2 on Linux Scenario: * My DCT [optionally] references another DCR (of a sepcific type) for some of its data. As such we have a 'browser' item for finding the DCR to reference. * I would like to add two additional buttons for this item(*) to allow for either editing of an already selected DCR or creation…

Adam Stoller

Environment: TS 7.3.2 on Linux

Scenario:

My DCT [optionally] references another DCR (of a sepcific type) for some of its data. As such we have a 'browser' item for finding the DCR to reference.
I would like to add two additional buttons for this item(*) to allow for either editing of an already selected DCR or creation of a new DCR of the same type.
It's been a while since I've done this kind of thing, and while I have part of this enabled, there are still some issues I'm hoping to get some guidance on (pointers to documentation is fine, code snippets are obviously fine too :-)

Existing Code:

<!-- 1st Pass DCT snippet --><item name="ref_dcr" pathid="ref_dcr">
  <browser initial-dir="..." ceiling-dir="..." extns=".xml">
    <callout label="New"/>
  </browser>
</item>

<!-- 2nd Pass DCT snippet (current) --><item name="ref_dcr" pathid="ref_dcr" rowcontinue="t">
  <browser initial-dir="..." ceiling-dir="..." extns=".xml"/>
</item>
<item name="new_dcr" pathid="new_dcr" rowcontinue="t">
  <hidden><callout label="New"/></hidden>
</item>
<item name="edit_dcr" pathid="edit_dcr">
  <hidden><callout label="Edit"/></hidden>
</item>

// 1st pass FormAPI snippets
function init() {
  ... 
  IWEventRegistry.addItemHandler("/root/ref_dcr", "onCallout", newDCR);
  ...
}
function newDCR(item) {
  var wa = IWDatacapture.getWorkarea();
  var url = "/iw-cc/newform?vpath="+wa+"&iw_tdt=****/yyy" +  
            "&done_page=refresh_parent_and_close_window.html"; 
  window.open(url, "New ****/yyy DCR");
}

// 2nd pass FormAPI snippets (current)
function init() {
  ... 
  IWEventRegistry.addItemHandler("/root/new_dcr", "onCallout", newDCR);
  IWEventRegistry.addItemHandler("/root/edit_dcr", "onCallout", editDCR);
  ...
}
function newDCR(item) {
  var dcrItem = IWDatacapture.getItem("/root/ref_dcr"); /* currently unused */
  var wa = IWDatacapture.getWorkarea();
  var url = "/iw-cc/newform?vpath="+wa+"&iw_tdt=****/yyy" +  
            "&done_page=refresh_parent_and_close_window.html"; 
  window.open(url, "New DCR");
}
function editDCR(item) {
  var dcr = IWDatacapture.getItem("/root/ref_dcr").getValue();
  if (dcr.match(/^\s*$/)) {
    alert("...");
    return false;
  }
  var wa = IWDatacapture.getWorkarea();
  var url = "/iw-cc/edit?vpath=" + wa + dcr +
            "&done_page=refresh_parent_and_close_window.html";
  window.open(url, "Edit DCR");
}

Issue / Query:

On completing the creation of the new DCR, and clicking Finish the window closes. Great, but I want to get the rel-path/name of the new DCR and fill it into the field in the "main" DCT

Once I have the information populating the field should be trivial, however I cannot recall how to get that information (and a quick glance at the UICG didn't seem to help)

Find more posts tagged with

Comments

Rick Poulin

Since your new DCR would be operating in a child window, you can probably catch the onSaveDone event and call your top form with opener.top.getScriptFrame().IWDatacapture.getItem('/blah').setValue(IWDCRInfo.getDCRPath());

..or at least that's what I'd try first, before anything more complex.

Adam Stoller

Excellent - I'll give you props on this (you were real-close), but I'll post the actual code for others to reference:

"Parent" FormAPI:

function init() {
    IWEventRegistry.addItemHandler("/root/****/new_dcr", "onCallout", newDCR);
    IWEventRegistry.addItemHandler("/root/****/edit_dcr", "onCallout", editDCR);
}

function newDCR(item) {
    var wa  = IWDatacapture.getWorkarea();
    var url = "/iw-cc/newform?vpath=" + wa + "&iw_tdt=cat/dtype&done_page=refresh_parent_and_close_window.html";
    window.open(url, "New DCR");
    return true;
}

function newDCRCallback(val) {
    IWDatacapture.getItem("/root/****/dcr").setValue(val);
}

function editDCR(item) {
    var dcr = IWDatacapture.getItem("/root/****/dcr").getValue();
    if (dcr.match(/^\s*$/)) {
        alert("You must browse and select a DCR before you can edit it");
        return false;
    }
    var wa  = IWDatacapture.getWorkarea();
    var url = "/iw-cc/edit?vpath=" + wa + dcr + "&done_page=refresh_parent_and_close_window.html";
    window.open(url, "New DCR");
    return true;
}

"Child" FormAPI:

function init() {
    IWEventRegistry.addFormHandler("onSaveDone", saveDoneHandler);
}

function saveDoneHandler() {
    try {
        var api = parent.opener.top.getScriptFrame();
        var dcrPath = IWDatacapture.getDCRPath().replace(/^.*\/WORKAREA\/[^\/]+/, "");
        api.newDCRCallback(dcrPath);
        return true;
    }
    catch(err) {
        console.log(err.message);
        return false;
    }
}
I've done some limited testing and it looks like it works when the "child" DCT is opened by itself, as well as when it is opened via the callout from the "parent".

In the case of the latter - when the "save" is done (either via the Save or Finish options) on the "child" Edit DCR window, the callback updates the appropriate field in the "parent". I could have put the code for updating the field in the "child"s FormAPI code - but I felt it was better to use a known-name callback function and keep the specifics of the location of the field to update in the "parent".