ICI Release Notes - Release 7.15[edit]


= ICI&nbsp;Release Notes - Release 7.15 =

== <span style="color:#800080;">Overview of Release 7.15</span> ==

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

The key enhancements of this release include:

*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span> 
**'''''User Experience''''' 
***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. 
***Providing &nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. 
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. 
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. 
***Viewing amendments in the grid view by default, for ease of use. 
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. 
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. 
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   
**'''''Workflow Enhancements''''' 
***Introducing &nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. 
***Allowing &nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. 
***Viewing clause extension attributes on the agreement entity for easy reference. 
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. 
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. 
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&nbsp; 
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &nbsp; 
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. 
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. 
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. 
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &nbsp; entities with one or more users, by selecting a subset of an entity &nbsp; or on all instances of the entity, for all records available for the user. 
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. 
***Providing the capability to control the supersede functionality for agreements by configuring rules. 
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. 
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. 
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. 
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. 
***Supporting larger files for masterdata and associations. 
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. 
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. 
***Providing the ability to configure filter on a lookup attribute &nbsp; with the “IN” operator on agreement contract type and template variables.&nbsp; 
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. 
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. 
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     

*<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. 
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   

*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span> 
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. 
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. 
**Provisioning success or failure message for workflow operations.   

*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span> 
**'''''Icertis Experience for Word''''' 
***Supporting &nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. 
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. 
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. 
***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp; 
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. 
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     

*<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. 
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. 
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. 
**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; 
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. 
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. 
**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> 
**'''''Signature Workflow''''' 
***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;   
**'''''Icertis Experience for Salesforce''''' 
***Providing the ability to send success and failures alerts for improved monitoring of messages. 
***Triggering document assembly for automatic data sync and displaying completion notification. 
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   
**'''''Icertis Experience for MS CRM''''' 
***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> 
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   

*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span> 
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   

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

&nbsp;

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

<span style="color:#800080;">'''659853 – Upfront chevron view of agreement journey'''</span>

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;

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;

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.&nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.

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;

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

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

'''Note''':&nbsp;

*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">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''512931 – Visibility of sections on the left navigation pane to non-team users'''</span></div> 
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;

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;

<span style="color:#800080;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>

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. 

Users can:&nbsp;

*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">&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/> &nbsp;</div> 
<span style="color:#800080;">'''584439 – Introducing the Contract Manager role for agreements&nbsp;'''</span>

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

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

With this release:&nbsp;

*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. 
*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 agreement''Team'' tab similar to primary owner role user. 

&nbsp;

<span style="color:#800080;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>

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;

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

&nbsp;

<span style="color:#800080;">'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''</span>

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.&nbsp;
<div class="image-green-border">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> <div class="image-green-border">This is applicable to the following associations:&nbsp;</div> 
*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.

&nbsp;

<span style="color:#800080;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>

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

Users can now:&nbsp;

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

&nbsp;

<span style="color:#800080;">'''583186 – Ability to add amendment on expired agreement'''</span>

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

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">&nbsp;</div> 
<span style="color:#800080;">'''593928 – Ability to configure sender email ID for automated emails'''</span>

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

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. 
<div class="image-green-border">&nbsp;</div> 
<span style="color:#800080;">'''593938&nbsp;– Time Zone support for date-dependent automated processes'''</span>

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.

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''':&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">&nbsp;</div> 
<span style="color:#800080;">'''512930 – Triggering service bus events for all actions'''</span>

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;

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

<span style="color:#800080;">'''545126 – Availability of business status value in ICI event messages'''</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.

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.

&nbsp;

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

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

&nbsp;

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

&nbsp;


== <span style="color:#800080;">ICI API Enhancements&nbsp;</span> ==
<div class="image-green-border">
<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;

This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:

*Contract Requests 
*Agreements 
*Associations 
*Amendments 

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

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

&nbsp;

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

Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.

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

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

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:

*Provided support for a Tracking Id header in every request for logging.&nbsp; 
*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:

*Related API Calls 
*Async operations 
*Bulk operations 
*Status check operations &nbsp; &nbsp; 

<br/> &nbsp;
</div>

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

<span style="color:#800080;">'''714872 – Improved document usability'''</span>

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;

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.
<div class="image-green-border">With this release:</div> 
*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">'''Note''':&nbsp;</div> 
*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. 

&nbsp;

<span style="color:#800080;">'''660390 – Ability to show more clauses per group'''</span>

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.
<div class="image-green-border">&nbsp;</div> 
<span style="color:#800080;">'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''</span>

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.
<div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''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.

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">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''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">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''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> 
&nbsp;

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

<span style="color:#800080;">'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''</span>

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.

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.
<div class="image-green-border">Negotiators can now:</div> 
*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">By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.</div> 
<br/> <span style="color:#800080;">'''575450 – Supporting clause hierarchy in .docx agreements'''</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.

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;

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

<span style="color:#800080;">'''663666 – Enhancing inbuilt discovery model to include additional attributes&nbsp;'''</span>

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;

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;

<span style="color:#800080;">'''575466 – Support for additional languages in AI apps&nbsp;'''</span>

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

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. 

&nbsp;

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

<span style="color:#800080;">'''514594 – Capability of time zone in reports'''</span>

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:#800080;">'''514609 – Introducing the Clause Summary Report'''</span>

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;

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.

&nbsp;

== <span style="color:#800080;">Integrations</span> ==

<span style="color:#800080;">'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''</span>

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

Salesforce users can now:&nbsp;

*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&nbsp; 
*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">&nbsp;</div> 
<span style="color:#800080;">'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''</span>

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

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;

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.

&nbsp;

<span style="color:#800080;">'''635822 – Support for pre- and post-processing in Generic Integration Framework'''</span>

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;

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

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

&nbsp;

<span style="color:#800080;">'''635823&nbsp;– Support for defining folder structure in Generic Integration Framework'''</span>

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

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

== <span style="color:#800080;">ICI Platform Tools</span> ==

'''<span style="color:#800080;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''

With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.<br/> The following entities are now supported:

*Organizations (Orgs), Organization Groups (Org Groups) 
*Users, User Groups, Security Groups 
*Role Action Mapping 
*Currencies 
*Reasons 
*Attribute Group 
*SLA Matrix 
*Notification Category 
*Default Search Columns 
*Cascade Team 
*Application Settings 
*Global/Admin Saved Searches 

'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.

&nbsp;

== <span style="color:#800080;">Partner Enablement</span> ==

<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>

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 the resources and tools needed while implementing ICI.&nbsp;

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

*ICI Coding Guidelines (version 2):&nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. 

*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. 

*Working with ICI Tasks: Updated for the 7.15 release. 

*Working with ICI Hooks:'''Updated for the 7.15 release. 

*ICI Developer Library: Updated for the 7.15 release. 

*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. 

*Self-Serve Tools:'''Updated for the 7.15 release. 

&nbsp;

== <span style="color:#800080;">Technical Requirements for Release 7.15</span> ==

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.

[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]

[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]

[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]

[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]

[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]

&nbsp;

&nbsp;

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