By default your source records are passed through as-is to be stored in TCS. Each entity type from the source will be mapped to a new record type and a key suffix in TCS that can be queried by your consumers like any other TCS keys.
You should not URL encode your TCS keys except when querying config-registry records, see TCS DAC for more detail
Let say your entity type is called TENANT_IP_ALLOW_LIST and we assign: 1/ a TCS record type of same name to you and 2/ a key suffix of
.allow-list. Your consumers can query your data from TCS like this: GET /entity/TENANT_IP_ALLOW_LIST/<entityId>.allow-list
If this is all you need, great just let us know that you want a pass-through transformer and skip the rest of this page. If you need to perform some transformations to your source records before storing them into TCS you will need to add one or more transformers for each of your entity type.
This is no different to adding a normal catalogue transformers except you need to extend a different abstract
class: AbstractExternalRecordTransformer or AbstractExternalRecordCompositeTransformer.
The former is for transformers that return a single key while the latter can return multiple keys.
Rate this page: