Working with CI templates is similar to working with the Staff Interface templates. The are composed of JavaScript and HTML with "##" tags interspersed. A "##" tag represents a substitution marker. bmui.cgi will substitute values for the "##" tags as the template a processed. A "##" tag spans from the "##" to the the terminating "#". An example is "##DSERVICE_number#" for which bmui.cgi will substitute the number of a Service. The following tags are supported:

For "##" tag F, if the name of the tag is followed by "_list", then an HTML dropdown list is displayed using the List referenced in the "##" as the source for the dropdown list. As an example, ##Fpaytype_list# will cause the entries from the paytypes list to be displayed.

	Note
	Note that the name of the list without the trailing "s" is used in the tag name.

For "##" tag F, if the name of the tag is followed by "select?", then an HTML dropdown list is displayed using the POP entries from the selected POP if the name of the tag was included in the hidden variable "POP_FIELDS". As an example, ##FPHONENUMBERselect# will cause the PHONENUMBER entries from the POP data for a specific POP to be displayed if PHONENUMBER was also part of the "POP_FIELDS" form variable.

A "##" tag may be qualified by (EDATE) specifying that field should be treated as a date and the date be split into year, month and day fields and the BillMax calendar icon be displayed. As an example, ##F(EDATE)enddate#.

By default, registration of a new customer associates the customer with the smallest number BillMax Virtual Company. Associating a new Account with a specific Virtual Company may be accomplished by add the following to the CI templates:

				
<input type="hidden" name="virtualcompany" value="num"/>
				
				

where num is the number of the Virtual Company to which the Account will be associated.

In addition, the Service Definition offerings for an existing customer may be filtered to those available to every Virtual Company and those specified by form variable "virtualcompany".

CI templates to which the hidden form variable "virtualcompany" may be added are"

As previously mentioned, upon successful registration, bmuid will process a template and pass the results to bmui.cgi. The processed template is called a "Registration Response". The data in the template should be customized to be suitable for the registration software, e.g. an HTML response for a browser, a special file format for a CD signup, etc. Lines beginning with the "#" character are ignored by bmuid and are not passed as part of the registration response.

As the template is processed, data may be inserted into the "Registration Response" by means replacing data for tags embedded in the template. The following tags are supported:

Values that are used to substitute for tags may come from a variety of sources. These are:

Note that there exists the file /usr/local/billmax/cgi-bin/cgimenu. This generates the default tree pane and may be used similarly to /usr/local/billmax/cgi-bin/cgimenu_html to customize the tree pane. When doing this, there is no need to copy the ".htm" files.

When registering a new customer, it may be necessary to correctly identify the customer's sales tax region for tax purposes. This may be done by customizing the program /usr/local/billmax/local/tax_hook. The data supplied by the customer is in the execution environment of /usr/local/billmax/local/tax_hook. This data may be used to determine the identifier of the BillMax sales tax region. The successful output of the program is an integer written to stdout that is the number of the sales tax region for the customer.

if( $ENV{ACCOUNT_zipcode} eq '82341' ) {
	printf( "1\n" );
	exit(0);
}
if( $ENV{ACCOUNT_zipcode} eq '81231' ) {
	printf( "2\n" );
	exit(0);
}
exit(1);