Hello Jacques, Problems with ShipmentGatewayConfigType and PaymentGatewayConfigType entities are: - 'hasTable' field values is set to N for these entities - 'typeId' field values do not give direction about detail entity name
-- Thanks & Regards --- Arun Patidar Manager, Enterprise Software Development HotWax Systems Pvt Ltd. www.hotwaxsystems.com On Fri, Sep 1, 2017 at 5:46 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > It's described here https://cwiki.apache.org/confl > uence/display/OFBIZ/General+Entity+Overview#GeneralEntityO > verview-ExtensibilityPattern > > What is the problem with ShipmentGatewayConfigType and > PaymentGatewayConfigType (did not check)? > > Jacques > > > > Le 01/09/2017 à 13:18, Arun Patidar a écrit : > >> 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. >> >> >> >
