From ICIHelp8.2
Jump to: navigation, search
 
(99 intermediate revisions by 6 users not shown)
Line 1: Line 1:
  
−
= ICI Release Notes - Release 7.15 =
+
= ICI Release Notes - Release 8.2 =
  
−
== Overview of Release 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 user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.
+
*[[#_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'''''
+
−
***Introducing &nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation.
+
−
***Providing &nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally.
+
−
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results.
+
−
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience.
+
−
***Viewing amendments in the grid view by default, for ease of use.
+
−
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience.
+
−
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels.
+
−
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection. 
+
−
**'''''Workflow Enhancements'''''
+
−
***Introducing &nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability.
+
−
***Allowing &nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience.
+
−
***Viewing clause extension attributes on the agreement entity for easy reference.
+
−
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles.
+
−
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch.
+
−
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&nbsp;
+
−
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &nbsp;
+
−
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable.
+
−
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents.
+
−
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately.
+
−
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &nbsp; entities with one or more users, by selecting a subset of an entity &nbsp; or on all instances of the entity, for all records available for the user.
+
−
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level.
+
−
***Providing the capability to control the supersede functionality for agreements by configuring rules.
+
−
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios.
+
−
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks.
+
−
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata.
+
−
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access.
+
−
***Supporting larger files for masterdata and associations.
+
−
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results.
+
−
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters.
+
−
***Providing the ability to configure filter on a lookup attribute &nbsp; with the “IN” operator on agreement contract type and template variables.&nbsp;
+
−
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation.
+
−
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates.
+
−
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).   
+
  
−
*<span style="color:#800080;">'''Mobile App Updates'''</span>
+
== Contract Authoring & Management&nbsp; ==
−
**Enhancing &nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users.
+
−
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines. 
+
  
−
*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>
 
−
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments.
 
−
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break.
 
−
**Provisioning success or failure message for workflow operations. 
 
  
−
*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>
+
=== Amend contracts preserving previously negotiated terms ===
−
**'''''Icertis Experience for Word'''''
+
−
***Supporting &nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session.
+
−
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries.
+
−
***Improving labeling of internal, external and fully signed copies of agreements for easy identification.
+
−
***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;
+
−
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses.
+
−
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.   
+
  
−
*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>
+
'''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.
−
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word.
+
−
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause.  
+
−
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration.
+
−
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries.
+
−
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights.
+
−
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&nbsp;
+
−
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&nbsp;
+
−
**Improving &nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.  
+
  
−
*<span style="color:#800080;">'''Enhancements to Reports'''</span>
+
'''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.
−
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates.
+
−
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users.
+
−
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&nbsp;
+
−
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version.
+
−
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information.
+
−
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability.  
+
−
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI.
+
−
**Enhancing localization support in reports.  
+
  
−
*<span style="color:#800080;">'''Improving the Icertis Experience'''</span>
+
'''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.
−
**'''''Signature Workflow'''''
+
−
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).<br/> Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.<br/> Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &nbsp; 
+
−
**'''''Icertis Experience for Salesforce'''''
+
−
***Providing the ability to send success and failures alerts for improved monitoring of messages.
+
−
***Triggering document assembly for automatic data sync and displaying completion notification.
+
−
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process. 
+
−
**'''''Icertis Experience for MS CRM'''''
+
−
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&nbsp;   
+
  
−
*<font color="#800080">'''Enhancements to Platform Tools'''</font>  
+
'''Value''': Compliance | User Experience<br/> '''For''': Legal Team | Authors | Contract Managers<br/> '''Feature ID''': 1233193
−
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches. 
+
  
−
*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>
+
=== Send multiple agreements packaged in a single envelope for electronic signature ===
−
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools. 
+
  
−
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.
+
'''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.
  
−
&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="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span> ==
+
'''How - '''Existing Esign functionality is enhanced to package peer agreements as a single bundle and send it for electronic signature.
  
−
<span style="color:#800080;">'''659853 – Upfront chevron view of agreement journey'''</span>
+
'''Value''': User Experience | Contract Building Performance<br/> '''For''': Contract Owners | Legal Compliance Team<br/> '''Feature ID''': 1369302
  
−
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&nbsp;
+
=== Quickly create and edit contract types in bulk using excel workbook ===
  
−
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&nbsp;
+
'''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, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.
+
'''Advantages'''
  
−
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.
+
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.
  
−
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:
+
Creating and editing multiple contract types at once will reduce time involved in configuring large contract types.
  
−
1.&nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.
+
'''How'''
  
−
2.'''Approve:'''&nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&nbsp;
+
A button “Bulk Contract Type” is now added under “Configure” tile.
  
−
3. '''Execute:&nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.
+
Users can generate pre-seeded contract type workbook, with 2 tabs in excel, contact type, and contract type attributes.
  
−
4. '''Manage:&nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.
+
'''Value''': User Experience<br/> '''For''': Admins | Legal Team | Contract Managers<br/> '''Feature ID''': 1342050
  
−
'''Note''':&nbsp;
+
== Icertis Experiences ==
  
−
*The chevron view is only applicable to agreement contract type (agreement&nbsp;and amendment).
+
=== Rules functionality added to Icertis Experience for Word ===
−
*By default, the chevron is disabled; it can be enabled for selected contract types.
+
−
*The chevron labels support localization.
+
−
<div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''512931 – Visibility of sections on the left navigation pane to non-team users'''</span></div>
+
−
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&nbsp;
+
  
−
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.<br/> &nbsp;
+
'''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.
  
−
<span style="color:#800080;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>
+
'''Advantages – '''Provides a familiar and intuitive interface for legal teams and contract authors to create conditional agreement templates.
  
−
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.
+
Reduced turnaround time, instead of switching while creating the clause and template
−
<div class="image-green-border">Configurators can:&nbsp;</div>
+
−
*Configure a smart link across any ICI entity that defines the entity relationships.
+
−
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities.
+
  
−
Users can:&nbsp;
+
'''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
  
−
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp;
+
=== Outlook Add-in – Labeling and validation for emails added to ICI ===
−
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results.
+
−
<div class="image-green-border">&nbsp;</div> <div class="image-green-border">Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.</div> <div class="image-green-border"><br/> For example, consider&nbsp;entities related in multi-level hierarchy as ''Agreement > Obligations > Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.</div> <div class="image-green-border"><br/> &nbsp;</div>
+
−
<span style="color:#800080;">'''584439 – Introducing the Contract Manager role for agreements&nbsp;'''</span>
+
  
−
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.
+
'''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.
  
−
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&nbsp;
+
'''Advantages – '''Avoid uploading duplicate email conversations in ICI.
  
−
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.
+
'''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;
  
−
With this release:&nbsp;
+
=== Revamping ICI Salesforce User Experience ===
  
−
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&nbsp;''action.
+
'''What''' – Revamping the ICI Salesforce user interface to give a better user experience, with addition of features and enhancement under agreement related sub tabs.
−
*Only one contract manager is available inside the agreement at any given point of time.
+
−
*The contract manager will have provisions same as that of primary owner.
+
−
*The contract manager name is displayed on the agreement summary page.
+
−
*Agreements can be searched using the contract manager name.
+
−
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user.  
+
  
−
&nbsp;
+
The following agreement sub tabs can now be seen with new capabilities:
  
−
<span style="color:#800080;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>
+
*Associations sub tab
 +
*Amendment sub tab
 +
*Note sub tab
 +
*Team sub tab
 +
*Collaboration sub tab
  
−
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&nbsp;
+
Some new features include:
  
−
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.
+
Hyperlink added in the first column of the association list grid navigating to the association details page within ICI Salesforce platform.
  
−
&nbsp;
+
Ability to preview the document from amendments sub tab.
  
−
<span style="color:#800080;">'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''</span>
+
The collaborations tab is now revamped from ICI Iframe to Salesforce native look and feel, with capability to view more messages.
  
−
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.
+
'''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.
  
−
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&nbsp;
+
'''How''' – Below are few screenshots of the revamped ICI Salesforce platform.
−
<div class="image-green-border">For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.</div> <div class="image-green-border">This is applicable to the following associations:&nbsp;</div>
+
−
*Import of Association (Line Item)
+
−
*Auto Attachment Association
+
−
*Obligation/ Fulfillment (Association of Association)
+
  
−
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.
+
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
  
−
&nbsp;
+
=== Salesforce – Visibility of products and services sold to customers ===
  
−
<span style="color:#800080;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>
+
'''What''' – ICI Salesforce experience users can now view the list of all the products and services sold to the customer under “Agreement Lines” subtab.
  
−
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.
+
'''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.
  
−
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&nbsp;
+
'''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.
 +
<div class="image-green-border">[[File:8.2.RN 3.png|720px|8.2.RN 3.png]]</div>
 +
'''Note: '''The “Agreement Lines” displays only active products and services from executed contracts.
  
−
Users can now:&nbsp;
+
'''Value''': User Experience<br/> '''For''': Sales Managers | Sales Executive<br/> '''Feature ID''': 1192973
  
−
*Capture multiple valid internal or external email addresses while working on agreements/ requests.
+
== Enhancements – Mobile App Experience ==
−
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.
+
  
−
&nbsp;
+
[[File:8.2 RN 32.PNG|720px|8.2 RN 32.PNG]]
  
−
<span style="color:#800080;">'''583186 – Ability to add amendment on expired agreement'''</span>
+
== Administration & Configuration ==
  
−
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.
+
=== Enhanced ICI startup validation architecture ===
  
−
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&nbsp;
+
'''What''' – A new validation framework for configuration keys and related metadata to resolve incorrect or missing keys and ensure seamless startup of ICI instances.
  
−
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.
+
'''Advantages – '''Timely validation of configuration keys and guardrails to prevent unnecessary startup blockers.
−
<div class="image-green-border">&nbsp;</div>
+
−
<span style="color:#800080;">'''593928 – Ability to configure sender email ID for automated emails'''</span>
+
  
−
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.
+
'''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.
  
−
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&nbsp;
+
'''Value''': Reliability, Supportability<br/> '''For''': Administrators<br/> '''Feature ID''': 1373024
  
−
Administrators can now:
+
=== Configure E-Signature Integrations within ICI ===
  
−
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement.
+
'''What''' – E- signature configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
−
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to.
+
−
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses.  
+
−
<div class="image-green-border">&nbsp;</div>
+
−
<span style="color:#800080;">'''593938&nbsp;– Time Zone support for date-dependent automated processes'''</span>
+
  
−
In ICI, there are scheduled jobs that perform certain actions on&nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.
+
'''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;
  
−
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.
+
'''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
  
−
With this release:
+
=== Integrated Config keys validation framework ===
  
−
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination).  
+
'''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.
−
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities.
+
−
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance.
+
−
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance.
+
−
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date.  
+
  
−
'''Note''':&nbsp;The time zone-based processing can be enabled for all contract types across&nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.
+
'''Advantages – '''Helps prevent issues that occur during application startup.
−
<div class="image-green-border">&nbsp;</div>
+
−
<span style="color:#800080;">'''512930 – Triggering service bus events for all actions'''</span>
+
  
−
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&nbsp;
+
'''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.
  
−
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&nbsp;
+
'''Value''': Self-service &nbsp;<br/> '''For''': Administrators<br/> '''Feature ID''': 1373030
  
−
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.<br/> &nbsp;
+
=== Configure SSO integrations within ICI ===
  
−
<span style="color:#800080;">'''545126 – Availability of business status value in ICI event messages'''</span>
+
'''What''' – SSO configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
  
−
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.
+
'''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;
  
−
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.
+
'''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
  
−
&nbsp;
+
=== Customer-specific SAML/OAuth SSO Configurations ===
  
−
== Mobile App Updates ==
+
'''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.
  
−
<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span><br/> Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.
+
'''Advantages''' –
  
−
&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.
  
−
<span style="color:#800080;">'''850259 – Updating logo and attributes to new guidelines'''</span><br/> As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.
+
'''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.
  
−
&nbsp;
+
'''Value: '''Self-service, Reliability, Supportability<br/> '''For:''' Technical Admins<br/> '''Feature ID: '''1317384
  
−
<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span><br/> With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.
+
=== Error-handling framework ===
  
−
&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.
  
−
<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span><br/> With this release, the UI WebView component for iOS has been deprecated.
+
The framework provides the following features:
  
−
&nbsp;
+
Detailed and structured data to determine severity, origin, module, area & source of the error.
  
−
== ICI API Enhancements&nbsp; ==
+
No unhandled exceptions emanating from the system.
−
<div class="image-green-border">
+
−
<span style="color:#800080;">'''704069 – Enhancing ICI API 2.0 implementation'''</span>
+
  
−
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&nbsp;
+
Detailed logging is done in a central repository like Kibana.
  
−
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:
+
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.
  
−
*Contract Requests
+
'''Why '''– Eliminates time required to locate and understand the issue and reduces the overall time needed to fix issues.
−
*Agreements
+
−
*Associations
+
−
*Amendments
+
  
−
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.
+
'''How '''– ExceptionHandler attribute is introduced, which will have following Origin, Area, Module, Sub Module in the form of code.
  
−
&nbsp;
+
For example: 50000030021360X8013153 (shown on User Interface)
  
−
<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>
+
Breakdown of the code is as follows:
  
−
ICI already supports downloading agreements.
+
5 – Severity
  
−
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.
+
00 – Origin (First parameter of Exception Handling attribute)
  
−
&nbsp;
+
00 – Source (mostly internal)
  
−
<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>
+
03 – Area (Second parameter of Exception Handling attribute)
  
−
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.
+
002 – Module (Third parameter of Exception Handling attribute)
  
−
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.
+
136 – SubModule (Fourth parameter of Exception Handling attribute)
  
−
<br/>  <br/> <span style="color:#800080;">'''660859 – Supporting correlation Id in APIs'''</span>
+
0X8013153 – Standard C# HResult which can be googled to see the exception type
  
−
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;
+
Class decorators for Exception Handling
  
−
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&nbsp;
+
['''ExceptionHandler''' (exceptionOrigin: ExceptionOrigin.Core, exceptionArea: ExceptionArea.CLM, module: ExceptionAreaModule.CLM_AdminTask, submodule: ExceptionAreaSubModule.CLM_AdminTask_Root)]
  
−
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&nbsp;
+
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
  
−
The following API changes have been made to ensure that the existing implementation and code do not break:
+
=== Administration & Configuration Enhancements ===
  
−
*Provided support for a Tracking Id header in every request for logging.&nbsp;
+
[[File:8.2 RN 34.PNG|720px|8.2 RN 34.PNG]]
−
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return).  
+
−
*The called API path with query string will be logged in Kibana.&nbsp;
+
  
−
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.
+
== Reporting Analysis ==
  
−
This can be used for:
+
=== Dashboard and Power BI reports for Supplier Evaluation ===
  
−
*Related API Calls
+
'''What – '''An interactive Supplier Evaluation dashboard with the following features is now available out-of-the-box:
−
*Async operations
+
−
*Bulk operations
+
−
*Status check operations &nbsp; &nbsp;
+
−
</div>
+
−
&nbsp;
+
  
−
== Enhancements to ICI Add-ins&nbsp; ==
+
Interactive graphs for status of evaluation cases, evaluation distribution by performance, and ageing in review or approval states.
  
−
<span style="color:#800080;">'''745266 – Supporting online editing of agreements'''</span>
+
Enlists the top and poor performing suppliers based on a host of filters like evaluation type, period of evaluation, supplier name and more.
  
−
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&nbsp;
+
Captures evaluations that are awaiting supplier inputs for missing documents.
  
−
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.
+
360-degree supplier performance score card about different evaluations, KPI and performance trend over a time period.
  
−
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.
+
Capture supplier documents/ certificates that are expired or expiring within 5 days.
  
−
It is now possible for:
+
'''Advantages –'''
  
−
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&nbsp;
+
Information is represented visually and is easier to consume and track.
−
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information.  
+
  
−
'''Note:&nbsp;'''
+
Assist the procurement team in setting up the right expectations and manage supplier relationships.
  
−
*The online Word editor is available only for users with valid Office 365 subscription.
+
Insights into poorly performing suppliers can help in planning proactive performance improvement.
−
*Only users with edit privileges on a document can make changes to the document online.
+
−
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly.  
+
  
−
<br/> <span style="color:#800080;">'''588686 – Tagging clause extended attributes in clause text'''</span>
+
'''How – '''The dashboard and reports can be accessed from the Supplier Management -> Dashboard.
  
−
ICI allows users to capture additional details for clauses in the extended attributes.&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
  
−
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.
+
=== New filters added to Agreement and Amendment based SSRS reports ===
  
−
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.
+
'''What – '''The following filters are now available on UI for DRF Agreements Pending Approval and DRF Expired Agreements reports:
  
−
&nbsp;
+
Contract Type
  
−
<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>
+
Org Unit
  
−
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.
+
Agreement Owner
  
−
Users can now:
+
Agreement Status
  
−
*Search and filter clauses and templates based on the name or text inside the clause or template respectively.
+
Created Date (Created Date From, Created Date To)
−
*Perform free text search on clauses and templates.
+
  
−
&nbsp;
+
Time Zone
  
−
<span style="color:#800080;">'''603690 – Updating templates automatically with latest clause version'''</span>
+
'''Note''': These reports are default and cannot be customized as of now.
  
−
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.
+
'''Advantages – '''One or more filters can be applied to help view the data in contextual slices.
  
−
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&nbsp;
+
'''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:8.2 RN 16.png|720px|8.2 RN 16.png]]</div>
 +
'''Value: '''Self-service<br/> '''For: '''Managers | Legal Team | Decision Makers<br/> '''Feature ID: '''1346718
  
−
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.
+
=== Self-Service Configuration page for creating custom SSRS reports and dynamic views ===
  
−
<br/>  <br/> <span style="color:#800080;">'''593421 – Labeling agreement document versions as per signature copy'''</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 in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.
+
'''Advantages – '''Provides a simpler path to customize reports and can be done by technical users without intervention from Icertis teams.
  
−
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.
+
'''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;
+
== APIs ==
  
−
== Enhancements to Artificial Intelligence Applications in ICI ==
 
  
−
<span style="color:#800080;">'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''</span>
+
=== API Management Service ===
  
−
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &nbsp;
+
'''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 this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&nbsp;
+
With the API Management, the following is possible for customers:
  
−
Users can now:&nbsp;
+
*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
  
−
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &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.
−
*View playbook details in a separate resizable window.&nbsp;
+
−
*View all playbook positions for a selected contract type with options to search and filter within.&nbsp;
+
−
*View all playbook positions for a selected agreement clause.&nbsp;
+
−
*Add deviation to the clause from playbook “Details” page.&nbsp;
+
−
*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word.  
+
  
−
&nbsp;
+
'''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.
  
−
<span style="color:#800080;">'''575475 – Automating user feedback for clauses, obligations and attributes'''</span>
+
'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
  
−
ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &nbsp;
+
=== Icertis API Hub–A New Developer Experience for Working with APIs ===
  
−
With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.
+
'''What – '''The new Icertis API Developer Experience is simple, secure, and immersive for the developers.
  
−
<br/> <span style="color:#800080;">'''539492 – Improving clause delineation in DiscoverAI'''</span>
+
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.
  
−
Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&nbsp;
+
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.
  
−
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&nbsp;
+
'''Advantages''' –
  
−
Users can now:&nbsp;
+
*Smoother developer on-boarding and learning experience
 +
*Real-time usage reports provide transparency
  
−
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&nbsp;
+
'''How – '''You must have the APIM Dev Portal User role assigned to access the new APIM Developer experience. Contact your system administrator for access.
−
*Create a sub-clause within a discovered clause.&nbsp;
+
−
*Change the clause category and the level (parent or child) of the discovered clause. &nbsp;
+
−
*Choose to view only the level 0 clauses.  
+
  
−
&nbsp;
+
Additional notes:
  
−
<span style="color:#800080;">'''770375 – Merging metadata discovery page with attribute page'''</span>
+
*You can use OAuth or token-based authentication method
 +
*An additional fee is required to use the access-based certificate authentication method
  
−
Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&nbsp;
+
'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
  
−
With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&nbsp;
+
=== Framework for the composite API ===
  
−
Users can:&nbsp;
+
'''What''' – This release introduces “Single Response – Composite APIs” to eliminate creation of wrappers over ICI Platform’s APIs while using them.
  
−
*View the discovery completion progress.&nbsp;
+
The Composite API Framework supports the following features:
−
*Identify discoverable attributes marked with the spinner icon.
+
−
*Get side-by-side document view for discoverable attributes.
+
−
*Get side-by-side document view for tagged attributes upon completion of discovery.
+
  
−
The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.
+
API endpoint for supporting composite structure
  
−
&nbsp;
+
Request and Response representation
  
−
<span style="color:#800080;">'''727312 – Formatting based clause delineation for additional document types'''</span>
+
Validation framework for composition
  
−
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.
+
Orchestration logic for composite requests
  
−
With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.
+
Referencing field's structure and usage
  
−
Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.
+
'''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.
  
−
&nbsp;
+
'''Value''': User Experience | Ease of Use | Improved Efficiency<br/> '''For''': API Developers | Administrators<br/> '''Feature ID''': 1182667
  
−
<span style="color:#800080;">'''727314 – Supporting additional languages in AI apps'''</span>
+
=== API Endpoint Changes ===
  
−
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.
+
[[File:8.2 RN 06.PNG|720px|8.2 RN 06.PNG]]
  
−
With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.
+
[[File:8.2 RN 07.PNG|720px|8.2 RN 07.PNG]]
  
−
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.
+
[[File:8.2 RN 08.PNG|720px|8.2 RN 08.PNG]]
  
−
&nbsp;
+
[[File:8.2 RN 09.PNG|720px|8.2 RN 09.PNG]]
  
−
<span style="color:#800080;">'''710739 – Configuring custom rules in DiscoverAI'''</span>
+
[[File:8.2 RN 10.PNG|720px|8.2 RN 10.PNG]]
  
−
Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&nbsp;
+
[[File:8.2 RN 11.PNG|720px|8.2 RN 11.PNG]]
  
−
With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&nbsp;
+
[[File:8.2 RN 12.PNG|720px|8.2 RN 12.PNG]]
  
−
The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.<br/> &nbsp;
+
== AI Applications ==
  
−
== Enhancements to Reports ==
+
=== Beta Feature – Refer existing obligations when reviewing AI-discovered obligations ===
  
−
<span style="color:#800080;">'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''</span>
+
'''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.
  
−
ICI provides default reports such as “Attributes Value Report” which captures the attribute values and edits made over time, and the “Attribute Information Report” which provides details of the attribute properties and its incorporation in different contract types. Previously, attributes tagged in clauses and templates could also be checked by using the Preview mode or using Icertis Experience for Word. However, administrators often need to understand how an attribute has been used in these entities; for example, to carry out an impact analysis before removing an obsolete attribute.
+
'''Advantages''' –
  
−
With this release, a new “Tagged Attributes Report” has been introduced as part of Admin Reports, which helps administrators understand the complete profile of an attribute, and how it has been tagged across different clauses and templates. This saves them considerable time as they no longer need to manually examine each clause and template, in addition to reducing manual errors.
+
Referring '''Library Obligations''' can help you get a standard position/scope/language to be used while setting up a newly discovered obligation
  
−
This report available on the “Reports” tile can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable and Attribute Display Name.&nbsp;
+
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)
  
−
'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.
+
'''How – '''Users can review AI-discovered obligations from the Review Obligation drawer, which can be accessed from the “Review Discovered Obligation” page.
  
−
&nbsp;
+
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.
  
−
<span style="color:#800080;">'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''</span>
+
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.
  
−
Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&nbsp;
+
'''Value''': Efficiency | Time Saving<br/> '''For''': Legal Team | Contract Managers<br/> '''Feature ID''': 1366783
  
−
In this release, the report is enhanced to display a “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 for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.
+
== Sourcing ==
  
−
<br/>  <br/> <span style="color:#800080;">'''514611 – Enhancing Notifications History Report for an entity'''</span>
+
The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application.
  
−
ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&nbsp;
+
=== Converting RFI to RFP or RFQ ===
  
−
The default SSRS 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.&nbsp;
+
'''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;
  
−
The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&nbsp;
+
'''Advantage''' – Saves time when creating an RFP or RFQ by allowing shortlisted suppliers to be selected from a previously completed RFI. &nbsp;
  
−
*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&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.
−
*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.  
+
  
−
&nbsp;
+
'''Value''': User Experience<br/> '''Feature ID''': 1328960&nbsp;&nbsp;
  
−
<span style="color:#800080;">'''742607 – Supporting localization for status and business status'''</span>
+
=== Shortlist Suppliers in RFx ===
  
−
With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&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.
  
−
*Obligation Management Health Report, Obligation Management Dashboard Report.&nbsp;
+
'''Advantage''' – Helps accessing preferred suppliers quickly or remove them from the “Suppliers” page thereby saving time.
−
*Contract type names, if the respective entity has locale resource key values in database.&nbsp;
+
−
*Status filter on all reports, drop-down with Yes/No values.&nbsp;
+
−
*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&nbsp;
+
−
*Dynamic column headers (for example, RFx Details Report in Sourcing).&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><br/> 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;
+
'''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;
  
−
Now, this filter is 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.
+
=== Sourcing Enhancements ===
  
−
&nbsp;
+
[[File:8.2.RN T4.PNG|720px|8.2.RN T4.PNG]]
  
−
<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>
+
== Obligation Management ==
  
−
The “Cycle Time Report” displays the cycles for contracts 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;
+
The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application
  
−
With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.
+
=== Auto-create Obligations from Associations data ===
  
−
&nbsp;
+
'''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.
  
−
<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</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.
  
−
A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.<br/> &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
  
−
== Integrations ==
+
=== Use “Date” & “DateTime” Attributes from Holding Agreement for Obligation Scheduling ===
  
−
<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
+
'''What – '''Due'''dates and end dates for obligations can now be selected from any of the date attributes of the agreement.'''
  
−
ICI has now improved the electronic signature process to provide a unified flexible signature workflow.
+
'''Advantages'''
  
−
With this release, the following capabilities have been added to the ICI signature process:
+
Eliminates the need for an Obligation creator to know specific dates.
  
−
*Introducing the hybrid signature process.
+
Consistency in Obligation dates used across various members / obligation creators
−
*Enabling DocuSign console for users to add and modify the signatories.
+
−
*Support for preview in DocuSign console.
+
−
*Support for tagging signatories in DocuSign console.
+
−
*Support for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign.
+
  
 +
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.
 +
<div class="image-green-border">[[File:8.2.RN 6.png|600px|8.2.RN 6.png]]</div>
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>
+
'''Value''': User Experience<br/> '''For''': Contract Operations<br/> '''Feature ID''': 913820
 +
 
 +
=== Obligation Management Enhancements ===
 +
 
 +
[[File:8.2.RN T5.PNG|720px|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:
  
−
Previously, DocuSign integration provided support for sequential signatures. This capability has 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.
+
On supplier qualification, the product/service category updates get copied to the Supplier Master category field.
  
−
With this release:
+
Buyers update the Supplier Master the information is synced with the Supplier Profile.
  
−
*Users can define the parallel signatories using rules.
+
Buyers update the Supplier Profile the information is synced with Supplier Master.
−
*Users can configure parallel signatories via the DocuSign console.
+
−
*DocuSign process can be triggered in parallel for the configured signatories.
+
−
*Sync back, audit and history can be captured in the ICI agreement.  
+
  
−
<br/> <span style="color:#800080;">'''701825– Supporting multiple vendors for electronic signature'''</span>
+
'''Advantage''' – Supplier records are consistent and can be consumed across all Icertis applications.
  
−
Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&nbsp;
+
'''How''' – If a supplier record in the database is modified depending on the conditions defined, the other relevant records also get updated automatically.&nbsp;
  
−
With this release, users can:
+
'''Value''': Efficiency<br/> '''For''': Buyer users<br/> '''Feature ID''': 1420117
  
−
*Select the provider at the agreement or amendment level, for electronic signature and execution. This is achieved by using the choice attribute “Esignature Provider” with “DocuSign” and “Adobe Sign” as options.
+
=== Supplier Relationship Management Enhancements ===
−
*Define standard rules and conditions to automatically select the provider for agreements and amendments.
+
  
−
'''Note: '''This is applicable to DocuSign and Adobe Sign.
+
[[File:8.2.RN T7.PNG|720px|8.2.RN T7.PNG]]
  
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''</span>
+
== Rebates Enhancements ==
  
−
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 changes on the agreement document.
+
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:
+
'''Refined seeded data model:'''
  
−
*Document assembly is triggered automatically after every update from Salesforce. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”.  
+
*Minimal configuration and data reusability to make Rebates app more scalable.
−
*Upon completion of data sync task for an opportunity, the Salesforce data sync task raises a “Data Sync Complete/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for the given opportunity.  
+
*Standardized naming conventions to avoid any conflicts with other apps.
−
*A message containing the opportunity Id and agreement SysId is updated, and the time stamp is also displayed.  
+
*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.  
  
−
<br/> <span style="color:#800080;">'''796155 – Improving data flow between Salesforce and ICI'''</span>
+
'''Power BI Reporting:'''
  
−
Previously, when changes were made to an agreement in the "Sent for External Signature" status, the data was synced from Salesforce to the ICI UI, but not in the template document.&nbsp;
+
*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.  
  
−
Additionally, the agreement status changed only when an attribute which is tagged in the template was changed. However, if an attribute which was not tagged in the template changed, it was updated in the ICI UI and the status of agreement also remained the same.
+
=== Risk Management Enhancements ===
  
−
With this release:
+
[[File:8.2.RN T6.PNG|720px|8.2.RN T6.PNG]]
  
−
*Changes made to agreements in Salesforce while they are in Send for External Signature, Send for Internal Signature, Executed or Expired statuses will not be updated to the ICI UI.&nbsp;
+
== Technology Updates ==
−
*When attributes are not tagged in the template document and the same attribute is mapped with Salesforce, updating the value of that field in Salesforce will change the status of the agreement from "Waiting for Approval" or "Approved" to "Draft"; unless it is a tracking attribute.&nbsp;
+
  
−
This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.
+
=== HTTP Artifact Binding Support for SSO Integration ===
  
−
&nbsp;
+
'''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;">'''674469 – Sending success or failures alerts for monitoring in Salesforce'''</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.
  
−
An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&nbsp;
+
'''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.
  
−
With this release:
+
'''Value: '''Secure Authentication Process<br/> '''For: '''All ICI Users<br/> '''Feature ID: '''1342076
  
−
*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&nbsp;
+
=== Microsoft retiring basic authentication for SMTP ===
−
*Additional logging has been introduced for ICI-Salesforce integration messages. Every message log will include the status, message Id and the incoming JSON details.&nbsp;
+
−
*Configurators also send email notifications to ICI users on forward/reverse data sync so that the recipients can take appropriate actions.
+
  
−
<br/> <span style="color:#800080;">'''679797 – Supporting OAuth in Salesforce adapter'''</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.
  
−
Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user Id and password for authentication and authorization of production systems in an enterprise. Security organizations also had stringent security policies which do not approve user id or password authentication process.&nbsp;
+
'''Why '''– Provide support for modern authentication methods & ensure service continuity even after Microsoft retires basic authentication later this year (Oct 1, 2022).
  
−
With this release, support is provided for OAuth, a more secured authentication and authorization process. This makes the ICI application more secured and is easy for customers to manage using an actual business user Id, instead of a service user to update the records in ICI. It also removes any access issues involved in the business process. Customers do not have to add owners of the record to contracts team to obtain access.
+
'''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.
  
−
When entities in Salesforce are updated by a user, the process builder sends a message to 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;
+
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
  
−
When data in Salesforce is updated and data sync job is triggered, the Salesforce adapter will use client Id and secret key from AKV to fetch a user token, for invoking Salesforce APIs, using OAuth protocol.
+
=== Microsoft retiring Outlook REST API ===
  
−
&nbsp;
+
'''What''': The Icertis Outlook Add-In that currently uses the Outlook REST API will now use Microsoft Graph API.
  
−
<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
+
Configurations are required for Outlook Add-In at the time of implementing or upgrading Icertis Contract Intelligence to work with Microsoft Graph API.
  
−
Previously, MS CRM plugin used logged in user credentials to invoke ICI APIs when sales users updated any entity in MS CRM. Also, reverse data sync flow used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&nbsp;
+
'''Why''': Microsoft has announced that Outlook REST API will be deprecated in the month of November, 2022.
  
−
ICI now uses the client id and secret key instead of user id and password for authentication/authorization process between Salesforce 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;
+
'''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.
  
−
Users will have the option to choose the authentication mechanism to be used. The system will provide the support for backward compatibility of old username and password flow.
+
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
  
−
&nbsp;
+
=== 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.<br/> <br/> '''Why''' – Customers have the option to use the StartTLS protocol, which supports enhanced security.
  
−
== ICI Platform Tools ==
+
'''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;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''
+
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
  
−
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.<br/> The following entities are now supported:
+
=== Bootstrap upgrade from version 4.5.2 to 5.1.3 ===
  
−
*Organizations (Orgs), Organization Groups (Org Groups)
+
'''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.
−
*Users, User Groups, Security Groups
+
−
*Role Action Mapping
+
−
*Currencies
+
−
*Reasons
+
−
*Attribute Group
+
−
*SLA Matrix
+
−
*Notification Category
+
−
*Default Search Columns
+
−
*Cascade Team
+
−
*Application Settings
+
−
*Global/Admin Saved Searches
+
  
−
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.
+
'''Why''' – To address security vulnerabilities.
 +
 
 +
'''TFS ID''': 1459132<br/> &nbsp;
 +
 
 +
=== 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<br/> '''For''': Administrators<br/> '''Feature ID''': 951438
  
 
&nbsp;
 
&nbsp;
  
−
== Partner Enablement ==
+
= Technical Requirements =
  
−
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
+
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.
  
−
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&nbsp;
+
The software and hardware requirements for the client system as well as the mobile application are listed in the table below:
  
−
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:
+
[[File:8.2.RN T8.PNG|720px|8.2.RN T8.PNG]]
  
−
*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.  
+
[[File:8.2.RN T9.PNG|720px|8.2.RN T9.PNG]]
  
−
*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.  
+
[[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]]
  
−
*Working with ICI Tasks: Updated for the 7.15 release.  
+
[[File:8.2.RN T12.PNG|720px|8.2.RN T12.PNG]][[File:8.2.RN T13.PNG|720px|8.2.RN T13.PNG]]
  
−
*Working with ICI Hooks:'''Updated for the 7.15 release.'''
+
[[File:8.2.RN T14.PNG|720px|8.2.RN T14.PNG]]
  
−
*ICI Developer Library: Updated for the 7.15 release.  
+
[[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]]
  
−
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release.  
+
[[File:8.2.RN T18.PNG|720px|8.2.RN T18.PNG]]
  
−
*Self-Serve Tools:'''Updated for the 7.15 release.'''
+
= Accessibility Conformance =
  
−
&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.
  
−
== Technical Requirements for Release 7.15 ==
+
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:
  
−
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.
+
ICI Platform Accessibility Conformance Report
  
−
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]
+
ICI AI/ML Accessibility Conformance Report
  
−
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]
+
ICI Reporting Accessibility Conformance Report
  
−
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]
+
ICI Obligation Management Accessibility Conformance Report
  
−
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]
+
ICI Sourcing Accessibility Conformance Report
  
−
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]
+
ICI Proposal Management Accessibility Conformance Report
  
−
&nbsp;
+
ICI SRM Accessibility Conformance Report
  
−
&nbsp;
+
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:
 +
 
 +
[[File:8.2.RN T19.PNG|720px|8.2.RN T19.PNG]]
  
−
'''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 

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