Revision as of 07:07, 6 September 2019 (view source) IDT-1 (Talk | contribs) ← Older edit		Latest revision as of 13:10, 29 September 2022 (view source) IDT-1 (Talk | contribs)
(325 intermediate revisions by 8 users not shown)
Line 1:		Line 1:
−	= ICM Release Notes - Release 7.9 =	+	= ICI Release Notes - Release 8.2 =
−	== Overview of Release 7.9 ==	+	Apart from new features and enhancements, this document contains information on:
−	The 7.9 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience and intuitiveness by continually improving ICM functionalities and user interface.	+	*[[#_Technical_Requirements_1|Technical Requirements]]
		+	*[[#_Accessibility_Conformance|Accessibility Conformance]]
		+	*[[#_Known_Issues|Known Issues]]
−	The key enhancements of this release include:	+	Refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.2/index.php?title=ICI_Help Wiki] documentation (also found in your ICI help section) for details on all ICI features and functionalities.
−	*Enhancements in AI applications such as providing the Agreement/Clause Similarity functions and some UX improvements in the Negotiate AI app, supporting Obligation discovery on Templates and incorporating user actions feedback in the Obligation AI app, adding support for implementation of custom visualization in the Visualize AI app, and adding support for Table discovery in the Discover AI app.	+	= New Features and Enhancements =
−	*Improving the ICM infrastructure to determine the Application Type (Contracting, Sourcing, Proposal, Obligation Management, and Supplier Lifecycle Management) when creating a Contract Type.	+
−	*Allowing multiple stakeholders to collaborate within ICM itself in context of Contract, thus eliminating the need for using external tools such as Email, Skype, etc.	+
−	*Enhancing Search filters to include Team roles. The search capabilities have been further improved to allow searching of Agreements and Associated documents based on Clause usage, so that users can tackle the high risk Agreements first and mitigate risks.	+
−	*Improving usability by allowing the comparison of any two versions of the Agreement document, and displaying a banner for an announcement or scheduled event.	+
−	*Introducing the bulk import tool to import Templates/Clauses in bulk along with tagging and rules, enhancing bulk upload capability to create an assignment or initiate termination, provision users, and add team members when creating or updating an Agreement/Amendment.	+
−	*Introducing the ability to tag the same Masterdata localized Attribute multiple times to support bilingual Templates within ICM.	+
−	*Improving the ability to create Rules by introducing new conditions such as ''Has A Value'' and supporting Power Set conditions for multi-select data 	+
−	*Extending support to Template Variables to be able to track the dependency between the Contract Type Attributes and Template Variables.	+
−	*Improving Power Business Intelligence (BI) usability by displaying the Power BI Dashboard on the Advanced Analytics tile and making some UX related changes to improve user experience.	+
−	*Refining Reports to display the Date and Time as per user preferences in addition to more reports now being available on the Dashboard as KPIs.	+
−	*Improving the Icertis Experience by:	+
−	**Introducing a new .JS version of the ICM Outlook Plugin to be able to upload the next version of the Agreement Document and Associated Document, or creating a new Association instance and the uploading the Associated Document received over Email to the Agreement, thus reducing the overall turnaround time for the author.	+
−	**Introducing a new field for Salesforce users named ''Field Set Name'' so that the Adapter reads the metadata and sends only the Attributes defined for the entity when the integration is triggered from Salesforce. It also allows using Attributes defined at the Template level to store critical data as part of the Agreement and sync with Salesforce, thus avoiding data duplication and redundancy in the process.	+
−	**Collaborating with Microsoft Team to provide a seamless user experience when authoring contracts, negotiations, or when discussing ideas and exchanging files, and in turn significantly improving the cycle time.	+
−	**Configuring the ICM Workday Adapter so that Executed Agreements can be attached as .PDF, instead of .docx.	+
−	**Providing the capability to upload a manually signed copy of an Agreement document using the ''Print, sign and upload'' capability of Adobe Sign, and supporting redlining in Associations tagged as a Table in a Template or Agreement document, in addition to allowing the user to send supporting documents along with the main Agreement for signature when using Adobe Sign.	+
−	<div class="note-box">'''Note: '''The ICM-Coupa integration adapter that supported exchange of data between ICM and Coupa Spend Management platform is no longer supported.</div>	+
−	These Release Notes provide an overview of enhancements to ICM and the ICM Experience for Integrations. Refer to the detailed Wiki documentation for explanation and capabilities of these and all other ICM features and functionalities.	+
−	== ICM Application Enhancements ==	+	== Contract Authoring & Management&nbsp; ==
−	<span style="color:#008000;">'''420230 – Extend Contract Type definition to be able to describe the Application Type &nbsp;'''</span><br/> ICM offers the ability to determine the Application type (Contracting, Sourcing, Proposal, Obligation Management, and Supplier Lifecycle Management) when creating a contract type. This is possible with the inclusion of two new choice type attributes, Business Application Type and Business Application Category at the contract type level. This feature helps effortlessly drive business applications on the ICM platform. These attributes are applicable for agreements and associated document contract types, after the business application is enabled through a technical configuration. The access privileges for business applications such as Sourcing, are driven through Security Groups.
−	<div class="image-green-border"><span style="color:#008000;">'''390639 – Collaboration in Contracts &nbsp;'''</span>
−	Previously, stakeholders involved in the contracting/sourcing process used to communicate via external tools such as Email, Skype, etc. Managing these conversations that involved multiple stakeholders and multiple discussions was a cumbersome task. With this release, ICM has eliminated the need to use external tools and created a dedicated space available within the agreement itself.&nbsp;<br/> To collaborate, multiple stakeholders involved in the contracting/sourcing process can:
−	</div>
−	*Use the ''Collaboration'' tab available inside the agreement&nbsp;
−	*Provision an internal/external team member to communicate with other internal or external team member(s) by creating topics and posting messages in it
−	*Provision users to send and receive attachments along with the message
−	*Provision users to mark the topic as closed once the discussion is concluded
−	*Send Email notifications to participants when messages are posted in the topic
−	<div class="image-green-border">
−	This can be achieved by setting the Enable Collaboration flag to Yes for the agreement contract type, which displays a Collaboration tab on the agreement Details page. To prevent data loss, once Collaboration is enabled for a contract type, it cannot be disabled.
−	</div> <div class="image-green-border">'''<span style="color:#008000;">400058 – Searching entities using nested filters</span>'''&nbsp;</div> <div class="image-green-border">With this release, ICM now supports the ability to apply nested filters to search entities. This allows users to derive out-of-the-box saved search KPIs that help them manage agreements and amendments easily. For example, you can search for all agreements where John Doe is present in the agreement as the deviation approver by nesting of filters.<br/> You can search and filter agreements based on any user roles using the following Categories – Team Member: Role Name, Is Group, Role Display Name, and User Name.</div> <div class="image-green-border">
−	<span style="color:#008000;">'''452265 – Ability to compare any 2 versions of the Agreement&nbsp;document'''</span>
−	Previously, users could only see the comparison between the last and the current version of the agreement document version. This functionality has now been enhanced and is accomplished through the Compare Documents icon on the agreement Details page, so that the user can compare any two of the available versions of the agreement as required.	+	=== Amend contracts preserving previously negotiated terms ===
−	<span style="color:#FF0000;">Note:</span> The agreement document version comparison always takes place between a higher version on the right panel and a lower version on the left panel.	+	'''What''' – When users amend a contract, they now have a choice to either use the base agreement or a previously negotiated and amended contract. Along with the contract version, users can also choose the associations to copy to the amendment.
−	<span style="color:#008000;">'''384321 – Ability to compare ''Associations tagged as a Table'' across versions'''</span>	+	'''Advantages''' – Maintaining a history of the original agreement and all amendments is now possible. This helps in auditing the changes made to contracts over time.
−	When a user uploads a new version of the document, ICM provides the ability to compare the changes in clause language or the attributes. Version-wise changed history is also stored in the Versions section on the Details page.&nbsp;<br/> With this release, modifications made to associations or saved search that were tagged as a table in a template (such as adding or removing rows/columns or changing the values in individual cells) will be visible at the time of upload as well as on the Versions tab of the agreement document. This will allow the contract negotiator to make informed decisions accordingly. ICM Scribe has also been enhanced to support this capability, but provides limited information.	+	'''How''' – Options to choose the amendment and copy associations to the amendment are now available when creating an amendment. Users can associate and inherit documents such as NDA, SOW, etc.
−	<span style="color:#FF0000;">Note: </span>Deviation tracking and syncing back of the changed table data to the respective association instances is not supported. Table comparison is only shown when cell values get changed, not when empty cells get added or removed.	+	'''Value''': Compliance | User Experience<br/> '''For''': Legal Team | Authors | Contract Managers<br/> '''Feature ID''': 1233193
−	'''<span style="color:#008000;">408652 – Displaying an Announcement Banner</span>'''	+	=== Send multiple agreements packaged in a single envelope for electronic signature ===
−	ICM has now improved user experience by providing the capability of displaying a scrolling banner message to inform users of a scheduled event or an announcement. For example, you can inform users that a maintenance activity is scheduled in 24 hours. A banner will scroll at the top of the ICM window alerting the users of the downtime, so that they can plan their work accordingly.&nbsp;<br/> This can be achieved through Application Settings by toggling the Show announcement banner field to Yes and entering the message to be displayed in the Announcement message box.	+	'''What''' – Earlier, agreement could be bundled only with its associations and sent for electronic signature. With this release you can also bundle peer agreements in a single package for electronic signing.
−	<br/> <span style="color:#008000;">'''408644 – Google Cloud Pub/Sub Support'''</span>	+	'''Advantages – '''Eliminates the need to send one agreement at a time for signature, thereby saving time. Provisions setting a sequence in which the agreements must be signed and facilitates reordering if required.
−	ICM has introduced out-of-the-box support for Google Pub/Sub (which is a fully managed real-time messaging service provided by Google Cloud) for ICM internal communication and also for any third party integrations.&nbsp;<br/> In ICM, the Message Pull option is used to receive messages from Pub/Sub. This change is transparent for ICM and there is no change as to how the communication between ICM Application (UI/API/Task) is perpetual.	+	'''How - '''Existing Esign functionality is enhanced to package peer agreements as a single bundle and send it for electronic signature.
−	<span style="color:#008000;">'''456074/439569/439668/467828 &nbsp;– Enhancements to Bulk Upload - Beta version'''</span>	+	'''Value''': User Experience | Contract Building Performance<br/> '''For''': Contract Owners | Legal Compliance Team<br/> '''Feature ID''': 1369302
−	The beta version of the Bulk Upload functionality has been enhanced. This allows you to:	+	=== Quickly create and edit contract types in bulk using excel workbook ===
−	*Provision users (which was earlier only available for Legacy Upload)	+	'''What''' – ICI now allows its users to edit and create contract types in bulk using the Microsoft Excel workbook. User can also edit multiple attributes for multiple contract types at once.
−	*Add team members when creating an agreement or amendment	+
−	*Add team members when updating agreement or amendment&nbsp;	+
−	*Create assignment and initiate the termination of agreements	+
−	<span style="color:#008000;">'''428153 – Promote to Production (P2P) Enhancements – Beta version'''</span>	+	'''Advantages'''
−	The beta version of the Promote to Production tool is now enabled. This functionality, provided to administrators, can promote ICM configurations/modifications that are made to ICM configurations in pre-production environments to production environments.&nbsp;<br/> This tool provides support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The elastic search sync is also supported by the tool.<br/> <span style="color:#FF0000;">Note: </span>This tool does not support the movement of agreements and amendments.&nbsp;	+	Contract type (CT) changes happen frequently in the implementation phase, the feedbacks from the customers regarding the changes in the CT have to be earlier implemented one by one for each CT in ICI UI. Now, this changes and edits can be done in one go using this feature.
−	</div> <div class="image-green-border">	+
−	'''<span style="color:#008000;">382235 – Power BI Integration with ICM&nbsp;</span>'''	+
−	With this release, in an effort to improve advanced analytics usability, additional functionalities have been added and some changes have been made.	+	Creating and editing multiple contract types at once will reduce time involved in configuring large contract types.
−	Default Dashboards are now available in the ''Advanced Analytics'' section. The ''Advanced Analytics'' tile now displays the following 3 tabs:	+	'''How'''
−	*'''''Business Summary:''''' displays the following charts based on the defined KPIs and the authorization of the user (for example, Finance Head):	+	A button “Bulk Contract Type” is now added under “Configure” tile.
−	**Agreement Summary such as Top Agreements by Value, Top Expiring Agreements, etc. (based on the defined KPIs).	+
−	**Deviations Summary such as Deviated Agreements and Contract Value (s) by Org Unit, Deviated Agreements by Contract Type, etc.&nbsp;	+
−	**Expiring Agreements such as Expiring Agreements by Month, Agreements marked for Auto-Renewal, etc.&nbsp;	+
−	**Cycle Time Report such as Cycle Time (in Days) by Contract Types, Trend of Cycle Time by Month, etc.&nbsp;	+
−	**Configuration Statistics such as Distribution of Templates by Contract Types, Clauses by Category, etc.&nbsp;	+
−	*'''''Legal Summary:'' '''displays the following based on the defined KPIs and the authorization of the user (for example, Legal Head):	+
−	**''Agreement Summary'' such as ''Top Agreements by Value, Top Expiring Agreements'', etc. (based on the defined KPIs).	+
−	**''Deviations Summary'' such as ''Deviated Agreements and Agreement Value (s) by Org Unit, Deviations Trend'', etc.	+
−	**''Expiring Agreements ''such ''as Expiring Agreements by Month, Agreements Value Expiring in next 12 Months by Org Unit'', etc.	+
−	**''Cycle Time Report ''such as ''Cycle Time (in Days) by Contract Types, Trend of Cycle Time by Month'', etc.	+
−	**''Configuration Statistics ''such as ''Distribution of Templates by Contract Types, User Information,'' etc.	+
−	*'''''Legal Details:''''' displays the legal details at a more granular level based on the defined KPIs and the authorization of the user (for example, Legal Head):	+	Users can generate pre-seeded contract type workbook, with 2 tabs in excel, contact type, and contract type attributes.
−	**''Agreement Summary'' such as ''Count of Agreements by Contract Type or Org Unit, Agreements by Status'', etc. (based on the defined KPIs).	+
−	**''Deviations Summary'' such as ''Deviated Agreements by Org Unit, Deviated Clause Cloud'', etc.	+
−	**''Expiring Agreements ''such ''as Expiring Agreements in 30 Days by their Org Unit, Agreements marked for Auto-Renewal in 30 Days by Org Unit'', etc.	+
−	**''Cycle Time Report ''such as ''Average'' ''Cycle Time (in Days) of Agreements, Month-wise Cycle Time Trend,'' etc.	+
−	*When creating reports, you can select which data model you want to use. For example, you can select Agreements data model to get agreement centric attributes and other data. If you select Clauses data model, then you would get clauses centric attributes and other data. The same applies using the ''Ask a question'' functionality.	+	'''Value''': User Experience<br/> '''For''': Admins | Legal Team | Contract Managers<br/> '''Feature ID''': 1342050
−	*The following UX related changes have been made:	+
−	**Last Updated On text is changed to Data Source updated successfully&nbsp;	+
−	**The Refresh icon (which shows the minimum time of refresh cycle among all datasets) is changed to the Refresh page button	+
−	*The ''Save your report'' option is now available for global reports. Users can save a copy of the global report. It is visible in the user’s''My Reports'' section and can be modified as required. If special characters are added to the report name, an error message will be displayed.	+
−	*You can change the name of the report using the ''Edit Report Name'' option. If special characters are added when renaming a report, an error message will be displayed.	+
−	*You can also delete this report using the ''Delete Report'' option if it is no longer relevant.	+
−	</div>	+
−	=== Enhancements to Rules ===	+
−	<span style="color:#008000;">'''288372 – Inclusion of Clauses and Clause properties in Search facets&nbsp;'''</span>	+	== Icertis Experiences ==
−	ICM has further enhanced the search capabilities by allowing searches on Agreements,&nbsp;Amendments, and Advanced Search based on Clause usage. This allows users to prioritize the Agreements they plan to work based on Clause usage, thus being able to tackle high-risk Agreements first and mitigating risks.&nbsp;You can now search and filter Agreements using the following Clause categories:&nbsp;''Clause Group, Clause Language, Clause Name, Is Alternate Clause, Is Dependent Clause, Is Deviated, Is Editable, Is Mandatory, Perform Deviation Analysis, Primary Clause, and Clause Code.''	+	=== Rules functionality added to Icertis Experience for Word ===
−	<span style="color:#FF0000;">Note: </span>Clause Description, Clause Text, Linked Primary Clauses, Clause Status, Linked Primary Template Clause, and search based on Clause text area are also not supported in Clause categories.&nbsp;	+	'''What''' – Users can now create rules for assembling the clause and define the rules for selecting the template from within Microsoft Word to display clauses in agreements based on specified conditions. Existing rules can also be viewed or edited from Microsoft Word.
−	'''<span style="color:#008000;">397346 – Ability to create Rule with ''Has A Value ''condition</span>'''&nbsp;	+	'''Advantages – '''Provides a familiar and intuitive interface for legal teams and contract authors to create conditional agreement templates.
−	With this release, the&nbsp;''Has A Value''&nbsp;condition has been enhanced to include all Data Types and system defined Attributes such that Rules can be set up for an Attribute having any value.&nbsp;For example, you want to set up a Rule so that an Approver John Doe should approve the Contract if a discount is applicable to it, irrespective of the value of the discount. Then, user can add a Rule using the&nbsp;''Has A Value''&nbsp;condition, such that John Doe is added as an Approver, if the discount has a value of 5%, 10% or whatever value is desired.&nbsp;	+	Reduced turnaround time, instead of switching while creating the clause and template
−	Earlier this condition supported only a limited set of user defined and system Attributes, but now it has been enhanced to support all Data Types and additional system Attributes. It is now also available for the following Contract Type Attributes and Data Types:&nbsp;''Contract Type Lookup'',&nbsp;''Contract Type Multi-Select Lookup'',&nbsp;''Choice'',&nbsp;''Multi-Select Choice'',&nbsp;''Number'',&nbsp;''Currency'',&nbsp;''Percentage'',&nbsp;''Date'',&nbsp;''DateTime'', and&nbsp;''URL''. In addition, it is also available for system Attributes such as&nbsp;''Template Name''&nbsp;and&nbsp;''Type Of Paper''.	+	'''How – '''Users can define conditions for selecting a clause or template while assembling of clauses and selection of templates from Microsoft Word.
		+	<div class="image-green-border">[[File:8.2 RN 01.png|300px|8.2 RN 01.png]]&nbsp;&nbsp;[[File:8.2 RN 02.png|300px|8.2 RN 02.png]]</div>
		+	'''Value''': User Experience<br/> '''For''': Legal Team<br/> '''Feature ID''': 1117626
−	<span style="color:#008000;">'''408653 – Enhancing Rules to support Power Set conditions for multi-select data&nbsp;'''</span>	+	=== Outlook Add-in – Labeling and validation for emails added to ICI ===
−	Currently, ICM supports only the ''Contains/Does Not Contain'' conditions for multi-select data. The ''Contains'' operator does not check whether all selected values of the Attribute are a subset of expected values, but only checks for any one of them. Thus, when the Rules were evaluated, even the Templates, Approvers, Clauses, etc. that are not required get executed.&nbsp;To avoid this confusion, Rules have been further augmented so that the user can configure conditions for power sets (i.e. cases where the user wants a Rule to be executed only if the entity field contains a subset of the configured values). This is achieved by introducing the new operator, ''Subset of, ''which is applicable to only multi-select lookup that supports evaluation of string, number, user, percentage and email data types only.<br/> Let’s consider the example of a Template Selection Rule to select multiple products using the Subset of operator. Suppose, the Rule is defined such that Template 1 should be selected if the selection is a subset of Products A, B, C, then:&nbsp;	+	'''What – '''Every email uploaded in ICI will now display an Outlook category label, that helps users know if the email is already added in ICI. Additionally, a validation is also displayed if user tries uploading same emails twice. Users can customize the outlook category label as per the needs.
−	*If the user selects any subset of products {A,B,C} like A,B or B,C or A,C or A,B,C, then Template 1 will be available for selection	+	'''Advantages – '''Avoid uploading duplicate email conversations in ICI.
−	*If the user selects any subset of products {A,B,C} & any other product like A,B,C,D or A,B,E, then Template 1 will NOT be available for selection	+
−	=== Enhancements to Templates ===	+	'''How – '''This feature is available as part of Icertis Experience for Outlook.
		+	<div class="image-green-border">[[File:8.2 RN 03.png|600px|8.2 RN 03.png]]</div>
		+	'''Value''': User Experience<br/> '''For''': Contract Managers | Legal Teams<br/> '''Feature ID''': 1341557&nbsp;
−	<span style="color:#008000;">'''419834 – Localization of Masterdata Attributes to support bilingual Agreements/Templates &nbsp;'''</span><br/> Earlier, ICM did not directly support bilingual Agreements and Templates. As a result, users had to tag multiple Attributes in a Template for different languages thereby ending up duplicating multiple attributes in a Contract Type.<br/> To simplify this process and facilitate bilingual templates, ICM has introduced the ability to tag the same Masterdata localized Attribute multiple times for different languages which can be tagged in a bilingual Template. This allows the user to manage the same Attribute with a different language in the same Template or Agreement. The support for bilingual templates allows the user to specify the second language for the Template and also be able to tag localized Attributes in the Template with the second language.<br/> <span style="color:#FF0000;">Note:'''&nbsp;'''</span>	+	=== Revamping ICI Salesforce User Experience ===
−	*It only supports string Attributes.	+	'''What''' – Revamping the ICI Salesforce user interface to give a better user experience, with addition of features and enhancement under agreement related sub tabs.
−	*Localization of Masterdata Attributes is applicable for - Template level support for Primary/Secondary language, Word Add-in (.NET and Scribe), Agreement and Clause tags, Document Assembly, and Rule-based Assembly.	+
−	*Rules will be evaluated in English for the Masterdata localized Attributes.	+
−	*Advanced Search also supports the localization of Masterdata Attributes.	+
−	*It is not applicable for Associations, Template Variables, Reverse Sync, and support tags on the Parent Agreement Clause.<br/> &nbsp;	+
−	<div class="image-green-border"><span style="color:#008000;">'''275828 &nbsp;– Template and Clause Harmonization – Beta version'''</span>	+
−	The beta version of the ''Legacy Upload'' functionality now provides an option to upload Templates and Clauses in bulk. This allows users to upload Templates, Template Metadata, Extended Template Entity Metadata, Template Variables, Template Team, Clauses, Clause Metadata and Clause Team. It also supports auto-tagging in Templates and Clauses of Template Variables, Contract Type Attributes, Associations, Signatories and Clauses.	+
−	<span style="color:#FF0000;">Note:</span> To enable auto-tagging, the details need to be provided in a set format/syntax.&nbsp;	+	The following agreement sub tabs can now be seen with new capabilities:
−	'''<span style="color:#008000;">397327 – Ability to drive dependency of Template Variables on Agreement Attributes&nbsp;</span>'''	+	*Associations sub tab
		+	*Amendment sub tab
		+	*Note sub tab
		+	*Team sub tab
		+	*Collaboration sub tab
−	With this release, ICM has extended support to Template Variables being conditional to the value of the Attributes that are part of a Contract Type. The user can track the dependency between the Contract Type Attribute and Template Variable as well as eliminate the creation of duplicate Attributes between them.&nbsp;This can be achieved by any user with&nbsp;''Manage''&nbsp;access on&nbsp;''Template Management''&nbsp;tile by enabling the&nbsp;''Is Conditional&nbsp;''flag for each Template Variable when creating or editing a Template. When&nbsp;''Is Conditional''&nbsp;is&nbsp;''On'', a user is able to set a dependent condition on the Template Variable by using&nbsp;''Depends on Contract Type Attribute''&nbsp;flag&nbsp;''On''&nbsp;and&nbsp;its related&nbsp;''Depends On Attribute&nbsp;''drop-down and&nbsp;''Depends On Value&nbsp;''field.&nbsp;	+	Some new features include:
−	The following conditions decide the dependency between the Template Variable and Contract Type Attribute: &nbsp;	+	Hyperlink added in the first column of the association list grid navigating to the association details page within ICI Salesforce platform.
−	*When ''Depends on'' ''Contract Type Attribute'' is ''On,&nbsp;''then it displays the Contract Type Attribute in the ''Depends On Attribute'' drop-down list.&nbsp;	+	Ability to preview the document from amendments sub tab.
−	*When ''Depends on'' ''Contract Type Attribute'' is ''Off,'' then it displays the Template Variable in the''Depends On Attribute'' drop-down list.&nbsp;	+
−	For each selected Attribute from ''Depends On Attribute'' drop-down list, the user can then enter the ''Depends On Value ''that will drive the dependency.&nbsp;	+	The collaborations tab is now revamped from ICI Iframe to Salesforce native look and feel, with capability to view more messages.
−	</div>	+
−	== Enhancements to Artificial Intelligence Apps in ICM ==	+
−	<span style="color:#008000;">'''386571 – Enhancements in AI Apps&nbsp;'''</span>	+	'''Advantages '''– This revamp will be giving a more consistent and familiar user experience with enhanced look and feel inline with Salesforce native user experience across tabs, subtabs and actions for sales personas.
−	With the 7.9 release, the Negotiate AI, Obligation AI and Visualize AI apps have been further enhanced to improve their usability. These apps are available in ICM through a technical configuration.	+	'''How''' – Below are few screenshots of the revamped ICI Salesforce platform.
−	'''Note:''' These apps are available in ICM through a technical configuration.	+	New ICI Salesforce Agreement Details screen
		+	<div class="image-green-border">[[File:8.2.RN 1.png|720px|8.2.RN 1.png]]</div>
		+	New Add Note Dialog box
		+	<div class="image-green-border">[[File:8.2.RN 2.png|720px|8.2.RN 2.png]]</div>
		+	'''Value''': User Experience<br/> '''For''': Sales Team<br/> '''Feature ID''': 1356012
−	'''Negotiate AI'''	+	=== Salesforce – Visibility of products and services sold to customers ===
−	While negotiating a particular Clause, the contract negotiator would like to quickly find similar Clauses in contracts that have already been executed to be able to make informed decisions. This also applies to the Agreement as a whole where the negotiator can refer to historical data from similar Agreements.	+	'''What''' – ICI Salesforce experience users can now view the list of all the products and services sold to the customer under “Agreement Lines” subtab.
−	With this release, the following options are provided within the Add-in so that the user can:	+	'''Advantages – '''With visibility to Agreement lines through this feature, Sales Executives will be able to identify Cross-sell, up-sell opportunities to pursue relevant sales, and request amendment to appropriate contract.
−	*Select a Clause/text and find similar Clauses from the ICM repository and compare them with the selected one	+	'''How – '''A new subtab “Agreement Lines” is added for account object displaying all the active product and services sold to the customer. The products displayed under agreement line subtab are fetched via ICI saved searches.
−	*Select similar Agreements present in the ICM repository	+	<div class="image-green-border">[[File:8.2.RN 3.png|720px|8.2.RN 3.png]]</div>
−	*Choose a filter to narrow down the Similarity search (for Clauses and Agreements) within particular type of Agreements	+	'''Note: '''The “Agreement Lines” displays only active products and services from executed contracts.
−	'''Note:'''	+	'''Value''': User Experience<br/> '''For''': Sales Managers | Sales Executive<br/> '''Feature ID''': 1192973
−	*It works on Microsoft Office 2016 for Windows version 16.0.4390.1000 or later, and Office .JS installed.	+	== Enhancements – Mobile App Experience ==
−	*Discovery workflow is supported only for non-ICM Agreements. However, the Similarity workflow is supported for both ICM and non-ICM Agreements	+
−	*The supported attribute data types include ''Choice, Currency, Date, Email, Text Area, Number ''and ''String''	+
−	'''Obligation AI'''	+	[[File:8.2 RN 32.PNG|720px|8.2 RN 32.PNG]]
−	Often business is interested in finding certain type of Obligations only. Our ML based obligation discovery finds all the obligations available in the document. In this release, we have enhances Obligation AI to discover only the specific obligations from the Agreement document.&nbsp;One of the most important aspects of ML algorithms is having the ability to learn from the users actions. In this release, we have enhanced the Obligation AI to immediately learn from user actions.	+	== Administration & Configuration ==
−	With this release, the user can:	+	=== Enhanced ICI startup validation architecture ===
−	*Choose the type of obligation discovery method to be run for a contract i.e. from a ML based generic discovery model or from a predefined set of obligation templates	+	'''What''' – A new validation framework for configuration keys and related metadata to resolve incorrect or missing keys and ensure seamless startup of ICI instances.
−	*Self-train from the ML obligation discovery ML model based on the actions taken by the user on the discovered obligations and display a higher confidence the next time similar obligations are discovered	+
−	'''Visualize AI'''	+	'''Advantages – '''Timely validation of configuration keys and guardrails to prevent unnecessary startup blockers.
−	The Visualize AI app is tightly coupled with the standard ICM entities. However, the app has been unable to cater to these customization needs of many enterprise customers who have customized these entities and have written their own logic.	+	'''How – '''At startup, the validation framework checks for configuration keys that are inconsistent or incorrect and restores those to default values thereby preempting any startup issues. Technical admins can view and investigate the validation logs on the self-service portal.
−	With this release, we support implementation of custom visualization using the following purposes:	+	'''Value''': Reliability, Supportability<br/> '''For''': Administrators<br/> '''Feature ID''': 1373024
−	*Data Fetching (for example, fetching data from external Web services)	+	=== Configure E-Signature Integrations within ICI ===
−	*Data Transformation (for example, adding a custom metadata property node)	+
−	*Data Rendering (for example, adding custom nodes in visualization)	+
−	<div class="image-green-border"><span style="color:#008000;">'''387056 – Add support for Table Discovery&nbsp;'''</span>	+
−	With this release, the Discover AI app has been further enhanced to include Table discovery. Along with Clause and metadata, ICM now also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Table Discovery'' tab (on the ''Details'' page). ICM tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&nbsp;	+
−	You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&nbsp;The table discovery allows you to:	+	'''What''' – E- signature configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
−	*Identify and discover the table(s) in the Agreement Document	+	'''Advantages '''– This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team.&nbsp;
−	*Update the data in the discovered table as required	+
−	*Create new instances of the Associations for the uploaded Agreement	+
−	</div> <div class="image-green-border"><span style="color:#FF0000;">Note: </span>Only the .docx document format is supported.&nbsp;</div>	+
−	== Enhancements to ICM Add-ins ==	+
−	'''<span style="color:#008000;">334171 – Enhancements in Email Outlook Plugin (.JS version) &nbsp;</span>'''<br/> With this release, a new .JS version of the ICM Outlook Plugin has been introduced. The overall turnaround time for authoring is reduced as he no longer needs to download the documents received over email to the local machine, then switch applications and log on to ICM, search the Agreement and then upload the documents.<br/> The provisioned user can now:	+	'''How''' – Technical administrators can configure E- sign providers (DocuSign and AdobeSign) from the E-sign configuration page.
		+	<div class="image-green-border">[[File:8.2 RN 04.png|720px|8.2 RN 04.png]]</div>
		+	'''Value''': Self-service<br/> '''For''': Technical admins<br/> '''Feature ID''': 1180879
−	*Upload the next version of the Agreement document received over an Email to the Agreement	+	=== Integrated Config keys validation framework ===
−	*Upload the next version of the Associated document (supporting Attachments) received over an Email to the Agreement	+
−	*Create a new Association instance and then upload the Associated Document received over an Email to the Agreement	+
−	The configuration of the Outlook Add-in is driven by the Masterdata, whereas the list of Agreements and their details are configured by the Saved Searches. You can configure multiple saved searches. This is available for MS Outlook online as well as the Desktop client.&nbsp;	+	'''What''' – ICI now has the capability to check incorrect values, difference in data types, and inconsistency in configuration data. The utility can be run prior to starting an application and the report and errors reported can be used to help find a solution.
−	== Enhancements to Reports ==	+	'''Advantages – '''Helps prevent issues that occur during application startup.
−	<span style="color:#008000;">'''275838 – Extended support for user's preferred Time Zone settings in Reports'''</span>	+	'''How – '''At the start of an ICI instance, the disparity in the configuration keys is identified, and the incorrect keys are set to the default value. All such changes are recorded in the self-service portal so that the technical admins can investigate the errors.
−	Previously, all Date related columns and parameters in all ICM reports were displayed in the UTC Time Zone in the ''mm/dd/yyyy ''format. ICM allowed users to set the Date and Time format as per their preferred locale settings.&nbsp;With this release, all reports will display the Date and Time as per the ''Time Zone'' set by the user in the user preferences.	+	'''Value''': Self-service &nbsp;<br/> '''For''': Administrators<br/> '''Feature ID''': 1373030
−	However, the following points need to be noted:	+	=== Configure SSO integrations within ICI ===
−	*When reports are exported to CSV format, due to the inherent property of the CSVS files, the Date and Time format of the Date columns will be as per the user's local machine format, not as per the User Preferences set in ICM.	+	'''What''' – SSO configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
−	*In all reports, where the parameters to generate the reports have dates (for example, ''Created Start Date ''and''Created End Date'' in the ''Cycle Time Report''), the default value in these fields are displayed in the UTC time zone. However, when the user changes values in these fields and generates the reports, the dates will then be displayed as per the user’s local time.	+
−	*If the ''Date Format ''selected in the user’s preferences is ''dd-mmm-yy'', the date value in the field gets converted to the month & vice-versa. As a workaround, the date format in this field has been set as mmmm-dd-yyy, so that the default value is displayed as per the user’s expectations. However, the date format when the report is generated is displayed as per the user’s preferences. For example, if the user selects the ''Date Format'' as ''dd-MMM-yy'' in ''My Preferences'', then the dates displayed in the ''Cycle Time Report'' fields ''Created Start Date ''and ''Created End Date ''are actually set as ''mmmm-dd-yy''.	+	'''Advantages '''– This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team.&nbsp;
−	<span style="color:#008000;">'''385409 – Additional&nbsp;Reports added to KPIs&nbsp;'''</span>	+	'''How''' – Technical administrators can configure SSO integrations (SAML, WS-Fed and O-Auth) from the SSO configuration page.
		+	<div class="image-green-border">[[File:8.2 RN 05.png|720px|8.2 RN 05.png]]</div>
		+	'''Value''': Self-service &nbsp;<br/> '''For''': Technical admins<br/> '''Feature ID''': 1180896
−	In addition to the reports that are already available on the Dashboard as KPIs (Agreement Deviation Report, Agreements Pending Approval Report, Agreements Pending Execution Reports, Average Agreement Turn Around Time Report, Clauses Pending Approval Report, Expiring Agreement Report, and Templates Pending Report), users can now also add the following reports:	+	=== Customer-specific SAML/OAuth SSO Configurations ===
−	This can be achieved by providing access through ''Security Groups''.	+	'''What – '''In a multitenant instance of Icertis Contract Intelligence, SSO configurations are now moved from a single configuration file to separate configuration files for each tenant. These configurations can now also be modified from within Icertis Contract Intelligence.
−	For example, the ''Signature Type Report'' KPI depicts the percentage of electronic signatures in ICM. If the number of electronic signatures is 6 and the number of manual signatures is 83, then the KPI is calculated as 6/83+6 = 6/89 (total number of agreements). Therefore, the percentage of electronic signatures displayed on the KPI tile on the Dashboard is 6 (rounded off to nearest digit).	+	'''Advantages''' –
−	The reports that were already present as KPIs on the Dashboard included the ''Agreement Deviation Report, Agreements Pending Approval Report, Agreements Pending Execution Report, Average Agreement Turn Around Time Report, Clauses Pending Approval Report, Expiring Agreements Report, ''and the''Templates Pending Approval Report.''	+	*Site reliability and stability - SSO issues affecting one tenant do not impact other tenants.
		+	*Self-service - Technical admin users can configure SSO without intervention from Icertis teams.
−	== Integrations ==	+	'''How – '''Users with the right permissions can make SSO configuration changes from the Tenant.config file. The changes can also be made from within ICI by Technical Admin users.
−	=== Integrations with Collaboration Tools ===	+	'''Value: '''Self-service, Reliability, Supportability<br/> '''For:''' Technical Admins<br/> '''Feature ID: '''1317384
−	<span style="color:#008000;">'''370460 – ICM Integration with MS Teams&nbsp;'''</span><br/> By integrating the ICM platform with MS Teams, users can collaborate for contract authoring, negotiations, etc. This not only provides a better, seamless user experience, but also helps to discuss ideas, and in turn significantly improve the cycle time.<br/> Through this integration, we support:	+	=== Error-handling framework ===
−	*Invoking ICM Bot in the Teams app	+	'''What '''– A centralized and industry-standard error handling framework for faster troubleshooting, analysis and resolution of issues. The list of error codes and related data is cataloged & documented, which will act as a standard reference for all error codes in the ICI platform.
−	*Querying My Pending Tasks using the ICM Bot to be able to collaborate with others and take decisions on pending tasks and expedite the contracting process	+
−	*Searching for Agreements using ICM Bot so that the user can find the relevant, share their status and make informed decisions	+
−	*Using ICM Bot to get answers to frequently asked questions	+
−	=== Icertis Experience for&nbsp;Salesforce ===	+	The framework provides the following features:
−	<span style="color:#008000;">'''348588 – Configuring Field Set from Salesforce to ICM using Rest API&nbsp;'''</span><br/> With this release, a new field called ''Field Set Name ''has been introduced that can be configured using the ''Configuration'' page which is accessible through the managed application available in Salesforce AppExchange. When the integration is triggered from Salesforce, the Adapter can read the metadata and send only the Attributes defined for the entity Field Set. If the Field Set is not defined, the Adapter sends all the Attributes for that entity.&nbsp;<br/> <span style="color:#FF0000;">Note: </span>It is necessary to create a new Field Set for every Salesforce entity. The field set determines the fields that the user can edit in a particular Salesforce entity instead of having to select each field individually. For example, a Field Set created for an Opportunity can have fields such as Opportunity Name, Opportunity ID, etc.&nbsp;	+	Detailed and structured data to determine severity, origin, module, area & source of the error.
−	<span style="color:#008000;">'''397315 – Create mapping between Template Variable for Agreements and SFDC fields'''</span>&nbsp;	+	No unhandled exceptions emanating from the system.
−	The ICM Salesforce Adapter allows mapping of Salesforce entities and their Attributes to be integrated with ICM for data flow from Salesforce to ICM (Forward Sync) as well as ICM to Salesforce (Reverse Sync). This was previously done using ''Client App Entity Mapping ''on the ''Masterdata Configuration'' page which allows mapping the ICM Attributes from Contract Types, but not from Agreement Templates.	+	Detailed logging is done in a central repository like Kibana.
−	With this release, Administrators can now use Attributes defined at Template level to store critical external data as part of the Agreement and sync with Salesforce, thus avoiding data duplication and redundancy in the process.	+	For ICI Instances where AppInsights is available, a correlation id helps to track calls and correlate the complete chain of events that led to the error.
−	=== Icertis Experience for&nbsp;Workday ===	+	'''Why '''– Eliminates time required to locate and understand the issue and reduces the overall time needed to fix issues.
−	<span style="color:#008000;">'''384529 – Executed PDF from ICM to Workday&nbsp;'''</span>	+	'''How '''– ExceptionHandler attribute is introduced, which will have following Origin, Area, Module, Sub Module in the form of code.
−	Customers using Workday ERP application to manage their procure-to-pay process want to have end-to-end integration to Icertis Contract Management (ICM) platform for managing their procurement process. The&nbsp;Icertis platform already supports integration to Workday Financials and HCM via an Adapter. As part of this integration, contracts authored in the ICM platform can be sent to Workday via the Adapter and attached to Workday contracts in .docx format.	+	For example: 50000030021360X8013153 (shown on User Interface)
−	Now, with the help of Event based configuration in the Adapter, it is possible to send the Agreement document in .PDF or .docx format to Workday for a specific event.	+	Breakdown of the code is as follows:
−	=== Enhancements to Adobe Sign and DocuSign ===	+	5 – Severity
−	<span style="color:#008000;">'''344436 – Support for Print, sign and upload (Wet Signed Copy) and sync back in ICM&nbsp;'''</span><br/> Adobe Sign provides users the capability of signing documents manually using ''Print, sign'' and ''upload'' option. However, earlier when the Agreement Document was Wet signed and uploaded, it did not get synced back to ICM, and the Agreement would get blocked in that state. With this release, ICM supports syncing back the signed Agreement document and changed status, so that the user can proceed with the workflow as expected.<br/> <span style="color:#FF0000;">Note:&nbsp;</span>	+	00 – Origin (First parameter of Exception Handling attribute)
−	*If the Wet Signatures Only option is selected, then system mandates all the users to sign the Agreement document using the Print, sign and upload option of Adobe Sign.&nbsp;	+	00 – Source (mostly internal)
−	*If the Wet Signatures Only option is not selected, then users can either sign it electronically or use the Print, sign and upload option to sign it manually. However, in this case if any user signs using the Print, sign and upload option, since all the Signature tags will be lost, Adobe Sign will add an additional page to the end of Agreement document that will have signature tags for subsequent signatories who are yet to sign.&nbsp;	+
−	*Attribute sync back to ICM will only work for the first signatory. Once Adobe Sign’s Print-Sign-Upload option is used, Attribute tags are not available for subsequent signatories who are yet to sign the document.	+
−	*In case of parallel signatures, the Wet Signature option is not applicable. If the Wet Signature Only option is selected, then the Agreement will be stuck in the Approved state.&nbsp;	+
−	<div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''430578 – Send Additional Supporting Documents to Adobe Sign&nbsp;'''</span><br/> The current Send for Signature functionality only allows users to send the main Agreement for signature. It does not allow users to add the supporting documents along with the main Agreement document.&nbsp;With this release,&nbsp;ICM will support Preview and sending of the associated documents (Attachments) along with the main Agreement for signature.&nbsp;<br/> <span style="color:#FF0000;">Note:</span> Only Agreement specific tags will be displayed in the Agreement document when reviewing and signing it. After the Agreement document is signed, only Agreement will be synchronized with ICM again.&nbsp;</div> <div class="image-green-border">The Associated Documents (attachments in the Word or PDF format that is associated to the main Agreement) will be available for selection when sending it for signature.&nbsp;</div>	+
−	== Technical Requirements for Release 7.9 ==	+
−	The Icertis Contract Management base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available in all the environments, and 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.	+	03 – Area (Second parameter of Exception Handling attribute)
−	[[File:Technical Requirements 1.PNG|Technical Requirements 1]]	+	002 – Module (Third parameter of Exception Handling attribute)
−	[[File:Technical Requirements 2.PNG|Technical Requirements 2]]	+	136 – SubModule (Fourth parameter of Exception Handling attribute)
−	[[File:Technical Requirements 3.PNG|Technical Requirements 3]]	+	0X8013153 – Standard C# HResult which can be googled to see the exception type
−	[[File:Technical Requirements 4.PNG|Technical Requirements 4]]	+	Class decorators for Exception Handling
		+
		+	['''ExceptionHandler''' (exceptionOrigin: ExceptionOrigin.Core, exceptionArea: ExceptionArea.CLM, module: ExceptionAreaModule.CLM_AdminTask, submodule: ExceptionAreaSubModule.CLM_AdminTask_Root)]
		+
		+	When an error occurs, the error code is displayed on the error message, see the screenshot below.&nbsp;&nbsp;
		+	<div class="image-green-border">[[File:8.2 RN 33.PNG|400px|8.2 RN 33.PNG]]</div>
		+	'''Value: '''Supportability<br/> '''For: '''Partner Developers | Any Application User | Troubleshooters<br/> '''Feature ID''': 1373034
		+
		+	=== Administration & Configuration Enhancements ===
		+
		+	[[File:8.2 RN 34.PNG|720px|8.2 RN 34.PNG]]
		+
		+	== Reporting Analysis ==
		+
		+	=== Dashboard and Power BI reports for Supplier Evaluation ===
		+
		+	'''What – '''An interactive Supplier Evaluation dashboard with the following features is now available out-of-the-box:
		+
		+	Interactive graphs for status of evaluation cases, evaluation distribution by performance, and ageing in review or approval states.
		+
		+	Enlists the top and poor performing suppliers based on a host of filters like evaluation type, period of evaluation, supplier name and more.
		+
		+	Captures evaluations that are awaiting supplier inputs for missing documents.
		+
		+	360-degree supplier performance score card about different evaluations, KPI and performance trend over a time period.
		+
		+	Capture supplier documents/ certificates that are expired or expiring within 5 days.
		+
		+	'''Advantages –'''
		+
		+	Information is represented visually and is easier to consume and track.
		+
		+	Assist the procurement team in setting up the right expectations and manage supplier relationships.
		+
		+	Insights into poorly performing suppliers can help in planning proactive performance improvement.
		+
		+	'''How – '''The dashboard and reports can be accessed from the Supplier Management -> Dashboard.
		+
		+	'''Pre-requisite''': HTTP Artifact binding should be supported by the respective IDP server to enable this feature.
		+	<div class="image-green-border">[[File:8.2 RN 15.png|720px|8.2 RN 15.png]]</div>
		+	'''Value: '''Analytics&nbsp;| User experience<br/> '''For: '''Vendor Management Office | Procurement Department | Business Analysts| Legal Team<br/> '''Feature ID: '''1235347
		+
		+	=== New filters added to Agreement and Amendment based SSRS reports ===
		+
		+	'''What – '''The following filters are now available on UI for DRF Agreements Pending Approval and DRF Expired Agreements reports:
		+
		+	Contract Type
		+
		+	Org Unit
		+
		+	Agreement Owner
		+
		+	Agreement Status
		+
		+	Created Date (Created Date From, Created Date To)
		+
		+	Time Zone
		+
		+	'''Note''': These reports are default and cannot be customized as of now.
		+
		+	'''Advantages – '''One or more filters can be applied to help view the data in contextual slices.
		+
		+	'''How – '''The filters can be applied from the respective reports page, which can be accessed from the Default Reports tab.
		+	<div class="image-green-border">[[File:8.2 RN 16.png|720px|8.2 RN 16.png]]</div>
		+	'''Value: '''Self-service<br/> '''For: '''Managers | Legal Team | Decision Makers<br/> '''Feature ID: '''1346718
		+
		+	=== Self-Service Configuration page for creating custom SSRS reports and dynamic views ===
		+
		+	'''What – '''Technical users can create or modify dynamic views and create or modify SSRS reports from the self-service configurations page. Some knowledge of technical column names and JSON is necessary to make the modifications.
		+
		+	'''Advantages – '''Provides a simpler path to customize reports and can be done by technical users without intervention from Icertis teams.
		+
		+	'''How – '''Users with technical role ‘Report admin’ can access the Report Configurations tab on the System Configuration – Self-Service page and create and modify the dynamic views and SSRS DRF reports.
		+	<div class="image-green-border">[[File:8.2 RN 17.png|720px|8.2 RN 17.png]]</div>
		+	'''Value: '''Self-service<br/> '''For: '''Configuration Admin | External implementation partners<br/> '''Feature ID: '''1346720
		+
		+	== APIs ==
		+
		+
		+
		+	=== API Management Service ===
		+
		+	'''What – '''API management is a key infrastructure of API offering working as a façade and controlling layer for use of ICI APIs. It consists of—a gateway which controls the flow of APIs from the integrating application to ICI API server, a management portal to configure the usage policies and an information portal called API Hub.
		+
		+	With the API Management, the following is possible for customers:
		+
		+	*Enforcing usage quota limit
		+	*Rate limiting (throughput throttling) of API calls (by default set to 5 API calls per min)
		+	*Monitoring and getting reports on usage of APIs
		+
		+	'''How – '''All customers using Icertis APIs can use the APIM gateway URLs as API URLs. For new customers, the APIs are automatically routed through APIM. For the existing customers that are already using APIs, they must make a configuration change to connect to APIM. The Icertis team will provide the exact API gateway URLs.
		+
		+	'''Note''': The API Hub capability where users can get the information about APIs, try out the endpoints and get API usage reports is described as a separate feature below in the release notes.
		+
		+	'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
		+
		+	=== Icertis API Hub–A New Developer Experience for Working with APIs ===
		+
		+	'''What – '''The new Icertis API Developer Experience is simple, secure, and immersive for the developers.
		+
		+	As an API developer, the new Icertis API Developer Experience allows you to discover and interact with the ICI APIs. Developers can find recommendations for making API requests, inputs for each endpoint, and authentication methods. Based on the subscription key, the developers can make API calls for the API products.
		+
		+	We have divided the API endpoints into distinct categories to facilitate access and search. Reports include data points like the number of API calls, response time, APIs used, etc.
		+
		+	'''Advantages''' –
		+
		+	*Smoother developer on-boarding and learning experience
		+	*Real-time usage reports provide transparency
		+
		+	'''How – '''You must have the APIM Dev Portal User role assigned to access the new APIM Developer experience. Contact your system administrator for access.
		+
		+	Additional notes:
		+
		+	*You can use OAuth or token-based authentication method
		+	*An additional fee is required to use the access-based certificate authentication method
		+
		+	'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
		+
		+	=== Framework for the composite API ===
		+
		+	'''What''' – This release introduces “Single Response – Composite APIs” to eliminate creation of wrappers over ICI Platform’s APIs while using them.
		+
		+	The Composite API Framework supports the following features:
		+
		+	API endpoint for supporting composite structure
		+
		+	Request and Response representation
		+
		+	Validation framework for composition
		+
		+	Orchestration logic for composite requests
		+
		+	Referencing field's structure and usage
		+
		+	'''Advantages''' – The framework helps simplify the implementation and makes the integration more efficient. How - API developer can work on ICI entities via single composite API request to trigger series of APIs calls in a single API call and get multiple request results in a single response body.
		+
		+	'''Value''': User Experience | Ease of Use | Improved Efficiency<br/> '''For''': API Developers | Administrators<br/> '''Feature ID''': 1182667
		+
		+	=== API Endpoint Changes ===
		+
		+	[[File:8.2 RN 06.PNG|720px|8.2 RN 06.PNG]]
		+
		+	[[File:8.2 RN 07.PNG|720px|8.2 RN 07.PNG]]
		+
		+	[[File:8.2 RN 08.PNG|720px|8.2 RN 08.PNG]]
		+
		+	[[File:8.2 RN 09.PNG|720px|8.2 RN 09.PNG]]
		+
		+	[[File:8.2 RN 10.PNG|720px|8.2 RN 10.PNG]]
		+
		+	[[File:8.2 RN 11.PNG|720px|8.2 RN 11.PNG]]
		+
		+	[[File:8.2 RN 12.PNG|720px|8.2 RN 12.PNG]]
		+
		+	== AI Applications ==
		+
		+	=== Beta Feature – Refer existing obligations when reviewing AI-discovered obligations ===
		+
		+	'''What''' – AI-discovered obligations are automatically categorized in a category and sub-category when presented for review and confirmation. When reviewing discovered obligations users can now refer to existing obligations in approved state belonging to the same category, sub-category and related agreements. Changing the category and sub-category, displays the relevant set of approved obligations.
		+
		+	'''Advantages''' –
		+
		+	Referring '''Library Obligations''' can help you get a standard position/scope/language to be used while setting up a newly discovered obligation
		+
		+	Referring from '''Related Agreements''' helps you understand what obligations from parent (peer) contracts are to be set at the child level specially in case of back-to-back contracting (e.g., checking customer contracts and passing on the related obligations in supplier contracts)
		+
		+	'''How – '''Users can review AI-discovered obligations from the Review Obligation drawer, which can be accessed from the “Review Discovered Obligation” page.
		+
		+	Review Obligation drawer displaying Approved Obligations in Library Obligation
		+	<div class="image-green-border">[[File:8.2 RN 35.PNG|720px|8.2 RN 35.PNG]]</div>
		+	'''Note:''' Library Obligations are to be added manually. Please refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.2/index.php?title=ICI_Obligation_Management#Obligation_Library OM wiki] on how to setup an Obligation Library.
		+
		+	Review Obligation drawer displaying Approved Obligations in Related Agreements
		+	<div class="image-green-border">[[File:8.2 RN 36.PNG|720px|8.2 RN 36.PNG]]</div>
		+	'''Note: '''Time needed to display Obligations from related agreements may vary depending upon the number of Linked agreements and count of Obligations within them.
		+
		+	'''Value''': Efficiency | Time Saving<br/> '''For''': Legal Team | Contract Managers<br/> '''Feature ID''': 1366783
		+
		+	== Sourcing ==
		+
		+	The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application.
		+
		+	=== Converting RFI to RFP or RFQ ===
		+
		+	'''What''' – ICI Sourcing application now allows creating an RFP or RFQ from an RFI from which the suppliers are shortlisted. Users can create multiple RFP’s or RFQ’s from a single RFI.&nbsp;
		+
		+	'''Advantage''' – Saves time when creating an RFP or RFQ by allowing shortlisted suppliers to be selected from a previously completed RFI. &nbsp;
		+
		+	'''How''' – Users can use the “Create from RFI” button from the Sourcing index page or from the Create RFP/RFQ option on the RFI that is in “Bidding Closed” state.
		+
		+	'''Value''': User Experience<br/> '''Feature ID''': 1328960&nbsp;&nbsp;
		+
		+	=== Shortlist Suppliers in RFx ===
		+
		+	'''What''' – An enhancement has been made to the existing '''Shortlist''' feature that allows buyers to select and shortlist specific suppliers for the next procurement stage. For example, from RFI to RFP or RFQ or from one round to another in the same RFX. The supplier Shortlist can be modified in certain RFx statuses.
		+
		+	'''Advantage''' – Helps accessing preferred suppliers quickly or remove them from the “Suppliers” page thereby saving time.
		+
		+	'''How''' – A “Shortlist Supplier” option is added on the “Suppliers” page. &nbsp;
		+	<div class="image-green-border">[[File:8.2.RN 4.png|500px|8.2.RN 4.png]]</div>
		+	'''Value''': User Experience<br/> '''For''': Buyer and Administrator users<br/> '''Feature ID''': 1341682&nbsp;&nbsp;
		+
		+	=== Sourcing Enhancements ===
		+
		+	[[File:8.2.RN T4.PNG|720px|8.2.RN T4.PNG]]
		+
		+	== Obligation Management ==
		+
		+	The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application
		+
		+	=== Auto-create Obligations from Associations data ===
		+
		+	'''What''' – ICI Platform now facilitates improved Obligation intake from source Association records. An Obligation is automatically created from any defined associations such as Deliverables, SLA, Risk Assessments. For example, if a SOW has ‘Deliverable’ as an association, then the user can directly convert that deliverable into an Obligation.
		+
		+	'''Advantages''' – Streamlines and simplifies creation of Delivery Dates, Milestones, SLAs, Risk Assessments, and other obligations from associated records, improving process efficiency. Auto-creation of Obligations enhances tracking compliance centrally using Obligation Management.
		+
		+	'''How – '''You can use the “Create Obligation” menu option from the Associations object list view or details page.
		+	<div class="image-green-border">[[File:8.2.RN 5.png|720px|8.2.RN 5.png]]</div>
		+	'''Value''': User Experience | Contract Building | Managing Obligations | Process Efficiency<br/> '''For''': Risk Managers | Contract Administrators<br/> '''Feature ID''': 649740
		+
		+	=== Use “Date” & “DateTime” Attributes from Holding Agreement for Obligation Scheduling ===
		+
		+	'''What – '''Due'''dates and end dates for obligations can now be selected from any of the date attributes of the agreement.'''
		+
		+	'''Advantages'''
		+
		+	Eliminates the need for an Obligation creator to know specific dates.
		+
		+	Consistency in Obligation dates used across various members / obligation creators
		+
		+	Reduces the extra effort required in referring to Date Attributes of holding agreement entity (for example, Effective Date / Expiry Date) and use them in Obligation creation.
		+
		+	'''How – '''Two new attributes have been added to the Obligation Contract Type – “Select Due Date From” and “Select End Date From”. You can select a specific date value from the given options. The date value selected will be as per the actual date defined in the Agreement. For example, if you select “Expiry Date” value, an Obligation will be created with an expiry date that is same as the expiry date for the Agreement.
		+	<div class="image-green-border">[[File:8.2.RN 6.png|600px|8.2.RN 6.png]]</div>
		+	&nbsp;
		+
		+	'''Value''': User Experience<br/> '''For''': Contract Operations<br/> '''Feature ID''': 913820
		+
		+	=== Obligation Management Enhancements ===
		+
		+	[[File:8.2.RN T5.PNG|720px|8.2.RN T5.PNG]]
		+
		+	== Supplier Relationship Management ==
		+
		+	ICI Supplier Relationship Management application is certified to work with the 8.2 release
		+
		+	=== Supplier Profile and Supplier Master records synchronization ===
		+
		+	'''What''' – Supplier product and service categories are now automatically synced in the following events:
		+
		+	On supplier qualification, the product/service category updates get copied to the Supplier Master category field.
		+
		+	Buyers update the Supplier Master the information is synced with the Supplier Profile.
		+
		+	Buyers update the Supplier Profile the information is synced with Supplier Master.
		+
		+	'''Advantage''' – Supplier records are consistent and can be consumed across all Icertis applications.
		+
		+	'''How''' – If a supplier record in the database is modified depending on the conditions defined, the other relevant records also get updated automatically.&nbsp;
		+
		+	'''Value''': Efficiency<br/> '''For''': Buyer users<br/> '''Feature ID''': 1420117
		+
		+	=== Supplier Relationship Management Enhancements ===
		+
		+	[[File:8.2.RN T7.PNG|720px|8.2.RN T7.PNG]]
		+
		+	&nbsp;
		+
		+	== Rebates Enhancements ==
		+
		+	Rebates App in ICI Platform is enhanced to improve the usability and thereby improve the overall user experience, scalability and robust calculations. The Rebates App extends support for Big Data, AI, and Dynamic JSON. The enhancements in Rebates App can be summarized as below:
		+
		+	'''Refined seeded data model:'''
		+
		+	*Minimal configuration and data reusability to make Rebates app more scalable.
		+	*Standardized naming conventions to avoid any conflicts with other apps.
		+	*Normalized data has improved Calculation Engine’s efficiency by 50%.
		+	*Dynamic JSON for Rebate program data eliminates the need to have distinct rebates and payout calculation for every business unit in an organization. The enhanced calculation engine extracts JSON data from the Agreement and its associated documents and maps it with the newly configured attributes.
		+	*Background tasks optimized to support big data such as calculation engine processing large invoice and agreement datasets. As an example, for performance testing, it took 35 seconds (approximately) to process 170,000 &nbsp;records (approximately) as compared to 1 minute (approximately) for 5000 records (approximately) in the earlier version.
		+	*Rebate program attributes are a part of associated document instead of an agreement, which enables handling multiple rebate programs within a contract. This also reduces the number of attributes in an agreement, that improves the performance of agreement creation.
		+	*Standardized attributes management by allowing 16-digit numbers with 6 decimal places.
		+	*Generic Product, Location, and Customer hierarchies allow customizing configuration and mapping it to the calculation engine.
		+	*Previously, configuration supported only up to 10 customer details as these details were part of the Agreement itself. However, now these details are migrated as Associated documents to support unlimited customer details.
		+
		+	'''Power BI Reporting:'''
		+
		+	*Intuitive dashboard with advanced analytics on the rebate agreement distribution and accruals accumulation.
		+	*Out-of-the-box reports added in Power BI, which were earlier focused on Accruals, are now aligned with the overall performance of Rebates.
		+	*Improved visibility for Rebates payout calendar with the next payout dates.
		+
		+	=== Risk Management Enhancements ===
		+
		+	[[File:8.2.RN T6.PNG|720px|8.2.RN T6.PNG]]
		+
		+	== Technology Updates ==
		+
		+	=== HTTP Artifact Binding Support for SSO Integration ===
		+
		+	'''What – '''In addition to HTTP POST and HTTP Redirect, ICI now supports HTTP Artifact binding for SSO (Single Sign-On) integration along with other IdPs like ADFS.
		+
		+	'''Advantages – '''With improved security, exchanging sensitive data across Id Provider (IdP) and Service Provider (SP) becomes more authenticated and trustworthy. This prevents intervention of any malicious party.
		+
		+	'''How – '''Administrator or Implementation Partner can choose between HTTP POST, HTTP Redirect and HTTP Artifact binding for SSO (Single Sign-On) integration, on the IdP server side.
		+
		+	'''Value: '''Secure Authentication Process<br/> '''For: '''All ICI Users<br/> '''Feature ID: '''1342076
		+
		+	=== Microsoft retiring basic authentication for SMTP ===
		+
		+	'''What '''– Microsoft is retiring basic authentication for SMTP, and it would be necessary for customers using basic authentication to move to an alternate service. ICI now supports modern authentication with support for Microsoft Graph API.
		+
		+	'''Why '''– Provide support for modern authentication methods & ensure service continuity even after Microsoft retires basic authentication later this year (Oct 1, 2022).
		+
		+	'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
		+
		+	'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
		+
		+	=== Microsoft retiring Outlook REST API ===
		+
		+	'''What''': The Icertis Outlook Add-In that currently uses the Outlook REST API will now use Microsoft Graph API.
		+
		+	Configurations are required for Outlook Add-In at the time of implementing or upgrading Icertis Contract Intelligence to work with Microsoft Graph API.
		+
		+	'''Why''': Microsoft has announced that Outlook REST API will be deprecated in the month of November, 2022.
		+
		+	'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
		+
		+	'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
		+
		+	=== Support for StartTLS protocol ===
		+
		+	'''What''' – Adding support for the StartTLS protocol through NuGet MailKit for authentication and notification. StartTLS protocol command is used to inform the email server that the email client wants to upgrade from an insecure connection to a secure one using TLS or SSL.<br/> <br/> '''Why''' – Customers have the option to use the StartTLS protocol, which supports enhanced security.
		+
		+	'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
		+
		+	'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
		+
		+	=== Bootstrap upgrade from version 4.5.2 to 5.1.3 ===
		+
		+	'''What''' – The Bootstrap library has been upgraded from version 4.5.2 to 5.1.3. The support for Bootstrap library version 4.5.2 ends by Q3 2022. 4.5.2 is compatible with the new version.
		+
		+	'''Why''' – To address security vulnerabilities.
		+
		+	'''TFS ID''': 1459132<br/> &nbsp;
		+
		+	=== Web Application Firewall & Azure Front Door ===
		+
		+	'''What''' –
		+
		+	Implementing Azure Front Door (AFD) with the following settings:
		+
		+	Web Application Firewall (WAF) in diagnostic mode
		+
		+	Prevention Rule in AFD to restrict access from embargo countries.
		+
		+	'''Advantages – '''WAF & AFD help prevent against common exploits and vulnerabilities.
		+
		+	'''How – '''It can be configured, deployed, and managed via the Azure Portal, PowerShell, and CLI (command-line interface).
		+
		+	'''Value''': Security<br/> '''For''': Administrators<br/> '''Feature ID''': 951438
		+
		+	&nbsp;
		+
		+	= 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:
		+
		+	[[File:8.2.RN T8.PNG|720px|8.2.RN T8.PNG]]
		+
		+	[[File:8.2.RN T9.PNG|720px|8.2.RN T9.PNG]]
		+
		+	[[File:8.2.RN T10.PNG|720px|8.2.RN T10.PNG]]<br/> [[File:8.2.RN T11.PNG|720px|8.2.RN T11.PNG]]
		+
		+	[[File:8.2.RN T12.PNG|720px|8.2.RN T12.PNG]][[File:8.2.RN T13.PNG|720px|8.2.RN T13.PNG]]
		+
		+	[[File:8.2.RN T14.PNG|720px|8.2.RN T14.PNG]]
		+
		+	[[File:8.2.RN T15.PNG|720px|8.2.RN T15.PNG]]<br/> [[File:8.2.RN T16.PNG|720px|8.2.RN T16.PNG]]<br/> [[File:8.2.RN T17.PNG|720px|8.2.RN T17.PNG]]
		+
		+	[[File:8.2.RN T18.PNG|720px|8.2.RN T18.PNG]]
		+
		+	= Accessibility Conformance =
		+
		+	We ran accessibility conformance tests on the Icertis Contract Intelligence platform and Business Apps for Web Content Accessibility Guidelines 2.1 for Level A and Level AA standards. We did not evaluate for Level AAA standards.
		+
		+	While most of the product functionality has at least one method that meets the criterion without any known defects, some functionality of the product may not meet the conformance criteria. The full report is published in the following documents and can be made available on request:
		+
		+	ICI Platform Accessibility Conformance Report
		+
		+	ICI AI/ML Accessibility Conformance Report
		+
		+	ICI Reporting Accessibility Conformance Report
		+
		+	ICI Obligation Management Accessibility Conformance Report
		+
		+	ICI Sourcing Accessibility Conformance Report
		+
		+	ICI Proposal Management Accessibility Conformance Report
		+
		+	ICI SRM Accessibility Conformance Report
		+
		+	ICI Risk Management Accessibility Conformance Report
		+
		+	= Known Issues =
		+
		+	This section includes some issues that we are aware of and plan to resolve at the earliest:
		+
		+	[[File:8.2.RN T19.PNG|720px|8.2.RN T19.PNG]]
		+
		+	&nbsp;'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Associations|Association Management]] | [[Compliances|Compliance Management]] | [[Templates|Template Management]] | [[Clauses|Clause Management]] | [[Configure|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]]&nbsp;

---

Latest revision as of 13:10, 29 September 2022

ICI Release Notes - Release 8.2

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

• Technical Requirements
• Accessibility Conformance
• Known Issues

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

New Features and Enhancements

Contract Authoring & Management 

Amend contracts preserving previously negotiated terms

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

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

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

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

Send multiple agreements packaged in a single envelope for electronic signature

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

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

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

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

Quickly create and edit contract types in bulk using excel workbook

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

Advantages

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

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

How

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

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

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

Icertis Experiences

Rules functionality added to Icertis Experience for Word

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

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

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

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

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

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

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

Advantages – Avoid uploading duplicate email conversations in ICI.

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

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

Revamping ICI Salesforce User Experience

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

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

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

Some new features include:

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

Ability to preview the document from amendments sub tab.

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

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

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

New ICI Salesforce Agreement Details screen

New Add Note Dialog box

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

Salesforce – Visibility of products and services sold to customers

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

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

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

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

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

Enhancements – Mobile App Experience

Administration & Configuration

Enhanced ICI startup validation architecture

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

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

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

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

Configure E-Signature Integrations within ICI

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

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

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

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

Integrated Config keys validation framework

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

Advantages – Helps prevent issues that occur during application startup.

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

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

Configure SSO integrations within ICI

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

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

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

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

Customer-specific SAML/OAuth SSO Configurations

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

Advantages –

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

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

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

Error-handling framework

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

The framework provides the following features:

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

No unhandled exceptions emanating from the system.

Detailed logging is done in a central repository like Kibana.

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

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

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

For example: 50000030021360X8013153 (shown on User Interface)

Breakdown of the code is as follows:

5 – Severity

00 – Origin (First parameter of Exception Handling attribute)

00 – Source (mostly internal)

03 – Area (Second parameter of Exception Handling attribute)

002 – Module (Third parameter of Exception Handling attribute)

136 – SubModule (Fourth parameter of Exception Handling attribute)

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

Class decorators for Exception Handling

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

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

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

Administration & Configuration Enhancements

Reporting Analysis

Dashboard and Power BI reports for Supplier Evaluation

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

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

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

Captures evaluations that are awaiting supplier inputs for missing documents.

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

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

Advantages –

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

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

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

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

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

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

New filters added to Agreement and Amendment based SSRS reports

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

Contract Type

Org Unit

Agreement Owner

Agreement Status

Created Date (Created Date From, Created Date To)

Time Zone

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

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

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

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

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

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

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

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

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

APIs

API Management Service

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

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

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

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

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

For: API Developers | Administrators
Feature ID: 1182735

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

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

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

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

Advantages –

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

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

Additional notes:

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

For: API Developers | Administrators
Feature ID: 1182735

Framework for the composite API

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

The Composite API Framework supports the following features:

API endpoint for supporting composite structure

Request and Response representation

Validation framework for composition

Orchestration logic for composite requests

Referencing field's structure and usage

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

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

API Endpoint Changes

AI Applications

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

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

Advantages –

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

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

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

Review Obligation drawer displaying Approved Obligations in Library Obligation

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

Review Obligation drawer displaying Approved Obligations in Related Agreements

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

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

Sourcing

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

Converting RFI to RFP or RFQ

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

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

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

Value: User Experience
Feature ID: 1328960  

Shortlist Suppliers in RFx

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

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

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

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

Sourcing Enhancements

Obligation Management

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

Auto-create Obligations from Associations data

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

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

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

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

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

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

Advantages

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

Consistency in Obligation dates used across various members / obligation creators

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

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

 

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

Obligation Management Enhancements

Supplier Relationship Management

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

Supplier Profile and Supplier Master records synchronization

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

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

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

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

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

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

Value: Efficiency
For: Buyer users
Feature ID: 1420117

Supplier Relationship Management Enhancements

 

Rebates Enhancements

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

Refined seeded data model:

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

Power BI Reporting:

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

Risk Management Enhancements

Technology Updates

HTTP Artifact Binding Support for SSO Integration

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

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

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

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

Microsoft retiring basic authentication for SMTP

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

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

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

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

Microsoft retiring Outlook REST API

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

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

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

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

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

Support for StartTLS protocol

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

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

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

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

Bootstrap upgrade from version 4.5.2 to 5.1.3

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

Why – To address security vulnerabilities.

TFS ID: 1459132
 

Web Application Firewall & Azure Front Door

What –

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

Web Application Firewall (WAF) in diagnostic mode

Prevention Rule in AFD to restrict access from embargo countries.

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

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

Value: Security
For: Administrators
Feature ID: 951438

 

Technical Requirements

The Icertis Contract Intelligence (ICI) application can be accessed from any device with an Internet connection and a supported browser. All features may not be available in all environments.

The software and hardware requirements for the client system as well as the mobile application are listed in the table below:

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