= ICI Release Notes - Release 7.15 =

The key enhancements of this release include:

*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>

***Introducing &nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation.

**'''''Workflow Enhancements'''''

*<span style="color:#800080;">'''Mobile App Updates'''</span>

**Enhancing &nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users.

*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>

*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>

**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word.

**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause.  

**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration.

**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&nbsp;

**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&nbsp;

**Improving &nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.  

*<span style="color:#800080;">'''Enhancements to Reports'''</span>

**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates.

**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users.

**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&nbsp;

**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability.  

**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI.

**Enhancing localization support in reports.  

*<span style="color:#800080;">'''Improving the Icertis Experience'''</span>

***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).<br/> Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.<br/> Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &nbsp; 

***Providing the ability to send success and failures alerts for improved monitoring of messages.

***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&nbsp;   

*<font color="#800080">'''Enhancements to Platform Tools'''</font>  

*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>

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

== <span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span> ==

<span style="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</span>

Previously, contract owners had to view the first version of an agreement in order to get a comprehensive view of the agreement that they had created.

With this release, a preview functionality is being introduced, so that primary owners or contract creators can review whether the selected template is appropriate, the rule-based clauses have been correctly added to the agreement, among other factors, and make changes to the agreement before the version is created.&nbsp;

'''Note: '''The preview functionality is configurable and will not be available by default.

<span style="color:#800080;">'''575640 – Creating associations on create or edit wizard of agreement'''</span>

Previously in ICI, contract authors had to create associations for agreements using the association management functionality. However, in practical terms associations such as annexures, supporting documents, SLAs, product specifications, rate tables, and so on, are all an inherent part of agreement information that is critical to business.

In view of this, the ability to create association instances as part of agreement creation is being introduced in this release. A separate page is displayed to the user during agreement or amendment creation to create, view or delete inline associations. The user also has an option to select the columns and their order in the association grid.

<br/>  <br/> <span style="color:#800080;">'''549900 – Supporting localized reason code values as per logged in user language'''</span>

Adapting existing products to new markets through translation and localization is the key for global growth. The localized versions of the product improve the overall user experience and helps to better connect with new and potential global customers.

ICI now extends its localization support to reason code values. Users can see localized reason codes as per their preferred language settings. Administrators can enter the translated values in the local language for each reason code using the “Translations Editor” tool. The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.

In ICI, to terminate an agreement, users create and execute a termination agreement on a main agreement. ICI has now extended this capability to contract requests also.&nbsp;

Users can enable the termination process at contract type level using the seeded attribute "Request for Termination", select the parent contract request, and create the termination contract on a contract request. The termination instance for contract request will have all the common attribute values inherited, if the inheritance is enabled. The termination record will be displayed as a peer association under the “Association” tab for the contract request.&nbsp;

The access privileges for the contract requests termination process is controlled through role action mapping.

'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''

ICI’s collaboration portal allows external users with login privileges to access the platform and perform tasks assigned to them within ICI itself.&nbsp;

In our continuous effort to improve usability, a search option has been introduced on index pages, so that external users can easily search records. To perform a more refined search, the attributes displayed as columns of the search grid are included as facets in the filter options. This is applicable to index pages of contract requests, agreements, associations and masterdata.<br/> '''Note:&nbsp;'''This is not applicable for:

With this release, users will be able to view these clause extension attributes on the agreement entity for easy reference while working with agreements.&nbsp;

*View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs.

*View the hyperlink “Show Clause Information”, which displays all clause extension attributes in a separate window.

*Select and save extension attributes to display in the grid view.

*View clause extension attributes in the “Clause Profiling Report”.  

<br/> <span style="color:#800080;">'''514615 – Approving a contract from emails'''</span>

Email notifications, in ICI, allow users to customize text, add tags (attributes) inside the email body, define recipients, and so on. This capability has been further enhanced such that approvers can directly approve or reject an agreement from within the email itself, as part of the approval or request review process, thus reducing the overall turnaround time and increasing efficiency.

They can also add notes on approval, add reason code on rejection, and enable download or upload of the agreement document along with comments. This is applicable to contract requests, agreements, associations, amendments, masterdata, templates, clauses and user information instances.

<span style="color:#800080;">'''514643 – Ordering of clauses as tagged in an agreement'''</span>

Previously in ICI, list of clauses available inside the agreement or amendment displayed clauses in a random order on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.

With this release, the tagged clauses are displayed on respective pages in ICI Web and Icertis Experience for Word, in the same order in which they are tagged inside the agreement, thus making it easier for users to identify them. The order is refreshed on every upload to display the latest.

<span style="color:#800080;">'''514621 – Reviving terminated agreements'''</span>

Users may terminate an agreement with the other party for various business reasons. To improve usability, ICI now provides the capability to add and execute amendments on a terminated agreement. This considerably saves the time for users who may want to re-instantiate their existing relationship with the other party, as they no longer need to create an entirely new agreement, and go through several workflows such as clause deviations clearance, template process, and so on.

Adding and executing an amendment on a terminated agreement will move the agreement back to the “Executed” or “Expired” state, based on its expiry date, thus reviving the terminated agreement. It will also revive any amendments of the base agreement terminated through the agreement termination process and move them back to their respective previous states. However, any previous amendments terminated through review process will remain in the terminated state. &nbsp;

'''Note: '''By default, only primary owners and contract managers can add an amendment to the terminated agreement. The access privileges are controlled through role action mapping.&nbsp;<br/> &nbsp;

<span style="color:#800080;">'''514625 – Terminating agreements in bulk'''</span>

Users may need to terminate agreements in bulk in many business scenarios such as regulatory changes, changes in product offerings, and so on. Users can now initiate termination of agreements in bulk, thereby reducing the manual errors and saving the time to terminate agreements one by one. Bulk termination is carried out using ICI’s existing “Bulk Actions” process. The termination related attributes will be pre-selected, and the Workbook for the bulk action batch will be generated with the executed agreement records from the saved search, as per the selected contract type and termination contract type.&nbsp;

Users can now:&nbsp;

'''Note: '''All the prerequisite configurations applicable for the Termination workflow should also be set for the bulk termination process.<br/> &nbsp;

<span style="color:#800080;">'''555898 – Defining display sequence on lookup attributes at contract type level'''</span>

Previously in ICI, users could not define the display order for lookup attribute’s values in a drop-down on ICI UI to reference masterdata. Users then had to scroll through all populated values in order to find the desired values during agreement creation. &nbsp;

This setting of display sequence is supported on create, edit and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause and template entities, and template variables.

The display will revert to the default alphabetical order if the display sequence is not configured in masterdata.&nbsp;

<span style="color:#800080;">'''558605 – Viewing amendments in grid view on agreement details page'''</span>

Previously in ICI, users could only view the agreement’s amendments in a “Tile” view, when opened from the left navigation pane on the agreement “Details” page.&nbsp;

ICI now allows users to view amendments in “Grid” view as well, and have the capability to toggle between the grid view and existing tile view. The grid view is the default view for amendments and supports all existing grid functionalities, such as standard search, filter, column selection, pagination, export to CSV/Excel, and so on.<br/> &nbsp;

<span style="color:#800080;">'''561410 – Enhancing the multi-select drop-down&nbsp;'''</span>

The multi-select choice drop-down has been enhanced for better usability, data input and post-selection data review of contract requests, agreements, amendments and masterdata entities.&nbsp;

*View eight default options in a drop-down list (instead of six), without scrolling.&nbsp;

*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&nbsp;

*Deselect the selected values individually or all with a single-click, without opening the drop-down.<br/> &nbsp;

<span style="color:#800080;">'''819453 – Configuring opening of drop-down menus on mouse hover'''</span>

ICI has improved usability by providing the capability to configure the expansion of drop-downs on mouse hover, instead of a mouse click.&nbsp;

This can be configured at a contract type level and supports contract requests, agreements, associated documents and masterdata. It is applicable for lookup, multi-select lookup, choice, multi-select choice and currency drop-downs.

<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>

In ICI, the configurator can filter the lookup masterdata table with “Must” and “Must Not” conditions, to achieve necessary business scenarios, while configuring a lookup attribute on contract types.&nbsp;

ICI now also provides the ability to configure a lookup attribute with the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup master data attribute.&nbsp;

Configurators can now:&nbsp;

*Use the "IN” operator in lookup filter attribute on agreement contract types.&nbsp;

Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;

ICI now provides the capability for administrators to set preferences as default, for users, according to their locations or offices they work in. This reduces the end user’s effort of setting up the ICI account with required parameters after first log-in, and presents the system with appropriate and specific pre-settings. &nbsp;&nbsp;

*Search users based on parameters related to preference settings.

Users can:&nbsp;

<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading document'''</span>

Previously in ICI, users could not move agreements and amendments from “Waiting For Signature” to “Executed” state without uploading the supporting document, in case of manually signed agreements.&nbsp;

Notifications can be configured to inform users about skipped document uploads, so that users can cover for delays occurring due to the scan and upload process while executing a large volume of documents.&nbsp;

ICI users could share the main agreement document as part of various email notifications that get triggered for the agreement from time to time.&nbsp;

This capability has now been extended to supporting (associated) documents as well, so that users no longer need to manually share them offline.

*Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements and amendments.  

*Users can define the notification as internal or external.&nbsp;

*Users can define the type of associated document instance as internal, external or restricted.  

*Based on the type of notification and type of tagged associated documents, documents are attached to the email notification.  

<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>

ICI allows users to define the linkage type as parent, child or peer while associating peer entities with each other.&nbsp;

Users now have the capability to define custom labels for peer associations by configuring the “Linkage Type” masterdata. The custom labels define various business relationships in the context of contracts. For example, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.&nbsp;

The custom labels will support existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as peer, with default peer linkage type label, defined in default peer mapping for amendment.&nbsp;

*Agreement creation workflows for peer entities, assignment, initiate termination flow.&nbsp;

*Associate and Inheritance icons.

*Broadcast – “Attachments” tab, beside peer-to-peer instances.  

'''Note: '''Custom labels are not supported for parent and child linkage types, as there is specific business logic built with them in the ICI system.

ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements and bulk operations.&nbsp;

With this release, users can also selectively download amendments of an agreement with corresponding parent child associations in the downloaded zip package.

For ease of access, each selected amendment will be downloaded with its selected associations in separate folders. The folders are named “Amendment_1”, “Amendment_2”, and so on (from oldest to latest), instead of actual amendment names. This helps to overcome the Windows limitation of supporting 260 characters in the file path, and gives users the flexibility while creating association’s names.<br/> &nbsp;

<span style="color:#800080;">'''615291 – Configuring attributes inheritance for amendments at contract type level'''</span>

ICI already provided the capability to exclude certain agreement attributes from being copied to the amendment through technical configuration which applied to all agreement contract types by default.&nbsp;

ICI now provides the flexibility for users to decide which attributes of an agreement can be copied to amendments, per contract type, as per business requirements. Configurators can enable or disable the attribute’s inheritance for amendments, using “Is Inherit On Amendments” attribute, at the agreement contract type and template variable levels. Users can then copy these defined attributes values from base agreement to amendment during amendment creation.&nbsp;

This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided for these admin actions.<br/> &nbsp;

<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</span>

In ICI, users could supersede all parent agreement’s attributes configured as supersedable with values from its amendment, either manually using “Supersede” action or automatically through auto-supersede backend task.&nbsp;

The administrator can control the supersede functionality for agreements by configuring rules with:&nbsp;

*The rule actions as “Is Auto Supersede by Amendment”, “Is Auto Supersede by Termination” and “Is Auto Supersede by Assignment for Amendment”, “Assignment and Termination”, with required attributes set, as per the business condition.

*The attribute selection field with all or multi-select capability.&nbsp;

Users can preview the attribute’s supersede value on the agreement and view the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing behavior.

ICI now provides the capability to suppress this message, thereby minimizing the number of unnecessary clicks through technical configuration.&nbsp;

Administrators can:&nbsp;

*Selectively enable or disable the “No Team Available” message window, at entity contract type level, appearing at various states.&nbsp;

*Disable the “No Team Available” message window completely, at instance level, for all entities. The instance level settings will override any entity level settings.&nbsp;

'''Note:''' This capability is available across ICI for all entities, events, integrations and add-ins in ICI.

<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>

Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator.&nbsp;

With this release, configurators can now set multiple, complex conditions to display attributes on ICI Web UI dynamically, based on business scenarios. Configurators can define conditions for attributes for all entities, except for template variables. For example, the configurator can set conditions to display an attribute based on the selection of specific value in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality. &nbsp;

Users can now:&nbsp;

*Apply multiple and complex conditions to display an attribute by enhancing the enable expression (visibility expression) for contract requests, agreements, associations and masterdata contract types.&nbsp;

*Define conditions with different operators based on the selected attribute datatype.&nbsp;

*View the conditional attribute value according to the value entered in the attribute on which a condition is set, which in turn helps to enter the information in the required attribute as per business requirements.<br/> &nbsp;

<span style="color:#800080;">'''616901 – Applying facets to business status search filter'''</span>

Previously, the ICI search functionality supported filters on “Business Status” for users to narrow down results. However, manually selecting filters often becomes a tedious task in case of several business statuses.&nbsp;

In order to provide a better user experience, faceted filters using string operators, such as “Contains”, “Starts With”, “Does Not Contain”, and so on, are being added to the “Business Status” filters for ease of use.

<span style="color:#800080;">'''732929 – Uploading clauses and templates in bulk'''</span>

With this release, an automation has been provided for bulk import, which will reduce any human dependency, manual approvals and delays for onboarding templates and clauses using the current capabilities. ICI administrators can now import templates and upload clauses to ICI in bulk.<br/> &nbsp;

ICI now provides support for larger files. This is applicable to masterdata and associations.

*Upload files up to 4GB under the file selection attribute.&nbsp;

*Upload files with all supported files extensions allowed in the file selection attribute.  

*Download All/Download Package up to 6 GB.  

ICI supports virus scanning of large files if the virus scan feature is enabled.<br/> &nbsp;

<span style="color:#800080;">'''697367 – Enhancing contract type publish to limit schema change for entity'''</span>

ICI has made the following enhancements to the contract type publish capability:

*There is zero downtime when a contract type is published.&nbsp;

*The schema of only selected contract types that are being published will be blocked for write operations, hence they will not be available at the time of contract creation. However, all other contract types will be available to the user.<br/> &nbsp;

<span style="color:#800080;">'''618994 – Supporting special characters in agreement templates'''</span>

Previously in ICI, attribute names did not support special characters.

Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash),&nbsp;: (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (dot) can be used in the display name of attributes for contract requests, agreements, associations and masterdata contract types. The same attribute display name as provided by the configurator will now be displayed including special characters.

<span style="color:#800080;">'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''</span>

Users can configure an alternate UI control for drop-downs with limited number of values for choice attributes at contract type, global attribute and template variable levels. This improves the user experience as the number of clicks and scrolls required to view options in a drop-down are considerably reduced, and provides better readability in terms of post-selection data review. &nbsp;&nbsp;

*Radio button for single-select choice attributes.&nbsp;

*Checkbox list for multi-select choice attributes.  

The configuration is applicable for creation and editing of contract requests, agreements and amendments.<br/> &nbsp;

<span style="color:#800080;">'''752540 – Upgrading client-side libraries'''</span>

With this release, some client-side libraries have been upgraded, whereas some that were not being used have been removed.&nbsp;<br/> &nbsp;

== Mobile App Updates ==

<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span><br/> Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.

<span style="color:#800080;">'''850259 – Updating logo and attributes to new guidelines'''</span><br/> As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.

&nbsp;

<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span><br/> With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.

&nbsp;

<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span><br/> With this release, the UI WebView component for iOS has been deprecated.

<span style="color:#800080;">'''704069 – Enhancing ICI API 2.0 implementation'''</span>

With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&nbsp;

<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>

ICI already supports downloading agreements.

As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.

<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>

As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.

For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&nbsp;

In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&nbsp;

 

The following API changes have been made to ensure that the existing implementation and code do not break:

 

*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return).

*The called API path with query string will be logged in Kibana.&nbsp;

 

'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.

 

This can be used for:

 

</div>  

<span style="color:#800080;">'''745266 – Supporting online editing of agreements'''</span>

As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&nbsp;

With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.

*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&nbsp;

*The online Word editor is available only for users with valid Office 365 subscription.

*Only users with edit privileges on a document can make changes to the document online.

*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly.  

ICI allows users to capture additional details for clauses in the extended attributes.&nbsp;

Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.

<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>

 

In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.

 

 

*Search and filter clauses and templates based on the name or text inside the clause or template respectively.  

*Perform free text search on clauses and templates.  

<span style="color:#800080;">'''603690 – Updating templates automatically with latest clause version'''</span>

Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.

Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.

<br/>  <br/> <span style="color:#800080;">'''593421 – Labeling agreement document versions as per signature copy'''</span>

Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.

== Enhancements to Artificial Intelligence Applications in ICI ==

<span style="color:#800080;">'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''</span>

ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &nbsp;

With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&nbsp;

Users can now:&nbsp;

<span style="color:#800080;">'''575475 – Automating user feedback for clauses, obligations and attributes'''</span>

ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &nbsp;

With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.

<br/> <span style="color:#800080;">'''539492 – Improving clause delineation in DiscoverAI'''</span>

ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&nbsp;

*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&nbsp;

*Change the clause category and the level (parent or child) of the discovered clause. &nbsp;

*Choose to view only the level 0 clauses.  

<span style="color:#800080;">'''770375 – Merging metadata discovery page with attribute page'''</span>

With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&nbsp;

Users can:&nbsp;

The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.

<span style="color:#800080;">'''727312 – Formatting based clause delineation for additional document types'''</span>

<span style="color:#800080;">'''727314 – Supporting additional languages in AI apps'''</span>

In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.

With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.

'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.

 

<span style="color:#800080;">'''710739 – Configuring custom rules in DiscoverAI'''</span>

 

 

 

The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.<br/> &nbsp;

 

 

<span style="color:#800080;">'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''</span>

 

 

 

 

'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.

<span style="color:#800080;">'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''</span>

Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&nbsp;

In this release, the report is enhanced to display a “Clause Extension Summary”, which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.

<br/>  <br/> <span style="color:#800080;">'''514611 – Enhancing Notifications History Report for an entity'''</span>

ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&nbsp;

The default SSRS report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities.&nbsp;

The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&nbsp;

*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&nbsp;

*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.  

<span style="color:#800080;">'''742607 – Supporting localization for status and business status'''</span>

*Status filter on all reports, drop-down with Yes/No values.&nbsp;

*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&nbsp;

*Dynamic column headers (for example, RFx Details Report in Sourcing).&nbsp;

*Any error or validation messages, informative messages such as “No data available”. &nbsp;

<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span><br/> Previously the "Agreement Status" filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&nbsp;

Now, this filter is also available for the "Agreement Deviation Report" and "Agreements Pending Execution Report". Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.

<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>

A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.<br/> &nbsp;

== Integrations ==

<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

[[File:7.15 Technical Requirements - Operating Systems.PNG|720px|7.15 Technical Requirements - Operating Systems]]

 

 

 

 

 

[[File:7.15 Technical Requirements - Special Requirements 2.PNG|720px|7.15 Technical Requirements - Special Requirements 2]]

 

[[File:7.15 Technical Requirements - Special Requirements 3.PNG|720px|7.15 Technical Requirements - Special Requirements 3]]

 

 

[[File:7.15 Technical Requirements - MS Office Plugins 2.PNG|720px|7.15 Technical Requirements - MS Office Plugins 2]]

 

[[File:7.15 Technical Requirements - Security.PNG|720px|7.15 Technical Requirements - Security]]

 

 

 

 

'''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;|