If you check entities, we have an entity Person and PartyGroup. The
with the same name. It's a simple pattern to extends a entity.
> Hi Nicolas,
>
> Yes, it makes sense, thank you. One more related issue please, what is the
> purpose of the ‘hasTable’ flag.
>
> Regards,
>
> Emad
>
> On Monday, December 7, 2020, Nicolas Malin <
[hidden email]> wrote:
>
>> Hi Emad,
>>
>> PARTY_GROUP and PERSON are root type for other.
>>
>> If you identify a party as CORPORATION by relation is a PARTY_GROUP.
>>
>> on demo data you have this :
>>
>> <PartyType description="Legal Organization" hasTable="N"
>> parentTypeId="PARTY_GROUP" partyTypeId="LEGAL_ORGANIZATION"/>
>>
>> <PartyType description="Corpration" hasTable="N"
>> parentTypeId="LEGAL_ORGANIZATION" partyTypeId="CORPORATION"/>
>>
>> So you can read as a corporation is a specialization of a legal
>> organization that is a specialization of a party group.
>> This help to qualify a party with force this nature.
>>
>> Nicolas
>>
>> On 07/12/2020 19:35, Emad Radwan wrote:
>>> Hi There,
>>>
>>> While navigating from the party search grid to the Party Profile there
>> is a logic that checks if the party is in PartyAndGroup or PartyAndPerson
>> view entities to decide the party type and decide the relevant details.,
>> That's all fine and understood, also the demo data has all parties in the
>> party grid assigned either Party Group or Person. My question is, why we
>> have other values in the seeded party types table like the following? In
>> other words, if I assign something like 'Legal Organization' as party type,
>> is there other logic path to handle it as it's not a party group or a
>> person and as I understand each party can be assigned one party type only!
>>> Appreciate if you shed some light,
>>>
>>> Regards,
>>>
>>> Emad.
>>>
>>> AUTOMATED_AGENT CORPORATION
>>> FAMILY GOVERNMENT_AGENCY INFORMAL_GROUP LEGAL_ORGANIZATION PARTY_GROUP
>> PERSON
>>> TEAM