The symbol is formed with the normalized values of tags mentioned in the configuration parameter DataManager.SymbolFormationTags. The tags should to be delimited by space. The repeating group tags can be mentioned in "[ ]" square brackets. The first tag in the brackets needs to be the repeating group tag. The tags in the "[ ]" are also space delimited.

From the configuration DataManager.SymbolFormationTags":"167 207 [146 309 310 313]"

The base tags : 167 207

Repeating group tags : 309 310 313

For example:

If you replace the tag numbers with their corresponding values picked from the security definition, that will become the mapped symbol.

The mapped symbol contains all the legs of the multi-leg security with configured tag values populated. If you find minimal tags to distinguish each security, then the mapped symbol is recommended.

For example:

All the above examples are the multi-leg scenarios.

In single leg securities, though the session configuration mentions the repeating group tags, the security definition received from exchange will not have the repeating group. So that part is removed while constructing the mapped symbol.

For example:

If you replace the tag numbers with their corresponding values, that will become the mapped symbol.

You must choose minimum base tags such that symbol formed will be unique and simple.

The created mapped symbol will appear in the dictionary field "extraParams" of InstrumentDataResponse() as a key value pair.