Create Action Screen

Under the Function Generation screen, click on the Action node.

Web Service related information and FLEXCUBE amendable fields details are captured in the actions screen.

Specify the details of the Form Actions screen as follow:

Table 35-1 Form Actions Details

Field	Description
XSD Type Identifier	A unique descriptive code should be given in this field, which would describe the nature of the Function. For example LCProd, For LC Product Definition Form Screen Layout Design
Service Name	An appropriate Web service name should be selected here. LOV will fetch the service names maintained in GWTM_OPERATIONS_MASTER.
Operation Id	This is the key using which the Web service operation code would be derived. For example of Operation Id is Product Operation Code for QUERY would be QueryProduct. Note that this should be given in the Sentence case and should be unique within the service. Ensure that the correct operation id is given that is in the case of LC Product Operation id can be Product. It need not be LCProduct. In case of multiple products/contracts there under the same service, for example in Exchange-traded derivates module, Operation Id for Deal product can DealProd and for Margin product MarginProd etc.
Action Code	Pre-defined actions will be available for the action code. These are the operations that are available in the FLEXCUBE. For maintenance, the type of function system enables the below action codes only: QUERY NEW MODIFY AUTHORIZE DELETE CLOSE REOPEN SUMMARYQUERY For transaction Screens, all the actions would be enabled.
Operation Code	If the web service is selected, the operation code will have defaulted and the operation code will be the combination of action code and Operation Id and the same operation code will be used to perform operations for web service. If the developer wants custom-specific Operation Code names, they can be provided so. For this double click on a particular action code, the Operation Code field for that action code will be enabled. Developer can modify the operation code now.
Action Stage Type	For multistage actions, it should be checked. If any field has to be made amendable during the particular operation, the action stage type has to be checked for the particular action.

Click on the Amendable button against each action to capture the amendable information for each action.

Amendable button 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 Details screen displays.

Specify the details in the Amendable Details screen for each action.

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.

Table 35-2 Amendable Details

Field	Description
All Records	If All records are checked, System expects the full data every time; that is 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.

Generated code also would perform validations based on the above preferences.

Click on the OK button.