AgreementRelationship

An AgreementRelationship business rule gives users the ability to define the parent/child relationships between Agreement Types.

AgreementRelationship: Elements and Attributes

Element/Tag	Attributes	Parent Element	Description	Element/Attribute Value
<AgreementRelationship>
<Agreement>	TYPECODE	<AgreementRelationship>	Required Attribute TypeCode of the Agreement.	The code values defined in AsCode table
	ROOT		Required Attribute Whether Agreement is a root node. An Agreement with ROOT=”No” cannot be added by clicking on ‘New’ button.	Yes | No
<Parent>		<Agreement>	Repeatable element; Agreement Type which can be designated as parent. An Agreement Type defined by TYPECODE above, can have multiple parents.	The code values defined in AsCode table

XML Schema

<AgreementRelationship>

<Agreement TYPECODE="AgreementTypeCode" ROOT="Yes|No">

<Parent>AgreementTypeCode</Parent>

<Parent>AgreementTypeCode</Parent>

...

</Agreement>

<Agreement TYPECODE="AgreementTypeCode" ROOT="Yes|No">

<Parent>AgreementTypeCode</Parent>

...

</Agreement>

...

</AgreementRelationship>

XML Example

<AgreementRelationship>

<Agreement TYPECODE="BANK" ROOT="Yes">

<Parent>BANK</Parent>

</Agreement>

    <Agreement TYPECODE="PG-CNT" ROOT="Yes">

     <Parent>PG-CNT</Parent>

      </Agreement>

<Agreement TYPECODE="FUNDING" ROOT="Yes">

<Parent>FUNDING</Parent>

</Agreement>

<Agreement TYPECODE="FUNDACCT" ROOT="Yes">

<Parent>MSTR-INS</Parent>

</Agreement>

<Agreement TYPECODE="MSTR-ASA" ROOT="Yes">

<Parent>MSTR-INS</Parent>

</Agreement>

</AgreementRelationship>