From ICIHelp8.2
Jump to: navigation, search
 
(68 intermediate revisions by 4 users not shown)
Line 1: Line 1:
  
= ICI Release Notes - Release 7.15 =
+
= ICI Release Notes - Release 8.2 =
  
== List of Enhancements 7.15 ==
+
Apart from new features and enhancements, this document contains information on:
  
The 7.15 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.
+
*[[#_Technical_Requirements_1|Technical Requirements]]
 +
*[[#_Accessibility_Conformance|Accessibility Conformance]]
 +
*[[#_Known_Issues|Known Issues]]
  
The key enhancements of this release include:
+
Refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.2/index.php?title=ICI_Help Wiki] documentation (also found in your ICI help section) for details on all ICI features and functionalities.
  
*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>
+
= New Features and Enhancements =
**'''''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;
+
***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”.
+
***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;
+
***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;
+
***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;
+
***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;
+
***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;   
+
  
*'''''Workflow Enhancements'''''
+
== Contract Authoring & Management&nbsp; ==
**Improved usability including the ability to create instances of associations as part of the agreement creation wizard itself.
+
**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.
+
**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;
+
**Expanded contract request experience now includes the ability to request Contract Terminations.
+
**Bulk actions support is now extended to Terminating agreements in bulk to support situations that require it, such as regulatory changes, or business partner insolvency. &nbsp;
+
**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.
+
**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;
 
  
*<span style="color:#800080;">'''Mobile App Updates'''</span>
+
=== Amend contracts preserving previously negotiated terms ===
**Enhancing the “Refresh” functionality for “Tasks” and “Commitment” tabs to continually show the latest changes in the status for mobile app users. 
+
  
&nbsp;
+
'''What''' – When users amend a contract, they now have a choice to either use the base agreement or a previously negotiated and amended contract. Along with the contract version, users can also choose the associations to copy to the amendment.
  
*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>
+
'''Advantages''' – Maintaining a history of the original agreement and all amendments is now possible. This helps in auditing the changes made to contracts over time.
**Providing support for the script and integrated attributes as cascaded attributes for lookup fields when configured at the contract type level. This is applicable for retrieval, creation, and update of the instances of contract requests, agreements, associations, and amendments.  
+
**Adding the identifier “TrackingId” which can be passed by subsequent API calls for logging and troubleshooting errors.
+
**Adding support for troubleshooting API issues with failure notifications. &nbsp; 
+
  
&nbsp;
+
'''How''' – Options to choose the amendment and copy associations to the amendment are now available when creating an amendment. Users can associate and inherit documents such as NDA, SOW, etc.
  
*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>  
+
'''Value''': Compliance | User Experience<br/> '''For''': Legal Team | Authors | Contract Managers<br/> '''Feature ID''': 1233193
**'''''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;
+
=== Send multiple agreements packaged in a single envelope for electronic signature ===
  
*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>
+
'''What''' – Earlier, agreement could be bundled only with its associations and sent for electronic signature. With this release you can also bundle peer agreements in a single package for electronic signing.
**Multiple enhancements to the AI-powered legal playbook capabilities:
+
***Improved usability by enabling larger window views of the “Details” page, including deviations.
+
***All the playbook positions for a contract type now have the option to search and filter.
+
***Administrators can create a new playbook record or update an existing one from within Icertis Experience for Word itself.  
+
**Improving the clause delineation logic so that users can rearrange the AI-identified clause boundaries. You can now merge or split discovered clauses or selected text in a clause and also create sub-clauses within the discovered clause.
+
**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;
+
'''Advantages – '''Eliminates the need to send one agreement at a time for signature, thereby saving time. Provisions setting a sequence in which the agreements must be signed and facilitates reordering if required.
  
*<span style="color:#800080;">'''Enhancements to Reports'''</span>
+
'''How - '''Existing Esign functionality is enhanced to package peer agreements as a single bundle and send it for electronic signature.
**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 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.
+
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.
+
**Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.
+
**Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis.&nbsp;
+
**Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.
+
**Multiple localization enhancements within reports.  
+
  
&nbsp;
+
'''Value''': User Experience | Contract Building Performance<br/> '''For''': Contract Owners | Legal Compliance Team<br/> '''Feature ID''': 1369302
  
*<span style="color:#800080;">'''Improving the Icertis Experience'''</span>
+
=== Quickly create and edit contract types in bulk using excel workbook ===
**'''''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).
+
***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.
+
***Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process.&nbsp;
+
***&nbsp; 
+
**'''''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'''''
+
***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.   
+
  
*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>
+
'''What''' – ICI now allows its users to edit and create contract types in bulk using the Microsoft Excel workbook. User can also edit multiple attributes for multiple contract types at once.
**
+
***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.
+
'''Advantages'''
  
&nbsp;
+
Contract type (CT) changes happen frequently in the implementation phase, the feedbacks from the customers regarding the changes in the CT have to be earlier implemented one by one for each CT in ICI UI. Now, this changes and edits can be done in one go using this feature.
  
== <span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancement Details</span> ==
+
Creating and editing multiple contract types at once will reduce time involved in configuring large contract types.
  
<span style="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</span>
+
'''How'''
  
Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.
+
A button “Bulk Contract Type” is now added under “Configure” tile.
  
With this release, a preview functionality is being introduced, so that the primary owner or contract creator can review whether the selected template is appropriate, the rule-based clauses have been correctly added to the agreement, among other factors, and make changes to the agreement before the version is created. The preview document would also include tagged associated documents, coming through inline or inheritance associations.
+
Users can generate pre-seeded contract type workbook, with 2 tabs in excel, contact type, and contract type attributes.
  
A preview section is available on the “Verify” stage of agreement/amendment creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. The preview is available till the Approved state of the agreement/amendment.
+
'''Value''': User Experience<br/> '''For''': Admins | Legal Team | Contract Managers<br/> '''Feature ID''': 1342050
  
'''Note: '''This functionality is configurable. It is not available by default and can be enabled or disabled for chosen contract types.
+
== Icertis Experiences ==
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 1.png|720px|7.15 Release Notes Screenshot 1]]</div>
+
&nbsp;
+
  
<span style="color:#800080;">'''575640 – Creating associations on the create or edit wizard of agreement'''</span>
+
=== Rules functionality added to Icertis Experience for Word ===
  
Previously in ICI, contract authors had to create associations for agreements after the agreement was already created. However, in practical terms, associations such as annexures, supporting documents, SLAs, product specifications, rate tables, and so on, are all an inherent part of the agreement information that is critical to the business, and some associations are required to be created along with the agreement.
+
'''What''' – Users can now create rules for assembling the clause and define the rules for selecting the template from within Microsoft Word to display clauses in agreements based on specified conditions. Existing rules can also be viewed or edited from Microsoft Word.
  
Hence, the ability to create association instances as part of agreement creation or update wizard is being introduced in this release. A separate page is displayed, when creating or updating the agreement or amendment for the user to create, view, or delete inline associations. The user also has an option to select the columns and their order in the association grid.&nbsp;
+
'''Advantages – '''Provides a familiar and intuitive interface for legal teams and contract authors to create conditional agreement templates.
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 2.png|720px|7.15 Release Notes Screenshot 2]]<br/>  
+
This new page also supports page navigation. Support is also provided to copy attribute rules, association events, and agreement assembly, in case associations are tagged in the agreement template.
+
</div> <div class="image-green-border">[[File:7.15 Release Notes Screenshot 3.png|720px|7.15 Release Notes Screenshot 3]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''549900 Supporting localized reason code values as per logged in user language'''</span></div>
+
Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers.
+
  
ICI now extends its localization support to reason code values. Administrators can enter the translated values in the local language, for each reason code, using the “Translations Editor” tool.
+
Reduced turnaround time, instead of switching while creating the clause and template
<div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 Release Notes Screenshot 4.png|720px|7.15 Release Notes Screenshot 4]]</div>
+
Users can see localized reason codes as per their preferred language settings.&nbsp;
+
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 5.png|720px|7.15 Release Notes Screenshot 5]]</div>
+
The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.
+
  
&nbsp;
+
'''How – '''Users can define conditions for selecting a clause or template while assembling of clauses and selection of templates from Microsoft Word.
 +
<div class="image-green-border">[[File:8.2 RN 01.png|300px|8.2 RN 01.png]]&nbsp;&nbsp;[[File:8.2 RN 02.png|300px|8.2 RN 02.png]]</div>
 +
'''Value''': User Experience<br/> '''For''': Legal Team<br/> '''Feature ID''': 1117626
  
<span style="color:#800080;">'''614944 Initiating termination for parent agreement from the contract request'''</span>
+
=== Outlook Add-in Labeling and validation for emails added to ICI ===
  
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.
+
'''What – '''Every email uploaded in ICI will now display an Outlook category label, that helps users know if the email is already added in ICI. Additionally, a validation is also displayed if user tries uploading same emails twice. Users can customize the outlook category label as per the needs.
<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.
+
'''Advantages – '''Avoid uploading duplicate email conversations in ICI.
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 7.png|720px|7.15 Release Notes Screenshot 7]]</div>
+
&nbsp;
+
  
'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''
+
'''How – '''This feature is available as part of Icertis Experience for Outlook.
 +
<div class="image-green-border">[[File:8.2 RN 03.png|600px|8.2 RN 03.png]]</div>  
 +
'''Value''': User Experience<br/> '''For''': Contract Managers | Legal Teams<br/> '''Feature ID''': 1341557&nbsp;
  
The Collaboration Portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself.&nbsp;
+
=== Revamping ICI Salesforce User Experience ===
  
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.
+
'''What''' – Revamping the ICI Salesforce user interface to give a better user experience, with addition of features and enhancement under agreement related sub tabs.
  
&nbsp;
+
The following agreement sub tabs can now be seen with new capabilities:
  
<span style="color:#800080;">'''514605 – Supporting extended clause attributes in agreements'''</span>
+
*Associations sub tab
 +
*Amendment sub tab
 +
*Note sub tab
 +
*Team sub tab
 +
*Collaboration sub tab
  
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;
+
Some new features include:
<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.
+
Hyperlink added in the first column of the association list grid navigating to the association details page within ICI Salesforce platform.
*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;
+
  
<span style="color:#800080;">'''514615 – Streamlining&nbsp;the approval process over emails'''</span>
+
Ability to preview the document from amendments sub tab.
  
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;
+
The collaborations tab is now revamped from ICI Iframe to Salesforce native look and feel, with capability to view more messages.
  
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;
+
'''Advantages '''– This revamp will be giving a more consistent and familiar user experience with enhanced look and feel inline with Salesforce native user experience across tabs, subtabs and actions for sales personas.
<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.
+
'''How''' – Below are few screenshots of the revamped ICI Salesforce platform.
*Approvers/reviewers can download the agreement, modify it and upload it back to ICI based on the access provided.
+
*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.
+
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 11.png|720px|7.15 Release Notes Screenshot]]</div>
+
&nbsp;
+
  
<span style="color:#800080;">'''617385&nbsp;– Ability to define additional clause group under clause entity'''</span>
+
New ICI Salesforce Agreement Details screen
 +
<div class="image-green-border">[[File:8.2.RN 1.png|720px|8.2.RN 1.png]]</div>
 +
New Add Note Dialog box
 +
<div class="image-green-border">[[File:8.2.RN 2.png|720px|8.2.RN 2.png]]</div>
 +
'''Value''': User Experience<br/> '''For''': Sales Team<br/> '''Feature ID''': 1356012
  
Previously, ICI supported 3 clause groups “Termination”, “Legal” and “None”.&nbsp;
+
=== Salesforce Visibility of products and services sold to customers ===
  
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.
+
'''What''' – ICI Salesforce experience users can now view the list of all the products and services sold to the customer under “Agreement Lines” subtab.
  
Administrators can now:
+
'''Advantages – '''With visibility to Agreement lines through this feature, Sales Executives will be able to identify Cross-sell, up-sell opportunities to pursue relevant sales, and request amendment to appropriate contract.
  
*Define and update clause groups.  
+
'''How – '''A new subtab “Agreement Lines” is added for account object displaying all the active product and services sold to the customer. The products displayed under agreement line subtab are fetched via ICI saved searches.
*Edit, delete, activate or deactivate clause group entities.  
+
<div class="image-green-border">[[File:8.2.RN 3.png|720px|8.2.RN 3.png]]</div>
*View additionally added clause group values in the clause entity when creating or editing a clause.  
+
'''Note: '''The “Agreement Lines” displays only active products and services from executed contracts.
*Search agreement records or clauses on the index page on clause group attributes with added values.  
+
  
&nbsp;
+
'''Value''': User Experience<br/> '''For''': Sales Managers | Sales Executive<br/> '''Feature ID''': 1192973
  
<span style="color:#800080;">'''514643 Ordering of clauses as tagged in an agreement'''</span>
+
== Enhancements Mobile App Experience ==
  
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.
+
[[File:8.2 RN 32.PNG|720px|8.2 RN 32.PNG]]
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 514643.png|720px|514643]]</div>
+
&nbsp;
+
  
<span style="color:#800080;">'''514621 – Reviving terminated agreements'''</span>
+
== Administration & Configuration ==
  
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.
+
=== Enhanced ICI startup validation architecture ===
  
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.
+
'''What''' – A new validation framework for configuration keys and related metadata to resolve incorrect or missing keys and ensure seamless startup of ICI instances.
  
'''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.
+
'''Advantages – '''Timely validation of configuration keys and guardrails to prevent unnecessary startup blockers.
<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.
+
'''How – '''At startup, the validation framework checks for configuration keys that are inconsistent or incorrect and restores those to default values thereby preempting any startup issues. Technical admins can view and investigate the validation logs on the self-service portal.
  
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;
+
'''Value''': Reliability, Supportability<br/> '''For''': Administrators<br/> '''Feature ID''': 1373024
  
Users can now:&nbsp;
+
=== Configure E-Signature Integrations within ICI ===
  
*Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch. &nbsp;
+
'''What''' – E- signature configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
*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.
+
'''Advantages '''– This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team.&nbsp;
  
&nbsp;
+
'''How''' – Technical administrators can configure E- sign providers (DocuSign and AdobeSign) from the E-sign configuration page.
 +
<div class="image-green-border">[[File:8.2 RN 04.png|720px|8.2 RN 04.png]]</div>
 +
'''Value''': Self-service<br/> '''For''': Technical admins<br/> '''Feature ID''': 1180879
  
<span style="color:#800080;">'''555898 – Defining display sequence on lookup attributes at the contract type level'''</span>
+
=== Integrated Config keys validation framework ===
  
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;
+
'''What''' – ICI now has the capability to check incorrect values, difference in data types, and inconsistency in configuration data. The utility can be run prior to starting an application and the report and errors reported can be used to help find a solution.
  
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;
+
'''Advantages – '''Helps prevent issues that occur during application startup.
  
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;
+
'''How – '''At the start of an ICI instance, the disparity in the configuration keys is identified, and the incorrect keys are set to the default value. All such changes are recorded in the self-service portal so that the technical admins can investigate the errors.
<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>
+
'''Value''': Self-service &nbsp;<br/> '''For''': Administrators<br/> '''Feature ID''': 1373030
  
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;
+
=== Configure SSO integrations within ICI ===
  
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.
+
'''What''' – SSO configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 558605.png|720px|558605]]</div>
+
&nbsp;
+
  
<span style="color:#800080;">'''561410 Enhancing the multi-select drop-down&nbsp;'''</span>
+
'''Advantages '''This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team.&nbsp;
  
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;
+
'''How''' – Technical administrators can configure SSO integrations (SAML, WS-Fed and O-Auth) from the SSO configuration page.
 +
<div class="image-green-border">[[File:8.2 RN 05.png|720px|8.2 RN 05.png]]</div>
 +
'''Value''': Self-service &nbsp;<br/> '''For''': Technical admins<br/> '''Feature ID''': 1180896
  
Users can now:&nbsp;
+
=== Customer-specific SAML/OAuth SSO Configurations ===
  
*View eight options in a drop-down list (instead of six), without scrolling.&nbsp;
+
'''What – '''In a multitenant instance of Icertis Contract Intelligence, SSO configurations are now moved from a single configuration file to separate configuration files for each tenant. These configurations can now also be modified from within Icertis Contract Intelligence.
*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&nbsp;
+
*View all selected values at the top of the drop-down.
+
*Deselect the selected values, individually or all with a single click, without opening the drop-down.
+
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 16.png|720px|7.15 Release Notes Screenshot 16]]</div>
+
&nbsp;
+
  
<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>
+
'''Advantages'''
  
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;
+
*Site reliability and stability - SSO issues affecting one tenant do not impact other tenants.
 +
*Self-service - Technical admin users can configure SSO without intervention from Icertis teams.  
  
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;
+
'''How – '''Users with the right permissions can make SSO configuration changes from the Tenant.config file. The changes can also be made from within ICI by Technical Admin users.
  
Configurators can now:&nbsp;
+
'''Value: '''Self-service, Reliability, Supportability<br/> '''For:''' Technical Admins<br/> '''Feature ID: '''1317384
  
*Use the "IN” operator in the lookup filter attribute on agreement contract types.&nbsp;
+
=== Error-handling framework ===
*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;
+
'''What '''– A centralized and industry-standard error handling framework for faster troubleshooting, analysis and resolution of issues. The list of error codes and related data is cataloged & documented, which will act as a standard reference for all error codes in the ICI platform.
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 17.png|720px|7.15 Release Notes Screenshot 17]]</div>
+
&nbsp;
+
  
<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>
+
The framework provides the following features:
  
Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;
+
Detailed and structured data to determine severity, origin, module, area & source of the error.
  
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;
+
No unhandled exceptions emanating from the system.
  
&nbsp;Administrators can:&nbsp;
+
Detailed logging is done in a central repository like Kibana.
  
*Set and manage preferences for a single user through a single user update, and for multiple users through the bulk process.
+
For ICI Instances where AppInsights is available, a correlation id helps to track calls and correlate the complete chain of events that led to the error.
*View preference settings modification details in the “History” tab for audit.
+
*Search users based on parameters related to preference settings.  
+
  
Users can:&nbsp;
+
'''Why '''– Eliminates time required to locate and understand the issue and reduces the overall time needed to fix issues.
  
*Access the ICI system with appropriate details as default, after the first login.&nbsp;
+
'''How '''– ExceptionHandler attribute is introduced, which will have following Origin, Area, Module, Sub Module in the form of code.
*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;
+
  
<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading the document'''</span>
+
For example: 50000030021360X8013153 (shown on User Interface)
  
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;
+
Breakdown of the code is as follows:
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 604775.png|720px|604775]]</div>
+
With this release, users can now skip uploading the document, to move agreements from “Waiting For External Signature” or “Waiting For Internal Signature” to the “Executed – (Pending Signed Document)” state.
+
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 20.png|720px|7.15 Release Notes Screenshot 20]]</div>
+
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;
+
  
This functionality is available for agreements, amendments, and orphan amendments.
+
5 – Severity
  
&nbsp;
+
00 – Origin (First parameter of Exception Handling attribute)
  
<span style="color:#800080;">'''614860 Attaching associated documents to agreement notifications'''</span>
+
00 Source (mostly internal)
  
ICI users can share the main agreement document as part of various email notifications that get triggered for the agreement.&nbsp;
+
03 – Area (Second parameter of Exception Handling attribute)
  
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.
+
002 – Module (Third parameter of Exception Handling attribute)
  
With this release:
+
136 – SubModule (Fourth parameter of Exception Handling attribute)
  
*Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements, and amendments.
+
0X8013153 – Standard C# HResult which can be googled to see the exception type
*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;
+
Class decorators for Exception Handling
  
<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>
+
['''ExceptionHandler''' (exceptionOrigin: ExceptionOrigin.Core, exceptionArea: ExceptionArea.CLM, module: ExceptionAreaModule.CLM_AdminTask, submodule: ExceptionAreaSubModule.CLM_AdminTask_Root)]
  
ICI allows users to define the linkage type as a parent, child, or peer while associating peer entities with each other.&nbsp;
+
When an error occurs, the error code is displayed on the error message, see the screenshot below.&nbsp;&nbsp;
 +
<div class="image-green-border">[[File:8.2 RN 33.PNG|400px|8.2 RN 33.PNG]]</div>
 +
'''Value: '''Supportability<br/> '''For: '''Partner Developers | Any Application User | Troubleshooters<br/> '''Feature ID''': 1373034
  
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.
+
=== Administration & Configuration Enhancements ===
  
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;
+
[[File:8.2 RN 34.PNG|720px|8.2 RN 34.PNG]]
  
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;
+
== Reporting Analysis ==
  
*Agreement creation workflows for peer entities, assignment, and initiate termination flow.&nbsp;
+
=== Dashboard and Power BI reports for Supplier Evaluation ===
*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>
+
'''What – '''An interactive Supplier Evaluation dashboard with the following features is now available out-of-the-box:
  
ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements.&nbsp;
+
Interactive graphs for status of evaluation cases, evaluation distribution by performance, and ageing in review or approval states.
  
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.
+
Enlists the top and poor performing suppliers based on a host of filters like evaluation type, period of evaluation, supplier name and more.
<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>
+
Captures evaluations that are awaiting supplier inputs for missing documents.
  
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;
+
360-degree supplier performance score card about different evaluations, KPI and performance trend over a time period.
  
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;
+
Capture supplier documents/ certificates that are expired or expiring within 5 days.
  
Users can then copy these defined attribute values from base agreement to amendment during amendment creation.&nbsp;
+
'''Advantages –'''
<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.
+
Information is represented visually and is easier to consume and track.
*The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.  
+
  
&nbsp;
+
Assist the procurement team in setting up the right expectations and manage supplier relationships.
  
<span style="color:#800080;">'''614877 – Replacing a user with multiple users'''</span>
+
Insights into poorly performing suppliers can help in planning proactive performance improvement.
  
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;
+
'''How – '''The dashboard and reports can be accessed from the Supplier Management -> Dashboard.
  
Administrators can now:&nbsp;
+
'''Pre-requisite''': HTTP Artifact binding should be supported by the respective IDP server to enable this feature.
 +
<div class="image-green-border">[[File:8.2 RN 15.png|720px|8.2 RN 15.png]]</div>
 +
'''Value: '''Analytics&nbsp;| User experience<br/> '''For: '''Vendor Management Office | Procurement Department | Business Analysts| Legal Team<br/> '''Feature ID: '''1235347
  
*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;
+
=== New filters added to Agreement and Amendment based SSRS reports ===
*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;
+
'''What – '''The following filters are now available on UI for DRF Agreements Pending Approval and DRF Expired Agreements reports:
  
<span style="color:#800080;">'''615293 – Showing or hiding the No Team Available message'''</span>
+
Contract Type
  
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;
+
Org Unit
  
ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks.&nbsp;
+
Agreement Owner
  
Administrators can:&nbsp;
+
Agreement Status
  
*Selectively enable or disable the “No Team Available” message window, at the entity contract type level, appearing at various states.&nbsp;
+
Created Date (Created Date From, Created Date To)
*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.
+
Time Zone
  
&nbsp;
+
'''Note''': These reports are default and cannot be customized as of now.
  
<span style="color:#800080;">'''614963 Superseding agreement values as per amendment using rules'''</span>
+
'''Advantages – '''One or more filters can be applied to help view the data in contextual slices.
  
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.
+
'''How – '''The filters can be applied from the respective reports page, which can be accessed from the Default Reports tab.
<div class="image-green-border">[[File:7.15 Release Notes Screenshot 27.png|720px|7.15 Release Notes Screenshot 27]]</div>  
+
<div class="image-green-border">[[File:8.2 RN 16.png|720px|8.2 RN 16.png]]</div>  
The administrator can control the supersede functionality for agreements by:
+
'''Value: '''Self-service<br/> '''For: '''Managers | Legal Team | Decision Makers<br/> '''Feature ID: '''1346718
  
*Enabling Auto Supersede option at the contract type level.
+
=== Self-Service Configuration page for creating custom SSRS reports and dynamic views ===
*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>
+
'''What – '''Technical users can create or modify dynamic views and create or modify SSRS reports from the self-service configurations page. Some knowledge of technical column names and JSON is necessary to make the modifications.
  
Previously, users could configure a conditional attribute for a contract type with simple conditions using a single “equal to” operator.&nbsp;
+
'''Advantages – '''Provides a simpler path to customize reports and can be done by technical users without intervention from Icertis teams.
  
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;
+
'''How – '''Users with technical role ‘Report admin’ can access the Report Configurations tab on the System Configuration – Self-Service page and create and modify the dynamic views and SSRS DRF reports.
 +
<div class="image-green-border">[[File:8.2 RN 17.png|720px|8.2 RN 17.png]]</div>
 +
'''Value: '''Self-service<br/> '''For: '''Configuration Admin | External implementation partners<br/> '''Feature ID: '''1346720
  
&nbsp;Users can now:&nbsp;
+
== APIs ==
  
*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>
+
=== API Management Service ===
  
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;
+
'''What – '''API management is a key infrastructure of API offering working as a façade and controlling layer for use of ICI APIs. It consists of—a gateway which controls the flow of APIs from the integrating application to ICI API server, a management portal to configure the usage policies and an information portal called API Hub.
  
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.
+
With the API Management, the following is possible for customers:
<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>
+
*Enforcing usage quota limit
 +
*Rate limiting (throughput throttling) of API calls (by default set to 5 API calls per min)
 +
*Monitoring and getting reports on usage of APIs
  
Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&nbsp;
+
'''How – '''All customers using Icertis APIs can use the APIM gateway URLs as API URLs. For new customers, the APIs are automatically routed through APIM. For the existing customers that are already using APIs, they must make a configuration change to connect to APIM. The Icertis team will provide the exact API gateway URLs.
  
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.
+
'''Note''': The API Hub capability where users can get the information about APIs, try out the endpoints and get API usage reports is described as a separate feature below in the release notes.
  
&nbsp;
+
'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
  
<span style="color:#800080;">'''732929 – Uploading clauses and templates in bulk'''</span>
+
=== Icertis API Hub–A New Developer Experience for Working with APIs ===
  
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;
+
'''What – '''The new Icertis API Developer Experience is simple, secure, and immersive for the developers.
  
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.
+
As an API developer, the new Icertis API Developer Experience allows you to discover and interact with the ICI APIs. Developers can find recommendations for making API requests, inputs for each endpoint, and authentication methods. Based on the subscription key, the developers can make API calls for the API products.
  
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.
+
We have divided the API endpoints into distinct categories to facilitate access and search. Reports include data points like the number of API calls, response time, APIs used, etc.
  
&nbsp;
+
'''Advantages''' –
  
<span style="color:#800080;">'''655507 – Uploading and downloading large files with the file path attribute'''</span>
+
*Smoother developer on-boarding and learning experience
 +
*Real-time usage reports provide transparency
  
ICI now provides support for larger files. This applies to masterdata and association entities.
+
'''How – '''You must have the APIM Dev Portal User role assigned to access the new APIM Developer experience. Contact your system administrator for access.
  
Users can now:
+
Additional notes:
  
*Upload files up to 4GB under the file selection attribute.&nbsp;
+
*You can use OAuth or token-based authentication method
*Upload files with all supported file extensions allowed in the file selection attribute.
+
*An additional fee is required to use the access-based certificate authentication method
*Download All/Download Package up to 6 GB.
+
  
ICI supports virus scanning of large files if the virus scan feature is enabled.<br/> &nbsp;
+
'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
  
'''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.
+
=== Framework for the composite API ===
  
&nbsp;
+
'''What''' – This release introduces “Single Response – Composite APIs” to eliminate creation of wrappers over ICI Platform’s APIs while using them.
  
<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>
+
The Composite API Framework supports the following features:
  
Previously in ICI, attribute names did not support special characters, apart from _ (underscore), & (ampersand), and space.&nbsp;
+
API endpoint for supporting composite structure
  
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.
+
Request and Response representation
  
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;
+
Validation framework for composition
  
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;
+
Orchestration logic for composite requests
<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>
+
Referencing field's structure and usage
  
With this release, ICI provides new controls for multi-select and single-select choice attributes.
+
'''Advantages''' – The framework helps simplify the implementation and makes the integration more efficient. How - API developer can work on ICI entities via single composite API request to trigger series of APIs calls in a single API call and get multiple request results in a single response body.
  
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;
+
'''Value''': User Experience | Ease of Use | Improved Efficiency<br/> '''For''': API Developers | Administrators<br/> '''Feature ID''': 1182667
<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;
+
=== API Endpoint Changes ===
*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.
+
[[File:8.2 RN 06.PNG|720px|8.2 RN 06.PNG]]
<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>
+
[[File:8.2 RN 07.PNG|720px|8.2 RN 07.PNG]]
  
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.
+
[[File:8.2 RN 08.PNG|720px|8.2 RN 08.PNG]]
<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>
+
[[File:8.2 RN 09.PNG|720px|8.2 RN 09.PNG]]
  
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.
+
[[File:8.2 RN 10.PNG|720px|8.2 RN 10.PNG]]
  
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;
+
[[File:8.2 RN 11.PNG|720px|8.2 RN 11.PNG]]
  
*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.  
+
[[File:8.2 RN 12.PNG|720px|8.2 RN 12.PNG]]
*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.
+
== AI Applications ==
  
&nbsp;
+
=== Beta Feature – Refer existing obligations when reviewing AI-discovered obligations ===
  
== Mobile App Enhancement Details ==
+
'''What''' – AI-discovered obligations are automatically categorized in a category and sub-category when presented for review and confirmation. When reviewing discovered obligations users can now refer to existing obligations in approved state belonging to the same category, sub-category and related agreements. Changing the category and sub-category, displays the relevant set of approved obligations.
  
<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span>
+
'''Advantages'''
  
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;
+
Referring '''Library Obligations''' can help you get a standard position/scope/language to be used while setting up a newly discovered obligation
  
Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to refresh on these actions and improve usability automatically.
+
Referring from '''Related Agreements''' helps you understand what obligations from parent (peer) contracts are to be set at the child level specially in case of back-to-back contracting (e.g., checking customer contracts and passing on the related obligations in supplier contracts)
  
&nbsp;
+
'''How – '''Users can review AI-discovered obligations from the Review Obligation drawer, which can be accessed from the “Review Discovered Obligation” page.
  
<span style="color:#800080;">'''850259 – Updating logo and ICM to new guidelines'''</span>
+
Review Obligation drawer displaying Approved Obligations in Library Obligation
 +
<div class="image-green-border">[[File:8.2 RN 35.PNG|720px|8.2 RN 35.PNG]]</div>
 +
'''Note:''' Library Obligations are to be added manually. Please refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.2/index.php?title=ICI_Obligation_Management#Obligation_Library OM wiki] on how to setup an Obligation Library.
  
As part of our new branding, “ICM” has been updated to “ICI”, and the new logo has also been added to the mobile app.
+
Review Obligation drawer displaying Approved Obligations in Related Agreements
 +
<div class="image-green-border">[[File:8.2 RN 36.PNG|720px|8.2 RN 36.PNG]]</div>
 +
'''Note: '''Time needed to display Obligations from related agreements may vary depending upon the number of Linked agreements and count of Obligations within them.
  
&nbsp;
+
'''Value''': Efficiency | Time Saving<br/> '''For''': Legal Team | Contract Managers<br/> '''Feature ID''': 1366783
  
<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span>
+
== Sourcing ==
  
Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.
+
The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application.
  
&nbsp;
+
=== Converting RFI to RFP or RFQ ===
  
<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span>
+
'''What''' – ICI Sourcing application now allows creating an RFP or RFQ from an RFI from which the suppliers are shortlisted. Users can create multiple RFP’s or RFQ’s from a single RFI.&nbsp;
  
With this release, the UI WebView component for iOS has been deprecated.
+
'''Advantage''' – Saves time when creating an RFP or RFQ by allowing shortlisted suppliers to be selected from a previously completed RFI. &nbsp;
  
&nbsp;
+
'''How''' – Users can use the “Create from RFI” button from the Sourcing index page or from the Create RFP/RFQ option on the RFI that is in “Bidding Closed” state.
  
 +
'''Value''': User Experience<br/> '''Feature ID''': 1328960&nbsp;&nbsp;
  
 +
=== Shortlist Suppliers in RFx ===
  
== ICI API Enhancement Details&nbsp; ==
+
'''What''' An enhancement has been made to the existing '''Shortlist''' feature that allows buyers to select and shortlist specific suppliers for the next procurement stage. For example, from RFI to RFP or RFQ or from one round to another in the same RFX. The supplier Shortlist can be modified in certain RFx statuses.
<div class="image-green-border">
+
<span style="color:#800080;">'''863795&nbsp;Support for context-based translations in ICI'''</span>
+
  
&nbsp;
+
'''Advantage''' – Helps accessing preferred suppliers quickly or remove them from the “Suppliers” page thereby saving time.
  
<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>
+
'''How''' – A “Shortlist Supplier” option is added on the “Suppliers” page. &nbsp;
 +
<div class="image-green-border">[[File:8.2.RN 4.png|500px|8.2.RN 4.png]]</div>
 +
'''Value''': User Experience<br/> '''For''': Buyer and Administrator users<br/> '''Feature ID''': 1341682&nbsp;&nbsp;
  
ICI already supports downloading agreements. As part of our efforts to continually improve ICI, new API endpoints have been added in this release to download associated documents of agreements and contract requests.
+
=== Sourcing Enhancements ===
  
&nbsp;
+
[[File:8.2.RN T4.PNG|720px|8.2.RN T4.PNG]]
  
<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>
+
== Obligation Management ==
  
A new service bus topic has been created to publish messages about workflow operations. The messages will notify if any failures are encountered during workflow actions.
+
The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application
  
As workflow APIs are asynchronous, customers using Actions API and API 2.0 get a return success code, only on the initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.
+
=== Auto-create Obligations from Associations data ===
  
Users will now get a definite response with required details of the error and cause on the service bus. Based on the topic notification, integration developers can take follow-up actions based on success and failure.
+
'''What''' – ICI Platform now facilitates improved Obligation intake from source Association records. An Obligation is automatically created from any defined associations such as Deliverables, SLA, Risk Assessments. For example, if a SOW has ‘Deliverable’ as an association, then the user can directly convert that deliverable into an Obligation.
  
<br/> <span style="color:#800080;">'''660859 – Supporting TrackingId in APIs'''</span>
+
'''Advantages''' – Streamlines and simplifies creation of Delivery Dates, Milestones, SLAs, Risk Assessments, and other obligations from associated records, improving process efficiency. Auto-creation of Obligations enhances tracking compliance centrally using Obligation Management.
  
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;
+
'''How – '''You can use the “Create Obligation” menu option from the Associations object list view or details page.
 +
<div class="image-green-border">[[File:8.2.RN 5.png|720px|8.2.RN 5.png]]</div>
 +
'''Value''': User Experience | Contract Building | Managing Obligations | Process Efficiency<br/> '''For''': Risk Managers | Contract Administrators<br/> '''Feature ID''': 649740
  
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow”, “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature”.&nbsp;
+
=== Use “Date” & “DateTime” Attributes from Holding Agreement for Obligation Scheduling ===
  
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused the failure of the agreement creation. An identifier has been added to resolve this issue which subsequent APIs can pass for correlating from a logging perspective.&nbsp;
+
'''What – '''Due'''dates and end dates for obligations can now be selected from any of the date attributes of the agreement.'''
  
The following API changes have been made to ensure that the existing implementation and code remains intact:
+
'''Advantages'''
  
*Provided support for a “TrackingId” header in every logging request.&nbsp;
+
Eliminates the need for an Obligation creator to know specific dates.
*Users will receive the “TrackingId” provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will be returned).
+
*The called API path with the query string will be logged in Kibana. In Kibana, developers must look for “CorrelationId” which maps the “TrackingId” used in the API.<br/> &nbsp;
+
  
'''Note: '''The implementation of the "TrackingId" is optional and the value must be GUID only.&nbsp;
+
Consistency in Obligation dates used across various members / obligation creators
  
This can be used for:
+
Reduces the extra effort required in referring to Date Attributes of holding agreement entity (for example, Effective Date / Expiry Date) and use them in Obligation creation.
 
+
*Related API Calls
+
*Async operations
+
*Bulk operations
+
*Status check operations&nbsp; &nbsp;&nbsp;
+
  
 +
'''How – '''Two new attributes have been added to the Obligation Contract Type – “Select Due Date From” and “Select End Date From”. You can select a specific date value from the given options. The date value selected will be as per the actual date defined in the Agreement. For example, if you select “Expiry Date” value, an Obligation will be created with an expiry date that is same as the expiry date for the Agreement.
 +
<div class="image-green-border">[[File:8.2.RN 6.png|600px|8.2.RN 6.png]]</div>
 
&nbsp;
 
&nbsp;
</div>
 
  
== ICI Add-ins Enhancement Details ==
+
'''Value''': User Experience<br/> '''For''': Contract Operations<br/> '''Feature ID''': 913820
  
<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>
+
=== Obligation Management Enhancements ===
  
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;
+
[[File:8.2.RN T5.PNG|720px|8.2.RN T5.PNG]]
  
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.
+
== Supplier Relationship Management ==
  
Users can now:
+
ICI Supplier Relationship Management application is certified to work with the 8.2 release
  
*Filter and search clauses and templates by clause metadata in the clause and template library respectively.
+
=== Supplier Profile and Supplier Master records synchronization ===
*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;
+
'''What''' – Supplier product and service categories are now automatically synced in the following events:
  
== AI Applications Enhancement&nbsp;Details ==
+
On supplier qualification, the product/service category updates get copied to the Supplier Master category field.
  
<span style="color:#800080;">'''727318 – Enhancing AI-powered playbook in Icertis Experience for Word'''</span>
+
Buyers update the Supplier Master the information is synced with the Supplier Profile.
  
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;
+
Buyers update the Supplier Profile the information is synced with Supplier Master.
  
The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word.&nbsp;
+
'''Advantage''' – Supplier records are consistent and can be consumed across all Icertis applications.
  
With this release:
+
'''How''' – If a supplier record in the database is modified depending on the conditions defined, the other relevant records also get updated automatically.&nbsp;
  
*Negotiators can easily review the playbook exceptions found in deviated agreement clauses on the “Agreement Clause” page. &nbsp;
+
'''Value''': Efficiency<br/> '''For''': Buyer users<br/> '''Feature ID''': 1420117
*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>
+
  
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;
+
=== Supplier Relationship Management Enhancements ===
  
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;
+
[[File:8.2.RN T7.PNG|720px|8.2.RN T7.PNG]]
  
<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;
 
<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>
 
 
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>
+
== Rebates Enhancements ==
  
In the previous release, clause hierarchy discovery was introduced in well-formatted .docx agreements.
+
Rebates App in ICI Platform is enhanced to improve the usability and thereby improve the overall user experience, scalability and robust calculations. The Rebates App extends support for Big Data, AI, and Dynamic JSON. The enhancements in Rebates App can be summarized as below:
  
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.
+
'''Refined seeded data model:'''
  
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.
+
*Minimal configuration and data reusability to make Rebates app more scalable.
 +
*Standardized naming conventions to avoid any conflicts with other apps.
 +
*Normalized data has improved Calculation Engine’s efficiency by 50%.
 +
*Dynamic JSON for Rebate program data eliminates the need to have distinct rebates and payout calculation for every business unit in an organization. The enhanced calculation engine extracts JSON data from the Agreement and its associated documents and maps it with the newly configured attributes.
 +
*Background tasks optimized to support big data such as calculation engine processing large invoice and agreement datasets. As an example, for performance testing, it took 35 seconds (approximately) to process 170,000 &nbsp;records (approximately) as compared to 1 minute (approximately) for 5000 records (approximately) in the earlier version.
 +
*Rebate program attributes are a part of associated document instead of an agreement, which enables handling multiple rebate programs within a contract. This also reduces the number of attributes in an agreement, that improves the performance of agreement creation.
 +
*Standardized attributes management by allowing 16-digit numbers with 6 decimal places.
 +
*Generic Product, Location, and Customer hierarchies allow customizing configuration and mapping it to the calculation engine.
 +
*Previously, configuration supported only up to 10 customer details as these details were part of the Agreement itself. However, now these details are migrated as Associated documents to support unlimited customer details.  
  
&nbsp;
+
'''Power BI Reporting:'''
  
<span style="color:#800080;">'''727314 – A generalized framework to support additional languages in AI apps'''</span>
+
*Intuitive dashboard with advanced analytics on the rebate agreement distribution and accruals accumulation.
 +
*Out-of-the-box reports added in Power BI, which were earlier focused on Accruals, are now aligned with the overall performance of Rebates.
 +
*Improved visibility for Rebates payout calendar with the next payout dates.
  
In the previous release, support was provided for clause and obligation discovery for agreements in English, German, Spanish and Portuguese languages.
+
=== Risk Management Enhancements ===
  
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;
+
[[File:8.2.RN T6.PNG|720px|8.2.RN T6.PNG]]
  
Along with the clause and obligation discovery support, AI models can now discover attributes too, in all the supported languages.&nbsp;
+
== Technology Updates ==
  
&nbsp;
+
=== HTTP Artifact Binding Support for SSO Integration ===
  
== Reports Enhancement Details ==
+
'''What – '''In addition to HTTP POST and HTTP Redirect, ICI now supports HTTP Artifact binding for SSO (Single Sign-On) integration along with other IdPs like ADFS.
  
<span style="color:#800080;">'''514593 Introducing the&nbsp;Tagged Attributes Report'''</span>
+
'''Advantages – '''With improved security, exchanging sensitive data across Id Provider (IdP) and Service Provider (SP) becomes more authenticated and trustworthy. This prevents intervention of any malicious party.
  
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.
+
'''How – '''Administrator or Implementation Partner can choose between HTTP POST, HTTP Redirect and HTTP Artifact binding for SSO (Single Sign-On) integration, on the IdP server side.
  
This report, available on the “Reports” tile, can be accessed based on the security groups’ configuration.
+
'''Value: '''Secure Authentication Process<br/> '''For: '''All ICI Users<br/> '''Feature ID: '''1342076
  
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.
+
=== Microsoft retiring basic authentication for SMTP ===
  
<span style="color:#800080;">'''769602 – Displaying clause extension attribute summary in the Clause Summary Report'''</span>
+
'''What '''– Microsoft is retiring basic authentication for SMTP, and it would be necessary for customers using basic authentication to move to an alternate service. ICI now supports modern authentication with support for Microsoft Graph API.
  
Previously, the “Clause Summary Report” displayed “Clause Summary” and “Clause Version Summary” sections on the report index page.
+
'''Why '''– Provide support for modern authentication methods & ensure service continuity even after Microsoft retires basic authentication later this year (Oct 1, 2022).
  
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;
+
'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
  
<br/> <span style="color:#800080;">'''514611 – Introducing the&nbsp;Notifications History Report'''</span>
+
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
  
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;
+
=== Microsoft retiring Outlook REST API ===
  
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;
+
'''What''': The Icertis Outlook Add-In that currently uses the Outlook REST API will now use Microsoft Graph API.
<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 514611.png|720px|514611]]</div>
+
&nbsp;
+
  
<span style="color:#800080;">'''742607 – Providing additional localization support in reports'''</span>
+
Configurations are required for Outlook Add-In at the time of implementing or upgrading Icertis Contract Intelligence to work with Microsoft Graph API.
  
With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas:&nbsp;
+
'''Why''': Microsoft has announced that Outlook REST API will be deprecated in the month of November, 2022.
  
*Contract type names, if the respective entity has locale resource key values in the database.&nbsp;
+
'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
*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>
+
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
  
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;
+
=== Support for StartTLS protocol ===
  
<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.
+
'''What''' – Adding support for the StartTLS protocol through NuGet MailKit for authentication and notification. StartTLS protocol command is used to inform the email server that the email client wants to upgrade from an insecure connection to a secure one using TLS or SSL.<br/> <br/> '''Why''' – Customers have the option to use the StartTLS protocol, which supports enhanced security.
  
&nbsp;
+
'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
  
<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>
+
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
  
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;
+
=== Bootstrap upgrade from version 4.5.2 to 5.1.3 ===
  
With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.
+
'''What''' – The Bootstrap library has been upgraded from version 4.5.2 to 5.1.3. The support for Bootstrap library version 4.5.2 ends by Q3 2022. 4.5.2 is compatible with the new version.
  
&nbsp;
+
'''Why''' – To address security vulnerabilities.
  
<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>
+
'''TFS ID''': 1459132<br/> &nbsp;
  
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.
+
=== Web Application Firewall & Azure Front Door ===
  
&nbsp;
+
'''What''' –
  
== Integration Details ==
+
Implementing Azure Front Door (AFD) with the following settings:
  
<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
+
Web Application Firewall (WAF) in diagnostic mode
  
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.
+
Prevention Rule in AFD to restrict access from embargo countries.
  
With this release, the ICI signature process has been enhanced as follows:
+
'''Advantages – '''WAF & AFD help prevent against common exploits and vulnerabilities.
  
*The hybrid signature process has been introduced that allows the usage of manual and electronic signature modes in a single transaction.  
+
'''How – '''It can be configured, deployed, and managed via the Azure Portal, PowerShell, and CLI (command-line interface).
  
'''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.
+
'''Value''': Security<br/> '''For''': Administrators<br/> '''Feature ID''': 951438
 
+
*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;
+
 
+
<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.
+
<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>
+
 
+
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>
+
= Technical Requirements =
  
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.
+
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.
  
With this release:
+
The software and hardware requirements for the client system as well as the mobile application are listed in the table below:
  
*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”.  
+
[[File:8.2.RN T8.PNG|720px|8.2.RN T8.PNG]]
*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;
+
[[File:8.2.RN T9.PNG|720px|8.2.RN T9.PNG]]
  
<span style="color:#800080;">'''796155 –&nbsp;Enhancements to the data flow between Salesforce/MS CRM and ICI'''</span>
+
[[File:8.2.RN T10.PNG|720px|8.2.RN T10.PNG]]<br/> [[File:8.2.RN T11.PNG|720px|8.2.RN T11.PNG]]
  
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.
+
[[File:8.2.RN T12.PNG|720px|8.2.RN T12.PNG]][[File:8.2.RN T13.PNG|720px|8.2.RN T13.PNG]]
  
With this release:
+
[[File:8.2.RN T14.PNG|720px|8.2.RN T14.PNG]]
  
*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;
+
[[File:8.2.RN T15.PNG|720px|8.2.RN T15.PNG]]<br/> [[File:8.2.RN T16.PNG|720px|8.2.RN T16.PNG]]<br/> [[File:8.2.RN T17.PNG|720px|8.2.RN T17.PNG]]
*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.
+
[[File:8.2.RN T18.PNG|720px|8.2.RN T18.PNG]]
  
<br/> <span style="color:#800080;">'''674469 – Generating ICI notifications and enhancing Salesforce data sync'''</span>
+
= Accessibility Conformance =
  
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;
+
We ran accessibility conformance tests on the Icertis Contract Intelligence platform and Business Apps for Web Content Accessibility Guidelines 2.1 for Level A and Level AA standards. We did not evaluate for Level AAA standards.
  
With this release:
+
While most of the product functionality has at least one method that meets the criterion without any known defects, some functionality of the product may not meet the conformance criteria. The full report is published in the following documents and can be made available on request:
  
*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;
+
ICI Platform Accessibility Conformance Report
*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>
+
ICI AI/ML Accessibility Conformance Report
  
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;
+
ICI Reporting Accessibility Conformance Report
  
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;
+
ICI Obligation Management Accessibility Conformance Report
  
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;
+
ICI Sourcing Accessibility Conformance Report
  
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.
+
ICI Proposal Management Accessibility Conformance Report
  
&nbsp;
+
ICI SRM Accessibility Conformance Report
  
<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
+
ICI Risk Management Accessibility Conformance Report
  
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;
+
= Known Issues =
 
+
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;
+
 
+
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;
+
 
+
== Partner Enablement ==
+
 
+
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
+
 
+
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. 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:
+
 
+
*'''ICI Coding Guidelines (version 2):'''&nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.
+
 
+
*'''ICI Customization and Use Cases (version 2): '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support TypeScript related code.
+
 
+
*'''Working with ICI Tasks: '''Updated for the 7.15 release.
+
 
+
*'''Working with ICI Hooks:&nbsp;'''Updated for the 7.15 release.
+
 
+
*'''ICI Developer Library:''' Updated for the 7.15 release.
+
 
+
*'''Local Environment Setup using ICI Binaries:''' Updated for the 7.15 release.
+
 
+
*'''Self-Serve Tools:'''&nbsp;Updated for the 7.15 release.
+
 
+
&nbsp;
+
 
+
== Technical Requirements for Release 7.15 ==
+
 
+
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.
+
<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;
+
 
+
&nbsp;
+
 
+
&nbsp;
+
 
+
&nbsp;
+
 
+
&nbsp;
+
 
+
== 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:
  
[[File:7.15 Release - Known Issues.PNG|720px|7.15 Release - Known Issues]]
+
[[File:8.2.RN T19.PNG|720px|8.2.RN T19.PNG]]
 
+
&nbsp;
+
 
+
&nbsp;
+
  
'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|
+
&nbsp;'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Associations|Association Management]] | [[Compliances|Compliance Management]] | [[Templates|Template Management]] | [[Clauses|Clause Management]] | [[Configure|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]]&nbsp;

Latest revision as of 13:09, 29 September 2022

Contents

ICI Release Notes - Release 8.2

Apart from new features and enhancements, this document contains information on:

Refer to the Wiki documentation (also found in your ICI help section) for details on all ICI features and functionalities.

New Features and Enhancements

Contract Authoring & Management 

Amend contracts preserving previously negotiated terms

What – When users amend a contract, they now have a choice to either use the base agreement or a previously negotiated and amended contract. Along with the contract version, users can also choose the associations to copy to the amendment.

Advantages – Maintaining a history of the original agreement and all amendments is now possible. This helps in auditing the changes made to contracts over time.

How – Options to choose the amendment and copy associations to the amendment are now available when creating an amendment. Users can associate and inherit documents such as NDA, SOW, etc.

Value: Compliance | User Experience
For: Legal Team | Authors | Contract Managers
Feature ID: 1233193

Send multiple agreements packaged in a single envelope for electronic signature

What – Earlier, agreement could be bundled only with its associations and sent for electronic signature. With this release you can also bundle peer agreements in a single package for electronic signing.

Advantages – Eliminates the need to send one agreement at a time for signature, thereby saving time. Provisions setting a sequence in which the agreements must be signed and facilitates reordering if required.

How - Existing Esign functionality is enhanced to package peer agreements as a single bundle and send it for electronic signature.

Value: User Experience | Contract Building Performance
For: Contract Owners | Legal Compliance Team
Feature ID: 1369302

Quickly create and edit contract types in bulk using excel workbook

What – ICI now allows its users to edit and create contract types in bulk using the Microsoft Excel workbook. User can also edit multiple attributes for multiple contract types at once.

Advantages

Contract type (CT) changes happen frequently in the implementation phase, the feedbacks from the customers regarding the changes in the CT have to be earlier implemented one by one for each CT in ICI UI. Now, this changes and edits can be done in one go using this feature.

Creating and editing multiple contract types at once will reduce time involved in configuring large contract types.

How

A button “Bulk Contract Type” is now added under “Configure” tile.

Users can generate pre-seeded contract type workbook, with 2 tabs in excel, contact type, and contract type attributes.

Value: User Experience
For: Admins | Legal Team | Contract Managers
Feature ID: 1342050

Icertis Experiences

Rules functionality added to Icertis Experience for Word

What – Users can now create rules for assembling the clause and define the rules for selecting the template from within Microsoft Word to display clauses in agreements based on specified conditions. Existing rules can also be viewed or edited from Microsoft Word.

Advantages – Provides a familiar and intuitive interface for legal teams and contract authors to create conditional agreement templates.

Reduced turnaround time, instead of switching while creating the clause and template

How – Users can define conditions for selecting a clause or template while assembling of clauses and selection of templates from Microsoft Word.

8.2 RN 01.png  8.2 RN 02.png

Value: User Experience
For: Legal Team
Feature ID: 1117626

Outlook Add-in – Labeling and validation for emails added to ICI

What – Every email uploaded in ICI will now display an Outlook category label, that helps users know if the email is already added in ICI. Additionally, a validation is also displayed if user tries uploading same emails twice. Users can customize the outlook category label as per the needs.

Advantages – Avoid uploading duplicate email conversations in ICI.

How – This feature is available as part of Icertis Experience for Outlook.

8.2 RN 03.png

Value: User Experience
For: Contract Managers | Legal Teams
Feature ID: 1341557 

Revamping ICI Salesforce User Experience

What – Revamping the ICI Salesforce user interface to give a better user experience, with addition of features and enhancement under agreement related sub tabs.

The following agreement sub tabs can now be seen with new capabilities:

  • Associations sub tab
  • Amendment sub tab
  • Note sub tab
  • Team sub tab
  • Collaboration sub tab

Some new features include:

Hyperlink added in the first column of the association list grid navigating to the association details page within ICI Salesforce platform.

Ability to preview the document from amendments sub tab.

The collaborations tab is now revamped from ICI Iframe to Salesforce native look and feel, with capability to view more messages.

Advantages – This revamp will be giving a more consistent and familiar user experience with enhanced look and feel inline with Salesforce native user experience across tabs, subtabs and actions for sales personas.

How – Below are few screenshots of the revamped ICI Salesforce platform.

New ICI Salesforce Agreement Details screen

8.2.RN 1.png

New Add Note Dialog box

8.2.RN 2.png

Value: User Experience
For: Sales Team
Feature ID: 1356012

Salesforce – Visibility of products and services sold to customers

What – ICI Salesforce experience users can now view the list of all the products and services sold to the customer under “Agreement Lines” subtab.

Advantages – With visibility to Agreement lines through this feature, Sales Executives will be able to identify Cross-sell, up-sell opportunities to pursue relevant sales, and request amendment to appropriate contract.

How – A new subtab “Agreement Lines” is added for account object displaying all the active product and services sold to the customer. The products displayed under agreement line subtab are fetched via ICI saved searches.

8.2.RN 3.png

Note: The “Agreement Lines” displays only active products and services from executed contracts.

Value: User Experience
For: Sales Managers | Sales Executive
Feature ID: 1192973

Enhancements – Mobile App Experience

8.2 RN 32.PNG

Administration & Configuration

Enhanced ICI startup validation architecture

What – A new validation framework for configuration keys and related metadata to resolve incorrect or missing keys and ensure seamless startup of ICI instances.

Advantages – Timely validation of configuration keys and guardrails to prevent unnecessary startup blockers.

How – At startup, the validation framework checks for configuration keys that are inconsistent or incorrect and restores those to default values thereby preempting any startup issues. Technical admins can view and investigate the validation logs on the self-service portal.

Value: Reliability, Supportability
For: Administrators
Feature ID: 1373024

Configure E-Signature Integrations within ICI

What – E- signature configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.

Advantages – This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team. 

How – Technical administrators can configure E- sign providers (DocuSign and AdobeSign) from the E-sign configuration page.

8.2 RN 04.png

Value: Self-service
For: Technical admins
Feature ID: 1180879

Integrated Config keys validation framework

What – ICI now has the capability to check incorrect values, difference in data types, and inconsistency in configuration data. The utility can be run prior to starting an application and the report and errors reported can be used to help find a solution.

Advantages – Helps prevent issues that occur during application startup.

How – At the start of an ICI instance, the disparity in the configuration keys is identified, and the incorrect keys are set to the default value. All such changes are recorded in the self-service portal so that the technical admins can investigate the errors.

Value: Self-service  
For: Administrators
Feature ID: 1373030

Configure SSO integrations within ICI

What – SSO configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.

Advantages – This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team. 

How – Technical administrators can configure SSO integrations (SAML, WS-Fed and O-Auth) from the SSO configuration page.

8.2 RN 05.png

Value: Self-service  
For: Technical admins
Feature ID: 1180896

Customer-specific SAML/OAuth SSO Configurations

What – In a multitenant instance of Icertis Contract Intelligence, SSO configurations are now moved from a single configuration file to separate configuration files for each tenant. These configurations can now also be modified from within Icertis Contract Intelligence.

Advantages

  • Site reliability and stability - SSO issues affecting one tenant do not impact other tenants.
  • Self-service - Technical admin users can configure SSO without intervention from Icertis teams.

How – Users with the right permissions can make SSO configuration changes from the Tenant.config file. The changes can also be made from within ICI by Technical Admin users.

Value: Self-service, Reliability, Supportability
For: Technical Admins
Feature ID: 1317384

Error-handling framework

What – A centralized and industry-standard error handling framework for faster troubleshooting, analysis and resolution of issues. The list of error codes and related data is cataloged & documented, which will act as a standard reference for all error codes in the ICI platform.

The framework provides the following features:

Detailed and structured data to determine severity, origin, module, area & source of the error.

No unhandled exceptions emanating from the system.

Detailed logging is done in a central repository like Kibana.

For ICI Instances where AppInsights is available, a correlation id helps to track calls and correlate the complete chain of events that led to the error.

Why – Eliminates time required to locate and understand the issue and reduces the overall time needed to fix issues.

How – ExceptionHandler attribute is introduced, which will have following Origin, Area, Module, Sub Module in the form of code.

For example: 50000030021360X8013153 (shown on User Interface)

Breakdown of the code is as follows:

5 – Severity

00 – Origin (First parameter of Exception Handling attribute)

00 – Source (mostly internal)

03 – Area (Second parameter of Exception Handling attribute)

002 – Module (Third parameter of Exception Handling attribute)

136 – SubModule (Fourth parameter of Exception Handling attribute)

0X8013153 – Standard C# HResult which can be googled to see the exception type

Class decorators for Exception Handling

[ExceptionHandler (exceptionOrigin: ExceptionOrigin.Core, exceptionArea: ExceptionArea.CLM, module: ExceptionAreaModule.CLM_AdminTask, submodule: ExceptionAreaSubModule.CLM_AdminTask_Root)]

When an error occurs, the error code is displayed on the error message, see the screenshot below.  

8.2 RN 33.PNG

Value: Supportability
For: Partner Developers | Any Application User | Troubleshooters
Feature ID: 1373034

Administration & Configuration Enhancements

8.2 RN 34.PNG

Reporting Analysis

Dashboard and Power BI reports for Supplier Evaluation

What – An interactive Supplier Evaluation dashboard with the following features is now available out-of-the-box:

Interactive graphs for status of evaluation cases, evaluation distribution by performance, and ageing in review or approval states.

Enlists the top and poor performing suppliers based on a host of filters like evaluation type, period of evaluation, supplier name and more.

Captures evaluations that are awaiting supplier inputs for missing documents.

360-degree supplier performance score card about different evaluations, KPI and performance trend over a time period.

Capture supplier documents/ certificates that are expired or expiring within 5 days.

Advantages –

Information is represented visually and is easier to consume and track.

Assist the procurement team in setting up the right expectations and manage supplier relationships.

Insights into poorly performing suppliers can help in planning proactive performance improvement.

How – The dashboard and reports can be accessed from the Supplier Management -> Dashboard.

Pre-requisite: HTTP Artifact binding should be supported by the respective IDP server to enable this feature.

8.2 RN 15.png

Value: Analytics | User experience
For: Vendor Management Office | Procurement Department | Business Analysts| Legal Team
Feature ID: 1235347

New filters added to Agreement and Amendment based SSRS reports

What – The following filters are now available on UI for DRF Agreements Pending Approval and DRF Expired Agreements reports:

Contract Type

Org Unit

Agreement Owner

Agreement Status

Created Date (Created Date From, Created Date To)

Time Zone

Note: These reports are default and cannot be customized as of now.

Advantages – One or more filters can be applied to help view the data in contextual slices.

How – The filters can be applied from the respective reports page, which can be accessed from the Default Reports tab.

8.2 RN 16.png

Value: Self-service
For: Managers | Legal Team | Decision Makers
Feature ID: 1346718

Self-Service Configuration page for creating custom SSRS reports and dynamic views

What – Technical users can create or modify dynamic views and create or modify SSRS reports from the self-service configurations page. Some knowledge of technical column names and JSON is necessary to make the modifications.

Advantages – Provides a simpler path to customize reports and can be done by technical users without intervention from Icertis teams.

How – Users with technical role ‘Report admin’ can access the Report Configurations tab on the System Configuration – Self-Service page and create and modify the dynamic views and SSRS DRF reports.

8.2 RN 17.png

Value: Self-service
For: Configuration Admin | External implementation partners
Feature ID: 1346720

APIs

API Management Service

What – API management is a key infrastructure of API offering working as a façade and controlling layer for use of ICI APIs. It consists of—a gateway which controls the flow of APIs from the integrating application to ICI API server, a management portal to configure the usage policies and an information portal called API Hub.

With the API Management, the following is possible for customers:

  • Enforcing usage quota limit
  • Rate limiting (throughput throttling) of API calls (by default set to 5 API calls per min)
  • Monitoring and getting reports on usage of APIs

How – All customers using Icertis APIs can use the APIM gateway URLs as API URLs. For new customers, the APIs are automatically routed through APIM. For the existing customers that are already using APIs, they must make a configuration change to connect to APIM. The Icertis team will provide the exact API gateway URLs.

Note: The API Hub capability where users can get the information about APIs, try out the endpoints and get API usage reports is described as a separate feature below in the release notes.

For: API Developers | Administrators
Feature ID: 1182735

Icertis API Hub–A New Developer Experience for Working with APIs

What – The new Icertis API Developer Experience is simple, secure, and immersive for the developers.

As an API developer, the new Icertis API Developer Experience allows you to discover and interact with the ICI APIs. Developers can find recommendations for making API requests, inputs for each endpoint, and authentication methods. Based on the subscription key, the developers can make API calls for the API products.

We have divided the API endpoints into distinct categories to facilitate access and search. Reports include data points like the number of API calls, response time, APIs used, etc.

Advantages

  • Smoother developer on-boarding and learning experience
  • Real-time usage reports provide transparency

How – You must have the APIM Dev Portal User role assigned to access the new APIM Developer experience. Contact your system administrator for access.

Additional notes:

  • You can use OAuth or token-based authentication method
  • An additional fee is required to use the access-based certificate authentication method

For: API Developers | Administrators
Feature ID: 1182735

Framework for the composite API

What – This release introduces “Single Response – Composite APIs” to eliminate creation of wrappers over ICI Platform’s APIs while using them.

The Composite API Framework supports the following features:

API endpoint for supporting composite structure

Request and Response representation

Validation framework for composition

Orchestration logic for composite requests

Referencing field's structure and usage

Advantages – The framework helps simplify the implementation and makes the integration more efficient. How - API developer can work on ICI entities via single composite API request to trigger series of APIs calls in a single API call and get multiple request results in a single response body.

Value: User Experience | Ease of Use | Improved Efficiency
For: API Developers | Administrators
Feature ID: 1182667

API Endpoint Changes

8.2 RN 06.PNG

8.2 RN 07.PNG

8.2 RN 08.PNG

8.2 RN 09.PNG

8.2 RN 10.PNG

8.2 RN 11.PNG

8.2 RN 12.PNG

AI Applications

Beta Feature – Refer existing obligations when reviewing AI-discovered obligations

What – AI-discovered obligations are automatically categorized in a category and sub-category when presented for review and confirmation. When reviewing discovered obligations users can now refer to existing obligations in approved state belonging to the same category, sub-category and related agreements. Changing the category and sub-category, displays the relevant set of approved obligations.

Advantages

Referring Library Obligations can help you get a standard position/scope/language to be used while setting up a newly discovered obligation

Referring from Related Agreements helps you understand what obligations from parent (peer) contracts are to be set at the child level specially in case of back-to-back contracting (e.g., checking customer contracts and passing on the related obligations in supplier contracts)

How – Users can review AI-discovered obligations from the Review Obligation drawer, which can be accessed from the “Review Discovered Obligation” page.

Review Obligation drawer displaying Approved Obligations in Library Obligation

8.2 RN 35.PNG

Note: Library Obligations are to be added manually. Please refer to the OM wiki on how to setup an Obligation Library.

Review Obligation drawer displaying Approved Obligations in Related Agreements

8.2 RN 36.PNG

Note: Time needed to display Obligations from related agreements may vary depending upon the number of Linked agreements and count of Obligations within them.

Value: Efficiency | Time Saving
For: Legal Team | Contract Managers
Feature ID: 1366783

Sourcing

The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application.

Converting RFI to RFP or RFQ

What – ICI Sourcing application now allows creating an RFP or RFQ from an RFI from which the suppliers are shortlisted. Users can create multiple RFP’s or RFQ’s from a single RFI. 

Advantage – Saves time when creating an RFP or RFQ by allowing shortlisted suppliers to be selected from a previously completed RFI.  

How – Users can use the “Create from RFI” button from the Sourcing index page or from the Create RFP/RFQ option on the RFI that is in “Bidding Closed” state.

Value: User Experience
Feature ID: 1328960  

Shortlist Suppliers in RFx

What – An enhancement has been made to the existing Shortlist feature that allows buyers to select and shortlist specific suppliers for the next procurement stage. For example, from RFI to RFP or RFQ or from one round to another in the same RFX. The supplier Shortlist can be modified in certain RFx statuses.

Advantage – Helps accessing preferred suppliers quickly or remove them from the “Suppliers” page thereby saving time.

How – A “Shortlist Supplier” option is added on the “Suppliers” page.  

8.2.RN 4.png

Value: User Experience
For: Buyer and Administrator users
Feature ID: 1341682  

Sourcing Enhancements

8.2.RN T4.PNG

Obligation Management

The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application

Auto-create Obligations from Associations data

What – ICI Platform now facilitates improved Obligation intake from source Association records. An Obligation is automatically created from any defined associations such as Deliverables, SLA, Risk Assessments. For example, if a SOW has ‘Deliverable’ as an association, then the user can directly convert that deliverable into an Obligation.

Advantages – Streamlines and simplifies creation of Delivery Dates, Milestones, SLAs, Risk Assessments, and other obligations from associated records, improving process efficiency. Auto-creation of Obligations enhances tracking compliance centrally using Obligation Management.

How – You can use the “Create Obligation” menu option from the Associations object list view or details page.

8.2.RN 5.png

Value: User Experience | Contract Building | Managing Obligations | Process Efficiency
For: Risk Managers | Contract Administrators
Feature ID: 649740

Use “Date” & “DateTime” Attributes from Holding Agreement for Obligation Scheduling

What – Duedates and end dates for obligations can now be selected from any of the date attributes of the agreement.

Advantages

Eliminates the need for an Obligation creator to know specific dates.

Consistency in Obligation dates used across various members / obligation creators

Reduces the extra effort required in referring to Date Attributes of holding agreement entity (for example, Effective Date / Expiry Date) and use them in Obligation creation.

How – Two new attributes have been added to the Obligation Contract Type – “Select Due Date From” and “Select End Date From”. You can select a specific date value from the given options. The date value selected will be as per the actual date defined in the Agreement. For example, if you select “Expiry Date” value, an Obligation will be created with an expiry date that is same as the expiry date for the Agreement.

8.2.RN 6.png

 

Value: User Experience
For: Contract Operations
Feature ID: 913820

Obligation Management Enhancements

8.2.RN T5.PNG

Supplier Relationship Management

ICI Supplier Relationship Management application is certified to work with the 8.2 release

Supplier Profile and Supplier Master records synchronization

What – Supplier product and service categories are now automatically synced in the following events:

On supplier qualification, the product/service category updates get copied to the Supplier Master category field.

Buyers update the Supplier Master the information is synced with the Supplier Profile.

Buyers update the Supplier Profile the information is synced with Supplier Master.

Advantage – Supplier records are consistent and can be consumed across all Icertis applications.

How – If a supplier record in the database is modified depending on the conditions defined, the other relevant records also get updated automatically. 

Value: Efficiency
For: Buyer users
Feature ID: 1420117

Supplier Relationship Management Enhancements

8.2.RN T7.PNG

 

Rebates Enhancements

Rebates App in ICI Platform is enhanced to improve the usability and thereby improve the overall user experience, scalability and robust calculations. The Rebates App extends support for Big Data, AI, and Dynamic JSON. The enhancements in Rebates App can be summarized as below:

Refined seeded data model:

  • Minimal configuration and data reusability to make Rebates app more scalable.
  • Standardized naming conventions to avoid any conflicts with other apps.
  • Normalized data has improved Calculation Engine’s efficiency by 50%.
  • Dynamic JSON for Rebate program data eliminates the need to have distinct rebates and payout calculation for every business unit in an organization. The enhanced calculation engine extracts JSON data from the Agreement and its associated documents and maps it with the newly configured attributes.
  • Background tasks optimized to support big data such as calculation engine processing large invoice and agreement datasets. As an example, for performance testing, it took 35 seconds (approximately) to process 170,000  records (approximately) as compared to 1 minute (approximately) for 5000 records (approximately) in the earlier version.
  • Rebate program attributes are a part of associated document instead of an agreement, which enables handling multiple rebate programs within a contract. This also reduces the number of attributes in an agreement, that improves the performance of agreement creation.
  • Standardized attributes management by allowing 16-digit numbers with 6 decimal places.
  • Generic Product, Location, and Customer hierarchies allow customizing configuration and mapping it to the calculation engine.
  • Previously, configuration supported only up to 10 customer details as these details were part of the Agreement itself. However, now these details are migrated as Associated documents to support unlimited customer details.

Power BI Reporting:

  • Intuitive dashboard with advanced analytics on the rebate agreement distribution and accruals accumulation.
  • Out-of-the-box reports added in Power BI, which were earlier focused on Accruals, are now aligned with the overall performance of Rebates.
  • Improved visibility for Rebates payout calendar with the next payout dates.

Risk Management Enhancements

8.2.RN T6.PNG

Technology Updates

HTTP Artifact Binding Support for SSO Integration

What – In addition to HTTP POST and HTTP Redirect, ICI now supports HTTP Artifact binding for SSO (Single Sign-On) integration along with other IdPs like ADFS.

Advantages – With improved security, exchanging sensitive data across Id Provider (IdP) and Service Provider (SP) becomes more authenticated and trustworthy. This prevents intervention of any malicious party.

How – Administrator or Implementation Partner can choose between HTTP POST, HTTP Redirect and HTTP Artifact binding for SSO (Single Sign-On) integration, on the IdP server side.

Value: Secure Authentication Process
For: All ICI Users
Feature ID: 1342076

Microsoft retiring basic authentication for SMTP

What – Microsoft is retiring basic authentication for SMTP, and it would be necessary for customers using basic authentication to move to an alternate service. ICI now supports modern authentication with support for Microsoft Graph API.

Why – Provide support for modern authentication methods & ensure service continuity even after Microsoft retires basic authentication later this year (Oct 1, 2022).

How – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.

Value: Business as usual (BAU) without Impact
For: Authorized Signatories | Approval Team | Contributors
Feature ID: 1417372

Microsoft retiring Outlook REST API

What: The Icertis Outlook Add-In that currently uses the Outlook REST API will now use Microsoft Graph API.

Configurations are required for Outlook Add-In at the time of implementing or upgrading Icertis Contract Intelligence to work with Microsoft Graph API.

Why: Microsoft has announced that Outlook REST API will be deprecated in the month of November, 2022.

How – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.

Value: Business as usual (BAU) without Impact
For: Authorized Signatories | Approval Team | Contributors
Feature ID: 1417372

Support for StartTLS protocol

What – Adding support for the StartTLS protocol through NuGet MailKit for authentication and notification. StartTLS protocol command is used to inform the email server that the email client wants to upgrade from an insecure connection to a secure one using TLS or SSL.

Why – Customers have the option to use the StartTLS protocol, which supports enhanced security.

How – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.

Value: Business as usual (BAU) without Impact
For: Authorized Signatories | Approval Team | Contributors
Feature ID: 1417372

Bootstrap upgrade from version 4.5.2 to 5.1.3

What – The Bootstrap library has been upgraded from version 4.5.2 to 5.1.3. The support for Bootstrap library version 4.5.2 ends by Q3 2022. 4.5.2 is compatible with the new version.

Why – To address security vulnerabilities.

TFS ID: 1459132
 

Web Application Firewall & Azure Front Door

What

Implementing Azure Front Door (AFD) with the following settings:

Web Application Firewall (WAF) in diagnostic mode

Prevention Rule in AFD to restrict access from embargo countries.

Advantages – WAF & AFD help prevent against common exploits and vulnerabilities.

How – It can be configured, deployed, and managed via the Azure Portal, PowerShell, and CLI (command-line interface).

Value: Security
For: Administrators
Feature ID: 951438

 

Technical Requirements

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:

8.2.RN T8.PNG

8.2.RN T9.PNG

8.2.RN T10.PNG
8.2.RN T11.PNG

8.2.RN T12.PNG8.2.RN T13.PNG

8.2.RN T14.PNG

8.2.RN T15.PNG
8.2.RN T16.PNG
8.2.RN T17.PNG

8.2.RN T18.PNG

Accessibility Conformance

We ran accessibility conformance tests on the Icertis Contract Intelligence platform and Business Apps for Web Content Accessibility Guidelines 2.1 for Level A and Level AA standards. We did not evaluate for Level AAA standards.

While most of the product functionality has at least one method that meets the criterion without any known defects, some functionality of the product may not meet the conformance criteria. The full report is published in the following documents and can be made available on request:

ICI Platform Accessibility Conformance Report

ICI AI/ML Accessibility Conformance Report

ICI Reporting Accessibility Conformance Report

ICI Obligation Management Accessibility Conformance Report

ICI Sourcing Accessibility Conformance Report

ICI Proposal Management Accessibility Conformance Report

ICI SRM Accessibility Conformance Report

ICI Risk Management Accessibility Conformance Report

Known Issues

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

8.2.RN T19.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