You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page:
Template used on this page:
Return to Working with Agreements.
The "Agreements" or Agreement index 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:
You navigate to this page from the "Home" page by clicking the "Agreements" tile > "Create" button.
On this page, you can do the following tasks:
You can create Agreements in ICI in the following ways:
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:
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.
Enter the following basic details of the Agreement in this section:
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.
File scanning during upload:
Note:
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.
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:
There is a preview functionality, 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.
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.
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 > Agreements> Create. 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.
You can create multiple agreements from a single agreement with the provision of copying associations and attributes as required.
Users now:
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.
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:
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 "Agreements" tile on the Home page. The "Agreements" page opens.
2. Click the "Create". The "Create Agreement" page opens.
3. Select the Contract Type Name. For example, Agreement CT with Arithmetic Computation CT.
4. Select Type Of Paper as Own.
8. Enter All Data in the Test Case Id field.
Let’s create a base agreement such as an MSA.
Let’s create an association of the base agreement as a peer such as a SOW.
1. Click Next. The Associations tab opens.
2. Click + Association.
3. Enter an Association Name. For example,ICISOWPeercreation.
The Associated Contract Type is automatically populated and Relation Type is Peer.
4. By default, all flags are set to No. You may set the flags to Yes as required. However, the following flags must be enabled:
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.
5. Click Save. The created association ICMSOWPeercreation will be displayed in the Association list on the left hand side.
6. Click Next. Enter the required details in the following tabs.
7. Verify all the details and click Create. The Contract Type Details page opens.
8. Click Send For Approval. The Configure page opens listing the created Contract Type - Automation MSA_PeerAssociationcreation in an Approved state.
9. Click the View Details icon next to this entity to view the contract type details.
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.
1. Click Next. The Associations tab opens.
2. Click+ Association.
3. Enter an Association Name. For example,ICIPeerCT_MSAassociation.
The Associated Contract Type is automatically populated andRelation Type isPeer.
4. By default, all flags are set to No. You may set the flags to Yes as required. However, the following flags must be enabled:
5. Click Create to create the peer contract type with MSA association.
The base agreement MSA can have multiple associations (SOWs), but the associations (SOWs) can have just 1 parent agreement.
1. Create MSA agreement and go to Details page.
2. 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, Assoc_LineItems.
The page will redirect the user to the new agreement creation wizard for Automation SOW_PeerAssociationCreation.
The contract type name will be auto-populated.
2. Select Own Type Of Paper from the drop-down.
3. On the Attributes page, attribute values from base agreement will get inherited into peer attributes.
4. Click Next on the following tabs.
5. Verify the details and click Create to create the agreement.
The peer agreement will get linked to the base agreement.
6. Click "View Details" 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:
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.
To view the contract manager role:
1. Click Admin 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.
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.
2. Click Next and then click Create to create the event rule.
You can view the contract manager added in the agreement team if the event rule is executed as expected.
Select the attribute from the drop-down on agreement index page to display the list of users with contract manager role.
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.
User roles can be provided while Provisioning users. For managing users, refer Managing Users
The user created above can create a User Group. For more information, refer Managing User Groups.
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 "Configure" > Rules > "Create". 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.
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.
This functionality has the following limitations:
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:
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 Fourth Approver 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 "Admin" > 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.
The access to the associated documents of the agreement can be controlled by role action mapping.
Only authorized users can:
To control access on the associations creation action from agreement details page through role-action mapping:
1. Click Admin > 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 on the left panel configuration will be disabled for all users other than Primary Owner.
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. Click "Admin" >User Groups> Role-Action Mappingon the Home page. The Role-Action Mapping page 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 Arithmetic Computation CT, only Primary Owner and Secondary 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 users with approver role.
You can add Static and Dynamic filters after configuring the filters on Masterdata records. For more information about Static and Dynamic filters configuration, refer Masterdata.
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:
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 Admin > 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.
Authorized users can restrict the access to extension attributes for specific users using Attributes Group Privileges.
To restrict the access:
1. Click Admin > 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.
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.
To edit the masterdata:
1. Click Configure > Contract Types on the Home page. The Contract Type index page opens.
2. Click View Details 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.
Attribute types such as conditional, lookup, computations (enable expressions), tracking, multi-select choice and so on can be configured to support extension attributes.
Users can make the attribute mandatory by setting the Is Required For Extension attribute field On in the contract type.
1. Click "Agreements"> on the "Home" page and then click "Create". The "Create Agreement" page opens..
2. Select the Contract Type Name. For example, Quotation.
4. Select the Type Of Paper.
15. Select the Contract Type from the drop-down list.
16. Select the attribute from the Available Attribute list.
17. Click the arrow icon to move the attribute to the Selected Attribute list.
18. Click Next. The View and Confirm tab opens.
All attributes and their Contract Types are displayed.
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 "Agreements" on the Home page and then click "Create". 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.
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.
Changes in extension attributes are captured and can be viewed on the History tab.
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.
All the entities with extension attribute Vehicle Type will be displayed.
The Activity Panel tile helps logged on users to track, create and resume workflow actions at the agreement, association and amendment levels.
1. Click the Admin > Application Settings on the Home page. The Application Settings page opens.
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 "Please Confirm" window opens.
3. Click "Yes". The "Add Note-Cancel" drawer opens. 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.
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 Details" icon next to the Agreement you wish to edit on the Agreements page. The Agreement Details page opens.
2. Click "Edit" from the three dots menu. The "Edit Agreement" page opens.
3. Follow the steps 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.
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.
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 "Configure" > 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.
Follow these steps to copy an Agreement:
1. Click the "Agreements"> on the Home page. The agreement index page opens.
2. Click "View Details" 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.
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.
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.
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.
To copy an agreement from agreement index page:
1. Click the "Agreements" 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.
5. 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.
Only users with manage privileges can copy the agreement record. The error message will be displayed if unauthorized users try to copy the agreement.
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.
1. Click Agreements on the "Home" page and then click "Create". The Create Agreement page opens.
1. Click Agreements on the Home page and then click "Create". 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.
1. Click Upload Document in the Owner’s instance. The Upload Document window opens.
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:
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 Configure > Contract Types on the Home page and then click "Create". The Create Contract Type page opens.
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.
1. Click the "Agreements" on the Home page and then click "Create". The Create Agreement page opens.
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.
4. Enter the message in the Message field.
5. Click Send.
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.
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
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.
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 :
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, refer Bulk Actions
ICI provides the ability to send the entity-wise reminder notifications by using the Subscription Reminder Notification Template.
To create a Subscription Reminder Notification Template, refer Create a Subscription
Creating an Event Rule for the Agreement Reminder Event
To create an Event Rule:
1. Click the Configure tile and then click "Rules". The "Rules" menu opens.
2. Click Create . The Create Rule page opens.
3. Select the Contract Type. For example, MSA_SD.
4. Enter a Rule Name. For example, Agreement Expiry Notification.
5. Enter a description for the Rule in the Rule Description field.
6. Select Event Rule from the Rule Type drop-down list.
7. Select Agreement Reminder from the Rule Type drop-down list.
8. Click Next. The Build tab opens.
9. Click Add Rule under the Build tab.
10. Select the Contract Type from the drop-down list for which you want to apply the condition. For example, MSA_SD.
11. Select the Attribute for which you want to apply the condition from the Select Value drop-down list. For example, Created By.
12. Select the operator from the drop-down list. For example, Equals.
13. Select the user for which you want to apply the condition from the Enter Value drop-down list. For example, CLM Admin.
14. Select the Action that you want to take from the Actions drop-down list. For example, Set Recurrence Reminder.
15. Select the template from the Reminder Template drop-down list. For example, Reminder Notification.
16. Enter the value in the Interval field. For example, 1.
17. Select the frequency from the Interval Frequency drop-down list. For example, Day(s).
18. Select the date in the Start Date drop-down list from where you want to start the reminder. For example, Reminder Start Time.
19. Select the date in the End Date drop-down list from where you want to end the reminder. For example, Reminder End Time.
20. Select Yes or No in the Stop Processing More Rules drop-down list.
21. 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.
22. Click Create.
The Agreement Expiry Notification rule gets created. This can be viewed on the Rules page.
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.
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:
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 refer Edit_a_Contract_Type
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.
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.
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 " Agreements" on the Home page. The agreements index page opens.
2. Click the View Details icon for the agreement for which you want to view the document versions. For example, MSA. The agreement Details page opens.
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:
Below is an example for allowing users to approve/reject an agreement from email:
1. Go to Home >Admin > 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:
Note:
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:
2. Select the “Effective Date” and “Expiry Date”.
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.
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.
Users can view the current status of an agreement on the "Agreement Index or Details" page, a generic progress view on the "Team" tab, and logged audit details on the "History" tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.
A horizontal chevron is displayed, which is a visual depiction of the agreement’s journey that provides a simple, upfront, and consolidated view of the agreement’s lifespan. The chain of compact dots and a square on the top right of the Agreement (or Amendment) details page, just below the title in the title bar, the chevron view prominently communicates an entity’s journey including the previous, current, and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.
The colors of the chevron are indicative of the stage of the agreement:
The chevron displays the following 4 dots corresponding to the various stages of the agreement’s journey:
1. Generate – Agreement (or Amendment) action statuses, as also displayed in the agreement History, up to “Publish”, such as “Draft”, “Modified”, “Cancel”, “Revert”, “Lock-Unlock” etc.
2. Approve – Agreement (or Amendment) action statuses, per Approval stages, such as “Pending” or “Completed” approvals from Deviation Approval, Agreement Approvals, etc. with step numbers.
3. Execute – Agreement (or Amendment) action statuses in the Signature lifecycle, such as “Waiting for Internal Signature” or “External Signature” up to “Executed”.
4. Manage – Agreement (or Amendment) actions reported in History post executed state, such as Reviewed, Terminated, Expired, Amended, Superseded, Archived etc.
On hovering over the chevron dots, a tooltip text is displayed to represent the current status of the agreement - “Agreement (or Amendment) is <State Name>, click here for more information”, where state name is the current state of the agreement or amendment. For example, for an agreement that is published and approved, it shows “Agreement is Approved, click here for more information”.
Note:
Clicking anywhere on the compact chevron view opens up the details and step-by-step history of the agreement lifecycle till that moment in an expanded view.
1. Generate: The following screenshot shows the status of an agreement in draft state:
2. Approve: Displays the following details:
Manage: Displays the following details:
Contract authoring is a team-based activity consisting of multiple subject matter experts and operations personae, often remote from each other. This release features a real-time, collaborative authoring environment, embedded into the Icertis UI where the contract artifacts are stored in ICI and respect all prevailing entitlements.
It is now possible for:
Note:
The Word online editing is available only for Agreements and Amendments in Draft, Waiting for Approval, Approved & Review Pending states.
To edit an agreement online:
1. Click "Agreements". The Agreement Index page opens.
5. Click "Sign in with a work or school account".
Multiple users can simultaneously edit and contribute in an online editing session of an agreement.
7. Users can copy the document’s online editing session link using the "Copy Editor Link" available on the top right share it with other users. The users with valid Office 365 subscriptions who are authorized to access the agreement can then edit the agreement online. If options are more the link is available under the more-actions three dots menu on the far right before the "Split View" icon.
8. Click "Check-In" on the top right. The drawer "Check In Edits from Office on the web" opens.
9. Type a note to enter details for future reference though this field is optional.
10. Click "Check In".
The confirmation window showing the document comparison opens.
11. Click "Compare Changes" to view the changes.
12. Click "Yes" on the confirmation drawer after comparing changes. The changes are saved and a new version of an agreement is created in the "Draft" state. For example, Version 3. The "Versions" page is displayed with the version details. You can click "Show Details" to view the details. Refer to the Versionspage for more details.
The audit for online editing session events is captured and displayed in the "History" Tab in the left navigation pane on the agreement Details page. Refer to the Historypage for more details.
Users get the emails and notifications for the online editing session which can be accessed from the "Notifications Dashboard". For example, Agreement Notification- Agreement Online Editor Session Start. The notifications contain the link to access the agreement record.
Refer Notifications Dashboard page for more details.
The online editing in ICI now covers the editing of Associated Documents along with the agreements in shared online sessions for a complete collaboration with various stakeholders encompassing the components of agreements.
The online editing for associated document is available for the MS Excel, PowerPoint and MS Word files (DOCX, XLSX and PPTX file extensions).
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in one of the groups: Users, User.
You can view and copy the source of this page:
Template used on this page:
Return to Working with Agreements.