[jira] [Updated] (OFBIZ-9696) Extend type entities to add name of detail entity where hasTable is true

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun Patidar updated OFBIZ-9696:
--------------------------------
    Description:
'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.

We should follow the naming convention.

Below are some entities that are not following the pattern. Some of them are:
   - ShipmentGatewayConfigType
   - PaymentGatewayConfigType


  was:
'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.

We can add a field in Type entities to mention the name of detail entity.

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

> Extend type entities to add name of detail entity where hasTable is true
> ------------------------------------------------------------------------
>
>                 Key: OFBIZ-9696
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9696
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Arun Patidar
>            Assignee: Arun Patidar
>
> '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.
> We should follow the naming convention.
> Below are some entities that are not following the pattern. Some of them are:
>    - ShipmentGatewayConfigType
>    - PaymentGatewayConfigType

--
This message was sent by Atlassian JIRA
(v6.4.14#64029)