From ICIHelp8.1
Jump to: navigation, search
 
(96 intermediate revisions by 6 users not shown)
Line 1: Line 1:
  
−
= ICI Release Notes - Release 7.15 =
+
= ICI Release Notes - Release 8.1 =
  
−
== Overview of Release 7.15 ==
+
== Release 8.1 New Features ==
  
−
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.
+
These release notes provide an overview of the enhancements to ICI, the ICI experience for integrations, and so on.
  
−
The key enhancements of this release include:
+
•      Refer to the [[#_Technical_Requirements_8.1|'''Technical Requirements''']] for the release in this document.
  
−
*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>
+
•&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.1/index.php?title=ICI_Help '''Wiki'''] documentation (also found in your ICI help section) for details on all ICI features and functionalities.
−
**'''''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>
+
The 8.1 Release introduces the following enhancements to the Icertis Contract Intelligence (ICI) platform:
−
**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>
+
== Icertis Contract Intelligence&nbsp; ==
−
**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>
+
=== Agreement & Platform&nbsp; ===
−
**'''''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>
+
'''A new collaboration experience with Microsoft Teams'''
−
**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>
+
ICI now leverages the powerful capabilities of Microsoft Teams to help internal teams collaborate on contract creation workflow and expediting the contracting lifecycle. The Teams integrations will help customers to use a single communication system and discussions can be held in context of the agreement.
−
**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>
+
The feature includes:
−
**'''''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>
+
*Contract owner can initiate a collaboration on MS teams from agreement details page and also invite agreement team members to participate in the discussion.
−
**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.  
+
*The latest version of the agreement document is also made available on the teams channel while initiating the collaboration. Participants can review, redline the agreement document in MS teams and publish the edited document back to ICI as a new version.  
 +
*The documents associated with main agreement in ICI can also referenced in MS teams channel
  
−
*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>
+
Feature ID: 1188391
−
**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.
+
'''Negotiate and Update Agreements with the new Outlook Add-in'''
  
−
&nbsp;
+
The new Outlook Add-in connects users’ emails with Icertis Contract Intelligence and provides improved collaboration capabilities and ensures information sent on emails is tracked for audit and governance on ICI. In addition, the new add-in provides a better interaction design, in line with the modern ACE user experience released in version 8.0.
  
−
== <span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span> ==
+
The Add-in for Microsoft Outlook Desktop is supported on Windows and Mac OS. Once installed, an '''Icertis Experience for Outlook''' pane is accessible from Outlook. The pane provides access to ICI agreement data, along with success and error messaging for interactions. It can be pinned on the interface for easy access.
  
−
<span style="color:#800080;">'''659853 – Upfront chevron view of agreement journey'''</span>
+
With the Outlook Add-in improvements, users can now do the following:
  
−
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;
+
*Add attached documents in emails as associations or a new agreement version in ICI.
 +
*Preview Agreement and Association documents from the Outlook Add-in.
 +
*Drag-and-drop single or multiple emails as associations.
 +
*Replace existing associated document with a new email or email attachment.
 +
*Access agreements and associated documents from the Outlook plugin and email them attachments to reviewers or approvers any stakeholders.
 +
*New incoming messages for email threads marked as associated documents are automatically added as new associated documents.&nbsp;  
  
−
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&nbsp;
+
Feature IDs: 1137119, 1137121
  
−
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.
+
'''Quick & Easy Agreement Creation'''
  
−
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.
+
Agreement Contract Types now come with a Quick Creation option. For all agreements using this option, users can fill all the necessary information on a single page and publish the contract or send it for approval immediately.
  
−
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:
+
Feature ID: 1183356
  
−
1.&nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.
+
'''More Quick Action Options'''
  
−
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;
+
The Quick Actions widget “What would you like to do” has been enhanced to provide multiple actions/links with one quick action line item. For example, “Create MSA” quick action now provides multiple links catering to “Own” and “Third Party” paper selections, as displayed in the image below.
 +
<div class="image-green-border">[[File:RN 8.1 1.png|520px|RN 8.1 1.png]]</div>
 +
Feature ID: 1183310
  
−
3. '''Execute:&nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.
+
'''External Emails Split to Ensure Compliance&nbsp;'''
  
−
4. '''Manage:&nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.
+
Contracts sent for review or approval by email to other parties, legal consultants and users not within ICI are now split in two parts. A URL and passcode can be shared with the users and the review can be done completely online. No need of downloading and attaching documents and tracking versions offline. The process is quick, secure and easy to audit.<br/> Two emails are sent, One email is sent containing the agreement URL and the other with the passcode to access the URL. This method could be used for requesting reviews, reviews and approval.<br/> <br/> Users can also resend the notification to external users whose reviews are pending, with the help of the “Resend Passcode Notification” button.<br/> <br/> To enable this feature, the implementation team needs to configure it explicitly.&nbsp;<br/> <br/> Feature ID: 1216716&nbsp;
  
−
'''Note''':&nbsp;
+
'''Deviation management for text and tables outside content control'''
  
−
*The chevron view is only applicable to agreement contract type (agreement&nbsp;and amendment).
+
If changes are made to the plain text in agreements or tables in associations of an agreement document (text which is not a clause or attribute), a deviation can now be triggered to help Legal teams exercise greater content control. The changes are highlighted and the deviations will flow through an approval process.<br/> <br/> Feature ID: 1183384&nbsp;
−
*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;
+
'''Support for Microsoft Powerpoint documents'''
  
−
<span style="color:#800080;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>
+
ICI now supports Microsoft Powerpoint file formats (files with .ppt and .pptx extension) as third-party paper agreement file formats. In addition to PDF and DOCX file formats, users can now create and negotiate contracts using PPT and PPTX files.
  
−
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.
+
Feature ID: 1183367
−
<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;
+
'''Online Editing Of Own Paper'''
  
−
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp;
+
In this release, ICI is enhancing its existing online editing feature &nbsp;by supporting online editing of own paper documents. using Microsoft WOPI.We have improved the experience for editing agreements with Microsoft Online applications In this release.
−
*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.
+
The following improvements can be observed:
  
−
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;
+
*Documents with editable content control can be edited and and values are is synced seamlessly.  
 +
*The track changes option will now track all the changes made by the users in reviewing mode, creating a redlined version of the document.
 +
*The empty content control will be displayed as blank instead of “obj”.
 +
*The content controls within tables can now be edited with associations tagged as tables and saved searches.Content controls within tables will now be editable.&nbsp;  
  
−
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.
+
Feature ID: 1287270&nbsp;
  
−
With this release:&nbsp;
+
'''Support for Inheritance of Bulk Associations&nbsp;'''
  
−
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&nbsp;''action.
+
In addition to attributes and associations, now bulk associations contract types (BACT) and their extension attributes can now be inherited from parent to child agreements.&nbsp;
−
*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 agreements with BACT associations will get inherited asynchronously along with all extension attributes of all the associations. The bulk associations will also work as they do in parent agreements.
  
−
<span style="color:#800080;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>
+
Feature ID: 1278205&nbsp;
  
−
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;
+
'''Enhancement to Download all Agreement & Associated Documents in one click''' &nbsp;
  
−
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.
+
With this release, we have expanded on the Download all capability which allowed users can to download the agreement and itsall associated documents in one click saving much time and effort.&nbsp;
  
−
&nbsp;
+
This functionality was earlier available when the signature type for the agreement was set to manual, it is now available for electronic and hybrid signature types as well.
  
−
<span style="color:#800080;">'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''</span>
+
Additionally, the “Download All” button will now be visible to users based on the role action mapping in superseded state as well.&nbsp;
  
−
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.
+
Feature ID: 980342&nbsp;
  
−
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;
+
'''Platform changes to enhance UX for Business Applications'''
−
<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.
+
To improve findability and relevance of information pertaining to a particular business application, some configuration changes are now available in the platform. These changes significantly improve the search and usability experience when working with Agreements, Associations or any Business Application.
  
 +
The following configurations are now supported:
 +
 +
*Business Applications have dedicated index pages, where users can search for the information pertaining to the specific business application.
 +
*Agreements and Associations index pages do not show information from Business Applications.
 +
*On the Advanced Search page, users have a choice to search for information from Agreements or specific business applications.
 +
*Left navigation of a business application entity page can be configured to show the relevant links.
 +
*Results for global search are categorized by the business application name if they are not Agreements or Associations.
 +
*When creating a Contract Type, seeded attributes only relevant to the Business Application Type and Category can be seededwill be selected.
 +
 +
Feature ID: 1183274&nbsp;
 +
 +
=== Self-Service ===
 +
 +
'''Introduction of a Technical Admin user to access the System Configuration on Self Service Portal'''
 +
 +
With the risk of inaccuracies in technical configurations, given their critical importance, such configurations have been, till now, hosted outside the confines of ICI, where ICI admin users, who have azure subscriptions to an instance, authored the process.
 +
 +
Therefore, the capability of admin users within ICI were being limited and the scope of technical configurations had to be expanded.
 +
 +
Now, a solution has been devised with this feature, as enunciated in the following:
 +
 +
*Technical Administrators can now be configured/added for performing required technical configurations in the System Configuration Portal, using the new “Technical Roles” field while adding, provisioning or editing a user.
 +
 +
'''Note:''' The user has to be Internal in order to be authorized with “Technical Roles”, and selecting an external user will automatically discount the Technical Roles feature.
 +
 +
*The portal has been upgraded for Technical Admin users, with enhancements to the Landing page, header, menu options, along with a static welcome message.
 +
*Appropriate messaging and communication will be provided for any negative scenarios, wherein the Technical Admin User faces any challenge accessing or configuring.
 +
*When a new ICI admin user logs in, they should be able to setup other internal users as technical admin users of the System Configuration portal.&nbsp;
 +
 +
'''Note:''' Only the ICI Admin user should be able to setup other internal provisioned users as the Technical Admin user.
 +
 +
*The ICI Admin can either create a new Security group, as required, or use an existing security group.&nbsp;
 +
*The authorization of technical admin users will depend on Security Groups Privilege to the “Self Service” privilege entity, and on roles assigned to specific users.
 +
*The “Self Service” privilege can be configured in the backend and it will be visible to users under the Security Group Privilege tab.
 +
*The “Manage” access option can be selected to grant access to the System Configuration Portal for technical admin users.
 +
 +
'''Note:''' The user who gets Technical Admin privileges can be any internal provisioned user on that instance (even a non admin user).
 +
 +
Feature ID: 1210894
 +
 +
'''Building the Config Key Update utility as part of the System Configuration on Self Service Portal'''
 +
 +
Today, in ICI – There are close to 800 configuration keys in the system. These keys are managed via the ICM Tools which is hosted outside of ICI. With this initiative, we have started the migration these Keys incrementally to be part of the System Configuration – Self Service Portal.&nbsp;
 +
 +
The scope for this release is to migrate 10 keys into the utility. The access to this utility is driven by the Technical Admin role as explained in the previous section.&nbsp;
 +
 +
Once the user successfully enters the ‘System Configuration – Self Service’ portal with the correct security groups and technical admin role, they will be able to see the ‘Config Key Updates’ entry point at the top of the screen
 +
<div class="image-green-border">[[File:RN 8.1 2.png|720px|RN 8.1 2.png]]</div>
 +
On clicking the Config Key Updates menu, the user will be able to see the utility where the defined 10 keys will be loaded on the screen, along with their existing values.
 +
<div class="image-green-border">[[File:RN 8.1 3.png|720px|RN 8.1 3.png]]</div>
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#800080;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>
+
The user will be able to view each key loaded into a card. The card will contain the name of the key along with it’s value.&nbsp;
  
−
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.
+
The user will be able to see a dedication section to the right of the page for viewing help information
  
−
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;
+
The user will be able to click on the ‘3-dot’ option on each card to edit the value of the key
 +
<div class="image-green-border">[[File:RN 8.1 4.png|720px|RN 8.1 4.png]]</div>
 +
&nbsp;
  
−
Users can now:&nbsp;
+
On clicking the Edit option, the key information will be loaded in the right drawer panel. Here the user can edit the key value and Save using the button at the bottom of the drawer
  
−
*Capture multiple valid internal or external email addresses while working on agreements/ requests.  
+
&nbsp;
−
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.  
+
<div class="image-green-border">[[File:RN 8.1 5.png|720px|RN 8.1 5.png]]</div>
 +
&nbsp;
 +
 
 +
The user can edit one or more keys using the ‘3-dot’ option on each card. Once the user has finished editing all the keys, they need to click on the ‘PUSH CHANGES TO ICI’ button at the top of the grid. This will internally update the keys with the edited values in ICI for the changes to take effect
  
 
&nbsp;
 
&nbsp;
 +
<div class="image-green-border">[[File:RN 8.1 6.png|720px|RN 8.1 6.png]]</div>
 +
Feature ID: 1180864
  
−
<span style="color:#800080;">'''583186 – Ability to add amendment on expired agreement'''</span>
+
=== Administration & Configuration&nbsp; ===
  
−
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.
+
'''Quick Configuration with ICI Import Solution'''
  
−
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&nbsp;
+
The ICI Import Solution is an automated solution for configuring ICI entities. It simplifies the initial configuration process and reduces the time and complexities involved in the process.
  
−
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.
+
Using the Import Solution tool, ICI users can now:
−
<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.
+
*Import configurations from a source ICI instance to a target ICI Instance with no pre-existing configuration data.
 +
*Import configurations between different versions of ICI.  
  
−
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;
+
'''Note:''' Support will be provided for up to 2 releases preceding the target ICI version.
  
−
Administrators can now:
+
*Register and publish preconfigured import solutions.
 +
*Import the following information:  
 +
*Contract Types
 +
*Templates
 +
*Clauses
 +
*Rules
 +
*Notifications
 +
*Masterdata Instances
 +
*Seeded Masterdata entity instances
 +
*Users & User Groups
 +
*Security Groups
  
−
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement.
+
Feature ID: 1262996&nbsp;
−
*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.
+
'''Contract Types can now be locked for editing&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.
+
Contract types can now be edited by only one user at a time. This functionality helps prevent data inconsistencies or concurrency errors.
  
−
With this release:
+
Product enhancements include:
  
−
*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).  
+
*A Lock/Unlock button on the contract type page.&nbsp;
−
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities.  
+
*Auto system lock when users start edit a contract type without locking it.&nbsp;
−
*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.  
+
*Messaging providing information on who is editing the contract type.&nbsp;
−
*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.
+
*System locks get released when contract types are saved.  
−
*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.
+
Feature ID: 1212463&nbsp;
−
<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;
+
'''Enhancements to Legacy Upload Tool'''
  
−
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&nbsp;
+
The following features will be added to the Legacy Upload utility with this release, improving speed and accuracy and reducing file size.
  
−
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;
+
*Records bypass workflow states directly to the desired state.&nbsp;
 +
*Users can schedule upload in batches within guardrails to improve system resource allocation.&nbsp;
 +
*Specific range of records from the UI can now be uploaded.
 +
*Infra and Elastic Search health check can be run before executing the scheduled batches.
 +
*On demand batch scheduling based on the user provided schedule.&nbsp;  
 +
*Supporting legacy entity created with large files 100MB+.
  
−
<span style="color:#800080;">'''545126 – Availability of business status value in ICI event messages'''</span>
+
Feature ID: 1069763
  
−
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.
+
'''Unique clause and template code for every environment'''
  
−
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.
+
Users can now customize their clause and template codes for different instances. If unique codes are used, it reduces errors when migrating data from one instance to another. It also simplifies searching of clauses and templates.
  
−
&nbsp;
+
Feature ID: 938126
  
−
== Mobile App Updates ==
+
'''Template and Clause creation options in Microsoft Word'''
  
−
<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.
+
The Create Template and Create Clause options in the Icertis Experience for Word are only displayed to users with access to these features. Earlier an error message was displayed to users without access and resulted in an unsatisfactory experience.
  
−
&nbsp;
+
Feature ID: 1187041
  
−
<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.
+
'''Show or Hide confirmation messages in Microsoft Word&nbsp;'''
  
−
&nbsp;
+
Administrators can now choose to show or hide certain confirmation messages, as per the organization's preference, on the Icertis Experience for Word.
  
−
<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.
+
Feature ID: 1187044
  
−
&nbsp;
+
=== Technology Updates ===
  
−
<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.
+
'''ServiceBus upgraded to Azure.Messaging.ServiceBus'''
  
−
&nbsp;
+
“Azure.Messaging.ServiceBus” is now replacing “Microsoft.ServiceBus”. &nbsp;<br/> <br/> This is a Microsoft recommended upgrade and provides the following improvements:
  
−
== ICI API Enhancements&nbsp; ==
+
*Up-to-date, streamlined Azure.
−
<div class="image-green-border">
+
*More accurate messaging without any anomaly or junk data in the message characters.  
−
<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;
+
<br/> Feature ID: 940871
  
−
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:
+
'''Authentication Library and Graph API update'''
  
−
*Contract Requests
+
Microsoft has announced* deprecation of the Azure Active Directory (Azure AD) Authentication Library (ADAL) and Azure AD Graph API libraries and recommends using Microsoft Authentication Library (MSAL) and Microsoft Graph API.
−
*Agreements
+
−
*Associations
+
−
*Amendments
+
  
−
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.
+
We have updated Microsoft Graph, Identity and Key Vault packages to include stability and security fixes from Microsoft. The migration from ADAL and Azure AD Graph API to MSAL and Microsoft Graph API will ensure continuing support for the following areas:
  
−
&nbsp;
+
*User Provisioning&nbsp;
 +
*Bulk Action&nbsp;
 +
*Integration - SFDC, GIF (Generic Integration Framework), MSCRM &nbsp;
 +
*Reporting&nbsp;
 +
*Key Vault&nbsp;  
  
−
<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>
+
Refer to the following link for Microsoft’s circular: [https://techcommunity.microsoft.com/t5/azure-active-directory-identity/update-your-applications-to-use-microsoft-authentication-library/ba-p/1257363 Update your applications to use Microsoft Authentication Library and Microsoft Graph API - Microsoft Tech Community].
  
−
ICI already supports downloading agreements.
+
Feature ID: 1276938
  
−
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.
+
=== API Enhancements ===
  
−
&nbsp;
+
In this release we focused on providing API 2.0 versions of most of our APIs with a goal to improve the performance and overall usability.
  
−
<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>
+
Following APIs are upgraded to API 2.0 versions in this release:
  
−
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.
+
[[File:RN 8.1 7.PNG|720px|RN 8.1 7.PNG]]
  
−
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.
+
[[File:RN 8.1 8.PNG|720px|RN 8.1 8.PNG]]
  
−
<br/>  <br/> <span style="color:#800080;">'''660859 – Supporting correlation Id in APIs'''</span>
+
[[File:RN 8.1 9.PNG|720px|RN 8.1 9.PNG]]
  
−
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;
+
[[File:RN 8.1 10.PNG|720px|RN 8.1 10.PNG]]
  
−
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;
+
[[File:RN 8.1 11.PNG|720px|RN 8.1 11.PNG]]<br/> [[File:RN 8.1 12.PNG|720px|RN 8.1 12.PNG]]
  
−
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;
+
[[File:RN 8.1 13.PNG|720px|RN 8.1 13.PNG]]<br/> <br/> [[File:RN 8.1 14.PNG|720px|RN 8.1 14.PNG]]
  
−
The following API changes have been made to ensure that the existing implementation and code do not break:
+
[[File:RN 8.1 15.PNG|720px|RN 8.1 15.PNG]]
  
−
*Provided support for a Tracking Id header in every request for logging.&nbsp;
+
[[File:RN 8.1 16.PNG|720px|RN 8.1 16.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.
+
[[File:RN 8.1 17.PNG|720px|RN 8.1 17.PNG]]
  
−
This can be used for:
+
[[File:RN 8.1 18.PNG|720px|RN 8.1 18.PNG]]
  
−
*Related API Calls
+
[[File:RN 8.1 19.PNG|720px|RN 8.1 19.PNG]]
−
*Async operations
+
−
*Bulk operations
+
−
*Status check operations &nbsp; &nbsp;
+
−
</div>
+
−
&nbsp;
+
  
−
== Enhancements to ICI Add-ins&nbsp; ==
+
[[File:RN 8.1 20.PNG|720px|RN 8.1 20.PNG]]
  
−
<span style="color:#800080;">'''745266 – Supporting online editing of agreements'''</span>
+
[[File:RN 8.1 21.PNG|720px|RN 8.1 21.PNG]]
  
−
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;
+
[[File:RN 8.1 22.PNG|720px|RN 8.1 22.PNG]]
  
−
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.
+
[[File:RN 8.1 23.PNG|720px|RN 8.1 23.PNG]]
  
−
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.
+
[[File:RN 8.1 24.PNG|720px|RN 8.1 24.PNG]]
  
−
It is now possible for:
+
[[File:RN 8.1 25.PNG|720px|RN 8.1 25.PNG]]
  
−
*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;
+
[[File:RN 8.1 26.PNG|720px|RN 8.1 26.PNG]]
−
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information.  
+
  
−
'''Note:&nbsp;'''
+
[[File:RN 8.1 27.PNG|720px|RN 8.1 27.PNG]]
  
−
*The online Word editor is available only for users with valid Office 365 subscription.  
+
[[File:RN 8.1 28.PNG|720px|RN 8.1 28.PNG]]
−
*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>
+
'''API Deprecations'''
  
−
ICI allows users to capture additional details for clauses in the extended attributes.&nbsp;
+
Any integrations utilizing the deprecated APIs must adopt alternate APIs. Previously, API endpoints have been periodically deprecated and alternate APIs have been provisioned.
  
−
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.
+
However, no existing API endpoints have been deprecated in the 8.1 Release. To check previously deprecated endpoints, refer to 7.16 Release Notes. More details on the alternate APIs are available in the Swagger documentation.
  
−
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.
+
=== Mobile App Update&nbsp; ===
  
−
&nbsp;
+
'''Improved Security on Mobile Devices with SafetyNet Attestation API'''
  
−
<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>
+
With this release, ICI is implementing SafetyNet Attestation API for Android mobile application to restrict users from accessing the application through rooted/vulnerable device, to avoid breaching of the IT and cyber security policy.
  
−
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.
+
'''Note: '''The SafetyNet Attestation API is supported Android version 8.0 onwards.
  
−
Users can now:
+
Feature ID: 1095223
  
−
*Search and filter clauses and templates based on the name or text inside the clause or template respectively.
+
== AI Applications&nbsp; ==
−
*Perform free text search on clauses and templates.
+
  
−
&nbsp;
+
Usually, the implementation team spends a lot of time analyzing and training the AI model for the discovery of the new attributes. With this release, ICI is extending the number of pre-trained attributes so that the AI apps implementation project can be expedited. ICI previously had added 23 out-of-the-box attributes and introducing 15 additional attributes in this release, making it a total of 38 new attributes as a part pre-trained model. Customers can now start using attributes from pre-trained model with no or very little retraining.
  
−
<span style="color:#800080;">'''603690 – Updating templates automatically with latest clause version'''</span>
+
The additional attributes are:
  
−
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.
+
*Acceptance Completion Period
 +
*Breach Cure Period
 +
*Confidentiality Survival Period
 +
*Force Majeure Period
 +
*Interest Percentage on Payment Delay
 +
*Liquidated Damages Cap
 +
*Policy changes notice period
 +
*Records Retention Period
 +
*Renewal notice period
 +
*Signatory Name
 +
*Signatory Title
 +
*Signature Date
 +
*Termination for cause notice period
 +
*Termination for convenience notice period
 +
*Warranty Claim Period
  
−
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;
+
Feature ID: 1187824
  
−
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.
+
=== Enhancing the scope of DiscoverAI app& Negotiate AI differentiation ===
  
−
<br/>  <br/> <span style="color:#800080;">'''593421 – Labeling agreement document versions as per signature copy'''</span>
+
Discover AI helps users to identify attributes and clauses in browser and save them in the system.
  
−
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.
+
With this release, scope of DiscoverAI has been enhanced to include the discovery of attributes and clauses within Microsoft word also using Icertis Experience for Word plugin.&nbsp;
  
−
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.
+
*The following actions/functionalities will be available under the Discover AI license in Icertis experience for Word:&nbsp;
 +
*Discovery of attributes and clauses.&nbsp;
 +
*Confirm, Confirm with Deviation, Ignore, Compare and Replace the clauses based on discovered clauses data.&nbsp;
 +
*Select the Matched Clause from the library.&nbsp;
  
−
&nbsp;
+
Feature ID: 1284012
  
−
== Enhancements to Artificial Intelligence Applications in ICI ==
+
== Reports Enhancements ==
  
−
<span style="color:#800080;">'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''</span>
+
=== Data for agreements awaiting signature in reports ===
  
−
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;
+
Out-of-the-box ICI reports will now display details for the business status “Waiting for Signature”, in addition to existing statuses. This update to the reporting logic resolves an existing gap in the reports data.
  
−
With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&nbsp;
+
This enhancement applies to the following reports:
  
−
Users can now:&nbsp;
+
[[File:RN 8.1 29.PNG|520px|RN 8.1 29.PNG]]
  
−
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &nbsp;
+
Feature ID: 1071182
−
*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;
+
=== Custom reporting views using JSON&nbsp; ===
  
−
<span style="color:#800080;">'''575475 – Automating user feedback for clauses, obligations and attributes'''</span>
+
Developers can now create new custom reports views using Stored Procedures (SP) and JSON files. This feature gives flexibility to organizations to easily develop new reports relevant to their business requirements.
  
−
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;
+
An Import SP is now available that takes JSON files as input. The JSON file used for input is where developers can define the new view. New reporting views are automatically created on running the Import SP.
  
−
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.
+
An Export SP is also provided, which can be used to download&nbsp;a JSON file which contains the structure of an existing view in the database, to use as a template to create a new views.
  
−
<br/> <span style="color:#800080;">'''539492 – Improving clause delineation in DiscoverAI'''</span>
+
Feature ID: 1208472
  
−
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;
+
=== Dataset and seeded dashboard for Proposal Management application ===
  
−
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&nbsp;
+
A dedicated Power BI Dataset is now available for the Proposal Management application for out-of-the-box and custom reporting.&nbsp;&nbsp;
  
−
Users can now:&nbsp;
+
PM App Power BI report will have clickable links to ICI entity details page for Proposal Management Entities such as, Sell Side RFx, RFx Qualification, and Bid Proposal.
  
−
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&nbsp;
+
Feature ID: 1232650
−
*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;
+
=== Attribute Information Report Enhancements ===
  
−
<span style="color:#800080;">'''770375 – Merging metadata discovery page with attribute page'''</span>
+
The following filters and columns are added to the Attribute Information report giving more options to analyse the Attributes used in the system.
  
−
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;
+
*Filters: Contract Type, and Group by Property Columns: Is Mandatory and Tracking Attribute
  
−
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;
+
Feature ID: 1158976
  
−
Users can:&nbsp;
+
=== Edit SSRS Reports without customization ===
  
−
*View the discovery completion progress.&nbsp;
+
Icertis and partner developers can now edit the SQL Server Reporting Services (SSRS) reports eliminating the need to create additional customized reports even for small changes. Users can now make the following edits to SSRS reports:
−
*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.
+
*Add or remove columns in an existing report.
 +
*Modify column’s position, name, or default values.
 +
*Modify sorting order of the results.
 +
*Apply query level filters.
 +
*Apply security group access as standard reports.
 +
*Create copy of existing report and modify it.
 +
*Use a new framework, which has a JSON-based interface.
 +
*Create new or modify custom reports.  
  
−
&nbsp;
+
Feature ID: 744814
  
−
<span style="color:#800080;">'''727312 – Formatting based clause delineation for additional document types'''</span>
+
=== Report-based edit access for Power BI reports ===
  
−
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.
+
Manage access for Power BI reports can now be provided at a report level to ensure that edit access is only given to the necessary users within the organization.<br/> This feature works does not impact “Advanced Analytics” access.<br/> <br/> Feature ID: 1070905
  
−
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.
+
=== Maintainance and storage optimization with a Common Data Model for Clause-based reports ===
  
−
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.
+
PlatformClause - a common data model for clause related information can now be used to create clause-based reports such as Clause Profiling Report, Clause Pending Approval Report and more. This helps optimize storage capacity and reduces the development and maintenance effort siginificantly.&nbsp;<br/> <br/> Feature ID: 1083685
  
−
&nbsp;
+
=== SSRS Reports now available with Power BI ===
  
−
<span style="color:#800080;">'''727314 – Supporting additional languages in AI apps'''</span>
+
Power BI reports are faster, more scalable, richer in features, customization-friendly, sport a modern UI and overall a better experience. To leverage its advantages, the following SSRS reports are now made available in Power BI:
  
−
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.
+
*Clause Summary Report
 +
*Tagged Attribute Report
 +
*Agreement Clause Content Report – A widget that displays the clauses with the most deviations is also added in this release.&nbsp;
  
−
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.
+
Feature IDs: 1214787, 1214720, 1223598<br/> &nbsp;
  
−
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.
+
== Salesforce Integration&nbsp; ==
  
−
&nbsp;
+
=== &nbsp;Activity Object and Trigger Simplification in Salesforce Adapter ===
  
−
<span style="color:#800080;">'''710739 – Configuring custom rules in DiscoverAI'''</span>
+
The following enhancements are made to the SFDC Manage package Adapter:
  
−
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;
+
*Triggers for Accounts and Opportunity objects have been removed from the Managed package to avoid unnecessary update-related issues. Users can get more flexibility and control over them when they use the auto contract creation feature. Note: This is applicable to both fresh installs as well as updates on existing packages.
 +
*Previously, 6 custom fields were needed on the Salesforce activity object to sync ICI tasks with Salesforce, and now, the dependency on these fields have been reduced with only 2 custom fields required for the sync.
 +
*For customers who didn’t need the ICI task sync feature and were unable to remove the custom fields with the limit of 100 fields on the Activity object, now, these fields have been removed from our managed package to provide more flexibility.  
  
−
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;
+
'''Note:''' Guideline documentation and support by ICI implementation/upgrade team will be duly provided, for creation of desired fields during new installs as well as release upgrades, or deletion of fields during upgrade scenarios.
  
−
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;
+
Feature ID: 1066353
  
−
== Enhancements to Reports ==
+
=== User Experience for Salesforce Revamped ===
  
−
<span style="color:#800080;">'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''</span>
+
Using ICI within Salesforce is now a more seamless experience as we have made significant improvements to preserve the native Salesforce UI interactions, which users are familiar with, without compromising the ICI functionality.
  
−
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.
+
These are the enhancements that have been introduced:
  
−
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.
+
*&nbsp;Native Salesforce components are now used along with the ICI iframe.
 +
*Sub-tabs moved from ICI to Salesforce native tabs, for example: Agreements, Requests and Agreement Reports.  
 +
*Agreement and Request Details pages are now displayed in native Salesforce UI.
 +
*On the Details page certain actions (example - Reset Expiry) and sub-tabs (example – Associations) are now native Salesforce components.  
  
−
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;
+
'''Note:''' The implementation team will provide a list of native and i-frame components.
  
−
'''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.
+
Feature ID: 1186642
  
−
&nbsp;
+
== eSign Integration&nbsp; ==
  
−
<span style="color:#800080;">'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''</span>
+
=== Integration Support for DocuSign using JWT authentication ===
  
−
Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&nbsp;
+
The ICI and DocuSign integration was previously based on authenticating the APIs with “IntegratorKey” and “API Password”.
  
−
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.
+
The product has now been upgraded to support an enhanced authentication using JSON Web Token (JWT), along with the existing basic authentication support. This enhancement has also enabled JWT support for “Multisign” as well as “Single Esign” configurations.
  
−
<br/>  <br/> <span style="color:#800080;">'''514611 – Enhancing Notifications History Report for an entity'''</span>
+
Feature ID: 1000798
  
−
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;
+
=== DocuSign API upgraded from 2.0 to 2.1 ===
  
−
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;
+
DocuSign released an update announcement that OAuth 2.0 would be required to support DocuSign API applications. In keeping with this announcement we have upgraded DocuSign REST APIs from 2.0 to 2.1. With this upgrade, a new JSON parser has been introduced to support DocuSign Connect, a notification mechanism to receive updates when any event is triggered in the eSignature workflow.
  
−
The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&nbsp;
+
Feature ID: 1060689
  
−
*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;
+
=== Adapting webhook feature of Adobe Sign ===
−
*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;
+
Adobe Sign adapter couldn’t communicate precise callback information to ICI Platform, thus causing intermittent errors in ICM workflow after the Agreements were electronically signed. Adobe Sign responded with the same information for every signature, hence it wasn’t possible to distinguish between callbacks from different signature. However, with the introduction of Adobe webhook, this problem can be resolved.
  
−
<span style="color:#800080;">'''742607 – Supporting localization for status and business status'''</span>
+
Adobe webhooks can be created on the workflow for each agreement, requesting the type of information in the callback, which further benefits as follows:
  
−
With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&nbsp;
+
*Identifying the signatory requesting a callback
 +
*Identifying for which event or action the callback is requested
 +
*Concisely updating the status in ICM
  
−
*Obligation Management Health Report, Obligation Management Dashboard Report.&nbsp;  
+
'''Note:'''&nbsp; Upgrade Adobe Sign API from 5.0 to 6.0 to use the webhook feature.
−
*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;
+
Also, Adobe rebranded Echo sign to Adobe Sign, hence non overridden localization strings for validation messages have been modified accordingly.
  
−
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.
+
Feature ID: 1091947
  
−
&nbsp;
+
=== Electronic Signature support using ICI BioPharma setting for 21 CFR Part 11 & Annex 11 compliant groups ===
  
−
<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>
+
ICI Platform now supports the Life Science industry documents that need to comply with 21 CFR Part 11 (for US FDA) or Annex 11 (for EU) regulatory compliance.
  
−
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;
+
This feature allows integration with DocuSign Part 11 module and Adobe Sign Bio-Pharma setting to get electronically signed approvals for such agreements.
  
−
With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.
+
Feature ID: 1220095
  
−
&nbsp;
+
=== Changes in IP whitelisting process for eSign adapters ===
  
−
<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>
+
ICI Platform supports integration with third party eSign adapters, which communicate using callback information. To receive the callback data from the eSign servers, certain IPs to intended methods are whitelisted. This action is done through the web.config file. However, any change in the IPs requires modifying the web.config file, which resets the IIS, resulting in performance issues.
  
−
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;
+
To address this issue, “Core.IPSecurity” key has been introduced, which stores information related to the IPs as a JSON, and thus eliminates the need to modify the web.config file.
  
−
== Integrations ==
+
'''Note''': Blocking or allowing IP addresses based on DNS is not supported as a part of this feature.
  
−
<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
+
Feature ID: 1193062
  
−
ICI has now improved the electronic signature process to provide a unified flexible signature workflow.
+
=== Update eSign document with correct status ===
  
−
With this release, the following capabilities have been added to the ICI signature process:
+
In certain scenarios, the electronic signature status in ICI and eSign provider are inconsistent. An enhancement has been added wherein the respective statuses are verified and the agreement status is updated or corrected accordingly.
  
−
*Introducing the hybrid signature process.
+
Feature ID: 1193061
−
*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.
+
  
−
&nbsp;
+
== Sourcing&nbsp; ==
  
−
<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>
+
The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (SRC8.1.0.404).
  
−
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.
+
=== Support for new RFx type-RFP ===
  
−
With this release:
+
Icertis Sourcing application now supports Requests for Proposals (RFPs). Organizations can leverage the advantages of a secure and seamless application to organize and maintain their procurement processes digitally using the RFP feature.
  
−
*Users can define the parallel signatories using rules.  
+
RfPs are integrated requests containing information on both questions and bids. Buyers can now design, create, and publish RFPs in the Sourcing application and invite suppliers to respond to them. Once Buyers receive the responses, they can evaluate them and make their procurement decisions.
−
*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>
+
Key RFP features:
  
−
Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&nbsp;
+
*Integrated mechanism to get responses to questions and bids from suppliers.  
 +
*Reusable templates for Questions, Questionnaires, and Bidding templates.
 +
*Questionnaires and questions can be arranged and reordered as required.&nbsp;  
 +
*Attachments, and responses to questions can be downloaded in a package.
 +
*A consolidated excel spreadsheet is available to analyse bids and responses.
 +
*Suppliers can provide responses to questions using Excel as well as Sourcing UI.
  
−
With this release, users can:
+
Feature ID: 404602
  
−
*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.
+
=== Improved Sourcing workflow with Sourcing Request ===
−
*Define standard rules and conditions to automatically select the provider for agreements and amendments.
+
  
−
'''Note: '''This is applicable to DocuSign and Adobe Sign.
+
Users within an organization can now create Sourcing Requests for procuring items or services. These requests can be designed to go through an approval flow before they are turned over to procurement teams. The approval cycle can be easily tracked and audited for compliance.
  
−
&nbsp;
+
Sourcing Request features:
  
−
<span style="color:#800080;">'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''</span>
+
*Configure a Sourcing Request based on the necessary privileges.
 +
*Request forms can be designed to capture necessary details and attachments.
 +
*Requests can be sent to designated approvers for approval.
 +
*An RFx can be created after the request is approved.
 +
*Requests can be modified until they are approved or a RFX is created based on it.
 +
*Cancel or recall the Sourcing Request.
 +
*Put the Sourcing Request on Hold till approved state provided RFx is not created using this Sourcing Request.
  
−
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.
+
Feature ID: 611297
  
−
With this release:
+
=== Ordering and additional data types for Questions in Questionnaire ===
  
−
*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”.
+
We have made the following enhancements to Icertis Sourcing to improve the user experience when working with Questions and Questionnaires:
−
*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.
+
−
*A message containing the opportunity Id and agreement SysId is updated, and the time stamp is also displayed.
+
  
−
<br/> <span style="color:#800080;">'''796155 – Improving data flow between Salesforce and ICI'''</span>
+
The order of Questions and questionnaires in RFx can be set and modified as per the preference of users.
  
−
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;
+
The following data types are now supported for questions in RFx:
  
−
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.
+
*Boolean
 +
*String
 +
*Choice
 +
*Multi Choice
 +
*Currency
 +
*DateTime
 +
*Number
 +
*Percentage
 +
*Text Area
 +
*Rich Text Area&nbsp;&nbsp;
 +
*Email
 +
*File Selection
  
−
With this release:
+
'''Note''':
  
−
*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;
+
*On exporting rich text data type information to Excel or HTML, some formatting features may be lost.  
−
*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;
+
*Uploading a file attachment as response for file type question response using Excel is not supported. Supplier must log on to ICI to upload files.  
  
−
This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.
+
Feature ID: 896873
  
−
&nbsp;
+
== Obligation Management&nbsp; ==
  
−
<span style="color:#800080;">'''674469 – Sending success or failures alerts for monitoring in Salesforce'''</span>
+
The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application (OM8.1.0.404).
  
−
An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&nbsp;
+
=== An interface to quickly add obligations discovered by AI ===
  
−
With this release:
+
Obligations that are identified in contracts using the Discover AI feature can now be easily reviewed on the user interface. User can review the obligations and decide to add one or more to the Obligation Management application for tracking approvals and fulfillment.
  
−
*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&nbsp;
+
The interface to review and create obligations in bulk saves users much time and manual effort.
−
*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>
+
The following image shows an example of creating Obligations in bulk:
 +
<div class="image-green-border">[[File:RN 8.1 30.png|720px|RN 8.1 30.png]]</div>  
 +
Notifications for successfully processed or failed obligations can also be configured.
  
−
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;
+
Feature ID: 1090383
  
−
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.
+
=== Auto-approval of Obligations to improve efficiency ===
  
−
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;
+
Many obligations are extracted from executed contracts and they don’t usually need to go through an approval process in the Obligation Management application. To reduce time and effort spent approving a large number of obligations and not block the obligation fulfillment lifecycle on account of pending approvals, an automatic approval process for obligations can now be configured.
  
−
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.
+
Once the auto-approval process is defined based on obligation taxonomy, this is how the feature works:
  
−
&nbsp;
+
*If approval is turned off, and no approvers are added to obligations, the obligations are automatically approved.
 +
*If approvers are added to obligations, manually or automatically through a rule, then even if approvals are turned off, the obligations will need to be approved.
  
−
<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
+
Feature ID: 519344
  
−
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;
+
=== Organize and manage obligations by creating groups&nbsp; ===
  
−
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;
+
An obligations could have one or more sub obligations or tasks, which would need to be completed by different individuals in an organization. Also, some obligations may be related to each other and grouping them could help organize and track the fulfillment. To facilitate such scenarios, obligation groups can now be created in the Obligation Management application.
  
−
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.
+
Users can now categorize different obligations under logical groups and create parent-child relationships between obligations.
  
−
&nbsp;
+
Child obligations automatically inherit any changes made to the parent Obligation. For example, if the status of parent Obligation is changed to Approved, all the related child Obligations also get approved.
  
−
== ICI Platform Tools ==
+
Feature ID: 649768
  
−
'''<span style="color:#800080;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''
+
=== Duplicate obligations no longer inherited&nbsp; ===
  
−
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:
+
When an Agreement (parent), with an associated Obligation, is inherited by another Agreement (peer), a duplicate Obligation is created. An enhancement in this release eliminates this limitation.
  
−
*Organizations (Orgs), Organization Groups (Org Groups)
+
Feature ID: 1040723
−
*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.
+
=== UI Improvements for Obligation Management ===
  
 +
The following improvements are made in the product to improve the search and usability experience when using Obligation Management:
 +
 +
*Dedicated index pages for Obligations and Fulfillments,
 +
*Relevant page titles, breadcrumbs and history page information.
 +
 +
Feature ID: 1236413
 +
 +
== Risk Management ==
 +
 +
The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (RM8.1.0.404).
 +
 +
=== UI Improvements for Risk Management&nbsp; ===
 +
 +
The following Improvements are made in the product to improve the search and usability experience when using Risk Management:&nbsp;
 +
 +
*Dedicated index pages for Risk Management and Risk Assessment.&nbsp;
 +
*Relevant page titles, breadcrumbs and history page information.&nbsp;
 +
*Saved searches display Risk Assessment as category. &nbsp;
 +
*The “Create” action button has now been added on the “Risk Assessment” index page.&nbsp; &nbsp;
 +
<div class="image-green-border">[[File:RN 8.1 31.png|720px|RN 8.1 31.png]]</div>
 +
Other enhancements include:
 +
 +
*The “Delete” action has now been moved under the three dots icon on the Risk Assessment “Details” page. On deleting the risk assessment, users will be redirected to the Risk Assessment “Index” page.
 +
 +
Feature ID: 1067718
 +
 +
== Proposal Management&nbsp; ==
 +
 +
ICI Proposal Management application is certified to work with the 8.1 release (PM8.1.0.404).&nbsp;
 +
 +
=== Track and analyse performance with a Power BI Dashboard ===
 +
 +
A seeded dashboard that helps supplier organizations track their proposals by status, time, and outcome is now available within the Proposal Management application.The following features and reports are now available with the Proposal Management application:
 +
 +
*A new Power BI data model with Power BI dataset specific to Proposal Management.
 +
*Proposal Management KPIs report
 +
*Capture Management report
 +
 +
'''Note''': Users with access to Sell Side RFx or Bid Proposal can view the Dashboard.
 +
<div class="image-green-border">[[File:RN 8.1 31.png|720px|RN 8.1 31.png]]</div>
 
&nbsp;
 
&nbsp;
  
 +
=== Enhancements to Seeded Contract Types ===
  
−
== Partner Enablement ==
+
With this release, the PM App is being enhanced with newly seeded attributes to its seeded contract types.
  
−
<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
+
In this enhancement:
  
−
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;
+
*New attributes have been seeded with the Bid Proposal entity:
 +
*Total Bid Value For Proposal
 +
*Total Value Won Or Lost
 +
*Customer Address
 +
*Customer Geography
  
−
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:
+
These new attributes contribute in the essential computations of the Win Ratio and the Value Capture Ratio.
  
−
*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.
+
Feature ID: 1186830
  
−
*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.
+
=== Revamped User Experience across the PM App ===
  
−
*Working with ICI Tasks: Updated for the 7.15 release.  
+
The visual look and feel of the Proposal Management App has been considerably enhanced with the ICI-wide implementation of the new UI (User Interface) and UX (User Experience).
  
−
*Working with ICI Hooks:'''&nbsp;'''Updated for the 7.15 release.
+
The following summarizes the revamped user experience across the App:
  
−
*ICI Developer Library: Updated for the 7.15 release.  
+
*The new “Proposals” tile menu now features only the viewing tile options for the seeded PM App entities, in addition to a new “Dashboard” tile menu option.  
 +
*The create navigation flow has been moved from the “Proposals” tile and a dedicated “Create” button has now been added to each seeded entity index page.
 +
*The seeded entities now have their dedicated index pages, as opposed to the saved search driven listing in previous releases.
 +
*The Details pages of all the seeded entities (Sell Side RFx, Bid Proposal etc.) now have dedicated page titles starting with the entity name, instead of the contract type category. For example, the previous “Agreement / Sell Side RFx 123” has been replaced by “Sell Side RFx / Sell Side RFx 123”.
 +
*The newly added entity name (such as “Sell Side RFx”) on the Details page header is now a clickable link, clicking which opens the entity index page.
 +
*In the audit history of any entity, both Grid View and List View, the header now features the entity category name instead of the contract type, just like the change in entity Details page.
 +
*The display of action buttons on entity Details pages can now be configured to customize their sequence of display, and based on the available window space the remaining action buttons will be available under the three dots icon on the entity “Details” page.  
  
−
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release.
+
Feature ID: 1235186
  
−
*Self-Serve Tools:'''&nbsp;'''Updated for the 7.15 release.  
+
== Supplier Relationship Management Application&nbsp; ==
 +
 
 +
ICI Proposal Management application is certified to work with the 8.1 release (SRM8.1.0.404).
 +
 
 +
=== Supplier Evaluation ===
 +
 
 +
The Supplier Evaluation module introduced in the Supplier Relationship Management suite helps organizations manage supplier performance and evaluate and mitigate risks associated with working with suppliers.
 +
 
 +
'''How Supplier Evaluation fits within Supplier Relationship Management'''
 +
<div class="image-green-border">[[File:RN 8.1 33.png|520px|RN 8.1 33.png]]</div>
 +
The Supplier Evaluation module introduced in the Supplier Relationship Management suite helps organizations manage supplier performance and evaluate and mitigate risks associated with working with suppliers.
 +
 
 +
'''How Supplier Evaluation fits within Supplier Relationship Management'''
  
 
&nbsp;
 
&nbsp;
  
−
== Technical Requirements for Release 7.15 ==
+
Supplier Evaluation module is part of the Supplier Relationship Management application, which is built on Icertis Contract Intelligence.
  
−
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.
+
Once suppliers are onboarded, users can evaluate suppliers on the products or services they offer. The KPI criteria, schedule, and the evaluators can be set up within the module and on completing the assessment the supplier can be classified as high performing, low performing or standard supplier.
  
−
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]
+
A routine supplier evaluation can help organizations set expectations from their preferred suppliers and manage low performing suppliers.&nbsp;&nbsp;
  
−
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]
+
'''Supplier Evaluation Features'''
  
−
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]
+
Setting up Supplier Evaluation
  
−
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]
+
*'''KPIs''' – Users can create one or more KPIs (evaluation criteria) and evaluate suppliers based on the set parameters. For example, you can create KPIs for auditing, performance reviews, training requirements, and more.  
 +
*'''Supplier Data''' – The supplier evaluation creation process is simplified as much of the supplier information is auto-populated based on the supplier’s record.  
 +
*'''Evaluation Schedule''' – Users can set up a period for which the supplier will be evaluated.
 +
*'''Product/Service for Evaluation''' – The evaluation can be performed in context of the product or service provided or the agreements.
 +
*'''Reviewing suppliers based on the Criteria''' – The evaluation criteria can be put through an internal review process, and inputs can be sought to finalize the evaluation criteria.
 +
*'''Supplier Outreach''' – Suppliers can provide information and supporting documents needed to perform the evaluation by responding to review requests by buyers.
 +
*'''Responses & Scoring''' – Based on the responses provided by business team or evaluators on the supplier evaluation, scores are automatically computed.
 +
*'''Evaluation Approvals & Control''' – Once the evaluation process is over, then buyer team defines supplier performance classification and suggests the next course of action (in case of low performing supplier). This can also be sent for management approval. The approver team can either approve or reject and send it for rework..
 +
*'''Notifications''' – Notifications can also be configured for periodic evaluation. System notifications are sent to buyers when they are requested to evaluate a supplier.  
  
−
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]
+
Feature ID: 463049
 +
 
 +
=== Managing Supplier Hierarchy ===
 +
 
 +
'''Manage Related Supplier Organizations'''
 +
 
 +
The Supplier Relationship Management application now provides a mechanism to connect supplier organizations with their Parent, Holding or Subsidiary organizations. This is to ensure that you have a complete overview of the business you do with one supplier and its related entities. According to business needs, you may want to work with a local supplier or the parent global organization.
 +
 
 +
You can designate a supplier organization as one of the following types:
 +
 
 +
*'''Supplier''': Supplier organizations that may or may not have related Parent or Holding companies.
 +
*'''Parent company''': Parent company of one or more Supplier organizations, controls operations of the Supplier Organization
 +
*'''Holding company''': Holding company of one or more subsidiary Supplier organizations, does not have a direct say over the operations of subsidiaries.
 +
 
 +
Changes made to the supplier hierarchy for supplier registration, qualification or profile are synchronized with the vendor database and supplier master.
 +
 
 +
'''Unique Supplier Record Management'''
 +
 
 +
In Icertis Supplier Relationship management, the uniqueness of a supplier record is validated based on a combination of attributes . In this release, one or more of the unique identifiers attributes can be made editable. This is to account for entities that may change the Legal Entity Name in the course of doing business, considering legal entity name is one of the unique identifier attributes.
 +
 
 +
If the attributes are changed for an organization, the system validates and checks for duplicate records before allowing users to make the change.
 +
 
 +
'''Validating the Duplicate Registrations'''
 +
 
 +
Buyers may receive more than one registration from the same supplier submitted through the web page.
 +
 
 +
This release introduces the capability to match the supplier registration records based on the unique identifier attributes. This helps identifying the duplicate registrations. Buyers can perform limited actions on the duplicate registrations and the supplier qualification is not generated.
 +
 
 +
'''Note''': Customers upgrading to 8.1 from previous versions of ICI Supplier Relationship Management is supported.
 +
 
 +
Feature ID: 1271423
 +
 
 +
== Technical Requirements&nbsp; ==
 +
 
 +
The Icertis Contract Intelligence (ICI) application can be accessed from any device with an Internet connection and a supported browser. All features may not be available in all environments.
 +
 
 +
The software and hardware requirements for the client system as well as the mobile application are listed in the table below:
 +
 
 +
[[File:RN 8.1 43.PNG|720px|RN 8.1 43.PNG]]
 +
 
 +
[[File:RN 8.1 44.PNG|720px|RN 8.1 44.PNG]]
 +
 
 +
[[File:RN 8.1 45.PNG|720px|RN 8.1 45.PNG]]
 +
 
 +
'''Important Changes in IE11 Support:'''
 +
 
 +
From March 2021, Microsoft has stopped its technical support to Internet Explorer (IE) and has advised its customers to move to Microsoft Edge.
 +
 
 +
ICI will no longer support IE11. ICI will not be certified over IE11.
 +
 
 +
If customers use IE 11 then the below message will be displayed:
 +
 
 +
“You are using a browser that is not recommended to be used since it no longer supported by its OEM. The ICI support for this browser is limited for 7.16 version and will be discontinued from version 7.17 onwards. You should switch to Microsoft Edge as recommended by the OEM or any other supported browser prescribed by your organizational policy. You may contact your administrator for further information.”
 +
 
 +
[[File:RN 8.1 46.PNG|720px|RN 8.1 46.PNG]]&nbsp;
 +
 
 +
[[File:RN 8.1 47.PNG|720px|RN 8.1 47.PNG]]
 +
 
 +
[[File:RN 8.1 48.PNG|720px|RN 8.1 48.PNG]]<br/> [[File:RN 8.1 49.PNG|720px|RN 8.1 49.PNG]]<br/> [[File:RN 8.1 50.PNG|720px|RN 8.1 50.PNG]]
 +
 
 +
[[File:RN 8.1 51.PNG|720px|RN 8.1 51.PNG]]
 +
 
 +
== 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.
 +
 
 +
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:
 +
 
 +
[[File:RN 8.1 52.PNG|720px|RN 8.1 52.PNG]]
 +
 
 +
&nbsp;
  
 
&nbsp;
 
&nbsp;
Line 694: Line 840:
 
&nbsp;
 
&nbsp;
  
−
'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|
+
&nbsp;'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Associations|Association Management]] | [[Compliances|Compliance Management]] | [[Templates|Template Management]] | [[Clauses|Clause Management]] | [[Configure|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]]&nbsp;

Latest revision as of 08:35, 25 June 2022

Contents

ICI Release Notes - Release 8.1

Release 8.1 New Features

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

•      Refer to the Technical Requirements for the release in this document.

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

The 8.1 Release introduces the following enhancements to the Icertis Contract Intelligence (ICI) platform:

Icertis Contract Intelligence 

Agreement & Platform 

A new collaboration experience with Microsoft Teams

ICI now leverages the powerful capabilities of Microsoft Teams to help internal teams collaborate on contract creation workflow and expediting the contracting lifecycle. The Teams integrations will help customers to use a single communication system and discussions can be held in context of the agreement.

The feature includes:

  • Contract owner can initiate a collaboration on MS teams from agreement details page and also invite agreement team members to participate in the discussion.
  • The latest version of the agreement document is also made available on the teams channel while initiating the collaboration. Participants can review, redline the agreement document in MS teams and publish the edited document back to ICI as a new version.
  • The documents associated with main agreement in ICI can also referenced in MS teams channel

Feature ID: 1188391

Negotiate and Update Agreements with the new Outlook Add-in

The new Outlook Add-in connects users’ emails with Icertis Contract Intelligence and provides improved collaboration capabilities and ensures information sent on emails is tracked for audit and governance on ICI. In addition, the new add-in provides a better interaction design, in line with the modern ACE user experience released in version 8.0.

The Add-in for Microsoft Outlook Desktop is supported on Windows and Mac OS. Once installed, an Icertis Experience for Outlook pane is accessible from Outlook. The pane provides access to ICI agreement data, along with success and error messaging for interactions. It can be pinned on the interface for easy access.

With the Outlook Add-in improvements, users can now do the following:

  • Add attached documents in emails as associations or a new agreement version in ICI.
  • Preview Agreement and Association documents from the Outlook Add-in.
  • Drag-and-drop single or multiple emails as associations.
  • Replace existing associated document with a new email or email attachment.
  • Access agreements and associated documents from the Outlook plugin and email them attachments to reviewers or approvers any stakeholders.
  • New incoming messages for email threads marked as associated documents are automatically added as new associated documents. 

Feature IDs: 1137119, 1137121

Quick & Easy Agreement Creation

Agreement Contract Types now come with a Quick Creation option. For all agreements using this option, users can fill all the necessary information on a single page and publish the contract or send it for approval immediately.

Feature ID: 1183356

More Quick Action Options

The Quick Actions widget “What would you like to do” has been enhanced to provide multiple actions/links with one quick action line item. For example, “Create MSA” quick action now provides multiple links catering to “Own” and “Third Party” paper selections, as displayed in the image below.

RN 8.1 1.png

Feature ID: 1183310

External Emails Split to Ensure Compliance 

Contracts sent for review or approval by email to other parties, legal consultants and users not within ICI are now split in two parts. A URL and passcode can be shared with the users and the review can be done completely online. No need of downloading and attaching documents and tracking versions offline. The process is quick, secure and easy to audit.
Two emails are sent, One email is sent containing the agreement URL and the other with the passcode to access the URL. This method could be used for requesting reviews, reviews and approval.

Users can also resend the notification to external users whose reviews are pending, with the help of the “Resend Passcode Notification” button.

To enable this feature, the implementation team needs to configure it explicitly. 

Feature ID: 1216716 

Deviation management for text and tables outside content control

If changes are made to the plain text in agreements or tables in associations of an agreement document (text which is not a clause or attribute), a deviation can now be triggered to help Legal teams exercise greater content control. The changes are highlighted and the deviations will flow through an approval process.

Feature ID: 1183384 

Support for Microsoft Powerpoint documents

ICI now supports Microsoft Powerpoint file formats (files with .ppt and .pptx extension) as third-party paper agreement file formats. In addition to PDF and DOCX file formats, users can now create and negotiate contracts using PPT and PPTX files.

Feature ID: 1183367

Online Editing Of Own Paper

In this release, ICI is enhancing its existing online editing feature  by supporting online editing of own paper documents. using Microsoft WOPI.We have improved the experience for editing agreements with Microsoft Online applications In this release.

The following improvements can be observed:

  • Documents with editable content control can be edited and and values are is synced seamlessly.
  • The track changes option will now track all the changes made by the users in reviewing mode, creating a redlined version of the document.
  • The empty content control will be displayed as blank instead of “obj”.
  • The content controls within tables can now be edited with associations tagged as tables and saved searches.Content controls within tables will now be editable. 

Feature ID: 1287270 

Support for Inheritance of Bulk Associations 

In addition to attributes and associations, now bulk associations contract types (BACT) and their extension attributes can now be inherited from parent to child agreements. 

The agreements with BACT associations will get inherited asynchronously along with all extension attributes of all the associations. The bulk associations will also work as they do in parent agreements.

Feature ID: 1278205 

Enhancement to Download all Agreement & Associated Documents in one click  

With this release, we have expanded on the Download all capability which allowed users can to download the agreement and itsall associated documents in one click saving much time and effort. 

This functionality was earlier available when the signature type for the agreement was set to manual, it is now available for electronic and hybrid signature types as well.

Additionally, the “Download All” button will now be visible to users based on the role action mapping in superseded state as well. 

Feature ID: 980342 

Platform changes to enhance UX for Business Applications

To improve findability and relevance of information pertaining to a particular business application, some configuration changes are now available in the platform. These changes significantly improve the search and usability experience when working with Agreements, Associations or any Business Application.

The following configurations are now supported:

  • Business Applications have dedicated index pages, where users can search for the information pertaining to the specific business application.
  • Agreements and Associations index pages do not show information from Business Applications.
  • On the Advanced Search page, users have a choice to search for information from Agreements or specific business applications.
  • Left navigation of a business application entity page can be configured to show the relevant links.
  • Results for global search are categorized by the business application name if they are not Agreements or Associations.
  • When creating a Contract Type, seeded attributes only relevant to the Business Application Type and Category can be seededwill be selected.

Feature ID: 1183274 

Self-Service

Introduction of a Technical Admin user to access the System Configuration on Self Service Portal

With the risk of inaccuracies in technical configurations, given their critical importance, such configurations have been, till now, hosted outside the confines of ICI, where ICI admin users, who have azure subscriptions to an instance, authored the process.

Therefore, the capability of admin users within ICI were being limited and the scope of technical configurations had to be expanded.

Now, a solution has been devised with this feature, as enunciated in the following:

  • Technical Administrators can now be configured/added for performing required technical configurations in the System Configuration Portal, using the new “Technical Roles” field while adding, provisioning or editing a user.

Note: The user has to be Internal in order to be authorized with “Technical Roles”, and selecting an external user will automatically discount the Technical Roles feature.

  • The portal has been upgraded for Technical Admin users, with enhancements to the Landing page, header, menu options, along with a static welcome message.
  • Appropriate messaging and communication will be provided for any negative scenarios, wherein the Technical Admin User faces any challenge accessing or configuring.
  • When a new ICI admin user logs in, they should be able to setup other internal users as technical admin users of the System Configuration portal. 

Note: Only the ICI Admin user should be able to setup other internal provisioned users as the Technical Admin user.

  • The ICI Admin can either create a new Security group, as required, or use an existing security group. 
  • The authorization of technical admin users will depend on Security Groups Privilege to the “Self Service” privilege entity, and on roles assigned to specific users.
  • The “Self Service” privilege can be configured in the backend and it will be visible to users under the Security Group Privilege tab.
  • The “Manage” access option can be selected to grant access to the System Configuration Portal for technical admin users.

Note: The user who gets Technical Admin privileges can be any internal provisioned user on that instance (even a non admin user).

Feature ID: 1210894

Building the Config Key Update utility as part of the System Configuration on Self Service Portal

Today, in ICI – There are close to 800 configuration keys in the system. These keys are managed via the ICM Tools which is hosted outside of ICI. With this initiative, we have started the migration these Keys incrementally to be part of the System Configuration – Self Service Portal. 

The scope for this release is to migrate 10 keys into the utility. The access to this utility is driven by the Technical Admin role as explained in the previous section. 

Once the user successfully enters the ‘System Configuration – Self Service’ portal with the correct security groups and technical admin role, they will be able to see the ‘Config Key Updates’ entry point at the top of the screen

RN 8.1 2.png

On clicking the Config Key Updates menu, the user will be able to see the utility where the defined 10 keys will be loaded on the screen, along with their existing values.

RN 8.1 3.png

 

The user will be able to view each key loaded into a card. The card will contain the name of the key along with it’s value. 

The user will be able to see a dedication section to the right of the page for viewing help information

The user will be able to click on the ‘3-dot’ option on each card to edit the value of the key

RN 8.1 4.png

 

On clicking the Edit option, the key information will be loaded in the right drawer panel. Here the user can edit the key value and Save using the button at the bottom of the drawer

 

RN 8.1 5.png

 

The user can edit one or more keys using the ‘3-dot’ option on each card. Once the user has finished editing all the keys, they need to click on the ‘PUSH CHANGES TO ICI’ button at the top of the grid. This will internally update the keys with the edited values in ICI for the changes to take effect

 

RN 8.1 6.png

Feature ID: 1180864

Administration & Configuration 

Quick Configuration with ICI Import Solution

The ICI Import Solution is an automated solution for configuring ICI entities. It simplifies the initial configuration process and reduces the time and complexities involved in the process.

Using the Import Solution tool, ICI users can now:

  • Import configurations from a source ICI instance to a target ICI Instance with no pre-existing configuration data.
  • Import configurations between different versions of ICI.

Note: Support will be provided for up to 2 releases preceding the target ICI version.

  • Register and publish preconfigured import solutions.
  • Import the following information:
  • Contract Types
  • Templates
  • Clauses
  • Rules
  • Notifications
  • Masterdata Instances
  • Seeded Masterdata entity instances
  • Users & User Groups
  • Security Groups

Feature ID: 1262996 

Contract Types can now be locked for editing 

Contract types can now be edited by only one user at a time. This functionality helps prevent data inconsistencies or concurrency errors.

Product enhancements include:

  • A Lock/Unlock button on the contract type page. 
  • Auto system lock when users start edit a contract type without locking it. 
  • Messaging providing information on who is editing the contract type. 
  • System locks get released when contract types are saved.

Feature ID: 1212463 

Enhancements to Legacy Upload Tool

The following features will be added to the Legacy Upload utility with this release, improving speed and accuracy and reducing file size.

  • Records bypass workflow states directly to the desired state. 
  • Users can schedule upload in batches within guardrails to improve system resource allocation. 
  • Specific range of records from the UI can now be uploaded.
  • Infra and Elastic Search health check can be run before executing the scheduled batches.
  • On demand batch scheduling based on the user provided schedule. 
  • Supporting legacy entity created with large files 100MB+.

Feature ID: 1069763

Unique clause and template code for every environment

Users can now customize their clause and template codes for different instances. If unique codes are used, it reduces errors when migrating data from one instance to another. It also simplifies searching of clauses and templates.

Feature ID: 938126

Template and Clause creation options in Microsoft Word

The Create Template and Create Clause options in the Icertis Experience for Word are only displayed to users with access to these features. Earlier an error message was displayed to users without access and resulted in an unsatisfactory experience.

Feature ID: 1187041

Show or Hide confirmation messages in Microsoft Word 

Administrators can now choose to show or hide certain confirmation messages, as per the organization's preference, on the Icertis Experience for Word.

Feature ID: 1187044

Technology Updates

ServiceBus upgraded to Azure.Messaging.ServiceBus

“Azure.Messaging.ServiceBus” is now replacing “Microsoft.ServiceBus”.  

This is a Microsoft recommended upgrade and provides the following improvements:

  • Up-to-date, streamlined Azure.
  • More accurate messaging without any anomaly or junk data in the message characters.


Feature ID: 940871

Authentication Library and Graph API update

Microsoft has announced* deprecation of the Azure Active Directory (Azure AD) Authentication Library (ADAL) and Azure AD Graph API libraries and recommends using Microsoft Authentication Library (MSAL) and Microsoft Graph API.

We have updated Microsoft Graph, Identity and Key Vault packages to include stability and security fixes from Microsoft. The migration from ADAL and Azure AD Graph API to MSAL and Microsoft Graph API will ensure continuing support for the following areas:

  • User Provisioning 
  • Bulk Action 
  • Integration - SFDC, GIF (Generic Integration Framework), MSCRM  
  • Reporting 
  • Key Vault 

Refer to the following link for Microsoft’s circular: Update your applications to use Microsoft Authentication Library and Microsoft Graph API - Microsoft Tech Community.

Feature ID: 1276938

API Enhancements

In this release we focused on providing API 2.0 versions of most of our APIs with a goal to improve the performance and overall usability.

Following APIs are upgraded to API 2.0 versions in this release:

RN 8.1 7.PNG

RN 8.1 8.PNG

RN 8.1 9.PNG

RN 8.1 10.PNG

RN 8.1 11.PNG
RN 8.1 12.PNG

RN 8.1 13.PNG

RN 8.1 14.PNG

RN 8.1 15.PNG

RN 8.1 16.PNG

RN 8.1 17.PNG

RN 8.1 18.PNG

RN 8.1 19.PNG

RN 8.1 20.PNG

RN 8.1 21.PNG

RN 8.1 22.PNG

RN 8.1 23.PNG

RN 8.1 24.PNG

RN 8.1 25.PNG

RN 8.1 26.PNG

RN 8.1 27.PNG

RN 8.1 28.PNG

API Deprecations

Any integrations utilizing the deprecated APIs must adopt alternate APIs. Previously, API endpoints have been periodically deprecated and alternate APIs have been provisioned.

However, no existing API endpoints have been deprecated in the 8.1 Release. To check previously deprecated endpoints, refer to 7.16 Release Notes. More details on the alternate APIs are available in the Swagger documentation.

Mobile App Update 

Improved Security on Mobile Devices with SafetyNet Attestation API

With this release, ICI is implementing SafetyNet Attestation API for Android mobile application to restrict users from accessing the application through rooted/vulnerable device, to avoid breaching of the IT and cyber security policy.

Note: The SafetyNet Attestation API is supported Android version 8.0 onwards.

Feature ID: 1095223

AI Applications 

Usually, the implementation team spends a lot of time analyzing and training the AI model for the discovery of the new attributes. With this release, ICI is extending the number of pre-trained attributes so that the AI apps implementation project can be expedited. ICI previously had added 23 out-of-the-box attributes and introducing 15 additional attributes in this release, making it a total of 38 new attributes as a part pre-trained model. Customers can now start using attributes from pre-trained model with no or very little retraining.

The additional attributes are:

  • Acceptance Completion Period
  • Breach Cure Period
  • Confidentiality Survival Period
  • Force Majeure Period
  • Interest Percentage on Payment Delay
  • Liquidated Damages Cap
  • Policy changes notice period
  • Records Retention Period
  • Renewal notice period
  • Signatory Name
  • Signatory Title
  • Signature Date
  • Termination for cause notice period
  • Termination for convenience notice period
  • Warranty Claim Period

Feature ID: 1187824

Enhancing the scope of DiscoverAI app& Negotiate AI differentiation

Discover AI helps users to identify attributes and clauses in browser and save them in the system.

With this release, scope of DiscoverAI has been enhanced to include the discovery of attributes and clauses within Microsoft word also using Icertis Experience for Word plugin. 

  • The following actions/functionalities will be available under the Discover AI license in Icertis experience for Word: 
  • Discovery of attributes and clauses. 
  • Confirm, Confirm with Deviation, Ignore, Compare and Replace the clauses based on discovered clauses data. 
  • Select the Matched Clause from the library. 

Feature ID: 1284012

Reports Enhancements

Data for agreements awaiting signature in reports

Out-of-the-box ICI reports will now display details for the business status “Waiting for Signature”, in addition to existing statuses. This update to the reporting logic resolves an existing gap in the reports data.

This enhancement applies to the following reports:

RN 8.1 29.PNG

Feature ID: 1071182

Custom reporting views using JSON 

Developers can now create new custom reports views using Stored Procedures (SP) and JSON files. This feature gives flexibility to organizations to easily develop new reports relevant to their business requirements.

An Import SP is now available that takes JSON files as input. The JSON file used for input is where developers can define the new view. New reporting views are automatically created on running the Import SP.

An Export SP is also provided, which can be used to download a JSON file which contains the structure of an existing view in the database, to use as a template to create a new views.

Feature ID: 1208472

Dataset and seeded dashboard for Proposal Management application

A dedicated Power BI Dataset is now available for the Proposal Management application for out-of-the-box and custom reporting.  

PM App Power BI report will have clickable links to ICI entity details page for Proposal Management Entities such as, Sell Side RFx, RFx Qualification, and Bid Proposal.

Feature ID: 1232650

Attribute Information Report Enhancements

The following filters and columns are added to the Attribute Information report giving more options to analyse the Attributes used in the system.

  • Filters: Contract Type, and Group by Property Columns: Is Mandatory and Tracking Attribute

Feature ID: 1158976

Edit SSRS Reports without customization

Icertis and partner developers can now edit the SQL Server Reporting Services (SSRS) reports eliminating the need to create additional customized reports even for small changes. Users can now make the following edits to SSRS reports:

  • Add or remove columns in an existing report.
  • Modify column’s position, name, or default values.
  • Modify sorting order of the results.
  • Apply query level filters.
  • Apply security group access as standard reports.
  • Create copy of existing report and modify it.
  • Use a new framework, which has a JSON-based interface.
  • Create new or modify custom reports.

Feature ID: 744814

Report-based edit access for Power BI reports

Manage access for Power BI reports can now be provided at a report level to ensure that edit access is only given to the necessary users within the organization.
This feature works does not impact “Advanced Analytics” access.

Feature ID: 1070905

Maintainance and storage optimization with a Common Data Model for Clause-based reports

PlatformClause - a common data model for clause related information can now be used to create clause-based reports such as Clause Profiling Report, Clause Pending Approval Report and more. This helps optimize storage capacity and reduces the development and maintenance effort siginificantly. 

Feature ID: 1083685

SSRS Reports now available with Power BI

Power BI reports are faster, more scalable, richer in features, customization-friendly, sport a modern UI and overall a better experience. To leverage its advantages, the following SSRS reports are now made available in Power BI:

  • Clause Summary Report
  • Tagged Attribute Report
  • Agreement Clause Content Report – A widget that displays the clauses with the most deviations is also added in this release. 

Feature IDs: 1214787, 1214720, 1223598
 

Salesforce Integration 

 Activity Object and Trigger Simplification in Salesforce Adapter

The following enhancements are made to the SFDC Manage package Adapter:

  • Triggers for Accounts and Opportunity objects have been removed from the Managed package to avoid unnecessary update-related issues. Users can get more flexibility and control over them when they use the auto contract creation feature. Note: This is applicable to both fresh installs as well as updates on existing packages.
  • Previously, 6 custom fields were needed on the Salesforce activity object to sync ICI tasks with Salesforce, and now, the dependency on these fields have been reduced with only 2 custom fields required for the sync.
  • For customers who didn’t need the ICI task sync feature and were unable to remove the custom fields with the limit of 100 fields on the Activity object, now, these fields have been removed from our managed package to provide more flexibility.

Note: Guideline documentation and support by ICI implementation/upgrade team will be duly provided, for creation of desired fields during new installs as well as release upgrades, or deletion of fields during upgrade scenarios.

Feature ID: 1066353

User Experience for Salesforce Revamped

Using ICI within Salesforce is now a more seamless experience as we have made significant improvements to preserve the native Salesforce UI interactions, which users are familiar with, without compromising the ICI functionality.

These are the enhancements that have been introduced:

  •  Native Salesforce components are now used along with the ICI iframe.
  • Sub-tabs moved from ICI to Salesforce native tabs, for example: Agreements, Requests and Agreement Reports.
  • Agreement and Request Details pages are now displayed in native Salesforce UI.
  • On the Details page certain actions (example - Reset Expiry) and sub-tabs (example – Associations) are now native Salesforce components.

Note: The implementation team will provide a list of native and i-frame components.

Feature ID: 1186642

eSign Integration 

Integration Support for DocuSign using JWT authentication

The ICI and DocuSign integration was previously based on authenticating the APIs with “IntegratorKey” and “API Password”.

The product has now been upgraded to support an enhanced authentication using JSON Web Token (JWT), along with the existing basic authentication support. This enhancement has also enabled JWT support for “Multisign” as well as “Single Esign” configurations.

Feature ID: 1000798

DocuSign API upgraded from 2.0 to 2.1

DocuSign released an update announcement that OAuth 2.0 would be required to support DocuSign API applications. In keeping with this announcement we have upgraded DocuSign REST APIs from 2.0 to 2.1. With this upgrade, a new JSON parser has been introduced to support DocuSign Connect, a notification mechanism to receive updates when any event is triggered in the eSignature workflow.

Feature ID: 1060689

Adapting webhook feature of Adobe Sign

Adobe Sign adapter couldn’t communicate precise callback information to ICI Platform, thus causing intermittent errors in ICM workflow after the Agreements were electronically signed. Adobe Sign responded with the same information for every signature, hence it wasn’t possible to distinguish between callbacks from different signature. However, with the introduction of Adobe webhook, this problem can be resolved.

Adobe webhooks can be created on the workflow for each agreement, requesting the type of information in the callback, which further benefits as follows:

  • Identifying the signatory requesting a callback
  • Identifying for which event or action the callback is requested
  • Concisely updating the status in ICM

Note:  Upgrade Adobe Sign API from 5.0 to 6.0 to use the webhook feature.

Also, Adobe rebranded Echo sign to Adobe Sign, hence non overridden localization strings for validation messages have been modified accordingly.

Feature ID: 1091947

Electronic Signature support using ICI BioPharma setting for 21 CFR Part 11 & Annex 11 compliant groups

ICI Platform now supports the Life Science industry documents that need to comply with 21 CFR Part 11 (for US FDA) or Annex 11 (for EU) regulatory compliance.

This feature allows integration with DocuSign Part 11 module and Adobe Sign Bio-Pharma setting to get electronically signed approvals for such agreements.

Feature ID: 1220095

Changes in IP whitelisting process for eSign adapters

ICI Platform supports integration with third party eSign adapters, which communicate using callback information. To receive the callback data from the eSign servers, certain IPs to intended methods are whitelisted. This action is done through the web.config file. However, any change in the IPs requires modifying the web.config file, which resets the IIS, resulting in performance issues.

To address this issue, “Core.IPSecurity” key has been introduced, which stores information related to the IPs as a JSON, and thus eliminates the need to modify the web.config file.

Note: Blocking or allowing IP addresses based on DNS is not supported as a part of this feature.

Feature ID: 1193062

Update eSign document with correct status

In certain scenarios, the electronic signature status in ICI and eSign provider are inconsistent. An enhancement has been added wherein the respective statuses are verified and the agreement status is updated or corrected accordingly.

Feature ID: 1193061

Sourcing 

The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (SRC8.1.0.404).

Support for new RFx type-RFP

Icertis Sourcing application now supports Requests for Proposals (RFPs). Organizations can leverage the advantages of a secure and seamless application to organize and maintain their procurement processes digitally using the RFP feature.

RfPs are integrated requests containing information on both questions and bids. Buyers can now design, create, and publish RFPs in the Sourcing application and invite suppliers to respond to them. Once Buyers receive the responses, they can evaluate them and make their procurement decisions.

Key RFP features:

  • Integrated mechanism to get responses to questions and bids from suppliers.
  • Reusable templates for Questions, Questionnaires, and Bidding templates.
  • Questionnaires and questions can be arranged and reordered as required. 
  • Attachments, and responses to questions can be downloaded in a package.
  • A consolidated excel spreadsheet is available to analyse bids and responses.
  • Suppliers can provide responses to questions using Excel as well as Sourcing UI.

Feature ID: 404602

Improved Sourcing workflow with Sourcing Request

Users within an organization can now create Sourcing Requests for procuring items or services. These requests can be designed to go through an approval flow before they are turned over to procurement teams. The approval cycle can be easily tracked and audited for compliance.

Sourcing Request features:

  • Configure a Sourcing Request based on the necessary privileges.
  • Request forms can be designed to capture necessary details and attachments.
  • Requests can be sent to designated approvers for approval.
  • An RFx can be created after the request is approved.
  • Requests can be modified until they are approved or a RFX is created based on it.
  • Cancel or recall the Sourcing Request.
  • Put the Sourcing Request on Hold till approved state provided RFx is not created using this Sourcing Request.

Feature ID: 611297

Ordering and additional data types for Questions in Questionnaire

We have made the following enhancements to Icertis Sourcing to improve the user experience when working with Questions and Questionnaires:

The order of Questions and questionnaires in RFx can be set and modified as per the preference of users.

The following data types are now supported for questions in RFx:

  • Boolean
  • String
  • Choice
  • Multi Choice
  • Currency
  • DateTime
  • Number
  • Percentage
  • Text Area
  • Rich Text Area  
  • Email
  • File Selection

Note:

  • On exporting rich text data type information to Excel or HTML, some formatting features may be lost.
  • Uploading a file attachment as response for file type question response using Excel is not supported. Supplier must log on to ICI to upload files.

Feature ID: 896873

Obligation Management 

The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application (OM8.1.0.404).

An interface to quickly add obligations discovered by AI

Obligations that are identified in contracts using the Discover AI feature can now be easily reviewed on the user interface. User can review the obligations and decide to add one or more to the Obligation Management application for tracking approvals and fulfillment.

The interface to review and create obligations in bulk saves users much time and manual effort.

The following image shows an example of creating Obligations in bulk:

RN 8.1 30.png

Notifications for successfully processed or failed obligations can also be configured.

Feature ID: 1090383

Auto-approval of Obligations to improve efficiency

Many obligations are extracted from executed contracts and they don’t usually need to go through an approval process in the Obligation Management application. To reduce time and effort spent approving a large number of obligations and not block the obligation fulfillment lifecycle on account of pending approvals, an automatic approval process for obligations can now be configured.

Once the auto-approval process is defined based on obligation taxonomy, this is how the feature works:

  • If approval is turned off, and no approvers are added to obligations, the obligations are automatically approved.
  • If approvers are added to obligations, manually or automatically through a rule, then even if approvals are turned off, the obligations will need to be approved.

Feature ID: 519344

Organize and manage obligations by creating groups 

An obligations could have one or more sub obligations or tasks, which would need to be completed by different individuals in an organization. Also, some obligations may be related to each other and grouping them could help organize and track the fulfillment. To facilitate such scenarios, obligation groups can now be created in the Obligation Management application.

Users can now categorize different obligations under logical groups and create parent-child relationships between obligations.

Child obligations automatically inherit any changes made to the parent Obligation. For example, if the status of parent Obligation is changed to Approved, all the related child Obligations also get approved.

Feature ID: 649768

Duplicate obligations no longer inherited 

When an Agreement (parent), with an associated Obligation, is inherited by another Agreement (peer), a duplicate Obligation is created. An enhancement in this release eliminates this limitation.

Feature ID: 1040723

UI Improvements for Obligation Management

The following improvements are made in the product to improve the search and usability experience when using Obligation Management:

  • Dedicated index pages for Obligations and Fulfillments,
  • Relevant page titles, breadcrumbs and history page information.

Feature ID: 1236413

Risk Management

The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (RM8.1.0.404).

UI Improvements for Risk Management 

The following Improvements are made in the product to improve the search and usability experience when using Risk Management: 

  • Dedicated index pages for Risk Management and Risk Assessment. 
  • Relevant page titles, breadcrumbs and history page information. 
  • Saved searches display Risk Assessment as category.  
  • The “Create” action button has now been added on the “Risk Assessment” index page.   
RN 8.1 31.png

Other enhancements include:

  • The “Delete” action has now been moved under the three dots icon on the Risk Assessment “Details” page. On deleting the risk assessment, users will be redirected to the Risk Assessment “Index” page.

Feature ID: 1067718

Proposal Management 

ICI Proposal Management application is certified to work with the 8.1 release (PM8.1.0.404). 

Track and analyse performance with a Power BI Dashboard

A seeded dashboard that helps supplier organizations track their proposals by status, time, and outcome is now available within the Proposal Management application.The following features and reports are now available with the Proposal Management application:

  • A new Power BI data model with Power BI dataset specific to Proposal Management.
  • Proposal Management KPIs report
  • Capture Management report

Note: Users with access to Sell Side RFx or Bid Proposal can view the Dashboard.

RN 8.1 31.png

 

Enhancements to Seeded Contract Types

With this release, the PM App is being enhanced with newly seeded attributes to its seeded contract types.

In this enhancement:

  • New attributes have been seeded with the Bid Proposal entity:
  • Total Bid Value For Proposal
  • Total Value Won Or Lost
  • Customer Address
  • Customer Geography

These new attributes contribute in the essential computations of the Win Ratio and the Value Capture Ratio.

Feature ID: 1186830

Revamped User Experience across the PM App

The visual look and feel of the Proposal Management App has been considerably enhanced with the ICI-wide implementation of the new UI (User Interface) and UX (User Experience).

The following summarizes the revamped user experience across the App:

  • The new “Proposals” tile menu now features only the viewing tile options for the seeded PM App entities, in addition to a new “Dashboard” tile menu option.
  • The create navigation flow has been moved from the “Proposals” tile and a dedicated “Create” button has now been added to each seeded entity index page.
  • The seeded entities now have their dedicated index pages, as opposed to the saved search driven listing in previous releases.
  • The Details pages of all the seeded entities (Sell Side RFx, Bid Proposal etc.) now have dedicated page titles starting with the entity name, instead of the contract type category. For example, the previous “Agreement / Sell Side RFx 123” has been replaced by “Sell Side RFx / Sell Side RFx 123”.
  • The newly added entity name (such as “Sell Side RFx”) on the Details page header is now a clickable link, clicking which opens the entity index page.
  • In the audit history of any entity, both Grid View and List View, the header now features the entity category name instead of the contract type, just like the change in entity Details page.
  • The display of action buttons on entity Details pages can now be configured to customize their sequence of display, and based on the available window space the remaining action buttons will be available under the three dots icon on the entity “Details” page.

Feature ID: 1235186

Supplier Relationship Management Application 

ICI Proposal Management application is certified to work with the 8.1 release (SRM8.1.0.404).

Supplier Evaluation

The Supplier Evaluation module introduced in the Supplier Relationship Management suite helps organizations manage supplier performance and evaluate and mitigate risks associated with working with suppliers.

How Supplier Evaluation fits within Supplier Relationship Management

RN 8.1 33.png

The Supplier Evaluation module introduced in the Supplier Relationship Management suite helps organizations manage supplier performance and evaluate and mitigate risks associated with working with suppliers.

How Supplier Evaluation fits within Supplier Relationship Management

 

Supplier Evaluation module is part of the Supplier Relationship Management application, which is built on Icertis Contract Intelligence.

Once suppliers are onboarded, users can evaluate suppliers on the products or services they offer. The KPI criteria, schedule, and the evaluators can be set up within the module and on completing the assessment the supplier can be classified as high performing, low performing or standard supplier.

A routine supplier evaluation can help organizations set expectations from their preferred suppliers and manage low performing suppliers.  

Supplier Evaluation Features

Setting up Supplier Evaluation

  • KPIs – Users can create one or more KPIs (evaluation criteria) and evaluate suppliers based on the set parameters. For example, you can create KPIs for auditing, performance reviews, training requirements, and more.
  • Supplier Data – The supplier evaluation creation process is simplified as much of the supplier information is auto-populated based on the supplier’s record.
  • Evaluation Schedule – Users can set up a period for which the supplier will be evaluated.
  • Product/Service for Evaluation – The evaluation can be performed in context of the product or service provided or the agreements.
  • Reviewing suppliers based on the Criteria – The evaluation criteria can be put through an internal review process, and inputs can be sought to finalize the evaluation criteria.
  • Supplier Outreach – Suppliers can provide information and supporting documents needed to perform the evaluation by responding to review requests by buyers.
  • Responses & Scoring – Based on the responses provided by business team or evaluators on the supplier evaluation, scores are automatically computed.
  • Evaluation Approvals & Control – Once the evaluation process is over, then buyer team defines supplier performance classification and suggests the next course of action (in case of low performing supplier). This can also be sent for management approval. The approver team can either approve or reject and send it for rework..
  • Notifications – Notifications can also be configured for periodic evaluation. System notifications are sent to buyers when they are requested to evaluate a supplier.

Feature ID: 463049

Managing Supplier Hierarchy

Manage Related Supplier Organizations

The Supplier Relationship Management application now provides a mechanism to connect supplier organizations with their Parent, Holding or Subsidiary organizations. This is to ensure that you have a complete overview of the business you do with one supplier and its related entities. According to business needs, you may want to work with a local supplier or the parent global organization.

You can designate a supplier organization as one of the following types:

  • Supplier: Supplier organizations that may or may not have related Parent or Holding companies.
  • Parent company: Parent company of one or more Supplier organizations, controls operations of the Supplier Organization
  • Holding company: Holding company of one or more subsidiary Supplier organizations, does not have a direct say over the operations of subsidiaries.

Changes made to the supplier hierarchy for supplier registration, qualification or profile are synchronized with the vendor database and supplier master.

Unique Supplier Record Management

In Icertis Supplier Relationship management, the uniqueness of a supplier record is validated based on a combination of attributes . In this release, one or more of the unique identifiers attributes can be made editable. This is to account for entities that may change the Legal Entity Name in the course of doing business, considering legal entity name is one of the unique identifier attributes.

If the attributes are changed for an organization, the system validates and checks for duplicate records before allowing users to make the change.

Validating the Duplicate Registrations

Buyers may receive more than one registration from the same supplier submitted through the web page.

This release introduces the capability to match the supplier registration records based on the unique identifier attributes. This helps identifying the duplicate registrations. Buyers can perform limited actions on the duplicate registrations and the supplier qualification is not generated.

Note: Customers upgrading to 8.1 from previous versions of ICI Supplier Relationship Management is supported.

Feature ID: 1271423

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:

RN 8.1 43.PNG

RN 8.1 44.PNG

RN 8.1 45.PNG

Important Changes in IE11 Support:

From March 2021, Microsoft has stopped its technical support to Internet Explorer (IE) and has advised its customers to move to Microsoft Edge.

ICI will no longer support IE11. ICI will not be certified over IE11.

If customers use IE 11 then the below message will be displayed:

“You are using a browser that is not recommended to be used since it no longer supported by its OEM. The ICI support for this browser is limited for 7.16 version and will be discontinued from version 7.17 onwards. You should switch to Microsoft Edge as recommended by the OEM or any other supported browser prescribed by your organizational policy. You may contact your administrator for further information.”

RN 8.1 46.PNG 

RN 8.1 47.PNG

RN 8.1 48.PNG
RN 8.1 49.PNG
RN 8.1 50.PNG

RN 8.1 51.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:

RN 8.1 52.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.1/index.php?title=Release_Notes&oldid=24894"