Re: Extend type entities to add name of detail entity where hasTable is true.

[Michael Brohl]

Hi Arun,

thanks for reporting this.

I think we should keep the convention and fix the metioned types.

Introducing a new field to specify the detail table should not be necessary.

Thanks,

Michael


Am 01.09.17 um 13:18 schrieb Arun Patidar:

Hello All,

'hasTable' field of 'Type' entities is used to give an idea that detail
entity exists or not. We generally get the name of detail entity on the
basis of typeId field value.

For example :

ContactMechType,contactMechTypeId = "POSTAL_ADDRESS"  then we go to
PostalAddress for detail.

similarly,
ContactMechType,contactMechTypeId = "TELECOM_NUMBER"  then we go to
TelecomNumber for detail.

is it a best practice to identify the name of detail entity on the basis of
typeId value?

If yes, then there are some entities that are not following the pattern.
Some of them are:
    - ShipmentGatewayConfigType
    - PaymentGatewayConfigType

if not, then we can add a field in Type entities to mention the name of
detail entity.


Please let me know your thoughts.

smime.p7s
Description: S/MIME Cryptographic Signature