a_customer.xml file

The system uses the a_customer.xml file to reference any system classes that have been customized.

Because the a_customer.xml file is the first to be run by the UpdateDB utility, the changes you reference in the product script files are the first to be applied. All your system options are then incorporated into the customization before the UpdateDB utility runs the product_description.xml scripts. If you incorporate class extensions in any of your system options, create the a_customer.xml file. All modified class files and scripts must be referenced in the format shown in the following example.

Example

In this example, the UpdateDB utility runs the scripts representing each successive update version up to and including the referenced V600_01 script. The altered <mboset objectname> and <mbo object> entries indicate that the purchase order classes have been extended.

<?xml version="1.0" encoding="UTF-8"?>
<product>
	<name>Customer Product</name>
	<version>
		<major>6</major>
		<minor>0</minor>
		<patch>0</patch>
		<build>999</build>
	</version>
	<dbmaxvarname>DBCUST</dbmaxvarname>
	<dbscripts>cus</dbscripts>
	<dbversion>V600-01</dbversion>
	<lastdbversion>V520-20</lastdbversion>
	<extensions>
		<mboset objectname='PO'>psdi.app.cust.POSet</mboset>
		<mbo objectname='PO'> psdi.app.cust.PO</mbo>
	</extensions>
</product>


Feedback