11.2 Amendable Field Information
This topic describes about the amendable field information.
Button amendable against each action would capture the amendable information for each action. It is mandatory to give amendable information for applicable actions for web services to function normally. Amendable information is not just for ‘Modification’ and for all the applicable actions. For example in a transaction screen, for QUERY action amendable information could be Oracle FLEXCUBE Reference number, User Reference Number, and External reference Number. It is not necessary to just have the Primary key in the XSD as external systems might query contracts based on any of these reference numbers. At a block-level user has to specify All Records, Delete allowed, New allowed, and Mandatory. This information is used by the Tool to generate scripts and code accordingly. Generated code also would perform validations based on the above preferences.
Table 11-1 Amendable Field Information
| Field | Description |
|---|---|
| All Records | If All records are checked, System expects the full data every time; i.e. in case of a multi-record block if there are 10 records and 1 record has to be modified, external systems still should send the remaining 9 records with the old data. |
| New Allowed | This indicates whether a new record can be added or not, in this block as part of this action. |
| Delete Allowed | This indicates whether a record can be deleted or not, in this block as part of this action. |
| Mandatory | This flag indicates whether the node is mandatory to be sent from external systems. This flag would be used to set the Min Occurs Flag in XSDs for that operation. |
Figure 11-2 Maintaining Amendable Fields Information
Parent topic: Actions