All examples of custom statements in both Pan6 and PanX show the parameter name and type definitions in upper case, as in
<parameter NAME=FIRSTNUM TYPE=TEXT> The first number. </parameter > < parameter NAME=SECONDNUM TYPE=TEXT> The second number. </parameter > < parameter NAME=TOTALNUM TYPE=TEXT> The sum of the two numbers. </parameter >
In fact, in both versions, a custom statement works fine if all of this is in lower case. Is there a reason to use upper case (I’m primarily concerned with PanX)?
There are several new tag sets in PanX procedure info blocks, and I’m confused as to what values to enter into the and , tags of a new statement. Their format and purpose is clear but there appears to be little consistency across existing entries with considerable variation occurring even between a statement and its function - see
arayfilter( for example. It looks to me like a good idea that got out of its cage and is now running wild. Are there any guidelines for their content or do we just try to make the entries as meaningful and useful as possible?
My understanding is that we should use only the following tags in a procedure info block and that the tags should not include chevrons:
<procedureinfo> <description> <breadcrumb> <tags> <parameter> <body> <errors> <seealso> <history>
Is that correct?