From ICIHelp8.2
Jump to: navigation, search
Line 1: Line 1:
  
  
= ICM Release Notes - Release 7.11 =
 
  
== Overview of Release 7.11 ==
+
= ICM Release Notes - Release 7.12 =
  
The 7.11 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICM functionalities and the user interface.
+
== Overview of Release 7.12 ==
 +
 
 +
The 7.12 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICM functionalities and the user interface.
  
 
The key enhancements of this release include:
 
The key enhancements of this release include:
  
*'''Enhancements to Business Applications'''
 
**Integrating the ''ObligationAI'' and ''Obligation Management Application ''to track and manage obligations, fulfilments for a given agreement which helps in yielding contract compliance and reducing the risks involved in managing the contracts.
 
**Certifying that ICM is now able to support multiple business applications with reference to functionality, performance and security, to drive business compliance.
 
**Locking the ability to change the seeded rules that are essential for Obligation Management application flow.  
 
 
*'''Enhancements to the ICM Application'''  
 
*'''Enhancements to the ICM Application'''  
**Improving the user interface that allows the users to navigate in ICM with just one click. This will enhance the user experience considerably by reducing the time and effort to click through several pages to reach the destination page.
+
**Enhancing extended template attributes to make them searchable on the Template Index page, global search, advanced search and on the search in Icertis Experience for Word
**Enhancing the ICM dashboard to provide a framework for configuring a new dashboard layout, and providing support for widgets for all the Saved Search, Task List and My Recent activities. In addition, the support is also extended to use the earlier KPI based dashboard, resize the widget, and re-order the widget sequence.
+
**Enabling Download All button for expired agreements and amendments
**Introducing a Pre-Publish Checker tool on the User Administration tile that will analyze all the checkpoints which potentially result in downtime and provide failure information to the configurators, thus allowing users to take appropriate actions.
+
**Enhancing the functionality of Associations added as tables with localization of table headers 
**Enforcing boundaries for technical configurations and providing guidelines on the consumption of client-side hooks and server-side hooks, as well as the deployment and configuration of implemented customization.
+
**Providing localization support for clauses and templates to enable users to configure templates and create localized agreements 
**Allowing users to define the order for associations and assemble them as per the defined order.
+
**Providing administrators the ability to add global favorites to entity detail pages   
**Enhancing the Promote To Production (PToP) tool for Vulnerability and Penetration Testing (VAPT) fixes, testing open bugs in PToP engine, some new validations in the PToP engine, as well as new enhancements in the PToP engine and user interface to provide support to PToP and DevOps teams.
+
**Establishing the differentiation between Internal Reviewer and External Reviewer along with respective role-action mapping 
**Enabling users to predefine filters or apply them based on any other attribute values that the user keys in while referring value from any master records.
+
**Introducing a Click to Sign process, whereby signatories can directly preview and accept agreements
**Providing the flexibility to use attributes of masterdata as extensions to any agreement or associated document, which considerably improves usability and simplifies the process for users who deal with hundreds of items and need to have multiple configurations.
+
**Enhancing bulk creation of agreements with an option at configuration level to set the target workflow action for the agreements to be created  
**Simplifying the process of authoring by allowing the contract author to create multiple agreements from a single agreement with the provision of copying associations and attributes as required.
+
**Provisioning users to preview Approvers when swapping primary clauses for alternate clauses
**Introducing the capability to define a sub-role for the approver role and enabling all the capabilities of the approval process based on the sub-role.
+
**Introducing online editing support for agreement documents to greatly improve operational efficiency for contract owners
**Allowing filtering out agreements while inheriting.
+
**Enhancing commitments functionality with an option to send reminders
**Providing the ability to exclude attributes or associated documents when copying agreements and allowing the copying of commitments when copying the RFQ/Agreement.
+
**Enhancing user experience by grouping buttons on all entities' index pages, among other major functionalities
**Provisioning users to define their currency preferences.
+
**Providing the flexibility to control users' actions on agreements based on their roles
**Providing the capability to retain the original file name for any entity when uploading it, making it easier for users to identify and manage them.
+
**Enhancing the agreement index page with a button which allows copying an existing agreement to create a similar agreement  
**Allowing copy team role mapping by copying team from the contract request, agreement or amendment to its association capturing the rule condition based on which a user has been added to the team.
+
**Enhancing metadata of clauses with the ability to add details which can be leveraged in searches and defining rules
**Providing Administrators the ability to pin the necessary saved searches for external user or suppliers.
+
**Extending the functionality to copy team roles for peer associations of contract requests /agreements/amendments
**Enhancing the document comparison capability to view and download the redlined document of the selected agreement versions.
+
**Providing users the option to clone commitments from existing ones
**Extending support of multiple rulesets for event rules, for any entity, per event.
+
**Enhancing Excel data upload functionality with validations on choice value attributes
**Allowing swapping of the primary clause with its alternate clause, and enabling users to clearly identify the first version of an agreement in the Clause Comparison Report.
+
**Extending bulk download/upload functionality to associated documents enabling users to create line items with extended attributes or associated document attributes
**Alerting users about the modifications identified in the association files assembled in the document.
+
**Providing the flexibility for users to create line items using extended or associated document attributes
**Enhancing KPI Reports’ performance, and deprecating the CLM Activity and Cycle Time reports.    
+
**Providing users the flexibility to specify attributes for bid analysis per RFx Item and to enter value for bid analysis attributes per supplier item bid
 +
**Ability to have flexible contract type extension
 +
**Enhancing user experience by allowing resizing of popup windows
 +
**Supporting the trigger of rules in case of attributes which have been localized
 +
**Extending the number of records that can be added while adding a table as an association
 +
**Introducing the ability to uniquely identify records related to RFQs
 +
**Introducing flexibility in defining roles other than default roles provided in ICM
 +
**Providing support for auto-attachment functionality for agreements, amendments and contract requests
 +
**Enhancing associations with the ability to explicitly define the type of relationship between the association and agreement/amendment as parent, child or peer
 +
**Enhancing the functionality of copying associations with the flexibility to exclude attachments
 +
**Introducing a virus scan option for files uploaded into ICM<br/> &nbsp;    
 
*'''Enhancements to ICM API 2.0'''  
 
*'''Enhancements to ICM API 2.0'''  
**Introducing a new version of the Icertis APIs that will allow business applications to interact with ICM using standard API nomenclature for agreement and associated entities.    
+
**Introducing some new APIs that will allow business applications to interact with ICM using standard API nomenclature for amendments, contract requests and searches    
 +
 
 
*'''Enhancements to ICM Add-ins'''  
 
*'''Enhancements to ICM Add-ins'''  
**Allowing users to stay on the document for further edits or reviews while publishing occurs in the background.   
+
**Allowing users to stay on the document for further edits or reviews while publishing occurs in the background.  
 +
**Enhancing the Word Add-in to display deviated clauses within the plugin
 +
**Introducing WordAI to enhance user experience by merging NegotiateAI and Icertis Experience for Word (previously known as Scribe)
 +
**Updating the logo for ICM Word Add-in
 +
**Providing users the ability to take workflow actions such as approve, reject, send for approval and others using Icertis Experience for Word<br/> &nbsp;    
 
*'''Enhancements to Artificial Intelligence Applications'''  
 
*'''Enhancements to Artificial Intelligence Applications'''  
**Introducing eDiscovery to derive critical insights by analyzing legacy contracts.
+
**Establishing a contract lineage using AI so that users can visualize the changes done in the clauses, attributes, team members, statuses, versions, obligations and associations over the contract negotiation process or due to various amendments and addendums added subsequently
**Introducing RiskAI based on automatic extraction of clauses and attributes through the in-built discovery model. The model has been extended to discover IT services industry specific attributes and clauses.
+
**Introducing a parallel view of discovered attributes against the original document<br/> Enhancing the in-built discovery model to discover attributes from Statement of Work agreements
**Improved accuracy of AI models by incorporating user action feedback when the user is interacting with the attribute discovery in DiscoverAI and NegotiateAI apps.
+
**Enhancing the discovery performance to reduce time required for discovery of documents
**Identifying important terms in contracts (contract highlights) using AI for different personas like legal, CxOs, finance, etc.
+
**Enhancing natural language search query with support for user created attributes    
**Extending the discovery support to URL datatype attributes; supporting multi-choice attributes and multi-choice lookup datatypes on the Attributes Discovery page, in both - DiscoverAI''and NegotiateAI apps.''
+
 
**Introducing NLP-based search query for agreement entities.    
+
 
*'''Enhancements to Reports'''  
 
*'''Enhancements to Reports'''  
**Introducing the Obligations Management Reports on the Reports tile in ICM. These out-of-the box reports include the Obligations Dashboard Report that provides information of the Fulfilments due in the next 30 days, Fulfilments overdue by the owner, and the OMH – Obligation Management Health Report that provides an overall view of fulfillment compliance.    
+
**Configuring core SSRS and Power BI reports to include contract types classified as Contracting&nbsp;
 +
**Introducing additional support for associated documents enabling users to create custom reports in Power BI<br/> &nbsp;    
 
*'''Improving the Icertis Experience '''  
 
*'''Improving the Icertis Experience '''  
**Building the Secure File Transfer Protocol (SFTP) adapter as an automated solution to load masterdata once extracted from source of truth via SFTP which facilitates file access, file transfer and file management over a Secure Shell (SSH) data stream.&nbsp;
+
**Providing configurators the ability to redirect emails to specific addresses when testing Adobe electronic signature on non-production instances
**Building the Azure Service Bus (ASB) adapter, which is an automated solution to load and update master as well as transaction data once extracted from the source of truth via ASB using JSON payloads.
+
**Introducing the new eSignature platform experience
**Integrating with DNCM’s (Daimler) enterprise Identity Provider (IdP) called GAS (Daimler Global Authentication System) via Open ID Connect protocol to provision the sub-roles or create new approver sub-roles.
+
**Enabling Electronic seal tag for signing agreement documents
**Allowing Salesforce users to take actions such as - Download, Assemble Contract and Send for Approval directly from the Action column of the contract index page grid, without opening the agreement record.
+
**Supporting creation of ICM entities and contracts using SAP S/4 HANA as well as supplier masterdata integration and masterdata lookup using S/4 HANA
**Enhancing the SFDC experience by providing users the ability to search for contracts or contract requests from a common page depending on the selection criteria.
+
**Enhancing generic integration framework to support contract requests, associations, amendments
**Providing the Reports tile within Salesforce so that users can view and execute custom and default reports, thus simplifying tasks and improving productivity.
+
**Enhancing Salesforce experience by providing users the ability to take request review and upload document actions from within the Salesforce grid&nbsp;
**Improving the ICM Experience for MS Dynamics interface, thus providing a seamless user experience across various form factors, simplifying the user administration experience, increasing the deal velocity and reducing the deal cycle time.    
+
**Providing users the flexibility to manage ICM tasks from within Salesforce  
 +
**Providing Salesforce users the ability to configure auto creation of contracts    
 +
 
 
*'''Introducing ICM Platform Tools'''  
 
*'''Introducing ICM Platform Tools'''  
**Introducing the Configuration Key tool so that a logged in user (who has access to Azure subscription) can search and update configuration keys as required reducing the dependency on the Engineering and DevOps teams.
+
**Enhancing ICM support for the PToP tool to promote ICM configurations or modifications that are made to ICM configurations in pre-production environments to production environments
**Releasing a Translations Editor tool that contains all strings that are localized so that users can now download all keys and their localization values as an Excel file, modify multiple values and upload the modified changes to ICM.
+
**Providing support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups
**Enhancing the ICM Health Check page to cover additional parameters that help identify potential outages and diagnose issues, and provide information on the performance of the ICM instance, its overall health, as well as its usefulness to users.
+
**Providing support for elastic search sync<br/> &nbsp;    
**Improving the Search Sync capability so that users can now check the value stored in Elastic Search for a specified key using the key name, thus eliminating the need to sync the SysId several times to verify if it is the latest one.    
+
  
 
These release notes provide an overview of the enhancements to ICM and the ICM experience for integrations. Refer to the technical requirements and known issues for the release in this document. Refer to the detailed Wiki documentation for the explanation and capabilities of these and all other ICM features and functionalities.
 
These release notes provide an overview of the enhancements to ICM and the ICM experience for integrations. Refer to the technical requirements and known issues for the release in this document. Refer to the detailed Wiki documentation for the explanation and capabilities of these and all other ICM features and functionalities.
Line 66: Line 79:
 
&nbsp;
 
&nbsp;
  
 +
== ICM Application Enhancements ==
  
== Icertis Business Applications ==
+
'''<span style="color:#008000;">625385 – Global Search</span>'''
  
'''<span style="color:#008000;">448830&nbsp;– Integrating ObligationAI with Obligation Management app&nbsp;</span>'''
+
The previous search functionality in ICM required users to traverse through multiple pages of the search results, to locate the record they were searching for. The results were displayed in no particular order. Traversing through pages of records was an inconvenient and time-consuming process for users, especially in case of hundreds of matching result records.<br/> Now, the ICM search functionality has been entirely revamped to provide a better, more user-friendly experience. Users can now view relevant records on the very first page of the results.<br/> With this release:<br/> Search results are displayed in order of relevance to the entered search query, with the best match(es) appearing as the top-most or most relevant search result(s).<br/> On the search details page through the Advanced Search button, the search mode radio button selected by default is Metadata. In case of Global Search, the default search mode is Combined, that is, search will be performed on both Metadata as well as Full Text. The default view here is the extended view.<br/> Document text which matches the search query is highlighted.<br/> The search drop-down displays top 5 relevant search results. A View All Results link is displayed, clicking which opens the results details page.<br/> Hovering over the results in the drop-down displays details about the entity&nbsp;<br/> Additional matching results are displayed below each result.<br/> Note: The global attributes display name begin with AppSrc, so that they can be easily searched and identified.<br/> &nbsp;
  
Discovering obligations is the critical step to start Obligation Management lifecycle. As there are hundreds of obligations in an agreement, manually having to discover, triage, and create Obligations is an exhaustive process.
+
<span style="color:#008000;">'''551111 – Grouping of actions on index page'''</span>
  
With this release, users can now track and manage Obligations for a given agreement using Obligation AI and Obligation Management (OM) for a seamless experience. The interconnected flow of AI with OM is aiming to solve the Legal persona’s job to triage, discover, and create obligations. With this feature, ICM provides a cohesive experience for setting up obligations. This helps in yielding contract compliance and reducing the risks involved in managing contracts which primarily leads to:
+
Earlier, the applicable set of actions available for any entity were represented using icons across ICM. For example, the agreement index page had icons for View Agreement, Preview Document and View Smart Link actions. As part of our efforts to continuously improve ICM, multiple new actions are added for an entity over time. Hence, actions are now grouped together to improve the usability and user experience. &nbsp;
  
*Reducing time and efforts to discover and create obligations.  
+
<br/>  <br/> <span style="color:#008000;">'''586165 – Support for online editing of agreements'''</span><br/> As part of contract management, agreement and amendment documents regularly go through reviews where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature. To make changes or modifications to an agreement, ICM users previously had to download a copy, perform edits and upload it back to ICM. This created a version of the document in ICM.&nbsp;<br/> Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but also audit information was often lost, it was not possible to trace what was approved and by whom.<br/> With this release, ICM offers online editing support for agreement documents creating radical operational efficiency for contract owners.&nbsp;<br/> It is now possible for:<br/> •&nbsp;&nbsp; &nbsp;Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session where more than one party can edit parallelly using existing MS Word capabilities.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;An agreement document, which has been edited using online editing, to be published to ICM without any loss of information.<br/> Note: Only users with edit privileges on a document can participate in editing it online.
*Using ICM’s human in loop model of consuming AI such that relevance of discovery becomes better over the time.  
+
*Scaling out the job of obligation discovery such that newer/junior members can effectively perform Obligation Management.  
+
  
The default configuration is Obligation AI and Obligation Management as a combined one, and you can also configure them individually as Obligation AI, or Obligation Management. The image describes the typical workflow of Obligation Management covering all phases of OM lifecycle. The red box in the image illustrates the cohesive experience of triaging and creating Obligations.
+
&nbsp;
<div class="image-green-border">[[File:7.11 Release Notes 01.png|720px|7.11 Release Notes 01.png]]</div> <div class="image-green-border">&nbsp;</div>
+
'''<span style="color:#008000;">508359&nbsp;– Multi-app testing (Sourcing, Obligation Management) configured and running in the same environment</span>'''
+
  
With the introduction of business applications - Sourcing, AI, Obligation Management earlier, there was a demand for supporting these apps with ICM from both - existing and new customers. ICM has thus made platform changes such that the build, deploy, and run time execution systems have been rehauled such that, multiple applications can now co-exist on any given ICM instance.
+
<span style="color:#008000;">'''550178 – Enabling search for extended template metadata'''</span><br/> Earlier in ICM, there were only predefined metadata for templates such as Name, Clause Code, Clause Group, and so on. To fulfill the requirements of some organizations, ICM provided the capability of extended template attributes to define additional custom metadata/attributes at the template level. However, users were not able to search templates based on these extended template attributes.<br/> Now, users can search and retrieve required templates using these extended attributes as search parameters in the global search, advanced search and the template index page.
  
With this release, we are certifying that ICM is able to support multiple business applications with reference to functionality, performance and security, to drive business compliance.
+
&nbsp;
<div class="note-box">'''Note''': ICM will now support platform and business applications with same version number.&nbsp;For example, if you are on ICM 7.9 core and want to consume the ICM 7.11 offerings of Sourcing and Obligation Management business applications, then you are requested to update core to 7.11 before installing the applications.</div>
+
<br/> '''<span style="color:#008000;">545763 – Non-editable seeded business rules</span>'''
+
  
Previously, business rules were seeded as part of the Obligation Management app to ensure its smooth functioning. Making business rules editable by other users could result in workflow errors.
+
<span style="color:#008000;">'''572767 – Ability to download all associated documents of expired agreements and amendments'''</span><br/> Earlier in ICM, users could download all the associated documents of an agreement or amendment for all other states but not when the agreement was in the Expired state.&nbsp;<br/> This capability is now also provided for expired agreements and amendments. This considerably improves usability as users no longer need to navigate to the respective Association tab to download the required documents one by one. The Administrator can now define access permissions so that the Download All button is available for authorized users allowing them to easily download all the associated documents of agreements and amendments for reference.&nbsp;
  
With this release, these business rules that are critical to the flow of the application are now locked by the service users when deploying the Obligation Management application. This prevents other users to unlock, edit and modify these rules, thus ensuring a smooth workflow.&nbsp;Refer to the 7.11 Wiki for the list of seeded rules.
+
<br/>  <br/> <span style="color:#008000;">'''569901 – Ability to resize popup windows'''</span><br/> Previously, popup windows within ICM had a fixed size.<br/> Now, support has been provided for users to be able to resize the windows, thereby enhancing their ICM experience manifold. This helps users to easily read information on Lookup, Team Grid and Create Association windows.
<div class="note-box">'''Note''': Even if the rulesets are locked, you can create new rulesets for event rules.</div>  
+
&nbsp;
+
<div class="image-green-border">&nbsp;[[File:7.11 Release Notes 04.png|720px|7.11 Release Notes 04.png]]</div>  
+
&nbsp;
+
  
 
&nbsp;
 
&nbsp;
  
 +
<span style="color:#008000;">'''551117 – Associated document content including table headers in the preferred language'''</span><br/> Earlier in ICM, if the language preference was English and the user created an agreement using a German language template that had an association as a table, then the buyer could create the association instance and assemble the contract. However, the language for the entire assembled document would be German, but the association table header (title) would be in English.&nbsp;<br/> This functionality has been improved so that the table header also appears in the same language as the remaining text in the template. In the example above, the entire assembled document as well as the association table header would be in German.
  
== ICM Application Enhancements ==
+
<br/> <span style="color:#008000;">'''571054 Ability to add global favorites to entity details page'''</span><br/> ICM Administrators can already set default favorites so that specific users can access relevant information targeted for them using global favorites. These global favorites are added to the Index page of the selected entity. With this release, this functionality is further enhanced such that the Administrators can now choose to add global favorites to the Entity Details page.&nbsp;<br/> They can set different default favorites for different entities for their users. For example, a pinned favorite search for line items can have different relevance as compared to a pinned favorite search for bids. Having default favorites pinned makes it easy for users to easily identify the actions that they need to take. Having pinned default favorite saved searches at entity level also helps the users access relevant information from within an entity, rather than at the Index page (outside the entity).<br/> Administrators can now:<br/> &nbsp;&nbsp; &nbsp;Choose to add global favorites to Entity Details page for specific users to view them in the associated parent or peer entity's Details page.<br/> •&nbsp;&nbsp; &nbsp;Have global favorites added by default to the corresponding selected entity's Index page.<br/> Note:&nbsp;<br/> •&nbsp;&nbsp; &nbsp;The global favorites will always be appended to the last for a user per entity type.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;A maximum of 4 global favorites are displayed to the user based on the security groups permissions.<br/> •&nbsp;&nbsp; &nbsp;As a user, if 4 favorites for an entity already exist, then the global favorite is added at the bottom of the saved search drop-down.
 
+
'''<span style="color:#008000;">532684 Navigation Enhancements</span>'''
+
 
+
Earlier, the ICM user interface was tile-based. Each time a user had to navigate from one page to another, it required multiple clicks or going back to the Dashboard page when using level1 functionalities.
+
 
+
With this release, the ICM user interface has been considerably improved so that the user can navigate between pages (from any sub menu to any other menu item) by just one-click. This significantly enhances the user experience as it reduces the number of clicks, improves usability in navigation in addition to decreasing the load times, as it reduces round trips to the server.
+
 
+
'''Note:'''
+
 
+
*Users can now navigate from any page in ICM to any other page, thus eliminating the need for multiple page loads.
+
*No training is required for user adoption as it maintains the same classic tile menu.  
+
*All color/theme preferences can be applied.
+
*Works on tablets on tap which requires handling and QA.
+
*Supported on all standard ICM supported browsers, resolution and devices.
+
*All user permission and access privileges continue to be supported.
+
*The entire menu is configurable. Adding or removing any menu or sub-menu option can be done through database configurations, thus reducing code level customizations.
+
<div class="image-green-border">[[File:7.11 Release Notes 05.png|720px|7.11 Release Notes 05.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.11 Release Notes 06.png|720px|7.11 Release Notes 06.png]]</div> <div class="image-green-border">&nbsp;</div>
+
'''<span style="color:#008000;">546019 – ICM Dashboard Enhancements</span>'''
+
 
+
The existing ICM dashboard is tile-based and displays only numerical data. A new layout has now been designed which allows users to switch to a widget-based dashboard layout in view of providing a comprehensive look of business information on the ''Home'' page. This has improved the user experience and usability especially around complex navigation and performing multiple clicks to achieve a seemingly simple task. Users are now able to view recent activities, saved search, notifications upfront on the dashboard, in addition to their list of tasks and KPIs/reports.
+
<div class="image-green-border">[[File:7.11 Release Notes 07.png|720px|7.11 Release Notes 07.png]]</div>  
+
The widget-based dashboard offers the following widgets:
+
 
+
*'''Performance Metric:''' displays all the KPIs to which the user has access. These include Saved Search KPIs and Report KPIs.
+
*'''My Tasks:''' displays a list of tasks assigned to the user. The total number of tasks is displayed at the top of the widget, followed by the task link and the date on which each task was received.
+
*'''Notification:''' displays the notifications in the descending order of the date and time in which they have been received. Clicking the notification navigates the user to the ''Notifications'' page.
+
*'''My Recent Activities:''' displays a list of the latest activities performed by the user on agreements, contract requests and clauses. The activities are displayed in the descending order (latest first, oldest last).
+
*'''Saved Search:''' displays the searches saved on the ''Search'' page.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">519472 – Introducing the Pre-Publish Checker Tool</span>'''&nbsp;
+
<span style="color:#008000;">'''572768 – Display internal and external reviewer roles based on user type'''</span><br/> The Request Review functionality in ICM allows users to request their agreements to be reviewed. Before sending an agreement for approval or signature, the contract author can leverage the Request Review option and add a user or user group as reviewer.&nbsp;<br/> Previously, if the selected reviewer is an internal user, or a user group of internal users exclusively, then the team role/user role was depicted as External Reviewer in the Team and the History tabs respectively, on the agreement Details page. &nbsp;&nbsp;<br/> With this release:&nbsp;<br/> •&nbsp;&nbsp; &nbsp;An internal user added as a reviewer will be displayed as internal reviewer.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;An external user added as a reviewer will continue to be displayed as external reviewer.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Administrators will be able to define actions and action display names for different entities and states for internal and external reviewer roles, respectively.&nbsp;<br/> Note: This change does not apply to Send For Review functionality as that review happens only after an agreement is executed and is applicable only for internal users.
 
+
In ICM, when a contract type is published, agreements are created that move from the ''Draft'' state to the ''Approved'' state and finally to the ''Published'' state. The ''IsPublished'' flag indicates the state of the contract type. Publishing the entity is a complex process and ICM remains unavailable for use during this time. Hence, downtime is required for any publishing activity. Several times the publishing process itself fails resulting in extended downtime causing delays in configurations in addition to the loss of productivity.
+
 
+
ICM has now introduced a Pre-Publish Checker tool within the publishing process that will analyze the configuration status of contract types, APIs and running services along with infra sizing. The tool guides configurators whether publishing must be initiated or not, by listing the checkpoints regarding the failure information, instead of downtime about the corrections needed. This allows users to take appropriate actions when Publish is not possible.
+
 
+
The Pre-Publish tool performs basic checks for publishing contract types. The checklist includes a comprehensive list of 20 checks which may cause publish process to fail. This Pre-Publish check will help reduce instance downtime due to Publish related errors.
+
 
+
Administrators can now:
+
  
*View the pre-publish checklist items in case of failures.
 
*View the checklist items status and its corresponding evaluations on why publish must not be continued.
 
*View database information - SLO (Service Level Objectives) of database.
 
<div class="note-box">'''Note''': If no errors are identified, publish process continues normally.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.11 Release Notes 08.png|720px|7.11 Release Notes 08.png]]</div>
 
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">541970 &nbsp;Assembly of associated documents into the main agreement based on a defined order</span>'''
+
<span style="color:#008000;">'''551122 Localization support for clauses and templates'''</span><br/> Previously in ICM, there was no provision to have localization of clauses that could be used to create agreements in different languages. Hence, the users had to create multiple templates to be able to create agreements in different languages.<br/> With this release, users can store the localized version of clauses and enable them when authoring and executing agreements. So, users can configure the template that can be used to create a localized agreement. This considerably reduces the efforts of creating and managing multiple templates to support different languages.
  
ICM now enables users to define the format for assembly of associations tagged as a Table or File in the main agreement using saved search.
 
<div class="image-green-border">[[File:7.11 Release Notes 09.png|720px|7.11 Release Notes 09.png]]</div>
 
Users can create saved search of the desired association, using the capabilities of Search to Filter, Order, and Select the columns and their sequence, to be rendered in the final output. This saved search can be used along with the tagged association to assemble associations as desired using ICM Experience for Word.
 
<div class="image-green-border">[[File:7.11 Release Notes 10.png|720px|7.11 Release Notes 10.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">'''Note:''' If saved search is not configured or not tagged along with the association, ICM behaves as-is.</div>
 
 
&nbsp;
 
&nbsp;
<div class="image-green-border">[[File:7.11 Release Notes 11.png|720px|7.11 Release Notes 11.png]]</div> <div class="image-green-border">&nbsp;</div>
 
'''<span style="color:#008000;">476165 – PToP tool enhancements</span>'''
 
  
The beta version of the Promote To Production (PToP) tool was enabled in release 7.10. This functionality, provided to administrators, could promote ICM configurations/modifications that were made to ICM configurations in pre-production environments to production environments.
+
<span style="color:#008000;">'''568718 – Additional Click to Sign signature option available for agreements'''</span><br/> ICM already supports electronic and manual signatures. With this release, a Click to Sign signature process is being introduced where the signatory can preview the agreement and indicate acceptance to the terms in the agreement. &nbsp;<br/> If the signatory accepts the terms and conditions by checking the box in the Preview window, it is used to mark the agreement as accepted and signed by the signatory. The signatory also has the usual option to reject the agreement for signing, with the agreement going back to the Draft state.&nbsp;<br/> ICM Administrators who are authorized to create contract types can now add Click to Sign as an option in the signature type attribute. This would make this signature flow available for contracts of that type.&nbsp;
 
+
With this release, the following enhancements have been made for:
+
 
+
*Vulnerability and Penetration Testing (VAPT) fixes.
+
*Testing open bugs in PToP engine.  
+
*Some new validations in the PToP engine.  
+
*Better user interface to provide support to PToP and DevOps teams.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">541976 – Ability to configure and apply multiple filters while referring value from master records</span>'''
+
<span style="color:#008000;">'''574611 – Ability to swap alternate clause from Clause Comparison Report and view approvers'''</span><br/> Previously in ICM, the substitute language of a clause was stored as an Alternate Clause to the Primary Clause. Contract authors had the provision to replace any Alternate Clause using the Clause Comparison Report. Whenever such clauses are replaced by alternate clauses, a certain set of approvers get triggered for the agreement.&nbsp;<br/> With this release, contract authors are being provided with the capability to preview the list of approvers that will be triggered due to the clause swap.&nbsp;<br/> Similarly, whenever new version of an agreement is created, the Content Control window which is now displayed now has a provision to preview the approvers that will be added or removed based on the changes made to the clause.
  
Earlier, ICM provided the capability of filtering records on the basis of a single attribute using cascading.
+
<br/> <span style="color:#008000;">'''<br/> 568773 – Ability to create and send agreements for approval during bulk creation&nbsp;'''</span><br/> ICM allows contract authors to create multiple agreements from a single agreement with the provision of copying associations and attributes as required. Previously, these agreements created in bulk would be in Draft status. In order to send the bulk created agreements for approval, users had to either do it individually for each agreement or they had to configure a Saved Search and take a bulk action on it.<br/> With this release, this feature has been enhanced with an option at configuration level to define if these agreements are to be published, or created and sent for approval as part of the creation process.&nbsp;<br/> A choice-type attribute Target Workflow Action has been added in the existing bulk configuration masterdata contract type. Administrators can now specify whether bulk created agreements should be sent for approval or not. When the Target Workflow Action attribute is set to Create and Send for Approval and bulk agreements are generated on the model agreement:&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Approvers get added to the agreement’s team based on the rules configured.<br/> •&nbsp;&nbsp; &nbsp;Agreements will be sent for approval to the approver(s), and the agreement status will be updated to Waiting for Approval.<br/> •&nbsp;&nbsp; &nbsp;If no approver is present in the agreement’s team, the agreement will be approved directly and its status will be updated as Approved.<br/> By default, the agreements would be created in Draft status. Amendments can also be sent for bulk approval using the same functionality.<br/> Users can also decide whether the templates for bulk created agreements would be different or same than model agreement during bulk creation process. A flag Enable Template ReEvaluation is added in existing bulk configuration masterdata contract type.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;When Enable Template ReEvaluation flag is set to Yes, the Template Selection rules will be re-evaluated, and the first template from the list will be used for creating bulk agreements. The Template can be same or different than model agreement depending on the configured rules.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;When the Enable Template ReEvaluation flag is set to No, the template used for bulk created and model agreements will be same.<br/> Any Template selection rule configured for bulk creation will not be evaluated if Enable Template ReEvaluation value is No.
  
The capability has been further enhanced so that users can now apply multiple filters while referencing values from any master records. This provides users the flexibility to predefine filters or apply them based on any other attribute values that the user keys in.
+
<span style="color:#008000;">'''550187 – Provision to send reminder notifications for commitments'''</span><br/> ICM has the provision to track the milestones in an agreement with the Commitment functionality. Initially, to ensure that these commitments are fulfilled in timely manner, automated reminders were sent. Now, users also have the capability to send reminders at any time using the Send Reminder option and customize the notification as well as trigger reminder notifications in bulk.&nbsp;
  
Users can now:
+
<br/> <br/> <span style="color:#008000;">'''572677 – Flexibility to control the agreement actions based on role of the user'''</span><br/> ICM already allows controlling workflow actions for a user through role action mapping.&nbsp;<br/> ICM has extended support for other agreement actions that can also be controlled based on the user role, thus improving the overall access control for a user.&nbsp;<br/> Users can now control:<br/> &nbsp;&nbsp; &nbsp;Actions such as Compare Documents, Compare Clause Changes and Broadcast available to a user for an agreement.<br/> •&nbsp;&nbsp; &nbsp;Visibility of reports available in the agreement.<br/> •&nbsp;&nbsp; &nbsp;Creation and disassociation of associated documents from an agreement.<br/> •&nbsp;&nbsp; &nbsp;Linking and disassociation of peer association from an agreement.
 
+
*Define UI based configuration for multiple static and dynamic filters for the referred masterdata.
+
*Filter masterdata records directly in the drop-downs as well as the popup, based on the predefined configured static filters, while working with agreements/amendments.
+
*Filter masterdata records directly in the drop-downs as well as the popup, based on the predefined dynamic filters as the user keys in the values for the selected attributes marked as filters, while working with agreements/amendments.
+
<div class="image-green-border">[[File:7.11 Release Notes 12.png|720px|7.11 Release Notes 12.png]]</div> <div class="image-green-border">&nbsp;</div>  
+
'''<span style="color:#008000;">541980 – Ability to have flexible contract type extensions</span>'''
+
 
+
Previously, for any agreement or associated document, attributes were fixed and defined during the contract type configuration. However, users often have the requirement to define or select the attributes when they are creating the agreement or an associated document instance.
+
 
+
For line items, the attributes are required to be defined based on type of line item. For example, the attributes for “wheel” and “pen refills” are different. These can be defined by the users at the time of line items creation.
+
 
+
With this release, ICM provides the flexibility to use attributes of masterdata as extensions to any agreement or associated document. These extended attributes can be selected and added when user is actually creating the instance. This considerably improves usability and simplifies the process for users who deal hundreds of items and need to have multiple configurations.
+
 
+
Users now:
+
 
+
*Can create rules to attach masterdata attributes (single or multiple) to your associated documents and agreements based on certain conditions.
+
*Have flexibility to select (add or remove) and use any masterdata attributes as extensions at the time of agreements/associated documents creation.<br/> &nbsp;  
+
 
+
'''<span style="color:#008000;">541975 – Ability to create multiple agreements from a single agreement</span>'''
+
 
+
With this release, ICM has improved usability and considerably simplified the process of authoring, allowing the contract author to 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. &nbsp;  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">541982 – Ability to support approver sub-roles</span>'''
+
<span style="color:#008000;">'''572781 – Ability to copy existing agreement from the agreement index page'''</span><br/> Previously, ICM supported the copy existing agreement functionality from the agreement Details page. Now, the same functionality has been added on the agreement index page for better usability. With this, the user can perform the copy action without having to navigate into the individual agreement details page.<br/> Authorized users can now click an icon on the agreement index page to copy it to create a similar agreement. Along with the agreement, users now also have the ability to select any associated documents (parent-child or peer associations), commitments or obligations to be copied; where the Allow Copy with Association flag is set to True at the contract type level. If the association flag is set to False, a validation is displayed.
 
+
With this release, ICM is providing 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 type of approvers for an agreement based on functions such as Legal Approver, Finance Approver, and so on.&nbsp;
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">541979 Ability to filter agreements available for inheritance</span>'''
+
<span style="color:#008000;">'''551116 Support for extended clause metadata'''</span><br/> Previously, users were not able to add more details to a clause. With this release, an entity for clause extension is being introduced which could help users in various ways, such as, when defining rules and searches.<br/> Users can now:<br/> &nbsp;&nbsp; &nbsp;Create contract types with defining attributes from masterdata, similar to the template/user extended entity.<br/> •&nbsp;&nbsp; &nbsp;View the clauses extended entity attributes in the clause creation wizard.<br/> &nbsp;&nbsp; &nbsp;Configure rules using these attributes.<br/> •&nbsp;&nbsp; &nbsp;Enter the values for clause extended attributes using Add-ins.
 
+
With this release, ICM provides the capability to configure multiple mandatory and non-mandatory filters at contract type level for inheritance by which agreements can be filtered. This improves usability and reduces the overall effort, making it easier to find the desired agreement.
+
<div class="image-green-border">[[File:7.11 Release Notes 13.png|720px|7.11 Release Notes 13.png]]</div>  
+
&nbsp;
+
 
+
'''<span style="color:#008000;">549081 – Availability of contract type description during contract type instance creation</span>'''
+
 
+
ICM has now included the ''Contract Type Description ''field when creating agreements, amendments, associated documents, masterdata or contract requests. This facilitates users to select the desired contract type.&nbsp;&nbsp;
+
<div class="image-green-border">[[File:7.11 Release Notes 14.png|720px|7.11 Release Notes 14.png]]</div> <div class="image-green-border">&nbsp;</div>  
+
'''<span style="color:#008000;">551098/551099/551100 – Enhancements when copying agreements</span>'''
+
  
ICM has improved the usability when copying agreements by allowing the users to:
+
<br/>  <br/> <span style="color:#008000;">'''569900 – Ability to cascade team from contract request, agreement, amendment to its association'''</span><br/> Previously, ICM provided support to copy team role from contract request, agreement and its amendment to its parent child association. With this release, the support is being extended to copy team role from contract request, agreement or amendment to its peer associations.<br/> A tile has been added under the configuration, where an authorized user can map all such team roles for a defined contract type to its parent-child as well as peer associations.<br/> Administrators can now:<br/> •&nbsp;&nbsp; &nbsp;Provide the capability to copy the entire or selective team of the entity (contract request, agreement or amendment) to its peer association.<br/> •&nbsp;&nbsp; &nbsp;Copy all or selective team of the entity to its peer association on a parent or peer entity event.<br/> Users can now:<br/> •&nbsp;&nbsp; &nbsp;Sync/update the team of association when any team is added or removed from a contract request, agreement or amendment entity.<br/> •&nbsp;&nbsp; &nbsp;Capture audit logs while copying the team from the contract request, agreement or amendment entity to its peer association.
  
*Exclude associated documents from getting copied.
 
*Exclude the attributes of selected associated documents.
 
*Select and copy Commitments.&nbsp;
 
*Exclude the attributes of selected Commitments.
 
<div class="image-green-border">[[File:7.11 Release Notes 15.png|720px|7.11 Release Notes 15.png]]</div>
 
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">551101 – Ability to configure role for commitment when adding user to the team</span>'''
+
<span style="color:#008000;">'''574034 – Ability to have flexible contract type extension'''</span><br/> ICM 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.<br/> With this release, many ICM features such as lookups, saving a search, saving as a template, and so on are further enhanced to manage the extended attributes in the same way as normal attributes. This considerably improves usability and simplifies the process for users who deal with hundreds of items and need to have multiple configurations.<br/> Users can now:<br/> •&nbsp;&nbsp; &nbsp;Configure conditional attributes, tracking attributes, computations (enable expressions) to use as extended attributes.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Mark extended attributes as mandatory and validate. &nbsp;<br/> •&nbsp;&nbsp; &nbsp;Control access privileges for extended attributes based on the user’s role.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Maintain audits of the extended attributes.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Exclude extended attributes from copy while creating an agreement by copying the existing agreement.&nbsp;
  
Previously, when creating commitments, business owners were added to the agreement team as ''Contributors''. It is now possible to configure the role in which business owners of the commitment should be added to the agreement team (for example, ''Secondary Owner'', ''Observer'', etc.).
+
<br/> <span style="color:#008000;">'''551119 – Ability to copy and create existing commitments'''</span><br/> With this release, users have been provided with the capability to copy an existing commitment and generate new commitments from it. Users can also configure attributes to be excluded from being copied automatically. This considerably reduces time and effort required to create individual commitments.
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">466694 Ability to configure reminder notifications on entities</span>'''
+
<span style="color:#008000;">'''550181 Rules implementation for localized masterdata attributes'''</span><br/> Previously, localization support for masterdata attributes was limited to attributes only. If the attribute had a lookup value, its rule would not get triggered as the rule was supported only in English.<br/> With this release, users will be able to:<br/> •&nbsp;&nbsp; &nbsp;Trigger a rule if the masterdata value has been localized on the agreement, contract request, association or the masterdata creation page.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Trigger a rule if any lookup type attribute is updated using Icertis Experience for Word.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Configure any rule type as all rules now have localization support.
  
Earlier, ICM did not have Out-of-the-Box (OOTB) support for the reminder notifications in the core platform. Reminder notifications had to be customized based on each customer’s requirements.
 
 
To simplify the process, ICM now provides the ability to send the entity-wise reminders using a Reminder Notification Template to cater to wider requirements in the domain of Contract Management, Sourcing, and other Business Apps (Obligation Management and Supplier lifecycle).
 
 
The reminders can be set up based on a recurring or One-time pattern (Minute(s), Hour(s), Day(s), week(s), month(s), year(s)). This has enhanced productivity and user&nbsp; experience in addition to reducing efforts of technical configuration for task reminders.
 
 
Users can now:
 
 
*Set reminder notification for agreements, amendments and associations.
 
*Configure a template for reminder notification.
 
*Set the reminder notification based on Event Rule.
 
*Set reminders based on two types of recurrences – ''Set One Time Reminder'' and ''Set Recurrence Reminder'', which will get triggered once or multiple times respectively, based on the interval frequency.
 
<div class="image-green-border">[[File:7.11 Release Notes 16.png|720px|7.11 Release Notes 16.png]]</div>
 
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">551103 Auto-populating the currency when creating entities</span>'''
+
<span style="color:#008000;">'''551105 Ability to use attributes to identify unique line items'''</span><br/> Previously, RFQs and their multiple related records such as line items, rounds and awarding records were created without any associations. Users found it difficult to link RFQs to its related records.<br/> With this release, ICM offers a provision to define an agreement code that refers to both, the RFQ attribute and the current record attribute, at the time of linking the peer association to the agreement contract type.&nbsp;<br/> Users can now:<br/> •&nbsp;&nbsp; &nbsp;Set a flag to mark the peer association as child type at contract type level which will have normal association creation workflow.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Define the value of agreement code from the agreement and its related association contract type.
  
Earlier, currency preferences were defined at the contract type level and users had to manually change it based on their requirements. Now, users can define their preferred currency (for example, USD) using the&nbsp;''Preferred Currency'' option in ''My Preferences''. Based on the user preference, the selected currency will be auto-populated for any Currency attribute.
 
<div class="image-green-border">[[File:7.11 Release Notes 17.png|720px|7.11 Release Notes 17.png]]</div>
 
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">551104 Ability to retain original filename of uploaded files</span>'''
+
<span style="color:#008000;">'''550193 Extended number of records while adding a table as an association'''</span><br/> ICM supports adding associations to an agreement in various forms, such as documents and tables. With this release, ICM has now extended support to 200 records that can be assembled in an Association tagged as a table.&nbsp;
  
Earlier, when downloading a file in ICM, the original file name was not retained, and the file name was changed as per the naming convention defined in ICM.
+
<br/>  <br/> <span style="color:#008000;">'''568776 – Export and import capability for associated documents'''</span><br/> ICM provides a capability for bulk download (export) and upload (import) of line items from association grid using Excel. Now, users can create line items with extended attributes or associated document attributes based on the template selection and export/import through Excel into ICM.<br/> Users can now:<br/> •&nbsp;&nbsp; &nbsp;Select and add attributes from all attributes defined in masterdata contract type.<br/> •&nbsp;&nbsp; &nbsp;Load Excel filled by the buyer (at the RFQ level) at the Round level to match the information.<br/> •&nbsp;&nbsp; &nbsp;Create, edit and delete records in bulk using Excel.<br/> •&nbsp;&nbsp; &nbsp;Manage import/ export of lookup attributes, conditional attributes, and attributes derived by computations or enabled expressions in bulk.<br/> •&nbsp;&nbsp; &nbsp;Look up attributes in the same way as masterdata is looked up using Excel.<br/> •&nbsp;&nbsp; &nbsp;Control the access privileges to import/export Excel based on the user’s role.<br/> •&nbsp;&nbsp; &nbsp;Control access privileges for attributes in Excel based on the user’s role.<br/> •&nbsp;&nbsp; &nbsp;Localize and display attributes and headers in the Excel.<br/> •&nbsp;&nbsp; &nbsp;Validate data during import/export using Excel.<br/> •&nbsp;&nbsp; &nbsp;Keep data in Excel in sync with data displayed on the user interface.<br/> •&nbsp;&nbsp; &nbsp;Make attributes non-editable.<br/> •&nbsp;&nbsp; &nbsp;Manage refreshing associations during import/export.<br/> •&nbsp;&nbsp; &nbsp;Maintain and display audit of import/export operations.<br/> •&nbsp;&nbsp; &nbsp;Generate log files for line items.
  
The usability has now been improved so that users can now retain the original file name for any entity when uploading it to ICM, making it easier for users to identify and manage them. This is applicable to agreements, amendments, associations, and file attributes in agreements/associations.
+
<br/> <span style="color:#008000;">'''574036 Ability to configure and control access privileges based on role'''</span><br/> Previously, ICM users could only be assigned one of the default roles available in the system.&nbsp;<br/> With this release, ICM provides users the capability to define new roles and control access by specifying privileges depending on their business requirement. The access to the newly defined roles can be controlled using existing capabilities in ICM (such as Security Groups, Role Action Mapping, etc.). This is applicable for agreements, amendments and associated documents.&nbsp;<br/> With custom roles, users can:&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Control navigation pane access for agreement and associated documents.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Control group access privileges and team actions.&nbsp;
<div class="image-green-border">[[File:7.11 Release Notes 18.png|720px|7.11 Release Notes 18.png]]</div> <div class="image-green-border">&nbsp;</div>
+
'''<span style="color:#008000;">560477 Automatic update of entity count on navigation pane without refresh</span>'''
+
 
+
ICM now automatically updates the count for entities (such as ''Association'', ''Commitment'', etc.) at the execution of an event on the left navigation pane of the ''Details'' page. This improves the user experience as the page is no longer refreshed and the workflow continues smoothly.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">488574 &nbsp;– Replace primary clauses with alternate clauses from Clause Comparison Report</span>'''
+
<span style="color:#008000;">'''574087 – Ability to add auto-attachments as associations via event rule'''</span><br/> As part of RFQ creation process, users need to add several documents as mandatory attachments to RFQs that may not change frequently. Previously, users had to attach multiple such documents manually to every RFQ which was a tedious and time consuming process.<br/> ICM now has simplified the process by allowing users to attach predefined standard documents automatically to associations based on defined event rules.<br/> Users can now:<br/> •&nbsp;&nbsp; &nbsp;Maintain a repository of standard documents in masterdata.<br/> •&nbsp;&nbsp; &nbsp;Define the mapping between associations for auto-attachments for agreements.<br/> •&nbsp;&nbsp; &nbsp;Define rules and saved search to trigger the auto-attachment process for associations.<br/> •&nbsp;&nbsp; &nbsp;Bifurcate auto-attachments from manual attachments when copying an agreement.<br/> Note: This is applicable for agreements and amendments.
  
Earlier, ICM users could only replace clause text and language by using Word Add-ins (Icertis Experience for Word (.JS) or .Net). This was achieved by substituting the clause's text or language by the stored alternate clause.
+
<br/>  <br/> <span style="color:#008000;">'''585000 – Ability to define parent-child relationship for peer associations'''</span><br/> ICM provides the functionality to attach Associations to Agreement entities. This functionality has now been enhanced with the ability to define the type of relationship (association) as parent, child or peer.<br/> With this release:<br/> •&nbsp;&nbsp; &nbsp;Only one parent agreement can be added to another (child) agreement.<br/> •&nbsp;&nbsp; &nbsp;If an agreement has already been associated as a child of an agreement, then another agreement cannot be added to it as a parent.<br/> •&nbsp;&nbsp; &nbsp;Amendments can be linked to agreements and vice-versa only with a peer type of relationship; parent or child type relationships are not allowed.<br/> •&nbsp;&nbsp; &nbsp;Amendments can also be associated to other amendments.<br/> •&nbsp;&nbsp; &nbsp;Only one amendment can be associated as a peer to another amendment.<br/> •&nbsp;&nbsp; &nbsp;All existing related agreements will be tagged as peer associations.<br/> The option to define the relationship type is provided on the same window which opens up for linking/searching an agreement from the ‘+’ sign icon.
 
+
With this release, ICM allows replacing the clause text with the alternate clause text from ICM itself. This is accomplished using ''Compare Clause Changes with Previous Document Version'' icon available on the agreement ''Details'' page. For any particular primary clause, users can view the list of alternate clauses by clicking the ''Select Alternate Clause'' link and select the alternate clause to swap it with the selected primary clause. This ''Compare Changes with Previous Document Version'' window gives users the additional flexibility to preview the ''Previous Text'' and the ''Current Text ''of clauses.
+
 
+
Users can:
+
 
+
*View the ''Select Alternate Clause'' link in the Clause Comparison Report.  
+
*Replace a non-mandatory clause.  
+
*Track clause changes (primary clause replaced with alternate clause) through the ''Versions'' and the ''History'' tabs.
+
*View agreement preview with a replaced alternate clause.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">488577 Document upload validation shows the changes in associations tagged as file(s)</span>'''
+
<span style="color:#008000;">'''572764 Ability to scan files for viruses when uploading to ICM'''</span><br/> With this release, ICM 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 ICM against a wide variety of threats. It is applicable to the Word and Excel plugins as well.<br/> Users can now:<br/> •&nbsp;&nbsp; &nbsp;Scan all supported file formats by default during upload.<br/> •&nbsp;&nbsp; &nbsp;Scan files in bulk.
  
In ICM, associations tagged as a file in a template are added to the agreement by document assembly. During the redlining process, users may modify the agreement and make changes in the associations. Earlier, at the time of uploading a new version of the agreement, the user was notified of the changes detected in Associations tagged as a table.
 
 
With this release, ICM alerts the user and presents a summary of any text that is added, removed or modified in association(s) tagged as file(s).&nbsp;
 
 
The following actions take place as soon as a new agreement version is uploaded:
 
 
*The version being uploaded is compared with the latest version available in ICM.
 
*A window is displayed alerting the changes made in associations.
 
 
'''Note''': The user can view the changes in association by clicking the ''View all modifications'' button for a published agreement in Icertis Experience for Word. The user may also download a comparison between the previous version of the agreement and the version being uploaded. This downloaded document would highlight the modifications identified.&nbsp;
 
<div class="image-green-border">[[File:7.11 Release Notes 19.png|720px|7.11 Release Notes 19.png]]</div> <div class="image-green-border">&nbsp;</div>
 
'''<span style="color:#008000;">535845 – Ability to identify the first version of an agreement in the Clause Comparison Report</span>'''
 
 
Earlier in ICM, if there was only one version of the agreement, the ''Clause Comparison Report'' would display a ''No changes found'' message. This message was misleading to the users as it suggested that no clauses were changed, instead of conveying that only one version of the agreement has been created and hence there is no clause comparison.
 
 
This has now been rectified by leaving the ''Previous Text'' box blank and displaying the actual clauses that are available in the agreement in the ''Current Text'' box. This clearly indicates to the user that only a single version of the agreement is currently available.
 
<div class="image-green-border">[[File:7.11 Release Notes 20.png|720px|7.11 Release Notes 20.png]]</div> <div class="image-green-border">&nbsp;</div>
 
'''<span style="color:#008000;">467201 – Ability to copy team role from contract request, agreement, and amendment to its association</span>'''
 
 
Previously, in ICM when approvers were added to the contract request, agreement and amendment, they would get ''Manage'' Privilege to the respective entity, but ''None'' Privilege on the supporting document (Association entity) as they were not part of the team. Hence, these entities with supporting documents were sent out for approval without the approvers having the rights to make any changes to the associated documents.
 
 
ICM has now introduced the capability to copy the role-based team members while creating associations, so that the users have the privileges for associated documents as they do for the parent entities. This is achieved by configuring contract types.
 
 
Users can now:
 
 
*Copy the entire team of the entity (''Contract Request, Agreement, Amendmen''t) to its defined Association entity on a specific role (such as ''Observer)''.
 
*Copy an individual team member from a particular role of the entity (''Contract Request, Agreement, Amendment'') to its defined Association entity for any specific role (such as ''Secondary Owner, Contributor, Observer, Contract Admin'').
 
*Copy the entire team from the entity (''Contract Request, Agreement, Amendment'') to the association on predefined event.
 
*Get an Audit log while copying the team from the agreement to its respective association.
 
<div class="image-green-border">[[File:7.11 Release Notes 21.png|720px|7.11 Release Notes 21.png]]</div>
 
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">560209 User inclusion condition visibility in team</span>'''
+
<span style="color:#008000;">'''645417 Ability to create agreement with latest approved version while using Copy Agreement functionality'''</span><br/> Previously, In ICM, when the new agreement is created by coping existing agreement using the Copy Record functionality, it is created with the same version as the original agreement.&nbsp;<br/> ICM now provides the capability to choose the latest approved version of the template of the original agreement during copy to create the new agreement.<br/> Note: The Copy Record functionality does not change for third party paper.
  
Previously, the ''Teams'' tab for an agreement displayed columns with details for each user within a team such as ''Team Role, Step Number'', and so on. Now, a new column with the header ''By Rule'' has been added which indicates if the user has been added using a rule condition.
+
<br/>  <br/> '''<span style="color:#008000;">572756 – Ability to exclude auto-attached documents from the copied association</span>'''<br/> ICM now allows attaching standard documents from the masterdata repository for associations automatically based on the defined event rule.<br/> When an association with auto-attached documents is replicated by copying, there is a need to exclude auto-attached documents from the copied association. This is required to avoid duplication of association records and unnecessary upload of files into the ICM repository as the new created record will have its own auto-attached documents.<br/> ICM provides a flag or identifier to separate associations into manual and auto-attachment associations.<br/> Users can now:<br/> •&nbsp;&nbsp; &nbsp;Select auto-attachment associations when an agreement is sent for signature along with the bundled association.<br/> •&nbsp;&nbsp; &nbsp;Download all associations of an agreement in the ZIP format.&nbsp;<br/> &nbsp;
<div class="image-green-border">[[File:7.11 Release Notes 22.png|720px|7.11 Release Notes 22.png]]</div>  
+
If a user has been added by a rule, the value ''Yes'' is displayed in the column with a hyperlink.
+
  
Clicking the hyperlink displays a window specifying the rule condition with which the user has been added to the team. For example, ''John has been added if Created Date Is After February 12, 2020.''
+
== ICM API Enhancements&nbsp; ==
 +
<div class="image-green-border">
 +
<span style="color:#008000;">'''553319 – Additional APIs for amendments, contract requests and searches in ICM API 2.0'''</span>
  
The value ''No'' is displayed in this column if a user has not been added by a rule or if the user is added through an event rule.
+
With this release, some new APIs have been introduced that will allow business applications to interact with ICM using standard API nomenclature for amendments, contract requests and searches.<br/> These include:<br/> Amendment APIs&nbsp;<br/> In addition to the existing APIs to create amendments, new API are provisioned to create orphan amendments in the system.<br/> Contract Request APIs<br/> In addition to the existing APIs to manage contract requests, new APIs have been added to support getting and adding associations in a contract request.<br/> Search APIs<br/> Search API have been added to allow users to query agreements and related entities across multiple contract types.<br/> Search APIs have been added to allow creating, editing, executing and deleting saved searches.
<div class="image-green-border">[[File:7.11 Release Notes 23.png|720px|7.11 Release Notes 23.png]]</div> <div class="image-green-border">&nbsp;</div>  
+
</div> <div class="image-green-border">&nbsp;</div>  
'''<span style="color:#008000;">560216 – Generate a redline version for document comparison</span>'''
+
== Enhancements to ICM Add-ins&nbsp; ==
  
Previously, in ICM, users could view the changes made between two agreement versions side-by-side through the ''Document Comparison'' option. With this release, instead of the side-by-side view, the ''Document Comparison'' capability has been enhanced with an option to view and download the redlined document of the selected agreement versions, highlighting the changes in Microsoft Word format.
+
<span style="color:#008000;">'''619841 – Introducing Icertis Experience for WordAI'''</span><br/> With this release, two of the ICM Add-ins - NegotiateAI and Icertis Experience for Word have been merged into Icertis Word.AI to provide users a seamless experience.&nbsp;<br/> Icertis Word.AI can be leveraged to create, edit and manage templates, clauses and agreements.&nbsp;<br/> Using Icertis Word.AI, it is now possible for:&nbsp;<br/> •&nbsp;&nbsp; &nbsp;ICM Administrators to configure and setup Icertis Word.AI.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Other users to work with templates, clauses and agreements.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Perform different tasks such as creating, editing and deleting template variables. &nbsp;<br/> •&nbsp;&nbsp; &nbsp;Tag attributes, clauses, associations, signatories and template variables. &nbsp;<br/> Note: &nbsp;<br/> •&nbsp;&nbsp; &nbsp;Users can view and edit only those clauses and agreements for which they have Manage privilege in ICM. &nbsp;<br/> •&nbsp;&nbsp; &nbsp;To edit an agreement, a user needs to download the agreement document and open it in Word.AI.&nbsp;
<div class="image-green-border">[[File:7.11 Release Notes 24.png|720px|7.11 Release Notes 24.png]]</div> <div class="image-green-border">&nbsp;</div>  
+
'''<span style="color:#008000;">545742 – Extending support of multiple rulesets for event rules</span>'''
+
 
+
Previously, ICM users could create multiple rulesets for approval rules, template selection rules, and clause assembly rules. However, creating rulesets for event rules was not supported.
+
 
+
Rulesets are the set of rules created for a particular event for any ICM entity. For example, you can create multiple rules in the ruleset as displayed in the image below.
+
<div class="image-green-border">[[File:7.11 Release Notes 02.png|720px|7.11 Release Notes 02.png]]</div>  
+
With this release, an Administrator can now:
+
 
+
*Create multiple rulesets for event rules, for any entity, per event.
+
*Copy event rules to target entity. However, a new rule is created for the target entity that does not override the existing one, if any. The name of the ruleset remains unique throughout the system.
+
 
+
For example, you can create multiple rulesets for event rules for any entity as displayed in the image below. When multiple event rules are defined, ICM ensures all event rules are executed.
+
<div class="image-green-border">[[File:7.11 Release Notes 03.png|720px|7.11 Release Notes 03.png]]</div>  
+
The ''Stop Processing More Rules ''option when selected as ''Yes ''allows users to stop evaluating the rules within the ruleset.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">560728 Global favorites – supplier view</span>'''
+
<span style="color:#008000;">'''571651 Provision to show clause deviations in Icertis Experience for Word'''</span><br/> Previously, users were able to view deviations in agreement clauses through the agreement details page. With this release, users can now see within the Word Add-in, any such clauses which have been tagged/added in an agreement and which are deviated. The details of the deviated clause are also displayed through Word Add-in.<br/> With this release:<br/> •&nbsp;&nbsp; &nbsp;A list of deviations is displayed in Agreement Clauses tab for an agreement or amendment’s document version.&nbsp;<br/> •&nbsp;&nbsp; &nbsp;Clauses that are added using the Add Deviation option through the Word Add-in are also displayed.<br/> •&nbsp;&nbsp; &nbsp;View information regarding the deviated clauses such as Status, Deviated By, Deviated On in the Word Add-in as well as a View in ICM link.<br/> The deviation clauses are visible based on role action mapping as per existing ICM flow. They are searchable, so users can easily navigate to a particular clause in the agreement document and view the highlighted content of those clauses in Word Add-in.<br/> Note:&nbsp;<br/> •&nbsp;&nbsp; &nbsp;The deviation clauses are only displayed for the latest version of the agreement.<br/> •&nbsp;&nbsp; &nbsp;Users cannot perform the deviation approval flow from the Word Add-in.
  
Previously, ICM users created favorites for themselves however, these favorites were not accessible to all users in the domain.
+
<br/>  <br/> <span style="color:#008000;">'''487082 – Ability to take workflow actions using Icertis Experience for Word'''</span><br/> Previously, tasks related to template and clause management could be managed using Icertis Experience for Word. However, to manage agreement related tasks, users had to switch between ICM and the Word Add-in. &nbsp; &nbsp;<br/> ICM now enables the users to accomplish agreement related workflow actions such as approving, rejecting or recalling an approved agreement directly using Icertis Experience for Word. This considerably reduces the turnaround time and improves the user experience. User can view the updated status of the agreements on the Versions tab, History tab and Audit Trail on the ICM Web.
 
+
ICM Administrators can now set default favorites for all the users in the domain.&nbsp; They will be able to pin the necessary saved searches for external users/suppliers (who do not have access to saved searches) so that they can easily find actions and even view the filtered lists.
+
 
+
Administrators can now:
+
 
+
*Mark the global search as a global favorite so that all users can view the global favorites
+
*Display the global favorites in the respective entities for easy navigation to exact action or list
+
*Reorder the global favorites as per entity so that the desired order can be published for the user  
+
*Configure maximum 4 favorites per entity
+
 
+
'''Note''':
+
 
+
*Users cannot set the Administrator default favorites. However, users can un-pin the global favorites.
+
*When users pin the searches along with global favorites, they won’t get any more updates on global favorites.&nbsp;
+
*Global favorites apply to agreements only.
+
*A maximum of 4 global favorites are displayed to the user based on the permissions for those security groups.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">589531/591634 – Enhancement of KPI reports performance</span>'''
+
<span style="color:#008000;">'''574616 – Icertis logo updation in Icertis Experience for Word'''</span><br/> With this release, the ICM Word Add-in logo has been replaced with the improved logo for Icertis Experience for Word.<br/> &nbsp;
 
+
Previously, additional reports such as ''Cycle Time Report'', ''Template Clause Report'', ''Expired Agreements'', ''Approved Requests Waiting'' ''for Contract Creation'', ''Signature Type Report'', ''User Login Report'' and ''CLM Activity Report'' were available to the user as dashboard KPIs.
+
 
+
With this release, the ''CLM Activity Report'' and ''Cycle Time Report'' have been deprecated, thereby improving ICM performance considerably.
+
  
 
&nbsp;
 
&nbsp;
  
== ICM API Enhancements&nbsp; ==
+
== Enhancements to Artificial Intelligence Applications in ICM ==
<div class="image-green-border">
+
'''<span style="color:#008000;">541856 – API 2.0 Implementation</span>'''
+
  
With this release, a new version of the Icertis APIs have been introduced that will allow business applications to interact with ICM using standard API nomenclature for agreement and associated entities.
+
<span style="color:#008000;">'''510546 – Establishing a contract lineage using AI'''</span><br/> Contracts go through multiple transformations over a period of time. During the contract negotiations, multiple attributes and clauses get added or changed. Team members, statuses, obligations, associations also get added, updated or removed. Once the contract is executed, many addendums are added later or multiple clauses are replaced with new clauses in the amendments, etc. With such high number of transformations, it is difficult to keep track of which clause or attribute is in force.&nbsp;<br/> ICM has now improved usability by using AI so that users can now easily see the changes in the clauses, attributes, team members, statuses, versions, obligations and associations due to developments in the contract negotiation process or due to various amendments and addendums added subsequently in one go. This helps contract owners to learn from these changes and devise an optimal negotiation strategy for further engagement with customers or vendors.<br/> Contract owners can now:&nbsp;<br/> Identify the changes done to the contract over a period of time, so that all the changes made are visible in the contract at one go.&nbsp;<br/> Visualize how the attribute values are changed over a period of time.&nbsp;<br/> Visualize how the clauses and their languages have changed over a period of time.&nbsp;<br/> Visualize how the statuses of agreements have changed over a period of time.&nbsp;
  
The highlights include:
 
 
*Supporting Resume workflow action to perform additional activities such as Send for External Review, Upload Signed Copy
 
*Caching strategy
 
*Swagger documentation
 
*Security review
 
*Multi-tenancy
 
*Error message localization
 
*Designing Masterdata endpoints similar to agreements endpoints
 
*Embedding internal associations of agreements (such as Clauses, Version, Deviations, Teams) in agreement response; support, create, update and get internal association from agreement
 
*API Gateway capabilities such as throttling and metering
 
 
The list for API 2.0 include the following endpoints for creating an Agreement, Masterdata and Contract Request, whichever applicable:
 
 
*'''Get the instance:''' used to get an empty instance of an entity.
 
*'''Create Instance:''' used to create an instance record of an entity. There could be additional parameters which could specify actions such as Create, Create and Publish, Create and Send for Approval.
 
*'''Update Instance:''' used to update an instance record of an entity. There could be additional parameters which could specify actions such as Update Metadata, Upload Document or Update Instance.
 
*'''Save the Document:''' used to upload a document.
 
*'''Trigger Actions:''' used to trigger workflow actions; different actions will be part of additional parameters such as Send for Approval, Signature, Approve, Reject, Recall, Publish, etc.
 
*'''Get Instance:''' used to get the instance of an entity.
 
*'''Get Instances:''' used to get the instance of an entity in bulk. The search condition could be a post parameter.
 
*'''Add Team Member:''' used to add a team member to an instance.
 
*'''Remove Team Member:''' used to remove a team member from an instance.
 
</div>
 
 
&nbsp;
 
&nbsp;
  
== Enhancements to ICM Add-ins&nbsp; ==
+
<span style="color:#008000;">'''575397 Improved discovery based on existing customer data'''</span><br/> ICM’s existing discovery model discovers 15 attributes and more than 40 clauses from MSA or NDA type agreement documents.&nbsp;<br/> With this release, the process of discovering attributes and clauses is improved for better accuracy by training the in-built discovery model with wide variety of agreements. ICM discovery model now discovers out-of-the-box attributes from SOW type of agreements.&nbsp;<br/> The existing ObligationAI approach, which was model based, is now replaced by AI and Rule-based approach to discover obligations more accurately.<br/> Contract negotiators can now:&nbsp;<br/> Identify clauses and attributes from multiple MSA, NDA, IT MSA, SOW contract types more accurately and automatically using DiscoverAI and NegotiateAI apps.&nbsp;<br/> Identify obligations from MSA, NDA and SOW contract types more accurately and automatically with ObligationAI.<br/> Select a discovery model specific to contract types to discover attributes and clauses with better accuracy as compared to other models.
<div class="image-green-border">
+
'''<span style="color:#008000;">515446 Word Add-In (.Net) should not close once the contract is published</span>'''
+
  
Previously, when a user tried to publish an agreement document, Word Add-in (.Net) would notify the users that the document would be saved and closed. This behavior forced the user to select ''OK'' if they wanted to publish the document. However, this action would close the document before publishing it.
+
<br/> <span style="color:#008000;">'''575399 – UX revamp to display discovered attributes and original document side-by-side'''</span><br/> Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.<br/> With this release, when contract negotiators trigger the discovery process, they can view the progress of AI discovery on the agreement Details page. They will be able to view:<br/> The progress of all four discovery processes.<br/> The percentage of discovery process completed for each of discovery process and the overall discovery process.<br/> The approximate time it would take to complete the individual discovery process and the overall discovery process.<br/> Contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, etc. are displayed along with the agreement document. An option is now available to launch side-by-side view of the document along with the discovered entities. Using this option, users can view different sections for discovered clauses, attributes, tables and obligations.&nbsp;<br/> Contract negotiators also have an option to search within the agreement document. The results are highlighted to the user and a count is displayed. Users can also save any changes made in the individual discovery sections.
  
With this release, once the document gets published, a validation window is displayed giving the user the choice to open the published document. Hence, the user does not need to download the new version to view the published document. The user can now stay on the document and make further edits or reviews, as required, while publish function occurs in the background.
 
</div> <div class="image-green-border">[[File:7.11 Release Notes 25.png|720px|7.11 Release Notes 25.png]]</div>
 
 
&nbsp;
 
&nbsp;
  
 
+
<span style="color:#008000;">'''575455 Ability to process multiple documents simultaneously during the discovery process'''</span><br/> Previously, upon receiving multiple requests, the AI discovery model added them in a queue form and processed each document individually. With this release, the discovery performance has been enhanced such that multiple documents can be processed simultaneously and within lesser time.<br/> Users can now start the discovery process for their document without waiting for other discovery processes to complete. A total of 20 documents can now be processed in parallel.<br/> The duration for a document discovery to be completed depends on the number of pages in a document. For example, discovery process for a .docx file with 10 pages and 1 table will take 120 seconds to complete; whereas one with 500 pages and 15 tables will take 1800 seconds.
== Enhancements to Artificial Intelligence Applications in ICM ==
+
 
+
'''<span style="color:#008000;">510541 eDiscovery using Artificial Intelligence</span>'''
+
 
+
Legacy contract documents from the archives of companies contain a host of unstructured but valuable information. From a CLM platform perspective, this information can be categorized and structured into attributes, clauses, agreements, etc.
+
 
+
With this release, ICM introduces a framework using Artificial Intelligence (AI) to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.
+
 
+
With eDiscovery using AI:
+
 
+
*ICM can automatically confirm certain discovered clauses, so that users do not have to confirm them manually.  
+
*Auto-confirmed clauses can be searched in the same way as any other agreement clauses.  
+
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses.
+
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically.
+
*While auto confirming, ICM compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with a clause in the clause library, then the discovered clause is identified as one from the clause library. If the match percentage is lesser than the threshold, then clause is identified as one of the standard ICM AI clause category.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">510549 Inbuilt discovery of attributes and clauses in IT services vertical</span>'''
+
<span style="color:#008000;">'''602198 Support for user created attributes in NLP search'''</span><br/> Previously, the ICM AI enabled mode of searching allowed users to search agreements using a spoken language statement. With this release, the functionality has been enhanced to support user defined attributes as well. For example, queries such as “contract value above 20000 USD”, “contract value below 20000 USD”, “contract value between 20000 USD and 2000000 USD” and so on, can be entered to search contracts of a certain value.<br/> &nbsp;
  
The nature of business for companies providing IT services is such that more than 80% of their contracts would be drafted using third party paper. As of now, such IT firms deploy large teams to extract important clauses and attributes in these third party contracts in order to track the contractual obligations, risks, rebates, discounts, etc. It is a time consuming and error-prone process. Hence, companies need a system which will extract these clauses and attributes automatically.
+
== Enhancements to Reports ==
  
''RiskAI'' is a major application of inbuilt discovery of such attributes and clauses, using which a risk score can now be computed for a given agreement. ''DiscoverAI'' will set a value of an attribute if a specific clause is found in the agreement. A rule can further be written to assign a risk score in either case if the clause is present or absent in the agreement.
+
<span style="color:#008000;">'''570314 – All core SSRS reports to only include contract types classified as Contracting'''</span><br/> ICM offers the functionality to classify Business Type/ Contracting agreement type at contract type level. With this release, core reports will be limited to Contracting business application type.<br/> Users with access to standard and insights reports will only be able to see data related to agreements with Contracting business application type. Thus, the reporting data would not contain any sourcing agreements.<br/> This is applicable to the following reports:<br/> Agreement Clause Content Report&nbsp;<br/> Agreement Deviation Report<br/> Agreements Pending Approval Report<br/> Agreements Pending Execution Report<br/> Average Agreement Turn Around Time Report<br/> Clauses Pending Approval Report<br/> Expiring Agreements Report<br/> Templates Pending Approval Report<br/> Cycle Time Report&nbsp;<br/> Detailed Report&nbsp;<br/> Attribute Value Report&nbsp;<br/> Template Clause Report&nbsp;<br/> Clause Profiling Report&nbsp;<br/> Clause Deviations Report<br/> Expired Agreements Report&nbsp;<br/> Approved Requests Waiting For Contract Creation Report<br/> Signature Type Report&nbsp;<br/> CLM Activity Report&nbsp;<br/> Clause Insights Report<br/> Deviation Insights Report
  
With this release, in addition to the generic discovery model:
+
<br/>  <br/> <span style="color:#008000;">'''606134 – All Power BI Reports to only include contract types classified as Contracting'''</span><br/> Users with access to Power BI dashboards will now only see data of agreements with business application type as Contracting while accessing the Business Summary, Legal Summary and Legal Details reports.<br/> Since the Custom report is common to sourcing and contracting, having a filter which is configurable makes the experience more user-friendly than only restricting the create report for contracting use cases only.
 
+
*The ICM configurator can deploy a discovery model specific to the IT service industry, so that users can discover attributes and clauses specific to that industry.
+
**'''Attributes: '''''LiabilityType'', ''ComplianceType''
+
**'''Clauses''': ''Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability ''and''Uncapped'' 
+
*Contract negotiators can use ICM to discover attributes and clauses using a pre-trained model, so that they do not have to identify them manually,
+
*Contract negotiators can identify if a specific clause is included in the document or not, so that they can initiate an approval workflow to take care of compliance.
+
*The value of the contract can now be driven based on the presence or absence of the specified clause, and this can further be used for calculating the risk score.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">510545 Automating retraining of AI models based on user action feedback</span>'''
+
<span style="color:#008000;">'''567137 Ability to add datasets for associated documents in Power BI for obligation and management'''</span><br/> In order to have a comprehensive view of the state of obligation compliance users needed to have self-serve ways to build reports and dashboards. Users have now been given the flexibility to build reports on obligation compliance across hierarches – from agreements and obligations to fulfillments and fulfillment evidences.&nbsp;<br/> With this release, users have the option for slice and dice for viewing and narrowing down to the right type of Obligations for any given context. Advanced Analytics with Power BI is the ICM offering to let customers create and view custom reports. Users will now have OM application datasets for Agreement, Obligation and Fulfillment entities in the Power BI data model as well.&nbsp;<br/> With the additional data sets, users will be able to generate reports on Power BI such as for:<br/> The aggregate fulfillment status for a given obligation, especially for recurring fulfillments.<br/> Number of days it took for a fulfillment cycle, which is for an obligation or fulfillment to move from created to approved state.
  
Continuous learning and improvement based on user feedback is what differentiates AI/ML apps. The recall and precision of AI apps improves as it learns from a variety of documents.
+
<br/> <span style="color:#008000;">'''657965 – Support for Service Principal Authentication method for Power BI'''</span><br/> ICM has now extended support for Service Principal Authentication method to authenticate Power BI resources for Advanced Analytics. It has been implemented as the default method of Power BI authentication for improved security. However, the option to continue with the current authentication method of using user credentials for Power BI is still available.
 
+
While user feedback is heavily incorporated in the initial phase of model training, this model has now been retrained to incorporate changes based on user interactions. It has been further enhanced to incorporate user interactions with the attribute discovery on the Web UI as well as ''NegotiateAI'' and the feedback will be used to suggest precise default options on the attributes for subsequent discoveries.
+
 
+
With this release, the actions taken by contract negotiators to correct recommendations for discovered attributes like selecting different option than the default option suggested by the algorithm, or selecting an altogether different value if none of the options suggested by algorithm match the expectation, would be automatically learned by the model. When a document with same language or similar language is processed next time, then the model will suggest the learned value as a default option to the users so that they do not have to enter it manually again.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">465906 Contract highlights</span>'''
+
<span style="color:#008000;">'''573000 Sub-role included in Detailed and User Profiling Reports'''</span><br/> ICM provides the ability to define sub-roles for the Approver role. With this, all the capabilities of the Approver are enabled for users at the sub-role level. This capability has now been extended to reports so that users can have relevant information and make informed decisions.&nbsp;<br/> With this release, the Detailed Report, User Profiling Report and Agreements Pending Approval Report have now been modified to display the Approver sub-roles such as Contract Admin, Legal Approver and others.
 
+
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.
+
 
+
With this release,
+
 
+
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience.  
+
*In case no phrases are specified, then ICM will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance.
+
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user.
+
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICM will identify the important sections of the contract based on historical data and phrases specified by the configurator.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">539481 – DiscoveryAI / NegotiateAI support for multi-select attributes</span>'''
+
<span style="color:#008000;">'''573621 - Enhancement to reports processing error message'''</span><br/> Previously, when viewing reports resulted in processing errors, the No data available message was displayed. This message has now been modified for clarity, as follows:<br/> An error occurred during report processing, if the issue persist kindly contact customer support team.
 
+
''DiscoverAI&nbsp;''helps contract negotiators to discover attributes and clauses in the agreement document. The discovered attributes are mapped to respective datatypes. Previously, ICM supported string, number, date, choice, boolean, text, lookup percentage and currency type attributes.
+
 
+
With this release, ICM has extended the discovery support to URL datatype attributes. ''DiscoverAI'' and ''NegotiateAI'' can now discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page, in both - ''DiscoverAI'' and ''NegotiateAI'' apps.
+
 
+
ICM has now added an option in the discovered clauses menu of ''NegotiateAI'' to find clauses similar to discovered clauses in the ICM repository.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">566499 – Search as a natural language query in ICM</span>'''
+
<span style="color:#008000;">'''601540 - Unavailability of Template Clause Report as Dashboard KPI'''</span><br/> With this release, the Template Clause Report has been deprecated from the Dashboard KPIs. However, it will still be accessible from the Reports tile.
 
+
The current search functionality in ICM supports dynamic faceting and keyword-based search in three modes - metadata search, document or full-text search, and combined search. It assumes some level of expertise with users when they want to filter down the results to find exact records they were looking for.
+
 
+
With this release, ICM has introduced an AI enabled mode of searching the agreements. Users will be able to find the agreements in ICM by simply writing a spoken language statement. This mode allows a user to enter search terms in any form, including a statement, a question, or a simple list of keywords.
+
 
+
In this release, the user would be leveraging this Natural Language Processing (NLP) technology for an Agreement entity on Global Search page as well as Agreement index page.
+
 
+
&nbsp;It supports querying on system attributes as well as few seeded attributes like status, contract type name, effective, created, modified, expiry dates, users, roles, clauses, etc. In this mode, users can specify the additional filters in the query itself to get the required results; for example, ''MSA Agreements expiring next month, Agreements which are executed and contain a confidentiality clause, etc.'' The NLP search query results can be further filtered using the existing ICM category-based filters.
+
<div class="image-green-border">[[File:7.11 Release Notes 26.png|720px|7.11 Release Notes 26.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.11 Release Notes 27.png|720px|7.11 Release Notes 27.png]]</div> <div class="image-green-border">&nbsp;</div>
+
 
+
== Enhancements to Reports ==
+
 
+
'''<span style="color:#008000;">519281 – Out-of-the-Box Obligations Management Dashboard reports</span>'''
+
 
+
With the introduction of the Obligation Management app in the previous release, the need for specific reporting techniques is evident so that business executives can track and monitor obligations and fulfillments. To achieve this, the implementation teams are required to spend considerable time and effort to customize Obligation objects as per the customer requirements.
+
 
+
Hence with this release, the Obligations Management Dashboard Reports have been introduced on the Reports tile in ICM. These out-of-the box reports are available to authorized users who have access to the Obligation Management app without any need for customization.
+
 
+
The Obligation Management Reports include:
+
 
+
*'''Obligations Dashboard Report:''' provides information of the Fulfillments due in the next 30 days and Fulfillments overdue by the owner. This enables the users to take corrective actions on time and thus mitigate any risks.
+
*'''OMH - Obligation Management Health Report:''' provides an overall view of the total Fulfillments across all agreements that are fulfilled.
+
 
+
Access to these reports can be provided through Security Groups (similar to other reports). Only authorized users with access to Obligation Management can view the Obligation Management Dashboard reports. Even if the users are authorized to view/access a specific report, the privileges of the reports further follow the authorization that the user has in ICM. If the user does not have the privileges to view a particular set of agreements in ICM, they would not see those in the report even though they have the view privileges for the reports.
+
  
 
&nbsp;
 
&nbsp;
Line 525: Line 245:
 
== Integrations ==
 
== Integrations ==
  
'''<span style="color:#008000;">467181 Generic integration framework to support SFTP interface</span>'''&nbsp;&nbsp;
+
<span style="color:#008000;">'''541825 Integration with the new eSignature platform &nbsp;&nbsp;'''</span><br/> With this release, customers can now use Namirial eSignAnyWhere as their electronic signature platform to send the agreements electronically for signatures to internal and external signatories. The invited signatories receive an email notification with a link to the document to review and sign or decline to sign or to delegate the action. The agreement will be executed once the document is signed electronically by all the involved signatories. &nbsp;&nbsp;<br/> Contract administrators can track the status of the agreements sent for signature within ICM. They can also recall the agreement sent for signature, if it was not signed by all parties.<br/> 569172 – Enabling Electronic seal tag for signing agreement documents &nbsp;&nbsp;<br/> Previously, users were able to sign agreements based on signature tags present in the agreement templates. &nbsp;&nbsp;<br/> With this release, ICM has extended the support for enabling electronic seal tags in templates that will be used for marking electronic seals during the signature process using DocuSign. The support of electronic seals will help the organization’s legal teams to certify the integrity and the origin of the contracts.
  
Contract creation in ICM relies heavily upon availability of appropriate masterdata. As ICM does not own the masterdata, customers have to upload it manually. The process of extracting, transforming and loading the masterdata into ICM is cumbersome and can get very complicated depending on the source of origin. Moreover, the lack of industry standard data upload capability such as SFTP as part of platform leads to redundant coding effort for implementation teams.
+
&nbsp;
  
With this release, the Secure File Transfer Protocol (SFTP) adapter has been built as an automated solution to load masterdata once extracted from source of truth via SFTP. SFTP, a secure version of File Transfer Protocol (FTP), is a network protocol which facilitates file access, file transfer, and file management over a Secure Shell (SSH) data stream.
+
<span style="color:#008000;">'''579067 – Ability to support additional electronic signature platforms'''</span><br/> Just like support has been extended to Namirial eSignAnyWhere in addition to DocuSign and Adobe Sign for electronic signatures, ICM has enhanced adaptability by making it possible to implement and integrate any other electronic signature provider as well based on customer requirements.
  
This will enable Administrators to:
+
&nbsp;
  
*Define configuration parameters required for SFTP interface using Client App Reference and Client App Entity Mapping.  
+
<span style="color:#008000;">'''572516 – SAP S/4 Supplier masterdata integration &nbsp;'''</span><br/> The Icertis Experience for SAP S/4 HANA allows users to search, display and select S/4 HANA masterdata required for completing the contracting process within ICM.<br/> The ICM Experience for S/4 HANA adapter:<br/> Allows periodic data sync between S/4 HANA masterdata and ICM masterdata tables.<br/> Can be configured such that ICM Admin ca configure the data sync jobs and the related entity mappings.<br/> Is agnostic to masterdata entity i.e. it is generic enough to support any masterdata that the customer would like to sync from S/4 HANA into ICM to complete contracting business process.&nbsp;<br/> Some key use cases that customers should be able to configure the adapter to include:<br/> Supplier master data from S/4 HANA to ICM.<br/> Material/Items master data from S/4 HANA to ICM.<br/> Payment master (Terms, Types) from S/4 HANA to ICM.
*Configure and run scheduled batch jobs via SFTP.  
+
  
The execution of this integration sync task allows ICM to read the metadata definitions and execute the job successfully, which in turn will allow users to easily upload masterdata required for completing CLM process in bulk. Users will receive an error when records are not present and can generate log files for further processing.
+
&nbsp;
  
This enables users to:
+
<span style="color:#008000;">'''572517 – SAP S/4 HANA masterdata lookup&nbsp;'''</span><br/> With this release, ICM and ICM business applications (Sourcing and Obligation Management) have been integrated with SAP S/4 HANA to render masterdata lookup from SAP S/4 HANA.
  
*Create generic integration mapping in cross reference.
+
<br/>  <br/> <span style="color:#008000;">'''573373 – Generic integration framework to support contract requests via ASB'''</span><br/> Previously, ICM supported a generic ASB adapter for inbound and outbound integration for Agreements. With this release, support is provided for creating contract requests for agreements. Users will now be able to create and update Contract Requests in ICM using an external application.
*Create generic integration mapping in client app entity mapping.  
+
*Download masterdata template file from cross reference (based on client app entity mapping).
+
*Publish masterdata template file on SFTP (based on client app entity mapping)
+
*Create, update and delete records from masterdata tables using the input file from SFTP server.
+
*Receive logs/errors on SFTP.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">530080 – Generic integration framework to support ASB interface</span>'''&nbsp;&nbsp;
+
<span style="color:#008000;">'''573377 – Generic integration framework to support associations via ASB'''</span><br/> Previously, ICM supported a generic ASB adapter for inbound and outbound integration only for agreements. With this release, support is provided for creating contract requests for the agreements. Users will now be able to create and update contract requests in ICM using an external application. &nbsp;<br/> The ASB adapter will pick the JSON payload from the message queue and create associations to an existing agreement or RFx record in ICM. Users will thus be able to manage purchase requisitions, purchase orders, sourcing events and similar tasks by sending associated data. &nbsp;
 
+
As we know that the process to extract, transform and load data into ICM is a substantial task based on the source of the origin. To simplify this, we have built the Azure Service Bus (ASB) adapter, which is an automated solution to load and update master, transaction data once extracted from the source of truth via ASB using JSON payloads.
+
 
+
Azure Service Bus (ASB) is a fully managed enterprise integration message broker. Data is transferred between different applications and services using messages. The ICM-ASB adapter considers the approach based on REST and OData principles that exposes a uniform, stateless interface which communicates using HTTP(S) and JSON payloads.
+
 
+
Users can now:
+
 
+
*Define configuration parameters for ASB interface using client app reference and client app entity mapping.
+
*Create and maintain latest masterdata in ICM required for contracts and contract requests via ASB interface.  
+
*Push transaction data to third party systems via ASB interface to be able to manage ICM entities using necessary JSON payloads.
+
*Maintain business entities such as purchase requisitions. Purchase orders or sourcing event from procurement systems to ICM via ASB interface.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">544347 Ability to integrate ICM with Enterprise-Level Identity Providers using OpenID Connect protocol</span>'''
+
<span style="color:#008000;">'''573379 Generic integration framework to support amendments via ASB'''</span><br/> Contract amendments are an integral part of business flow and the support for amendment integration is critical for businesses. With this release, the generic integrations ASB adapter will be able to update amendments to an agreement on the created, updated, approved and executed actions.&nbsp;
 
+
ICM is now integrated with Enterprise-Level Identity Providers (IdP) such as PingFederate for user authentication and Single Sign-On (SSO) using the OpenID Connect protocol.
+
 
+
This will allow users trying to access the ICM application to get authenticated using the SSO platform. Once the credentials have been validated, the user will be redirected to the ICM Dashboard and ICM will authorize the user to securely access ICM based on the authentication token from the SSO platform. Users will be able to login using different browsers and to all ICM Add-ins.
+
 
+
This integration implementation is flexible enough to enable connection with other identity providers that use the OpenID Connect protocol.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">467179 SFDC experience enhancements – simplified UX - action in grid</span>'''&nbsp;&nbsp;
+
<span style="color:#008000;">'''594454 Additional connector support for JSON file format'''</span><br/> Previously CSV files were supported for masterdata upload using ASB and SFTP, while text based files were supported for uploads using SFTP.&nbsp;<br/> With this release, the file based integration will additionally support JSON file format, while also supporting blob connectors.
 
+
The Icertis Experience for Salesforce already provides the capability for Salesforce users to perform agreement-related tasks from within Salesforce.
+
 
+
ICM is now improving the user experience such that Salesforce users can perform their tasks more seamlessly by taking actions on agreements with fewer clicks than required earlier.
+
 
+
The user will now be able to view a contract record by double-clicking the row, instead of the earlier option of clicking the ''View'' hyperlink. They will be able to take ''Download, Assemble Contract'' and ''Send for Approval'' actions directly from the ''Action'' column of the Contract grid on Salesforce entity forms, without opening the agreement record. These actions will be displayed to the user based on the workflow state of the agreement.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">537762 – SFDC experience enhancements improved search functionality</span>'''
+
<span style="color:#008000;">'''554864/554868 Support for request review and upload actions in Salesforce grid'''</span><br/> Previously, ICM users could manage and execute contract management tasks using Salesforce Classic and Lightning user interface. The Icertis Experience for Salesforce introduced support for the following actions at the grid level: Assemble, Download and Send for Approval.&nbsp;<br/> With this release, support has been extended for the Send for Review and Upload document actions, thus considerably improving usability. &nbsp;The action buttons displayed on the user interface are based on the privileges assigned to the user via role action mapping in ICM . The agreement can be sent for review to multiple users by selecting the users from the available list.<br/> Note: If a user wants to view or edit a contract record, they will still have to double-click the contract record which will open the contract Details page in Salesforce.&nbsp;
 
+
Previously, there were 2 separate sub-tabs, 1 each for Contracts and Contract Requests, under the ICM tab within Salesforce. The previous ''Search ''page when rendered from within an iFrame inside Salesforce, gave the user a perception that they are working outside of Salesforce application.
+
 
+
With the SFDC experience enhancement, the user will have the ability to:
+
 
+
*Search for contracts or contract requests from a common page.  
+
*Provide search conditions to limit their search.
+
*View both contract and contract request&nbsp;records as a result set, on the same page, depending on the selection criteria.
+
*View ICM saved searches, and refine searches based on metadata and full text.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">537766 Reporting capability within Salesforce</span>'''
+
<span style="color:#008000;">'''537774 Ability to create contracts based on Opportunity or Quote'''</span><br/> Previously, users could only manage contracts using the Icertis Experience for Salesforce. They did not have the option to automatically initiate a contract based on an Opportunity or Quote status.&nbsp;<br/> With this release, the contract creation process has been automated based on opportunity or quote status, will increase the productivity of sales users.<br/> Sales admin users can now:<br/> Configure the opportunity or quote status which can automatically trigger the contract creation.<br/> Configure the contract type which should be used to create the contract based on data from an Opportunity or Quote.<br/> Define the Type of Paper to be used as Own or Third Party.<br/> Configure automated contract creation or manual contract creation by creating a task for the opportunity (for which a contract needs to be created).&nbsp;<br/> If there is a task to manually create a contract, Sales users will be able to create a contract using a single button click that will assemble all necessary documents for the type of contract to be created i.e. follow the same steps as above.<br/> For auto creation of contracts, the ICM for Salesforce will determine the dependencies for the contract. For example, if the opportunity is for an extension, the existing master agreement for the account will be identified and an appropriate contract type such as an order form will be selected and associated with it.<br/> Additionally, Salesforce users will receive a Task and/or Chatter notification whenever a contract is automatically created.
  
Icertis Experience for Salesforce already provides the capability for Salesforce users to execute contract management tasks from within Salesforce.
 
 
Now, this capability has been enhanced by allowing users to access ICM's reports within Salesforce instead of having to login to ICM to do so.
 
 
Providing the ''Reports'' tab within the ICM tab of Salesforce radically simplifies tasks for the users as well as increases the productivity many folds. Based on their authorization, users can view and execute ''Default'' and ''Custom'' ''Reports''.
 
<div class="image-green-border">[[File:7.11 Release Notes 28.png|720px|7.11 Release Notes 28.png]]</div>
 
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">556549 Enabling existing adapter functionality in the new MS Dynamics unified interface</span>'''
+
<span style="color:#008000;">'''580066 Ability to redirect emails when testing Adobe Sign eSignature on other instances'''</span><br/> As a part of the signature process, emails to signatories are triggered via Adobe Sign, starting from when the agreement is sent for signature till the agreement is signed. However, when ICM is set up on non-production environments, these emails need to be redirected (or overridden) so that real business users are not flooded with emails that require no action from them while the instances are being set up for testing purpose.
  
Microsoft has released a new unified interface for Dynamics CRM. Earlier, ICM Experience for MS Dynamics offered an iFrame based solution to embed the ICM application within MS Dynamics 365. With this release, ICM is making the iFrame fully responsive to the new unified interface, so that users have a seamless experience across various form factors.
+
<br/>  <br/> <span style="color:#008000;">'''574458 – ICM task integration to Salesforce tasks'''</span><br/> Previously, Salesforce users could manage all internal and external tasks within Salesforce itself. However, they could not manage ICM tasks from within Salesforce. &nbsp;<br/> With this release, ICM users can now:&nbsp;<br/> Manage ICM tasks from within Salesforce. The tasks created in ICM are pushed to Salesforce that allows to view the summary of the tasks with the attributes such as Task Name, Status, Priority, Due Date. &nbsp;<br/> View the task details after it is available in Salesforce.&nbsp;<br/> Configure ICM task integration with Salesforce. &nbsp;
 
+
&nbsp;
+
  
 
&nbsp;
 
&nbsp;
Line 617: Line 291:
 
== ICM Platform Tools ==
 
== ICM Platform Tools ==
  
'''<span style="color:#008000;">519481 Introducing the ICM Tools portal</span>'''
+
<span style="color:#008000;">'''588361 PToP support for ICM'''</span><br/> The 7.11 release, some enhancements were made to the Promote To Production (PToP) tool such as Vulnerability and Penetration Testing (VAPT) fixes, testing open bugs in PToP engine, some validations in the PToP engine, and an improved user interface to provide support to PToP and DevOps teams.<br/> With this release, changes have been made in ICM to support the PToP engine. This functionality, provided to administrators, can promote ICM configurations/modifications that are made to ICM configurations in pre-production environments to production environments. This tool provides support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The elastic search sync is also supported by the tool.<br/> Note: UI changes on contract type, rule set, notification template are not included.
  
With this release, ICM introduces the new ICM Tools portal for easier instance management and improved productivity. This release launches two tools—''Configuration Key'' and the ''Redis Flush'' functionality.
+
&nbsp;
  
Earlier, the ICM platform instance configuration keys were modified by the Solutions Engineering/DevOps teams, and even minor configuration changes took considerable time. The ''Configuration Key tool'' has been introduced so that a logged in user (who has access to Azure subscription) can search and update configuration keys as required.
+
<span style="color:#008000;">'''561717 – PToP support for Daimler'''</span><br/> With this release, changes have been made in ICM to support the PToP engine. This functionality, provided to Administrators, can promote ICM configurations/modifications that are made to ICM configurations in pre-production environments to production environments.<br/> This functionality:<br/> Provides AWS Support for File Copy in Auto PToP tool.<br/> Supports for movement of Security Group, User Group and Rule.&nbsp;<br/> Gets the list of entities for which ES Sync has failed when ES Sync is not successful.<br/> Provides upfront validation for Source and Target DB version mismatch before actual P2P validation process starts.<br/> Gives an option to enable DB, ES and Store backup before PToP starts which is helpful for complex PToP.<br/> Gives a validation error if the same entity is added multiple times, so that PToP does not fail.<br/> Supports saved searches.<br/> Supports User groups, Security Groups and Org Groups (which is done through manual PToP in Daimler).<br/> Supports terminated clauses and templates. This is required when a user makes a mistake, for example in language, and this already has been pushed to production.<br/> Provides validations of PToP task using a small tool in Daimler to validate names of all clauses and templates, thus helping to resolve issues in naming CSV files, naming in ICM, etc. This is checked through VBA script). Also, users may need to manually verify Is Latest which may be in an issue in environments.<br/> Note: Customers using ICM version before 7.12 need to upgrade to use this feature.<br/> &nbsp;
  
Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.
 
 
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform Role Restart on the instances to which the user has access.
 
<div class="image-green-border">[[File:7.11 Release Notes 29.png|720px|7.11 Release Notes 29.png]]</div> <div class="image-green-border">&nbsp;</div>
 
'''<span style="color:#008000;">547429 – Introducing the Translations Editor Tool</span>'''
 
 
The ICM platform is available in different languages and different languages label text are available&nbsp;for&nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.
 
 
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized. Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICM. Once the values are updated in ICM, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.
 
 
Using this tool, users can now:
 
 
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale.
 
*Update multiple language strings by selecting and saving the Resource Key value.
 
*Download and upload the localization key values using Microsoft Excel.
 
*View the modified values in the ICM instance immediately.
 
<div class="image-green-border">[[File:7.11 Release Notes 30.png|720px|7.11 Release Notes 30.png]]</div> <div class="image-green-border">&nbsp;</div>
 
'''<span style="color:#008000;">519630 – Improved ICM Health Check</span>'''
 
 
The ICM platform hosted on Azure Cloud uses services such as Elastic Search, Redis, along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ''ICM Health Check'' page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.
 
 
The ''ICM Health Check'' page has been further enhanced to cover additional parameters to help identify potential outages and diagnose issues. The health insights provide information on how well the ICM instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICM) that tracks application health alongside usage metrics and application crash data.
 
 
The health statuses are classified into three categories:
 
 
*''Warning ''- indicated by a yellow warning icon
 
*''Healthy'' -&nbsp; indicated by a green checkmark icon
 
*''Unhealthy'' - indicated by a red warning icon
 
 
The following details are displayed in the Health Check:
 
 
*'''Elastic Search Health''': displays the Status (yellow/green/red), the Elastic Search version, the Uptime, and so on.
 
*'''Redis Cache Health''': displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on.
 
*'''API Health''': displays the API Response Time, Status and Issues, and so on.
 
*'''Database Server Metrics''': displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec, and so on.
 
*'''IIS Server Metrics''': displays&nbsp;% 404 HTTP Response Sent,&nbsp;% 500 HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on.
 
<div class="image-green-border">[[File:7.11 Release Notes 31.png|720px|7.11 Release Notes 31.png]]</div> <div class="image-green-border">&nbsp;</div>
 
'''<span style="color:#008000;">553394 – Enhancement to search sync</span>'''
 
 
Previously, the ''Search Sync'' task available in ICM under ''Admin Tasks'' provided the ability to sync from the database into Elastic Search (ES) for the respective instance. For this, the ''SysId'' could be provided as input CSV file or as comma separated. However, this tool did not provide the capability to check the value stored in ES for a key using the key name. Several times, users would keep syncing the ''SysId'' assuming that the data is not updated in ES.
 
 
With this feature, users can now get data from elastic search for a given instance’s ''SysId'', so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message ''Could not fetch value for provided SysId''.
 
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time.</div>
 
 
&nbsp;
 
&nbsp;
 
  
 
== Technical Requirements for Release 7.11 ==
 
== Technical Requirements for Release 7.11 ==
Line 673: Line 303:
 
The Icertis Contract Management base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below:
 
The Icertis Contract Management base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below:
  
[[File:7.11 Release Notes Technical Requirements 001.png|720px]]
+
[[File:7.11 Release Notes Technical Requirements 001.png|720px|7.11 Release Notes Technical Requirements 001.png]]
  
[[File:7.11 Release Notes Technical Requirements 2.png|720px]]
+
[[File:7.11 Release Notes Technical Requirements 2.png|720px|7.11 Release Notes Technical Requirements 2.png]]
  
 
[[File:7.11 Release Notes Technical Requirements 03.png|720px|7.11 Release Notes Technical Requirements 03.png]]
 
[[File:7.11 Release Notes Technical Requirements 03.png|720px|7.11 Release Notes Technical Requirements 03.png]]
  
[[File:7.11 Release Notes Technical Requirements 4.png|720px]]<br/> [[File:7.11 Release Notes Technical Requirements 05.png|720px|7.11 Release Notes Technical Requirements 05.png]]
+
[[File:7.11 Release Notes Technical Requirements 4.png|720px|7.11 Release Notes Technical Requirements 4.png]]<br/> [[File:7.11 Release Notes Technical Requirements 05.png|720px|7.11 Release Notes Technical Requirements 05.png]]
  
 
&nbsp;
 
&nbsp;

Revision as of 05:32, 2 July 2020


ICM Release Notes - Release 7.12

Overview of Release 7.12

The 7.12 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICM functionalities and the user interface.

The key enhancements of this release include:

  • Enhancements to the ICM Application
    • Enhancing extended template attributes to make them searchable on the Template Index page, global search, advanced search and on the search in Icertis Experience for Word
    • Enabling Download All button for expired agreements and amendments
    • Enhancing the functionality of Associations added as tables with localization of table headers 
    • Providing localization support for clauses and templates to enable users to configure templates and create localized agreements 
    • Providing administrators the ability to add global favorites to entity detail pages 
    • Establishing the differentiation between Internal Reviewer and External Reviewer along with respective role-action mapping 
    • Introducing a Click to Sign process, whereby signatories can directly preview and accept agreements
    • Enhancing bulk creation of agreements with an option at configuration level to set the target workflow action for the agreements to be created  
    • Provisioning users to preview Approvers when swapping primary clauses for alternate clauses
    • Introducing online editing support for agreement documents to greatly improve operational efficiency for contract owners
    • Enhancing commitments functionality with an option to send reminders
    • Enhancing user experience by grouping buttons on all entities' index pages, among other major functionalities
    • Providing the flexibility to control users' actions on agreements based on their roles
    • Enhancing the agreement index page with a button which allows copying an existing agreement to create a similar agreement
    • Enhancing metadata of clauses with the ability to add details which can be leveraged in searches and defining rules
    • Extending the functionality to copy team roles for peer associations of contract requests /agreements/amendments
    • Providing users the option to clone commitments from existing ones
    • Enhancing Excel data upload functionality with validations on choice value attributes
    • Extending bulk download/upload functionality to associated documents enabling users to create line items with extended attributes or associated document attributes
    • Providing the flexibility for users to create line items using extended or associated document attributes
    • Providing users the flexibility to specify attributes for bid analysis per RFx Item and to enter value for bid analysis attributes per supplier item bid
    • Ability to have flexible contract type extension
    • Enhancing user experience by allowing resizing of popup windows
    • Supporting the trigger of rules in case of attributes which have been localized
    • Extending the number of records that can be added while adding a table as an association
    • Introducing the ability to uniquely identify records related to RFQs
    • Introducing flexibility in defining roles other than default roles provided in ICM
    • Providing support for auto-attachment functionality for agreements, amendments and contract requests
    • Enhancing associations with the ability to explicitly define the type of relationship between the association and agreement/amendment as parent, child or peer
    • Enhancing the functionality of copying associations with the flexibility to exclude attachments
    • Introducing a virus scan option for files uploaded into ICM
       
  • Enhancements to ICM API 2.0
    • Introducing some new APIs that will allow business applications to interact with ICM using standard API nomenclature for amendments, contract requests and searches
  • Enhancements to ICM Add-ins
    • Allowing users to stay on the document for further edits or reviews while publishing occurs in the background.
    • Enhancing the Word Add-in to display deviated clauses within the plugin
    • Introducing WordAI to enhance user experience by merging NegotiateAI and Icertis Experience for Word (previously known as Scribe)
    • Updating the logo for ICM Word Add-in
    • Providing users the ability to take workflow actions such as approve, reject, send for approval and others using Icertis Experience for Word
       
  • Enhancements to Artificial Intelligence Applications
    • Establishing a contract lineage using AI so that users can visualize the changes done in the clauses, attributes, team members, statuses, versions, obligations and associations over the contract negotiation process or due to various amendments and addendums added subsequently
    • Introducing a parallel view of discovered attributes against the original document
      Enhancing the in-built discovery model to discover attributes from Statement of Work agreements
    • Enhancing the discovery performance to reduce time required for discovery of documents
    • Enhancing natural language search query with support for user created attributes
  • Enhancements to Reports
    • Configuring core SSRS and Power BI reports to include contract types classified as Contracting 
    • Introducing additional support for associated documents enabling users to create custom reports in Power BI
       
  • Improving the Icertis Experience
    • Providing configurators the ability to redirect emails to specific addresses when testing Adobe electronic signature on non-production instances
    • Introducing the new eSignature platform experience
    • Enabling Electronic seal tag for signing agreement documents
    • Supporting creation of ICM entities and contracts using SAP S/4 HANA as well as supplier masterdata integration and masterdata lookup using S/4 HANA
    • Enhancing generic integration framework to support contract requests, associations, amendments
    • Enhancing Salesforce experience by providing users the ability to take request review and upload document actions from within the Salesforce grid 
    • Providing users the flexibility to manage ICM tasks from within Salesforce
    • Providing Salesforce users the ability to configure auto creation of contracts
  • Introducing ICM Platform Tools
    • Enhancing ICM support for the PToP tool to promote ICM configurations or modifications that are made to ICM configurations in pre-production environments to production environments
    • Providing support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups
    • Providing support for elastic search sync
       

These release notes provide an overview of the enhancements to ICM and the ICM experience for integrations. Refer to the technical requirements and known issues for the release in this document. Refer to the detailed Wiki documentation for the explanation and capabilities of these and all other ICM features and functionalities.

 

ICM Application Enhancements

625385 – Global Search

The previous search functionality in ICM required users to traverse through multiple pages of the search results, to locate the record they were searching for. The results were displayed in no particular order. Traversing through pages of records was an inconvenient and time-consuming process for users, especially in case of hundreds of matching result records.
Now, the ICM search functionality has been entirely revamped to provide a better, more user-friendly experience. Users can now view relevant records on the very first page of the results.
With this release:
Search results are displayed in order of relevance to the entered search query, with the best match(es) appearing as the top-most or most relevant search result(s).
On the search details page through the Advanced Search button, the search mode radio button selected by default is Metadata. In case of Global Search, the default search mode is Combined, that is, search will be performed on both Metadata as well as Full Text. The default view here is the extended view.
Document text which matches the search query is highlighted.
The search drop-down displays top 5 relevant search results. A View All Results link is displayed, clicking which opens the results details page.
Hovering over the results in the drop-down displays details about the entity 
Additional matching results are displayed below each result.
Note: The global attributes display name begin with AppSrc, so that they can be easily searched and identified.
 

551111 – Grouping of actions on index page

Earlier, the applicable set of actions available for any entity were represented using icons across ICM. For example, the agreement index page had icons for View Agreement, Preview Document and View Smart Link actions. As part of our efforts to continuously improve ICM, multiple new actions are added for an entity over time. Hence, actions are now grouped together to improve the usability and user experience.  



586165 – Support for online editing of agreements
As part of contract management, agreement and amendment documents regularly go through reviews where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature. To make changes or modifications to an agreement, ICM users previously had to download a copy, perform edits and upload it back to ICM. This created a version of the document in ICM. 
Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but also audit information was often lost, it was not possible to trace what was approved and by whom.
With this release, ICM offers online editing support for agreement documents creating radical operational efficiency for contract owners. 
It is now possible for:
•    Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session where more than one party can edit parallelly using existing MS Word capabilities. 
•    An agreement document, which has been edited using online editing, to be published to ICM without any loss of information.
Note: Only users with edit privileges on a document can participate in editing it online.

 

550178 – Enabling search for extended template metadata
Earlier in ICM, there were only predefined metadata for templates such as Name, Clause Code, Clause Group, and so on. To fulfill the requirements of some organizations, ICM provided the capability of extended template attributes to define additional custom metadata/attributes at the template level. However, users were not able to search templates based on these extended template attributes.
Now, users can search and retrieve required templates using these extended attributes as search parameters in the global search, advanced search and the template index page.

 

572767 – Ability to download all associated documents of expired agreements and amendments
Earlier in ICM, users could download all the associated documents of an agreement or amendment for all other states but not when the agreement was in the Expired state. 
This capability is now also provided for expired agreements and amendments. This considerably improves usability as users no longer need to navigate to the respective Association tab to download the required documents one by one. The Administrator can now define access permissions so that the Download All button is available for authorized users allowing them to easily download all the associated documents of agreements and amendments for reference. 



569901 – Ability to resize popup windows
Previously, popup windows within ICM had a fixed size.
Now, support has been provided for users to be able to resize the windows, thereby enhancing their ICM experience manifold. This helps users to easily read information on Lookup, Team Grid and Create Association windows.

 

551117 – Associated document content including table headers in the preferred language
Earlier in ICM, if the language preference was English and the user created an agreement using a German language template that had an association as a table, then the buyer could create the association instance and assemble the contract. However, the language for the entire assembled document would be German, but the association table header (title) would be in English. 
This functionality has been improved so that the table header also appears in the same language as the remaining text in the template. In the example above, the entire assembled document as well as the association table header would be in German.


571054 – Ability to add global favorites to entity details page
ICM Administrators can already set default favorites so that specific users can access relevant information targeted for them using global favorites. These global favorites are added to the Index page of the selected entity. With this release, this functionality is further enhanced such that the Administrators can now choose to add global favorites to the Entity Details page. 
They can set different default favorites for different entities for their users. For example, a pinned favorite search for line items can have different relevance as compared to a pinned favorite search for bids. Having default favorites pinned makes it easy for users to easily identify the actions that they need to take. Having pinned default favorite saved searches at entity level also helps the users access relevant information from within an entity, rather than at the Index page (outside the entity).
Administrators can now:
•    Choose to add global favorites to Entity Details page for specific users to view them in the associated parent or peer entity's Details page.
•    Have global favorites added by default to the corresponding selected entity's Index page.
Note: 
•    The global favorites will always be appended to the last for a user per entity type. 
•    A maximum of 4 global favorites are displayed to the user based on the security groups permissions.
•    As a user, if 4 favorites for an entity already exist, then the global favorite is added at the bottom of the saved search drop-down.

 

572768 – Display internal and external reviewer roles based on user type
The Request Review functionality in ICM allows users to request their agreements to be reviewed. Before sending an agreement for approval or signature, the contract author can leverage the Request Review option and add a user or user group as reviewer. 
Previously, if the selected reviewer is an internal user, or a user group of internal users exclusively, then the team role/user role was depicted as External Reviewer in the Team and the History tabs respectively, on the agreement Details page.   
With this release: 
•    An internal user added as a reviewer will be displayed as internal reviewer. 
•    An external user added as a reviewer will continue to be displayed as external reviewer. 
•    Administrators will be able to define actions and action display names for different entities and states for internal and external reviewer roles, respectively. 
Note: This change does not apply to Send For Review functionality as that review happens only after an agreement is executed and is applicable only for internal users.

 

551122 – Localization support for clauses and templates
Previously in ICM, there was no provision to have localization of clauses that could be used to create agreements in different languages. Hence, the users had to create multiple templates to be able to create agreements in different languages.
With this release, users can store the localized version of clauses and enable them when authoring and executing agreements. So, users can configure the template that can be used to create a localized agreement. This considerably reduces the efforts of creating and managing multiple templates to support different languages.

 

568718 – Additional Click to Sign signature option available for agreements
ICM already supports electronic and manual signatures. With this release, a Click to Sign signature process is being introduced where the signatory can preview the agreement and indicate acceptance to the terms in the agreement.  
If the signatory accepts the terms and conditions by checking the box in the Preview window, it is used to mark the agreement as accepted and signed by the signatory. The signatory also has the usual option to reject the agreement for signing, with the agreement going back to the Draft state. 
ICM Administrators who are authorized to create contract types can now add Click to Sign as an option in the signature type attribute. This would make this signature flow available for contracts of that type. 

 

574611 – Ability to swap alternate clause from Clause Comparison Report and view approvers
Previously in ICM, the substitute language of a clause was stored as an Alternate Clause to the Primary Clause. Contract authors had the provision to replace any Alternate Clause using the Clause Comparison Report. Whenever such clauses are replaced by alternate clauses, a certain set of approvers get triggered for the agreement. 
With this release, contract authors are being provided with the capability to preview the list of approvers that will be triggered due to the clause swap. 
Similarly, whenever new version of an agreement is created, the Content Control window which is now displayed now has a provision to preview the approvers that will be added or removed based on the changes made to the clause.



568773 – Ability to create and send agreements for approval during bulk creation 

ICM allows contract authors to create multiple agreements from a single agreement with the provision of copying associations and attributes as required. Previously, these agreements created in bulk would be in Draft status. In order to send the bulk created agreements for approval, users had to either do it individually for each agreement or they had to configure a Saved Search and take a bulk action on it.
With this release, this feature has been enhanced with an option at configuration level to define if these agreements are to be published, or created and sent for approval as part of the creation process. 
A choice-type attribute Target Workflow Action has been added in the existing bulk configuration masterdata contract type. Administrators can now specify whether bulk created agreements should be sent for approval or not. When the Target Workflow Action attribute is set to Create and Send for Approval and bulk agreements are generated on the model agreement: 
•    Approvers get added to the agreement’s team based on the rules configured.
•    Agreements will be sent for approval to the approver(s), and the agreement status will be updated to Waiting for Approval.
•    If no approver is present in the agreement’s team, the agreement will be approved directly and its status will be updated as Approved.
By default, the agreements would be created in Draft status. Amendments can also be sent for bulk approval using the same functionality.
Users can also decide whether the templates for bulk created agreements would be different or same than model agreement during bulk creation process. A flag Enable Template ReEvaluation is added in existing bulk configuration masterdata contract type. 
•    When Enable Template ReEvaluation flag is set to Yes, the Template Selection rules will be re-evaluated, and the first template from the list will be used for creating bulk agreements. The Template can be same or different than model agreement depending on the configured rules. 
•    When the Enable Template ReEvaluation flag is set to No, the template used for bulk created and model agreements will be same.
Any Template selection rule configured for bulk creation will not be evaluated if Enable Template ReEvaluation value is No.

550187 – Provision to send reminder notifications for commitments
ICM has the provision to track the milestones in an agreement with the Commitment functionality. Initially, to ensure that these commitments are fulfilled in timely manner, automated reminders were sent. Now, users also have the capability to send reminders at any time using the Send Reminder option and customize the notification as well as trigger reminder notifications in bulk. 



572677 – Flexibility to control the agreement actions based on role of the user
ICM already allows controlling workflow actions for a user through role action mapping. 
ICM has extended support for other agreement actions that can also be controlled based on the user role, thus improving the overall access control for a user. 
Users can now control:
•    Actions such as Compare Documents, Compare Clause Changes and Broadcast available to a user for an agreement.
•    Visibility of reports available in the agreement.
•    Creation and disassociation of associated documents from an agreement.
•    Linking and disassociation of peer association from an agreement.

 

572781 – Ability to copy existing agreement from the agreement index page
Previously, ICM supported the copy existing agreement functionality from the agreement Details page. Now, the same functionality has been added on the agreement index page for better usability. With this, the user can perform the copy action without having to navigate into the individual agreement details page.
Authorized users can now click an icon on the agreement index page to copy it to create a similar agreement. Along with the agreement, users now also have the ability to select any associated documents (parent-child or peer associations), commitments or obligations to be copied; where the Allow Copy with Association flag is set to True at the contract type level. If the association flag is set to False, a validation is displayed.

 

551116 – Support for extended clause metadata
Previously, users were not able to add more details to a clause. With this release, an entity for clause extension is being introduced which could help users in various ways, such as, when defining rules and searches.
Users can now:
•    Create contract types with defining attributes from masterdata, similar to the template/user extended entity.
•    View the clauses extended entity attributes in the clause creation wizard.
•    Configure rules using these attributes.
•    Enter the values for clause extended attributes using Add-ins.



569900 – Ability to cascade team from contract request, agreement, amendment to its association
Previously, ICM provided support to copy team role from contract request, agreement and its amendment to its parent child association. With this release, the support is being extended to copy team role from contract request, agreement or amendment to its peer associations.
A tile has been added under the configuration, where an authorized user can map all such team roles for a defined contract type to its parent-child as well as peer associations.
Administrators can now:
•    Provide the capability to copy the entire or selective team of the entity (contract request, agreement or amendment) to its peer association.
•    Copy all or selective team of the entity to its peer association on a parent or peer entity event.
Users can now:
•    Sync/update the team of association when any team is added or removed from a contract request, agreement or amendment entity.
•    Capture audit logs while copying the team from the contract request, agreement or amendment entity to its peer association.

 

574034 – Ability to have flexible contract type extension
ICM 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.
With this release, many ICM features such as lookups, saving a search, saving as a template, and so on are further enhanced to manage the extended attributes in the same way as normal attributes. This considerably improves usability and simplifies the process for users who deal with hundreds of items and need to have multiple configurations.
Users can now:
•    Configure conditional attributes, tracking attributes, computations (enable expressions) to use as extended attributes. 
•    Mark extended attributes as mandatory and validate.  
•    Control access privileges for extended attributes based on the user’s role. 
•    Maintain audits of the extended attributes. 
•    Exclude extended attributes from copy while creating an agreement by copying the existing agreement. 


551119 – Ability to copy and create existing commitments
With this release, users have been provided with the capability to copy an existing commitment and generate new commitments from it. Users can also configure attributes to be excluded from being copied automatically. This considerably reduces time and effort required to create individual commitments.

 

550181 – Rules implementation for localized masterdata attributes
Previously, localization support for masterdata attributes was limited to attributes only. If the attribute had a lookup value, its rule would not get triggered as the rule was supported only in English.
With this release, users will be able to:
•    Trigger a rule if the masterdata value has been localized on the agreement, contract request, association or the masterdata creation page. 
•    Trigger a rule if any lookup type attribute is updated using Icertis Experience for Word. 
•    Configure any rule type as all rules now have localization support.

 

551105 – Ability to use attributes to identify unique line items
Previously, RFQs and their multiple related records such as line items, rounds and awarding records were created without any associations. Users found it difficult to link RFQs to its related records.
With this release, ICM offers a provision to define an agreement code that refers to both, the RFQ attribute and the current record attribute, at the time of linking the peer association to the agreement contract type. 
Users can now:
•    Set a flag to mark the peer association as child type at contract type level which will have normal association creation workflow. 
•    Define the value of agreement code from the agreement and its related association contract type.

 

550193 – Extended number of records while adding a table as an association
ICM supports adding associations to an agreement in various forms, such as documents and tables. With this release, ICM has now extended support to 200 records that can be assembled in an Association tagged as a table. 



568776 – Export and import capability for associated documents
ICM provides a capability for bulk download (export) and upload (import) of line items from association grid using Excel. Now, users can create line items with extended attributes or associated document attributes based on the template selection and export/import through Excel into ICM.
Users can now:
•    Select and add attributes from all attributes defined in masterdata contract type.
•    Load Excel filled by the buyer (at the RFQ level) at the Round level to match the information.
•    Create, edit and delete records in bulk using Excel.
•    Manage import/ export of lookup attributes, conditional attributes, and attributes derived by computations or enabled expressions in bulk.
•    Look up attributes in the same way as masterdata is looked up using Excel.
•    Control the access privileges to import/export Excel based on the user’s role.
•    Control access privileges for attributes in Excel based on the user’s role.
•    Localize and display attributes and headers in the Excel.
•    Validate data during import/export using Excel.
•    Keep data in Excel in sync with data displayed on the user interface.
•    Make attributes non-editable.
•    Manage refreshing associations during import/export.
•    Maintain and display audit of import/export operations.
•    Generate log files for line items.


574036 – Ability to configure and control access privileges based on role
Previously, ICM users could only be assigned one of the default roles available in the system. 
With this release, ICM provides users the capability to define new roles and control access by specifying privileges depending on their business requirement. The access to the newly defined roles can be controlled using existing capabilities in ICM (such as Security Groups, Role Action Mapping, etc.). This is applicable for agreements, amendments and associated documents. 
With custom roles, users can: 
•    Control navigation pane access for agreement and associated documents. 
•    Control group access privileges and team actions. 

 

574087 – Ability to add auto-attachments as associations via event rule
As part of RFQ creation process, users need to add several documents as mandatory attachments to RFQs that may not change frequently. Previously, users had to attach multiple such documents manually to every RFQ which was a tedious and time consuming process.
ICM now has simplified the process by allowing users to attach predefined standard documents automatically to associations based on defined event rules.
Users can now:
•    Maintain a repository of standard documents in masterdata.
•    Define the mapping between associations for auto-attachments for agreements.
•    Define rules and saved search to trigger the auto-attachment process for associations.
•    Bifurcate auto-attachments from manual attachments when copying an agreement.
Note: This is applicable for agreements and amendments.



585000 – Ability to define parent-child relationship for peer associations
ICM provides the functionality to attach Associations to Agreement entities. This functionality has now been enhanced with the ability to define the type of relationship (association) as parent, child or peer.
With this release:
•    Only one parent agreement can be added to another (child) agreement.
•    If an agreement has already been associated as a child of an agreement, then another agreement cannot be added to it as a parent.
•    Amendments can be linked to agreements and vice-versa only with a peer type of relationship; parent or child type relationships are not allowed.
•    Amendments can also be associated to other amendments.
•    Only one amendment can be associated as a peer to another amendment.
•    All existing related agreements will be tagged as peer associations.
The option to define the relationship type is provided on the same window which opens up for linking/searching an agreement from the ‘+’ sign icon.

 

572764 – Ability to scan files for viruses when uploading to ICM
With this release, ICM 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 ICM against a wide variety of threats. It is applicable to the Word and Excel plugins as well.
Users can now:
•    Scan all supported file formats by default during upload.
•    Scan files in bulk.

 

645417 – Ability to create agreement with latest approved version while using Copy Agreement functionality
Previously, In ICM, when the new agreement is created by coping existing agreement using the Copy Record functionality, it is created with the same version as the original agreement. 
ICM now provides the capability to choose the latest approved version of the template of the original agreement during copy to create the new agreement.
Note: The Copy Record functionality does not change for third party paper.



572756 – Ability to exclude auto-attached documents from the copied association
ICM now allows attaching standard documents from the masterdata repository for associations automatically based on the defined event rule.
When an association with auto-attached documents is replicated by copying, there is a need to exclude auto-attached documents from the copied association. This is required to avoid duplication of association records and unnecessary upload of files into the ICM repository as the new created record will have its own auto-attached documents.
ICM provides a flag or identifier to separate associations into manual and auto-attachment associations.
Users can now:
•    Select auto-attachment associations when an agreement is sent for signature along with the bundled association.
•    Download all associations of an agreement in the ZIP format. 
 

ICM API Enhancements 

553319 – Additional APIs for amendments, contract requests and searches in ICM API 2.0

With this release, some new APIs have been introduced that will allow business applications to interact with ICM using standard API nomenclature for amendments, contract requests and searches.
These include:
Amendment APIs 
In addition to the existing APIs to create amendments, new API are provisioned to create orphan amendments in the system.
Contract Request APIs
In addition to the existing APIs to manage contract requests, new APIs have been added to support getting and adding associations in a contract request.
Search APIs
Search API have been added to allow users to query agreements and related entities across multiple contract types.
Search APIs have been added to allow creating, editing, executing and deleting saved searches.

 

Enhancements to ICM Add-ins 

619841 – Introducing Icertis Experience for WordAI
With this release, two of the ICM Add-ins - NegotiateAI and Icertis Experience for Word have been merged into Icertis Word.AI to provide users a seamless experience. 
Icertis Word.AI can be leveraged to create, edit and manage templates, clauses and agreements. 
Using Icertis Word.AI, it is now possible for: 
•    ICM Administrators to configure and setup Icertis Word.AI. 
•    Other users to work with templates, clauses and agreements. 
•    Perform different tasks such as creating, editing and deleting template variables.  
•    Tag attributes, clauses, associations, signatories and template variables.  
Note:  
•    Users can view and edit only those clauses and agreements for which they have Manage privilege in ICM.  
•    To edit an agreement, a user needs to download the agreement document and open it in Word.AI. 

 

571651 – Provision to show clause deviations in Icertis Experience for Word
Previously, users were able to view deviations in agreement clauses through the agreement details page. With this release, users can now see within the Word Add-in, any such clauses which have been tagged/added in an agreement and which are deviated. The details of the deviated clause are also displayed through Word Add-in.
With this release:
•    A list of deviations is displayed in Agreement Clauses tab for an agreement or amendment’s document version. 
•    Clauses that are added using the Add Deviation option through the Word Add-in are also displayed.
•    View information regarding the deviated clauses such as Status, Deviated By, Deviated On in the Word Add-in as well as a View in ICM link.
The deviation clauses are visible based on role action mapping as per existing ICM flow. They are searchable, so users can easily navigate to a particular clause in the agreement document and view the highlighted content of those clauses in Word Add-in.
Note: 
•    The deviation clauses are only displayed for the latest version of the agreement.
•    Users cannot perform the deviation approval flow from the Word Add-in.



487082 – Ability to take workflow actions using Icertis Experience for Word
Previously, tasks related to template and clause management could be managed using Icertis Experience for Word. However, to manage agreement related tasks, users had to switch between ICM and the Word Add-in.    
ICM now enables the users to accomplish agreement related workflow actions such as approving, rejecting or recalling an approved agreement directly using Icertis Experience for Word. This considerably reduces the turnaround time and improves the user experience. User can view the updated status of the agreements on the Versions tab, History tab and Audit Trail on the ICM Web.

 

574616 – Icertis logo updation in Icertis Experience for Word
With this release, the ICM Word Add-in logo has been replaced with the improved logo for Icertis Experience for Word.
 

 

Enhancements to Artificial Intelligence Applications in ICM

510546 – Establishing a contract lineage using AI
Contracts go through multiple transformations over a period of time. During the contract negotiations, multiple attributes and clauses get added or changed. Team members, statuses, obligations, associations also get added, updated or removed. Once the contract is executed, many addendums are added later or multiple clauses are replaced with new clauses in the amendments, etc. With such high number of transformations, it is difficult to keep track of which clause or attribute is in force. 
ICM has now improved usability by using AI so that users can now easily see the changes in the clauses, attributes, team members, statuses, versions, obligations and associations due to developments in the contract negotiation process or due to various amendments and addendums added subsequently in one go. This helps contract owners to learn from these changes and devise an optimal negotiation strategy for further engagement with customers or vendors.
Contract owners can now: 
Identify the changes done to the contract over a period of time, so that all the changes made are visible in the contract at one go. 
Visualize how the attribute values are changed over a period of time. 
Visualize how the clauses and their languages have changed over a period of time. 
Visualize how the statuses of agreements have changed over a period of time. 

 

575397 – Improved discovery based on existing customer data
ICM’s existing discovery model discovers 15 attributes and more than 40 clauses from MSA or NDA type agreement documents. 
With this release, the process of discovering attributes and clauses is improved for better accuracy by training the in-built discovery model with wide variety of agreements. ICM discovery model now discovers out-of-the-box attributes from SOW type of agreements. 
The existing ObligationAI approach, which was model based, is now replaced by AI and Rule-based approach to discover obligations more accurately.
Contract negotiators can now: 
Identify clauses and attributes from multiple MSA, NDA, IT MSA, SOW contract types more accurately and automatically using DiscoverAI and NegotiateAI apps. 
Identify obligations from MSA, NDA and SOW contract types more accurately and automatically with ObligationAI.
Select a discovery model specific to contract types to discover attributes and clauses with better accuracy as compared to other models.


575399 – UX revamp to display discovered attributes and original document side-by-side
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.
With this release, when contract negotiators trigger the discovery process, they can view the progress of AI discovery on the agreement Details page. They will be able to view:
The progress of all four discovery processes.
The percentage of discovery process completed for each of discovery process and the overall discovery process.
The approximate time it would take to complete the individual discovery process and the overall discovery process.
Contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, etc. are displayed along with the agreement document. An option is now available to launch side-by-side view of the document along with the discovered entities. Using this option, users can view different sections for discovered clauses, attributes, tables and obligations. 
Contract negotiators also have an option to search within the agreement document. The results are highlighted to the user and a count is displayed. Users can also save any changes made in the individual discovery sections.

 

575455 – Ability to process multiple documents simultaneously during the discovery process
Previously, upon receiving multiple requests, the AI discovery model added them in a queue form and processed each document individually. With this release, the discovery performance has been enhanced such that multiple documents can be processed simultaneously and within lesser time.
Users can now start the discovery process for their document without waiting for other discovery processes to complete. A total of 20 documents can now be processed in parallel.
The duration for a document discovery to be completed depends on the number of pages in a document. For example, discovery process for a .docx file with 10 pages and 1 table will take 120 seconds to complete; whereas one with 500 pages and 15 tables will take 1800 seconds.

 

602198 – Support for user created attributes in NLP search
Previously, the ICM AI enabled mode of searching allowed users to search agreements using a spoken language statement. With this release, the functionality has been enhanced to support user defined attributes as well. For example, queries such as “contract value above 20000 USD”, “contract value below 20000 USD”, “contract value between 20000 USD and 2000000 USD” and so on, can be entered to search contracts of a certain value.
 

Enhancements to Reports

570314 – All core SSRS reports to only include contract types classified as Contracting
ICM offers the functionality to classify Business Type/ Contracting agreement type at contract type level. With this release, core reports will be limited to Contracting business application type.
Users with access to standard and insights reports will only be able to see data related to agreements with Contracting business application type. Thus, the reporting data would not contain any sourcing agreements.
This is applicable to the following reports:
Agreement Clause Content Report 
Agreement Deviation Report
Agreements Pending Approval Report
Agreements Pending Execution Report
Average Agreement Turn Around Time Report
Clauses Pending Approval Report
Expiring Agreements Report
Templates Pending Approval Report
Cycle Time Report 
Detailed Report 
Attribute Value Report 
Template Clause Report 
Clause Profiling Report 
Clause Deviations Report
Expired Agreements Report 
Approved Requests Waiting For Contract Creation Report
Signature Type Report 
CLM Activity Report 
Clause Insights Report
Deviation Insights Report



606134 – All Power BI Reports to only include contract types classified as Contracting
Users with access to Power BI dashboards will now only see data of agreements with business application type as Contracting while accessing the Business Summary, Legal Summary and Legal Details reports.
Since the Custom report is common to sourcing and contracting, having a filter which is configurable makes the experience more user-friendly than only restricting the create report for contracting use cases only.

 

567137 – Ability to add datasets for associated documents in Power BI for obligation and management
In order to have a comprehensive view of the state of obligation compliance users needed to have self-serve ways to build reports and dashboards. Users have now been given the flexibility to build reports on obligation compliance across hierarches – from agreements and obligations to fulfillments and fulfillment evidences. 
With this release, users have the option for slice and dice for viewing and narrowing down to the right type of Obligations for any given context. Advanced Analytics with Power BI is the ICM offering to let customers create and view custom reports. Users will now have OM application datasets for Agreement, Obligation and Fulfillment entities in the Power BI data model as well. 
With the additional data sets, users will be able to generate reports on Power BI such as for:
The aggregate fulfillment status for a given obligation, especially for recurring fulfillments.
Number of days it took for a fulfillment cycle, which is for an obligation or fulfillment to move from created to approved state.


657965 – Support for Service Principal Authentication method for Power BI
ICM has now extended support for Service Principal Authentication method to authenticate Power BI resources for Advanced Analytics. It has been implemented as the default method of Power BI authentication for improved security. However, the option to continue with the current authentication method of using user credentials for Power BI is still available.

 

573000 – Sub-role included in Detailed and User Profiling Reports
ICM provides the ability to define sub-roles for the Approver role. With this, all the capabilities of the Approver are enabled for users at the sub-role level. This capability has now been extended to reports so that users can have relevant information and make informed decisions. 
With this release, the Detailed Report, User Profiling Report and Agreements Pending Approval Report have now been modified to display the Approver sub-roles such as Contract Admin, Legal Approver and others.

 

573621 - Enhancement to reports processing error message
Previously, when viewing reports resulted in processing errors, the No data available message was displayed. This message has now been modified for clarity, as follows:
An error occurred during report processing, if the issue persist kindly contact customer support team.

 

601540 - Unavailability of Template Clause Report as Dashboard KPI
With this release, the Template Clause Report has been deprecated from the Dashboard KPIs. However, it will still be accessible from the Reports tile.

 

Integrations

541825 – Integration with the new eSignature platform   
With this release, customers can now use Namirial eSignAnyWhere as their electronic signature platform to send the agreements electronically for signatures to internal and external signatories. The invited signatories receive an email notification with a link to the document to review and sign or decline to sign or to delegate the action. The agreement will be executed once the document is signed electronically by all the involved signatories.   
Contract administrators can track the status of the agreements sent for signature within ICM. They can also recall the agreement sent for signature, if it was not signed by all parties.
569172 – Enabling Electronic seal tag for signing agreement documents   
Previously, users were able to sign agreements based on signature tags present in the agreement templates.   
With this release, ICM has extended the support for enabling electronic seal tags in templates that will be used for marking electronic seals during the signature process using DocuSign. The support of electronic seals will help the organization’s legal teams to certify the integrity and the origin of the contracts.

 

579067 – Ability to support additional electronic signature platforms
Just like support has been extended to Namirial eSignAnyWhere in addition to DocuSign and Adobe Sign for electronic signatures, ICM has enhanced adaptability by making it possible to implement and integrate any other electronic signature provider as well based on customer requirements.

 

572516 – SAP S/4 Supplier masterdata integration  
The Icertis Experience for SAP S/4 HANA allows users to search, display and select S/4 HANA masterdata required for completing the contracting process within ICM.
The ICM Experience for S/4 HANA adapter:
Allows periodic data sync between S/4 HANA masterdata and ICM masterdata tables.
Can be configured such that ICM Admin ca configure the data sync jobs and the related entity mappings.
Is agnostic to masterdata entity i.e. it is generic enough to support any masterdata that the customer would like to sync from S/4 HANA into ICM to complete contracting business process. 
Some key use cases that customers should be able to configure the adapter to include:
Supplier master data from S/4 HANA to ICM.
Material/Items master data from S/4 HANA to ICM.
Payment master (Terms, Types) from S/4 HANA to ICM.

 

572517 – SAP S/4 HANA masterdata lookup 
With this release, ICM and ICM business applications (Sourcing and Obligation Management) have been integrated with SAP S/4 HANA to render masterdata lookup from SAP S/4 HANA.



573373 – Generic integration framework to support contract requests via ASB
Previously, ICM supported a generic ASB adapter for inbound and outbound integration for Agreements. With this release, support is provided for creating contract requests for agreements. Users will now be able to create and update Contract Requests in ICM using an external application.

 

573377 – Generic integration framework to support associations via ASB
Previously, ICM supported a generic ASB adapter for inbound and outbound integration only for agreements. With this release, support is provided for creating contract requests for the agreements. Users will now be able to create and update contract requests in ICM using an external application.  
The ASB adapter will pick the JSON payload from the message queue and create associations to an existing agreement or RFx record in ICM. Users will thus be able to manage purchase requisitions, purchase orders, sourcing events and similar tasks by sending associated data.  

 

573379 – Generic integration framework to support amendments via ASB
Contract amendments are an integral part of business flow and the support for amendment integration is critical for businesses. With this release, the generic integrations ASB adapter will be able to update amendments to an agreement on the created, updated, approved and executed actions. 

 

594454 – Additional connector support for JSON file format
Previously CSV files were supported for masterdata upload using ASB and SFTP, while text based files were supported for uploads using SFTP. 
With this release, the file based integration will additionally support JSON file format, while also supporting blob connectors.

 

554864/554868 – Support for request review and upload actions in Salesforce grid
Previously, ICM users could manage and execute contract management tasks using Salesforce Classic and Lightning user interface. The Icertis Experience for Salesforce introduced support for the following actions at the grid level: Assemble, Download and Send for Approval. 
With this release, support has been extended for the Send for Review and Upload document actions, thus considerably improving usability.  The action buttons displayed on the user interface are based on the privileges assigned to the user via role action mapping in ICM . The agreement can be sent for review to multiple users by selecting the users from the available list.
Note: If a user wants to view or edit a contract record, they will still have to double-click the contract record which will open the contract Details page in Salesforce. 

 

537774 – Ability to create contracts based on Opportunity or Quote
Previously, users could only manage contracts using the Icertis Experience for Salesforce. They did not have the option to automatically initiate a contract based on an Opportunity or Quote status. 
With this release, the contract creation process has been automated based on opportunity or quote status, will increase the productivity of sales users.
Sales admin users can now:
Configure the opportunity or quote status which can automatically trigger the contract creation.
Configure the contract type which should be used to create the contract based on data from an Opportunity or Quote.
Define the Type of Paper to be used as Own or Third Party.
Configure automated contract creation or manual contract creation by creating a task for the opportunity (for which a contract needs to be created). 
If there is a task to manually create a contract, Sales users will be able to create a contract using a single button click that will assemble all necessary documents for the type of contract to be created i.e. follow the same steps as above.
For auto creation of contracts, the ICM for Salesforce will determine the dependencies for the contract. For example, if the opportunity is for an extension, the existing master agreement for the account will be identified and an appropriate contract type such as an order form will be selected and associated with it.
Additionally, Salesforce users will receive a Task and/or Chatter notification whenever a contract is automatically created.

 

580066 – Ability to redirect emails when testing Adobe Sign eSignature on other instances
As a part of the signature process, emails to signatories are triggered via Adobe Sign, starting from when the agreement is sent for signature till the agreement is signed. However, when ICM is set up on non-production environments, these emails need to be redirected (or overridden) so that real business users are not flooded with emails that require no action from them while the instances are being set up for testing purpose.



574458 – ICM task integration to Salesforce tasks
Previously, Salesforce users could manage all internal and external tasks within Salesforce itself. However, they could not manage ICM tasks from within Salesforce.  
With this release, ICM users can now: 
Manage ICM tasks from within Salesforce. The tasks created in ICM are pushed to Salesforce that allows to view the summary of the tasks with the attributes such as Task Name, Status, Priority, Due Date.  
View the task details after it is available in Salesforce. 
Configure ICM task integration with Salesforce.  

 

ICM Platform Tools

588361 – PToP support for ICM
The 7.11 release, some enhancements were made to the Promote To Production (PToP) tool such as Vulnerability and Penetration Testing (VAPT) fixes, testing open bugs in PToP engine, some validations in the PToP engine, and an improved user interface to provide support to PToP and DevOps teams.
With this release, changes have been made in ICM to support the PToP engine. This functionality, provided to administrators, can promote ICM configurations/modifications that are made to ICM configurations in pre-production environments to production environments. This tool provides support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The elastic search sync is also supported by the tool.
Note: UI changes on contract type, rule set, notification template are not included.

 

561717 – PToP support for Daimler
With this release, changes have been made in ICM to support the PToP engine. This functionality, provided to Administrators, can promote ICM configurations/modifications that are made to ICM configurations in pre-production environments to production environments.
This functionality:
Provides AWS Support for File Copy in Auto PToP tool.
Supports for movement of Security Group, User Group and Rule. 
Gets the list of entities for which ES Sync has failed when ES Sync is not successful.
Provides upfront validation for Source and Target DB version mismatch before actual P2P validation process starts.
Gives an option to enable DB, ES and Store backup before PToP starts which is helpful for complex PToP.
Gives a validation error if the same entity is added multiple times, so that PToP does not fail.
Supports saved searches.
Supports User groups, Security Groups and Org Groups (which is done through manual PToP in Daimler).
Supports terminated clauses and templates. This is required when a user makes a mistake, for example in language, and this already has been pushed to production.
Provides validations of PToP task using a small tool in Daimler to validate names of all clauses and templates, thus helping to resolve issues in naming CSV files, naming in ICM, etc. This is checked through VBA script). Also, users may need to manually verify Is Latest which may be in an issue in environments.
Note: Customers using ICM version before 7.12 need to upgrade to use this feature.
 

 

Technical Requirements for Release 7.11

The Icertis Contract Management base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below:

7.11 Release Notes Technical Requirements 001.png

7.11 Release Notes Technical Requirements 2.png

7.11 Release Notes Technical Requirements 03.png

7.11 Release Notes Technical Requirements 4.png
7.11 Release Notes Technical Requirements 05.png

 

 

 

Known Issues for Release 7.11

480546 – Loading issues when Require SSL set to True and Client certificates enabled as Accept

When the following settings are enabled on the environment - Require SSL to True and Client certificates is enabled as Accept (instead of Ignore) in IIS for API site, office.JS Word Add-In does not load in Internet Explorer. This issue occurs when using Internet Explorer, Windows 10 version < 1903 and Office version < 16.0.11629. 

7.11 Release Notes Known Issues 1.png
 
Note: On MAC OS, this issue is not applicable.

Workaround 

The two workarounds available for the issue: 
It is recommended to Upgrade Windows 10 version > = 1903 and Office 365 version > = 16.0.11629 by end user.
Change IIS setting For API site to SSL Settings -> Uncheck Required SSL and Client certificates to Ignore.

579215 – Lookup filtering not working when configured on multi-select lookup string attribute  
This is with reference to the new feature 541976 – Ability to configure and apply multiple filters while referring value from any master records (in ICM Application Enhancements), developed in 7.11.

While defining the lookup filter, if the source and target are multi-select string lookup and dynamic filter is configured for target attribute, the filtering will not work. No values will be displayed for target attribute in drop-down as well as the lookup popup.

Workaround

Currently, there is no workaround for this defect. However, it has been found that there is no strong business use case yet that required such configuration.


589456 – In agreement Versions tab, Content Control Difference panel not displaying the association-updated record if association document is created/modified under peer association  

This is with reference to the new feature 488577 – Document upload validation displays the changes in associations tagged as file(s) (in ICM Application Enhancements), developed in 7.11. 
In the agreement Versions tab, Content Control Difference panel is not displaying association updated record if peer association is tagged as file where peer associated document contains saved search as table, association as table, association as file tags. This behavior is also for document assembly and upload scenario Content Control Difference popup.

Workaround

To compare the differences, the user can download the comparison document of the parent agreement and review the changes.

597869 – In office.JS Word Add-In, Clause preview not displaying in MS Edge browser as default view on Mac  

In office.JS Word Add-In, Clause preview is not displayed in Microsoft Edge browser as default view on Mac OS.

Workaround 

User can navigate to ICM to see preview of the respective clauses.