3 Preferences

This topic explains the systematic instructions to set the preferences at function ID level.

Function id level preferences like module, logging required, tanking modification Main menu, Sub-Menu1, Sub-Menu2 is maintained through Preferences screen in ODT.

The data maintained in preferences screen will be used for generating static data script for tables SMTB_MENU, SMTB_FUNCTION_DESCRIPTION, SMTB_ROLE_DETAIL and SMTB_FCC_FCJ_MAPPING.

  1. Click the Preferences node in the Function Generation screen.
    The Function Generation screen displays.

    Figure 3-1 Preferences Screen in ODT Function Generation



  2. On the Preferences screen, specify the fields.
    For more information on this, refer to the field description table.

    Table 3-1 Preferences - Field Description

    Field Description
    Module

    It captures the Module of the function id. Developer can choose module name from the list of values provided. List of values is populated based on the modules maintained in SMTB_MODULE table of the business schema (current FLEXCUBE environment to which tool is mapped).

    Module Code has to be provided mandatorily. Module name provided would be reflected in the script for SMTB_MENU generated by ODT (in module column).This will also be considered while naming the packages generated by the tool. First two characters of the packages generated will be taken from the module code maintained.

    Module Description Module description gets defaulted based on the module code selected.
    Head office Function

    It captures whether the function is a head office function or not. It will be reflected in the static script for SMTB_MENU in column HO_FUNCTION.

    If the function is a head office function, only query operation will be possible at all the other branches for the particular screen.

    Logging Required

    It captures whether logging is required for the function or not. This will also be reflected in script generated for SMTB_MENU (column LOGGING_REQD).

    If this option is selected, all the request and response for the function ID will be logged in CSTB_MSG_LOG. This is used for view change option.

    Auto Authorization

    It captures whether Auto Authorization is allowed for the function or not. This will also be reflected in script generated for SMTB_MENU (column AUTO_AUTH).

    Note:

    Auto authorization is possible only if it is allowed at function id level, user level and the branch level.
    Tank Modification

    It captures whether modification to be tanked for the function or not. This will be reflected in TANK_MODIFICATIONS column of SMTB_MENU table script.

    If tank modification is enabled, then the record in that screen would be logged to logging tables and taken up for processing (untanking) in later stage during EOD operations. Currently this is applicable only for maintenance screens.

    Field Log Required It captures whether field Logging is required for the function or not. This will be reflected in the FIELD_LOG_REQD column in SMTB_MENU. If field log required is enabled, then all operations on the screen will be logged to logging tables (STTB_FIELD_LOG.STTB_RECORD_LOG etc.,). Currently this is applicable only for maintenance screens.
    Excel Export Required This field captures whether option to export records from summary screen to excel is required.
    Multi Branch Access It captures whether multi branch access is required for the function Id or not. This will be reflected in MULTIBRANCH_ACCESS column of SMTB_MENU table script generated. If multi branch access is allowed, then records of different branches for the screen can be modified from a single branch.
    Txn Block Name It captures the Transaction Block Name. This is applicable only if multi branch access is allowed for the screen. Select the block from the select list which contains the field for branch code.
    Txn Field Name

    It captures the Transaction Field Name. This is applicable only if multi branch access is allowed for the screen. Select list provides all the block fields for the transaction block selected.

    Choose the field for branch code from the list. Txn Block Name and Txn Field Name will be reflected in the system JavaScript file (SYS js) generated by ODT. Developer has to code for querying the records based on the branch code value of this field.

    Branch Program ID It captures branch program id for the function.
    Process Code This can be used to map which process needs to be initiated during screen launch. This is used for workflow screens.
    SVN Repository Url

    This is applicable only if integration to SVN (version control tool) is required. Path of the SVN repository till the module needs to be provided in this field.

    Control String

    Control String defines the operations which can be done on the particular screen. Control String has to be maintained for function id. Select the function id for which control string has to be modified and click Control String.