form api

sorry here is the attachments.

That error has nothing to do with your API -- it has everything to do with templating.cfg, I believe. Is your entry correct?

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

hi dave and everybody,
yes if i exclude the form API script then it works perfect.

any advise?

spiderman

Just curious, has any one configured the iw.cfg for formAPI?
enable_foemapi=true
in your iw.cfg?

Hey dave is this right?

var startItem = IWDatacapture.getItem("/newsPubDate").getValue();

var endItem = IWDatacapture.getItem("/newsExpDate").getValue();

var startDate = Date.parse(startItem);

var endDate = Date.parse(endItem);

if (startDate.getTime() > endDate.getTime()) { is this line valid?? your startDate and endDate both are strings, so how could they call getTime()?

startItem.setValid(false); Your startItem is nothing but a string, so how could you call .setValid() on it??

I think what you were probably trying to do is following:

var startItem = IWDatacapture.getItem("/newsPubDate");

var endItem = IWDatacapture.getItem("/newsExpDate");

var startDate = new Date(startItem.getValue());

var endDate = new Date(endItem.getValue());

if (startDate > endDate) {

startItem.setValid(false);
...........
}

These are just few problems I discovered in your code, not sure though if this is what was causing your "category/template" error. That definitely does not sound like a FormAPI error.

What version are you referring to? I've never seen that before and I checked the 6.1 and 6.5 admin documentation -- not there, either.

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

I'm not sure -- he's got var startDate = Date.parse(startItem); there already and I believe that takes care of the date parsing thing. I believe he's able to compare the two strings as dates after that point, no?

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

spiderman

I am refering to TS 6.5, there is no mention of something like
"enable_formapi=true"
this wonders me when some one says that they have it in 6.5.

var startDate = Date.parse(startItem); is right but he's again doing startDate.getTime()>endDate.getTime()
I don't think you can call getTime() on a string(?)

thanks cliff,

now if i have start date is > end date it highlights the start item fields and prompts me to fix it but after fixing , if i want to save,save as, preview the form , it won't let me to do anything.

any suggestions?

here is my new dct with form api script

if the start date is invalid you do a startDate.setValid(false), I think you need to explicitly do startDate.setValid(true) when they do enter a valid date after entering an invalid date

Sorry, maybe I misunderstand -- or, maybe we're in complete agreement. You asked if anyone had put this in iw.cfg? Previously, I was referring to templating.cfg and the error that madmax was getting looks as though the configuration wasn't set properly for that DCR type.

Is that what you mean?

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

No, I think he's right there, too. I haven't used this API yet, but I'm getting this from the 6.5 FormAPI manual, page 28. In fact, it looks as though madmax may have gotten the code from there, too


function validateForm() {
// Assume that the form is valid.
var result = true;
// Get handles for the start and end date items.
var startItem = IWDatacapture.getItem("/start");
var endItem = IWDatacapture.getItem("/end");
// Create date objects for the start and end dates.
var startDate = Date.parse(startItem.getValue());
var endDate = Date.parse(endItem.getValue());
// Is the start date after the end date?
if (startDate.getTime() > endDate.getTime()) {
// Yes. Set the start date as invalid.
startItem.setValid(false);
// Go into highlight mode.
IWDatacapture.setHighlightMode(true);
// Redraw the form to show the new label.
IWDatacapture.redrawLabels();
// Inform the user of the error.
alert("Start date cannot be after end date.");
// Return false to terminate the save.
result = false;
}
return result;
}

Okay, so I guess you don't need to check page 28, because there it is!

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

hmmmmmm

I ran his code in my System(6.1 SP1) and it gave me a JavaScript error when I did getTime() on the startDate when startDate equalled
Date.parse(Item.getValue())

spiderman

No Dave sorry for the whole confusion, I was wondering if there is any thing like "enable_formapi=true" in iw.cfg file in TeamSite 6.5?

Oh, I see. No, there's no setting for that in 6.5's iw.cfg. FormAPI is native to TeamSite and is enabled by default (I can't imagine why someone would want to disable it -- it's optional, after all).

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

Oh... < sarcasm > do you mean the documentation may have been wrong???? < /sarcasm > I've already trashed IW's documentation 3 times today in other posts and I have to assume that this is the last one for today

I'm actually surprised at this -- what does the error message say? Like I said, < disclaimer > I haven't had need for this function yet, so I speak only from the documentation and not from experience < /disclaimer >.

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3

hi cliff,

u r right i have to do explicit startItem.setValid(true); i am working on it.

but if anybody comes up with anything then it'll be great.

Adam Stoller

We have a couple of functions defined in our global.js file that we include in all our DCTs that do a nice job:function showInvalid(itemInvalid) {
itemInvalid.setValid(false);
IWDatacapture.setHighlightMode(true);
IWDatacapture.redrawLabels();
}
function showValid(item) {
item.setValid(true);
IWDatacapture.setHighlightMode(true);
IWDatacapture.redrawLabels();
}The redrawLabels() function is not needed in 6.5 it's apparently automatic now and the redraw() and redrawLabels() functions are no-ops.
These two functions (showValid, showInvalid) come in handy in all sorts of places - essentially any place you would call setValid() you can replace it with one of these two functions and it takes care of setting the validity flag and highlighting or unhighlighting the field in the DCT form.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

srcasm noted Smiley Happy

it gives me "property/method not supported for this object" error(don't remember the exact wording- at home now....so can't even check it out.....). when I tried debugging the error in the debugger it points to startDate.getTime()

doing setValid(true) should be a quick thing to do....

You already have a if statement in which you set .setValid(false), you can have an else statement for it where you would set .setValid(true).

Even if the user doesn't enter invalid data, this forced .setValid() wouldn't harm your save process.

i have add the else statment at the bottom of my script , now it's acting weird. it's saving the dct without the form api code executions. i put some alert in my form api they r not executing at all.

help needed.

i am attaching the new datacapture.cfg

sample.jpg

You can't put anything between your } and your else, namely the alert('hallo5') that you have there, but I'm guessing you had put it there in the first place because there was an error?

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3