Revision as of 08:33, 25 January 2021 (view source) WikiSysop (Talk | contribs) ← Older edit		Latest revision as of 08:35, 25 June 2022 (view source) WikiSysop (Talk | contribs)
(86 intermediate revisions by 4 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'''''	+
−	***To ensure that the agreement document is generated with the correct clauses and metadata we now have the ability to preview an agreement from the pre-draft stage to the Approved stage, enabling a comprehensive review before publishing the contract.&nbsp;	+
−	***Improved usability for the global user base and their individual UI language preferences via expanded localization coverage now includes support for “Reason Codes”.	+
−	***Friction-free collaboration enabled via the Collaboration Portal’s external user interface that features the ability to search contract requests, agreements, associations and masterdata records on the index pages.&nbsp;	+
−	***Significantly improved accuracy and velocity of the document review process now featuring display order for clauses in the ICI web and Icertis Experience for Word that match the order in which the clauses are configured in the respective template and generated agreement. &nbsp; &nbsp;	+
−	***Improved usability now featuring the configurability of the attribute multi-selection interface when creating an agreement as either radio buttons or checkboxes per contract type to tailor the agreement creation experience.&nbsp;	+
−	***Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export.&nbsp;	+
−	***Improved usability where the sequence of values displayed in a masterdata lookup dropdown can now be configured to have the most frequently accessed values at the top.&nbsp;	+
−	*	+
−	**'''''Workflow Enhancements'''''	+
−	***Improved usability including the ability to create instances of associations as part of the agreement creation wizard itself.	+
−	***To continue bringing Extension Attributes capabilities at par with regular attributes, these are now quickly viewable for easy reference in the agreement entity’s “Agreement Clauses” tab.<br/> Agreements can be Approved or Rejected from within an agreement notification email itself making it faster to take actions on an agreement, reducing turnaround time for approval cycles.&nbsp;	+
−	***Improved system availability during Publish operations where only the contract types being published are not available during this system operation.	+
−	***Expanded contract request experience now including contract terminations.	+
−	***To save time when re-instantiating a terminated agreement, due to reasons such as reviving a business relationship, you can now do so by simply adding amendments to the terminated agreement rather than by having to create a new agreement from scratch.	+
−	***Bulk actions support now extended to Terminating agreements to support situations like regulatory changes, or business partner insolvency. &nbsp;	+
−	***Improved first-run experience via simplified administration of default user preferences set at user creation or update based on location or department.	+
−	***Simplified review of signature status labels of “External”, “Internal,” and “Fully Signed” are available in agreement versions.	+
−	***Enhanced flexibility when executing a large volume of contracts by not requiring uploading documents to change agreement status from “Waiting For Signature” to “Executed – Document Upload Pending”.	+
−	***Enabling sharing of Associated Documents via email notifications that are triggered for an agreement.	+
−	***For organizational changes, or employee turnover we now provide a data management interface that enables replacing users with multiple users on supported entities.	+
−	***Support for granularly defining which agreement attributes for a given contract type should be cascaded to the agreement’s amendments via the “Is Inherit On Amendments” flag at the agreement contract type and template variable level.	+
−	***In addition to the currently available functionality of all attributes to be superseded capability, we now offer the ability to selectively supersede an attribute.&nbsp;	+
−	***Conditional attributes comparison operators now have expanded capability to support multiple complex conditions to dynamically display attributes based on a range of business scenarios.	+
−	***Simplifying navigation by providing the capability of showing or hiding the “No Team Available” message during workflows when a team is not needed.	+
−	***Expanded support for special characters in the Attribute display name for contract requests, agreements, associations and masterdata.	+
−	***Selectively download amendments with the corresponding parent and child associations in a zip package respecting sub-folders.&nbsp;	+
−	***Larger file size support when uploading (4GB) and downloading (6GB) larger files for masterdata and associations.&nbsp;	+
−	***Simplified smart filter creation using string operators such as “Contains”, “Starts With”, “Does Not Contain” for the “Business Status” search facet.	+
−	***Expanded automation support for bulk clauses and template upload reducing the dependency on manual approvals and delays in onboarding clauses and templates.	+
−	***Enhanced configurable labels for peer associations that define the contractual relationship. (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).<br/> &nbsp;	+
−	*<span style="color:#800080;">'''Mobile App Updates'''</span>	+
−	**Enhancing &nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users.	+
−	*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>	+	The 8.1 Release introduces the following enhancements to the Icertis Contract Intelligence (ICI) platform:
−	**Providing support for script and integrated attributes as cascaded attributes for lookup fields when configured at the contract type level. This is applicable for retrieval, creation, and updating of the instances of contract requests, agreements, associations, and amendments.	+
−	**Adding the identifier “TrackingId” which can be passed by subsequent API calls for logging and troubleshooting errors.	+
−	**Adding&nbsp;support for troubleshooting API issues with failure notifications. &nbsp;	+
−	*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>	+	== Icertis Contract Intelligence&nbsp; ==
−	**'''''Icertis Experience for Word'''''	+
−	***Improving the filtering and searching capability with support for searching text inside clauses or templates to allow more powerful search especially when searching across large libraries.&nbsp;	+
−	***Improving labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.	+
−	***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;	+
−	*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>	+	=== Agreement & Platform&nbsp; ===
−	**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 filter. Administrators can create a new playbook record or update the existing one from within Icertis Experience for Word itself.	+
−	**Improving the clause delineation logic so that users can rearrange the clause boundaries identified by AI. They can merge or split discovered clauses or selected text in a clause, and create a sub-clause within the discovered clause.	+
−	**Extending clause hierarchy discovery support to text PDF as well as .docx documents.&nbsp;	+
−	**Improving library clause recommendations for discovered clause based on learnings from user’s action in previous discoveries.&nbsp;	+
−	**Providing support for additional languages including “French”, “Dutch”, “Norwegian” and “Swedish” in AI apps.	+
−	**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself. Thus, the discovered values will be auto-filled in empty attributes, instead of having to enter them manually making the discovery process redundant. This provides more flexibility to use AI on demand. &nbsp;	+
−	**Enhancing and optimizing the performance of ML service to simplify deployment and run the workload on-demand, with zero or less management of infrastructure.<br/> &nbsp;	+
−	*<span style="color:#800080;">'''Enhancements to Reports'''</span>	+	'''A new collaboration experience with Microsoft Teams'''
−	**Introducing the “Tagged Attributes Report” enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. This will help the Legal/admin users to assess the impact of configuration changes to the clauses and templates.&nbsp;	+
−	**Introducing the “Notifications History Report” for an entity, enabling users to track what notifications were sent to which recipient and when. This provides better visibility and compliance for the users.	+
−	**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.	+
−	**Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.	+
−	**Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis. &nbsp;	+
−	**Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.	+
−	**Multiple localization enhancements within reports.	+
−	*<span style="color:#800080;">'''Improving the Icertis Experience'''</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.
−	**'''''Signature Workflow'''''	+
−	***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid (manual and/or electronic) signature process enables users to add and modify signatories, preview the DocuSign console, and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).	+
−	***Enabling ICI platform to support more than one E-signature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.	+
−	***Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process.&nbsp;<br/> &nbsp;	+
−	**'''''Icertis Experience for Salesforce'''''	+
−	***Providing the ability to send success and failure alerts for improved monitoring of messages.	+
−	***Triggering document assembly for automatic data sync and displaying completion notification.	+
−	***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.<br/> &nbsp;	+
−	**'''''Icertis Experience for MS CRM'''''	+
−	***Providing server-to-server OAuth support, so that the adapter and the task service will use ‘client Id’ and ‘secret key’ from AKV, invoking the MS CRM APIs.	+
−	*<font color="#800080">'''Enhancements to Platform Tools'''</font>	+	The feature includes:
−	**Enhancing ICI to allow Administrators to promote additional configurable entities from pre-production to target environments. These include organizations and organization groups, users and user groups, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings, global and admin saved searches	+
−	*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>	+	*Contract owner can initiate a collaboration on MS teams from agreement details page and also invite agreement team members to participate in the discussion.
−	**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.	+	*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
−	These release notes provide an overview of the enhancements to ICI, the mobile app, the ICI experience for integrations, and so on.	+	Feature ID: 1188391
−	&nbsp;	+	'''Negotiate and Update Agreements with the new Outlook Add-in'''
−	== <span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span> ==	+	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="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</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.
−	Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.	+	With the Outlook Add-in improvements, users can now do the following:
−	With this release, a preview functionality is being introduced, so that the primary owner or contract creator can review whether the selected template is appropriate, the rule-based clauses have been correctly added to the agreement, among other factors, and make changes to the agreement before the version is created. The preview document would also include tagged associated documents, coming through inline or inheritance associations.	+	*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;
−	A preview section is available on the “Verify” stage of agreement/amendment creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. The preview is available till the Approved state of the agreement/amendment.	+	Feature IDs: 1137119, 1137121
−	'''Note: '''This functionality is configurable. It is not available by default and can be enabled or disabled for chosen contract types.	+	'''Quick & Easy Agreement Creation'''
−	&nbsp;	+	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.
−	<span style="color:#800080;">'''575640 – Creating associations on the create or edit wizard of agreement'''</span>	+	Feature ID: 1183356
−	Previously in ICI, contract authors had to create associations for agreements after the agreement is already created. However, in practical terms associations such as annexures, supporting documents, SLAs, product specifications, rate tables, and so on, are all an inherent part of agreement information that is critical to the business, and some associations are required to be created along with the agreement.	+	'''More Quick Action Options'''
−	Hence, the ability to create association instances as part of agreement creation or update wizard is being introduced in this release. A separate page is displayed, when creating or updating the agreement or amendment, for the user to create, view, or delete inline associations. The user also has an option to select the columns and their order in the association grid.&nbsp;	+	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
−	This new page also supports page navigation. Support is also provided to copy attribute rules, association events, and agreement assembly, in case associations are tagged in the agreement template.	+	'''External Emails Split to Ensure Compliance&nbsp;'''
−	<br/>  <br/> <span style="color:#800080;">'''549900 – Supporting localized reason code values as per logged in user language'''</span>	+	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;
−	Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers.	+	'''Deviation management for text and tables outside content control'''
−	ICI now extends its localization support to reason code values. Administrators can enter the translated values in the local language, for each reason code, using the “Translations Editor” tool.	+	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;
−	Users can see localized reason codes as per their preferred language settings.&nbsp;	+	'''Support for Microsoft Powerpoint documents'''
−	The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.	+	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.
−	&nbsp;	+	Feature ID: 1183367
−	<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from contract request'''</span>	+	'''Online Editing Of Own Paper'''
−	In ICI, users create and execute a termination agreement on the main agreement instance to terminate an agreement. ICI has now extended this capability to initiate the termination from contract requests too.&nbsp;	+	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.
−	Users can now enable the termination process at the contract type level using the seeded attribute "Request for Termination", select the parent contract request, and create the termination contract on a contract request. The termination instance for the contract request will have all the common attribute values inherited if the inheritance is enabled.&nbsp;	+	The following improvements can be observed:
−	The termination record will be displayed as a peer association under the “Association” tab for the contract request. The access privileges for the contract requests termination process is controlled through role action mapping.	+	*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;
−	&nbsp;	+	Feature ID: 1287270&nbsp;
−	'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''	+	'''Support for Inheritance of Bulk Associations&nbsp;'''
−	ICI’s collaboration portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself.&nbsp;	+	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;
−	In our continuous effort to improve usability, a search option has been introduced on contract requests, agreements, associations, and masterdata index pages, so that external users can easily search records. The attributes displayed as columns of the search grid are included as facets in the filter options to perform a more refined search.	+	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.
−	&nbsp;	+	Feature ID: 1278205&nbsp;
−	<span style="color:#800080;">'''514605 – Supporting extended clause attributes in agreements'''</span>	+	'''Enhancement to Download all Agreement & Associated Documents in one click''' &nbsp;
−	In ICI, users can capture additional details for a clause in extension attributes. With this release, users can view these clause extension attributes on the agreement entity for easy reference while working with agreements.&nbsp;	+	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;
−	Users can now:&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.
−	*Select and save extension attributes to display in the grid view, via the “Default Search” column functionality.	+	Additionally, the “Download All” button will now be visible to users based on the role action mapping in superseded state as well.&nbsp;
−	*View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs.	+
−	*View the hyperlink “Show Clause Information”, which displays all clause extension attributes along with clause attributes, in the same window.<br/> &nbsp;	+
−	<br/> <span style="color:#800080;">'''514615 – Streamlining&nbsp;the approval process over emails'''</span>	+	Feature ID: 980342&nbsp;
−	The approval process has now been streamlined by allowing approvers to directly approve or reject an agreement from within the email itself, through a hyperlink to the webpage, instead of logging in to the system to do so. External users, who do not have access to ICI can now review or approve the documents from the notification email, instead of sending offline copies to do so and then uploading them to ICI. This reduces the overall turnaround time and increases productivity.&nbsp;	+	'''Platform changes to enhance UX for Business Applications'''
−	The internal users are authenticated through the SSO/IDP before opening the page where the actions are to be taken. The external users are authenticated by sending them a code in the email, which has limited validity.&nbsp;	+	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.
−	With this release:	+	The following configurations are now supported:
−	*Administrators can add tag an Approve/Reject link in the notification template.	+	*Business Applications have dedicated index pages, where users can search for the information pertaining to the specific business application.
−	*Approvers/reviewers can download the agreement, modify it and upload it back to ICI.	+	*Agreements and Associations index pages do not show information from Business Applications.
−	*Approvers can approve/reject the agreement or amendment from the email, only if the task approval or review is assigned to them. Based on the access, the user can approve or reject the agreement by entering notes or reasons for rejection respectively.<br/> &nbsp;	+	*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.
−	<span style="color:#800080;">'''514643 – Ordering of clauses as tagged in an agreement'''</span>	+	Feature ID: 1183274&nbsp;
−	To improve the user experience, clauses are now displayed in the same order in the agreement document as they are tagged inside the agreement, on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.	+	=== Self-Service ===
−	&nbsp;	+	'''Introduction of a Technical Admin user to access the System Configuration on Self Service Portal'''
−	<span style="color:#800080;">'''514643 – Ability to define additional clause group under clause entity'''</span>	+	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.
−	Previously, ICI supported 3 clause groups – “Termination”, “Legal” and “None”.	+	Therefore, the capability of admin users within ICI were being limited and the scope of technical configurations had to be expanded.
−	With this release, this capability has been further enhanced so that the configurator can configure various clause group names in ICI. These clause groups can be categorized or grouped as per business requirements for better identification and negotiations during the contract workflow.	+	Now, a solution has been devised with this feature, as enunciated in the following:
−	Administrators can now:	+	*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.
−	*Define and update clause groups.	+	'''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.
−	*Edit, delete, activate or deactivate clause group entities.	+
−	*View additionally added clause group values in the clause entity when creating or editing a clause.	+
−	*Search agreement records or clauses on the index page on clause group attributes with added values.<br/> &nbsp;	+
−	<span style="color:#800080;">'''514621 – Reviving terminated agreements'''</span>	+	*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;
−	Users may terminate an agreement with the other party for various business reasons. To improve usability, ICI now provides the capability to add and execute amendments on a terminated agreement. This considerably saves time for users who may want to re-instantiate their existing relationship with the other party, as they no longer need to create an entirely new agreement and go through several workflows such as clause deviations clearance, template process, and so on.	+	'''Note:''' Only the ICI Admin user should be able to setup other internal provisioned users as the Technical Admin user.
−	Adding and executing an amendment on a terminated agreement will move the agreement back to the “Executed” or “Expired” state, based on its expiry date, thus reviving the terminated agreement. The system sets an identifier attribute "Is Termination Revived" for such revived base agreements, and users can use them in search filters, notification rules while configuring saved searches, and so on.	+	*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: '''By default, only primary owners and contract managers can add an amendment to the terminated agreement. The access privileges are controlled through role action mapping.&nbsp;<br/> &nbsp;	+	'''Note:''' The user who gets Technical Admin privileges can be any internal provisioned user on that instance (even a non admin user).
−	<span style="color:#800080;">'''514625 – Terminating agreements in bulk'''</span>	+	Feature ID: 1210894
−	Users may need to terminate agreements in bulk in many business scenarios such as regulatory changes, changes in product offerings, and so on. Users can now initiate the termination of agreements in bulk, thereby saving the time to terminate agreements one by one and reducing manual errors.	+	'''Building the Config Key Update utility as part of the System Configuration on Self Service Portal'''
−	Bulk termination is carried out using ICI’s existing “Bulk Actions” process. The termination related attributes will be pre-selected, and the Workbook for the bulk action batch will be generated with the executed agreement records from the saved search, as per the selected contract type and termination contract type.&nbsp;	+	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;
−	Users can now:&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;
−	*Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch. &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
−	*Generate and view a status report for agreements terminated in bulk.&nbsp;	+	<div class="image-green-border">[[File:RN 8.1 2.png|720px|RN 8.1 2.png]]</div>
−	*Create termination agreements for “Draft”, “Published” or “Send for Approval” states, as per the batch Workbook configuration for bulk action.	+	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;
−	'''Note:''' All prerequisite configurations applicable for the termination workflow should also be set for the bulk termination process.<br/> &nbsp;	+	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;
−	<span style="color:#800080;">'''555898 – Defining display sequence on lookup attributes at the contract type level'''</span>	+	The user will be able to see a dedication section to the right of the page for viewing help information
−	Previously in ICI, users could not define the display order for lookup attribute values in a drop-down on the UI that references masterdata. Users had to scroll through all the populated values to find the desired values during agreement creation. &nbsp;	+	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;
−	Configurators can now define and maintain the display sequence for selected masterdata records, starting from 1 to n, at the contract type level, using a seeded display sequence attribute. The values will thus be displayed at the top for easier and faster selection in lookup attributes. &nbsp;	+	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
−	This display sequence setting is supported on the create, edit, and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause entities, and template variables. The display will follow the default alphabetical order if the display sequence is not configured in masterdata.&nbsp;<br/> &nbsp;	+	&nbsp;
		+	<div class="image-green-border">[[File:RN 8.1 5.png|720px|RN 8.1 5.png]]</div>
		+	&nbsp;
−	<span style="color:#800080;">'''558605 – Viewing amendments in grid view on the agreement details page'''</span>	+	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
−	Previously in ICI, users could only view the agreement’s amendments in a “Tile” view, when opened from the left navigation pane on the agreement “Details” page.&nbsp;	+	&nbsp;
		+	<div class="image-green-border">[[File:RN 8.1 6.png|720px|RN 8.1 6.png]]</div>
		+	Feature ID: 1180864
−	ICI now allows users to view amendments in the “Grid” view, and toggle between grid view or tile view. The grid view is the default view for amendments and supports all existing grid functionalities, such as standard search, filter, column selection, pagination, export to CSV/Excel, and so on.<br/> &nbsp;	+	=== Administration & Configuration&nbsp; ===
−	<span style="color:#800080;">'''561410 – Enhancing the multi-select drop-down&nbsp;'''</span>	+	'''Quick Configuration with ICI Import Solution'''
−	The multi-select choice drop-down has been enhanced for better usability, data input, and post-selection data review of contract requests, agreements, amendments, and masterdata entities.&nbsp;	+	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.
−	Users can now:&nbsp;	+	Using the Import Solution tool, ICI users can now:
−	*View eight options in a drop-down list (instead of six), without scrolling.&nbsp;	+	*Import configurations from a source ICI instance to a target ICI Instance with no pre-existing configuration data.
−	*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&nbsp;	+	*Import configurations between different versions of ICI.
−	*View all selected values at the top of the drop-down.	+
−	*Deselect the selected values, individually or all with a single click, without opening the drop-down.<br/> &nbsp;	+
−	<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>	+	'''Note:''' Support will be provided for up to 2 releases preceding the target ICI version.
−	In ICI, the configurator can filter the lookup masterdata table with “Must” and “Must Not” conditions, to achieve necessary business scenarios, while configuring a lookup attribute on contract types.&nbsp;	+	*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
−	With this release, ICI provides the ability to configure a lookup attribute using the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup master data attribute.&nbsp;	+	Feature ID: 1262996&nbsp;
−	Configurators can now:&nbsp;	+	'''Contract Types can now be locked for editing&nbsp;'''
−	*Use the "IN” operator in the lookup filter attribute on agreement contract types.&nbsp;	+	Contract types can now be edited by only one user at a time. This functionality helps prevent data inconsistencies or concurrency errors.
−	*View the applied filter on the “Attributes” page on the UI for the selected attribute.&nbsp;	+
−	*Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute. &nbsp;<br/> &nbsp;	+
−	<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>	+	Product enhancements include:
−	Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;	+	*A Lock/Unlock button on the contract type page.&nbsp;
		+	*Auto system lock when users start edit a contract type without locking it.&nbsp;
		+	*Messaging providing information on who is editing the contract type.&nbsp;
		+	*System locks get released when contract types are saved.
−	ICI now provides administrators the capability to set preferences as default, for users, according to their locations or the offices they work in. This reduces the end user’s effort of setting up the ICI account with required parameters after the first log-in and presents the system with appropriate and specific pre-settings. &nbsp;&nbsp;	+	Feature ID: 1212463&nbsp;
−	Administrators can:&nbsp;	+	'''Enhancements to Legacy Upload Tool'''
−	*Set and manage preferences for a single user through a single user update, and for multiple users through the bulk process.	+	The following features will be added to the Legacy Upload utility with this release, improving speed and accuracy and reducing file size.
−	*View preference settings modifications details in the “History” tab for audit.&nbsp;	+
−	*Search users based on parameters related to preference settings.	+
−	Users can:&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+.
−	*Access the ICI system with appropriate details as default after the first login.&nbsp;	+	Feature ID: 1069763
−	*Override the default preference settings as per individual preferences.<br/> &nbsp;	+
−	<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading the document'''</span>	+	'''Unique clause and template code for every environment'''
−	Previously in ICI, users could not move agreements and amendments from “Waiting For Signature” to “Executed” state, without uploading the supporting document, in case of manually signed agreements.&nbsp;	+	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.
−	With this release, users can now skip uploading the document, to move agreements from “Waiting For External Signature” or “Waiting For Internal Signature” to the “Executed - (Pending Signed Document)” state.&nbsp;	+	Feature ID: 938126
−	Users can then search or create a saved search for such agreements and upload the required documents later using the “Upload Fully Signed Copy” action. Notifications can be configured to inform users about skipped document uploads, so that users can cover for delays occurring due to the scan and upload process while executing a large volume of documents.&nbsp;	+	'''Template and Clause creation options in Microsoft Word'''
−	This functionality is available for agreements, amendments, and orphan amendments.<br/> &nbsp;	+	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.
−	<span style="color:#800080;">'''614860 – Attaching associated documents to agreement notifications'''</span>	+	Feature ID: 1187041
−	ICI users can share the main agreement document as part of various email notifications that get triggered for the agreement from time to time.&nbsp;	+	'''Show or Hide confirmation messages in Microsoft Word&nbsp;'''
−	In addition to the main agreement document, users can now also send associated documents as part of various email notifications that get triggered for the agreement from time to time. Access to these documents can be controlled based on the type of document – internal, external, or restricted. For example, some documents may only be shared with internal users, some may be shared with internal and external users, whereas some may not be shared with anyone.	+	Administrators can now choose to show or hide certain confirmation messages, as per the organization's preference, on the Icertis Experience for Word.
−	With this release:	+	Feature ID: 1187044
−	*Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements, and amendments.	+	=== Technology Updates ===
−	*Users can define:	+
−	**The type of notification as internal or external.&nbsp;	+
−	**The type of associated document instance as internal, external, or restricted.	+
−	*Based on the type of notification and type of tagged associated documents, attachments are added to the email notification.<br/> &nbsp;	+
−	<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>	+	'''ServiceBus upgraded to Azure.Messaging.ServiceBus'''
−	ICI allows users to define the linkage type as a parent, child, or peer while associating peer entities with each other.	+	“Azure.Messaging.ServiceBus” is now replacing “Microsoft.ServiceBus”. &nbsp;<br/> <br/> This is a Microsoft recommended upgrade and provides the following improvements:
−	With this release, users can define configurable labels for peer associations between existing contracts by configuring the “Linkage Type” masterdata. The configurable labels define various business relationships in the context of contracts. For example, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on. The labels can be activated or deactivated as per business requirements.	+	*Up-to-date, streamlined Azure.
		+	*More accurate messaging without any anomaly or junk data in the message characters.
−	The configurable labels support the existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as a peer, with default peer linkage type label, defined in default peer mapping for amendment.&nbsp;	+	<br/> Feature ID: 940871
−	Users can select configurable peer linkage type labels in the “Linkage Type” drop-down list and view them on various ICI functionalities such as: &nbsp;	+	'''Authentication Library and Graph API update'''
−	*Agreement creation workflows for peer entities, assignment, and initiate termination flow.&nbsp;	+	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.
−	*Associate and Inheritance icons.	+
−	*Bulk actions.	+
−	*Agreement creation through business APIs.	+
−	*Broadcast – “Attachments” tab and captured notes.	+
−	'''Note:''' Multiple configurable labels are not supported for parent and child linkage types, as there is specific business logic built with them in the ICI system.	+	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;">'''619558 – Downloading amendments using download all functionality'''</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 users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements.&nbsp;	+	Feature ID: 1276938
−	With this release, users will download amendments of an agreement with corresponding parent-child associations in the downloaded zip package. This is supported on the selective download option too.	+	=== API Enhancements ===
−	For ease of access, each selected amendment will be downloaded with its selected associations in separate folders. The folders are named “Amendment_1”, “Amendment_2”, and so on (from oldest to latest), instead of actual amendment names. This helps to overcome the Windows limitation of supporting 260 characters in the file path and gives users the flexibility while creating association’s names.	+	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.
−	&nbsp;	+	Following APIs are upgraded to API 2.0 versions in this release:
−	<span style="color:#800080;">'''615291 – Configuring attributes inheritance for amendments at the contract type level'''</span>	+	[[File:RN 8.1 7.PNG|720px|RN 8.1 7.PNG]]
−	ICI already provided the capability to exclude specific agreement attributes from being copied to amendments through technical configuration, which applied to all agreement contract types by default.&nbsp;	+	[[File:RN 8.1 8.PNG|720px|RN 8.1 8.PNG]]
−	ICI now provides the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. Configurators can enable or disable the attribute’s inheritance for amendments, using the “Is Inherit On Amendments” flag, at the agreement contract type and template variable levels. Users can then copy these defined attribute values from base agreement to amendment during amendment creation.&nbsp;	+	[[File:RN 8.1 9.PNG|720px|RN 8.1 9.PNG]]
−	'''Note:&nbsp;'''	+	[[File:RN 8.1 10.PNG|720px|RN 8.1 10.PNG]]
−	*The technical configuration settings for excluding parent agreement attributes from its amendments will always take preference over the settings at agreement contract type and template level.	+	[[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]]
−	*The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.<br/> &nbsp;	+
−	<span style="color:#800080;">'''614877 – Replacing a user with multiple users'''</span>	+	[[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]]
−	In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees.&nbsp;	+	[[File:RN 8.1 15.PNG|720px|RN 8.1 15.PNG]]
−	Administrators can now:&nbsp;	+	[[File:RN 8.1 16.PNG|720px|RN 8.1 16.PNG]]
−	*Replace the user with one or more users, by selecting the entity and all/selective instances of that entity, and create a saved search for records to replace users. &nbsp;	+	[[File:RN 8.1 17.PNG|720px|RN 8.1 17.PNG]]
−	*Validate the replaced user role against the assigned role.&nbsp;	+
−	*Get a notification on adding or completing a task.&nbsp;<br/> &nbsp;	+
−	This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided to carry out these user management actions.	+	[[File:RN 8.1 18.PNG|720px|RN 8.1 18.PNG]]
−	&nbsp;	+	[[File:RN 8.1 19.PNG|720px|RN 8.1 19.PNG]]
−	<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</span>	+	[[File:RN 8.1 20.PNG|720px|RN 8.1 20.PNG]]
−	In ICI, users could supersede all attributes of a parent agreement configured as ‘supersedable’ with values from its amendment, either manually using the “Supersede” action or automatically through the auto-supersede task. Users can now selectively supersede individual entities based on business conditions.	+	[[File:RN 8.1 21.PNG|720px|RN 8.1 21.PNG]]
−	The administrator can control the supersede functionality for agreements by:	+	[[File:RN 8.1 22.PNG|720px|RN 8.1 22.PNG]]
−	*Enabling auto supersede option at the contract type level.	+	[[File:RN 8.1 23.PNG|720px|RN 8.1 23.PNG]]
−	*Configuring the “Supersede Rule” with “Is Supersede by Amendments” or “Is Supersede by Termination” options.&nbsp;	+
−	*Selecting attributes in rule actions based on the selected Supersede On option.&nbsp;	+
−	Users can view the attribute’s supersede value on the agreement and the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing ICI behavior.	+	[[File:RN 8.1 24.PNG|720px|RN 8.1 24.PNG]]
−	&nbsp;	+	[[File:RN 8.1 25.PNG|720px|RN 8.1 25.PNG]]
−	<span style="color:#800080;">'''615293 – Showing or hiding the No Team Available message'''</span>	+	[[File:RN 8.1 26.PNG|720px|RN 8.1 26.PNG]]
−	In ICI, users may encounter specific workflow configurations, such as the self-approval process, that do not require users added to the team. The “No Team Available” message, displayed in such cases, adds to the number of non-value clicks for users to continue.&nbsp;	+	[[File:RN 8.1 27.PNG|720px|RN 8.1 27.PNG]]
−	ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks.&nbsp;	+	[[File:RN 8.1 28.PNG|720px|RN 8.1 28.PNG]]
−	Administrators can:&nbsp;	+	'''API Deprecations'''
−	*Selectively enable or disable the “No Team Available” message window, at the entity contract type level, appearing at various states.&nbsp;	+	Any integrations utilizing the deprecated APIs must adopt alternate APIs. Previously, API endpoints have been periodically deprecated and alternate APIs have been provisioned.
−	*Disable the “No Team Available” message window altogether, at the instance level, for all entities. The instance level settings will override the entity level settings.&nbsp;	+
−	'''Note:''' This capability is available across ICI for all entities, events, integrations and add-ins in ICI.	+	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.
−	&nbsp;	+	=== Mobile App Update&nbsp; ===
−	<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>	+	'''Improved Security on Mobile Devices with SafetyNet Attestation API'''
−	Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator.&nbsp;	+	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.
−	With this release, configurators can now set multiple, complex conditions to display ICI Web UI attributes dynamically, based on business scenarios. Configurators can define conditions for attributes for all entities, except for template variables. For example, the configurator can set conditions to display an attribute based on the selection of specific values in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality. &nbsp;	+	'''Note: '''The SafetyNet Attestation API is supported Android version 8.0 onwards.
−	Users can now:&nbsp;	+	Feature ID: 1095223
−	*Apply multiple and complex conditions to display an attribute by enhancing the enable expression (visibility expression) for contract requests, agreements, associations, and masterdata contract types.&nbsp;	+	== AI Applications&nbsp; ==
−	*Support conditional expressions for extension attributes. &nbsp;	+
−	*Define conditions with different operators based on the selected attribute datatype.&nbsp;	+
−	*View the conditional attribute value according to the value entered in the attribute on which a condition is set.	+
−	&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;">'''616901 – Applying facets to business status search filter'''</span>	+	The additional attributes are:
−	Business statuses are prominently used across all customers as they reflect the actual status in business terms compared to the system workflow status. Previously, the ICI search functionality supported filters on “Business Status” for users to narrow down results. However, manually selecting filters often becomes a tedious task in the case of several business statuses.&nbsp;	+	*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 provide a better user experience and ease of use, faceted filters using string operators, such as “Contains”, “Exactly”, “Starts With” and “Does Not Contain” are being added to the “Business Status” filters.<br/> &nbsp;	+	Feature ID: 1187824
−	<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>	+	=== Enhancing the scope of DiscoverAI app& Negotiate AI differentiation ===
−	Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&nbsp;	+	Discover AI helps users to identify attributes and clauses in browser and save them in the system.
−	ICI's parsing logic is now improved for handling string combinations with special and alphanumeric characters so that no errors are generated. This applies to all entities across ICI, where a combination of special characters, alphabets, and numbers can be used.<br/> &nbsp;	+	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;
−	<span style="color:#800080;">'''732929 – Uploading clauses and templates in bulk'''</span>	+	*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;
−	New customers or new groups onboarding to ICI mostly have their templates and clauses already created in a separate file. Previously, manual efforts were needed to onboard the hundreds to thousands of templates and clauses.&nbsp;	+	Feature ID: 1284012
−	With this release, automation has been provided for bulk import using the “Legacy Upload” tool, which will reduce any human dependency, manual approvals, and delays for onboarding templates and clauses using the current capabilities. ICI administrators can now import templates and upload clauses to ICI in bulk.	+	== Reports Enhancements ==
−	Along with the tool, an XML specification document is also released which can be used for creating tags in the input document files of clauses and templates.<br/> &nbsp;	+	=== Data for agreements awaiting signature in reports ===
−	<span style="color:#800080;">'''655507 – Uploading and downloading large files with the file path attribute'''</span>	+	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.
−	ICI now provides support for larger files. This is applicable to masterdata and associations.	+	This enhancement applies to the following reports:
−	Users can now:	+	[[File:RN 8.1 29.PNG|520px|RN 8.1 29.PNG]]
−	*Upload files up to 4GB under the file selection attribute.&nbsp;	+	Feature ID: 1071182
−	*Upload files with all supported file extensions allowed in the file selection attribute.	+
−	*Download All/Download Package up to 6 GB.	+
−	ICI supports virus scanning of large files if the virus scan feature is enabled.<br/> &nbsp;	+	=== Custom reporting views using JSON&nbsp; ===
−	'''Note:&nbsp;'''This is not applicable for contract requests, agreements, associations with large files in the DocuSign/Adobe Sign association selection pop-up, document assembly, bulk actions, legacy upload, integrations (Salesforce, Workday, etc.), and APIs.&nbsp;The Upload/Download of the files would be supported for Azure and Windows Storage.	+	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.
−	&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.
−	<span style="color:#800080;">'''618994 – Supporting special characters in agreement templates and support to skip empty columns while a saved search/association is tagged in a template'''</span>	+	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.
−	Previously in ICI, attribute names did not support special characters apart from _ (underscore), & (ampersand), and space.&nbsp;	+	Feature ID: 1208472
−	Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash), : (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (period) can be used in the display name of attributes for contract requests, agreements, associations, and masterdata contract types. The same attribute display name, as provided by the configurator, will now be displayed including special characters.	+	=== Dataset and seeded dashboard for Proposal Management application ===
−	In scenarios where the association or saved search is tagged as a table in the agreement, and a particular column of the table does not have any data, we have introduced a functionality to skip such empty columns.&nbsp;	+	A dedicated Power BI Dataset is now available for the Proposal Management application for out-of-the-box and custom reporting.&nbsp;&nbsp;
−	During template creation from Icertis Experience for Word, the configurator can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table. This property needs to be added manually in the “Content Control Properties”, at any position after the contract type GUID, separated by a '|' (pipe separator). This enables empty columns to be skipped in document assembly, thereby eliminating unnecessary empty columns in the agreement version. The order of the columns in the table is determined by the attributes in the display preference of the associated document contract type.&nbsp;	+	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.
−	Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export.&nbsp;<br/> &nbsp;	+	Feature ID: 1232650
−	<span style="color:#800080;">'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''</span>	+	=== Attribute Information Report Enhancements ===
−	With this release, ICI provides new controls for multi-select and single-select choice attributes.&nbsp;	+	The following filters and columns are added to the Attribute Information report giving more options to analyse the Attributes used in the system.
−	Users can configure an alternate UI control for drop-downs with a limited number of values for choice attributes at contract type, global attribute, and template variable levels. This improves the user experience as the number of clicks and scrolls required to view options in a drop-down are considerably reduced and provides better readability in terms of post-selection data review. &nbsp;&nbsp;	+	*Filters: Contract Type, and Group by Property Columns: Is Mandatory and Tracking Attribute
−	Users can select:&nbsp;	+	Feature ID: 1158976
−	*The radio button for single-select choice attributes.&nbsp;	+	=== Edit SSRS Reports without customization ===
−	*The checkbox list for multi-select choice attributes.	+
−	The configuration applies across ICI for the creation and editing of agreement, amendment, associated document, masterdata, and contract request entities.	+	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:
−	&nbsp;	+	*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.
−	<span style="color:#4B0082;">'''593421 – Labeling agreement document versions as per signature copy'''</span>	+	Feature ID: 744814
−	While agreements go through various signature states till executed, users can now navigate to the “Versions” tab and easily identify which version of the agreement is internally signed, externally signed, or fully signed.	+	=== Report-based edit access for Power BI reports ===
−	&nbsp;	+	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
−	<span style="color:#800080;">'''872309 – Providing flexibility for assembling associations tagged as clauses'''</span>	+	=== Maintainance and storage optimization with a Common Data Model for Clause-based reports ===
−	In ICI, on publishing and updating actions, all clauses are evaluated, assembled and changes are reflected in the agreement document. However, if associations are tagged in clauses, on “Assemble Contract” and “Send For Approval” actions, clauses do not get assembled and associations do not get populated in the agreement document.	+	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
−	As part of our continuous effort to provide flexibility to ICI users and improve the user experience, a key “Core.Agreement.EnableDynamicClauseAssemblyPostCreate” has been introduced.&nbsp;	+	=== SSRS Reports now available with Power BI ===
−	*If the key is enabled, when an associated document is uploaded, the entire document will be automatically assembled (Clause, Attribute, Associations, Saved Search) on the “Assemble Contract” and “Send For Approval” actions.	+	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:
−	*If the key is not enabled, the ICI document will be assembled on “Publish” and “Edit Agreement” actions. Only associations will be assembled on the “Assemble Contract” and “Send For Approval” actions.	+
−	'''Note: '''By default, the key is set to false.<br/> &nbsp;	+	*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;
−	== Mobile App Updates ==	+	Feature IDs: 1214787, 1214720, 1223598<br/> &nbsp;
−	<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span><br/> Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.	+	== Salesforce Integration&nbsp; ==
−	&nbsp;	+	=== &nbsp;Activity Object and Trigger Simplification in Salesforce Adapter ===
−	<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.	+	The following enhancements are made to the SFDC Manage package Adapter:
−	&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.
−	<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.	+	'''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.
−	&nbsp;	+	Feature ID: 1066353
−	<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.	+	=== User Experience for Salesforce Revamped ===
−	&nbsp;	+	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 API Enhancements&nbsp; ==	+	These are the enhancements that have been introduced:
−	<div class="image-green-border">	+
−	<span style="color:#800080;">'''704069 – Enhancing ICI API 2.0 implementation'''</span>	+
−	With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&nbsp;	+	*&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 is applicable for visualize, retrieval, creation and updation of the instances of the following entities:	+	'''Note:''' The implementation team will provide a list of native and i-frame components.
−	*Contract Requests	+	Feature ID: 1186642
−	*Agreements	+
−	*Associations	+
−	*Amendments	+
−	New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.	+	== eSign Integration&nbsp; ==
−	&nbsp;	+	=== Integration Support for DocuSign using JWT authentication ===
−	<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>	+	The ICI and DocuSign integration was previously based on authenticating the APIs with “IntegratorKey” and “API Password”.
−	ICI already supports downloading agreements.	+	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.
−	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.	+	Feature ID: 1000798
−	&nbsp;	+	=== DocuSign API upgraded from 2.0 to 2.1 ===
−	<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>	+	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.
−	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.	+	Feature ID: 1060689
−	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.	+	=== Adapting webhook feature of Adobe Sign ===
−	<br/>  <br/> <span style="color:#800080;">'''660859 – Supporting correlation Id in APIs'''</span>	+	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.
−	To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;	+	Adobe webhooks can be created on the workflow for each agreement, requesting the type of information in the callback, which further benefits as follows:
−	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;	+	*Identifying the signatory requesting a callback
		+	*Identifying for which event or action the callback is requested
		+	*Concisely updating the status in ICM
−	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;	+	'''Note:'''&nbsp; Upgrade Adobe Sign API from 5.0 to 6.0 to use the webhook feature.
−	The following API changes have been made to ensure that the existing implementation and code do not break:	+	Also, Adobe rebranded Echo sign to Adobe Sign, hence non overridden localization strings for validation messages have been modified accordingly.
−	*Provided support for a Tracking Id header in every request for logging.&nbsp;	+	Feature ID: 1091947
−	*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.	+	=== Electronic Signature support using ICI BioPharma setting for 21 CFR Part 11 & Annex 11 compliant groups ===
−	This can be used for:	+	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.
−	*Related API Calls	+	This feature allows integration with DocuSign Part 11 module and Adobe Sign Bio-Pharma setting to get electronically signed approvals for such agreements.
−	*Async operations	+
−	*Bulk operations	+
−	*Status check operations &nbsp; &nbsp;	+
−	</div>	+
−	&nbsp;	+
−	== Enhancements to ICI Add-ins&nbsp; ==	+	Feature ID: 1220095
−	<span style="color:#800080;">'''745266 – Supporting online editing of agreements'''</span>	+	=== Changes in IP whitelisting process for eSign adapters ===
−	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;	+	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 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.	+	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.
−	With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.	+	'''Note''': Blocking or allowing IP addresses based on DNS is not supported as a part of this feature.
−	It is now possible for:	+	Feature ID: 1193062
−	*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;	+	=== Update eSign document with correct status ===
−	*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information.	+
−	'''Note:&nbsp;'''	+	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.
−	*The online Word editor is available only for users with valid Office 365 subscription.	+	Feature ID: 1193061
−	*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>	+	== Sourcing&nbsp; ==
−	ICI allows users to capture additional details for clauses in the extended attributes.&nbsp;	+	The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (SRC8.1.0.404).
−	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.	+	=== Support for new RFx type-RFP ===
−	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.	+	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.
−	&nbsp;	+	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.
−	<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>	+	Key RFP features:
−	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.	+	*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.
−	Users can now:	+	Feature ID: 404602
−	*Search and filter clauses and templates based on the name or text inside the clause or template respectively.	+	=== Improved Sourcing workflow with Sourcing Request ===
−	*Perform free text search on clauses and templates.	+
−	&nbsp;	+	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.
−	<span style="color:#800080;">'''603690 – Updating templates automatically with latest clause version'''</span>	+	Sourcing Request features:
−	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.	+	*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.
−	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: 611297
−	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.	+	=== Ordering and additional data types for Questions in Questionnaire ===
−	<br/>  <br/> <span style="color:#800080;">'''593421 – Labeling agreement document versions as per signature copy'''</span>	+	We have made the following enhancements to Icertis Sourcing to improve the user experience when working with Questions and Questionnaires:
−	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.	+	The order of Questions and questionnaires in RFx can be set and modified as per the preference of users.
−	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 data types are now supported for questions in RFx:
−	&nbsp;	+	*Boolean
		+	*String
		+	*Choice
		+	*Multi Choice
		+	*Currency
		+	*DateTime
		+	*Number
		+	*Percentage
		+	*Text Area
		+	*Rich Text Area&nbsp;&nbsp;
		+	*Email
		+	*File Selection
−	&nbsp;	+	'''Note''':
−	== Enhancements to Artificial Intelligence Applications in ICI ==	+	*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.
−	<span style="color:#800080;">'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''</span>	+	Feature ID: 896873
−	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;	+	== Obligation Management&nbsp; ==
−	With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&nbsp;	+	The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application (OM8.1.0.404).
−	Users can now:&nbsp;	+	=== An interface to quickly add obligations discovered by AI ===
−	*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &nbsp;	+	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.
−	*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;	+	The interface to review and create obligations in bulk saves users much time and manual effort.
−	<span style="color:#800080;">'''575475 – Automating user feedback for clauses, obligations and attributes'''</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.
−	ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery recommends values to users, it is expected that users would select the correct value at the time of review. &nbsp;	+	Feature ID: 1090383
−	During clause review of discovered clause, AI suggests a list of library clauses to be matched with the discovered clause. If a user selects one of them or selects a completely new clause from library, the AI algorithm learns from such user actions. These learnings are incorporated in the next discoveries to improve the accuracy of clause recommendations.	+	=== Auto-approval of Obligations to improve efficiency ===
−	<br/> <span style="color:#800080;">'''539492 – Improving clause delineation in DiscoverAI'''</span>	+	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.
−	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;	+	Once the auto-approval process is defined based on obligation taxonomy, this is how the feature works:
−	ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&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.
−	Users can now:&nbsp;	+	Feature ID: 519344
−	*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&nbsp;	+	=== Organize and manage obligations by creating groups&nbsp; ===
−	*Create a sub-clause within a discovered clause.&nbsp;	+
−	*Change the clause category and the level (parent or child) of the discovered clause. &nbsp;	+
−	*Choose to view only the level 0 clauses.	+
−	&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.
−	<span style="color:#800080;">'''770375 – Merging metadata discovery page with attribute page'''</span>	+	Users can now categorize different obligations under logical groups and create parent-child relationships between obligations.
−	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;	+	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.
−	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: 649768
−	Users can:&nbsp;	+	=== Duplicate obligations no longer inherited&nbsp; ===
−	*View the discovery completion progress.&nbsp;	+	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.
−	*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.	+	Feature ID: 1040723
−	&nbsp;	+	=== UI Improvements for Obligation Management ===
−	<span style="color:#800080;">'''727312 – Formatting based clause delineation for additional document types'''</span>	+	The following improvements are made in the product to improve the search and usability experience when using Obligation Management:
−	In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.	+	*Dedicated index pages for Obligations and Fulfillments,
		+	*Relevant page titles, breadcrumbs and history page information.
−	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.	+	Feature ID: 1236413
−	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.	+	== Risk Management ==
−	&nbsp;	+	The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (RM8.1.0.404).
−	<span style="color:#800080;">'''727314 – Supporting additional languages in AI apps'''</span>	+	=== UI Improvements for Risk Management&nbsp; ===
−	In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.	+	The following Improvements are made in the product to improve the search and usability experience when using Risk Management:&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.	+	*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:
−	'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.	+	*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.
−	&nbsp;	+	Feature ID: 1067718
−	<span style="color:#800080;">'''710739 – Configuring custom rules in DiscoverAI'''</span>	+	== Proposal Management&nbsp; ==
−	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;	+	ICI Proposal Management application is certified to work with the 8.1 release (PM8.1.0.404).&nbsp;
−	With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&nbsp;	+	=== Track and analyse performance with a Power BI Dashboard ===
−	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;	+	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:
−	&nbsp;	+	*A new Power BI data model with Power BI dataset specific to Proposal Management.
−		+	*Proposal Management KPIs report
−	== Enhancements to Reports ==	+	*Capture Management report
−		+
−	<span style="color:#800080;">'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''</span>	+
−		+
−	With this release, a new “Tagged Attributes Report”, which helps administrators understand the complete profile of an attribute and how it has been tagged across different clauses and templates. This provides them better visibility into attribute usage and saves them considerable time.	+
−		+
−	This report, available on the “Reports” tile, can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable, Attribute tagged as Clause Extended Attribute and Attribute Display Name	+
		+	'''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;
−	<span style="color:#800080;">'''769602 – Displaying clause extension attribute summary in the Clause Summary Report'''</span>	+	=== Enhancements to Seeded Contract Types ===
−	Previously, the “Clause Summary Report” displayed “Clause Summary” and “Clause Version Summary” sections on the report index page.	+	With this release, the PM App is being enhanced with newly seeded attributes to its seeded contract types.
−	In this release, the report is being enhanced to display “Clause Extension Summary” which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information of the clause extension attributes. The “Clause Extension Version Summary” will display the latest values of clause extension attributes.	+	In this enhancement:
−	<br/>  <br/> <span style="color:#800080;">'''514611 – Enhancing Notifications History Report for an entity'''</span>	+	*New attributes have been seeded with the Bid Proposal entity:
		+	*Total Bid Value For Proposal
		+	*Total Value Won Or Lost
		+	*Customer Address
		+	*Customer Geography
−	ICI administrators can set up subscriptions for different entities, for notifications to be sent to subscribed users at the occurrence of certain events. Notifications can also be sent using the broadcast functionality. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity.&nbsp;	+	These new attributes contribute in the essential computations of the Win Ratio and the Value Capture Ratio.
−	The default report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities. This report displays a list of notifications sent for an entity, including details such as the event that triggered the notification, the message body, subject, the To, CC, BCC recipient names and email addresses; along with other details such as the attachment file names or sent date and time.&nbsp;	+	Feature ID: 1186830
−	&nbsp;	+	=== Revamped User Experience across the PM App ===
−	<span style="color:#800080;">'''742607 – Providing additional localization support in reports'''</span>	+	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).
−	With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&nbsp;	+	The following summarizes the revamped user experience across the App:
−	*Contract type names, if the respective entity has locale resource key values in database.&nbsp;	+	*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.
−	*Drop-down with Yes/No values.	+	*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.
−	*Graph and Time zone tool tips, if present in the report.	+	*The seeded entities now have their dedicated index pages, as opposed to the saved search driven listing in previous releases.
−	*Column headers. &nbsp;	+	*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”.
−	*Any error or validation messages.	+	*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.
−	*Informative messages such as “No data available”.&nbsp;	+	*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.
−	<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span>	+	Feature ID: 1235186
−	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;	+	== Supplier Relationship Management Application&nbsp; ==
−	This filter is now also available for the "Agreement Deviation Report" and "Agreements Pending Execution Report". Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.	+	ICI Proposal Management application is certified to work with the 8.1 release (SRM8.1.0.404).
−	&nbsp;	+	=== Supplier Evaluation ===
−	<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>	+	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.
−	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;	+	'''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.
−	With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.	+	'''How Supplier Evaluation fits within Supplier Relationship Management'''
	&nbsp;		&nbsp;
−	<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>	+	Supplier Evaluation module is part of the Supplier Relationship Management application, which is built on Icertis Contract Intelligence.
−	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;	+	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.
−	== Integrations ==	+	A routine supplier evaluation can help organizations set expectations from their preferred suppliers and manage low performing suppliers.&nbsp;&nbsp;
−	<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>	+	'''Supplier Evaluation Features'''
−	ICI has now improved the electronic signature process to provide a unified flexible signature workflow.	+	Setting up Supplier Evaluation
−	With this release, the following capabilities have been added to the ICI signature process:	+	*'''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.
−	*Introducing the hybrid signature process.	+	Feature ID: 463049
−	*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;	+	=== Managing Supplier Hierarchy ===
−	<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>	+	'''Manage Related Supplier Organizations'''
−	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.	+	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.
−	With this release:	+	You can designate a supplier organization as one of the following types:
−	*Users can define the parallel signatories using rules.	+	*'''Supplier''': Supplier organizations that may or may not have related Parent or Holding companies.
−	*Users can configure parallel signatories via the DocuSign console.	+	*'''Parent company''': Parent company of one or more Supplier organizations, controls operations of the Supplier Organization
−	*DocuSign process can be triggered in parallel for the configured signatories.	+	*'''Holding company''': Holding company of one or more subsidiary Supplier organizations, does not have a direct say over the operations of subsidiaries.
−	*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>	+	Changes made to the supplier hierarchy for supplier registration, qualification or profile are synchronized with the vendor database and supplier master.
−	Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&nbsp;	+	'''Unique Supplier Record Management'''
−	With this release, users can:	+	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.
−	*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.	+	If the attributes are changed for an organization, the system validates and checks for duplicate records before allowing users to make the change.
−	*Define standard rules and conditions to automatically select the provider for agreements and amendments.	+
−	'''Note: '''This is applicable to DocuSign and Adobe Sign.	+	'''Validating the Duplicate Registrations'''
−	&nbsp;	+	Buyers may receive more than one registration from the same supplier submitted through the web page.
−	<span style="color:#800080;">'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''</span>	+	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.
−	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.	+	'''Note''': Customers upgrading to 8.1 from previous versions of ICI Supplier Relationship Management is supported.
−	With this release:	+	Feature ID: 1271423
−	*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”.	+	== Technical Requirements&nbsp; ==
−	*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 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.
−	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 software and hardware requirements for the client system as well as the mobile application are listed in the table below:
−	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.	+	[[File:RN 8.1 43.PNG|720px|RN 8.1 43.PNG]]
−	With this release:	+	[[File:RN 8.1 44.PNG|720px|RN 8.1 44.PNG]]
−	*Changes made to agreements in Salesforce while they are in Send for External Signature, Send for Internal Signature, Executed or Expired statuses will not be updated to the ICI UI.&nbsp;	+	[[File:RN 8.1 45.PNG|720px|RN 8.1 45.PNG]]
−	*When attributes are not tagged in the template document and the same attribute is mapped with Salesforce, updating the value of that field in Salesforce will change the status of the agreement from "Waiting for Approval" or "Approved" to "Draft"; unless it is a tracking attribute.&nbsp;	+
−	This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.	+	'''Important Changes in IE11 Support:'''
−	&nbsp;	+	From March 2021, Microsoft has stopped its technical support to Internet Explorer (IE) and has advised its customers to move to Microsoft Edge.
−	<span style="color:#800080;">'''674469 – Sending success or failures alerts for monitoring in Salesforce'''</span>	+	ICI will no longer support IE11. ICI will not be certified over IE11.
−	An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&nbsp;	+	If customers use IE 11 then the below message will be displayed:
−	With this release:	+	“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.”
−	*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&nbsp;	+	[[File:RN 8.1 46.PNG|720px|RN 8.1 46.PNG]]&nbsp;
−	*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>	+	[[File:RN 8.1 47.PNG|720px|RN 8.1 47.PNG]]
−	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;	+	[[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]]
−	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.	+	[[File:RN 8.1 51.PNG|720px|RN 8.1 51.PNG]]
−	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;	+	== Accessibility Conformance&nbsp; ==
−	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.	+	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.
−	&nbsp;	+	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:
−	<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>	+	*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
−	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;	+	== Known Issues ==
−	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;	+	This section includes some issues that we are aware of and plan to resolve at the earliest:
−	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.	+	[[File:RN 8.1 52.PNG|720px|RN 8.1 52.PNG]]
−		+
−	&nbsp;	+
−		+
−	== ICI Platform Tools ==	+
−		+
−	'''<span style="color:#800080;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''	+
−		+
−	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:	+
−		+
−	*Organizations (Orgs), Organization Groups (Org Groups)	+
−	*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.	+
−		+
−	&nbsp;	+
−		+
−	== Partner Enablement ==	+
−		+
−	<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>	+
−		+
−	Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&nbsp;	+
−		+
−	As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:	+
−		+
−	*ICI Coding Guidelines (version 2):&nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.	+
−		+
−	*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript.	+
−		+
−	*Working with ICI Tasks: Updated for the 7.15 release.	+
−		+
−	*Working with ICI Hooks:'''&nbsp;'''Updated for the 7.15 release.	+
−		+
−	*ICI Developer Library: Updated for the 7.15 release.	+
−		+
−	*Local Environment Setup using ICI Binaries: Updated for the 7.15 release.	+
−		+
−	*Self-Serve Tools:'''&nbsp;'''Updated for the 7.15 release.	+
−		+
−	&nbsp;	+
−		+
−	== Technical Requirements for Release 7.15 ==	+
−		+
−	The Icertis Contract Intelligence 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.	+
−		+
−	[[File:7.15 Technical Requirements - Operating Systems.PNG|720px|7.15 Technical Requirements - Operating Systems]]	+
−		+
−	[[File:7.15 Technical Requirements - Browser Compatability Matrix.PNG|720px|7.15 Technical Requirements - Browser Compatibility Matrix]]	+
−		+
−	[[File:7.15 Technical Requirements - Other Requirements.PNG|720px|7.15 Technical Requirements - Other Requirements]]	+
−		+
−	[[File:7.15 Technical Requirements - Smartphone Mobile App.PNG|720px|7.15 Technical Requirements - Smartphone Mobile App]]	+
−		+
−	[[File:7.15 Technical Requirements - Special Requirements 1.PNG|720px|7.15 Technical Requirements - Special Requirements 1]]	+
−		+
−	[[File:7.15 Technical Requirements - Special Requirements 2.PNG|720px|7.15 Technical Requirements - Special Requirements 2]]	+
−		+
−	[[File:7.15 Technical Requirements - Special Requirements 3.PNG|720px|7.15 Technical Requirements - Special Requirements 3]]	+
−		+
−	[[File:7.15 Technical Requirements - MS Office Plugins 1.PNG|720px|7.15 Technical Requirements - MS Office Plugins 1]]	+
−		+
−	[[File:7.15 Technical Requirements - MS Office Plugins 2.PNG|720px|7.15 Technical Requirements - MS Office Plugins 2]]	+
−		+
−	[[File:7.15 Technical Requirements - Security.PNG|720px|7.15 Technical Requirements - Security]]	+
−		+
−	&nbsp;	+
	&nbsp;		&nbsp;
Line 918:		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

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.

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

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.

 

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

 

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

 

 

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

 

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:

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:

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:

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.   

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.

 

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

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:

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

 

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:

 

 

 

 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