You can customize your application by defining additional fields from the Gateway user interface or in the XML description file as shown below.
The following example, defines two fields: CostCode UDF field, and TotalPlannedCost UDF field.
In P6 EPPM, customers might have fields defined for project, activity, or other objects. They can define them using codes (project code, resource code or activity code) or user defined fields (UDF). Similarly, they might have fields defined in their enterprise application as well that carries the same information as the corresponding fields in P6 EPPM. Hence, they would want these fields to be integrated when they implement their integration.
To provide support for these fields, you start by defining them in an XML description file and then reference the fields later in direct field mappings, foreign field mappings, custom Java field mappings, Groovy mappings, or custom steps. Here is a sample from the customization.xml in the sample customization project that defines the CostCode UDF field for Activity and the TotalPlannedCost UDF field for the project on the P6 side. You can define additional fields for the enterprise application side as well.
<CustomMetadata>
<App>
<Name>P6</Name>
<BusinessObject>
<Name>Activity</Name>
<Field category="UDF">
<Description>Cost code UDF Field</Description>
<Name>CostCode</Name>
<Type>String</Type>
<MaxLength>255</MaxLength>
</Field>
</BusinessObject>
<BusinessObject>
<Name>Project</Name>
<Field category="UDF">
<Description>Total planned cost UDF Field</Description>
<Name>TotalPlannedCost</Name>
<Type>Double</Type>
</Field>
</BusinessObject>
</App>
</CustomMetadata>