DCR Save using a field value w/o overwrite

I am using the built-in teamsite function inorder to save DCR using a DCT field value. However, I am having hard time in figuring out how to restrict the save function not to overwrite an existing DCR having the name identical to a field value in a brand new DCT. Is there a built-in function to restrict the iwdatacapture.save() not to overwrite same name dcrs?

Find more posts tagged with

Comments

cute_guy

I am using the built-in teamsite function inorder to save DCR using a DCT field value. However, I am having hard time in figuring out how to restrict the save function not to overwrite an existing DCR having the name identical to a field value in a brand new DCT. Is there a built-in function to restrict the iwdatacapture.save() not to overwrite same name dcrs?

Why not use event handlers in form api to achieve what you want?

Adam Stoller

I am using the built-in teamsite function inorder to save DCR using a DCT field value. However, I am having hard time in figuring out how to restrict the save function not to overwrite an existing DCR having the name identical to a field value in a brand new DCT. Is there a built-in function to restrict the iwdatacapture.save() not to overwrite same name dcrs?

You need to use an onSave event handler which uses a callServer() script - pass in the parameters such as the proposed name and location of the DCR - check it in the script (which runs server-side) and then, if it's okay - do the IWDatacapture.save(). If it's not okay - you can either modify the proposed name programmatically or callback to an error function in the FormAPI code to display a message indicating that the name is already in use and that the user needs to change something in order to come up with a unique name.

ISCBorisB

I am using the built-in teamsite function inorder to save DCR using a DCT field value. However, I am having hard time in figuring out how to restrict the save function not to overwrite an existing DCR having the name identical to a field value in a brand new DCT. Is there a built-in function to restrict the iwdatacapture.save() not to overwrite same name dcrs?

Are you using setDCRName? If so, you may use its callback Function, see for example here.
With this approach all can be done locally, you do not have to code any server-side scripts, etc.

enthusiast

I did some thing like that but incase of the valid save i.e. a new dcr with no name match, the save button has to be pressed twice before the dcr save actually happens. The status bar message however comes up in both cases. Here is the snippet from DCT:

IWEventRegistry.addFormHandler("onSave", checkDCRName);
IWEventRegistry.addFormHandler("onSaveDone", saveDone);

function checkDCRName()
{
var pathNew = IWDatacapture.getItem("/question/classification/class");
var classLabel= pathNew.getOptions()[pathNew.getValue()].text;
var data = new Object();
data.dcrName = classLabel;
data.path = '/question/classification/class';
IWDatacapture.callServer("/iw-bin/Custom/redesign/checkClassDCRName.ipl", data, true);
}

// This function is called from PERL Script after successfull setting of DCR Name
function finalize()
{
IWDatacapture.save();
}

function saveDone(success)
{
if (! success)
{
alert("The save did not succeed ...");
}
}

Here is the snippet from the perl script:

function checkVal (path, val, flag)
{
var item = api.IWDatacapture.getItem(path);

if (flag) //dcr exists
{
item.setValid(false);
api.IWDatacapture.displayMessage("The classification name already exists!! Please select a different classification.");
}
else
{
item.setValid(true);
api.IWDCRInfo.setDCRName(val, api.finalize());
api.IWDatacapture.displayMessage("The '"+val+ "' is saved successfully.");
}

}

Any help would be greatly appreciated.

Adam Stoller

Are you using setDCRName? If so, you may use its callback Function, see for example here.
With this approach all can be done locally, you do not have to code any server-side scripts, etc.

Hmm - I keep forgetting about that - partially because the information about the callback function seems only vaguely covered in the documentation - and partially because it's essentially a built-in callServer script - because it's also asynchronous ... however, it's probably a generally cleaner solution if you don't want to do any other custom stuff in your naming routine.

enthusiast

I removed the finalize() function and added the code instead in the perl like the following:

api.IWDCRInfo.setDCRName(val);
api.IWDatacapture.save();

and its now seems to be working. However, one small issue is that it doesn't allow edited dcrs to be resaved and is prompting with the message that was suppose to appear for the existing dcrs. Is there a way to know if a dcr is newly created or edited?

enthusiast

Are you using setDCRName? If so, you may use its callback Function, see for example <a href="http://devnet.interwoven.com/forums_vb/showpost.php?postid=98599" target="_blank">here</a>.
With this approach all can be done locally, you do not have to code any server-side scripts, etc.

It worked perfectly. Thanks for your help.

Adam Stoller

I removed the finalize() function and added the code instead in the perl like the following:

api.IWDCRInfo.setDCRName(val);
api.IWDatacapture.save();

and its now seems to be working. However, one small issue is that it doesn't allow edited dcrs to be resaved and is prompting with the message that was suppose to appear for the existing dcrs. Is there a way to know if a dcr is newly created or edited?

I'm not sure if your second response indicated that this issue was resolved - but if you do a getDCRName() first - and it comes back with a value - then you don't need to do the setDCRName(val) piece - because the DCR was already saved with a name.