Agreements

This page displays all the Agreements that you are associated with in one way or the other. You may have created an Agreement or you may be a member of the team that is working on the Agreement. This page displays the most current version of an Agreement regardless of its status.

From this page you can:

• Search Agreements in several ways. You can Search Agreements using the Search tile or use the Advanced Search page.
• View pinned saved searched by Administrator. If you are logging on to ICI for the first time, you will see saved searches pinned to your Agreement page. These pinned searches are applicable to the User Group you belong to and will remain unchanged, unless you modify them. The saved searches are created by the Administrator for the User Groups and pinned to the Agreements page by the application. A maximum of six searches can be pinned. Once you modify any of your pinned searches, your preferences override the Administrator’s preferences.

• View details of an Agreement by clicking the View Record icon. The details are displayed on the Agreement Details Page.

• View the document to see what the printed Agreement would look like by clicking the View Document icon. Thus, you can quickly find the required Agreement record without opening each Agreement record to view the document. If the Agreement is in Draft state, the preview only displays the attributes defined in the Agreement. If it is in an Approved state, then it also displays the actual values of those attributes. You can print the document or export the Agreement attributes to the desired format. 

Note: This feature is the same as the Preview option from the Agreement Details Page.

 

• View Smart Links to link related documents to one another by clicking the View Smart Links icon drop-down. For example, if there are several Agreements with the same vendor, you can link all of them through smart links to see the types of Agreements that are currently in force with that vendor. See the Creating Smart Links page for details.
• Perform Bulk Actions on Agreements.
• Configure default columns and their sequence on the Search and Index pages throughout ICI for all the users. The configuration can be done for each Entity as well as Contract Type thus offering complete flexibility to define columns as per your business needs.
• Configure multiple mandatory and non-mandatory filters at Contract Type level for inheritance by which agreements can be filtered. This is achieved through a technical configuration at the contract type level.

 

Creating an Agreement

You navigate to this page from the Home page by clicking the Agreement Management > Create Agreement tiles.

On this page, you can do the following tasks:

• Specify basic details of the Agreement
• Select Attributes 
• Select a Template to use for creating the Agreement
• Publish the Agreement
• Send the Agreement for approval 

You can create Agreements in ICI in the following ways:

• Copy an Existing Agreement and make changes to the copy.
• Create an Agreement from a Contract Request.
• Create a new Agreement by using the Create Agreement tile. This help page describes this process.

The following figure shows the different states of an agreement with various roles that are involved in creating it.

Figure: Agreement workflow and various roles involved at different states of the Agreement. 

To create a new Agreement, complete the details for the sections mentioned below:

1. Contract Type Details
2. Attributes
3. Select Template
4. Verify

Click Next at the end of each section to go to the next section and complete creating the Agreement. You can also Save a section at any time and return to this page to complete your Agreement.

 

Contract Type Details

Enter the following basic details of the Agreement in this section:

• Category: categories are created by the administrator and they are similar to labels; useful for organizing your agreements. The drop-down shows all the categories that were chosen while creating the Contract Type. Select one.
• Contract Type Name: shows a list of all the contract types that were created for the chosen category. The Type of Paper option is displayed depending on the contract type definition.
• Contract Type Description: This field facilitates users to select the desired Contract Type. 
• Type of Paper: indicates if your own or a third party template should be used for creating this agreement. Provide your template if you select Own. Select Third Party option when you want to create the agreement by uploading a template agreement provided by the vendor or the provider. Few points to remember when selecting third party paper:
  • should be used mainly when dealing with legacy contracts
  • in case of a deviation, the deviation approval becomes a manual process in ICI,
  • are uploaded as a PDF, making it difficult to analyze them. As a result, attributes may have to be manually created in ICI (which can be time-consuming) or ICI may have to be used with limited functionality.

Note: Of the 4 sections, the Templates section depends on the selected type of paper (Own or Third Party).

If the Type of Paper is Own, the Select Template page with a list of templates  is displayed for the selected Contract Type. If the Type Of Paper selected is Third Party, the Select Template section is not shown. Instead, you would manually upload a third party agreement. You cannot use Own paper with this option.

 

Attributes

This section captures important details of the agreement that you are creating. Note that the attributes shown on this page will vary depending on the Contract Type that you selected. Below is an explanation of some of the less obvious attributes.

• Associate and Inherit: Click  the  icon to associate that agreement and inherit all its attributes to the agreement that you are creating. This field is displayed only for those contract types that have an association with any other contract type.
• Organization Unit: Select the organization unit you would like to create this agreement in. Users within an organization unit must also have certain privileges. With a Vi'ew privilege, users can only view agreements but users with Manage privilege can perform actions on the agreement. For example, if John and Mary share one organization unit, then for John to have access to Mary's agreements, John needs view privilege on her agreements. View privilege is also required for users to search a particular agreement.
• Name: Type a name for the Agreement you are creating. To make it easier for users in the organization to find your Agreement, the name should include some basic information about the Agreement. Basic information could include details such as the purpose of the Agreement and with which vendor this Agreement was entered in to. 
• Contract Value: Type the value of the contract or set it using the controls provided. Selecting a currency is mandatory.
• Agreement Code: Each agreement is assigned a unique agreement ID in ICI, known as its Agreement code. The system automatically generates the Agreement ID when you click the Create button in the 4. Verify section.
• Signature Type: 
  • Manual Signature: Select if all signatories will sign the agreement manually.
  • Electronic Signature: Select if all the signatories will sign the agreement electronically.
  • Fully Signed: Indicates that all signatories have signed the agreement document.
  • Click to Sign: Select this option so that the user can see an online preview of the agreement, which can be used to mark the agreement as signed and executed.
  • Hybrid Signature: Select if both manual and electronic signatures will be used. Note: When selecting Signature Type as Hybrid Signature, the Signature Sequence is by default “Mixed Signature”.
• Signature Sequence: Select the sequence in which the agreement will be signed: External First, Internal First or Mixed Signature.
• Is Amendment: Specify if this Agreement is being created as an amendment for an existing agreement.
• Multi-Party: Specify if this Agreement involves multiple parties. For example, if the organization this agreement is being created for uses a sub-contractor, then this agreement would be marked as multi-party, as the sub-contractor details would also have to be captured.
• Previous Agreement ID: If this agreement  is an amendment or a renewal of an existing agreement, use this field to add a smart link to the existing agreement. 
• External Signatory: C'lick' the Add User icon. The Select User window opens. If the External user is already provisioned you can select that user from the list, or click the Add External User button. The Create External User window opens. Enter all the mandatory fields such as, Name, Email Address and Language. It’s important to select the appropriate language for the user since the user will receive all the ICI notifications in the selected language. Click Save, the user gets added as an External Signatory.

Note: The email IDs of all users are displayed on hovering the mouse over the selected user across the application. If there are two signatories with the same name, it makes it easier to identify the users by their email ID. 

• File Path: specify the path from where you want to upload the third party template.  This field is displayed only when you select Third Party paper on 1. Contract Type Details section.
• Custome File Path: You can add additional user defined file selection attributes to the agreement contract type. Also, it is possible to configure such user defined file selection attribute as read-only to further safeguard the uploaded documents when sent for review to the external Stakeholders. You can do this by enabling the Is_Editable attribute property. Business users cannot edit the uploaded documents; however, they can still preview and download these read-only documents.  System can still attach a file through a read-only file selection attribute through backend tasks or API integrations.

 

 

File scanning during upload:

ICI has added a generic virus scan framework which can be used to implement other virus scanning software. 
When configured, this will help to scan files for any malware and protect ICI against a wide variety of threats whenever a user uploads a file using the File Upload attribute in ICI or a file is uploaded through an API.

The scanning starts on the same page as soon as the user selects a file to upload.

 

 

Upon clicking next action, the scanning status window is displayed only if the scanning is still in progress or malicious content has been found, otherwise the next page in a workflow opens.

 

 

The scanning progress bar is displayed in red color when the file has malicious contents.

 

Upon clicking OK:

• The next page in the workflow opens if the files are safe.
• The current page is displayed again if any file has malicious contents.

Note:

• Any ICI entity (such as agreement, associations, template, clause, masterdata and so on) that takes file as an input in any mode, the virus scan is performed by default for that entity before uploading file into the ICI.
• Files can be scanned in bulk.
• File scanning while uploading through Word and Excel plugins is handled through API.

 

Template

This section displays the Templates that you created for the selected Contract Type. This section is displayed only if you select Own paper to create the agreement on the Contract Type Details section. Select the appropriate Template. Template Selection page displays all the applicable templates in a Grid view by default. Clicking on the row having the desired template selects the template. Clicking again on the same row deselects it. You can switch between the Grid and Tile views as desired and if any selections exist, these are retained between any view switches. 

The Templates listed in the Grid view includes columns based on template metadata such as, template name, template status, etc. or extended template metadata if configured in your instance. Through a technical configuration, you can specify which columns should display on the grid.

You can preview the Template on the Template Selection page itself prior to selection when creating or editing Agreements.

 
•    The template preview displays the directly added Clauses and Attribute/Association placeholders, but does not display any rule based clauses that have been added to the Template. 
•    For a new Template that is currently being used, the latest approved version is displayed in the preview. 
•    When editing an Agreement and the template has been previously selected, ICI displays the content from the version of the template that was used at the time of original selection. For example, a user is trying to edit an agreement for which v2 of the MSA template had been used. The current version of the approved MSA template is v5. Now when the user is editing the agreement and chooses to preview the selection of the MSA template, the product shall display the contents as of v2 of the MSA template. There shall be no difference between the contents of the template displayed in the preview and the agreement document that gets generated except for addition of any rule based clauses and associations. 
Refer to Template Management for complete details on creating, editing, uploading and working with Templates.

 

 

Verify

This is the final section for creating an agreement. It displays only the sections and attributes that you used to create this agreement. Verify all the details you have entered.You can:

• Click the View icon beside the files you uploaded on the Attributes page to preview. The Preview is available for documents in .docx, .pdf, .ppt, .pptx, .msg and Images (.jpg, .jpeg, .png and .gif) file formats.
• Click Discard to abort the creation of this agreement.
• Click Previous to go back and make any changes. Click Next to return to this section after making the required changes.
• Click Create to create the Agreement. The Agreement is not visible to anyone yet (as it is not published) and you can continue creating or editing it on the Agreement Details Page.
• Click Create and Publish to create and publish the Agreement. After the Agreement is published, other users with adequate access can search, view, and take actions on the agreement. After publishing, a Draft watermark appears on the Agreement in all states until it is approved. The watermark gets removed after the agreement is approved.
• Click Create and Send for approval to create and send the Agreement for approval. The Agreement gets sent to approvers that are set by a rule on the Contract Type selected for this Agreement. The state changes to Pending Approval. If no rules are set and no approvers are defined, the Agreement status automatically changes to Approved.

 

Ability to preview agreement before publishing

With this release, a preview functionality is being introduced, so that the primary owner or contract creator can review whether the selected template is appropriate, the rule-based clauses have been correctly added to the agreement, among other factors, and make changes to the agreement before the version is created. The preview document would also include tagged associated documents, coming through inline or inheritance associations.

A preview section is available on the “Verify” stage of agreement creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. 

Note: This functionality is configurable. It is not be available by default, and can be enabled or disabled for chosen contract types. 

To view the agreement before creating or editing the document:
1. Create an agreement and complete the Contract Type Details, Attributes and Select Template pages of the wizard.
2. Click Next. The Verify page opens.

3. Click the Document Preview tab on the right. The Document Preview section is displayed alongside the Verify page. 

 

Note: The preview generation may take some time to load depending on the length of the document, among other factors.

 

4. Click the Expand Preview icon. 

 
The document preview opens in a pop-up window.

 
Note:

• Any associations or inline associations (whether tagged as file or table) will also be included in the preview.
• If the user navigates back to the Select Template page and chooses a different template, the preview displays the latest selected template.
• Only the latest version of the document is displayed in the document preview.

Visibility of sections on the left navigation pane to non-team users

The Administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and want a quick glance at the contract. 
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and associations.

Let’s consider an example where a team member who is at a lower level of the Organization Structure, such as Automation user5, creates an agreement.
1. Click Home > Agreement Management > Create Agreement. The Create Agreement page opens.

2. Click Next. Enter and verify all details for the following tabs.
3. Click Create. The Details page opens with the agreement in Draft status. Note that the user Automation user5, who is at a lower level in the organization chart (an engineer at level 5 of the hierarchy) but part of the team, has access to all the tabs includingTeam and Notes. 

 

Suppose Abe Kim who is at a higher level in the organization chart (CTO at level 2 of the hierarchy) tries to access the agreement, visibility to the tabs can be controlled for him.

 

4. To remove access for the user Abe Kim to the Team andNotes tabs in the Draft state, a backend hard coded configuration using a GUID is done so that these tabs will not be visible for Abe Kim in the left navigation pane.

The user Abe Kim will see all other tabs except for Team and Notes tabs.

 

 

Creating multiple agreements from a single agreement 

You can create multiple agreements from a single agreement with the provision of copying associations and attributes as required. 

Users now:

• Have complete flexibility at configuration level to define the applicable contract type, decision attribute, compute attribute for bulk agreement creation 
• Have the option of bulk agreement creation in the model agreement based on the above configuration with provision to define unique batch Id for all the agreements created using a single model agreement
• Can access model agreements only through technically configured Admin saved search.

Bulk created agreements are created in Draft status by default. However, users can send agreements for approval as part of the bulk creation process by configuring an attribute added in the bulk configuration masterdata contract type. The bulk agreements will then be created in Approved or Waiting for Approval status.

Note: Amendments can also be sent for approval using the same functionality.

 

Configuring Bulk Agreement 

Users are required to use the instance of seeded masterdata contract type to enable bulk agreement creation. The seeded masterdata attributes and their description are explained here briefly. For information about how to configure a masterdata contract type for bulk creation, see the Configuration Guide for Bulk Agreement.

The seeded masterdata attributes in ICI:

 

Creating Bulk Agreement

Let us consider an example where we create an agreement using the contract type Automation All DataTypes Attributes which is already configured for the bulk creation.    

1. Click the Agreement Management tile on the Home page. The Agreement Management menu opens.
2. Click the Create Agreement menu. The Create Agreement menu opens.
3. Select the Contract Type Name. For example, Agreement CT with All DataTypes Attributes.
4. Select Type Of Paper as Own.

 
5. Click Next. The Attributes tab opens.
6. Select Yes from Enable Bulk Agreement Creation drop-down list. 
 

Note:  The Enable Bulk Agreement Creation determines that the created agreement is a model agreement for the bulk creation.

7. Select parties from the Other Parties drop-down list. For example, Other Party 01, Other Party 02, & Other Party 03.
 

Note: The Other Parties drop-down field is basically a multiselect attribute having a technical name BulkCreateSourceAttribute from the Masterdata Contract type which will be used as a spawning attribute (for model agreement) and the Other Parties drop-down options are IndividualSourceAttribute. When bulk agreements are created, each value of Other Parties drop-down field will be spawned by  IndividualSourceAttribute.

8. Enter All Data in the Test Case Id field.

 
9. Click Next. The Select Template tab opens.
10. Select All Data Types Basic Template.

 

 

11. Click Next. The Verify tab opens.
12. Click Create and Publish. The Details window opens. The agreement changes to Draft state.
13. Click Show more. 

 

 
14. Click Generate Bulk Contracts. The Information window opens.

 

 
15. Enter a unique batch identifier. For example, Batch-4284. 
 

Note: The batch identifier must be a unique number.

 

 
16. Click Ok. The Information window opens displaying that Bulk Creation for Batch-4284 initiated successfully.

 

 
17. Click Ok. The Bulk Creation action started in the background. Users get the notification email that Bulk operation is completed along with the information regarding the success and failure of individual agreements created. 
18. Click the Agreement Management tile.
 

Note: To filter agreements created by any batch id, users need filter agreements using Bulk Agreement Batch Identifier.

 

19. Enter Bulk Agreement Batch Identifier in the Categories field.
20. Select the batch identifier from the drop-down list.

 

All three agreements (Other Party 01, Other Party 02, & Other Party 03) are created using Bulk action. The Agreements created using Bulk action are in the Draft state and users are notified regarding the success and failure of agreements created. 

 

Creating peer agreement from base agreement

It is possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it. 
You can also create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - Allow Peer Creation Wizard, Allow Multiple Instances andAllow Two-Way Linkage.
 
Consider an example of creating a peer-peer association (of SOWs) from within the base agreement (MSA). 

 

Creating the base contract type 

Let’s create a base agreement such as an MSA.

1. Click Home > Configuration > Create Contract Type. The Create Contract Type page opens.

 

2. Select Agreement.
3. Click Next. The Details tab opens.

 

4. Enter a Contract Type Name. For example, Automation MSA_PeerAssociationcreation.

 

5. Click Next. The Attributes tab opens. 
6. Select the Available Attributes and move to the Selected Attributes column. 
7. Edit the attributes as required. Click Save.

 

Creating an association of the base agreement 

Let’s create an association of the base agreement as a peer such as a SOW. 

8. Click Next. The Associations tab opens.
9. Click + Association.

 

10. Enter an Association Name. For example,ICMSOWPeercreation. 
The Associated Contract Type is automatically populated and Relation Type is Peer.

11. By default, all flags are set to No. You may set the flags to Yes as required. However, the following flags must be enabled: 

• Toggle the Allow Peer creation wizard flag to Yes. This allows the user to create the peer association instance and directly link it to the base agreement. In this case, the association ICMSOWPeercreation will directly be linked to the base agreement Automation MSA_PeerAssociationcreation as a peer.
• Toggle the Allow Inheritance flag to No.
• Toggle the Multiple Instance flag to Yes to create multiple peer agreement instances in the base agreement. 
• Toggle theAllow Two Way Linkage flag to Yes for both the base and peer assocaition. This creates a two-way linkage so that the peer association gets linked to the base agreement and vice-versa. 

Peer agreement can also be created from within the base agreement in Executed state.

The configuration key “Core.Agreement.StatesToAlowPeerAssociationsPostExecution” is used to create the association from the executed state of the base agreement.

Note: To copy with association, the peer association that has Allow peer creation wizard enabled will be skipped.

12. Click Save. The created association ICMSOWPeercreation will be displayed in the Association list on the left hand side.

13. Click Next. Enter the required details in the following tabs.
14. Verify all the details and click Create. The Contract Type Details page opens.
15. Click Send For Approval. The Configuration page opens listing the created Contract Type -  Automation MSA_PeerAssociationcreation in an Approved state.

16. Click the View Record icon next to this entity to view the contract type details. 
 

Creating association for peer contract type 

Create a peer contract type in the similar way as mentioned in section 1. For example, Automation SOW_PeerAssociationcreation.

Then create an association of the base agreement under peer contract type Automation SOW_PeerAssociationcreation. 

17. ClickNext. The Associationstab opens.
18. Click+ Association.

19. Enter an Association Name. For example,ICMPeerCT_MSAassociation. 
The Associated Contract Type is automatically populated andRelation Type isPeer.

20. By default, all flags are set to No. You may set the flags to Yes as required. However, the following flags must be enabled: 

• Toggle the Allow Inheritance flag to Yes. This inherits the values from the base agreement into the peer agreement. In this case, the association ICMPeerCT_SOWassociation will directly be linked to the base agreement Automation MSA_PeerAssociationcreation as a peer.
• Toggle the Allow Two Way Linkage flag to Yes for both the base and peer contract type assocaition. This creates a two-way linkage so that the peer contract type association gets linked to the base agreement and vice-versa. 

21. Click Create to create the peer contract type with MSA association. 

 

Create multiple associations from base agreement

The base agreement MSA can have multiple associations (SOWs), but the associations (SOWs) can have just 1 parent agreement.

22. Create MSA agreement and go to Details page. 

23. Under the Associations section in the left navigation pane, all the associations will be listed. Click the Add icon against a particular association. In this example, Automation SOW_PeerAssociationCreation.

The page will redirect the user to the new agreement creation wizard for Automation SOW_PeerAssociationCreation. 

The contract type name will be auto-populated.

24. Select Own Type Of Paper from the drop-down.
25. On the Attributes page, attribute values from base agreement will get inherited into peer attributes.

26. Click Next on the following tabs.
27. Verify the details and click Create to create the agreement. 

The peer agreement will get linked to the base agreement.

28. Click View Record icon next to the created agreement on the agreement index page. The agreement Details page opens.

The agreement details displays the peer to peer association from within the (MSA_PeerAssociationCreation) listed in the Associations tab. 

Note: 

• The base agreement can have multiple associations; however, the association can have only one base agreement. For example, base agreement is MSA and association is SOW, then MSA can have multiple SOWs, but SOW can be attached to only 1 MSA. This can be achieved by enabling the Allow Multiple Instances flag.
• When copying associations, creating peer to peer association from base agreement is disabled. Hence, the MSA will not be attached to the new SOWs.

 

Adding Contract Manager role for agreements

In the contracting process, a Contract Manager/Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement. This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas the User B might look after the agreement during the negotiation process. 
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.
With this release:
•    Assignment of the user against Contract Manager role in the team can be only achieved through event rules using action Add To Team.
•    Only one Contract Manager is available inside the agreement at any given point of time.
•    The Contract Manager will have provisions same as that of primary owner.
•    Contract Manager Name are displayed on the agreement Summary page.
•    Agreements can be searched using the Contract Manager Name.
•    Managing adhoc modification for Contract Manager role user will be restricted inside the agreement team tab similar to primary owner role user. 

 

Viewing the Contract Manager role in ICI

To view the contract manager role: 
1.    Click User Administration tile and then click User Groups > User Roles.  The User Roles page opens.

2.   Navigate to the section displaying the Contract Manager role. 
3.   Click the icon next to the Contract Manager to edit the Display Name of the Contract Manager role. The Edit window opens.

4.   Edit the Display Name of the role and click Save. The display name for Contract Manager set here will be used across ICI such as on agreement details and summary pages. 

 

Note: You can view and manage the Contract Manager role for ICI entities on the Role Action Mapping page. By default, the access privileges for contract manager role would be the same as that of the primary owner. 

 

 

Adding a Contract Manager to the Team 

Add to Team condition is addition of users to a team after the particular event occurs. For example, addition of approvers after the Agreement Created event occurs. 
You can add a contract manager to the team only using the event rule.

To add a contract manager: 
1.   Select the action as Add To Team and then select Contract Manager role from the drop-down and the appropriate user.

 

Note: You can add only one and the users who are provisioned in ICI as the contract manager.

2.   Click Next and then click Create to create the event rule. 

 

Viewing Contract Manager in Agreement Team 

You can view the contract manager added in the agreement team if the event rule is executed as expected. 

 

Note: You can also view the contract manager on the agreement Details page in the Summary section.

 

 

Searching an agreement with Contract Manager role 

Select the attribute from the drop-down on agreement index page to display the list of users with contract manager role. 

 

Ability to support Approver Sub-roles 

Users have the ability to define sub-roles for the Approver role. This flexibility enables all the capabilities of the Approver for the users at the sub-role level.
For example, you can now set different types of approvers for an agreement based on functions such as legal approver, finance approver, and so on. This can be achieved through a technical configuration.

Provisioning User

User roles can be provided while Provisioning users. 
1. Click User Administration >Users > Provision Users. The Provision User page opens.

 
2. Select a user from the Active Directory Users column and move to the Selected Users columns using the right arrow key. The user details are displayed.
3. In the Personal Details tab, select Approver Role from Roles drop-down.
    For example, Finance Approver.

 

  
4. On the Work Details tab, enter the details.
5. Click Next. The User Details page opens. The Finance Approver Role is added. 

 

Creating a User Group

The user created above can create a User Group. 

To create a User Group:

1. Click User Administration > User Groups > Create. The Create User Group page opens. 
2. On the Details tab, enter the Name and Description for the user group.
3. Click Next. The Users tab opens.
4. Click Add User icon. The Add User window opens.
5. Select the sub-roles for the User Group from the Roles drop-down. For example, Finance Approver, Investment Approver.  

 
 
6. Click the Add User button. The user group of the sub-roles is displayed which you selected above.  

 

 
7. Click Next. The Verify tab opens. You can verify that the created group is created with the appropriate role.

 

 
8. Click Save. The User Groups Details page displays the created user group with the sub-roles.

Creating a Rule for the sub-role

You can add a user for a sub-role by creating a Rule. The user Roles drop-down is only available for the Approval Rule and Notification Rule types. 
1. Click Configuration > Rule > Create Rule. The Create Rule page opens.
2. Select the Contract Type from the drop-down.
3. Enter the Rule Name and Rule Description.
4. Select the Rule Type. For example, Approval Rule. The Team Role field is displayed.

Note: The user Roles drop-down is only available for the Approval Rule and Notification Rule types. 

5. Select a Team Role for the user. For example, Approver.
6. Click Next. The Build tab opens. 
7. Click the Add Rule button. 
8. In the Action section, select Require Approval From Any.
9. Select the User Role from the drop-down. For example, Finance Approver.

 

10. Click the Search User icon to select a user for the sub-role. The Search User window opens.
11. Click Add after selecting the user. 

 
12. Click Next. The Build tab opens.
13. Click Next. The Summary tab opens displaying details of the created Rule.
14. Click Create. The Rule created successfully message is displayed.

 

  
12. Click Ok. The Rules Details page opens.
 

Note: You can create an agreement by satisfying the created Rule.

13. When the agreement is created, the user with the sub-role (Finance Approver) is displayed on the Team tab of the agreement Details page.  

Creating a Subscription

You can create notification settings for the created sub-role.

1. Click User Administration > Notification Setting > Subscription. The Create Subscription page opens. 
2. On the Details tab, enter the user details for the Subscription.
3. Click Next. The Template tab opens.
4. Enter the sub-role Display Name in Template Subject and the sub-role details In the Template Body.
5. Click Next. The Recipient tab opens.

6. Click the Add Recipients icon to add the recipient. The Add Recipients window is displayed.

 
7. Select the Roles from Select Roles drop-down. For example, Finance Approver.


 

Note: The Roles available in the drop-down are Sub-Roles and not Approver Role as it is a primary role. 

8. Click Next. The Verify tab opens.

 
9. Click Save. The Subscription Details page opens. 

The subscription with the user sub-role Finance Approver is created.

Limitations of Approver Sub-roles

This functionality has the following limitations:

• Sub-roles can be defined for the Approver role only.
• The following sub-roles are supported in the workflow of User Group, Agreement, Amendment, Associated Document, Rule creation based on Approval Rule, Subscription, Notification, Auto-delegation, and Broadcast from the Agreement Details page. 
• When the sub-role for the Approver role is defined in addition to the existing Approver role, in that scenario all roles new and old are supported unless the user disables the existing Approver role. ICI behaves as is and data migration with respect to the new and old role is not supported. 

Flexibility to control the Agreement actions based on the user role

The access control for Agreements and Amendments has been extended to control additional agreement level tasks and actions based on the user role.

Users can control:

1. The agreement actions such as Compare Documents, Compare Clause Changes, Broadcast and so on
2. Creation and disassociation of associated documents from an agreement
3. Linking and disassociation of peer association from an agreement
4. The visibility of the individual reports available on the agreement details page is controlled through technical configuration

Controlling the actions available on the agreement details page using the Role-Action Mapping

Consider an example where the agreement Automation AssoTwocolumn has the user added in the team as Approver. The agreement action Broadcast has the user role Approver mapped for the agreement in Draft state. If you remove the role approver from this role-action mapping, he or she will no longer has the access to the Broadcast action on agreement page for Draft state.

Click on the Team tab in the left panel configuration on the agreement details page to view the users added in the team. For example, user William Fagan is added as Approver for the agreement Automation AssoTwocolumn.

 

The role-action mapping for the agreement Broadcast action for Draft state has user role Approver mapped.

Now remove the user role Approver from the Broadcast action and Draft state.

To edit the role action mapping: 

1. Click User Administration > User Groups > Role-Action Mapping on the Home page. The Role-Action Mapping page opens.
2. Select entity in the Select Entity field. For example, agreement Automation AssoTwocolumn. The list of all Role-Action mappings applicable to the agreement opens.
3. Click Edit icon next to the action for particular state you want to edit. For example, action Broadcast for state Draft. The Edit window opens.
4. Add or remove the User Roles in the right section with the help of arrows. For example, remove user role Approver from right section.
5. Click Save. The role is removed from the Roles column for selected action and state.

 

The user with role Approver will then not be able to view the action Broadcast for the agreement in Draft state.

 

Note: User can set the role-action mapping for all states of the agreement and associated documents for all actions and user roles following the same process.

 

Controlling the Associations actions on the Agreement page using the Role-Action Mapping

The access to the associated documents of the agreement can be controlled by role action mapping.

Only authorized users can:

• Add associations to the agreement from left panel configuration on the agreement details page
• Dissociate the associated document from the agreement from grid page.

Note: User will also need to have the access privileges to the Associated Document Contract Type via Security Groups in addition to Role-Action Mapping configuration.

 

Create Associations instances from Agreement details page

To control access on the associations creation action from agreement details page through role-action mapping:

1. Click User Administration > User Groups > Role-Action Mapping on the Home page. The Role-Action Mapping page opens.
2. Select entity in the Select Entity field. For example, Automation Annexure Assembly (Associated Document Contract Type). The list of all applicable role-action mappings opens.
3. Click Edit icon next to the action for particular state that you want to edit. For example, Create Association From Parent. The Edit window opens.
4. Add or remove the User Roles in the right section using arrows. For example, add Primary Owner.

 

5. Click Save. The role is added to the Roles column for selected action and state.

 

The Create Associations action for Automation Annexure Assembly on the left panel configuration will be disabled for all users other than Primary Owner. For example, the Create Association action is disabled for the user William Fagan with the user role as an Approver.

 

 

Controlling the access for Association instances from the Association grid

Only authorized users can edit, dissociate or copy associations from agreement-association grid page. These actions are controlled using role-action mappings defined for respective parent-child or peer-to-peer associated document contract type. 

To control access on the association actions through role-action mapping:

1. ClickUser Administration >User Groups> Role-Action Mappingon the Home page. The Role-Action Mappingpage opens.
2. Select entity in the Select Entity field. For example, Automation Annexure Assembly (Associated Documents Contract Type). The list of all applicable role-action mappings of the association opens.
3. Click Edit icon next to the action for particular state that you want to edit. For example, Edit. The Edit window opens.
4. Add or remove the User Roles in the right section with using arrows. For example, add Primary Owner, Secondary Owner and Document Owner.
5. Click Save. The role is added to the Roles column for selected action and state. For example, For Automation Annexure Assembly, only Primary Owner, Secondary Owner and Document Owner can edit the Associations for Draft state.

 

When the user other than above roles tries to access the agreement, the Edit, Dissociate and Copy actions will not be visible to him from the agreement-association grid page. 
For example, the Edit, Dissociate and Copy action are not visible to the user William Fagan with the user role as an Approver.

 

 

Adding Static and Dynamic Filters

You can add Static and Dynamic filters after configuring the filters on Masterdata records. For more information about Static and Dynamic filters configuration, see Applying filters on Masterdata records. 

Adding Static Filters

To add Static filters: 

1. Click the Agreement Management tile on the Home page. The Agreement Management menu opens.
2. Click the Create Agreement menu. The Create Agreement menu opens.
3. Select the Contract Type Name. For example, MSA.
4. Select Type Of Paper as Own.

 
5. Click Next. The Attributes tab opens. 
6. Click the Filtered Lookup Search or Add New Record icon in the Country Name String drop-down list.


 
The Country Name String attribute displays all countries except the country West Indies as set in the configured static filter.  

 
The predefined Static filter is applied to the masterdata record.

7. Select the checkbox as per requirement. For example, Indonesia.
8. Click Select. 
9. Click Next.
Complete the remaining tabs of Select Template and Verify to move the Agreement to the Draft state.

 

Adding Dynamic Filters

To add Dynamic filters:

1. Click the Agreement Management tile on the Home page. The Agreement Management menu opens.
2. Click the Create Agreement menu. The Create Agreement menu opens.
3. Select the Contract Type Name. For example, MSA.
4. Select Type Of Paper as Own.

5. Click Next. The Attributes tab opens. 
6. Select the country in the Country Name drop-down list. For example, Singapore. 
7. Click the Filtered Lookup Search or Add New Record icon in the Country Name String drop-down list to select the country. For example, Singapore.

 

 

The Country Name String attribute displays all countries except the country Singapore which is filtered dynamically based on the Country Name attribute value. This is as per the configuration where Country Name String attribute value is dynamically linked to the attribute value of Country Name.
 

 
8. Select the checkbox. For example, Indiana.
9. Click Select. 
10. Click Next.
Complete the remaining tabs of Select Template and Verify to move the Agreement to the Draft state. 

Ability to have flexible contract type extension

ICI provides the flexibility to select and use masterdata attributes as extensions to agreements and associated documents at the time of instance creation. Users can create rules to add or remove these extended attributes to agreement and associated documents. ICI capabilities support the extension attributes in the same way as normal attributes. 

Users can:

• Configure conditional attributes, tracking attributes, computations (enable expressions) to use as extended attributes
• Save extension attributes selection as a template for reuse
• Control access privileges for extended attributes based on the user role
• Maintain audits for the extended attributes

Defining access for extension attributes actions using Role Action Mapping

The authorized users can control the access privileges for the actions Configure Attributes and Re-evaluate Rule on the Extension Attributes page during agreement creation through Role-Action Mapping.

1. Click User Administration > User Groups > Role-Action Mapping on the Home page. The Role-Action Mapping page opens.
2. Select entity in the Select Entity field. For example, Agreement. The list of all role-action mappings applicable to the agreement opens.
3. Click Edit icon next to the action for particular state you want to edit. For example, Configure Extension Attributes for state Approved. The Edit window opens.
4. Add or remove the User Roles in the right column with the help of arrows. For example, add user roleBusiness Owner to the right column.

 

5. Click Save. The role is mapped under the Roles column for selected action and state.

The users with role as Business Owner will now be able to access the action Configure Extension Attributes for the agreement entities in Approved state. For example, user Anushree added to the agreement’s team as Business Owner can access Configure Attributes action on Extension Attributes page for the agreement entities in Approved state. 

 

Defining access for extension attributes using Attribute Group Privileges

Authorized users can restrict the access to extension attributes for specific users using Attributes Group Privileges.

To restrict the access:

1. Click User Administration > User Groups > Attribute Group Privileges > Add on the Home page. The Add window to configure and add the attribute group privileges opens.
2. Select Copy from Contract Type. For example, RFQ.
3. Toggle Show Extension attribute Group to Yes.
4. Select Attribute Group for which you want to restrict the access. For example,Location Details.
5. Select States for which you want restrict the access. For example, Approved.
6. Select user Roles for whom you want restrict the access. For example, Business Owner.
    

 

7. Click Save. The Mapping added successfully message is displayed. The added mapping will be displayed in the table on attribute group privileges page under the selected entity.

 

The user with roleBusiness Owner will be restricted to access the selected attribute group in selected state. For example, user Anushree (added as Business Owner to the agreement’s team) will not be able to access Location Details attributes for the RFQ contract type in Approved state.

 

Making the contract type available for extension attributes selection

Users can make the attributes of masterdata available for extension by setting Is available to be used as Extension field to Yes. Masterdata contract types which have this field value set to Yes will only be available for extension on the Configure Attributes window during agreement creation. 

Note:  By default, the Is available to be used as Extension field is set to No for all masterdata contract types.  Ensure to set this field to Yes to make the attributes of the desired masterdata contract type available for extension.

To edit the masterdata:

1. Click Configuration > Contract Types on the Home page. The Contract Type index page opens.
2. Click View Record icon next to the masterdata contract type you want to edit. For example, Food Master. The contract type Details page opens. 
3. Click Edit. The Edit Contract Type page opens.
4. Toggle the Is available to be used as Extension field to Yes.

 

5. Click Next. 
6. Edit the details on the remaining Display Preference and Team tabs if required.
7. Verify the details and click Update. The contract type is updated.

The masterdata Food Master is then available on the Configure Attributes window in the Select Contract Type drop-down during agreement creation.

 

 

Examples of different attribute types available as extension attributes

Attribute types such as conditional, lookup, computations (enable expressions), tracking, multi-select choice and so on can be configured to support extension attributes.

For example, the masterdata Vehicle Master has types of attributes which can be extended. The attribute Place of delivery Vehicle is conditional attribute and it’s value depends upon the Do you want to Place Order attribute’s value. 

 

The attribute Place of Delivery Vehicle is displayed only when the attribute Do you want to Place Order is set to Yes.

 

Note: User cannot delete the parent extension attribute if there are any dependent conditional or cascading attributes.

 
Users can make the attribute mandatory by setting the Is Required For Extension attribute field On in the contract type. 

 

For example, the attribute Vehicle Part Number is mandatory (with red asterix mark). The mandatory attributes are available on the Extension Attributes tab during agreement creation by default and users cannot remove them. For example, the delete action is disabled for the mandatory attribute Vehicle Part Number.

 

 

Note: Extension attributes can be configured to be excluded during copy agreement through technical configuration.

 

Creating Agreement and Associated Document instances with flexible entity attributes

1. Click the Agreement Management menu. The Agreement menu opens.
2. Click Create Agreement. The Create Agreement page opens.
3. Select the Contract Type Name. For example, Quotation.
4. Select the Type Of Paper.

 
5. Click Next. The Extension Attributes tab opens.
On clicking the Next button, the Extension Selection rule for Agreement Contract Type (Quotation) gets triggered and all the configured attributes of Select Extension Contract Types (PurchaseMaster), Select Extension Attributes (FoodPurchaseMaster) and attributes group Quality (FoodMaster) are already selected and available in the Extension Attributes tab.

6. Enter Order ID.
7. Enter Food Category.
8. Select Order Date.
9. Select Expiry Date.
10. Select the Order Status from the drop-down list.
11. Enter Quantity.

 

 
12. Click the Configure Attributes icon to add or remove attributes. The Configure Attributes page opens.
 

 

13. Select Food Master in the Select Contract Type drop-down field. 
14. Select the attribute Storage Information from the Available Attribute list.
15. Click the arrow icon to move the attribute to the Selected Attribute list.
16. Click Next. The View and Confirm tab opens.
17. Click Confirm. The Storage Information field is added to the page.

 

 
18. Click Next. The Verify page opens.
19. Click Create and Publish. The agreement status changes to the Draft state. 
 

 

20. Click the Create Association icon in the Associations tab. The Create Association page opens.
21. Enter a Name. For example, Raw material.
22. Enter a Product ID.
23. Select the Priority from the drop-down list. For example, Medium.
24. Select the Category from the drop-down list. For example, Other.

 

25. Click Next. The Extension Attributes tab opens.

On clicking the Next button, the Extension Selection rule for Associated Document Contract Type (Quotation Line Item) gets triggered and all the configured attributes of Select Extension Contract Types (PurchaseMaster) and attribute groups (FoodMaster) are already selected and available in the Extension Attributes tab.
The Other category displays the three attributes Order ID, Order Date and, Order Status as per the configured Extension Selection rule. 

26. Enter the Order ID.
27. Select the Order Date from the drop-down list.
28. Select the Order Status from the drop-down list.

29. Enter the details in the fields on the attribute group Quality.

 
30. Click Create. The Associations Quotation Line Item is created.

 

 
Let us now create another Quotation Line Item with a Food Category and also insert attributes from other Contract Type dynamically.  

31. Click the Create Association icon in the Associations tab. The Create Association page opens.
32. Enter a Name. For example, Raw material.
33. Enter a Product ID.
34. Select the Priority from the drop-down list. For example, Medium.
35. Select the Category from the drop-down list. For example, Food.

 

 
36. Click Next. The Extension Attributes tab opens.

On clicking the Next button, the Extension Selection rule for Associated Document Contract Type (Quotation Line Item) gets triggered and all the configured attributes of Select Extension Contract Types (PurchaseMaster), Select Extension Attribute Groups (FoodMaster) and Select Extension Attributes (FoodPurchaseMaster) are already selected and available in the Extension Attributes tab.
The Food category displays the attributes: Order ID, Order Date and Order Status from PurchaseMaster Contract Type, Food Category, Expiry Date, and Quantity from FoodPurchaseMaster  and attributes from Quality attributes group from FoodMaster as per the configured Extension Selection rule. 

37. Enter the Order ID.
38. Select the Food Category.
39. Select the Order Date.
40. Select the Expiry Date.
41. Select the Order Status from the drop-down list.
42. Enter the Quantity.
43. Click the Configure Attributes icon to add attributes during run time. The Configure Attributes window opens.

44. Enter the details in the fields on the attribute group Quality.

 
45. Select the Contract Type from the drop-down list. For example, Food Master.
46. Select the attribute Storage Information from the Available Attribute list.
47. Click the arrow icon to move the attribute to the Selected Attribute list.
 

  
48. Click Next. The View and Confirm tab opens.
All attributes and theirContract Types are displayed.

 

 
49. Click Confirm. The Extension Attributes tab opens. 

 

 
50. Click Create. The two Quotation Line Items are displayed.
51. Click the view icon. The Quotation Line Item Details page is displayed.

52. Click the Details tab.

 

 
All attributes of the Quotation Line Item Association are displayed including the recently added Storage Information attribute.

 

For information about configuring the Extension Selection Rules, see Create an Extension Selection Rule.

 

 

Saving the extension attributes selection as a template

Users can save their selection of extension attributes as a template for reuse during the creation of agreement.

To save a template of the selection of extension attribute:

1. Click Agreement Management > Create Agreement on the Home page. The Create Agreement page opens.
2. Enter details on the Details, Attributes and Select Template tabs. 
3. Click Next. The Extension Attributes tab opens.
4. Click Configure Attributes action icon. The Configure Attributes window opens.
5. Select the contract type and its corresponding attributes on Select Attributes tab. For example,VehicleMaster.
6. Click Next. The View and Confirm tab opens.
7. Select the checkbox to Save configuration as an extension template.
8. Enter a name in Template Name field. For example, Vehicle.

 

9. Click Confirm. TheExtension attribute template ‘Vehicle’ saved successfully message is displayed.

The selection is saved as a template and available in Select Template drop-down on the Select Attribute tab.

 

When user selects the saved template, the extension attributes from that template are displayed on the Extension Attributes page during agreement creation.

 

If the user adds a new attribute through Configure Attributes window during agreement instance creation, the existing attributes on theExtension Attributes page evaluated from the rule will be retained on the page with their values.

 

Setting a template as default for associations

Users can save the selection of extension attributes as a template to create the associations for agreements or amendments instances.

To save a template for the association for the agreement:

1. Click Associations on the left panel configuration on agreement Details page. For example, Line Item.
2. Click Create Associations. The Create Association page opens.
3. Enter the details on Metadata tab.
4. Click Next. The Extension Attributes tab opens.

 

5. Click Confiure Attribute action icon. The Configure Attribute window opens.
6. Click Next. TheView and Confirm tab opens.
7. Click checkbox for Save configuration for all future associations. The Extension attribute template saved successfully message is displayed.

 

The selected extension attributes will be available by default on the Extention Attributes page during future assocaition creations for the current agreement instance.

 

Audit with Extension attribute

Changes in extension attributes are captured and can be viewed on the History tab. For example, changes in extension attribute Vehicle Type from Vehicle Master are captured.

 

Saving a search with extension attributes

Users can search and retrieve entities with extended attributes as search parameters and save the search criteria as a saved search. Extended attributes are available in search facets drop-downs along with regular attributes. 

To search entities with extension attributes:

1. Click Search on the Home page. The Search page opens.
2. Select entity in Entity drop-down. For example, Agreement.
3. Select extended attribute as search parameter in the Categories drop-down. Extension attributes are available in search drop-down with Extension Attributes: prefix. For example, Extension Attribute: Vehicle Type. 

All the entities with extension attribute Vehicle Type will be displayed.

Refer to Using Advanced Search for details on using search filters, operators, and options.
Users can save the search criteria with extended attributes as search parameters and use as global or local Saved Search. Refer to Saved Searches for details on saving a search. Refer to Using Advanced Search for details on retrieving a Saved Search.

Using the Activity Panel 

The Activity Panel tile helps logged on users to track, create and resume workflow actions at the agreement, association and amendment levels.  

Configuring the Activity Panel tile

1. Click the User Administration > Application Settings on the Home page. The Application Settings page opens.

 
2. Click the Other Configuration tab. 
3. Toggle the Show Activity Panel to Yes. 
4. Click Update. The Application Settings updated successfully window opens.

 
 
5. Click Ok. The Activity Panel tile is displayed.

Displaying the Activity Panel tile at the agreement level

1. Click Agreement Management > Create Agreement on the Home page. The Create Agreement page opens.

  
2. Enter all the details on the Create Agreement page.
3. Select a Contract Type Name. For example, MSA_Calculations.

 
4. Enter the remaining details in the Attributes section.
5. Click Next.
6. Select a file for the Template.
7. Click Next. The Verify window opens. 
8. Click Create or Create and Publish or Create and Send for Approval as required. The agreement is now in the Draft state. 

As soon as the agreement moves to Draft, a validation message is displayed to the user indicating that the request has been successfully submitted. The Activity Panel displays the number of activities completed by the user for any given session. 
 

Note: Activities are either in the Completed or In Progress states. The Completed activities are visible in the Activity Panel so long as the user remains active on Activity Panel.

 

9. Click the respective entity to view its details page.
The count on the Activity Panel gets incremented as and when the user performs activities during a given session.

 

Note: Limitations of the Activity Panel.
* Activities are displayed in the same browser tab only. If the user opens any other browser, the current activities will not be displayed.
* Activities are displayed in the logged on tab only. If the user opens another tab, the current activities will not be displayed.
* If the logged in user closes a session and opens a new tab, then the current activities will not be displayed.

Canceling an Agreement

The Primary Owner can cancel or delete an agreement in any state, except executed. The Cancel button is displayed once the Agreement is published.

To cancel an Agreement:

1. Open the Agreement that you wish to cancel from the Agreements page.

2. Click Cancel. The he Add Note page opens.

3. Select a Reason Code and type a note for cancelling this agreement. Though this field is optional, it should be used to enter detailed notes for future reference. The Reason Code is mandatory; select one from the drop down list.

4. Click Add. The status of the agreement changes to Cancelled.

The cancellation action appears in the History section of the Agreement Details page. The cancelled Agreement continues to be displayed in the Agreement searches and you can revert cancelled agreements to draft state from the Agreement Details page.

Editing an Agreement

You can edit an Agreement at any stage till it is executed. Editing an executed agreement involves going through the approval process with both internal and external parties again.

To edit an existing Agreement:

1. Click the View Record icon next to the Agreement you wish to edit on the Agreements page. The Agreement Details page opens.

2. Click Edit. The Create Agreement page opens.

3. Follow the steps in Creating an Agreement section to edit the Agreement.

4. Click Update to save your changes.

5. Click Upload Document to upload the new version fot he docuemnt. When a new document version is uploaded to ICI, the user is redirected to the Versions page.

• If the new version being uploaded includes changes to key document tags such as Attribute, Clause, Association or Signatory tags, i.e. if a tag has been added, removed or their values changed; while uploading the document, the user receives a notification that specifies the details of the changes (i.e. added, deleted or attribute/clause value changed). The notification includes an option to proceed with the changes or cancel them if found to be unintentional. If the user continues, the document is uploaded to ICI and a summary of changes gets logged in the Versions tab. Tags are tracked based on changes to tag count between two document versions and only for .docx formats. Changes regarding the position of tags are not tracked and notified.
• If the new version being uploaded includes a tagged Association that has margin less than that of the Agreement or Amendment document, the user receives a notification regarding the margin mismatch between the two. The notification includes an option to proceed with the changes or cancel them if found to be unintentional. If the user continues, the document is uploaded to ICI and changes logged in the Versions tab against the particular version. The notification includes information about margin and orientation differences. If the Agreement or Amendment includes more than one tagged Association, all Associations having lesser margin than the Agreement or Amendment document are included in the notification. Margin tracking is done only for .docx file types. The Type Of Paper differences are not included (e.g. A4, Legal).

Copy the Existing Agreement

Users can copy an existing agreement and create a new agreement using Copy Record functionality. The resulting agreement will be a copy of existing agreement with all the metadata and selected associated documents from existing source agreement. The source agreement’s latest approved template will be selected by default to create the copy.

Configuring contract type to enable copy existing agreement

Authorized users can configure Agreement Contract Type and set Allow Copy With Associations field to Yes to enable Copy record. The agreement created using this specific Contract Type will have Copy Record feature enabled by default.

To configure agreement contract type:

1. Click Configuration > Create Contract Type > Agreement > Next on the Home page. The Create Contract Type page opens.
2. Toggle Allow Copy With Associations to Yes on Details tab.
3. Enter remaining details on the Details tab.
4. Click Next. The Attributes tab opens.

4. Enter the details in the remaining fields on Attributes, Association, Display Preference and Team tabs.
5. Verify and click Create.
6. Approve and Publish the Contract Type.

You can also edit the existing contract type and set the Allow Copy With Associations to Yes to enable the Copy Record functionality.

 

Copy the agreement from agreement details page

Follow these steps to copy an Agreement:

1. Click the Agreement Management > Agreement on the Home page. The agreement index page opens.
2. Click View Record icon next to the Agreement for which you would like to create copy.
3. Click Copy Record icon. The Copy Record page opens.
4. Select the Associated Documents and Commitments that you want to copy in addition to the Agreement Metadata in the resulting Agreement. You can either select the Associations and Commitments checkbox to select all available Associated Documents and Commitments or select the checkboxes for specific Associated Documents and Commitments.

 

Note: Users can now exclude Associated Documents, Associated Documents Attributes, Commitments and Commitments Attributes and extension attributes when copying Agreements through a technical configuration at the Contract Type level.   

5. If the Associated Document selected is of the Parent-Child type, then a new copy of that Associated Document is created and attached to the copied Agreement. However, if the Associated Document is of the Peer-to-Peer type, then the actual Associated Document is attached.
6. Click Copy, this creates the copy of the original Agreement with your selections. The Agreement created is in Draft state.

Note: The Associated Document of Prerequisite and None constraints can only get copied.

 

Exclude auto-attached associated documents during copy

ICI allows attaching standard documents from the masterdata repository as associations to the agreement based on the defined event rule on the agreement. 

When a user copies the agreement with auto-attached associations, system excludes all auto attached associations from being copied to the new agreement. The auto-attached associations won’t be displayed on the Copy Record window. The resulting agreement has the selected manual associations and its own auto-attached associations as per the configured rules.

This avoids the unnecessary upload of files into the ICI repository and duplication of association records on copied agreement as it will have its own auto-attached documents. 

Users can select auto-attachment associations when an agreement is sent for signature along with the bundled association and download all associations of an agreement in the ZIP format.

 

Copy the agreement from agreement index page

You can copy the agreement by clicking Copy Record icon next to the agreement name on the agreement index page.

You can only copy published agreements. The error message will be displayed if users try to copy non-published agreement.

Click Ok to go back to the agreement index page.

 

To copy an agreement from agreement index page:

1. Click the Agreement Management > Agreement on the Home page. The Agreement index page opens.
2. Click Select Action (3 dots) icon next to the Agreement of which you would like to create a copy. For example, Saas Agreement. The drop-down with available actions opens.
3. Click Copy Record . The Copy Record page opens.

 

1. Click the checkbox next to the Associations and Commitments that you want to copy in addition to the agreement metadata in the resulting agreement.

 

Note: Users can exclude Associated Documents, Associated Documents Attributes, Commitments and Commitments Attributes when copying Agreements through a technical configuration at the Contract Type level.

4. Click Copy. The copy of the original agreement with your selections is created in Draft state.

 

When Allow Copy with Association in the Agreement Contract Type is False and users try to copy the agreement from agreement index page, the confirmation message is displayed.

After clicking Ok, the agreement will be copied and new agreement is generated in Draft status.

 

Only users with manage privileges can copy the agreement record. The error message will be displayed if unauthorized users try to copy the agreement.

Click Ok to go back to the agreement index page.

 

Word Document Compatibility between two different ICI Instances 

For example, consider a scenario where a user (non-owner) is using a document as third party paper created by the user (owner) and makes some changes in the Word document and sends it to the owner. The owner then uploads the modified version of the Word document. ICI now also supports document assembly, data sync (of metadata, clauses), etc. of the agreement document.

Creating an Agreement by the Owner in an ICI Instance

1. Click Agreement Management > Create Agreement on the Home page. The Create Agreement page opens. 

4. Enter all the details on the Create Agreement page. 
5. Select Own for Type Of Paper.
6. Select Contract Type Name. For example, Clinical Trials Agreement.

7. Follow the steps to create the agreement. It is now in the Draft state. 

 

Modification of an agreement by a Non-Owner using Owner’s document in a different ICI Instance

1. Click Agreement Management > Create Agreement on the Home page. The Create Agreement page opens. 
2. Enter all the details on the Create Agreement page. 
3. Select a Contract Type Name. For example, MSA_SD.
4. Select the Type Of Paper field. The Non-Owner will select the Third Party type of paper.

5. Click Next. The Attributes tab opens.
6. Upload the owner’s document to non-owner ICI instance. 
7. Follow the remaining steps to send the agreement to the Draft state. The document gets uploaded with a message indicating that Document Assembly is restricted for this agreement.

Now make some changes in the agreement document at Non-Owner’s ICI instance that is uploaded in the Owner’s instance. For example, change tagged effeective date December 10, 2019 to December 12, 2019 in the document.

 

Note: Reverse sync and document assembly are restricted for the non-owner system. 

 

Uploading the revised agreement document in the Owner’s instance

1. Click Upload Document in the Owner’s instance. The Upload Document window opens.

2. Click Select File to upload the modified agreement document.  

3. Click Upload File. The Please Confirm window opens indicating the changes in the original document.

4. Click Yes.
5. Click Preview in the agreement Details tab. You can now view the changes that were made to the agreement document at Non-Owner’s instance in the owner’s instance as well.  

Collaboration in Contracts  

ICI has eliminated the need to use external tools such as Email, Skype, etc. and created a dedicated space available within the Agreement itself to collaborate between multiple stakeholders.

To collaborate, multiple stakeholders involved in the contracting/sourcing process can:

• Use the Collaboration tab available inside the Agreement 
• Provision an internal/external Team member to communicate with other internal or external team member(s) by creating Topics and posting messages in it
• Provision users to send and receive attachments along with the message
• Provision users to mark the topic as closed once the discussion is concluded
• Send Email notification to participants when messages are posted on the topic

This can be achieved by setting the Enable Collaboration flag to Yes for the Agreement Contract Type, which displays a Collaboration tab on the Agreement Details page. To prevent data loss, once Collaboration is enabled for a Contract Type, it cannot be disabled.  

Configuring Collaboration for Contract Types

To enable Collaboration  for Contract  Types:

1.  Click the Configuration > Create Contract Type on the Home page. The Create Contract Type page opens.

2.  Select the Agreement Contract Type you want to create.  

 

 
3.  Click Next. The Create Contract Type page opens.
4.  Enter a name in the Contract Type Name field. For example, Collaboration Contract Type.
5.  Enter all the details on the Details tab. 
6.  Toggle the Enable Collaboration flag to Yes to enable Collaboration at Agreement level.
 

Note: The Enable Collaboration flag is only available for Agreement Contract Type.

 

7.  Click Next. The Attributes tab opens.
8.  Enter the details in the remaining Attributes, Association, Display Preference, Team, and Verify tabs to send the Collaboration Contract Type to Approved state.  Alternatively, you can edit an already existing Contract Type to enable the Collaboration tab.

Note: To prevent data loss, once the Enable Collaboration field is toggled to Yes, it cannot be turned back to No. 

 

Creating a new Topic and sending Messages by Internal user and External user

Sending Messages by an Internal user to another Internal user 

1.  Click the Agreement Management > Create Agreement on the Home page. The Create Agreement page opens.

 
 
2.  Enter all the details in the Create Agreement page.
3.  Click the Collaboration tab on the Agreement’s Details page. The Collaboration page opens in the right pane as shown in the below image indicating that there is no topic for you to collaborate as you click the Collaboration tab for the first time. You would see a different window if Topics and its related conversations are already present.
 

4.  Click the New Topic icon. The Create a New Topic window opens.

• You can now select participants who will collaborate and able to send and receive messages for a topic related to the agreement. For example, let’s collaborate with an Internal user, CLM Admin.

 

5.  To select Participants for the Topic, click the Add Team Members icon or you can select all Team members. The Select Participant(s) window opens. For example, let’s collaborate with an Internal user, CLM Admin.

 
6.  Click Add. The Create a New Topic window opens displaying the Participant.
7.  You can choose to keep the topic confidential from other internal participants by toggling the Do you want to mark this topic as Confidential flag to Yes.  In that case, only internal users who are part of the Topic conversation (Participants) will be able to view and reply to the Topic.
8.  Enter the Subject for the Topic. 
9. Enter the message in the Message field. 


 
10.  Click Create. The Topic is created. Based on the confidentiality, participants or other team members can view the created topic, in the Topics window of the Collaboration page.

 

Sending Messages by an Internal user to External user

Let’s consider a case where an internal user wants to collaborate with an external user. 
 
1.  Click the New Topic icon. The Create a New Topic window opens.
2.  To select Participants for the Topic, click the Add Team Members icon or you can select all Team members. For example, let’s collaborate with an External user, Lee Yen Po.


 
3.  Click Add. The Create a New Topic window opens displaying the Participant. 
4.  You can choose to keep the topic confidential from other internal users by toggling the Do you want to mark this topic as Confidential flag to Yes.
5.  Enter the Subject for the Topic. 
6.  Enter the message in the Message field. 

 

 
7.  Click Create. The Topic is created. The participants can view this topic in the Topics window of the Collaboration page and the body of the message at the right.
 

Details such as who initiated the conversation, who took the last action on a Topic, along with the Date, are displayed in the window.

 

Sending Messages by an External user to Internal user

Ler's consider a case where an external user wants to collaborate with an internal user.

1.  Click the Agreement Management > Agreements on the Home page. The Agreement index page opens. 


 
2.  Select the Agreement where you want to Collaborate. For example, SaaS Agreement.

 
3.  Click the Collaboration tab on the Agreement’s Details page. The Collaboration page opens in the right pane. 
 

4.  Click the New Topic icon. The Create a New Topic window opens.
   

5.  Enter the Subject for the Topic. 
6.  Enter the message in the Message field.  
7.  Click Create. The Topic is created. The participants can view this topic in the Topics window of the Collaboration page and the body of the message at the right.

 

Replying Messages

Replying Messages by an Internal user to another Internal user
 

Now let’s see how an internal user Configuration Admin responds to the message sent by another internal user.

1.  Click the Collaboration tab of the Agreement Details page. 
2.  Select the Topic where you communicate with an internal user. Let’s consider topic Informal chat.

 
3.  Click Reply to reply to the message to a single participant or click Reply All to broadcast the message to all participants. The response window opens.

Note: Broadcast icon is only available when the internal users reply to all the participants.

4.  Enter the message in the Message field.
5.  Click Send.

Let’s see how the Internal user views the Internal user’s response.

 

Replying Messages by an External user to Internal user

Now let's see how the provisioned external user Lee Yen Po can respond to the message.
1.  Click the Collaboration tab of the Agreement Details page. 


 
2.  Click Reply to respond to the selected message. 
Based on confidentiality, a message posted by an external user will be visible to participants or other team members, but not external users.
3.  Click Send. 

 

 

Note: Internal and external users are identified in a Topic with two different colors.  

Let’s see how the Internal user views the External user’s response.

 

Email Notifications to Participants

For every message sent or replied in any topic triggers a notification email to its participants and has got the following conditions:

1.  An email notification is sent to all participants whenever an internal or external user posts a message based on confidential condition.
2.  All email notifications can be tracked from the Notifications Alerts present on the Home page and then Collaboration Notifications section present in the Notifications Dashboard.

 

Searching Messages

A user can search messages across topics using the Search tab available in the Collaboration window.   
To search messages in a topic:

1.  Enter the keyword in the Search for Messages field. For example, let’s search the word - Can. All the topics where the message contains the searched criteria are rendered in the search result along with the search word is highlighted. 

Closing the Topics

An Internal user can close the topic when the discussion/conversation is concluded. Once closed, the user cannot reply to a conversation or reopen the topic. 

To close a topic:
1.  Click Close Topic to end any Topic conversation. A message is displayed indicating that once you closed the topic, you can no longer post any new messages in this topic. 

 

2.  Click Yes. The Topic is now closed.

 
The message is displayed in the message window indicating the name of the user who closed the topic along with the date and time.
 

 

Performing Bulk Actions on Agreements

ICI provides users the ability to perform bulk actions on saved searches to efficiently work with entities in bulk and help save time and manual efforts.

The bulk actions on saved searches provides below mentioned functionalities :  

• Performing validation checks against resubmission of in-progress records for same bulk action and display validation message.
• Sending notifications upon bulk action submission and completion.
• Displaying a toast message on the UI along with the bulk action initiation activity on the activity panel upon bulk action submission.

The bulk action notification contains a page link which will display the statistics of the processed records and the live updates on in-progress records.

To take bulk actions on agreements:

1. Click Agreement Management > Agreements on the Home page. The Agreement index page opens.
2. Select a Saved Search to get the set of agreements which you want to process in bulk. For example, Saved Search Todays Task, created for today’s agreements which are waiting to be approved. The agreements matching the criteria defined in the Saved Search are displayed with associated checkboxes.

Note: You need to create a Saved Search beforehand to group desired agreements for bulk processing.

1. Mark a checkbox next to the agreement to select it for bulk processing. The bulk actions will be enabled for selection when you mark at least one agreement.
2. Click the three dots icon in the Bulk Actions column to view available bulk actions you can take on the selected agreements. For example, Approve, Reject, Delete, Send for Approval, Send for External Signature and Download.
3. Select the Bulk Action. For example, Approve. The Add note window opens as per the standard approval workflow.

4. Type a relevant approval note for a future reference and click Add Note. The Confirmation window opens for submitting a bulk action.

5. Click Yes to proceed. The records will be processed according to the selected bulk action.

The ICI system assists users to carry out bulk actions on records through validation messages, in cases, where some or all records are invalid for a submitted request.

On a successful bulk action submission, a toast message will be displayed on the User Interface at the top right corner to notify users about the Bulk Action Initiation.

You can view the details of the in-progress bulk actions on the Activity Panel.

The notifications will be sent on initiation and completion of selected bulk action. You can view the notification on the Notification Dashboard under the Bulk Action Notifications Category.

The notification contains a page link to view the status summary of the submitted bulk action. The page displays statistics of the processed records and also provides the live updates on the in-progress records.

 

 

Ability to configure Reminder Notification on Entities 

ICI provides the ability to send the entity-wise reminder notifications by using the Subscription Reminder Notification Template.  

Creating a Subscription 

To create a Subscription Reminder Notification Template:

1. Click the User Administration tile. The User Administration menu opens.
2. Click Notification Settings. The Notification Settings menu opens.
3. Click Subscription. The Subscriptions page opens.
4. Click Create Subscription. The Details tab of the Create Subscription page opens.
 
5. Enter the Template Name. For example,Reminder Notification.
6. Select the entity from the Entity Name drop-down list. For example, Agreement.
7. Select the Event Name from the drop-down list. For example, Agreement Reminder.
8. Select the Category Name from the drop-down list. For example, Reminder Notifications.
9. Click Next. The Template tab opens.
 
10. Enter a subject in the Template Subject field. For example, Reminder Notification for [$Agreement.Name$] expiry. 
11. Tag attributes from the Attributes section as per requirement. 
12. Enter a message in the Template Body field. 
13. Click Next. The Recipient tab opens. 
 
14. Click the Add Recipients icon to add recipients. 
15. Select recipients from the list. 

Note: The users added in the Recipients tab are notified on Agreement expiry through email. 

16. Click Next. The Verify tab opens. 
17. Click Save. 
  
The Reminder Notification is created for Agreement. It can be viewed on the Notification Template page.
Let us now create a Rule for the Agreement Reminder Event.  

Creating an Event Rule for the Agreement Reminder Event

To create an Event Rule:
1. Click the Configuration tile. The Configuration menu opens.
2. Click Rule. The Rule menu opens.
3. Click Create Rule. The Create Rule page opens.
4. Select the Contract Type. For example, MSA_SD.
5. Enter a Rule Name. For example, Agreement Expiry Notification.
6. Enter a description for the Rule in the Rule Description field.
7. Select Event Rule from the Rule Type drop-down list.
8. Select Agreement Reminder from the Rule Type drop-down list.
9. Click Next. The Build tab opens.
 
10. Click Add Rule under the Build tab.
11. Select the Contract Type from the drop-down list for which you want to apply the condition. For example, MSA_SD.
12. Select the Attribute for which you want to apply the condition from the Select Value drop-down list. For example, Created By.
13. Select the operator from the drop-down list. For example, Equals.  
14. Select the user for which you want to apply the condition from the Enter Value drop-down list. For example, CLM Admin.
15. Select the Action that you want to take from the Actions drop-down list. For example, Set Recurrence Reminder. 
16. Select the template from the Reminder Template drop-down list. For example, Reminder Notification.
17. Enter the value in the Interval field. For example, 1.
18. Select the frequency from the Interval Frequency drop-down list. For example, Day(s).
19. Select the date in the Start Date drop-down list from where you want to start the reminder. For example, Reminder Start Time.
20. Select the date in the End Date drop-down list from where you want to end the reminder. For example, Reminder End Time.
21. Select Yes or No in the Stop Processing More Rules drop-down list.
22. Click Next. The Summary tab opens.
 
The Reminder Notification for Agreement will get triggered every day for the Contract Type MSA_SD created by the user CLM Admin.
23. Click Create.
 
The Agreement Expiry Notification rule gets created. This can be viewed on the Rules page.

Tracking Notifications using the Notifications Dashboard

As per the event rule, reminder notification gets triggered every day and users can keep a track of notifications by using the Notifications Dashboard.

To view notifications:
1. Click the Notifications tile. The Notifications Dashboard opens.
2. Click Agreement Reminder under the Agreement Notifications tab.
3. The Agreement Reminder Notification message is displayed on the right side.  

 

 

Capturing user emails to send notifications

Users can capture multiple valid internal or external email addresses at a run time in a single attribute configured at the contract type level. These email addresses then can be used for sending the automated email notifications and configure the sender’s email ID (From and Reply To Email Addresses) dynamically based on subscription configuration.

Administrators can:

• Configure email attribute to capture single or multiple email addresses while setting up a contract type.
• Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.
• Configure the sender’s email ID (From Email Address) dynamically based on the specific contract type or instance of a record by setting up subscription templates using specific user or role or user attribute.
• Configure the email addresses for Reply To in the subscriptions setup which recipients can revert to.
   

Configuring contract types to capture user emails

Users can enable capturing the single or multiple user email addresses during agreement creation by configuring attributes with Data Type as Email and Email Type Option as Single/Multiple at the contract type level.
To edit the contract type:

1. Click Configuration > Contract Types on the Home page. The contract type index page opens.

2. Click View Record icon corresponding to the contract type you want to edit. For example, ICI Master Service Agreement. The contract type details page opens.

3. Click Edit. The Edit Contract Type page opens.

4. Select Attributes tab.

5. Click Add action icon. The section for adding new attribute opens.

6. Enter a Display name. For example, Observer Emails.

7. Select Email in the Data Type field.

8. Select Multiple in the Email Type Option field. This enables users to enter multiple email addresses in the attribute value.

9. Click Save. The attribute will be added to the contract type.

Note: The Email Type Option field has default value as Single. The field will be frozen once users set it to Multiple and changing back to Single is not allowed.

 

 

10. Add another attribute following steps no. 5 to 9 for capturing a single email address with Data Type as Email and Email Type Option as Single. For example, attribute Customer Email.

11. Click Next.

12. Edit the details in Association, Display Preference and Team tabs if required.

13. Verify the details and click Update. The contract type will be updated with the attributes configured to capture multiple and single email addresses. 

14. Approve the contract type following standard ICI approval workflow.

 

Capturing email addresses during agreement creation

1. Click Agreement Management > Create Agreement on the Home page. The Create Agreement page opens.

2. Select the Contract Type Name for which you want to add recipient emails. For example, ICI Master Service Agreement.

 

 

3. Click Next. The Attributes tab opens.

4. Enter the email in the Customer Email. For example, johndoe@icertis.com.

5. Enter multiple email addresses in Observer Emails field. 

Note: The semicolon (;) is used as a delimiter to separate multiple email addresses.

The Incorrect email address error message is displayed if user enters any invalid email address.

 

 

For example, enter email addresses as james@icertis.com; lily@icertis.com; harry@icertis.com.

 

 

6. Enter other required details and click Next. The Select Template page opens.

7. Select the template and click Next. The Verify page opens.

8. Click Show more link to display all email addresses in the Observer Emails field.

Note: The Show more link is displayed only when there are more than two email addresses present in the multiple email address field. The count of remaining email addresses is displayed along with the Show more link.

 

 

9. Verify the details and click Create and Publish. The agreement is created with the entered email addresses.

 

 

Sample Emails

Users can now configure the Notification Subscriptions  and Notification Rule  to send the automated emails to the captured email addresses.

The email as per the configured Email Types in Subscription and notification rule and email addresses provided in the attributes Customer Email and Observer Emails in the ICM Master Service Agreement instance.

• From Email Type:sample VP Business
• To Email Type: jillwater023@icertis.com
• CC EmailUsers can now configure the notification subscription and notification rule to send the automated emails to the captured addresses. Type: Customer Email Johndoe@icertis.com
• Bcc Email Type: ICMAdmin@icertis.com and Observer Emails as james@icertis.com; lily@icertis.com; harry@icertis.com

 

When the recipient jillwater023@icertis.com replies to the received email, the reply would be sent to the email addresses configured with the Email Type as Reply To:. In this case, Observer Emails attribute value: james@icertis.com; lily@icertis.com; harry@icertis.com.

Labeling agreement document versions as per signature copy

While agreements go through various signature states till executed, users can now navigate to the “Versions” tab and easily identify which version of the agreement is internally signed, externally signed, or fully signed.

A configuration key needs to be enabled for this feature.

To view agreement version labels:

1. Go to Agreement Management > Agreements on the Home page. The agreements index page opens.

2. Click the View Record icon for the agreement for which you want to view the document versions. For example, MSA. The agreement Details page opens.

3. Click the Versions tab in the left navigation pane. The available versions of the agreement are displayed in a table.
 

Depending on whether internal, external or both signatories have signed the document, the Version Label column displays the following:

• Internal Signed Copy: Indicates that all internal signatories have signed the agreement document
• External Signed Copy: Indicates that all external signatories have signed the agreement document
• Fully Signed Copy: Indicates that all signatories have signed the agreement document

Note: 

• The version label is only displayed for agreement and amendment entities. 
• The labels will be displayed only when all the respective signatories have signed the document. For example, if an agreement has 2 internal and 2 external signatories in a mixed signature sequence, then the label Internal Signed Copy will only be displayed after both internal signatories have signed. Similarly, the label External Signed Copy will only be displayed after both external signatories have signed the document. 
   

Ability to approve a contract from email

The approval process has now been streamlined by allowing approvers to directly approve or reject an agreement from within the email itself, through a hyperlink to the webpage, instead of logging in to the system to do so. External users, who do not have access to ICI can now review or approve documents from the notification email, instead of sending offline copies to do so and then uploading them to ICI. This reduces the overall turnaround time and increases productivity. 

Internal users are authenticated through the SSO/IDP before opening the page where the actions are to be taken. External users are authenticated by sending them a code in the email, which has limited validity.

With this release:

• Administrators can add tag an Approve/Reject link in the notification template.
• Approvers/reviewers can download the agreement, modify it and upload it back to ICI based on the access provided.
• Approvers can approve/reject the agreement or amendment from the email, only if the task approval or review is assigned to them. Based on the access, the user can approve or reject the agreement by entering notes or reasons for rejection respectively.

Note: The quick approval link can be configured for send for approval, review as well as delegate event notifications.

Below is an example for allowing users to approve/reject an agreement from email:

1. Go to Home > User Administration > Notification Settings > Notification Templates on the Dashboard. The list of existing Subscriptions is displayed.

2. Select a subscription created for Agreement Sent for Approval event, for example AgreementSentForApproval. You can also create a new subscription for this configuration.

3. Click the Edit button. The Edit Subscription wizard opens.

4. Click Next. The subscription Template page opens.

5. Add the Template:QuickApprovalURI key to the Template Body.  

6. Click Next to continue and complete the wizard.

7. Create a rule, for example AllExtApproverParallel.

When an agreement is created and sent for approval, based on the above configuration, the approvers will receive an email with a link where they can approve or reject the agreement without having to log on to ICI.

To approve/reject an agreement directly from an email:

1. Open the email received from ICI. This email will contain a link to approve/reject the agreement and an access code.

2. Click the hyperlink “click here” in the email. A new page opens displaying a window to enter an access code.

3. Type the access code received in the email.

4. Click Continue, the page reloads displaying a preview of the agreement along with 4 buttons:

• Approve: Click to approve the agreement. The agreement in ICI moves to Approved state.
• Reject: Click to reject the agreement. A reason code needs to be selected while rejecting an agreement. The agreement moves back to Draft state in ICI.
• Download: Click to download the agreement document.
• Upload Document: Click to upload the signed agreement document to the system.

Note: 

• For internal groups, only one common email is sent to all recipients/approvers. However, for external users, 2 different mails are sent. A unique email is sent to each external user, each containing a unique passcode and the URL for the approve/reject page.
• The page that opens on clicking the link in the email is displayed as per the localization settings for the user. In this example, it is displayed in English.
• Once the user takes any action on the page, the link becomes invalid and cannot be accessed again and the page displays an error.
   

Ability to update dates while uploading signed copy

Users now get the flexibility to update the effective and expiry dates while uploading the signed copy with manual signatures.
These fields, to be added through technical configuration, are displayed on the “Upload Signed Copy” and “Upload Fully Signed Copy” popups, where users can conveniently update the desired values. 

If the effective/expiry dates for an agreement have not been updated in the Draft or Approved states, they can be updated while uploading the signed copy using the “Upload Signed Copy” button.
This button is displayed for an agreement in “Waiting for Signature” state, on the agreement details page.
To update agreement dates while uploading the signed agreement document:

 
1. Click the “Upload Signed Copy” button. The “Upload Document” popup window is displayed.

Note: In case of uploading documents for an agreement in Executed state pending upload of the fully signed copy, click the “Upload Fully Signed Copy” button.

 

2. Select the “Effective Date” and “Expiry Date”. For example, April 22, 2021 and April 22, 2023 respectively.

Note:

The values are auto populated based on the Effective/Expiry Dates entered while creating the agreement. 

If no dates are selected, then by default, the current date is pre-selected as the effective date and the expiry date is set as blank. 

The expiry date should be a date greater than the effective date.

Any validations set for effective/expiry dates attributes at the agreement level are applicable here. For example, validation set for expiry date set more than 100 years after the effective date.

 
3. Click “Select File” to upload the signed agreement document. The rest of the workflow continues as usual. 
The effective/expiry dates get saved to the agreement and the updates can be viewed in the agreement History.

 

 

Note:
All limitations for the “Enable Expressions” attribute property will be applicable, in case the Enable Expression Result / Visibility / Validation is configured for the “Expiry Date” and “Effective Date” attributes.
The Enable Expression validation will perform validations for other attributes, even if they are not present on the Upload Signed Copy / Upload Fully Signed Copy popup window.

 

 

 

Related Topics: Agreement Management | Requests | Searching agreements and requests | Adding Supporting Documents to an Agreement | Sending an Agreement for Review and Approval | Notes | Creating an Agreement from a Contract Request | Bulk Actions | Sending agreements for approval during bulk creation