> > just a simple question for Custom Fields: > > Can a Custom Field be 'validate', and non-mandatory? > > This means, only a check that the content is a Number and > nothing else > but > > not needed or mandatory? > > Actually, we are just in the process at where I work of > modifying RT to > make "Mandatory" a completely separate checkbox to format validation > partly for this very reason. We want all this in the core API so it's > enforced for all interfaces (GUI, REST, Email ...) and so "being > mandatory" is completely separate from "matching a certain pattern". > There are a few reasons why this makes sense and it's really important > when using RT in an audited change management environment. We'll > probably be posting the patches when it's done (fairly soon). > > PK
I thought that using the current interface, if you wanted to make something non-mandatory, you could just wrap a '()?' around it (not including quotes)? I'm pretty sure I've seen that posted to the mailing list as well. Eric Schultz United Online _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
