General Validation Rules Across all Services

General commenting is only supported by getCompleteBPRecord service.

Special characters must be escaped in a valid XML document. The following characters ", ‘, < , >, & will be escaped to:

For Web Services (createBPRecord, addBPLineItems, updateBPRecord, createProject) the XML is scanned for validity and any errors are reported when found.

A non-required tag like <hello>hello</hello> is completely ignored.

Date fields (which are set as Date type) must be in the following format:

MM/dd/yyyy
MM-dd-yyyy
MM/dd/yyyy HH:mm:ss
MM-dd-yyyy HH:mm:ss
MM-dd-yyyy HH:mm:ss z (this format accepts timezone)
MM/dd/yyyy HH:mm:ss z (this format accepts timezone)
yyyy/MM/dd HH:mm:ss
yyyy-MM-dd'T'HH:mm:ss
yyyy-MM-dd

MM-dd-yyyy hh:mm is a 24-hour clock. Users should specify time in hours instead of AM/PM notation.

The "z" in MM/dd/yyyy HH:mm:ss z signifies timezone.

The system converts user specified time to server time zone and stores in the database.

Tag names are case sensitive. For example: <_BP> is not a valid tag.

When designing Business Processes (BPs) that are related to Integration:

All BPs must have the record_no tag in the Upper forms.
For Cost related BPs, the Amount field must be present in the Line Items.

If the XML has a leading tag <?xml encoding="iso-8859-1" ?>, the system supports all characters within this ISO standard.

There are no form-level validations (required field, form level validation rules, and so forth).

There is no auto-populate feature through Integration, if integration interface is not designed for the BP.

See Also