How requests are processed

Changes that you specify in a single call occur as part of an atomic unit and are applied immediately on successful completion of the call. If one change contains an error, none of the changes are applied. For example, if you attempt to issue five discrepancies, and you specify invalid data for one discrepancy, none of the discrepancies is issued.

Requests are subject to the following constraints:

Processing time—The maximum allowed time for a single request is five minutes. Processing that exceeds the maximum time results in an error.
Size of requests—Requests must be smaller than 5 MB.
Case-sensitivity—The Discrepancy interface operations require the same case-sensitivity rule as the InForm application—object references by name are case-sensitive. Objects whose names contain different cases (for example, "cra" and "CRA") are different objects
Sequence of operations—The caller is responsible for sequencing operations as required for semantic correctness (for example, a discrepancy must exist before it can be updated).

Before the request is processed, the following operations are performed:

The server logs the request (operation and user name only) to the event log for historical analysis.
The user name and password are extracted from the SOAP header and are validated against the InForm database. Only requests with valid credentials for active accounts are accepted and processed.
Multiple repeat requests with invalid passwords will disable the account and require administrative action according to existing InForm business logic. The allowed number of failed log-on attempts is set in the InForm application on the System Configuration page.
Parameters are validated. If the request contains invalid content, an error is returned. For example, schema validation and InForm character restrictions are enforced.