= ICI Release Notes - Release 7.15 =

The key enhancements of this release include:

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

***To ensure that the agreement document is generated with the correct clauses and metadata we now have the ability to preview an agreement from the pre-draft stage to the Approved stage, enabling a comprehensive review before publishing the contract.&nbsp;

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

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

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

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

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

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

**Introducing the “Notifications History Report” for an entity, enabling users to track what notifications were sent to which recipient and when. This provides better visibility and compliance for the users.

**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.

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

**Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis. &nbsp;

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

***Enabling ICI platform to support more than one E-signature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.  

***Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process.&nbsp;<br/> &nbsp; 

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

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

**Enhancing ICI to allow Administrators to promote additional configurable entities from pre-production to target environments. These include organizations and organization groups, users and user groups, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings, global and admin saved searches 

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

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

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

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

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.

'''Note: '''This functionality is configurable. It is not available by default and can be enabled or disabled for chosen contract types.

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

Hence, the ability to create association instances as part of agreement creation or update wizard is being introduced in this release. A separate page is displayed, when creating or updating the agreement or amendment, for the user to create, view, or delete inline associations. The user also has an option to select the columns and their order in the association grid.&nbsp;

This new page also supports page navigation. Support is also provided to copy attribute rules, association events, and agreement assembly, in case associations are tagged in the agreement template.

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

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.

Users can see localized reason codes as per their preferred language settings.&nbsp;

The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.

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

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

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 “Association” tab for the contract request. The access privileges for the contract requests termination process is controlled through role action mapping.

&nbsp;

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

ICI’s collaboration portal allows external users with login privileges to access the platform and perform 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.

<span style="color:#800080;">'''514605 – Supporting extended clause attributes in agreements'''</span>

In ICI, users can capture additional details for a clause in extension attributes. With this release, users can view these clause extension attributes on the agreement entity for easy reference while working with agreements.&nbsp;

*Select and save extension attributes to display in the grid view, via the “Default Search” column functionality.

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

*View the hyperlink “Show Clause Information”, which displays all clause extension attributes along with clause attributes, in the same window.<br/> &nbsp;

<br/> <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 the 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;

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

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

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

*Approvers can approve/reject the agreement or amendment from the email, only if the task approval or review is assigned to them. Based on the access, the user can approve or reject the agreement by entering notes or reasons for rejection respectively.<br/> &nbsp;

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

To improve the user experience, clauses are now displayed in the same order in the agreement document as they are tagged inside the agreement, on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.

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

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

*Define and update clause groups.

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

*Search agreement records or clauses on the index page on clause group attributes with added values.<br/> &nbsp;

<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 users can use them in search filters, notification rules while configuring saved searches, and so on.

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

Users may need to terminate agreements in bulk in many business scenarios such as regulatory changes, changes in product offerings, and so on. Users can now initiate 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;

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

*Generate and view a status report for agreements terminated in bulk.&nbsp;

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

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

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

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

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

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

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

Users can now:&nbsp;

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

*View all selected values at the top of the drop-down.  

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

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

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

Configurators can now:&nbsp;

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

*View the applied filter on the “Attributes” page on the UI for the selected attribute.&nbsp;

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

ICI now provides administrators 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 of setting up the ICI account with required parameters after the first log-in and presents the system with appropriate and specific pre-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 modifications details in the “History” tab for audit.&nbsp;

*Search users based on parameters related to preference settings.  

Users can:&nbsp;

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

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

Users can then search or create a saved search for such agreements and upload the required documents later using the “Upload Fully Signed Copy” action. Notifications can be configured to inform users about skipped document uploads, so that users can cover for delays occurring due to the scan and upload process while executing a large volume of documents.&nbsp;

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

In addition to the main agreement document, users can now also 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.

With this release:

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

**The type of notification as internal or external.&nbsp;  

**The type of associated document instance as internal, external, or restricted.  

*Based on the type of notification and type of tagged associated documents, attachments are added to the email notification.<br/> &nbsp;

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

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

Users can select configurable peer linkage type labels in the “Linkage Type” drop-down list and view them on various ICI functionalities such as: &nbsp;

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

*Broadcast – “Attachments” tab and captured notes.  

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

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

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

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

ICI now provides the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. Configurators 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. Users can then copy these defined attribute values from base agreement to amendment during amendment creation.&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 level.

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

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

The administrator can control the supersede functionality for agreements by:

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.

<span style="color:#800080;">'''615293 – Showing or hiding the No Team Available message'''</span>

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

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

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

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

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

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

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

*Support conditional expressions for extension attributes. &nbsp;

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

*View the conditional attribute value according to the value entered in the attribute on which a condition is set.  

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

To provide a better user experience and ease of use, faceted filters using string operators, such as “Contains”, “Exactly”, “Starts With” and “Does Not Contain” are being added to the “Business Status” filters.<br/> &nbsp;

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

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

<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 the hundreds to thousands of templates and clauses.&nbsp;

With this release, automation has been provided for bulk import using the “Legacy Upload” tool, 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.<br/> &nbsp;

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

'''Note:&nbsp;'''This is not applicable for contract requests, agreements, 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.&nbsp;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>

Previously in ICI, attribute names did not support special characters apart from _ (underscore), & (ampersand), and space.&nbsp;

Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash), : (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;

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

Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export.&nbsp;<br/> &nbsp;

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

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

*The checkbox list for multi-select choice attributes.  

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

While agreements go through various signature states till executed, users can now navigate to the “Versions” tab and easily identify which version of the agreement is internally signed, externally signed, or fully signed.

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

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

'''Note: '''By default, the key is set to false.<br/> &nbsp;

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

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

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

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

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

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

*Associations  

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>

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

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

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:

 

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

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

 

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

 

This can be used for:

 

</div>  

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

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

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

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

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

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

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

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

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

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

 

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

 

 

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

*Perform free text search on clauses and templates.  

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

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

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

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

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

== Enhancements to Artificial Intelligence Applications in ICI ==

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

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

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

Users can now:&nbsp;

*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &nbsp;

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

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

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

Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&nbsp;

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

Users can now:&nbsp;

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

*Create a sub-clause within a discovered clause.&nbsp;

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

*Choose to view only the level 0 clauses.  

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

Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&nbsp;

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

Users can:&nbsp;

*View the discovery completion progress.&nbsp;

*Identify discoverable attributes marked with the spinner icon.  

*Get side-by-side document view for discoverable attributes.  

*Get side-by-side document view for tagged attributes upon completion of discovery.  

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

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

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 now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.

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

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

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

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

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

Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&nbsp;

With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&nbsp;

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

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

With this release, a new “Tagged Attributes Report”, 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.

This report, available on the “Reports” tile, can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable, Attribute tagged as Clause Extended Attribute and Attribute Display Name

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

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

ICI administrators can set up subscriptions for different entities, for notifications to be sent to subscribed users at the occurrence of certain events. Notifications can also be sent using the broadcast functionality. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity.&nbsp;

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

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.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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

 

 

 

 

 

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

 

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

 

 

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

 

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

 

 

 

 

'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|