You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page:
Return to Adding Supporting Documents to an Agreement.
You can add Associations and supporting documents to an Agreement after it is created. Supporting documents are not necessarily part of the agreement, but are used to capture miscellaneous details, like email threads, minutes of meetings, and so on. There are two types of associations:
To add an Association:
1. Click Agreement Management > Agreements on the Home page. The Agreements index page opens.
2. Click the View Record icon next to the agreement you want to view the details of. The Agreement Details Page opens.
3. Click the Associations option in the left navigation to see a list of all associations that have been added to the agreement.
4. Click icon to add a peer to peer association. The Select Association page opens.
5. Select an appropriate association and then click Select. The selected Association gets added under theAssociation section with an incremented association number.
6. Click to add a parent to child association. The Create Associated Document dialog box opens with the parent agreement name on the right side of the page.
7. Type the appropriate information in the respective fields and click Create to create a child association for that agreement.
8. The Association gets added under the Association section with an incremented association number.
Previously, in ICM, tracking individual associated records such as line items, rounds and awards back to their related RFQ was very difficult.
With this release, ICM provides a capability to define a custom agreement code with reference to the peer and parent-child contract type, at the time of creating associations for that agreement contract type.
Users can now:
Users need to configure the contract type and define associations and set the Use Custom Nomenclature field to Yes to enable the creation of custom agreement code for association.
To set the associations properties in contract type:
The Relation Type will be displayed as per the selected entities.
The selected format will be previewed in Association Agreement Code Format field.
For example, {Parent Agreement Code}-{Name}-{ID – with 2 leading zeros}.
You can also edit the existing contract type and configure the associations to enable the creation of custom agreement code for association.
After the agreement is created, you will be directed back to the parent agreement and the current association will be selected on the left navigation panel on the parent agreement’s Details page and displayed in the grid by default.
The Agreement Code is created as per the configuration at contract type level. For example ICM_MSA_19-Item 2-001.
Note:
ICM provides the functionality to attach associations to agreement entities. This functionality has now been enhanced with the ability to define the type of relationship (association) as Parent, Child or Peer.
With this release, agreements can have only one association as a parent and all existing related agreements will be tagged as peer or child associations.
Users need to configure the contract type and define default associations to enable the parent child linkage for peer associations.
To set the associations in Contract Type:
You can also edit and configure the associations in the existing agreement contract type.
User can self-link the agreement instance as an association.
To create the self-linked association for the agreement:
All the configured associations for the contract type will be visible by default on the left panel configuration under Associations tab on the agreement Details page.
User cannot associate the same agreement instance with itself. For example, here if user selects agreement instance ICMPK_SOW_223, the association will not be allowed and the validation message will be displayed.
For example, select Peer.
The association will not be allowed and the validation messages will be displayed if the user tries to:
For example, validation message is displayed when the user associates the agreement as child which already has parent:
The Allow Two-Way Linkage field is set to No for the associations in the contract type to create the unidirectional associations.
To create the association for the agreement:
The Lookup Search window opens. All the agreements for the selected contract type (Base CT) are displayed irrespective of their states.
Users need to set the Allow Two-Way Linkage field to Yes for the associations in the contract type to create the bidirectional associations.
To create the association for the agreement:
Note:
To create the association for the amendment:
When the amendment is created for the agreement, all associations from parent agreement will be copied to the amendment with the relation type as peer.
In case of two-way linkage, if one of the association is dissociated, it will be removed in the other associated agreement as well.
To dissociate the association for SOW agreement:
When user dissociates the association in the agreement, the association is removed from the linked (parent/child or peer) association as well for two-way linkage type. For example, ICMPK_SOW_223 is removed from ICMPK_MSA_19.
User can copy the existing agreement and create a new copy with Copy Record functionality.
To copy the agreement:
The agreement will be copied if its associations are of peer and parent linkage type. The agreement with associations with linkage type as child cannot be copied and the validation error is displayed.
For example, the agreement Icertis Statement of Work has the association ICMPK_MSA_20 with linkage type as child, so the agreement cannot be copied.
The validation message is displayed.
Users can configure the contract type to associate and inherit all its attributes while creating the agreement. User need to set the attributes as global and there Is_inherited property to Yes at contract type level to enable the inheritance of the agreement.
To set the attribute properties in agreement contract type:
Similarly, configure the contract type which inherits thisICMPK_MSA contract type.
You can edit and configure the existing agreement contract type to allow the inheritance.
The attributes in the parent agreement with Is_Inherit property set to yes will be inherited in the current agreement.
The inherited agreement will be associated with the current agreement with the linkage type as peer and displayed on the association grid of the agreement.
For example, the inherited agreement ICMPK_MSA_20 is associated with the current agreementICMPK_SOW_225 as Peer.
As part of RFQ creation process, users need to add several documents as mandatory attachments to RFQs that may not change frequently. Previously, users had to attach multiple such documents manually to every RFQ which was a tedious and time consuming process.
ICM now has simplified the process by allowing users to attach predefined standard documents automatically to agreement / amendment based on defined event rules.
Users can now:
The Standard Document Master stores the documents to attach to an agreement based on the configured event rule. This Standard Document Master is a seeded masterdata with defined attributes for uploading the documents to the masterdata instance.
Administrators can edit and add additional attributes to the existing Standard Document Master as per the business requirements.
To add attributes to masterdata contract type:
Users can upload files for auto-attachment by creating instances of the Standard Documents Master.
To create masterdata instances:
You can edit Standard Document Master to add, delete or modify stored documents.
Click Remove to delete the existing file in the Standard Document Master.
Administrators can create a global saved search using Standard Document Master instances as auto-attached documents through Save Search functionality.
For example, the SearchAutoAttachment search is saved as global search.
The Administrators need to add the attribute (Master Data Instance Reference Id) to the Associated Documents Contract Type to link it with the Standard Document Master. This Master Data Instance Reference Id is a seeded script attribute that refers to the unique sysId of the Standard Document masterdata.
To add the attribute to the Associations contract type:
Users can configure the Event Rule for agreements and amendments to attach standard documents automatically when certain actions such as Create, Publish and Update occur. The rule is configured using association name and standard document's saved search.
To configure an event rule for agreement:
Documents will be attached to the agreement under selected associations automatically as per the configured event rule.
To auto-attach documents to the agreement when the agreement is updated:
When the agreement is updated, event rule Agreement Update With Auto Attachment will be evaluated. The three associations will be created for Annexure3 as per the saved search SearchAutoAttachment.
The agreementICMAutomationAssoTwocolumn_382 will now have two auto-attached documents.
To summarize, the documents will be attached to agreements when the certain event occurs as per the criteria:
There are two ways to add an Associated document Saved search to an Agreement.
Note: A Saved Search needs to be created in ICM of the required association data.
To tag Associated Document Saved Search:
You can add the rich text content control to tag the saved search in the Template or Agreement document using Word:
1. Select the Plain Text Content Control from the Developer menu.
2. Click Properties. TheContent Control Prpoerties winow opens.
3. Enter the Title and tag as ICMAssociation|AssociatedSavedSearchName. For example, ICMAssociation|Country Master.
4. Click Ok. The Saved Search is now tagged in the Template/Agreement document in the form of a table.
Note: This template is uploaded in ICM to be available while creating a document. The Saved Search is visible after assembling the contract.
Upon publishing the Agreement you can add more instances to the Associated document Saved Search in the Agreement document from the Agreement's Details page:
1. Click the Associations tab on the Agreement's Details page.
2. Click the Create Association icon in the Associations tab. The Create Association page opens.
3. Enter the necessary details on the Meta Data tab. For example, Name, Contract Value.
4. Click Next. The Templates tab opens.
4. Select the appropriate template.
5. Click Create. The association instance is added. The Agreement's Details page opens. The number next to the association is updated in the Associations tab.Erlier there were 2 instances of the associations and now there are 3.
6. Click the Assemble Contract button on the Details page. The newly added instance get's updated in the Agreement document.
Note: The Associated document saved search instances can also be updated in the document by Edit and Update actions.
Related Topics: Agreement Details Page | Association Management | Saved Searches
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in one of the groups: Users, User.
You can view and copy the source of this page:
Return to Adding Supporting Documents to an Agreement.