= ICI Release Notes - Release 7.15 =

The key enhancements of this release include:

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

**Expanded contract request experience now includes the ability to request Contract Terminations.

**Bulk actions support is now extended to Terminating agreements in bulk to support situations that require it, such as regulatory changes, or business partner insolvency. &nbsp;

**Larger file size support when uploading (4GB) and downloading (6GB) files for masterdata and associations.&nbsp;  

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

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

**Providing support for the script and integrated attributes as cascaded attributes for lookup fields when configured at the contract type level. This is applicable for retrieval, creation, and update of the instances of contract requests, agreements, associations, and amendments.  

**Adding the identifier “TrackingId” which can be passed by subsequent API calls for logging and troubleshooting errors.

**Adding support for troubleshooting API issues with failure notifications. &nbsp; 

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

**'''''Icertis Experience for Word'''''  

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

***Improved usability by enabling larger window views of the “Details” page, including deviations.

***All the playbook positions for a contract type now have the option to search and filter.

***Administrators can create a new playbook record or update an existing one from within Icertis Experience for Word itself.  

**Improving the clause delineation logic so that users can rearrange the AI-identified clause boundaries. You can now merge or split discovered clauses or selected text in a clause and also create sub-clauses within the discovered clause.

**Improving library clause recommendations for discovered clauses based on learnings from user’s actions in previous discoveries.&nbsp;

**Enhancing and optimizing the performance of Machine Learning services to simplify deployment and run the workload on-demand while significantly reducing infrastructure management needs.  

*<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. This will help the Legal/Admin users to assess the impact of configuration changes to the clauses and templates.

**Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.

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

**Multiple localization enhancements within 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 (manual and/or electronic) 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).

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

***With this release, the following SDK documents have been updated – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, and Self-Serve Tools.<br/>     

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

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

Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.

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

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

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 1.png|720px|7.15 Release Notes Screenshot 1]]</div>

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

Previously in ICI, contract authors had to create associations for agreements after the agreement was already created. However, in practical terms, associations such as annexures, supporting documents, SLAs, product specifications, rate tables, and so on, are all an inherent part of the agreement information that is critical to the business, and some associations are required to be created along with the agreement.

</div> <div class="image-green-border">[[File:7.15 Release Notes Screenshot 3.png|720px|7.15 Release Notes Screenshot 3]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''549900 – Supporting localized reason code values as per logged in user language'''</span></div>

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

ICI now extends its localization support to reason code values. 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.

&nbsp;

<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from the contract request'''</span>

To terminate an agreement in ICI, users create and execute a termination agreement on the main agreement instance. This capability is now extended to initiate the termination from contract requests as well.

Users can now enable the termination process at the 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 the contract request will have all the common attribute values inherited if the inheritance is enabled.&nbsp;

The termination record will be displayed as a peer association under the “Associations” tab for the contract request. The access privilege for the contract request termination process is controlled through role action mapping.

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

The Collaboration Portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself.&nbsp;

In our continuous effort to improve usability, a search option has been introduced on contract requests, agreements, associations, and masterdata index pages, so that external users can easily search records. The attributes displayed as columns of the search grid are included as facets in the filter options to perform a more refined search.

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 8.png|720px|7.15 Release Notes Screenshot 8]]</div>

*Select and save extension attributes to display in the grid view, via the default search column functionality.

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

*View the hyperlink “Show Clause Information”, which displays all clause extension attributes along with clause attributes, in the same window.

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 9.png|720px|7.15 Release Notes Screenshot&nbsp;9]]</div>

<span style="color:#800080;">'''514615 – Streamlining&nbsp;the approval process over emails'''</span>

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

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

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 10.png|720px|7.15 Release Notes Screenshot&nbsp;10]]</div>

*Administrators can add tags for an Approve/Reject link in the notification template.

*Approvers/reviewers can download the agreement, modify it and upload it back to ICI based on the access provided.

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 11.png|720px|7.15 Release Notes Screenshot]]</div>

<span style="color:#800080;">'''617385&nbsp;– Ability to define additional clause group under clause entity'''</span>

Previously, ICI supported 3 clause groups – “Termination”, “Legal” and “None”.&nbsp;

With this release, this capability has been further enhanced so that the configurator can configure various clause group names in ICI. These clause groups can be categorized or grouped as per business requirements for better identification and negotiation during the contract workflow.

*Define and update clause groups.  

*Edit, delete, activate or deactivate clause group entities.  

*View additionally added clause group values in the clause entity when creating or editing a clause.  

*Search agreement records or clauses on the index page on clause group attributes with added values.  

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

<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 514643.png|720px|514643]]</div>

<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 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. The system sets an identifier attribute "Is Termination Revived" for such revived base agreements, and they can be used in search filters, notification rules while configuring saved searches, and so on.

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

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 the termination of agreements in bulk, thereby saving the time to terminate agreements one by one and reducing manual errors.

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;&nbsp;

*Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch. &nbsp;

*Create termination agreements for “Draft”, “Published” or “Send for Approval” states, as per the batch Workbook configuration for bulk actions.  

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

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

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

Configurators can now define and maintain the display sequence for selected masterdata records, starting from 1 to n, at the masterdata contract type level, using a seeded display sequence attribute. The values will thus be displayed at the top for easier and faster selection in lookup attributes. &nbsp;

This display sequence setting is supported on the create, edit, and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause entities, and template variables. The display will follow the default alphabetical order if the display sequence is not configured in masterdata.&nbsp;&nbsp;

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 14.png|720px|7.15 Release Notes Screenshot 14]]</div>

<span style="color:#800080;">'''558605 – Viewing amendments in grid view on the 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;

Users can now view amendments in the “Grid” view, and toggle between grid or tile view. The grid view is the default for amendments and supports all existing grid functionalities, such as standard search, filter, column selection, pagination, export to CSV/Excel, and so on.

<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 options in a drop-down list (instead of six), without scrolling.&nbsp;

*Deselect the selected values, individually or all with a single click, without opening the drop-down.

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 16.png|720px|7.15 Release Notes Screenshot 16]]</div>

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

With this release, ICI provides the ability to configure a lookup attribute using the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup masterdata attribute.&nbsp;

Configurators can now:&nbsp;

Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute. &nbsp;

<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>

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

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

*Set and manage preferences for a single user through a single user update, and for multiple users through the bulk process.

*View preference settings modification details in the “History” tab for audit.

*Search users based on parameters related to preference settings.  

*Access the ICI system with appropriate details as default, after the first login.&nbsp;

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 18.png|720px|7.15 Release Notes Screenshot 18]]</div>

<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading the 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;

With this release, users can now skip uploading the document, to move agreements from “Waiting For External Signature” or “Waiting For Internal Signature” to the “Executed – (Pending Signed Document)” state.

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 20.png|720px|7.15 Release Notes Screenshot 20]]</div>

<span style="color:#800080;">'''614860 – Attaching associated documents to agreement notifications'''</span>

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

In addition to the main agreement document, users can now send associated documents as part of various email notifications that get triggered for the agreement from time to time. Access to these documents can be controlled based on the type of document – internal, external, or restricted. For example, some documents may only be shared with internal users, some may be shared with internal and external users, whereas some may not be shared with anyone.

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

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

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

The configurable labels support the 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 the default peer mapping for the amendments.&nbsp;

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

<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 586492.png|720px|586492]]</div>

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 22.png|720px|7.15 Release Notes Screenshot 22]]</div>

<span style="color:#800080;">'''619558 – Downloading amendments using download all functionality'''</span>

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

With this release, users can download amendments of an agreement with corresponding parent-child associations in the downloaded zip package. This is supported on the selective download option too.

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 flexibility to users while creating association names.

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 24.png|720px|7.15 Release Notes Screenshot 24]]</div>

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

ICI already provided the capability to exclude specific agreement attributes from being copied to amendments through technical configuration, which applies to all agreement contract types by default.&nbsp;

Configurators now have the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. They can enable or disable the attribute’s inheritance for amendments, using the “Is Inherit On Amendments” flag, at the agreement contract type and template variable levels.&nbsp;

'''Note:&nbsp;'''

*The technical configuration settings for excluding parent agreement attributes from its amendments will always take preference over the settings at agreement contract type and template levels.

*The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.  

In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees.&nbsp;

Administrators can now:&nbsp;

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 26.png|720px|7.15 Release Notes Screenshot 26]]</div>

This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management UI is provided to carry out these user management actions.

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

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

In ICI, users could supersede all attributes of a parent agreement configured as ‘supersedable’ with values from its amendment, either manually using the “Supersede” action or automatically through the auto-supersede task. Users can now selectively supersede individual entities based on business conditions.

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 27.png|720px|7.15 Release Notes Screenshot 27]]</div>  

The administrator can control the supersede functionality for agreements by:

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 28.png|720px|7.15 Release Notes Screenshot 28]]</div>

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

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 29.png|720px|7.15 Release Notes Screenshot 29]]</div>

<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 a single “equal to” operator.&nbsp;

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

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

Business statuses are prominently used by all customers as they reflect the actual status in business terms as compared to the system workflow status. Previously, the ICI search functionality supported filters on “Business Status” for users to refine results. However, manually selecting filters often becomes a tedious task in case there are several business statuses.&nbsp;

For ease of use and a better user experience, faceted filters using string operators, such as “Contains”, “Exactly”, “Starts With” and “Does Not Contain” have been added to the “Business Status” filters.

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 31.png|720px|7.15 Release Notes Screenshot 31]]</div>

<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>

Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&nbsp;

ICI's parsing logic is now improved for handling string combinations with special and alphanumeric characters so that no errors are generated. This applies to all entities across ICI, where a combination of special characters, alphabets, and numbers can be used.

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

New customers or new groups onboarding to ICI mostly have their templates and clauses already created in a separate file. Previously, manual efforts were needed to onboard hundreds to thousands of templates and clauses.&nbsp;

With this release, the bulk import functionality using the “Legacy Upload” tool has been automated, 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.

Along with the tool, an XML specification document is also released which can be used for creating tags in the input document files of clauses and templates.

<span style="color:#800080;">'''655507 – Uploading and downloading large files with the file path attribute'''</span>

ICI now provides support for larger files. This applies to masterdata and association entities.

Users can now:

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

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

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

'''Note:&nbsp;'''This is not applicable for contract requests, agreements, or associations with large files in the DocuSign/Adobe Sign association selection pop-up, document assembly, bulk actions, legacy upload, integrations (Salesforce, Workday, etc.), and APIs. The Upload/Download of the files would be supported for Azure and Windows Storage.

<span style="color:#800080;">'''618994 – Supporting special characters in agreement templates and support to skip empty columns while a saved search/association is tagged in a template'''</span>

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 . (period) 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.

In scenarios where the association or saved search is tagged as a table in the agreement, and a particular column of the table does not have any data, we have introduced a functionality to skip such empty columns.&nbsp;<br/> During template creation from Icertis Experience for Word, the configurator can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table.&nbsp;This property needs to be added manually in the “Content Control Properties”, at any position after the contract type GUID, separated by a '|' (pipe separator). This enables empty columns to be skipped in document assembly, thereby eliminating unnecessary empty columns in the agreement version. The order of the columns in the table is determined by the attributes in the display preference of the associated document contract type.&nbsp;

<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 618994.png|720px|618994]]</div>

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

With this release, ICI provides new controls for multi-select and single-select choice attributes.

Users can configure an alternate UI control for drop-downs with a 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 is considerably reduced and provides better readability in terms of post-selection data review. &nbsp;&nbsp;&nbsp;

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 33.png|720px|7.15 Release Notes Screenshot 33]]</div>  

Users can select:&nbsp;

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 34.png|720px|7.15 Release Notes Screenshot 34]]</div>

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

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 35.png|720px|7.15 Release Notes Screenshot 35]]</div>

<span style="color:#800080;">'''872309 – Providing flexibility for assembling associations tagged as clauses'''</span>

In ICI, on publishing and updating actions, all clauses are evaluated, assembled and the changes are reflected in the agreement document. However, if associations are tagged in clauses, on “Assemble Contract” and “Send For Approval” actions, clauses do not get assembled and associations do not get populated in the agreement document.

As part of our continuous effort to provide flexibility to ICI users and improve the user experience, a key “Core.Agreement.EnableDynamicClauseAssemblyPostCreate” has been introduced.&nbsp;

*If the key is enabled, when an associated document is uploaded, the entire document will be automatically assembled (Clause, Attribute, Associations, Saved Search) on the “Assemble Contract” and “Send For Approval” actions.  

*If the key is not enabled, the ICI document will be assembled on “Publish” and “Edit Agreement” actions. Only associations will be assembled on the “Assemble Contract” and “Send For Approval” actions.  

<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span>

Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to refresh on these actions and improve usability automatically.

<span style="color:#800080;">'''850259 – Updating logo and ICM to new guidelines'''</span>

As part of our new branding, “ICM” has been updated to “ICI”, and the new logo has also been added to the mobile app.

<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span>

Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.

<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span>

With this release, the UI WebView component for iOS has been deprecated.

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

This is applicable for visualizing, retrieval, creation, and updating of instances of the following entities:

New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.

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

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

A new service bus topic has been created to publish messages about workflow operations. The messages will notify if any failures are encountered during workflow actions.

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

Users will now get a definite response with required details of the error and cause on the service bus. Based on the topic notification, integration developers can take follow-up actions based on success and failure.

<br/> <span style="color:#800080;">'''660859 – Supporting TrackingId in APIs'''</span>

To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;

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

*Users will receive the “TrackingId” provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will be returned).

*The called API path with the query string will be logged in Kibana. In Kibana, developers must look for “CorrelationId” which maps the “TrackingId” used in the API.<br/> &nbsp;

 

 

 

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

Multiple filters can now be configured at the clause and template level to help users easily retrieve relevant data. This improves usability for customers having a large number of clauses and templates in their clause and template library.

*Filter and search clauses and templates by clause metadata in the clause and template library respectively.  

<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 and allows users to review and take corrective actions on them, and assess the risk when negotiators accept these exceptions. &nbsp;

The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word.&nbsp;

*Negotiators can easily review the playbook exceptions found in deviated agreement clauses on the “Agreement Clause” page. &nbsp;

*As AI may not be able to find all the playbook positions for a type of a contract, an option has been added to view all playbook positions for a selected type of contract, with options to search and filter within, so that negotiators have a ready reference for all applicable playbook positions while reviewing the contract.

*Negotiators can view all the applicable playbook positions for a selected agreement clause.&nbsp;  

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

<br/> <br/> <span style="color:#800080;">'''539492 – Rearranging discovered clauses'''</span>

<span style="color:#800080;">'''727312 – Clause hierarchy discovery in text PDFs'''</span>

In the previous release, clause hierarchy discovery was introduced in well-formatted .docx agreements.

Clause discovery processor is now trained to identify sections and sub-sections in Word and PDF documents up to 3 levels. Support for formatting-based clause delineation has also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in a hierarchical format.

<span style="color:#800080;">'''727314 – A generalized framework to support additional languages in AI apps'''</span>

With this release, a language framework has been implemented for AI discovery which can support a large number of languages. Using this generalized framework, DiscoverAI, NegotiateAI, and DiscoverAI for legacy apps have been enhanced to support additional European languages – French, Dutch, Norwegian, and Swedish.&nbsp;

<span style="color:#800080;">'''514593 – Introducing the&nbsp;Tagged Attributes Report'''</span>

With this release, a new “Tagged Attributes Report”, has been introduced which helps administrators understand the complete profile of an attribute and how it has been tagged across different clauses and templates. This provides them better visibility into attribute usage and saves them considerable time.

<span style="color:#800080;">'''769602 – Displaying clause extension attribute summary in the Clause Summary Report'''</span>

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

In this release, the report is being enhanced to display “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 of the clause extension attributes. The “Clause Extension Version Summary” will display the latest values of clause extension attributes.&nbsp;

<br/> <span style="color:#800080;">'''514611 – Introducing the&nbsp;Notifications History Report'''</span>

The default 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. This report displays a list of notifications sent for an entity, including details such as the event that triggered the notification, the message body, subject, the To, CC, BCC recipient names, and email addresses, along with other details such as the attachment filename or sent date and time.&nbsp;

<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 514611.png|720px|514611]]</div>

With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas:&nbsp;

*Contract type names, if the respective entity has locale resource key values in the database.&nbsp;

*Drop-down with Yes/No values.  

*Graph and Time zone tooltips, if present in the report.

*Informative messages such as “No data available”. &nbsp;

<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span>

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;

<br/> This filter is now 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>

The “Cycle Time Report” displays the cycles for contract requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&nbsp;

With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.

<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>

With this release, the user creating a PowerBI report can hyperlink the "Agreement Code" using conditional formatting with the Web URL option, so that on clicking an agreement code, the user is navigated to the corresponding agreement in ICI.

Signing agreements is often a combination of manual signatures and electronic signatures. ICI now provides a unified flexible signature workflow to its customers, thus improving the overall turnaround time and reducing the efforts of printing and scanning manually signed documents.

*The hybrid signature process has been introduced that allows the usage of manual and electronic signature modes in a single transaction.  

'''Note: '''If the DocuSign console is enabled, then the user has the provision to tag the signatories after manual signatures.&nbsp;For other signature modes, ICI relies on the provisions facilitated by your signature provider.

 

*The DocuSign console has been enabled with ICI that allows users to:  

 

<br/> &nbsp;

 

<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>

 

<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 641289.png|720px|641289]]</div>

<br/> <span style="color:#800080;">'''701825– Supporting multiple vendors for electronic signature'''</span>

 

 

 

Users now have the flexibility to:

 

<span style="color:#800080;">'''751651 – Publishing success/failure notification message on ASB post data sync from Salesforce'''</span>

Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any agreement document changes.

With this release:

*Document assembly or notification to third party applications can be triggered by consuming the notification message posted on Azure Service Bus (ASB) via custom task implementation. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”.  

*Upon completion of data sync for an opportunity, the Salesforce data sync task raises a “Data Sync Passed/Failed” event on the ASB upon completion of data sync for each ICI entity related to the given opportunity. The message posted on ASB will display details such as Opportunity ID, ICI entity SysId and time stamp, among other information.  

<span style="color:#800080;">'''796155 –&nbsp;Enhancements to the data flow between Salesforce/MS CRM and ICI'''</span>

Previously, when changes were made to any Salesforce entity, then the data would sync in all related ICI contracts/requests, irrespective of their state in ICI. For example, contracts in the "Waiting For External Signature" state would not be updated via ICI UI but would get updated via data sync.

With this release:

*Changes made to a record of an entity (for example, “Opportunity”) in Salesforce will not sync to corresponding ICI contracts if they are in “Waiting For External Signature”, “Waiting For Internal Signature” or “Expired” states.&nbsp;

*The data will sync only for tracking attributes if the contract is in the "Executed" state.&nbsp;

These enhancements to the data flow, done for configurability and consistency with the ICI user interface, will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.

<br/> <span style="color:#800080;">'''674469 – Generating ICI notifications and enhancing Salesforce data sync'''</span>

An alert mechanism is introduced for monitoring success and failure in Icertis Experience for Salesforce integrations, using ICI/Email notifications, so that end-users get notified about success/failure in data sync.&nbsp;

With this release:

*Customers will get success/failure ICI notifications for data sync as well as reverse sync. If there are any failures/exceptions in the sync process (data/reverse), the system will retry the respective operation, based on the configured retry count.&nbsp;

<br/> <span style="color:#800080;">'''679797 –&nbsp;Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use'''</span>

With this release, support is provided for JWT (JSON Web Token) Bearer OAuth, a secure authentication and authorization process. This makes the ICI integration with Salesforce more secure as the actual “Modified By” user from Salesforce is set as “Modified By” user in ICI for the corresponding ICI records during data sync.&nbsp;

When entities in Salesforce are updated by a user, the process builder sends a message to the ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&nbsp;

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

== Known Issues ==

[[File:7.15 Release - Known Issues.PNG|720px|7.15 Release - Known Issues]]

 

 

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