From ICIHelp8.2
Jump to: navigation, search
Line 1: Line 1:
  
−
 
+
 
  
 
= ICI Release Notes - Release 7.16 =
 
= ICI Release Notes - Release 7.16 =
Line 6: Line 6:
 
== List of Enhancements 7.16 ==
 
== List of Enhancements 7.16 ==
  
−
The 7.16 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance the user experience, intelligence, analytics, intuitiveness, and usability by continually improving the user interface and functionalities.
+
The 7.16 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. Key enhancements include new AI and Analytics capabilities, User Experience updates, and Contract Workflow and Localization features.
  
−
The key enhancements of this release include:
+
The enhancements of this release include:
  
 
*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>  
 
*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>  
 
**'''''User Experience'''''  
 
**'''''User Experience'''''  
−
***To ensure that the agreement document is generated with the correct clauses and metadata, we now can preview an agreement from the pre-draft to the Approved stage, enabling a comprehensive review before publishing the contract.&nbsp;  
+
***Enabling users to create associations from directly within the contract request creation wizard. File-drag-and-drop functionality is also enabled while creating associations within agreement creation wizard to reduce the number of clicks required and save time.&nbsp;  
−
***Improved usability for the global user base and their individual user interface (UI) language preferences via expanded localization coverage which now includes support for localized “Reason Codes”.  
+
***Improving usability by extending document preview to custom file selection attributes on entity’s Summary, Details and Verify pages. Also, the preview for associations is extended to .ppt, .pptx, .msg and images (.jpg, .jpeg, .png and .gif) file formats along with .docx and .pdf files.  
−
***Friction-free collaboration enabled via the Collaboration Portal’s external UI which now enables external users to search contract requests, agreements, associations, and masterdata records.&nbsp;  
+
***Improving the Legacy Upload tool for a better User experience and reduced manual intervention with auto generation of workbook, support for peer associations, linkage type and sub folder structure and various other related improvements.&nbsp;  
−
***Improved document review process where the display order for clauses in the ICI web and Icertis Experience for Word match the order in which the clauses are configured in the respective template and generated agreement. &nbsp; &nbsp;  
+
***Extending dual language template capability with options of rule-based auto assembly in secondary language in accordance with the content in primary language. &nbsp; &nbsp;  
−
***Improved usability whereby the attribute multi-selection interface, when creating an agreement, can be configured as either radio buttons or checkboxes to tailor the agreement creation experience per the contract type.&nbsp;
+
***Enhancing the existing localization capability to support additional UI components such as entity statuses/business statuses, choice/multi-choice attributes, signature sequence among others, as per logged in user’s language preference.&nbsp;  
−
***Amendments to an agreement are now viewable in the “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;  
+
***Creating a base for supporting context-based translations across ICI.&nbsp;  
−
***Improved usability where the sequence of values displayed in a masterdata lookup drop-down can now be configured to have the most frequently accessed values available at the top of the list.&nbsp;    
+
***Providing the capability to carry out delete and update operations to help Administrator users to fix data inconsistencies using a self-serve Data Management utility.  
−
 
+
***Enhancing bulk actions on saved searches to provide better process visibility with notifications and validation messages.  
−
*'''''Workflow Enhancements'''''
+
***Improving the ICI out of office delegation functionality to support multi-level and conditional delegations with the sequencing capability to create complex delegation structures and help users manage tasks more efficiently.  
−
**Improved usability including the ability to create instances of associations as part of the agreement creation wizard itself.  
+
***Enabling filtering capabilities for selecting users on contract requests and agreements using the lookup to extended user entity and fulfill specific business requirements.  
−
**To continue bringing Extension Attributes capabilities at par with regular attributes, these are now quickly viewable for easy reference in the agreement entity’s “Agreement Clauses” tab.
+
***Enhancing the auto-attachment capability to support associated document contract types with non-mandatory attributes.  
−
**Agreements can be Approved or Rejected from within an agreement notification email itself making it faster to take actions on an agreement and reducing turnaround time for approval cycles.&nbsp;
+
***Allowing users to configure a file selection attribute as read-only on the UI using attribute property and have more control over the file access, further safeguarding uploaded documents.  
−
**Expanded contract request experience now includes the ability to request Contract Terminations.
+
***Displaying clause comments along with clause text while assembling a rule-based clause in an agreement, enhancing the collaborative experience among users.  
−
**Bulk actions support is now extended to Terminating agreements in bulk to support situations that require it, such as regulatory changes, or business partner insolvency. &nbsp;
+
**'''''Workflow Enhancements'''''
−
**To save time when re-instantiating a terminated agreement, due to reasons such as reviving a business relationship, you can now do so by simply adding amendments to the terminated agreement rather than by having to create a new agreement from scratch.
+
***Providing users the ability to set the minimum approvals requirement from selected ad-hoc user groups to qualify agreement as approved, thereby accelerating approval process.    
−
**Simplified administration of the first-run default user preference which can now be pre-set or updated for users based on their location or department.  
+
−
**Simplified signature status labels such as “External”, “Internal,” and “Fully Signed” are now shown in agreement versions.
+
−
**Enhanced flexibility when executing a large volume of contracts by not requiring the immediate upload of documents to change the status to “Executed” for manual signatures. Instead, the agreement status will change from “Waiting For Signature” to “Executed – Pending Signed Document”.
+
−
**Enabling sharing of Associated Documents as well via the email notifications that are triggered for an agreement.
+
−
**For organizational changes or employee turnover, we now provide a data management interface that enables replacing users with multiple users on supported agreement entities.
+
−
**Support for granularly defining which agreement attributes for a given contract type should be cascaded to the agreement’s amendment via the “Is Inherit On Amendments” flag at the agreement contract type and template variable levels.  
+
−
**In addition to the currently available functionality of all attributes to be superseded capability, we now offer the ability to selectively supersede an attribute through rules.&nbsp;
+
−
**Conditional attributes’ comparison operators now support multiple complex conditions to dynamically display attributes based on a range of business scenarios.  
+
−
**Simplifying agreement workflow navigation by enabling the option to show a “No Team Available” message during workflows when a team is not needed.
+
−
**Expanded support for special characters in the Attribute display name for contract requests, agreements, associations, and masterdata.  
+
−
**Download amendments with the corresponding parent and child associations in a zip package with corresponding sub-folders.&nbsp;
+
−
**Larger file size support when uploading (4GB) and downloading (6GB) files for masterdata and associations.&nbsp;
+
−
**Boost smart filter creation using string operators such as “Contains”, “Starts With”, or “Does Not Contain” for the “Business Status” search facet.
+
−
**Expanded support for automating the bulk upload of clauses and templates reducing the dependency on manual approvals and delays in onboarding clauses and templates.
+
−
**Enhanced configurable labels for peer associations that define the contractual relationship (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.). 
+
  
 
&nbsp;
 
&nbsp;
  
−
*<span style="color:#800080;">'''Mobile App Updates'''</span>  
+
*<span style="color:#800080;">'''Mobile App Enhancements'''</span>  
−
**Enhancing the “Refresh” functionality for “Tasks” and “Commitment” tabs to continually show the latest changes in the status for mobile app users.   
+
**Updating the theme color as per new Icertis branding.   
  
 
&nbsp;
 
&nbsp;
  
 
*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>  
 
*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>  
−
**Providing support for the script and integrated attributes as cascaded attributes for lookup fields when configured at the contract type level. This is applicable for retrieval, creation, and update of the instances of contract requests, agreements, associations, and amendments.  
+
**Adding new API endpoints to add/remove/get teams as well as add/get notes for associations.  
−
**Adding the identifier “TrackingId” which can be passed by subsequent API calls for logging and troubleshooting errors.
+
**Adding filters to the Get Users API response for users to be able to fetch desired records in a shorter time frame.  
−
**Adding support for troubleshooting API issues with failure notifications. &nbsp; 
+
**Announcing deprecated APIs and their provisioned alternatives. &nbsp;  
−
 
+
−
&nbsp;
+
−
 
+
−
*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>
+
−
**'''''Icertis Experience for Word'''''
+
−
***Improving the filtering and searching capability which now supports searching text inside clauses or templates to allow more powerful deep searches especially when searching across large libraries.  
+
−
***Improved labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
+
−
***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;    
+
  
 
&nbsp;
 
&nbsp;
  
 
*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>  
 
*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>  
−
**Multiple enhancements to the AI-powered legal playbook capabilities:
+
**Introducing AI studio to analyze multiple set of documents in a go, generating analytics to enable real time decision and actions.  
−
***Improved usability by enabling larger window views of the “Details” page, including deviations.  
+
**Introducing self-serve AI to create your own AI models and train them. Administrators can define new attribute, clause or obligation to be discovered and include them in an AI model. ICI’s AI engine would learn the patterns from user feedback and recommend the attribute value in subsequent discoveries.  
−
***All the playbook positions for a contract type now have the option to search and filter.  
+
**Extending DiscoverAI clause delineation support to text PDF, mixed formatted .docx files and for documents in languages other than English. It also identifies document objects such as titles, table of contents, signature blocks, headers, and footers and separates them from the clause text.  
−
***Administrators can create a new playbook record or update an existing one from within Icertis Experience for Word itself.  
+
**Enhancing the AI engine so that it learns the clause or obligation category changes made by the user and identifies the correct category next time onwards.   
−
**Improving the clause delineation logic so that users can rearrange the AI-identified clause boundaries. You can now merge or split discovered clauses or selected text in a clause and also create sub-clauses within the discovered clause.  
+
−
**Extending the clause hierarchy discovery feature to support text PDFs in addition to .docx documents.&nbsp;
+
−
**Improving library clause recommendations for discovered clauses based on learnings from user’s actions in previous discoveries.&nbsp;
+
−
**Providing support for additional languages including “French”, “Dutch”, “Norwegian” and “Swedish” in AI apps.
+
−
**Enabling users to flexibly leverage AI on-demand by manually triggering attribute discovery on an agreement from the “Attributes” page to accelerate workflows. The discovered values will be auto-filled in empty attributes, instead of redundant manual entry.  
+
−
**Enhancing and optimizing the performance of Machine Learning services to simplify deployment and run the workload on-demand while significantly reducing infrastructure management needs.   
+
  
 
&nbsp;
 
&nbsp;
  
 
*<span style="color:#800080;">'''Enhancements to Reports'''</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.  
+
**Introducing Platform Analytics that merges a range of Power BI reports within the ICI core reporting, enabling users to leverage Microsoft Power BI capabilities for customized report creation.  
−
**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 conformity for the users.  
+
**Introducing the AI Studio Report which displays the result of the AI studio batch, helping users to quickly comprehend discovery results and take informed decisions.  
−
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.
+
**Enhancing the core reporting capability with the ability to add, edit and delete attributes to provide better visibility in reports.  
−
**Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.
+
**Introducing the AI Model Training Performance Report enabling users to view the improvements in the discovery performance over a period of time.  
−
**Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis.&nbsp;
+
**Improving user experience by enabling localization for business statuses, choice/multi-choice attributes, signature sequence, among other elements in reporting.   
−
**Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.  
+
−
**Multiple localization enhancements within reports.   
+
  
 
&nbsp;
 
&nbsp;
  
 
*<span style="color:#800080;">'''Improving the Icertis Experience'''</span>  
 
*<span style="color:#800080;">'''Improving the Icertis Experience'''</span>  
 +
**'''''Icertis Experience for Workday'''''
 +
***Providing users the ability to create associations using purchase order and invoice entity data. 
 
**'''''Signature Workflow'''''  
 
**'''''Signature Workflow'''''  
−
***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).  
+
***Improving the electronic signature process when using Adobe Sign to provide a unified, flexible signature workflow. This hybrid (manual and/or electronic) signature process enables users to add, modify and/or tag signatories, change signatory sequence and specify authentication methods for the signatories.  
−
***Enabling the ICI platform to support more than one E-signature vendor at the same time, to execute agreements and amendments, thus improving flexibility for users.  
+
***Providing the ability to send associated documents for signature along with agreements when using Adobe Sign.  
−
***Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process.&nbsp;
+
***Increasing the text limit for email subject lines to 255 characters, when sending documents for signature using Adobe Sign.  
−
***&nbsp; 
+
***Providing users the flexibility to update effective and expiry dates while uploading the manual signed copy of an agreement/amendment.   
−
**'''''Icertis Experience for Salesforce'''''
+
−
***Providing the ability to send success and failure 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.<br/> &nbsp;    
+
 
**'''''Icertis Experience for MS CRM'''''  
 
**'''''Icertis Experience for MS CRM'''''  
−
***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.     
+
***Enhancing the Icertis Experience for Microsoft Dynamics CRM to improve user experience. 
 +
**'''''Icertis Experience for Generic Integrations'''''
 +
***Enhancing file and ASB based integrations to support provisioning, deprovisioning and reprovisioning both internal and external users.
 +
***Enhancing SFTP based integrations to support inbound integration for agreement, amendment and association entities.   
 +
 
 +
&nbsp;
 +
 
 +
*<span style="color:#800080;">'''Enhancements to Platform Tools&nbsp;'''</span>
 +
**Enhancing ICI Promote to Production (P2P) framework to allow Administrators to promote configuration on different ICI patch versions for a major release (assuming no schema changes). Also enhanced robustness of the tool with provisions for automated fixes for known P2P validation errors, better display of progress status and ability to resume P2P activity from the last successful step in ICI UI. 
 +
 
 +
*<span style="color:#800080;">'''Enhancements to Business Applications&nbsp;'''</span>
 +
**Sourcing
 +
***Introducing One-Click Download on Download Package window, enabling users to download specific files relevant to a RFx in a single click. 
 +
**Risk Management
 +
***Certifying the ICI Risk Management application to work with the 7.16 release. 
 +
**Obligation Management
 +
***Introducing the Obligation Library, providing users the ability to automatically create obligations.     
  
 
*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>  
 
*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>  
−
**
+
**With this release, the following SDK documents have been updated: ICI Technical Configuration Hooks and Self-Serve Tools.  
−
***With this release, the following SDK documents have been updated – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, and Self-Serve Tools.<br/>     
+
  
 
These release notes provide an overview of the enhancements to ICI, the mobile app, the ICI experience for integrations, and so on.
 
These release notes provide an overview of the enhancements to ICI, the mobile app, the ICI experience for integrations, and so on.
Line 117: Line 99:
 
<span style="color:#800080;">'''704597 – Extending inline association support for contract request and introducing file drop functionality in inline association'''</span>
 
<span style="color:#800080;">'''704597 – Extending inline association support for contract request and introducing file drop functionality in inline association'''</span>
  
−
ICI enables users to create association instances as part of agreement creation or update wizard. When creating or updating an agreement or amendment, users can create, view, or delete inline associations. With this release, this inline associations functionality has been extended to contract request creation/update wizard as well. The users can create, view or delete associations while creating or updating the contract requests. The file drop functionality available on the associations grid of the agreement details page has been extended to inline associations grid in agreement as well as contract request creation wizard. The inline association functionality now supports dynamic associations for agreements, amendments and contract requests.
+
ICI enables users to create association instances as part of agreement creation or update wizard. When creating or updating an agreement or amendment, users can create, view, or delete inline associations.&nbsp;<br/> With this release, this inline associations functionality has been extended to contract request create/update wizard as well. The users can create, view or delete associations while creating or updating the contract requests.<br/> On a separate note, a file drop zone similar to the one in agreements, has been made available on the contract request details page for the configured associated document. This file drop functionality has also been extended to inline associations grid in agreement as well as contract request creation wizard. The inline association functionality now supports dynamic associations for agreements, amendments and contract requests.
  
 
<span style="color:#800080;">'''421708 – Extending preview support for additional file formats'''</span>
 
<span style="color:#800080;">'''421708 – Extending preview support for additional file formats'''</span>
  
−
As a part of our upgrading and upscaling process, the document preview facility has been extended to support custom file selection attributes appearing on the various UI screens. Users can now preview documents uploaded though custom and system file selection attributes as the entity goes through workflows stages, for an easy and quick reference. Furthermore, it is now possible to preview associated documents in ppt, pptx, msg and image (tiff, jpg, jpeg, png, gif) file formats along with Word and pdf documents. This saves a big trouble for business users downloading many documents and cluttering their system.
+
As a part of our upgrading and upscaling process, the document preview facility has been extended to support custom file selection attributes appearing on the various UI screens. Users can now preview documents uploaded through custom and system file selection attributes as an entity goes through workflows stages, for easy and quick reference.&nbsp;<br/> Furthermore, it is now possible to preview associated documents in .ppt, .pptx, .msg and image file formats (.jpg, .jpeg, .png, .gif) along with .docx and .pdf documents. This saves efforts for business users downloading multiple documents and avoiding local copies from cluttering their system.&nbsp;
−
 
+
<div class="image-green-border">[[File:7.16 RN SS 01.png|720px]]<br/> The preview option will now be available on the entity “Summary”, “Verify” and “Details” pages for system and custom file path attributes in addition to the “Preview” available from the left navigation pane.<br/> Administrators can configure an option to preview the entire document or limit the number of pages through technical configuration. Preview for large files is not available.</div>
−
The preview option will now be available on the entity “Summary”, “Verify” and “Details” pages for system and custom file path attributes in addition to the “Preview” available from the left navigation pane. Administrators can configure an option to preview the entire document or limit the number of pages by setting the configuration key.
+
−
 
+
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from the contract request'''</span>
+
<span style="color:#800080;">'''842776 – Enhancements to the Legacy Upload tool'''</span>
  
−
To terminate an agreement in ICI, users create and execute a termination agreement on the main agreement instance. This capability is now extended to initiate the termination from contract requests as well.
+
To improve usability and the user experience for our customers, the following enhancements have been made to the “Legacy Upload” tool:&nbsp;
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 6.png|720px|7.15 Release Notes Screenshot 6]]</div>
+
−
Users can now enable the termination process at the contract type level using the seeded attribute "Request for Termination", select the parent contract request, and create the termination contract on a contract request. The termination instance for the contract request will have all the common attribute values inherited if the inheritance is enabled.&nbsp;
+
  
−
The termination record will be displayed as a peer association under the “Associations” tab for the contract request. The access privilege for the contract request termination process is controlled through role action mapping.
+
*Enhanced the User Interface for better usability and self operation mode.  
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 7.png|720px|7.15 Release Notes Screenshot 7]]</div>
+
*Provided support of selecting the required attributes from the attribute select columns with pre-populated mandatory attributes, along with extended entity attributes.&nbsp;
−
&nbsp;
+
*Enabled single-click self-generation of workbook to reduce the number of steps in the process.  
−
 
+
*Provided support for uploading &nbsp;the peer association entity so that they can be uploaded along with &nbsp;existing association of the main agreement and ensure there is no manual work post legacy upload.&nbsp;
−
'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''
+
*Enabled support for Linkage Type to define proper contractual relationship between different records.&nbsp;
−
 
+
*Provided support for uploading records in various states (such as “Terminated”, “Expired”) so that the user does not have to reinitiate the workflow and move it manually to these states.&nbsp;  
−
The Collaboration Portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself.&nbsp;
+
*Capability to support the sub-folders structure so that the segregated document structure is followed in ICI as well.&nbsp;
−
 
+
*Added validation and error messages across ICI that will help users rectify issues themselves quickly and reduce dependency on technical teams.&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.
+
*Capability to process a failed batch again with the corrected records.  
 +
*Provided ability to schedule the batch upload frequency using a configuration key to reduce dependency on the database team.
 +
*Enabled email notification on the batch initiation and completion to the concerned recipient.  
  
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''514605 – Supporting extended clause attributes in agreements'''</span>
+
'''<span style="color:#800080;">817886 – Enhancing dual language template capability in ICI</span>'''
−
 
+
<div class="image-green-border">ICI provides the capability to configure a template in two languages which helps to reduce or eliminate the language barrier and communicate better with regional customers. The capability is now further enhanced to support the rule-based assembly of primary and its equivalent localized secondary clauses in the bilingual template.<br/> Business users can define a template as dual-language and set the template’s primary and secondary languages with the language specific date and time formats. Tagged rule-based clauses will be assembled in both languages of a bilingual template on a single ruleset.<br/> [[File:7.16 RN SS 02.png|720px]]&nbsp;<br/> When a user replaces a primary clause with its alternate clause either from the UI or Icertis Experience for Word, the corresponding secondary clause will also get replaced with its respective alternate clause. Any modification in the standard text of primary or secondary clauses will trigger the standard deviation workflows.</div>  
−
In ICI, users can capture additional details for a clause in extension attributes.&nbsp;With this release, users can view these clause extension attributes on the agreement entity for easy reference while working with agreements.&nbsp;
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 8.png|720px|7.15 Release Notes Screenshot 8]]</div>  
+
−
Users can now:&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 Clauses” and “Clause Approver” tabs.  
+
−
*View the hyperlink “Show Clause Information”, which displays all clause extension attributes along with clause attributes, in the same window.  
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 9.png|720px|7.15 Release Notes Screenshot&nbsp;9]]</div>  
+
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''514615 – Streamlining&nbsp;the approval process over emails'''</span>
+
<span style="color:#800080;">'''791889 – Supporting localized values on user interface as per logged in user’s language'''</span>
−
 
+
−
The approval process has now been streamlined by allowing approvers to directly approve or reject an agreement from within the email itself, through a hyperlink to the webpage, instead of logging in to the system to do so. External users, who do not have access to ICI can now review or approve documents from the notification email, instead of sending offline copies to do so and then uploading them to ICI. This reduces the overall turnaround time and increases productivity.&nbsp;
+
  
−
Internal users are authenticated through the SSO/IDP before opening the page where the actions are to be taken. External users are authenticated by sending them a code in the email, which has limited validity.&nbsp;
+
ICI now extends its localization support to status/business statuses, choice/multi-choice attributes, signature sequence, among other elements as per language preference set by the logged in user.<br/> Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers. In order to achieve this, ICI now extends its localization support to below mentioned UI components to display them in a logged in user’s preferred language:
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 10.png|720px|7.15 Release Notes Screenshot&nbsp;10]]</div>
+
−
With this release:
+
  
−
*Administrators can add tags for an Approve/Reject link in the notification template.
+
*Status and Business Status
−
*Approvers/reviewers can download the agreement, modify it and upload it back to ICI based on the access provided.
+
*Type of paper
−
*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.  
+
*Signature Type and Signature Sequence
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 11.png|720px|7.15 Release Notes Screenshot]]</div>  
+
*Contract Type Choice and Multi-choice attributes
 +
*Contract Type Description
 +
*Search and default text&nbsp;
 +
*Notification Category and Events on Notifications Dashboard
 +
<div class="image-green-border"><br/> Administrators can enter the translated values for these elements in the local language using ICI’s “Translations Editor” tool.<br/> [[File:7.16 RN SS 03.png|720px]]&nbsp;</div> <div class="image-green-border"><br/> Business users can see localized values as per their preferred language settings.</div> <div class="image-green-border"><br/> [[File:7.16 RN SS 04.png|720px]]&nbsp;<br/> The UI elements will be displayed in English if there are no local values available in the system for that specific element.</div>  
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''617385&nbsp;– Ability to define additional clause group under clause entity'''</span>
+
<span style="color:#800080;">'''863795 – Support for context-based translations in ICI'''</span>
−
 
+
−
Previously, ICI supported 3 clause groups – “Termination”, “Legal” and “None”.&nbsp;
+
−
 
+
−
With this release, this capability has been further enhanced so that the configurator can configure various clause group names in ICI. These clause groups can be categorized or grouped as per business requirements for better identification and negotiation during the contract workflow.
+
−
 
+
−
Administrators can now:
+
−
 
+
−
*Define and update clause groups.
+
−
*Edit, delete, activate or deactivate clause group entities.
+
−
*View additionally added clause group values in the clause entity when creating or editing a clause.
+
−
*Search agreement records or clauses on the index page on clause group attributes with added values.
+
  
 +
The same value/term in English appearing on multiple pages across ICI might have different meanings based on the context of the page on which it is used and the purpose for which it is used. For example, the word “home” is translated as “Zuhause” in German, whereas in the context of “home page” it is translated as “Startseite”.<br/> Previously, the same resource key was used for the same term appearing on multiple pages across ICI, whereas the translation of the term differed depending on the context in the different areas of ICI.&nbsp;<br/> With this release, the resource keys are split based on the respective context so that corresponding translated terms appear in the localized ICI version.
 +
<div class="note-box">'''Note''': The resource values have not been changed in the context of the language in the current release.</div>
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''514643 – Ordering of clauses as tagged in an agreement'''</span>
+
<span style="color:#800080;">'''740579 – Provision of self-serve data management tool'''</span>
−
 
+
<div class="image-green-border">Moving one step ahead in the self-service, ICI now allows performing data management activities for entities in all workflow stages.<br/> The data management activities introduced with this release are update and delete operations for Agreements, Associated Documents, Contract Requests, User Information, Files and Attributes. These self-serve data management operations will empower administrative users to troubleshoot data inconsistency issues on their own.</div> <div class="image-green-border"><br/> [[File:7.16 RN SS 05.png|720px]]&nbsp;</div> <div class="image-green-border"><br/> However, users are advised to execute these operations cautiously as the data fix does not go through necessary business validations and are performed directly in the database itself. Furthermore, updating or deleting data through the data management tool cannot be undone and will not trigger any underlying rules, workflows, notifications, triggers or integrations. Therefore, it is recommended to follow standard ICI workflows for any major or entity state modifications.<br/> Note: The type of attributes such as Expressions, Conditional, Multi-select Lookup, Script and System will remain non editable and cannot be updated through data management tool.<br/> By default, the Data Management utility is enabled and can be controlled through the technical configuration.</div>  
−
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.
+
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 514643.png|720px|514643]]</div>  
+
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''514621 – Reviving terminated agreements'''</span>
+
<span style="color:#800080;">'''685700 – Enhancements to bulk action functionality on Saved Searches'''</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.
+
ICI provides users the ability to perform bulk actions on saved searches to efficiently work with entities in bulk.&nbsp;<br/> With this release, this bulk action on saved searches functionality provides enhanced experience as: &nbsp;
  
−
Adding and executing an amendment on a terminated agreement will move the agreement back to the “Executed” or “Expired” state, based on its expiry date, thus reviving the terminated agreement. The system sets an identifier attribute "Is Termination Revived" for such revived base agreements, and they can be used in search filters, notification rules while configuring saved searches, and so on.
+
*Performing validation checks against resubmission of in-progress records for same bulk action and display validation message.
 +
*Sending notifications upon bulk action submission and completion.&nbsp;
 +
*Displaying a toast message on the UI along with the bulk action initiation activity on the activity panel upon bulk action submission.  
  
−
'''Note:''' By default, only primary owners and contract managers can add an amendment to the terminated agreement. The access privileges are controlled through role action mapping.
+
The notification contains a page link which will display the statistics of the processed records and the live updates on in-progress records.<br/> This enhancement will be available with the upgrade and does not require any further configuration.
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 13.png|720px|7.15 Release Notes Screenshot 13]]<br/> &nbsp;</div>
+
−
<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;&nbsp;
+
−
 
+
−
Users can now:&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 actions.
+
−
 
+
−
'''Note:&nbsp;'''All prerequisite configurations applicable for the termination workflow should also be set for the bulk termination process.
+
  
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''555898 – Defining display sequence on lookup attributes at the contract type level'''</span>
+
<span style="color:#800080;">'''788412 – Enhancements to auto delegations'''</span>
  
−
Previously in ICI, users could not define the display order for lookup attribute values in a drop-down menu on the UI that references masterdata. Users had to scroll through all the populated values to find the desired values during agreement creation. &nbsp;
+
ICI users can delegate their tasks for situations such as when they are out of office. These delegation capabilities are now enhanced, and business users can now:&nbsp;
  
−
Configurators can now define and maintain the display sequence for selected masterdata records, starting from 1 to n, at the masterdata contract type level, using a seeded display sequence attribute. The values will thus be displayed at the top for easier and faster selection in lookup attributes. &nbsp;
+
*Set multi-level auto delegations&nbsp;
 +
*Set conditional delegations
 +
*Reorder delegation sequence  
 +
<div class="image-green-border">Utilizing these capabilities, users will be able to create complex delegation structures and manage their tasks more efficiently.<br/> Multi-level delegations allow automatic delegation of user’s tasks to the next delegate in a sequence up to a third level, when the subsequent delegates have also set up delegations overlapping with the selected time period.<br/> Conditional delegations will selectively delegate a user’s tasks to another user based on saved searches. The delegation will take effect only if the set conditions are met.<br/> While setting multiple delegations, users can reorder the evaluation sequence to suit their needs.</div> <div class="image-green-border"><br/> [[File:7.16 RN SS 06.png|720px]]&nbsp;</div> <div class="image-green-border"><br/> The validation messages will be displayed to assist users while setting up auto delegations in cases where a similar delegation already exists, delegation dates overlap, or a delegate is already out of office, so that the user can make appropriate decisions.<br/> Users can view the recently expired 15 delegations which they can reactivate by updating; and reuse while setting up delegations structure.<br/> These enhancements are automatically available with the upgrade and no further configuration is required.</div> <div class="image-green-border">&nbsp;</div>
 +
<span style="color:#800080;">'''789103 – Enhancements to Extended User Entity to support lookup filtering'''</span>
  
−
This display sequence setting is supported on the create, edit, and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause entities, and template variables. The display will follow the default alphabetical order if the display sequence is not configured in masterdata.&nbsp;&nbsp;
+
The process of selecting users on contract request now provides a support to lookup attribute as well, to avail the benefits of filtering capabilities to handle specific business scenarios.&nbsp;<br/> It is now possible to filter users, such as external or internal users, using the lookup on extended user entity while working with contract requests and agreements.&nbsp;<br/> The enhancements include:
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 14.png|720px|7.15 Release Notes Screenshot 14]]</div>
+
−
&nbsp;
+
  
−
<span style="color:#800080;">'''558605 – Viewing amendments in grid view on the agreement details page'''</span>
+
*Enabling multi filter Lookup for contract request and user datatype.&nbsp;  
−
 
+
*Filtering user type attributes as per Extended User Entity details.&nbsp;
−
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;
+
*Managing external users through Extended User Entity.
−
 
+
*Migrating existing users to the Extended User Entity through script as a part of upgrade.&nbsp;  
−
Users can now view amendments in the “Grid” view, and toggle between grid or tile view. The grid view is the default for amendments and supports all existing grid functionalities, such as standard search, filter, column selection, pagination, export to CSV/Excel, and so on.
+
<div class="note-box">'''Note''': The necessary user details must be added to the Extended User Entity masterdata through technical configuration in order to migrate the user data.</div>  
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 558605.png|720px|558605]]</div>  
+
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''561410 – Enhancing the multi-select drop-down&nbsp;'''</span>
+
<span style="color:#800080;">'''384324 – Ability to configure number of approvals required from selected ad-hoc user groups'''</span>
  
−
The multi-select choice drop-down has been enhanced for better usability, data input, and post-selection data review of contract requests, agreements, amendments, and masterdata entities.&nbsp;
+
Previously in ICI, when a user group was added as an ad-hoc approver or reviewer, all users from the added group were required to approve a document, except when added using a rule.&nbsp;<br/> Users now have the ability to set the minimum approvals required from selected ad-hoc user groups to qualify the agreement as approved, thereby accelerating approval process.<br/> In ICI, during the contract negotiation flow, authorized users can add ad-hoc approvers or reviewers to a contract’s team.
−
 
+
<div class="image-green-border">[[File:7.16 RN SS 07.png|720px]]</div>
−
Users can now:&nbsp;
+
&nbsp;<br/> They can specify whether all or specific number of users from each selected user groups are required to approve the document. This will considerably reduce the approval cycle time and unnecessary follow ups.
−
 
+
<div class="image-green-border">[[File:7.16 RN SS 08.png|720px]]<br/> &nbsp;<br/> The request will then be sent to all users in a group in parallel, where either a specified minimum number of users or all can approve a document to consider it as approved by that user group.<br/> This configuration is available for:</div>
−
*View eight options in a drop-down list (instead of six), without scrolling.&nbsp;
+
*Workflows: approver, reviewer, request review and deviation approver.
−
*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&nbsp;  
+
*Entities: agreement, amendment, orphan amendment, contract request, association and masterdata.
−
*View all selected values at the top of the drop-down.  
+
*Integrations: Icertis Experience for Salesforce and for Microsoft Dynamics CRM (Iframe where ICI loads).
−
*Deselect the selected values, individually or all with a single click, without opening the drop-down.  
+
*Sub-roles.
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 16.png|720px|7.15 Release Notes Screenshot 16]]</div>  
+
*Add to Team window’s Grid and Tile views.
 +
<div class="image-green-border">This enhancement is available with the upgrade and no further configuration is required.</div>  
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>
+
<span style="color:#800080;">'''832489 – Enhancing auto-attachment functionality to support all ADCT configurations'''</span>
  
−
In ICI, the configurator can filter the lookup masterdata table with “Must” and “Must Not” conditions, to achieve necessary business scenarios, while configuring a lookup attribute on contract types.&nbsp;
+
Users will now be able to auto-attach associated documents containing mandatory attributes as well to an agreement as this functionality is enhanced to support all associated document contract types.<br/> The auto-attachment can now be used in obligation management as well, where users may need to instantiate and associate a predefined set of obligations to agreements. Users can automatically attach these obligations as associations to agreements and amendments based on defined event rules.<br/> Users can now:
  
−
With this release, ICI provides the ability to configure a lookup attribute using the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup masterdata attribute.&nbsp;
+
*Define and maintain a library for Associated Document Contract Types (ADCTs) as a standard document master with all their required attributes configured.
 +
*Update and delete associated documents in a library.
 +
*Define the mapping between agreements and associated documents for auto-attachments.
 +
*Define rules and saved search to trigger the auto-attachment process for associations.
 +
*Update associations according to the modifications in the corresponding masterdata.
 +
<div class="note-box">'''Note''': The auto-associations functionality supports only parent child type associations.&nbsp;</div>
 +
The auto-attachment of associations is enabled through technical configuration.
  
−
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;
 
−
 
−
Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute. &nbsp;
 
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 17.png|720px|7.15 Release Notes Screenshot 17]]</div>
 
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>
+
<span style="color:#800080;">'''688229 – Allowing configurators to setup the file selection attribute as read only&nbsp;'''</span>
  
−
Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;
+
In ICI, users upload a document file using the file selection attribute. With this release, ICI provides an option to disable the user defined file selection attribute at a contract type level thereby preventing unintentional or intentional tampering with the document.<br/> Configurators can configure the user defined file selection attribute to appear as editable or non-editable on the User Interface. This configuration can be done at agreement, amendment, association, masterdata, contract request, extended entity attributes, extension attributes and template variables level.&nbsp;<br/> System can still attach a file on a non-editable file selection attribute through backend tasks or API integrations. However, users would not be able to replace or remove such original files from UI which are attached through backend task/integration.
  
−
Administrators now have the capability to set preferences as default, for users, according to their locations or the offices they work in. This reduces the end user’s effort in setting up their ICI account with the required parameters after the first login and presents the system with appropriate and specific pre-configured settings. &nbsp;&nbsp;
 
−
 
−
&nbsp;Administrators can:&nbsp;
 
−
 
−
*Set and manage preferences for a single user through a single user update, and for multiple users through the bulk process.
 
−
*View preference settings modification details in the “History” tab for audit.
 
−
*Search users based on parameters related to preference settings.
 
−
 
−
Users can:&nbsp;
 
−
 
−
*Access the ICI system with appropriate details as default, after the first login.&nbsp;
 
−
*Override the default preference settings as per individual preferences.
 
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 18.png|720px|7.15 Release Notes Screenshot 18]]</div>
 
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading the document'''</span>
+
<span style="color:#800080;">'''693051 – Displaying Microsoft Word comments along with clause text for rule-based clauses in an agreement'''</span>
−
 
+
<div class="image-green-border">In ICI, clause comments are displayed along with clause text while assembling a rule-based clause in an agreement, enhancing the collaborative experience among users. Clauses are tagged and assembled into templates and agreements either in a static manner or using rules. Clause authors or custodians may have added comments to clauses using MS Word markup to collaborate with other stakeholders.&nbsp;<br/> With this release, clause comments will be displayed along with clause text when a clause is assembled in an agreement through rules as well, as they are displayed in case of static clauses. This will help stakeholders to collaborate efficiently while making the working of clauses consistent across ICI.</div> <div class="image-green-border"><br/> [[File:7.16 RN SS 09.png|720px]]</div> <div class="image-green-border"><br/> The clause comments and edits made to them will be displayed:</div>  
−
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;
+
*For rule-based clauses with or without page break.  
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 604775.png|720px|604775]]</div>
+
*For agreements, amendments, associations and assignments.  
−
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.
+
*In the “Show Comparison” window on the entity details page.  
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 20.png|720px|7.15 Release Notes Screenshot 20]]</div>
+
*For Word online editing of documents.&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 they can cover for delays occurring due to the scan and upload process while executing a large volume of documents.&nbsp;
+
<div class="image-green-border">The clause comments will be displayed for clauses, tagged and assembled in agreements, with no further configuration required.</div>  
−
 
+
−
This functionality is available for agreements, amendments, and orphan amendments.
+
−
 
+
−
&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.&nbsp;
+
−
 
+
−
In addition to the main agreement document, users can now send associated documents as part of various email notifications that get triggered for the agreement from time to time. Access to these documents can be controlled based on the type of document – internal, external, or restricted. For example, some documents may only be shared with internal users, some may be shared with internal and external users, whereas some may not be shared with anyone.
+
−
 
+
−
With this release:
+
−
 
+
−
*Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements, and amendments.
+
−
*Users can define:
+
−
**The 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.
+
−
 
+
−
&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.&nbsp;
+
−
 
+
−
With this release, users can define configurable labels for peer associations between existing contracts by configuring the “Linkage Type” masterdata. The configurable labels define various business relationships in the context of contracts. For example, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on. The labels can be activated or deactivated as per business requirements.
+
−
 
+
−
The configurable labels support the existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as peer, with default peer linkage type label, defined in the default peer mapping for the amendments.&nbsp;
+
−
 
+
−
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;
+
−
*Associate and Inheritance icons.
+
−
*Bulk actions.
+
−
*Agreement creation through business APIs.
+
−
*Broadcast – “Attachments” tab and captured notes.
+
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 586492.png|720px|586492]]</div>  
+
−
'''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.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 22.png|720px|7.15 Release Notes Screenshot 22]]</div>
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''619558 – Downloading amendments using download all functionality'''</span>
+
−
 
+
−
ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements.&nbsp;
+
−
 
+
−
With this release, users can download amendments of an agreement with corresponding parent-child associations in the downloaded zip package. This is supported on the selective download option too.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 23.png|720px|7.15 Release Notes Screenshot 23]]</div>
+
−
For ease of access, each selected amendment will be downloaded with its selected associations in separate folders. The folders are named “Amendment_1”, “Amendment_2”, and so on (from oldest to latest), instead of actual amendment names. This helps to overcome the Windows limitation of supporting 260 characters in the file path and gives flexibility to users while creating association names.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 24.png|720px|7.15 Release Notes Screenshot 24]]</div>
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''615291 – Configuring attributes inheritance for amendments at the contract type level'''</span>
+
−
 
+
−
ICI already provided the capability to exclude specific agreement attributes from being copied to amendments through technical configuration, which applies to all agreement contract types by default.&nbsp;
+
−
 
+
−
Configurators now have the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. They can enable or disable the attribute’s inheritance for amendments, using the “Is Inherit On Amendments” flag, at the agreement contract type and template variable levels.&nbsp;
+
−
 
+
−
Users can then copy these defined attribute values from base agreement to amendment during amendment creation.&nbsp;
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 25.png|720px|7.15 Release Notes Screenshot 25]]</div>
+
−
'''Note:&nbsp;'''
+
−
 
+
−
*The technical configuration settings for excluding parent agreement attributes from its amendments will always take preference over the settings at agreement contract type and template levels.
+
−
*The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.
+
−
 
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''614877 – Replacing a user with multiple users'''</span>
+
−
 
+
−
In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees.&nbsp;
+
−
 
+
−
Administrators can now:&nbsp;
+
−
 
+
−
*Replace the user with one or more users, by selecting the entity and all/selective instances of that entity, and create a saved search for records to replace users.&nbsp;
+
−
*Validate the replaced user role against the assigned role.
+
−
*Get a notification on adding or completing a task.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 26.png|720px|7.15 Release Notes Screenshot 26]]</div>
+
−
This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management UI is provided to carry out these user management actions.
+
−
 
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''615293 – Showing or hiding the No Team Available message'''</span>
+
−
 
+
−
In ICI, users may encounter specific workflow configurations, such as the self-approval process, that do not require users added to the team. The “No Team Available” message, displayed in such cases, adds to the number of non-value clicks for users to continue.&nbsp;
+
−
 
+
−
ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks.&nbsp;
+
−
 
+
−
Administrators can:&nbsp;
+
−
 
+
−
*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.
+
−
 
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</span>
+
−
 
+
−
In ICI, users could supersede all attributes of a parent agreement configured as ‘supersedable’ with values from its amendment, either manually using the “Supersede” action or automatically through the auto-supersede task. Users can now selectively supersede individual entities based on business conditions.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 27.png|720px|7.15 Release Notes Screenshot 27]]</div>
+
−
The administrator can control the supersede functionality for agreements by:
+
−
 
+
−
*Enabling Auto Supersede option at the contract type level.
+
−
*Configuring the “Supersede Rule” with “Is Supersede by Amendments” or “Is Supersede by Termination” options.&nbsp;
+
−
*Selecting attributes in rule actions based on the selected Supersede On option.&nbsp;
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 28.png|720px|7.15 Release Notes Screenshot 28]]</div>  
+
−
Users can view the attribute’s supersede value on the agreement and the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing ICI behavior.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 29.png|720px|7.15 Release Notes Screenshot 29]]</div>  
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>
+
−
 
+
−
Previously, users could configure a conditional attribute for a contract type with simple conditions using a single “equal to” operator.&nbsp;
+
−
 
+
−
With this release, configurators can now set multiple, complex conditions to display ICI Web UI attributes dynamically, based on business scenarios. They can define conditions for attributes of all entities, except for template variables. For example, the configurator can set conditions to display an attribute based on the selection of specific values in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality. &nbsp;
+
−
 
+
−
&nbsp;Users can now:&nbsp;
+
−
 
+
−
*Apply multiple and complex conditions to display an attribute by enhancing the enable expression (Visibility Expression) for contract requests, agreements, associations, and masterdata contract types.&nbsp;
+
−
*Support conditional expressions for extension attributes. &nbsp;
+
−
*Define conditions with different operators based on the selected attribute data type.&nbsp;
+
−
*View the conditional attribute value according to the value entered in the attribute on which a condition is set.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 30.png|720px|7.15 Release Notes Screenshot 30]]</div>  
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''616901 – Applying facets to business status search filter'''</span>
+
−
 
+
−
Business statuses are prominently used by all customers as they reflect the actual status in business terms as compared to the system workflow status. Previously, the ICI search functionality supported filters on “Business Status” for users to refine results. However, manually selecting filters often becomes a tedious task in case there are several business statuses.&nbsp;
+
−
 
+
−
For ease of use and a better user experience, faceted filters using string operators, such as “Contains”, “Exactly”, “Starts With” and “Does Not Contain” have been added to the “Business Status” filters.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 31.png|720px|7.15 Release Notes Screenshot 31]]</div>
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>
+
−
 
+
−
Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&nbsp;
+
−
 
+
−
ICI's parsing logic is now improved for handling string combinations with special and alphanumeric characters so that no errors are generated. This applies to all entities across ICI, where a combination of special characters, alphabets, and numbers can be used.
+
−
 
+
−
&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 hundreds to thousands of templates and clauses.&nbsp;
+
−
 
+
−
With this release, the bulk import functionality using the “Legacy Upload” tool has been automated, which will reduce any human dependency, manual approvals, and delays for onboarding templates and clauses using the current capabilities. ICI administrators can now import templates and upload clauses to ICI in bulk.
+
−
 
+
−
Along with the tool, an XML specification document is also released which can be used for creating tags in the input document files of clauses and templates.
+
−
 
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''655507 – Uploading and downloading large files with the file path attribute'''</span>
+
−
 
+
−
ICI now provides support for larger files. This applies to masterdata and association entities.
+
−
 
+
−
Users can now:
+
−
 
+
−
*Upload files up to 4GB under the file selection attribute.&nbsp;
+
−
*Upload files with all supported file extensions allowed in the file selection attribute.
+
−
*Download All/Download Package up to 6 GB.
+
−
 
+
−
ICI supports virus scanning of large files if the virus scan feature is enabled.<br/> &nbsp;
+
−
 
+
−
'''Note:&nbsp;'''This is not applicable for contract requests, agreements, or associations with large files in the DocuSign/Adobe Sign association selection pop-up, document assembly, bulk actions, legacy upload, integrations (Salesforce, Workday, etc.), and APIs. The Upload/Download of the files would be supported for Azure and Windows Storage.
+
−
 
+
−
&nbsp;
+
−
 
+
−
<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),&nbsp;: (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (period) can be used in the display name of attributes for contract requests, agreements, associations, and masterdata contract types. The same attribute display name, as provided by the configurator, will now be displayed including special characters.
+
−
 
+
−
In scenarios where the association or saved search is tagged as a table in the agreement, and a particular column of the table does not have any data, we have introduced a functionality to skip such empty columns.&nbsp;<br/> During template creation from Icertis Experience for Word, the configurator can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table.&nbsp;This property needs to be added manually in the “Content Control Properties”, at any position after the contract type GUID, separated by a '|' (pipe separator). This enables empty columns to be skipped in document assembly, thereby eliminating unnecessary empty columns in the agreement version. The order of the columns in the table is determined by the attributes in the display preference of the associated document contract type.&nbsp;
+
−
 
+
−
Amendments to an agreement are now available in the 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;
+
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 618994.png|720px|618994]]</div>
+
−
&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.
+
−
 
+
−
Users can configure an alternate UI control for drop-downs with a limited number of values for choice attributes at contract type, global attribute, and template variable levels. This improves the user experience as the number of clicks and scrolls required to view options in a drop-down is considerably reduced and provides better readability in terms of post-selection data review. &nbsp;&nbsp;&nbsp;
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 33.png|720px|7.15 Release Notes Screenshot 33]]</div>
+
−
Users can select:&nbsp;
+
−
 
+
−
*The radio button for single-select choice attributes.&nbsp;
+
−
*The checkbox list for multi-select choice attributes.
+
−
 
+
−
The configuration applies across ICI for the creation and editing of agreement, amendment, associated document, masterdata, and contract request entities.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 34.png|720px|7.15 Release Notes Screenshot 34]]</div>
+
−
&nbsp;
+
−
 
+
−
<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.
+
−
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 35.png|720px|7.15 Release Notes Screenshot 35]]</div>  
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''872309 – Providing flexibility for assembling associations tagged as clauses'''</span>
+
−
 
+
−
In ICI, on publishing and updating actions, all clauses are evaluated, assembled and the changes are reflected in the agreement document. However, if associations are tagged in clauses, on “Assemble Contract” and “Send For Approval” actions, clauses do not get assembled and associations do not get populated in the agreement document.
+
−
 
+
−
As part of our continuous effort to provide flexibility to ICI users and improve the user experience, a key “Core.Agreement.EnableDynamicClauseAssemblyPostCreate” has been introduced.&nbsp;
+
−
 
+
−
*If the key is enabled, when an associated document is uploaded, the entire document will be automatically assembled (Clause, Attribute, Associations, Saved Search) on the “Assemble Contract” and “Send For Approval” actions.
+
−
*If the key is not enabled, the ICI document will be assembled on “Publish” and “Edit Agreement” actions. Only associations will be assembled on the “Assemble Contract” and “Send For Approval” actions.
+
−
 
+
−
'''Note: '''By default, the key is set to false.
+
−
 
+
 
&nbsp;
 
&nbsp;
  
Line 503: Line 230:
  
 
<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span>
 
<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span>
−
 
−
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 on the mobile app.&nbsp;
 
−
 
−
Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to refresh on these actions and improve usability automatically.
 
−
 
−
&nbsp;
 
−
 
−
<span style="color:#800080;">'''850259 – Updating logo and ICM to new guidelines'''</span>
 
−
 
−
As part of our new branding, “ICM” has been updated to “ICI”, and the new logo has also been added to the mobile app.
 
−
 
−
&nbsp;
 
−
 
−
<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span>
 
−
 
−
Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.
 
−
 
−
&nbsp;
 
−
 
−
<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span>
 
−
 
−
With this release, the UI WebView component for iOS has been deprecated.
 
−
 
−
&nbsp;
 
−
 
−
&nbsp;
 
−
 
−
&nbsp;
 
  
 
&nbsp;
 
&nbsp;
Line 572: Line 271:
  
 
'''Note:''' Users are recommended to start using these new endpoints to perform the operations.&nbsp;The previous endpoints to perform notes operations on the agreement entity are being deprecated and will be removed after the next 4 releases.&nbsp;
 
'''Note:''' Users are recommended to start using these new endpoints to perform the operations.&nbsp;The previous endpoints to perform notes operations on the agreement entity are being deprecated and will be removed after the next 4 releases.&nbsp;
−
 
−
&nbsp;
 
−
 
−
<span style="color:#800080;">'''819569 – APIs to Get Users based on filters applied to created or modified date'''</span>
 
−
 
−
For customers having thousands of records in their database, the filtering capability has been enhanced to fetch only those records which are modified in the given time frame and belong to certain security groups. Hence, the Get Users API response has been modified to include “Created Date”, “Created By”, “Modified Date”, “Modified By” fields so that filters can be applied to them for improved retrieval of data.
 
−
 
−
&nbsp;
 
−
<div class="image-green-border">
 
−
<span style="color:#800080;">'''863795&nbsp;– Support for context-based translations in ICI'''</span>
 
−
 
−
The same value/term in English appearing on multiple pages across ICI might have different meanings based on the context of the page on which it is used and the purpose for which it is used. For example, the word "home" is translated as "Zuhause" in German, whereas in the context of "home page" it is translated as "Startseite".
 
−
 
−
Previously, the same resource key was used for the same term appearing on multiple pages across ICI, whereas the translation of the term differed depending on the context in the different areas of ICI. With this release, the resource keys are split based on the respective context so that corresponding translated terms appear in the localized ICI version.&nbsp;
 
−
 
−
'''Note:&nbsp;'''The resource values&nbsp;have&nbsp;not&nbsp;been&nbsp;changed in the context of the language in the current release.
 
−
 
−
&nbsp;
 
−
</div>
 
−
== ICI Add-ins Enhancement Details ==
 
−
 
−
<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>
 
−
 
−
ICI users may need to modify an agreement as per business requirements by adding a clause. The clauses are displayed by “Clause Group” in the clause library by default and then searched by the clause name.&nbsp;
 
−
 
−
Multiple filters can now be configured at the clause and template level to help users easily retrieve relevant data. This improves usability for customers having a large number of clauses and templates in their clause and template library.
 
−
 
−
Users can now:
 
−
 
−
*Filter and search clauses and templates by clause metadata in the clause and template library respectively.
 
−
*Filter and search clauses and templates by extended clause metadata in the clause and template library respectively.
 
−
*Perform free-text search on the clause and template content.
 
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 668859.png|720px|668859]]</div>
 
−
&nbsp;
 
  
 
&nbsp;
 
&nbsp;
Line 613: Line 278:
 
<span style="color:#800080;">'''727318 – Enhancing AI-powered playbook in Icertis Experience for Word'''</span>
 
<span style="color:#800080;">'''727318 – Enhancing AI-powered playbook in Icertis Experience for Word'''</span>
  
−
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document and allows users to review and take corrective actions on them, and assess the risk when negotiators accept these exceptions. &nbsp;
+
<br/> &nbsp;
  
−
The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word.&nbsp;
 
−
 
−
With this release:
 
−
 
−
*Negotiators can easily review the playbook exceptions found in deviated agreement clauses on the “Agreement Clause” page. &nbsp;
 
−
*Negotiators now have an option to view playbook details in a separate resizable window as the details of the playbook position for a clause can be lengthy.
 
−
*As AI may not be able to find all the playbook positions for a type of a contract, an option has been added to view all playbook positions for a selected type of contract, with options to search and filter within, so that negotiators have a ready reference for all applicable playbook positions while reviewing the contract.
 
−
*Negotiators can view all the applicable playbook positions for a selected agreement clause.&nbsp;
 
−
*Negotiators can request approval for a playbook exception from the playbook “Details” page.&nbsp;
 
−
*Legal administrators can add a new playbook position for a type of contract or edit the existing playbook position from within Icertis Experience for Word itself.
 
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 727318.png|720px|727318]]<br/> &nbsp;</div>
 
 
<span style="color:#800080;">'''575475 – Automating user feedback during clause review'''</span>
 
<span style="color:#800080;">'''575475 – Automating user feedback during clause review'''</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;
+
&nbsp;
−
 
+
−
While reviewing a discovered clause, AI suggests a list of library clauses to be matched with the discovered clause. If a user selects one of them or selects a completely new clause from the library, the AI algorithm learns from such user actions. These learnings are incorporated in the next discoveries to improve the accuracy of clause recommendations.&nbsp;
+
  
 
<br/> <br/> <span style="color:#800080;">'''539492 – Rearranging discovered clauses'''</span>
 
<br/> <br/> <span style="color:#800080;">'''539492 – Rearranging discovered clauses'''</span>
  
−
Clauses found using DiscoverAI in an agreement document are displayed with clause categories in the “Clause Discovery” section on the Web UI. Sometimes, AI may identify the clause boundaries incorrectly. Users can now review and rearrange boundaries for such clauses on the “Clause Discovery” page. &nbsp;&nbsp;
+
<br/> &nbsp;
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 539492 - SS1.png|720px|539492]]</div>  
+
−
In rearrangement mode, users can:&nbsp;
+
  
−
*Merge multiple discovered clauses into a single clause or split a large discovered clause into multiple clauses.&nbsp;
 
−
*Identify a section of the discovered clause as its sub-clause.
 
−
*Rearrange the clause hierarchy in case of misclassification by AI. Users can change clause hierarchy and identify a clause as a parent, child or peer of one or more clauses.
 
−
*Change the AI recommended category of a clause. &nbsp;
 
−
*Choose to view only the parent clauses.
 
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 539492 - SS2.png|720px|539492]]<br/> &nbsp;</div>
 
 
<span style="color:#800080;">'''770375 – Infusing attribute discovery in agreement creation workflow'''</span>
 
<span style="color:#800080;">'''770375 – Infusing attribute discovery in agreement creation workflow'''</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. Typically, users might have already entered attribute values by the time they trigger/perform the create/publish action, thereby making the attributes discovery process redundant. Also, two different attribute pages had to be maintained, with personalization 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 the agreement creation process. Discovered values will then be auto-filled in empty attributes and users can view additional potential options for the discovered attributes.&nbsp;
 
−
 
−
Users can:&nbsp;
 
−
 
−
*View the progress of the attribute discovery.&nbsp;
 
−
*Identify AI discoverable attributes on the “Attributes” page of the agreement creation wizard.
 
−
*View the values recommended by AI for discoverable attributes.
 
−
*View the agreement document on the “Attributes” page itself, for quick validation of AI recommended values for discoverable attributes, as well as attribute values already tagged in the agreement document.
 
−
 
−
'''Note: '''When&nbsp;an attribute discovery is triggered from the “Attributes” page, the two-column attributes layout is converted to a single column layout, to accommodate the agreement document view.
 
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 770375.png|720px|770375]]</div>
 
 
&nbsp;
 
&nbsp;
−
 
−
<span style="color:#800080;">'''727312 – Clause hierarchy discovery in text PDFs'''</span>
 
−
 
−
In the previous release, clause hierarchy discovery was introduced in well-formatted .docx agreements.
 
−
 
−
With this release, the clause delineation functionality has been enhanced to support text PDF documents and Word documents that do not use any styles. This enhancement helps to get better clause delineation, eliminates a large number of incorrectly classified clauses, and allows users to review the parent clause and child clause individually.
 
−
 
−
Clause discovery processor is now trained to identify sections and sub-sections in Word and PDF documents up to 3 levels. Support for formatting-based clause delineation has also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in a hierarchical format.
 
−
 
−
&nbsp;
 
−
 
−
<span style="color:#800080;">'''727314 – A generalized framework to support additional languages in AI apps'''</span>
 
−
 
−
In the previous release, support was provided for clause and obligation discovery for agreements in English, German, Spanish and Portuguese languages.
 
−
 
−
With this release, a language framework has been implemented for AI discovery which can support a large number of languages. Using this generalized framework, DiscoverAI, NegotiateAI, and DiscoverAI for legacy apps have been enhanced to support additional European languages – French, Dutch, Norwegian, and Swedish.&nbsp;
 
−
 
−
Along with the clause and obligation discovery support, AI models can now discover attributes too, in all the supported languages.&nbsp;
 
  
 
&nbsp;
 
&nbsp;
Line 685: Line 298:
 
<span style="color:#800080;">'''514593 – Introducing the&nbsp;Tagged Attributes Report'''</span>
 
<span style="color:#800080;">'''514593 – Introducing the&nbsp;Tagged Attributes Report'''</span>
  
−
With this release, a new “Tagged Attributes Report”, has been introduced which helps administrators understand the complete profile of an attribute and how it has been tagged across different clauses and templates. This provides them better visibility into attribute usage and saves them considerable time.
+
&nbsp;
−
 
+
−
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.&nbsp;<br/> 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>
 
<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.
+
&nbsp;
−
 
+
−
In this release, the report is being enhanced to display “Clause Extension Summary” which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information of the clause extension attributes. The “Clause Extension Version Summary” will display the latest values of clause extension attributes.&nbsp;
+
  
 
<br/> <span style="color:#800080;">'''514611 – Introducing the&nbsp;Notifications History Report'''</span>
 
<br/> <span style="color:#800080;">'''514611 – Introducing the&nbsp;Notifications History Report'''</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 that particular entity.&nbsp;
 
−
 
−
The default report is available for contract requests, agreements, and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities. This report displays a list of notifications sent for an entity, including details such as the event that triggered the notification, the message body, subject, the To, CC, BCC recipient names, and email addresses, along with other details such as the attachment filename or sent date and time.&nbsp;
 
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 514611.png|720px|514611]]</div>
 
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''742607 – Providing additional localization support in reports'''</span>
+
== Integration Enhancement Details ==
−
 
+
−
With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas:&nbsp;
+
−
 
+
−
*Contract type names, if the respective entity has locale resource key values in the database.&nbsp;
+
−
*Drop-down with Yes/No values.
+
−
*Graph and Time zone tooltips, if present in the report.
+
−
*Column headers. &nbsp;
+
−
*Any error or validation messages.
+
−
*Informative messages such as “No data available”. &nbsp;
+
−
 
+
−
<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span>
+
−
 
+
−
Previously, the "Agreement Status" filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&nbsp;
+
−
 
+
−
<br/> This filter is now also available for the "Agreement Deviation Report" and "Agreements Pending Execution Report". Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.
+
−
 
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>
+
−
 
+
−
The “Cycle Time Report” displays the cycles for contract requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&nbsp;
+
−
 
+
−
With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.
+
−
 
+
−
&nbsp;
+
−
 
+
−
<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>
+
−
 
+
−
With this release, the user creating a PowerBI report can hyperlink the "Agreement Code" using conditional formatting with the Web URL option, so that on clicking an agreement code, the user is navigated to the corresponding agreement in ICI.
+
−
 
+
−
&nbsp;
+
−
 
+
−
== Integration Details ==
+
  
 
<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
 
<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
−
 
−
Signing agreements is often a combination of manual signatures and electronic signatures. ICI now provides a unified flexible signature workflow to its customers, thus improving the overall turnaround time and reducing the efforts of printing and scanning manually signed documents.
 
−
 
−
With this release, the ICI signature process has been enhanced as follows:
 
−
 
−
*The hybrid signature process has been introduced that allows the usage of manual and electronic signature modes in a single transaction.
 
−
 
−
'''Note: '''If the DocuSign console is enabled, then the user has the provision to tag the signatories after manual signatures.&nbsp;For other signature modes, ICI relies on the provisions facilitated by your signature provider.
 
−
 
−
*The DocuSign console has been enabled with ICI that allows users to:
 
−
**Add and modify the signatories.
 
−
**Change the signature sequence.
 
−
**Preview documents in the DocuSign console.
 
−
**Tag signatories in the DocuSign console.
 
−
**Use Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign. 
 
  
 
<br/> &nbsp;
 
<br/> &nbsp;
Line 761: Line 316:
 
<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>
 
<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>
  
−
Previously, DocuSign integration provided support for sequential signatures. This capability has now been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process. Parallel signatories can now be configured using rules or the DocuSign console.
+
&nbsp;
−
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 641289.png|720px|641289]]</div>
+
 
 
<br/> <span style="color:#800080;">'''701825– Supporting multiple vendors for electronic signature'''</span>
 
<br/> <span style="color:#800080;">'''701825– Supporting multiple vendors for electronic signature'''</span>
−
 
−
Previously, ICI supported one signature vendor within one instance of ICI.&nbsp;
 
−
 
−
Now, users have the flexibility to not only select multiple electronic signature vendors in the same instance but also select the signature provider at the agreement level, based on the business requirements.
 
−
 
−
Users now have the flexibility to:
 
−
 
−
*Configure any number of signature providers for a single ICI instance, as per business requirements.
 
−
*Select the signature provider of choice, at the agreement or amendment level.
 
−
*Define standard rules and conditions to automatically select the signature provider of choice, based on the organizational needs.
 
−
*Use multiple accounts of the same signature provider or multiple accounts of different signature providers.
 
  
 
&nbsp;
 
&nbsp;
  
 
<span style="color:#800080;">'''751651 – Publishing success/failure notification message on ASB post data sync from Salesforce'''</span>
 
<span style="color:#800080;">'''751651 – Publishing success/failure notification message on ASB post data sync from Salesforce'''</span>
−
 
−
Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any agreement document changes.
 
−
 
−
With this release:
 
−
 
−
*Document assembly or notification to third party applications can be triggered by consuming the notification message posted on Azure Service Bus (ASB) via custom task implementation. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”.
 
−
*Upon completion of data sync for an opportunity, the Salesforce data sync task raises a “Data Sync Passed/Failed” event on the ASB upon completion of data sync for each ICI entity related to the given opportunity. The message posted on ASB will display details such as Opportunity ID, ICI entity SysId and time stamp, among other information.
 
  
 
&nbsp;
 
&nbsp;
  
 
<span style="color:#800080;">'''796155 –&nbsp;Enhancements to the data flow between Salesforce/MS CRM and ICI'''</span>
 
<span style="color:#800080;">'''796155 –&nbsp;Enhancements to the data flow between Salesforce/MS CRM and ICI'''</span>
−
 
−
Previously, when changes were made to any Salesforce entity, then the data would sync in all related ICI contracts/requests, irrespective of their state in ICI. For example, contracts in the "Waiting For External Signature" state would not be updated via ICI UI but would get updated via data sync.
 
−
 
−
With this release:
 
−
 
−
*Changes made to a record of an entity (for example, “Opportunity”) in Salesforce will not sync to corresponding ICI contracts if they are in “Waiting For External Signature”, “Waiting For Internal Signature” or “Expired” states.&nbsp;
 
−
*The data will sync only for tracking attributes if the contract is in the "Executed" state.&nbsp;
 
−
 
−
These enhancements to the data flow, done for configurability and consistency with the ICI user interface, will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.
 
  
 
<br/> <span style="color:#800080;">'''674469 – Generating ICI notifications and enhancing Salesforce data sync'''</span>
 
<br/> <span style="color:#800080;">'''674469 – Generating ICI notifications and enhancing Salesforce data sync'''</span>
  
−
An alert mechanism is introduced for monitoring success and failure in Icertis Experience for Salesforce integrations, using ICI/Email notifications, so that end-users get notified about success/failure in data sync.&nbsp;
+
&nbsp;
−
 
+
−
With this release:
+
−
 
+
−
*Customers will get success/failure ICI notifications for data sync as well as reverse sync. If there are any failures/exceptions in the sync process (data/reverse), the system will retry the respective operation, based on the configured retry count.&nbsp;
+
−
*Additional logging has been introduced for ICI-Salesforce integration messages. Depending on the message type (success/failure), the Kibana logs will contain correlation ID, status, and JSON details.&nbsp;  
+
  
 
<br/> <span style="color:#800080;">'''679797 –&nbsp;Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use'''</span>
 
<br/> <span style="color:#800080;">'''679797 –&nbsp;Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use'''</span>
  
−
Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user IDs and passwords for authentication and authorization of production systems in an enterprise. Security organizations also have stringent security policies which do not approve user Id or password authentication process.&nbsp;
+
&nbsp;
  
−
With this release, support is provided for JWT (JSON Web Token) Bearer OAuth, a secure authentication and authorization process. This makes the ICI integration with Salesforce more secure as the actual “Modified By” user from Salesforce is set as “Modified By” user in ICI for the corresponding ICI records during data sync.&nbsp;
+
&nbsp;
  
−
When entities in Salesforce are updated by a user, the process builder sends a message to the ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&nbsp;
+
<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
  
−
Users have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.
+
&nbsp;
  
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
+
== ICI Platform Tools Enhancement Details ==
  
−
Previously, reverse data sync flow in MS CRM used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&nbsp;
+
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
  
−
ICI now uses the client ID and secret key, instead of user ID and password, for the authentication/authorization process between MS CRM and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&nbsp;
+
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI.&nbsp;
−
 
+
−
Users will have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.
+
  
 
&nbsp;
 
&nbsp;
  
−
== Partner Enablement ==
+
== Business Apps Enhancement Details ==
  
 
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
 
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
Line 837: Line 358:
 
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI.&nbsp;
 
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced 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:
+
&nbsp;
  
−
*'''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.
+
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
  
−
*'''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 related code.  
+
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI.&nbsp;
  
−
*'''Working with ICI Tasks: '''Updated for the 7.15 release.
+
&nbsp;
  
−
*'''Working with ICI Hooks:&nbsp;'''Updated for the 7.15 release.
+
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
  
−
*'''ICI Developer Library:''' Updated for the 7.15 release.
+
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI.&nbsp;
−
 
+
−
*'''Local Environment Setup using ICI Binaries:''' Updated for the 7.15 release.
+
−
 
+
−
*'''Self-Serve Tools:'''&nbsp;Updated for the 7.15 release.
+
  
 
&nbsp;
 
&nbsp;
  
−
== Technical Requirements for Release 7.15 ==
+
== Partner Enablement ==
  
−
The Icertis Contract Intelligence (ICI) Proposal Management application can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available in all environments.&nbsp;The software and hardware requirements for the client system as well as mobile application are listed in the table below.
+
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
−
<div class="image-green-border">[[File:7.15 Release - Tech Req 1.PNG|720px|7.15 Release - Tech Req 1]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 Release - Tech Req 2.PNG|720px|7.15 Release - Tech Req 2]]</div> <div class="image-green-border">[[File:7.15 Release - Tech Req 3.PNG|720px|7.15 Release - Tech Req 3]]</div> <div class="image-green-border">[[File:7.15 Release - Tech Req 4.PNG|720px|7.15 Release - Tech Req 4]]</div> <div class="image-green-border">[[File:7.15 Release - Tech Req 5.PNG|720px|7.15 Release - Tech Req 5]]</div> <div class="image-green-border">[[File:7.15 Release - Tech Req 6.PNG|720px|7.15 Release - Tech Req 6]]</div>
+
−
&nbsp;
+
  
−
&nbsp;
+
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI.&nbsp;
  
 
&nbsp;
 
&nbsp;
Line 867: Line 382:
 
&nbsp;
 
&nbsp;
  
−
&nbsp;
+
== Technical Requirements for Release 7.16 ==
−
 
+
−
&nbsp;
+
  
 +
The Icertis Contract Intelligence (ICI) application can be accessed from any device with an Internet connection and a supported browser. All features may not be available in all environments.&nbsp;<br/> The software and hardware requirements for the client system as well as the mobile application are listed in the table below:
 +
<div class="image-green-border">&nbsp;</div>
 
== Known Issues ==
 
== Known Issues ==
  
 
This section includes some issues that we are aware of and plan to resolve at the earliest:
 
This section includes some issues that we are aware of and plan to resolve at the earliest:
−
 
+
<div class="image-green-border">[[File:7.16 RN SS 32.PNG|720px]]</div>
−
[[File:7.15 Release - Known Issues.PNG|720px|7.15 Release - Known Issues]]
+
&nbsp;
  
 
&nbsp;
 
&nbsp;

Revision as of 06:20, 14 June 2021

 

ICI Release Notes - Release 7.16

List of Enhancements 7.16

The 7.16 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. Key enhancements include new AI and Analytics capabilities, User Experience updates, and Contract Workflow and Localization features.

The enhancements of this release include:

  • Enhancements to the ICI Application
    • User Experience
      • Enabling users to create associations from directly within the contract request creation wizard. File-drag-and-drop functionality is also enabled while creating associations within agreement creation wizard to reduce the number of clicks required and save time. 
      • Improving usability by extending document preview to custom file selection attributes on entity’s Summary, Details and Verify pages. Also, the preview for associations is extended to .ppt, .pptx, .msg and images (.jpg, .jpeg, .png and .gif) file formats along with .docx and .pdf files.
      • Improving the Legacy Upload tool for a better User experience and reduced manual intervention with auto generation of workbook, support for peer associations, linkage type and sub folder structure and various other related improvements. 
      • Extending dual language template capability with options of rule-based auto assembly in secondary language in accordance with the content in primary language.    
      • Enhancing the existing localization capability to support additional UI components such as entity statuses/business statuses, choice/multi-choice attributes, signature sequence among others, as per logged in user’s language preference. 
      • Creating a base for supporting context-based translations across ICI. 
      • Providing the capability to carry out delete and update operations to help Administrator users to fix data inconsistencies using a self-serve Data Management utility.
      • Enhancing bulk actions on saved searches to provide better process visibility with notifications and validation messages.
      • Improving the ICI out of office delegation functionality to support multi-level and conditional delegations with the sequencing capability to create complex delegation structures and help users manage tasks more efficiently.
      • Enabling filtering capabilities for selecting users on contract requests and agreements using the lookup to extended user entity and fulfill specific business requirements.
      • Enhancing the auto-attachment capability to support associated document contract types with non-mandatory attributes.
      • Allowing users to configure a file selection attribute as read-only on the UI using attribute property and have more control over the file access, further safeguarding uploaded documents.
      • Displaying clause comments along with clause text while assembling a rule-based clause in an agreement, enhancing the collaborative experience among users.
    • Workflow Enhancements
      • Providing users the ability to set the minimum approvals requirement from selected ad-hoc user groups to qualify agreement as approved, thereby accelerating approval process.

 

  • Mobile App Enhancements
    • Updating the theme color as per new Icertis branding.

 

  • Enhancements to ICI API 2.0
    • Adding new API endpoints to add/remove/get teams as well as add/get notes for associations.
    • Adding filters to the Get Users API response for users to be able to fetch desired records in a shorter time frame.
    • Announcing deprecated APIs and their provisioned alternatives.  

 

  • Enhancements to Artificial Intelligence Applications
    • Introducing AI studio to analyze multiple set of documents in a go, generating analytics to enable real time decision and actions.
    • Introducing self-serve AI to create your own AI models and train them. Administrators can define new attribute, clause or obligation to be discovered and include them in an AI model. ICI’s AI engine would learn the patterns from user feedback and recommend the attribute value in subsequent discoveries.
    • Extending DiscoverAI clause delineation support to text PDF, mixed formatted .docx files and for documents in languages other than English. It also identifies document objects such as titles, table of contents, signature blocks, headers, and footers and separates them from the clause text.
    • Enhancing the AI engine so that it learns the clause or obligation category changes made by the user and identifies the correct category next time onwards.

 

  • Enhancements to Reports
    • Introducing Platform Analytics that merges a range of Power BI reports within the ICI core reporting, enabling users to leverage Microsoft Power BI capabilities for customized report creation.
    • Introducing the AI Studio Report which displays the result of the AI studio batch, helping users to quickly comprehend discovery results and take informed decisions.
    • Enhancing the core reporting capability with the ability to add, edit and delete attributes to provide better visibility in reports.
    • Introducing the AI Model Training Performance Report enabling users to view the improvements in the discovery performance over a period of time.
    • Improving user experience by enabling localization for business statuses, choice/multi-choice attributes, signature sequence, among other elements in reporting.

 

  • Improving the Icertis Experience
    • Icertis Experience for Workday
      • Providing users the ability to create associations using purchase order and invoice entity data.
    • Signature Workflow
      • Improving the electronic signature process when using Adobe Sign to provide a unified, flexible signature workflow. This hybrid (manual and/or electronic) signature process enables users to add, modify and/or tag signatories, change signatory sequence and specify authentication methods for the signatories.
      • Providing the ability to send associated documents for signature along with agreements when using Adobe Sign.
      • Increasing the text limit for email subject lines to 255 characters, when sending documents for signature using Adobe Sign.
      • Providing users the flexibility to update effective and expiry dates while uploading the manual signed copy of an agreement/amendment.
    • Icertis Experience for MS CRM
      • Enhancing the Icertis Experience for Microsoft Dynamics CRM to improve user experience.
    • Icertis Experience for Generic Integrations
      • Enhancing file and ASB based integrations to support provisioning, deprovisioning and reprovisioning both internal and external users.
      • Enhancing SFTP based integrations to support inbound integration for agreement, amendment and association entities.

 

  • Enhancements to Platform Tools 
    • Enhancing ICI Promote to Production (P2P) framework to allow Administrators to promote configuration on different ICI patch versions for a major release (assuming no schema changes). Also enhanced robustness of the tool with provisions for automated fixes for known P2P validation errors, better display of progress status and ability to resume P2P activity from the last successful step in ICI UI.
  • Enhancements to Business Applications 
    • Sourcing
      • Introducing One-Click Download on Download Package window, enabling users to download specific files relevant to a RFx in a single click.
    • Risk Management
      • Certifying the ICI Risk Management application to work with the 7.16 release.
    • Obligation Management
      • Introducing the Obligation Library, providing users the ability to automatically create obligations.
  • Additions to Icertis Software Development Kit for Partner Enablement
    • With this release, the following SDK documents have been updated: ICI Technical Configuration Hooks and Self-Serve Tools.

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

 

 

ICI Application Enhancement Details

704597 – Extending inline association support for contract request and introducing file drop functionality in inline association

ICI enables users to create association instances as part of agreement creation or update wizard. When creating or updating an agreement or amendment, users can create, view, or delete inline associations. 
With this release, this inline associations functionality has been extended to contract request create/update wizard as well. The users can create, view or delete associations while creating or updating the contract requests.
On a separate note, a file drop zone similar to the one in agreements, has been made available on the contract request details page for the configured associated document. This file drop functionality has also been extended to inline associations grid in agreement as well as contract request creation wizard. The inline association functionality now supports dynamic associations for agreements, amendments and contract requests.

421708 – Extending preview support for additional file formats

As a part of our upgrading and upscaling process, the document preview facility has been extended to support custom file selection attributes appearing on the various UI screens. Users can now preview documents uploaded through custom and system file selection attributes as an entity goes through workflows stages, for easy and quick reference. 
Furthermore, it is now possible to preview associated documents in .ppt, .pptx, .msg and image file formats (.jpg, .jpeg, .png, .gif) along with .docx and .pdf documents. This saves efforts for business users downloading multiple documents and avoiding local copies from cluttering their system. 

7.16 RN SS 01.png
The preview option will now be available on the entity “Summary”, “Verify” and “Details” pages for system and custom file path attributes in addition to the “Preview” available from the left navigation pane.
Administrators can configure an option to preview the entire document or limit the number of pages through technical configuration. Preview for large files is not available.

 

842776 – Enhancements to the Legacy Upload tool

To improve usability and the user experience for our customers, the following enhancements have been made to the “Legacy Upload” tool: 

  • Enhanced the User Interface for better usability and self operation mode.
  • Provided support of selecting the required attributes from the attribute select columns with pre-populated mandatory attributes, along with extended entity attributes. 
  • Enabled single-click self-generation of workbook to reduce the number of steps in the process.
  • Provided support for uploading  the peer association entity so that they can be uploaded along with  existing association of the main agreement and ensure there is no manual work post legacy upload. 
  • Enabled support for Linkage Type to define proper contractual relationship between different records. 
  • Provided support for uploading records in various states (such as “Terminated”, “Expired”) so that the user does not have to reinitiate the workflow and move it manually to these states. 
  • Capability to support the sub-folders structure so that the segregated document structure is followed in ICI as well. 
  • Added validation and error messages across ICI that will help users rectify issues themselves quickly and reduce dependency on technical teams. 
  • Capability to process a failed batch again with the corrected records.
  • Provided ability to schedule the batch upload frequency using a configuration key to reduce dependency on the database team.
  • Enabled email notification on the batch initiation and completion to the concerned recipient.

 

817886 – Enhancing dual language template capability in ICI

ICI provides the capability to configure a template in two languages which helps to reduce or eliminate the language barrier and communicate better with regional customers. The capability is now further enhanced to support the rule-based assembly of primary and its equivalent localized secondary clauses in the bilingual template.
Business users can define a template as dual-language and set the template’s primary and secondary languages with the language specific date and time formats. Tagged rule-based clauses will be assembled in both languages of a bilingual template on a single ruleset.
7.16 RN SS 02.png 
When a user replaces a primary clause with its alternate clause either from the UI or Icertis Experience for Word, the corresponding secondary clause will also get replaced with its respective alternate clause. Any modification in the standard text of primary or secondary clauses will trigger the standard deviation workflows.

 

791889 – Supporting localized values on user interface as per logged in user’s language

ICI now extends its localization support to status/business statuses, choice/multi-choice attributes, signature sequence, among other elements as per language preference set by the logged in user.
Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers. In order to achieve this, ICI now extends its localization support to below mentioned UI components to display them in a logged in user’s preferred language:

  • Status and Business Status
  • Type of paper
  • Signature Type and Signature Sequence
  • Contract Type Choice and Multi-choice attributes
  • Contract Type Description
  • Search and default text 
  • Notification Category and Events on Notifications Dashboard

Administrators can enter the translated values for these elements in the local language using ICI’s “Translations Editor” tool.
7.16 RN SS 03.png 

Business users can see localized values as per their preferred language settings.

7.16 RN SS 04.png 
The UI elements will be displayed in English if there are no local values available in the system for that specific element.

 

863795 – Support for context-based translations in ICI

The same value/term in English appearing on multiple pages across ICI might have different meanings based on the context of the page on which it is used and the purpose for which it is used. For example, the word “home” is translated as “Zuhause” in German, whereas in the context of “home page” it is translated as “Startseite”.
Previously, the same resource key was used for the same term appearing on multiple pages across ICI, whereas the translation of the term differed depending on the context in the different areas of ICI. 
With this release, the resource keys are split based on the respective context so that corresponding translated terms appear in the localized ICI version.

Note: The resource values have not been changed in the context of the language in the current release.

 

740579 – Provision of self-serve data management tool

Moving one step ahead in the self-service, ICI now allows performing data management activities for entities in all workflow stages.
The data management activities introduced with this release are update and delete operations for Agreements, Associated Documents, Contract Requests, User Information, Files and Attributes. These self-serve data management operations will empower administrative users to troubleshoot data inconsistency issues on their own.

7.16 RN SS 05.png 

However, users are advised to execute these operations cautiously as the data fix does not go through necessary business validations and are performed directly in the database itself. Furthermore, updating or deleting data through the data management tool cannot be undone and will not trigger any underlying rules, workflows, notifications, triggers or integrations. Therefore, it is recommended to follow standard ICI workflows for any major or entity state modifications.
Note: The type of attributes such as Expressions, Conditional, Multi-select Lookup, Script and System will remain non editable and cannot be updated through data management tool.
By default, the Data Management utility is enabled and can be controlled through the technical configuration.

 

685700 – Enhancements to bulk action functionality on Saved Searches

ICI provides users the ability to perform bulk actions on saved searches to efficiently work with entities in bulk. 
With this release, this bulk action on saved searches functionality provides enhanced experience as:  

  • Performing validation checks against resubmission of in-progress records for same bulk action and display validation message.
  • Sending notifications upon bulk action submission and completion. 
  • Displaying a toast message on the UI along with the bulk action initiation activity on the activity panel upon bulk action submission.

The notification contains a page link which will display the statistics of the processed records and the live updates on in-progress records.
This enhancement will be available with the upgrade and does not require any further configuration.

 

788412 – Enhancements to auto delegations

ICI users can delegate their tasks for situations such as when they are out of office. These delegation capabilities are now enhanced, and business users can now: 

  • Set multi-level auto delegations 
  • Set conditional delegations
  • Reorder delegation sequence
Utilizing these capabilities, users will be able to create complex delegation structures and manage their tasks more efficiently.
Multi-level delegations allow automatic delegation of user’s tasks to the next delegate in a sequence up to a third level, when the subsequent delegates have also set up delegations overlapping with the selected time period.
Conditional delegations will selectively delegate a user’s tasks to another user based on saved searches. The delegation will take effect only if the set conditions are met.
While setting multiple delegations, users can reorder the evaluation sequence to suit their needs.

7.16 RN SS 06.png 

The validation messages will be displayed to assist users while setting up auto delegations in cases where a similar delegation already exists, delegation dates overlap, or a delegate is already out of office, so that the user can make appropriate decisions.
Users can view the recently expired 15 delegations which they can reactivate by updating; and reuse while setting up delegations structure.
These enhancements are automatically available with the upgrade and no further configuration is required.
 

789103 – Enhancements to Extended User Entity to support lookup filtering

The process of selecting users on contract request now provides a support to lookup attribute as well, to avail the benefits of filtering capabilities to handle specific business scenarios. 
It is now possible to filter users, such as external or internal users, using the lookup on extended user entity while working with contract requests and agreements. 
The enhancements include:

  • Enabling multi filter Lookup for contract request and user datatype. 
  • Filtering user type attributes as per Extended User Entity details. 
  • Managing external users through Extended User Entity.
  • Migrating existing users to the Extended User Entity through script as a part of upgrade. 
Note: The necessary user details must be added to the Extended User Entity masterdata through technical configuration in order to migrate the user data.

 

384324 – Ability to configure number of approvals required from selected ad-hoc user groups

Previously in ICI, when a user group was added as an ad-hoc approver or reviewer, all users from the added group were required to approve a document, except when added using a rule. 
Users now have the ability to set the minimum approvals required from selected ad-hoc user groups to qualify the agreement as approved, thereby accelerating approval process.
In ICI, during the contract negotiation flow, authorized users can add ad-hoc approvers or reviewers to a contract’s team.

7.16 RN SS 07.png

 
They can specify whether all or specific number of users from each selected user groups are required to approve the document. This will considerably reduce the approval cycle time and unnecessary follow ups.

7.16 RN SS 08.png
 
The request will then be sent to all users in a group in parallel, where either a specified minimum number of users or all can approve a document to consider it as approved by that user group.
This configuration is available for:
  • Workflows: approver, reviewer, request review and deviation approver.
  • Entities: agreement, amendment, orphan amendment, contract request, association and masterdata.
  • Integrations: Icertis Experience for Salesforce and for Microsoft Dynamics CRM (Iframe where ICI loads).
  • Sub-roles.
  • Add to Team window’s Grid and Tile views.
This enhancement is available with the upgrade and no further configuration is required.

 

832489 – Enhancing auto-attachment functionality to support all ADCT configurations

Users will now be able to auto-attach associated documents containing mandatory attributes as well to an agreement as this functionality is enhanced to support all associated document contract types.
The auto-attachment can now be used in obligation management as well, where users may need to instantiate and associate a predefined set of obligations to agreements. Users can automatically attach these obligations as associations to agreements and amendments based on defined event rules.
Users can now:

  • Define and maintain a library for Associated Document Contract Types (ADCTs) as a standard document master with all their required attributes configured.
  • Update and delete associated documents in a library.
  • Define the mapping between agreements and associated documents for auto-attachments.
  • Define rules and saved search to trigger the auto-attachment process for associations.
  • Update associations according to the modifications in the corresponding masterdata.
Note: The auto-associations functionality supports only parent child type associations. 

The auto-attachment of associations is enabled through technical configuration.

 

688229 – Allowing configurators to setup the file selection attribute as read only 

In ICI, users upload a document file using the file selection attribute. With this release, ICI provides an option to disable the user defined file selection attribute at a contract type level thereby preventing unintentional or intentional tampering with the document.
Configurators can configure the user defined file selection attribute to appear as editable or non-editable on the User Interface. This configuration can be done at agreement, amendment, association, masterdata, contract request, extended entity attributes, extension attributes and template variables level. 
System can still attach a file on a non-editable file selection attribute through backend tasks or API integrations. However, users would not be able to replace or remove such original files from UI which are attached through backend task/integration.

 

693051 – Displaying Microsoft Word comments along with clause text for rule-based clauses in an agreement

In ICI, clause comments are displayed along with clause text while assembling a rule-based clause in an agreement, enhancing the collaborative experience among users. Clauses are tagged and assembled into templates and agreements either in a static manner or using rules. Clause authors or custodians may have added comments to clauses using MS Word markup to collaborate with other stakeholders. 
With this release, clause comments will be displayed along with clause text when a clause is assembled in an agreement through rules as well, as they are displayed in case of static clauses. This will help stakeholders to collaborate efficiently while making the working of clauses consistent across ICI.

7.16 RN SS 09.png

The clause comments and edits made to them will be displayed:
  • For rule-based clauses with or without page break.
  • For agreements, amendments, associations and assignments.
  • In the “Show Comparison” window on the entity details page.
  • For Word online editing of documents. 
The clause comments will be displayed for clauses, tagged and assembled in agreements, with no further configuration required.

 

Mobile App Enhancement Details

773907 – Refreshing tasks and commitments

 

 

 

ICI API Enhancement Details 

836235– API Support for BACT

The support for Bulk Association Contract Type (BACT) from API 2.0 was earlier not possible. Client integrations using API 2.0 were not able to create, update, edit, delete BACT entities, hence they were compelled to use API 1.0 API and do a hybrid (1.0 & 2.0) to cover integration use cases.

With this release, to ensure a seamless experience for our customers, CRUD support has been enabled for the Create, Update, Delete, and Get endpoints. Thus, customers no longer need to use API 1.0.

 

807086 – APIs to support team management in associations

As part of our efforts to continually improve ICI, the following API endpoints have been added to support the team management for associations: 

  • Add a team member to the association 
  • Get a team of association 
  • Remove team member from the association 
  • Get available actions for associations 
  • Trigger actions for associations  

 

807101 – APIs to manage notes for ICI entities

The following API endpoints have been added to support notes operations (Add/Get) on the following entities:

  • Contract Request 
  • Agreement 
  • Masterdata 
  • Association 
  • User Information 
  • Amendment

Note: Users are recommended to start using these new endpoints to perform the operations. The previous endpoints to perform notes operations on the agreement entity are being deprecated and will be removed after the next 4 releases. 

 

AI Applications Enhancement Details

727318 – Enhancing AI-powered playbook in Icertis Experience for Word


 

575475 – Automating user feedback during clause review

 



539492 – Rearranging discovered clauses


 

770375 – Infusing attribute discovery in agreement creation workflow

 

 

Reports Enhancement Details

514593 – Introducing the Tagged Attributes Report

 

769602 – Displaying clause extension attribute summary in the Clause Summary Report

 


514611 – Introducing the Notifications History Report

 

Integration Enhancement Details

605434 – Providing a unified flexible signature process


 

641289 – Allowing parallel signatures using DocuSign

 


701825– Supporting multiple vendors for electronic signature

 

751651 – Publishing success/failure notification message on ASB post data sync from Salesforce

 

796155 – Enhancements to the data flow between Salesforce/MS CRM and ICI


674469 – Generating ICI notifications and enhancing Salesforce data sync

 


679797 – Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use

 

 

749083 – Supporting OAuth in the MS CRM adapter

 

 

ICI Platform Tools Enhancement Details

703386 – Icertis Software Development Kit for Partner Enablement

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI. 

 

Business Apps Enhancement Details

703386 – Icertis Software Development Kit for Partner Enablement

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI. 

 

703386 – Icertis Software Development Kit for Partner Enablement

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI. 

 

703386 – Icertis Software Development Kit for Partner Enablement

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI. 

 

Partner Enablement

703386 – Icertis Software Development Kit for Partner Enablement

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI. 

 

 

Technical Requirements for Release 7.16

The Icertis Contract Intelligence (ICI) application can be accessed from any device with an Internet connection and a supported browser. All features may not be available in all environments. 
The software and hardware requirements for the client system as well as the mobile application are listed in the table below:

 

Known Issues

This section includes some issues that we are aware of and plan to resolve at the earliest:

7.16 RN SS 32.PNG

 

 

 

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

Retrieved from "https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&oldid=17763"