This section provides a brief overview of the Submit, Modify, and Query functions.
Submit functions are used to create a record; for example, opening a form in New mode, then saving it as a new record. Each subsection describing submit functions can contain the following tables:
- Required input field values
These fields are required and a record is not created if they have null values.
- Optional input field values
These fields are not required to create an entry, but they might need to be populated, depending on the status the entry to be created. (See the Notes column in each table for more information about specific fields).
- Fields set by workflow
The values in these fields are generated by workflow that is triggered by the input fields (required and optional) only. When using web services, they are not exposed to the user.
For example, the Priority field value is calculated when you populate the Impact and Urgency fields.
When a record is created successfully, the newly created record ID is returned.
The creation of work log entries is the only workflow triggered by a modify function. When using web services, if there are populated fields in the main form that you want to modify, specify those values in the corresponding web service fields.
If you specify a null value, the null value overwrites the value currently in the form.
There is no returned value to signal that a record has been modified.
The query functions are web service-specific operations.
When using web service functions, you must specify the ticket number on which to query (< module>Query_Service ), or a valid AR System qualification--if you query from a list of entries (< _module>_QueryList_service ).
The "LIKE" operator can be used in the qualification of an unlimited character field length, this type of field is stored as a CLOB in the database. An example of such a field is the 'Justification' field on the Purchase Requisition.