1.17.2 Additional Field Configuration

This topic describes the information about the Additional Field Configuration.

Scenario: Adding additional fields to a new Data Segment and add it to the train hop

Step 1: Add Metadata in additional attributes common core maintenance. Post maintenance the entry in CMC_TM_ADDT_ATTR_MASTER should be as follows:

Table 1-22 CMC_TM_ADDT_ATTR_MASTER - Entry Values

ID	UI_KEY	Description	FIELD_META_DATA
1	fsgbu-ob-cmn-ds-additional-fields@OBPY_REOB_ENRH	Additional fields for REOB process	[ { "id": "UDF_TEXTATTR", "label": "Text", "type": "TEXT" }, { "id": "UDF_NUMBERATTR", "label": "Number", "type": "NUMBER" }, { "id": "UDF_TEXTAREAATTR", "label": "TextArea", "type": "TEXTAREA" }, { "id": "UDF_DATEATTR", "label": "Date", "type": "DATE" }, { "id": "UDF_DROPDOWNATTR", "label": "Dropdown", "value":"A","type": "DROPDOWN", "options": [ { "value": "A", "label": "A" }, { "value": "U", "label": "U" } ]}, { "id": "UDF_SWITCHATTR", "label": "Switch", "value":true, "type": "SWITCH" }, { "id": "UDF_LOVATTR", "label": "Customer", "type": "LOV", "lovId": "customerLOV" } ]

Note:

• Values in UI_KEY column refers to a unique identification reference key of any screen
• Sample metadata has been given in the Field_meta_data column. In the example a field of type text has been defined with Id - UDF_TEXTATTR. Similarly type – Number, textarea, dropdown, lov and switch has been added

Step 2: Configure the train hop entries with the CCA Name for OBPY using Business Process screen.

OBPY UI:

CCA - fsgbu-ob-py-ds-additional-attributes is in OBPY component server to serve this purpose.

Service:

The payload with the additionalAttributes json will be processed on next click in UI for the above CCA.

Step 3: Handoff Changes

• A property in obpy-properties table is made available with the key REOB_ADDITIONAL_FIELDS_UIKEY, and the respective value holds the UI key of the core maintenance.
• REOB_ADDITIONAL_FIELDS_UIKEY can accept multiple UI keys for handoff and the values should be pipe (‘|’) separated (if additional attributes are added in multiple screens for a single process).
• All the additional fields captured in different data segments for a single process and configured in above property will be collated and passed on as UDF label, value list and will be available in the OBRH Request.
• UDF json will be appended to the party JSON which is ready for handoff and can be mapped to the request template through OBRH for the HOST.
  Template changes are available in the request transformation:

  #foreach($UDF in $body.UDFList)
      <fcub:UDFDETAILS>
      <fcub:FLDNAM>$UDF.label</fcub:FLDNAM>
      <!--Optional:-->
      <fcub:FLDVAL>$UDF.value</fcub:FLDVAL>
      </fcub:UDFDETAILS>
  #end

• Once after the FCUBS handoff, the UDF fields will be handed off and can be checked in STDCIF screen - Fields tab