2.4 Data Blocks

This topic describes about defining the data blocks for Online Forms.

  1. Determine the block structure for the function id. Define Data Blocks as per the design in the Block Properties screen.

    Figure 2-6 Defining Data Blocks and maintaining its properties


    Description of Figure 2-6 follows
    Description of "Figure 2-6 Defining Data Blocks and maintaining its properties"

  2. Master Data Block has to be a single entry data block.
  3. Provide XSD Node name if the block is normal and is required in gateway request.

    Figure 2-7 Attaching Block Fields and maintaining its properties


    Description of Figure 2-7 follows
    Description of "Figure 2-7 Attaching Block Fields and maintaining its properties"

  4. Block order and block field order can be changed by rearranging blocks and block fields in the browser tree (drag and drop).

    Note:

    Note that all units will have to be regenerated if block or block field order is changed (including xsd’s).
  5. Related currency fields should be placed above the amount field in the tree.
    Add block fields to the data block as required.

    Figure 2-8 Attaching Block Fields and maintaining its properties


    Description of Figure 2-8 follows
    Description of "Figure 2-8 Attaching Block Fields and maintaining its properties"

  6. In case the block is not required in XSD, select the Not Required in XSD checkbox.
  7. Ensure that Related Block and Related Field are given for Amount Fields.
  8. Minimize the use of query data sources by using DESC fields wherever possible.

    Note:

    Query data sources is rarely required for a Online Form screen; as launch form can be used for query only screens.
  9. Master block should contain reserved field names like AUTHSTAT, RECORDSTAT, ONCEAUTH, MODNO, MAKERID, CHECKERID, MAKERDTSTAMP and CHECKERDTSTAMP are added as part of the footer of the screen.

Parent topic: Screen Development