From ICIHelp7.14
Jump to: navigation, search
 
(134 intermediate revisions by 4 users not shown)
Line 1: Line 1:
  
= ICM Release Notes - Release 7.11 =
+
= ICI Release Notes - Release 7.14 =
  
 +
== Overview of Release 7.14 ==
  
 
+
The 7.14 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICI functionalities and the user interface.
== Overview of Release 7.11 ==
+
 
+
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.
+
  
 
The key enhancements of this release include:
 
The key enhancements of this release include:
  
*'''Enhancements to Business Applications'''
+
*<span style="color:#008000;">'''Enhancements to the ICI Application'''</span>  
**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.
+
**Extending support of multiple rulesets for event rules, for any entity, per event.
+
**Locking business rules that were critical to the flow of the application are now locked by the service users when deploying the Obligation Management application preventing other users to unlock, edit and modify these rules, thus ensuring a smooth workflow.&nbsp;  
+
*'''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 the ICM dashboard to provide a framework for configuring a new dashboard layout, and provide support for a widget for all the Saved Search, Task List and My Recent activities widgets. In addition, the support is also extended to use the earlier KPI based dashboard, resize the widget, and re-order the widget sequence.
+
**Introducing a Pre-Publish Checker tool on the User Administration tile that will analyze all the checkpoints which potentially result in downtime and provides failure information to the configurators, thus allowing users to take appropriate actions.
+
**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.
+
**Allowing users to define the order for associations and assemble them as per the defined order.
+
**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.
+
**Enabling users to apply multiple filters while referring value from any master records. These filters can either be predefined or can even be based on the attribute values that are being selected as the user enters the details.
+
**Allowing configuration of a flexible entity which enables users dealing with different types of items (such as line items in sourcing) to define and create entities based on business requirements.
+
**Enabling users to create multiple agreements from a single agreement by flagging the Bulk Agreement option to ''On'' at the contract type level.
+
**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.
+
**Allowing filtering out agreements while inheriting.
+
**Allowing the contract type description to be available when creating the contract type instance, so that users can easily identify the type of contract type that fulfills the requirement.
+
**Providing the ability to exclude attributes or associated documents when copying agreements and allowing the copying of commitments when copying the RFQ/Agreement.
+
**Providing the flexibility to configure role for commitment business owner while adding the user to the team, and configure reminder notifications on date parameters.
+
**Auto-populating the currency while creating entities, retaining the original file name of the uploaded files in ICM, updating the count of entities without refreshing the page.
+
**Allowing replacing of the alternate clause from the Clause Comparison Report, allowing download-upload validation to display the clause deviations as well as the changes included in associations assembled in the document, displaying clause comparison on the first version of the agreement, enhancing KPI reports performance.
+
**Allowing copy team role mapping by copying team from the contract request, agreement, amendment to its association, capturing the rule condition based on which a user has been added to the team, generating a redlined version for comparing agreement versions, providing Administrators the ability pin the necessary saved searches for external users/suppliers. 
+
*'''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. 
+
*'''Enhancements to ICM Add-ins''' <ul style="list-style-type:circle;">
+
</ul>  </ul>
+
  
*Allowing users to stay on the document for further edits or reviews while publishing is happening in the background.  
+
*'''''User Experience'''''
 +
**Introducing a horizontal chevron which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron, namely Generate, Approve, Execute and Manage, prominently communicate an entity’s journey including the previous, current and possible future states of the agreement.
 +
**Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement.
 +
**Facilitating one-click navigation from the ICI record to any related entities (multi-hierarchy level). For example, from RFx to Bid Response which would otherwise require multiple clicks.
 +
**Providing administrators the ability to configure access control for users who are not part of the team to sections or sub-sections in the left navigation pane at the contract type level.
 +
**Enhancing document usability by placing content control tags such that the end-user no longer views separate lines in the assembled document for assembled clauses that are not evaluated. 
 +
*'''''Workflow Enhancements'''''
 +
**Displaying the organization unit path of the parent document by default as the path for the associated document, so that both parent and child documents have the same organization path at the time of creation and updation.
 +
**Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle.
 +
**Providing the ability to add amendments to expired agreements. &nbsp;
 +
**Adding a time zone attribute to provide enterprise organizations the flexibility to track the time zone or region-based activities as needed for the instance of the agreement.
 +
**Providing the capability to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications and allowing configuration of the sender’s email ID dynamically based on the specific contract type or instance of the record.&nbsp; 
  
*'''Enhancements to Artificial Intelligence Applications''' <ul style="list-style-type:circle;">
+
*<span style="color:#008000;">'''Mobile App Updates'''</span>  
<li>Introducing eDiscovery to derive critical insights by analyzing legacy contracts.</li>
+
**Improving the usability of the mobile app by refreshing the agreement or requests list automatically after an approve, reject or request review action is performed.  
<li>Introducing ''Risk AI'' 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.</li>
+
<li>Improved accuracy of AI models by incorporating user action feedback when the user is interacting with the attribute discovery in ''DiscoverAI'' and ''NegotiateAI'' apps.</li>
+
<li>Identifying important terms in contracts (contract highlights) using AI for different personas like legal, CxOs, finance, etc.</li>
+
<li>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.</li>
+
<li>Introducing NLP-based search query for Agreement entities.</li>
+
</ul>  <li>'''Enhancements to Reports'''
+
*Introducing the Obligations Management Dashboard 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 and Fulfilments overdue by the owner, and the OMH – Obligation Management Health Report that provides an overall view of the total Fulfillments across all agreements that are fulfilled. </li>
+
  
 +
*<span style="color:#008000;">'''Enhancements to ICI API 2.0'''</span>
 +
**Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata. 
  
*'''Improving the Icertis Experience ''' <ul style="list-style-type:circle;">
+
*<span style="color:#008000;">'''Enhancements to ICI Add-ins'''</span>  
</ul>  </ul>
+
**''Icertis Experience for Word''
 +
***Displaying a set of 30 clauses per page with pagination for easy navigation between clauses listed on the clauses, clauses in templates and clauses in agreement pages.
 +
***Providing extended attributes within the add-in for creation and modification of clauses and templates.
 +
***Allowing the deviation approver to view and directly approve or reject clause deviations in an agreement from within the add-in.
 +
***Displaying a validation message in clause content control enabling users to insert and tag clauses at the correct location in the document before publishing it. 
 +
**''Outlook Add-in''
 +
***Enhancing the Outlook Add-in by providing the ability to upload email in .docx or .msg format as associated documents for an agreement from within Outlook.   
  
*Building the Secure File Transfer Protocol (SFTP) adapter 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.&nbsp;
+
*<span style="color:#008000;">'''Enhancements to Artificial Intelligence Applications'''</span>
*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 a legal playbook in the NegotiateAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.  
*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.
+
**Enhancing DiscoverAI to identify the different levels within a clause through a distinct visual representation of clauses with sub-sections displayed in a delineated view during the clause discovery process.  
*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.  
+
**Enhancing the ICI discovery models to support clause and obligation discovery for additional languages such as German, Spanish and Portuguese.  
*Enhancing the SFDC experience by providing user the ability to search for contracts or contract requests from a common page depending on the selection criteria.  
+
**Improving the inbuilt DiscoverAI model to identify additional attributes such as City, State, Zip Code, and so on.  
*Providing the ''Reports'' tile within Salesforce so that users can view and execute custom and default reports, thus simplifying tasks and improving productivity.  
+
*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.  
+
  
*'''Introducing ICM Platform Tools''' <ul style="list-style-type:circle;">
+
*<span style="color:#008000;">'''Enhancements to Reports'''</span>  
<li>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.</li>
+
**Introducing the Risk Assessment Report which is a trendline chart report that depicts the agreement aggregate risk score by their version. ICI’s AI algorithm identifies the playbook exceptions for a new version.  
<li>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.</li>
+
**Introducing the Clause Summary Report to help clause administrators to understand and assess the impact of changes made to a clause.  
<li>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.</li>
+
**Providing users the capability to generate a report as per the time zone of their choice from within the report itself.  
<li>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.</li>
+
</ul>  </ul>
+
  
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.
+
*<span style="color:#008000;">'''Improving the Icertis Experience'''</span>
 +
**Extending support for ICI dashboard widgets in the Icertis Experience for Salesforce Home page, so that users can perform all necessary actions from within Salesforce itself.  
 +
**Supporting auto-renewal and reset expiry functionalities in Icertis Experience for Workday, thus saving time and avoiding data duplication.  
 +
**Enhancing the generic integration framework to support custom pre- and post-processing hooks to considerably reduce implementation time, and allowing users to define and configure folder structure and file names as per the business requirement.  
  
 +
*<span style="color:#008000;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>
 +
**In release 7.12, the Software Development Kit (SDK) was released to support partners for technical configuration. With this release, documentation for ICI coding guidelines, ICI developer methods, local environment setup using ICI binaries, and ICI customization and use cases are also available. 
  
== Icertis Business Applications ==
+
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.
  
'''<span style="color:#008000;">448830&nbsp;– Integrating ObligationAI with Obligation Management app&nbsp;</span>'''
 
 
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.
 
 
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:
 
 
*Reducing time and efforts to discover and create obligations.
 
*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.
 
<div class="image-green-border">[[File:7.11 Release Notes 01.png|720px]]</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.
 
 
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.
 
<div class="note-box">'''Note''': ICM will now support platform and business applications with same version number.</div>
 
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">545742 – Extending support of multiple rulesets for event rules</span>'''
+
<span style="color: rgb(0, 119, 235); font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</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.
+
<span style="color:#008000;">'''659853 – Upfront chevron view of agreement journey'''</span>
  
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.
+
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&nbsp;
<div class="image-green-border">[[File:7.11 Release Notes 02.png|720px]]</div>
+
With this release, an Administrator can now:
+
  
*Create multiple rulesets for event rules, for any entity, per event.
+
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&nbsp;
*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.
+
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.
<div class="image-green-border">[[File:7.11 Release Notes 03.png|720px]]</div>
+
The ''Stop Processing More Rules ''option when selected as ''Yes ''allows users to stop evaluating the rules within the ruleset.
+
  
&nbsp;
+
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.
  
'''<span style="color:#008000;">545763 – Non-editable seeded business rules</span>'''
+
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:
  
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.
+
1.&nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.
  
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.
+
2.'''Approve:'''&nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&nbsp;
<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]]</div>
+
  
== ICM Application Enhancements ==
+
3. '''Execute:&nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.
  
'''<span style="color:#008000;">532684 – Navigation Enhancements</span>'''
+
4. '''Manage:&nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.
  
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.
+
'''Note''':&nbsp;
  
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.
+
*The chevron view is only applicable to agreement contract type (agreement&nbsp;and amendment).  
 +
*By default, the chevron is disabled; it can be enabled for selected contract types.
 +
*The chevron labels support localization.
 +
<div class="image-green-border">[[File:7.14 release note 1.png|720px|7.14 release note 1.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''<span style="color:#008000;">512931 – Visibility of sections on the left navigation pane to non-team users</span>'''
  
'''Note:'''
+
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&nbsp;
  
*Users can now navigate from any page in ICM to any other page, thus eliminating the need for multiple page loads.
+
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.<br/> &nbsp;
*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.  
+
  
'''<span style="color:#008000;">546019 ICM Dashboard Enhancements</span>'''
+
<span style="color:#008000;">'''659725 Ability to easily navigate to related entities in multi-level hierarchy'''</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.
+
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.
 +
<div class="image-green-border">Configurators can:&nbsp;</div>
 +
*Configure a smart link across any ICI entity that defines the entity relationships.  
 +
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities.  
  
The widget-based dashboard offers the following widgets:
+
Users can:&nbsp;
 
+
*'''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.
+
 
+
'''<span style="color:#008000;">519472 – Introducing the Pre-Publish Checker Tool</span>'''&nbsp;
+
 
+
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.
+
 
+
'''Note''': If no errors are identified, publish process continues normally.
+
 
+
'''<span style="color:#008000;">541970 –&nbsp;Assembly of associated documents into the main agreement based on a defined order</span>'''
+
 
+
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.
+
 
+
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.
+
 
+
'''Note:''' If saved search is not configured or not tagged along with the association, ICM behaves as-is.
+
  
 +
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp;
 +
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results.
 +
<div class="image-green-border">[[File:7.14 release note 2.png|720px|7.14 release note 2.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.</div> <div class="image-green-border"><br/> For example, consider&nbsp;entities related in multi-level hierarchy as ''Agreement > Obligations > Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.</div> <div class="image-green-border"><br/> [[File:7.14 release note 3.png|720px|7.14 release note 3.png]]</div>
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">476165 PToP tool enhancements</span>'''
+
'''<span style="color:#008000;">584439 Introducing the Contract Manager role for agreements&nbsp;</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.
+
 
+
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;
+
 
+
'''<span style="color:#008000;">541976 – Ability to configure and apply multiple filters while referring value from master records</span>'''
+
 
+
Earlier, ICM provided the capability of filtering records on the basis of a single attribute using cascading.
+
 
+
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.
+
 
+
Users can now:
+
 
+
*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.
+
 
+
'''<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.
+
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.
*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>'''
+
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&nbsp;
  
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.
+
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.
  
Users now:
+
With this release:&nbsp;
  
*Have complete flexibility at configuration level to define the applicable contract type, decision attribute, compute attribute for bulk agreement creation.  
+
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&nbsp;''action.  
*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.  
+
*Only one contract manager is available inside the agreement at any given point of time.
*Can access model agreements only through technically configured Admin saved search. &nbsp;
+
*The contract manager will have provisions same as that of primary owner.
 +
*The contract manager name is displayed on the agreement summary page.  
 +
*Agreements can be searched using the contract manager name.
 +
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user.  
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">541982 – Ability to support approver sub-roles</span>'''
+
<span style="color:#008000;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>
  
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. This can be achieved through a technical configuration.
+
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&nbsp;
  
'''<span style="color:#008000;">541979 – Ability to filter agreements available for inheritance</span>'''
+
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.
 
+
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.
+
 
+
This is achieved through a technical configuration at the contract type level.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">549081 Availability of contract type description during contract type instance creation</span>'''
+
<span style="color:#008000;">'''732038 Ability to use parent’s Organization Unit path when creating associated document'''</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;
+
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.
  
'''<span style="color:#008000;">551098/551099/551100 – Enhancements when copying agreements</span>'''
+
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&nbsp;
 +
<div class="image-green-border">[[File:7.14 release note 6.png|720px|7.14 release note 6.png]]</div>
 +
For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.
 +
<div class="image-green-border">[[File:7.14 release note 7.png|720px|7.14 release note 7.png]]</div>  
 +
This is applicable to the following associations:&nbsp;
  
ICM has improved the usability when copying agreements by allowing the users to:
+
*Import of Association (Line Item)
 +
*Auto Attachment Association
 +
*Obligation/ Fulfillment (Association of Association)
  
*Exclude associated documents from getting copied.
+
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.
*Exclude the attributes of selected associated documents.
+
*Select and copy Commitments.&nbsp;
+
*Exclude the attributes of selected Commitments.
+
 
+
'''Note''': The exclusions above are achieved through a technical configuration at the contract type level.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">551101 – Ability to configure role for commitment when adding user to the team</span>'''
+
<span style="color:#008000;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>
  
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.).
+
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.
  
'''Note''': This is achieved through a technical configuration at the contract type level.
+
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&nbsp;
  
'''<span style="color:#008000;">466694 – Ability to configure reminder notifications on entities</span>'''
+
Users can now:&nbsp;
  
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.
+
*Capture multiple valid internal or external email addresses while working on agreements/ requests.  
 
+
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.  
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, user 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.
+
 
+
'''<span style="color:#008000;">551103 – Auto-populating the currency when creating entities</span>'''
+
 
+
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''Preferred Currency'' option in ''My Preferences''. Based on the user preference, the selected currency will be auto-populated for any Currency attribute.
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">551104 – Ability to retain original filename of uploaded files</span>'''
+
<span style="color:#008000;">'''583186 – Ability to add amendment on expired agreement'''</span>
  
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.
+
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.
  
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 achieved through a technical configuration and applicable to agreements, amendments, associations, and file attributes in agreements/associations.
+
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&nbsp;
  
'''<span style="color:#008000;">560477 Automatic update of entity count on navigation pane without refresh</span>'''
+
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.
 +
<div class="image-green-border">[[File:7.14 release note 8.png|720px|7.14 release note 8.png]]<br/>  </div>
 +
<span style="color:#008000;">'''593928 Ability to configure sender email ID for automated emails'''</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.
+
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.
  
&nbsp;
+
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&nbsp;
  
'''<span style="color:#008000;">488574 &nbsp;– Replace primary clauses with alternate clauses from Clause Comparison Report</span>'''
+
Administrators can now:
  
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.
+
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement.  
 +
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to.  
 +
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses.
 +
<div class="image-green-border">[[File:7.14 release note 9.png|720px|7.14 release note 9.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''<span style="color:#008000;">593938&nbsp;– Time Zone support for date-dependent automated processes</span>'''
  
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.
+
In ICI, there are scheduled jobs that perform certain actions on&nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.
  
Users can:
+
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.
  
*View the ''Select Alternate Clause'' link in the Clause Comparison Report.
+
With this release:
*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.
+
  
'''<span style="color:#008000;">488577 – Document upload validation shows the changes in associations tagged as file(s)</span>'''
+
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination).
 +
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities.
 +
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance.
 +
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance.
 +
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date.
  
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.
+
'''Note''':&nbsp;The time zone-based processing can be enabled for all contract types across&nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.
 +
<div class="image-green-border">[[File:7.14 release note 10.png|720px|7.14 release note 10.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''<span style="color:#008000;">512930 – Triggering service bus events for all actions</span>'''
  
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;
+
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&nbsp;
  
The following actions take place as soon as a new agreement version is uploaded:
+
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&nbsp;
  
*The version being uploaded is compared with the latest version available in ICM.
+
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.<br/> &nbsp;
*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. The support for the same can be extended through a technical configuration.
+
<span style="color:#008000;">'''545126 – Availability of business status value in ICI event messages'''</span>
  
'''<span style="color:#008000;">535845 – Ability to identify the first version of an agreement in the Clause Comparison Report</span>'''
+
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.
  
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.
+
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.
  
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.
+
== Mobile App Updates ==
  
&nbsp;
+
'''<span style="color:#008000;">660965 – Refresh agreement list on approval</span>'''
  
'''<span style="color:#008000;">467201 – Ability to copy team role from contract request, agreement, and amendment to its association</span>'''
+
Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically.&nbsp;
  
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.
+
In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.
 +
<div class="image-green-border">[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]<br/> &nbsp;</div>
 +
== ICI API Enhancements&nbsp; ==
 +
<div class="image-green-border">
 +
<span style="color:#008000;">'''607867 – ICI API 2.0 Implementation'''</span>
  
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.
+
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.
  
Users can now:
+
Enhancements include:
  
*Copy the entire team of the entity (''Contract Request, Agreement, Amendmen''t) to its defined Association entity on a specific role (such as ''Observer)''.
+
*Addition of Masterdata APIs&nbsp;
*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'').
+
**Users can now update the masterdata instance
*Copy the entire team from the entity (''Contract Request, Agreement, Amendment'') to the association on predefined event.
+
**UserName field is returned in Get Team API as part of the response.  
*Get an Audit log while copying the team from the agreement to its respective association.  
+
  
&nbsp;
+
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well.
 +
</div>
 +
== Enhancements to ICI Add-ins&nbsp; ==
  
'''<span style="color:#008000;">560209 User inclusion condition visibility in team</span>'''
+
<span style="color:#008000;">'''714872 Improved document usability'''</span>
  
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.
+
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&nbsp;
  
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.'' 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.
+
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.
  
'''<span style="color:#008000;">560216 – Generate a redline version for document comparison</span>'''
+
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.
 +
<div class="image-green-border">[[File:7.14 release note 4.png|720px|7.14 release note 4.png]]</div> <div class="image-green-border">&nbsp;</div>  
 +
With this release:
  
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.
+
*All the content controls are put together in a single paragraph on any line with valid content.
 +
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.
 +
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules.  
 +
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&nbsp;
 +
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document.  
 +
<div class="image-green-border">[[File:7.14 release note 5.png|720px|7.14 release note 5.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''Note''':&nbsp;
  
'''<span style="color:#008000;">560728 – Global favorites – supplier view</span>'''
+
*Only file-based clauses are supported.  
 
+
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template.  
Previously, ICM users created favorites for specific users as per domain or organizational group, however, these favorites were not accessible to all users in the domain.
+
*Location-specific (such as center-justified) rule-based clauses cannot be tagged.
 
+
*Numbering at the template level is not supported.
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.
+
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.  
 
+
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration.  
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;">'''660390 Ability to show more clauses per group'''</span>
  
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, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.
  
With this release, the ''CLM Activity Report'' and ''Cycle Time Report'' have been deprecated, thereby improving ICM performance considerably.
+
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.
 +
<div class="image-green-border">[[File:7.14 release note 12.png|720px|7.14 release note 12.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
<span style="color:#008000;">'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''</span>
  
== ICM API Enhancements&nbsp; ==
+
In ICI, users capture additional details for clauses and templates in the extended attributes.
<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.
+
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.
 +
<div class="image-green-border">[[File:7.14 release note 13.png|720px|7.14 release note 13.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">'''<span style="color:#008000;">664488 – Ability to take deviation workflow actions from Icertis Experience for Word</span>'''</div>
 +
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.
  
The highlights include:
+
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.
 
+
<div class="image-green-border">[[File:7.14 release note 14.png|720px|7.14 release note 14.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.14 release note 15.png|720px|7.14 release note 15.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''</span></div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.14 release note 16.png|720px|7.14 release note 16.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''</span></div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.</div>  
*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; ==
+
== Enhancements to Artificial Intelligence Applications in ICI ==
<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.
+
<span style="color:#008000;">'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''</span>
  
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.
+
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.
</div>
+
&nbsp;
+
  
== Enhancements to Artificial Intelligence Applications in ICM ==
+
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.
  
'''<span style="color:#008000;">510541 – eDiscovery using Artificial Intelligence</span>'''
+
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.
  
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.
+
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.
 +
<div class="image-green-border">[[File:7.14 release note 17.png|720px|7.14 release note 17.png]]</div>
 +
Negotiators can now:
  
With eDiscovery using AI:
+
*Define the structure and setup the playbook by configuring a masterdata in ICI.
 +
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range.
 +
*Use artificial intelligence to identify and highlight the playbook exceptions in the document.
 +
*Review all discovered exceptions that are listed down on the page and take corrective actions as required.
 +
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores.
 +
*Review the version-wise cumulative risk using a risk report.
 +
<div class="image-green-border">[[File:7.14 release note 18.png|720px|7.14 release note 18.png]]</div>
 +
By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.
  
*ICM can automatically confirm certain discovered clauses, so that users do not have to confirm them manually.
+
<br/> <span style="color:#008000;">'''575450 – Supporting clause hierarchy in .docx agreements'''</span>
*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.  
+
  
'''<span style="color:#008000;">510549 – Inbuilt discovery of attributes and clauses in IT services vertical</span>'''
+
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.
  
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.
+
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&nbsp;
 
+
''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.
+
 
+
With this release, in addition to the generic discovery model:
+
 
+
*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.  
+
  
 +
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.
 +
<div class="image-green-border">[[File:7.14 release note 19.png|720px|7.14 release note 19.png]]</div> <div class="image-green-border"><br/> '''Note''':&nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&nbsp;</div>
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">510545 Automating retraining of AI models based on user action feedback</span>'''
+
'''<span style="color:#008000;">663666 Enhancing inbuilt discovery model to include additional attributes&nbsp;</span>'''
  
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.
+
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&nbsp;
  
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, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.<br/> &nbsp;
  
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.
+
<span style="color:#008000;">'''575466 – Support for additional languages in AI apps&nbsp;'''</span>
  
&nbsp;
+
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&nbsp;
  
'''<span style="color:#008000;">465906 Contract highlights</span>'''
+
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages German, Spanish and Portuguese, to meet the needs of our customers.
  
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:
  
With this release,
+
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration.  
 
+
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document.  
*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.  
+
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI.  
*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.  
+
*While discovering or matching the clause from clause library, document language is taken into consideration.  
*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.
+
*The additional languages are supported while discovering similar clauses.  
*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.
+
 
+
'''<span style="color:#008000;">539481 – DiscoveryAI / NegotiateAI support for multi-select attributes</span>'''
+
 
+
''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;
+
 
+
'''<span style="color:#008000;">566499 – Search as a natural language query in ICM</span>'''
+
 
+
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.
+
 
+
&nbsp;
+
  
 
== Enhancements to Reports ==
 
== Enhancements to Reports ==
  
'''<span style="color:#008000;">519281 Out-of-the-Box Obligations Management Dashboard reports</span>'''
+
<span style="color:#008000;">'''514594 Capability of time zone in 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:
+
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.
 +
<div class="image-green-border">With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.<br/> &nbsp;</div>
 +
<span style="color:#008000;">'''514609 – Introducing the Clause Summary Report'''</span>
  
*'''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.
+
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&nbsp;
*'''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.
+
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&nbsp;
  
 +
This default report is accessible from the Admin category of reports and its access is based on Security Groups.
 +
<div class="image-green-border">[[File:7.14 release note 20.png|720px|7.14 release note 20.png]]<br/> &nbsp;</div>
 
== Integrations ==
 
== Integrations ==
  
'''<span style="color:#008000;">467181 Generic integration framework to support SFTP interface</span>'''&nbsp;&nbsp;
+
<span style="color:#008000;">'''554867 Support for ICI dashboard in Icertis Experience for Salesforce'''</span>
  
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.
+
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&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.
+
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&nbsp;
  
This will enable Administrators to:
+
Salesforce users can now:&nbsp;
  
*Define configuration parameters required for SFTP interface using Client App Reference and Client App Entity Mapping.  
+
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&nbsp;
*Configure and run scheduled batch jobs via SFTP.  
+
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&nbsp;
 +
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab.
 +
<div class="image-green-border">[[File:7.14 release note 21.png|720px|7.14 release note 21.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
<span style="color:#008000;">'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''</span>
  
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.
+
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&nbsp;
  
This enables users to:
+
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&nbsp;
  
*Create generic integration mapping in cross reference.
+
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.<br/> <br/> '''Note''':&nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.
*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;">'''635822 Support for pre- and post-processing in Generic Integration Framework'''</span>
  
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.
+
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&nbsp;
  
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.
+
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:
  
Users can now:
+
*Pre-process inbound data through file-based integrations.
 +
*Pre-process inbound and outbound data through ASB-based integrations.
  
*Define configuration parameters for ASB interface using client app reference and client app entity mapping.
+
ICI administrators will now be able to:&nbsp;
*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;
+
*Enable or disable the hook as part of file-based and ASB integration.  
 
+
*Pass parameters to the hook for executing a custom logic.
'''<span style="color:#008000;">544347 – Ability to integrate ICM with Enterprise-Level Identity Providers using OpenID Connect protocol</span>'''
+
*Enable or disable the hook at file or record level.  
 
+
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook.  
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.
+
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.  
 
+
*Execute any custom logic in the system for a file or record when a hook is configured.  
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.
+
*Complete GIF process even when custom logic encounters any error while processing a record or file.  
 
+
This integration implementation is flexible enough to enable connection with other identity providers that use the OpenID Connect protocol.
+
 
+
'''<span style="color:#008000;">467179 – SFDC experience enhancements – simplified UX - action in grid</span>'''&nbsp;&nbsp;
+
 
+
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;">'''635823&nbsp;– Support for defining folder structure in Generic Integration Framework'''</span>
 
+
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.
+
  
'''<span style="color:#008000;">537766 – Reporting capability within Salesforce</span>'''
+
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.
  
Icertis Experience for Salesforce already provides the capability for Salesforce users to execute contract management tasks from within Salesforce.
+
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.
  
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.
+
With this release, users have:&nbsp;
  
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''.
+
*Support for single or multiple folders in the folder structure.
 +
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format).
 +
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change.
 +
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used.  
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">556549 – Enabling existing adapter functionality in the new MS Dynamics unified interface</span>'''
+
== Partner Enablement ==
  
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.
+
<span style="color:#008000;">'''703386 – Icertis Software Development Kit for Partner Enablement'''</span>
  
== ICM Platform Tools ==
+
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide them with the resources and tools that they need while implementing ICI.&nbsp;
  
'''<span style="color:#008000;">519481 – Introducing the ICM Tools portal</span>'''
+
As part of our continuous efforts to support our partners, we have created the following documents in this release:
  
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.
+
*'''ICI Coding Guidelines''':&nbsp;This document helps developers to follow specific guidelines and best practices while coding. This will help them reduce time in development, reduce errors, maintain consistency and enhance collaboration. The document focuses primarily on the .Net framework as platform and C# as the object-oriented programming language.  
  
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.
+
*'''ICI Developer Library''': This document provides a detailed insight into the ICI developer methods library used for various functions and functionalities. It provides a detailed listing of all the methods in ICI development covering multiple parameters such as the summary of the functionality, dependencies, input parameters, return parameters, exceptions and code snippets on how to call the methods.  
  
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.
+
*'''Local Environment Setup using ICI Binaries''': This document provides guidance to Icertis partner developers on how to set up and deploy ICI on their development machines using ICI’s deployable binaries and packages. These binaries and packages are published by Icertis for every GA version.&nbsp;'''&nbsp;'''
  
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.
+
*'''ICI Customization and Use Cases: '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations.  
 
+
'''<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.  
+
  
 
&nbsp;
 
&nbsp;
  
'''<span style="color:#008000;">519630 – Improved ICM Health Check</span>'''
+
== Technical Requirements for Release 7.14 ==
  
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 Icertis Contract Intelligence 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 ''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.
+
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]
  
The health statuses are classified into three categories:
+
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]
  
*''Warning ''- indicated by a yellow warning icon
+
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]
*''Healthy'' -&nbsp; indicated by a green checkmark icon
+
*''Unhealthy'' - indicated by a red warning icon
+
  
The following details are displayed in the Health Check:
+
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]
  
*'''Elastic Search Health''': displays the Status (yellow/green/red), the Elastic Search version, the Uptime, and so on.  
+
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]
*'''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 % 404 HTTP Response Sent, % 500 HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on.
+
 
+
'''<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>
+
== 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:<br/> &nbsp;
+
  
 
&nbsp;
 
&nbsp;
Line 657: Line 449:
 
&nbsp;
 
&nbsp;
  
== Known Issues for Release 7.11 ==
+
'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|
 
+
&nbsp;
+

Latest revision as of 12:24, 1 October 2020

ICI Release Notes - Release 7.14

Overview of Release 7.14

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

The key enhancements of this release include:

  • Enhancements to the ICI Application
  • User Experience
    • Introducing a horizontal chevron which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron, namely Generate, Approve, Execute and Manage, prominently communicate an entity’s journey including the previous, current and possible future states of the agreement.
    • Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement.
    • Facilitating one-click navigation from the ICI record to any related entities (multi-hierarchy level). For example, from RFx to Bid Response which would otherwise require multiple clicks.
    • Providing administrators the ability to configure access control for users who are not part of the team to sections or sub-sections in the left navigation pane at the contract type level.
    • Enhancing document usability by placing content control tags such that the end-user no longer views separate lines in the assembled document for assembled clauses that are not evaluated.
  • Workflow Enhancements
    • Displaying the organization unit path of the parent document by default as the path for the associated document, so that both parent and child documents have the same organization path at the time of creation and updation.
    • Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle.
    • Providing the ability to add amendments to expired agreements.  
    • Adding a time zone attribute to provide enterprise organizations the flexibility to track the time zone or region-based activities as needed for the instance of the agreement.
    • Providing the capability to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications and allowing configuration of the sender’s email ID dynamically based on the specific contract type or instance of the record. 
  • Mobile App Updates
    • Improving the usability of the mobile app by refreshing the agreement or requests list automatically after an approve, reject or request review action is performed.
  • Enhancements to ICI API 2.0
    • Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata.
  • Enhancements to ICI Add-ins
    • Icertis Experience for Word
      • Displaying a set of 30 clauses per page with pagination for easy navigation between clauses listed on the clauses, clauses in templates and clauses in agreement pages.
      • Providing extended attributes within the add-in for creation and modification of clauses and templates.
      • Allowing the deviation approver to view and directly approve or reject clause deviations in an agreement from within the add-in.
      • Displaying a validation message in clause content control enabling users to insert and tag clauses at the correct location in the document before publishing it.
    • Outlook Add-in
      • Enhancing the Outlook Add-in by providing the ability to upload email in .docx or .msg format as associated documents for an agreement from within Outlook.
  • Enhancements to Artificial Intelligence Applications
    • Introducing a legal playbook in the NegotiateAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.
    • Enhancing DiscoverAI to identify the different levels within a clause through a distinct visual representation of clauses with sub-sections displayed in a delineated view during the clause discovery process.
    • Enhancing the ICI discovery models to support clause and obligation discovery for additional languages such as German, Spanish and Portuguese.
    • Improving the inbuilt DiscoverAI model to identify additional attributes such as City, State, Zip Code, and so on.
  • Enhancements to Reports
    • Introducing the Risk Assessment Report which is a trendline chart report that depicts the agreement aggregate risk score by their version. ICI’s AI algorithm identifies the playbook exceptions for a new version.
    • Introducing the Clause Summary Report to help clause administrators to understand and assess the impact of changes made to a clause.
    • Providing users the capability to generate a report as per the time zone of their choice from within the report itself.
  • Improving the Icertis Experience
    • Extending support for ICI dashboard widgets in the Icertis Experience for Salesforce Home page, so that users can perform all necessary actions from within Salesforce itself.
    • Supporting auto-renewal and reset expiry functionalities in Icertis Experience for Workday, thus saving time and avoiding data duplication.
    • Enhancing the generic integration framework to support custom pre- and post-processing hooks to considerably reduce implementation time, and allowing users to define and configure folder structure and file names as per the business requirement.
  • Additions to Icertis Software Development Kit for Partner Enablement
    • In release 7.12, the Software Development Kit (SDK) was released to support partners for technical configuration. With this release, documentation for ICI coding guidelines, ICI developer methods, local environment setup using ICI binaries, and ICI customization and use cases are also available.

These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.

 

ICI Application Enhancements

659853 – Upfront chevron view of agreement journey

In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination. 

Users can view the current status of an agreement on the Agreement Index or Details page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs. 

With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.

The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.

The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:

1. Generate: Displays the list of actions taken by the user on the agreement before it is published.

2.Approve: Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them. 

3. Execute: Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.

4. Manage: Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.

Note

  • The chevron view is only applicable to agreement contract type (agreement and amendment).
  • By default, the chevron is disabled; it can be enabled for selected contract types.
  • The chevron labels support localization.
7.14 release note 1.png
 

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

The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract. 

This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.
 

659725 – Ability to easily navigate to related entities in multi-level hierarchy

With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.

Configurators can: 
  • Configure a smart link across any ICI entity that defines the entity relationships.
  • Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities.

Users can: 

  • Click on the left navigation link from an agreement contract type that will render the smart link result in grid. 
  • Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results.
7.14 release note 2.png
 
Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.
 
The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.

For example, consider entities related in multi-level hierarchy as Agreement > Obligations > Fulfillments. Earlier users had to navigate through obligations in order to access the child fulfillments.
 
Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.

7.14 release note 3.png

 

584439 – Introducing the Contract Manager role for agreements 

In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.

This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process. 

Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.

With this release: 

  • Assignment of the user against contract manager role in the team can be only achieved through event rules using the Add To Team action.
  • Only one contract manager is available inside the agreement at any given point of time.
  • The contract manager will have provisions same as that of primary owner.
  • The contract manager name is displayed on the agreement summary page.
  • Agreements can be searched using the contract manager name.
  • Managing adhoc modification for the contract manager role user will be restricted inside the agreementTeam tab similar to primary owner role user.

 

555890 – Ability to create peer agreement from within the base agreement

Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it. 

With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - Allow Peer Creation Wizard, Allow Multiple Instances and Allow Two-Way Linkage.

 

732038 – Ability to use parent’s Organization Unit path when creating associated document

Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.

With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability. 

7.14 release note 6.png

For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.

7.14 release note 7.png

This is applicable to the following associations: 

  • Import of Association (Line Item)
  • Auto Attachment Association
  • Obligation/ Fulfillment (Association of Association)

The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.

 

575665 – Ability to capture multiple email IDs in a single data type

Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.

With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way. 

Users can now: 

  • Capture multiple valid internal or external email addresses while working on agreements/ requests.
  • Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.

 

583186 – Ability to add amendment on expired agreement

Currently in ICI, users have to revive the agreement from Expired to Executed state by resetting its expiry date and then add amendments to it.

With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment. 

The Add Amendment action is configurable through role action mapping on the expired state of the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.

7.14 release note 8.png

593928 – Ability to configure sender email ID for automated emails

Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.

With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record. 

Administrators can now:

  • Configure the sender information while setting up the subscription under Notifications using the specific user and/ or user attribute information in the agreement.
  • Configure the email addresses for Reply To in the subscriptions setup which recipients can revert to.
  • Send automated notifications from the configured email address with the configured Reply To user email addresses.
7.14 release note 9.png
 

593938 – Time Zone support for date-dependent automated processes

In ICI, there are scheduled jobs that perform certain actions on agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.

To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.

With this release:

  • Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination).
  • Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities.
  • Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance.
  • ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance.
  • Expiry task is enhanced so that agreements expire at end of the day based on the expiry date.

Note: The time zone-based processing can be enabled for all contract types across ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.

7.14 release note 10.png
 

512930 – Triggering service bus events for all actions

For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI. 

With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated. 

The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.
 

545126 – Availability of business status value in ICI event messages

For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.

With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.

Mobile App Updates

660965 – Refresh agreement list on approval

Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically. 

In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.

7.14 release note 11.png
 

ICI API Enhancements 

607867 – ICI API 2.0 Implementation

With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.

Enhancements include:

  • Addition of Masterdata APIs 
    • Users can now update the masterdata instance
    • UserName field is returned in Get Team API as part of the response.
  • Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well.

Enhancements to ICI Add-ins 

714872 – Improved document usability

Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders. 

These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.

With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.

7.14 release note 4.png
 

With this release:

  • All the content controls are put together in a single paragraph on any line with valid content.
  • One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.
  • An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules.
  • If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph. 
  • Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document.
7.14 release note 5.png
 

Note

  • Only file-based clauses are supported.
  • Custom fonts at the content control level of the rule-based clauses are currently not supported in the template.
  • Location-specific (such as center-justified) rule-based clauses cannot be tagged.
  • Numbering at the template level is not supported.
  • One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.
  • A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration.

 

660390 – Ability to show more clauses per group

With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.

This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.

7.14 release note 12.png
 

707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word

In ICI, users capture additional details for clauses and templates in the extended attributes.

These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.

7.14 release note 13.png
 
 
664488 – Ability to take deviation workflow actions from Icertis Experience for Word

Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.

Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.

7.14 release note 14.png
 
7.14 release note 15.png
 
 
660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word
 
Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.
 
Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.
 
This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.
 
7.14 release note 16.png
 
 
667815 – Ability to upload email as association of an agreement using Outlook Add-in
 
Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in. 
 
With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.
 
Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.

 

Enhancements to Artificial Intelligence Applications in ICI

662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word

With this release, ICI is introducing a legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.

Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.

Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.

The exceptions are identified by the NegotiateAI app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.

7.14 release note 17.png

Negotiators can now:

  • Define the structure and setup the playbook by configuring a masterdata in ICI.
  • Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range.
  • Use artificial intelligence to identify and highlight the playbook exceptions in the document.
  • Review all discovered exceptions that are listed down on the page and take corrective actions as required.
  • Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores.
  • Review the version-wise cumulative risk using a risk report.
7.14 release note 18.png

By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.


575450 – Supporting clause hierarchy in .docx agreements

Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.

With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on. 

Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.

7.14 release note 19.png

Note: Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document. 

 

663666 – Enhancing inbuilt discovery model to include additional attributes 

The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents. 

With this release, identification of the following 9 additional attributes has been introduced - City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone.
 

575466 – Support for additional languages in AI apps 

Previously, the ICI clause and obligation discovery models were primarily based on the English language. 

In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.

With this release:

  • Additional language support is available in NegotiateAI and DiscoverAI for legacy migration.
  • Discovered clauses and obligations are displayed and then linked back to the matching text in the original document.
  • Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI.
  • While discovering or matching the clause from clause library, document language is taken into consideration.
  • The additional languages are supported while discovering similar clauses.

Enhancements to Reports

514594 – Capability of time zone in reports

ICI reports display the date and time values based on the Time Zone selected in the Locale Settings under Preferences.

With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.
 
The Time Zone parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.
 

514609 – Introducing the Clause Summary Report

Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes. 

With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity. 

This default report is accessible from the Admin category of reports and its access is based on Security Groups.

7.14 release note 20.png
 

Integrations

554867 – Support for ICI dashboard in Icertis Experience for Salesforce

In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks. 

With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI. 

Salesforce users can now: 

  • Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab. 
  • View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets. 
  • Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab.
7.14 release note 21.png
 

583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday

The Icertis Experience for Workday supports Create and Update events for agreements and amendments. 

With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday. 

These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.

Note: Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.

 

635822 – Support for pre- and post-processing in Generic Integration Framework

Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa. 

With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:

  • Pre-process inbound data through file-based integrations.
  • Pre-process inbound and outbound data through ASB-based integrations.

ICI administrators will now be able to: 

  • Enable or disable the hook as part of file-based and ASB integration.
  • Pass parameters to the hook for executing a custom logic.
  • Enable or disable the hook at file or record level.
    • When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook.
    • When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.
  • Execute any custom logic in the system for a file or record when a hook is configured.
  • Complete GIF process even when custom logic encounters any error while processing a record or file.

 

635823 – Support for defining folder structure in Generic Integration Framework

Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.

Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.

With this release, users have: 

  • Support for single or multiple folders in the folder structure.
  • A folder and file naming convention which is flexible and configurable via masterdata (in JSON format).
  • Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change.
  • A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used.

 

Partner Enablement

703386 – Icertis Software Development Kit for Partner Enablement

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide them with the resources and tools that they need while implementing ICI. 

As part of our continuous efforts to support our partners, we have created the following documents in this release:

  • ICI Coding Guidelines: This document helps developers to follow specific guidelines and best practices while coding. This will help them reduce time in development, reduce errors, maintain consistency and enhance collaboration. The document focuses primarily on the .Net framework as platform and C# as the object-oriented programming language.
  • ICI Developer Library: This document provides a detailed insight into the ICI developer methods library used for various functions and functionalities. It provides a detailed listing of all the methods in ICI development covering multiple parameters such as the summary of the functionality, dependencies, input parameters, return parameters, exceptions and code snippets on how to call the methods.
  • Local Environment Setup using ICI Binaries: This document provides guidance to Icertis partner developers on how to set up and deploy ICI on their development machines using ICI’s deployable binaries and packages. These binaries and packages are published by Icertis for every GA version.  
  • ICI Customization and Use Cases: This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations.

 

Technical Requirements for Release 7.14

The Icertis Contract Intelligence 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.14 release note 22.png

7.14 release note 23.png

7.14 release note 24.png

7.14 release note 25.png

7.14 release note 26.png

 

 

Related Topics: Agreement Management | Association Management | Compliance Management | Template Management | Clause Management | Configuration | Reports | Advanced Analytics | User Administration | ICI Tools Icertis Business Apps | AIML | ICI Add-ins | ICI Mobile_App | ICI Business Apps Release Notes |