<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>I need to have the
REST interface enforce various CF things like:</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>* Mandatory
CFs</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>* CF validation
other than mandatory</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>* Reject CF values
for Select* fields which are not valid for the field</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>I have all of this
working for AT and am working on adding it to RT (for tickets anyway). I will
submit a patch when done. I wanted to get opinions on this
though:</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>When creating a
thing (asset, ticket etc.). The current behaviour I have is:</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>* If a mandatory CF
is not present, give error and don't create.</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>* If a CF isn't
mandatory but a/the passed value doesn't match the validation string, don't
update the CF but still create the object.</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>* If a Select* CF
has no validation string but a/the passed value doesn't match any of the
possible values, don't update the CF but still create the
object.</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial size=2>I was wondering if
this was reasonable? I am in two minds about rejecting all creation attempts by
REST which fail any of these criteria. The mandatory case if obvious - that's
what mandatory means and this is really important for things like SOX audit -
you simply must be unable to create something without the mandatory CFs. But the
other two cases are less obvious. The GUI won't let you create these last two so
I supose it should be consistent.</FONT></SPAN></DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=046231201-24122006><FONT face=Arial
size=2>PK</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV align=left><FONT face=Arial size=2>--</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Philip Kime</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>NOPS Systems Architect</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>310 401 0407</FONT></DIV>
<DIV> </DIV></BODY></HTML>