Revision as of 11:56, 30 September 2020 (view source) WikiSysop (Talk | contribs) ← Older edit		Latest revision as of 05:14, 27 January 2021 (view source) WikiSysop (Talk | contribs)
(52 intermediate revisions by 4 users not shown)
Line 1:		Line 1:
−	= ICI Release Notes - Release 7.14 =	+	= ICI Release Notes - Release 7.15 =
−	== Overview of Release 7.14 ==	+	== List of Enhancements 7.15 ==
−	The 7.14 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICI functionalities and the user interface.	+	The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.
	The key enhancements of this release include:		The key enhancements of this release include:
−	*<span style="color:#008000;">'''Enhancements to the ICI Application'''</span>	+	*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>
	**'''''User Experience'''''		**'''''User Experience'''''
−	***Introducing a horizontal chevron which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron, namely Generate, Approve, Execute and Manage, prominently communicate an entity’s journey including the previous, current and possible future states of the agreement.	+	***To ensure that the agreement document is generated with the correct clauses and metadata, we now can preview an agreement from the pre-draft stage to the Approved stage, enabling a comprehensive review before publishing the contract.&nbsp;
−	***Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement.	+	***Improved usability for the global user base and their individual UI language preferences via expanded localization coverage which now includes support for localized “Reason Codes”.
−	***Facilitating one-click navigation from the ICI record to any related entities (multi-hierarchy level). For example, from RFx to Bid Response which would otherwise require multiple clicks.	+	***Friction-free collaboration enabled via the Collaboration Portal’s external user interface which now enables external users to search contract requests, agreements, associations and masterdata records.&nbsp;
−	***Providing administrators the ability to configure access control for users who are not part of the team to sections or sub-sections in the left navigation pane at the contract type level.	+	***Improved document review process where the display order for clauses in the ICI web and in Icertis Experience for Word match the order in which the clauses are configured in the respective template and generated agreement. &nbsp; &nbsp;
−	***Enhancing document usability by placing content control tags such that the end-user no longer views separate lines in the assembled document for assembled clauses that are not evaluated.	+	***Improved usability whereby the attribute multi-selection interface, when creating an agreement, can be configured as either radio buttons or checkboxes to tailor the agreement creation experience per the contract type.&nbsp;
−	**'''''Workflow Enhancements'''''	+	***Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export.&nbsp;
−	***Displaying the organization unit path of the parent document by default as the path for the associated document, so that both parent and child documents have the same organization path at the time of creation and updation.	+	***Improved usability where the sequence of values displayed in a masterdata lookup drop-down can now be configured to have the most frequently accessed values available at the top of the list.&nbsp;<br/> &nbsp;
−	***Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle.	+
−	***Providing the ability to add amendments to expired agreements. &nbsp;	+
−	***Adding a time zone attribute to provide enterprise organizations the flexibility to track the time zone or region-based activities as needed for the instance of the agreement.	+
−	***Providing the capability to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications and allowing configuration of the sender’s email ID dynamically based on the specific contract type or instance of the record.&nbsp;	+
−	*<span style="color:#008000;">'''Mobile App Updates'''</span>	+
−	**Improving the usability of the mobile app by refreshing the agreement or requests list automatically after an approve, reject or request review action is performed.	+
−	*<span style="color:#008000;">'''Enhancements to ICI API 2.0'''</span>	+
−	**Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata.	+
−	*<span style="color:#008000;">'''Enhancements to ICI Add-ins'''</span>	+	*'''''Workflow Enhancements'''''
−	**''Icertis Experience for Word''	+	**Greatly improved system availability during Publish operations where now only the contract types being published are not available during this system operation as opposed to the whole system being unavailable.
−	***Displaying a set of 30 clauses per page with pagination for easy navigation between clauses listed on the clauses, clauses in templates and clauses in agreement pages.	+	**Improved usability including the ability to create instances of associations as part of the agreement creation wizard itself.
−	***Providing extended attributes within the add-in for creation and modification of clauses and templates.	+	**To continue bringing Extension Attributes capabilities at par with regular attributes, these are now quickly viewable for easy reference in the agreement entity’s “Agreement Clauses” tab.
−	***Allowing the deviation approver to view and directly approve or reject clause deviations in an agreement from within the add-in.	+	**Agreements can be Approved or Rejected from within an agreement notification email itself making it faster to take actions on an agreement and reducing turnaround time for approval cycles.&nbsp;
−	***Displaying a validation message in clause content control enabling users to insert and tag clauses at the correct location in the document before publishing it.	+	**Expanded contract request experience now includes the ability to request Contract Terminations.
−	**''Outlook Add-in''	+	**Bulk actions support now extended to Terminating agreements in bulk to support situations that require it, such as regulatory changes, or business partner insolvency. &nbsp;
−	***Enhancing the Outlook Add-in by providing the ability to upload email in .docx or .msg format as associated documents for an agreement from within Outlook.	+	**To save time when re-instantiating a terminated agreement, due to reasons such as reviving a business relationship, you can now do so by simply adding amendments to the terminated agreement rather than by having to create a new agreement from scratch.
−	*<span style="color:#008000;">'''Enhancements to Artificial Intelligence Applications'''</span>	+	**Simplified administration of the first run default user preference which can now be pre-set or updated for users based on their location or department.
−	**Introducing a legal playbook in the WordAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.	+	**Simplified signature status labels of “External”, “Internal,” and “Fully Signed” are shown in agreement versions.
−	**Enhancing DiscoverAI to identify the different levels within a clause through a distinct visual representation of clauses with sub-sections displayed in a delineated view during the clause discovery process.	+	**Enhanced flexibility when executing a large volume of contracts by not requiring the immediate upload of documents to change the status to “Executed”. Instead, the agreement status will change from “Waiting For Signature” to “Executed – Document Upload Pending”.
−	**Enhancing the ICI discovery models to support clause and obligation discovery for additional languages such as German, Spanish and Portuguese.	+	**Enabling sharing of Associated Documents as well via the email notifications that are triggered for an agreement.
−	**Improving the inbuilt DiscoverAI model to identify additional attributes such as City, State, Zip Code, and so on.	+	**For organizational changes or employee turnover, we now provide a data management interface that enables replacing users with multiple users on supported agreement entities.
−	*<span style="color:#008000;">'''Enhancements to Reports'''</span>	+	**Support for granularly defining which agreement attributes for a given contract type should be cascaded to the agreement’s amendments via the “Is Inherit On Amendments” flag at the agreement contract type and template variable level.
−	**Introducing the Risk Assessment Report which is a trendline chart report that depicts the agreement aggregate risk score by their version. ICI’s AI algorithm identifies the playbook exceptions for a new version.	+	**In addition to the currently available functionality of all attributes to be superseded capability, we now offer the ability to selectively supersede an attribute through rules.&nbsp;
−	**Introducing the Clause Summary Report to help clause administrators to understand and assess the impact of changes made to a clause.	+	**Conditional attributes’ comparison operators now support multiple complex conditions to dynamically display attributes based on a range of business scenarios.
−	**Providing users the capability to generate a report as per the time zone of their choice from within the report itself.	+	**Simplifying agreement workflow navigation by enabling the option to show a “No Team Available” message during workflows when a team is not needed.
−	*<span style="color:#008000;">'''Improving the Icertis Experience'''</span>	+	**Expanded support for special characters in the Attribute display name for contract requests, agreements, associations and masterdata.
−	**Extending support for ICI dashboard widgets in the Icertis Experience for Salesforce Home page, so that users can perform all necessary actions from within Salesforce itself.	+	**Selectively download amendments with the corresponding parent and child associations in a zip package with corresponding sub-folders.&nbsp;
−	**Supporting auto-renewal and reset expiry functionalities in Icertis Experience for Workday, thus saving time and avoiding data duplication.	+	**Larger file size support when uploading (4GB) and downloading (6GB) larger files for masterdata and associations.&nbsp;
−	**Enhancing the generic integration framework to support custom pre- and post-processing hooks to considerably reduce implementation time, and allowing users to define and configure folder structure and file names as per the business requirement.	+	**Boost smart filter creation using string operators such as “Contains”, “Starts With”, “Does Not Contain” for the “Business Status” search facet.
−	*<span style="color:#008000;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>	+	**Expanded support for automating the bulk upload of clauses and templates reducing the dependency on manual approvals and delays in onboarding clauses and templates.
−	**In release 7.12, the Software Development Kit (SDK) was released to support partners for technical configuration. With this release, documentation for ICI coding guidelines, ICI developer methods, local environment setup using ICI binaries, and ICI customization and use cases are also available.	+	**Enhanced configurable labels for peer associations that define the contractual relationship. (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).
−	These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, platform tools, and so on.	+	&nbsp;
−	*Refer to the detailed ''[http://int-wiki.cloudapp.net:8086/ICIHelp7.14/index.php?title=ICI_Help Wiki]'' documentation for the explanation and capabilities of these and all other ICI features and functionalities.	+	*<span style="color:#800080;">'''Mobile App Updates'''</span>
−	*Refer to the [[#_Technical_Requirements_for|Technical Requirements]] for the release in this document.&nbsp;	+	**Enhancing the “Refresh” functionality for “Tasks” and “Commitment” tabs to continually show the latest changes in the status for mobile app users.
−	*Partners can access the Icertis Software Development Kit documentation [https://icertis365.sharepoint.com/sites/PartnerPortal/Shared%20Documents/Forms/AllItems.aspx?newTargetListUrl=/sites/PartnerPortal/Shared%20Documents&viewpath=/sites/PartnerPortal/Shared%20Documents/Forms/AllItems.aspx&viewid=29700541-b0d8-4150-b240-6aee2bc1cd05&id=/sites/PartnerPortal/Shared%20Documents/ICM%20Platform/Release%20Management/SDK here]. Icertis internal teams click [https://icertis365.sharepoint.com/sites/PM/Release%20Management/Forms/AllItems.aspx?csf=1&web=1&e=Pe8IWc&cid=e164ee54-11c8-49ad-a151-cc535011c793&RootFolder=/sites/PM/Release%20Management/C7%20Release%20Notes/Platform%20Core/7.12&FolderCTID=0x0120001C0CCA4C67C5754298A23D6FBE35622E here] to access the documents.	+
	&nbsp;		&nbsp;
−	== ICI Application Enhancements ==	+	*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>
		+	**Improving the filtering and searching capability which now supports searching text inside clauses or templates to allow more powerful deep searches especially when searching across large libraries.&nbsp;
		+	**Improved labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
		+	**Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;
−	<span style="color:#008000;">'''659853 – Upfront chevron view for agreement journey'''</span>	+	&nbsp;
−	In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&nbsp;<br/> Users can view the current status of an agreement on the Agreement Index or Details page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&nbsp;<br/> With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.	+	*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>
		+	**'''''Icertis Experience for Word'''''
		+	***Improving the filtering and searching capability with support for searching text inside clauses or templates to allow more powerful search especially when searching across large libraries.&nbsp;
		+	***Improving labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
		+	***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;
−	The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:	+	&nbsp;
−	1.&nbsp;Generate: Displays the list of actions taken by the user on the agreement before it is published.	+	*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>
		+	**Multiple enhancements to the AI-powered legal playbook capabilities:
		+	***Improved usability by enabling larger window views of the “Details” page and also including deviations.&nbsp;
		+	***All the playbook positions for a contract type now have the option to search and filter.&nbsp;
		+	***Administrators can create a new playbook record or update the existing one from within Icertis Experience for Word itself.
		+	**Improving the clause delineation logic so that users can rearrange the AI identified clause boundaries. You can now merge or split discovered clauses or selected text in a clause and also create sub-clauses within the discovered clause.
		+	**Extending the clause hierarchy discovery feature to support text PDFs in addition to .docx documents.&nbsp;
		+	**Improving library clause recommendations for discovered clause based on learnings from user’s action in previous discoveries.&nbsp;
		+	**Providing support for additional languages including “French”, “Dutch”, “Norwegian” and “Swedish” in AI apps.
		+	**Enabling users to flexibly leverage AI on-demand by manually triggering attribute discovery on an agreement from the “Attributes” page to accelerate workflows. Discovered values will be auto-filled in empty attributes, instead of redundant manual entry.
		+	**Enhancing and optimizing the performance of Machine Learning services to simplify deployment and run the workload on-demand while significantly reducing infrastructure management needs.
−	2. Approve:&nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&nbsp;	+	&nbsp;
−	3. Execute:&nbsp;Displays details such as internal/ external signatures that have either signed the agreement or whose signatures are pending.	+	*<span style="color:#800080;">'''Enhancements to Reports'''</span>
		+	**Introducing the “Tagged Attributes Report” enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. This will help the Legal/admin users to assess the impact of configuration changes to the clauses and templates.&nbsp;
		+	**Introducing the “Notifications History Report” for an entity, enabling users to track what notifications were sent to which recipient and when. This provides better visibility and compliance for the users.
		+	**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.
		+	**Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.
		+	**Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis. &nbsp;
		+	**Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.
		+	**Multiple localization enhancements within reports.
−	4. Manage:&nbsp;Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.	+	&nbsp;
−	'''Note''':&nbsp;	+	*<span style="color:#800080;">'''Improving the Icertis Experience'''</span>
		+	**'''''Signature Workflow'''''
		+	***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid (manual and/or electronic) signature process enables users to add and modify signatories, preview the DocuSign console, and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).
		+	***Enabling the ICI platform to support more than one E-signature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.
		+	***Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process.&nbsp;<br/> &nbsp;
		+	**'''''Icertis Experience for Salesforce'''''
		+	***Providing the ability to send success and failure alerts for improved monitoring of messages.
		+	***Triggering document assembly for automatic data sync and displaying completion notification.
		+	***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.<br/> &nbsp;
		+	**'''''Icertis Experience for MS CRM'''''
		+	***Providing server-to-server OAuth support, so that the adapter and the task service will use ‘client Id’ and ‘secret key’ from AKV, invoking the MS CRM APIs.
−	*The chevron view is only applicable to agreement contract type (agreements and amendments).	+	&nbsp;
−	*By default, the chevron is disabled; it can be enabled for selected contract types.	+
−	*The chevron labels support localization.	+
−	'''<span style="color:#008000;">512931 – Visibility of sections on the left navigation pane to non-team users</span>'''	+	*<font color="#800080">'''Enhancements to Platform Tools'''</font>
		+	**Enhancing ICI to allow administrators to promote additional configurable entities from pre-production to target environments. These include organizations and organization groups, users and user groups, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings, global and admin saved searches.
−	The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&nbsp;<br/> This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.<br/> &nbsp;	+	&nbsp;
−	<span style="color:#008000;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>	+	*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>
		+	**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.
−	With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.	+	These release notes provide an overview of the enhancements to ICI, the mobile app, the ICI experience for integrations, and so on.
−	<div class="image-green-border">Configurators can:&nbsp;</div>	+
−	*Configure a smart link across any ICI entity that defines the entity relationships.	+
−	*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities.	+
−	Users can:&nbsp;	+	&nbsp;
−	*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp;	+	== <span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancement Details</span> ==
−	*Access existing ICI grid’s capabilities such as such as export the smart link result or set to Excel/ CSV format for Smart Link results.	+
−	Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.<br/> The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.<br/> For example, consider entities related in multi-level hierarchy as Agreement > Obligations > Fulfillments. Earlier, users had to navigate through obligations in order to access the child fulfillments. Users can now navigate directly from parent agreement to grandchild fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.<br/> &nbsp;	+	<span style="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</span>
		+	Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.
		+
		+	With this release, a preview functionality is being introduced, so that the primary owner or contract creator can review whether the selected template is appropriate, the rule-based clauses have been correctly added to the agreement, among other factors, and make changes to the agreement before the version is created. The preview document would also include tagged associated documents, coming through inline or inheritance associations.
		+
		+	A preview section is available on the “Verify” stage of agreement/amendment creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. The preview is available till the Approved state of the agreement/amendment.
		+
		+	'''Note: '''This functionality is configurable. It is not available by default and can be enabled or disabled for chosen contract types.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 1.png|720px|7.15 Release Notes Screenshot 1]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">584439 – Introducing Contract Manager role for agreements&nbsp;</span>'''	+	<span style="color:#800080;">'''575640 – Creating associations on the create or edit wizard of agreement'''</span>
−	In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement. This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&nbsp;<br/> Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.<br/> With this release:&nbsp;	+	Previously in ICI, contract authors had to create associations for agreements after the agreement is already created. However, in practical terms associations such as annexures, supporting documents, SLAs, product specifications, rate tables, and so on, are all an inherent part of agreement information that is critical to the business, and some associations are required to be created along with the agreement.
−	*Assignment of the user against contract manager role in the team can be only achieved through event rules using action Add To Team.	+	Hence, the ability to create association instances as part of agreement creation or update wizard is being introduced in this release. A separate page is displayed, when creating or updating the agreement or amendment, for the user to create, view, or delete inline associations. The user also has an option to select the columns and their order in the association grid.&nbsp;
−	*Only one contract manager is available inside the agreement at any given point of time.	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 2.png|720px|7.15 Release Notes Screenshot 2]]<br/>  <br/> This new page also supports page navigation. Support is also provided to copy attribute rules, association events, and agreement assembly, in case associations are tagged in the agreement template.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 Release Notes Screenshot 3.png|720px|7.15 Release Notes Screenshot 3]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''549900 – Supporting localized reason code values as per logged in user language'''</span></div>
−	*The contract manager will have provisions same as that of primary owner.	+	Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers.
−	*The contract manager name is displayed on the agreement Summary page.	+	<div class="image-green-border">ICI now extends its localization support to reason code values. Administrators can enter the translated values in the local language, for each reason code, using the “Translations Editor” tool.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 Release Notes Screenshot 4.png|720px|7.15 Release Notes Screenshot 4]]</div>
−	*Agreements can be searched using the contract manager name.	+	Users can see localized reason codes as per their preferred language settings.&nbsp;
−	*Managing adhoc modification for contract manager role user will be restricted inside the agreement Team tab similar to primary owner role user.	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 5.png|720px|7.15 Release Notes Screenshot 5]]</div>
		+	The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''714872 – Improved document usability'''</span>	+	<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from the contract request'''</span>
−	Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&nbsp;	+	In ICI, users create and execute a termination agreement on the main agreement instance to terminate an agreement. ICI has now extended this capability to initiate the termination from contract requests too.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 6.png|720px|7.15 Release Notes Screenshot 6]]</div>
		+	Users can now enable the termination process at the contract type level using the seeded attribute "Request for Termination", select the parent contract request, and create the termination contract on a contract request. The termination instance for the contract request will have all the common attribute values inherited if the inheritance is enabled.&nbsp;
−	These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.	+	The termination record will be displayed as a peer association under the “Association” tab for the contract request. The access privileges for the contract requests termination process is controlled through role action mapping.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 7.png|720px|7.15 Release Notes Screenshot 7]]</div>
		+	&nbsp;
−	With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.	+	'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''
		+	ICI’s collaboration portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself.&nbsp;
		+
		+	In our continuous effort to improve usability, a search option has been introduced on contract requests, agreements, associations, and masterdata index pages, so that external users can easily search records. The attributes displayed as columns of the search grid are included as facets in the filter options to perform a more refined search.
		+
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''514605 – Supporting extended clause attributes in agreements'''</span>
		+
		+	In ICI, users can capture additional details for a clause in extension attributes. With this release, users can view these clause extension attributes on the agreement entity for easy reference while working with agreements.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 8.png|720px|7.15 Release Notes Screenshot 8]]</div>
		+	Users can now:&nbsp;
		+
		+	*Select and save extension attributes to display in the grid view, via the “Default Search” column functionality.
		+	*View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs.
		+	*View the hyperlink “Show Clause Information”, which displays all clause extension attributes along with clause attributes, in the same window.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 9.png|720px|7.15 Release Notes Screenshot&nbsp;9]]</div>
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''514615 – Streamlining&nbsp;the approval process over emails'''</span>
		+
		+	The approval process has now been streamlined by allowing approvers to directly approve or reject an agreement from within the email itself, through a hyperlink to the webpage, instead of logging in to the system to do so. External users, who do not have access to ICI can now review or approve the documents from the notification email, instead of sending offline copies to do so and then uploading them to ICI. This reduces the overall turnaround time and increases productivity.&nbsp;
		+
		+	The internal users are authenticated through the SSO/IDP before opening the page where the actions are to be taken. The external users are authenticated by sending them a code in the email, which has limited validity.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 10.png|720px|7.15 Release Notes Screenshot&nbsp;10]]</div>
	With this release:		With this release:
−	*All the content controls are put together in a single paragraph on any line with valid content.	+	*Administrators can add tag an Approve/Reject link in the notification template.
−	*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.	+	*Approvers/reviewers can download the agreement, modify it and upload it back to ICI based on the access provided.
−	*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules.	+	*Approvers can approve/reject the agreement or amendment from the email, only if the task approval or review is assigned to them. Based on the access, the user can approve or reject the agreement by entering notes or reasons for rejection respectively.
−	*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&nbsp;	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 11.png|720px|7.15 Release Notes Screenshot]]</div>
−	*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document.	+	&nbsp;
−	'''Note''':&nbsp;	+	<span style="color:#800080;">'''514643 – Ordering of clauses as tagged in an agreement'''</span>
−	*Only file-based clauses are supported.	+	To improve the user experience, clauses are now displayed in the same order in the agreement document as they are tagged inside the agreement, on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.
−	*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template.	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 12.png|720px|7.15 Release Notes Screenshot 12]]</div>
−	*Location-specific (such as center-justified) rule-based clauses cannot be tagged.	+	&nbsp;
−	*Numbering at the template level is not supported.	+
−	*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.	+	<span style="color:#800080;">'''617385&nbsp;– Ability to define additional clause group under clause entity'''</span>
−	*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration.	+
		+	Previously, ICI supported 3 clause groups – “Termination”, “Legal” and “None”.
		+
		+	With this release, this capability has been further enhanced so that the configurator can configure various clause group names in ICI. These clause groups can be categorized or grouped as per business requirements for better identification and negotiations during the contract workflow.
		+
		+	Administrators can now:
		+
		+	*Define and update clause groups.
		+	*Edit, delete, activate or deactivate clause group entities.
		+	*View additionally added clause group values in the clause entity when creating or editing a clause.
		+	*Search agreement records or clauses on the index page on clause group attributes with added values.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''514621 – Reviving terminated agreements'''</span>
		+
		+	Users may terminate an agreement with the other party for various business reasons. To improve usability, ICI now provides the capability to add and execute amendments on a terminated agreement. This considerably saves time for users who may want to re-instantiate their existing relationship with the other party, as they no longer need to create an entirely new agreement and go through several workflows such as clause deviations clearance, template process, and so on.
		+
		+	Adding and executing an amendment on a terminated agreement will move the agreement back to the “Executed” or “Expired” state, based on its expiry date, thus reviving the terminated agreement. The system sets an identifier attribute "Is Termination Revived" for such revived base agreements, and users can use them in search filters, notification rules while configuring saved searches, and so on.
		+
		+	'''Note: '''By default, only primary owners and contract managers can add an amendment to the terminated agreement. The access privileges are controlled through role action mapping.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 13.png|720px|7.15 Release Notes Screenshot 13]]<br/> &nbsp;</div>
		+	<span style="color:#800080;">'''514625 – Terminating agreements in bulk'''</span>
		+
		+	Users may need to terminate agreements in bulk in many business scenarios such as regulatory changes, changes in product offerings, and so on. Users can now initiate the termination of agreements in bulk, thereby saving the time to terminate agreements one by one and reducing manual errors.
		+
		+	Bulk termination is carried out using ICI’s existing “Bulk Actions” process. The termination related attributes will be pre-selected, and the Workbook for the bulk action batch will be generated with the executed agreement records from the saved search, as per the selected contract type and termination contract type.&nbsp;
		+
		+	Users can now:&nbsp;
		+
		+	*Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch. &nbsp;
		+	*Generate and view a status report for agreements terminated in bulk.&nbsp;
		+	*Create termination agreements for “Draft”, “Published” or “Send for Approval” states, as per the batch Workbook configuration for bulk action.
		+
		+	'''Note:''' All prerequisite configurations applicable for the termination workflow should also be set for the bulk termination process.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''555898 – Defining display sequence on lookup attributes at the contract type level'''</span>
−	<span style="color:#008000;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>	+	Previously in ICI, users could not define the display order for lookup attribute values in a drop-down on the UI that references masterdata. Users had to scroll through all the populated values to find the desired values during agreement creation. &nbsp;
−	Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&nbsp;<br/> With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - Allow Peer Creation Wizard, Allow Multiple Instances and Allow Two-Way Linkage.	+	Configurators can now define and maintain the display sequence for selected masterdata records, starting from 1 to n, at the contract type level, using a seeded display sequence attribute. The values will thus be displayed at the top for easier and faster selection in lookup attributes. &nbsp;
		+	This display sequence setting is supported on the create, edit, and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause entities, and template variables. The display will follow the default alphabetical order if the display sequence is not configured in masterdata.&nbsp;<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 14.png|720px|7.15 Release Notes Screenshot 14]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''</span>	+	<span style="color:#800080;">'''558605 – Viewing amendments in grid view on the agreement details page'''</span>
−	Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.<br/> With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&nbsp;<br/> For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document now displays the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents have the same organization unit path at the time of creation as well as updation.	+	Previously in ICI, users could only view the agreement’s amendments in a “Tile” view, when opened from the left navigation pane on the agreement “Details” page.&nbsp;
		+	ICI now allows users to view amendments in the “Grid” view, and toggle between grid view or tile view. The grid view is the default view for amendments and supports all existing grid functionalities, such as standard search, filter, column selection, pagination, export to CSV/Excel, and so on.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 15.png|720px|7.15 Release Notes Screenshot 15]]</div>
	&nbsp;		&nbsp;
−	This is applicable to the following associations:&nbsp;	+	<span style="color:#800080;">'''561410 – Enhancing the multi-select drop-down&nbsp;'''</span>
−	*Import of Association (Line Item)	+	The multi-select choice drop-down has been enhanced for better usability, data input, and post-selection data review of contract requests, agreements, amendments, and masterdata entities.&nbsp;
−	*Auto Attachment Association	+
−	*Obligation/ Fulfillment (Association of Association)	+
−	The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.	+	Users can now:&nbsp;
		+	*View eight options in a drop-down list (instead of six), without scrolling.&nbsp;
		+	*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&nbsp;
		+	*View all selected values at the top of the drop-down.
		+	*Deselect the selected values, individually or all with a single click, without opening the drop-down.<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 16.png|720px|7.15 Release Notes Screenshot 16]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>	+	<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>
−	Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.<br/> With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send the automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&nbsp;	+	In ICI, the configurator can filter the lookup masterdata table with “Must” and “Must Not” conditions, to achieve necessary business scenarios, while configuring a lookup attribute on contract types.&nbsp;
−	Users can now:&nbsp;	+	With this release, ICI provides the ability to configure a lookup attribute using the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup master data attribute.&nbsp;
−	*Capture multiple valid internal or external email addresses while working on agreements/ requests.	+	Configurators can now:&nbsp;
−	*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.	+
		+	*Use the "IN” operator in the lookup filter attribute on agreement contract types.&nbsp;
		+	*View the applied filter on the “Attributes” page on the UI for the selected attribute.&nbsp;
		+	*Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute. &nbsp;<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 17.png|720px|7.15 Release Notes Screenshot 17]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''583186 – Ability to add amendment on expired agreement'''</span>	+	<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>
−	Currently in ICI, users have to revive the agreement from expired to executed state by resetting its expiry date and can then add amendments to it.<br/> With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&nbsp;<br/> The Add Amendment action is configurable through role action mapping on the expired state of agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.<br/>	+	Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;
−	<span style="color:#008000;">'''593928 – Ability to configure sender email ID for automated emails'''</span><br/> Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.<br/> With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&nbsp;<br/> Administrators can now:	+	ICI now provides administrators the capability to set preferences as default, for users, according to their locations or the offices they work in. This reduces the end user’s effort of setting up the ICI account with required parameters after the first log-in and presents the system with appropriate and specific pre-settings. &nbsp;&nbsp;
−	*Configure the sender information while setting up the subscription under notifications using the specific user and/ or user attribute information in the agreement.	+	Administrators can:&nbsp;
−	*Configure the email addresses for Reply To in the subscriptions setup which recipients can revert to.	+
−	*Send automated notifications from the configured email address with the configured Reply To user email addresses.	+
		+	*Set and manage preferences for a single user through a single user update, and for multiple users through the bulk process.
		+	*View preference settings modifications details in the “History” tab for audit.&nbsp;
		+	*Search users based on parameters related to preference settings.
		+
		+	Users can:&nbsp;
		+
		+	*Access the ICI system with appropriate details as default after the first login.&nbsp;
		+	*Override the default preference settings as per individual preferences.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 18.png|720px|7.15 Release Notes Screenshot 18]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">593938&nbsp;– Time Zone support for date dependent automated processes</span>'''	+	<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading the document'''</span>
−	In ICI, there are scheduled jobs that perform certain actions on the agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&nbsp;<br/> To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.	+	Previously in ICI, users could not move agreements and amendments from “Waiting For Signature” to “Executed” state, without uploading the supporting document, in case of manually signed agreements.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 19.png|720px|7.15 Release Notes Screenshot 19]]</div>
		+	With this release, users can now skip uploading the document, to move agreements from “Waiting For External Signature” or “Waiting For Internal Signature” to the “Executed - (Pending Signed Document)” state.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 20.png|720px|7.15 Release Notes Screenshot 20]]</div>
		+	Users can then search or create a saved search for such agreements and upload the required documents later using the “Upload Fully Signed Copy” action. Notifications can be configured to inform users about skipped document uploads&nbsp;so that users can cover for delays occurring due to the scan and upload process while executing a large volume of documents.&nbsp;
−	With this release:	+	This functionality is available for agreements, amendments, and orphan amendments.<br/> &nbsp;
−	*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination).	+	<span style="color:#800080;">'''614860 – Attaching associated documents to agreement notifications'''</span>
−	*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities.	+
−	*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance.	+
−	*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance.	+
−	*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date.	+
−	'''Note''':&nbsp;The time zone-based processing can be enabled for all the contract types across the ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.	+	ICI users can share the main agreement document as part of various email notifications that get triggered for the agreement from time to time.&nbsp;
−	&nbsp;	+	In addition to the main agreement document, users can now also send associated documents as part of various email notifications that get triggered for the agreement from time to time. Access to these documents can be controlled based on the type of document – internal, external, or restricted. For example, some documents may only be shared with internal users, some may be shared with internal and external users, whereas some may not be shared with anyone.
−	'''<span style="color:#008000;">512930 – Triggering service bus events for all actions</span>'''	+	With this release:
−	For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&nbsp;<br/> With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&nbsp;<br/> The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.<br/> &nbsp;	+	*Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements, and amendments.
		+	*Users can define:
		+	**The type of notification as internal or external.&nbsp;
		+	**The type of associated document instance as internal, external, or restricted.
		+	*Based on the type of notification and type of tagged associated documents, attachments are added to the email notification.<br/> &nbsp;
−	<span style="color:#008000;">'''545126 – Availability of business status value in ICI event messages'''</span>	+	<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>
−	For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.<br/> With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.<br/> &nbsp;	+	ICI allows users to define the linkage type as a parent, child, or peer while associating peer entities with each other.
−	<span style="color:#008000;">'''574034 – Ability to have flexible contract type extension'''</span>	+	With this release, users can define configurable labels for peer associations between existing contracts by configuring the “Linkage Type” masterdata. The configurable labels define various business relationships in the context of contracts. For example, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on. The labels can be activated or deactivated as per business requirements.
−	ICI provides the flexibility to select and use masterdata attributes as extensions to agreements and associated documents at the time of instance creation. Users can create rules to add or remove these&nbsp;extended attributes&nbsp;to agreements and associated documents.	+	The configurable labels support the existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as a peer, with default peer linkage type label, defined in default peer mapping for amendment.&nbsp;
−	With this release, many ICI capabilities will now support the extension attributes in the same way as normal attributes.	+	Users can select configurable peer linkage type labels in the “Linkage Type” drop-down list and view them on various ICI functionalities such as: &nbsp;
−	Users can now:	+	*Agreement creation workflows for peer entities, assignment, and initiate termination flow.&nbsp;
		+	*Associate and Inheritance icons.
		+	*Bulk actions.
		+	*Agreement creation through business APIs.
		+	*Broadcast – “Attachments” tab and captured notes.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 21.png|720px|7.15 Release Notes Screenshot 21]]</div>
		+	'''Note:''' Multiple configurable labels are not supported for parent and child linkage types, as there is specific business logic built with them in the ICI system.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 22.png|720px|7.15 Release Notes Screenshot 22]]</div>
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''619558 – Downloading amendments using download all functionality'''</span>
−	*Configure conditional&nbsp;attributes,&nbsp;tracking&nbsp;attributes,&nbsp;computations&nbsp;(enable expressions)&nbsp;to use as&nbsp;extended&nbsp;attributes.	+	ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements.&nbsp;
−	*Save extension attributes selection as a template for reuse.	+
−	*Control access privileges&nbsp;for&nbsp;extended&nbsp;attributes based on the user role.	+
−	*Maintain audits for the&nbsp;extended&nbsp;attributes.	+
		+	With this release, users will download amendments of an agreement with corresponding parent-child associations in the downloaded zip package. This is supported on the selective download option too.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 23.png|720px|7.15 Release Notes Screenshot 23]]</div>
		+	For ease of access, each selected amendment will be downloaded with its selected associations in separate folders. The folders are named “Amendment_1”, “Amendment_2”, and so on (from oldest to latest), instead of actual amendment names. This helps to overcome the Windows limitation of supporting 260 characters in the file path and gives users the flexibility while creating association’s names.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 24.png|720px|7.15 Release Notes Screenshot 24]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''551122 – Localization support for clauses into templates'''</span>	+	<span style="color:#800080;">'''615291 – Configuring attributes inheritance for amendments at the contract type level'''</span>
−	Previously in ICI, there was no provision to have localization of clauses that could be used to create agreements in different languages. Hence, users had to create multiple templates to be able to create agreements in different languages.	+	ICI already provided the capability to exclude specific agreement attributes from being copied to amendments through technical configuration, which applied to all agreement contract types by default.&nbsp;
−	With this release, users can store the localized version of clauses and enable them when authoring and executing agreements. So, users can configure the template with localized clauses that can be used to create a localized agreement. This considerably reduces the efforts of creating and managing multiple templates to support different languages.	+	ICI now provides the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. Configurators can enable or disable the attribute’s inheritance for amendments, using the “Is Inherit On Amendments” flag, at the agreement contract type and template variable levels. Users can then copy these defined attribute values from base agreement to amendment during amendment creation.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 25.png|720px|7.15 Release Notes Screenshot 25]]</div>
		+	'''Note:&nbsp;'''
−	&nbsp;	+	*The technical configuration settings for excluding parent agreement attributes from its amendments will always take preference over the settings at agreement contract type and template level.
		+	*The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.<br/> &nbsp;
−	<span style="color:#008000;">'''550181 – Rules implementation for localized masterdata attributes'''</span><br/> Previously, localization support for masterdata attributes was limited to display localized values in lookup attributes based on language set in User Preference. If the attribute had a lookup with a localized value, its rule would not get triggered as the rule was supported only in English.	+	<span style="color:#800080;">'''614877 – Replacing a user with multiple users'''</span>
−	With this release, users will be able to:	+	In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees.&nbsp;
−	*Trigger a rule if the masterdata value has been localized on the agreement, contract request, association or the masterdata on the create/edit page.&nbsp;	+	Administrators can now:&nbsp;
−	*Trigger a rule if any lookup type attribute is updated using Icertis Experience for Word.&nbsp;	+
−	*Configure any rule type as all rules now have localization support.	+	*Replace the user with one or more users, by selecting the entity and all/selective instances of that entity, and create a saved search for records to replace users. &nbsp;
−	*Evaluation of localized values will be supported for all rule types given that the rule is configured in the English language.	+	*Validate the replaced user role against the assigned role.&nbsp;
		+	*Get a notification on adding or completing a task.&nbsp;<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 26.png|720px|7.15 Release Notes Screenshot 26]]</div>
		+	This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided to carry out these user management actions.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''551105 – Ability to define nomenclature for Association Agreement Code for Peer and child entity'''</span>	+	<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</span>
−	Previously in ICI, tracking individual associated records such as line items, rounds and awards back to their related RFQ was tedious.	+	In ICI, users could supersede all attributes of a parent agreement configured as ‘supersedable’ with values from its amendment, either manually using the “Supersede” action or automatically through the auto-supersede task. Users can now selectively supersede individual entities based on business conditions.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 27.png|720px|7.15 Release Notes Screenshot 27]]</div>
		+	The administrator can control the supersede functionality for agreements by:
−	With this release, ICI provides a capability to define a custom agreement code with reference to the peer and parent-child contract type at the time of creating associations for that agreement contract type.	+	*Enabling auto supersede option at the contract type level.
		+	*Configuring the “Supersede Rule” with “Is Supersede by Amendments” or “Is Supersede by Termination” options.&nbsp;
		+	*Selecting attributes in rule actions based on the selected Supersede On option.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 28.png|720px|7.15 Release Notes Screenshot 28]]</div>
		+	Users can view the attribute’s supersede value on the agreement and the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing ICI behavior.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 29.png|720px|7.15 Release Notes Screenshot 29]]</div>
		+	&nbsp;
−	Users can now:	+	<span style="color:#800080;">'''615293 – Showing or hiding the No Team Available message'''</span>
−	*Set a boolean attribute to define the custom nomenclature for the selected association contract type which can be either peer or parent-child.&nbsp;	+	In ICI, users may encounter specific workflow configurations, such as the self-approval process, that do not require users added to the team. The “No Team Available” message, displayed in such cases, adds to the number of non-value clicks for users to continue.&nbsp;
−	*Define the separator for the association agreement code with available options.&nbsp;	+
−	*Define the parameters for the association agreement code from the available selection attributes such as parent attribute, selected association attributes and agreement code suffix.<br/> &nbsp;	+	ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks.&nbsp;
−	<div class="image-green-border">[[File:7.12 Custom Agreement Code 3.png|720px|7.12 Custom Agreement Code 3.png]]</div>	+
−	'''Note:''' Users will be redirected to the ''Create Agreement ''wizard while creating associations for the agreement contract type that has custom nomenclature enabled.	+	Administrators can:&nbsp;
		+
		+	*Selectively enable or disable the “No Team Available” message window, at the entity contract type level, appearing at various states.&nbsp;
		+	*Disable the “No Team Available” message window altogether, at the instance level, for all entities. The instance level settings will override the entity level settings.&nbsp;
		+
		+	'''Note:''' This capability is available across ICI for all entities, events, integrations and add-ins in ICI.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''550193 – Extended number of records while adding a table as an association'''</span>	+	<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>
−	ICI supports adding associations to an agreement in various forms, such as documents and tables.	+	Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator.&nbsp;
−	With this release, ICI has now extended support to 200 records that can be assembled in an Association tagged as a table.	+	With this release, configurators can now set multiple, complex conditions to display ICI Web UI attributes dynamically, based on business scenarios. Configurators can define conditions for attributes for all entities, except for template variables. For example, the configurator can set conditions to display an attribute based on the selection of specific values in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality. &nbsp;
		+
		+	Users can now:&nbsp;
		+	*Apply multiple and complex conditions to display an attribute by enhancing the enable expression (visibility expression) for contract requests, agreements, associations, and masterdata contract types.&nbsp;
		+	*Support conditional expressions for extension attributes. &nbsp;
		+	*Define conditions with different operators based on the selected attribute datatype.&nbsp;
		+	*View the conditional attribute value according to the value entered in the attribute on which a condition is set.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 30.png|720px|7.15 Release Notes Screenshot 30]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''585000 – Ability to define parent-child relationship for peer associations'''</span>	+	<span style="color:#800080;">'''616901 – Applying facets to business status search filter'''</span>
−	ICI provides the functionality to attach associations to agreement entities. This functionality has now been enhanced with the ability to define the type of relationship (association) as Parent, Child or Peer. The Linkage Type field is enabled through technical configuration.	+	Business statuses are prominently used across all customers as they reflect the actual status in business terms compared to the system workflow status. Previously, the ICI search functionality supported filters on “Business Status” for users to narrow down results. However, manually selecting filters often becomes a tedious task in the case of several business statuses.&nbsp;
−	With this release, agreements can have only one association as a parent and all existing related agreements will be tagged as peer or child associations.	+	To provide a better user experience and ease of use, faceted filters using string operators, such as “Contains”, “Exactly”, “Starts With” and “Does Not Contain” are being added to the “Business Status” filters.<br/> &nbsp;
−	<div class="image-green-border">[[File:7.12 Linkage Type 10.png|720px|7.12 Linkage Type 10.png]]</div>	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 31.png|720px|7.15 Release Notes Screenshot 31]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''574036 – Ability to configure and control access privileges based on role'''</span>	+	<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>
−	ICI now provides the capability to define new roles for agreements, amendments and associated documents as per business requirements and control their access using existing ICI functionalities (such as Role Action Mapping, Attribute Group Privileges and Security Groups).	+	Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&nbsp;
−	'''Note:''' Custom roles do not support the workflow actions dependent upon other action requests (For example, workflow actions ''Approve'' and ''Reject'' for ''Send'' ''for'' ''Approval ''action).	+	ICI's parsing logic is now improved for handling string combinations with special and alphanumeric characters so that no errors are generated. This applies to all entities across ICI, where a combination of special characters, alphabets, and numbers can be used.<br/> &nbsp;
−	&nbsp;	+	<span style="color:#800080;">'''732929 – Uploading clauses and templates in bulk'''</span>
−	<span style="color:#008000;">'''645417 – Ability to create agreement with latest approved version while using Copy Agreement functionality'''</span>	+	New customers or new groups onboarding to ICI mostly have their templates and clauses already created in a separate file. Previously, manual efforts were needed to onboard the hundreds to thousands of templates and clauses.&nbsp;
−	Previously in ICI, the existing agreement’s template version was used to create a copy during ''Copy Record'' process even if the updated latest template was available in the system.	+	With this release, automation has been provided for bulk import using the “Legacy Upload” tool, which will reduce any human dependency, manual approvals, and delays for onboarding templates and clauses using the current capabilities. ICI administrators can now import templates and upload clauses to ICI in bulk.
−	With this release, the source agreement’s latest approved template will be selected by default to create the copy.	+	Along with the tool, an XML specification document is also released which can be used for creating tags in the input document files of clauses and templates.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''655507 – Uploading and downloading large files with the file path attribute'''</span>
		+
		+	ICI now provides support for larger files. This is applicable to masterdata and associations.
		+
		+	Users can now:
		+
		+	*Upload files up to 4GB under the file selection attribute.&nbsp;
		+	*Upload files with all supported file extensions allowed in the file selection attribute.
		+	*Download All/Download Package up to 6 GB.
		+
		+	ICI supports virus scanning of large files if the virus scan feature is enabled.<br/> &nbsp;
		+
		+	'''Note:&nbsp;'''This is not applicable for contract requests, agreements, associations with large files in the DocuSign/Adobe Sign association selection pop-up, document assembly, bulk actions, legacy upload, integrations (Salesforce, Workday, etc.), and APIs.&nbsp;The Upload/Download of the files would be supported for Azure and Windows Storage.
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">547854 – Ability to implement bulk association to support large volume data of associations</span>'''<br/> The bulk associations capability has enabled ICI to handle large number of associations in the tune of thousands, by presenting itself as a lightweight association as well as tremendously improving performance.&nbsp;	+	<span style="color:#800080;">'''618994 – Supporting special characters in agreement templates and support to skip empty columns while a saved search/association is tagged in a template'''</span>
−	The bulk association configuration has now been simplified by providing a Enable Bulk Processing flag at contract type definition level which triggers a set of defaults that has been intentionally restricted. The end user experience for the bulk association has not changed from the way that the conventional association is handled from the UI, rather the underlying data structure has been further enhanced to make it go the distance.&nbsp;	+	Previously in ICI, attribute names did not support special characters apart from _ (underscore), & (ampersand), and space.&nbsp;
−	Performance has been the key while introducing and designing this new association, which has given way to the new type of instance, namely the Proxy Instance, which is retrieved in every GET call. The actual instances are referred by using this proxy instance, thereby reducing the load on the GET APIs. Specialized GET and SET APIs have also been introduced for bulk associations to improve its adaptability and ease-of-use.	+	Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash),&nbsp;: (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (period) can be used in the display name of attributes for contract requests, agreements, associations, and masterdata contract types. The same attribute display name, as provided by the configurator, will now be displayed including special characters.
−	Bulk associations have very effectively consumed the Elastic Search Bulk API to sync a large set of data at one go, rather than the traditional way of one instance at a time, adding to the boost in performance.	+	In scenarios where the association or saved search is tagged as a table in the agreement, and a particular column of the table does not have any data, we have introduced a functionality to skip such empty columns.&nbsp;
−	Bulk association is tweaked to be able to address the large data situation that Sourcing apps require, including:	+	During template creation from Icertis Experience for Word, the configurator can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table. This property needs to be added manually in the “Content Control Properties”, at any position after the contract type GUID, separated by a '|' (pipe separator). This enables empty columns to be skipped in document assembly, thereby eliminating unnecessary empty columns in the agreement version. The order of the columns in the table is determined by the attributes in the display preference of the associated document contract type.&nbsp;
−	*Disabling the workflow.&nbsp;	+	Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export.&nbsp;
−	*Restricting the system associations to just team.&nbsp;	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 32.png|720px|7.15 Release Notes Screenshot 32]]</div>
−	*Restricting document assembly.&nbsp;	+
−	*Simplifying the association team by maintaining team at proxy level to use access level as ALL or NONE, using a layer over the existing robust ICI authorization.&nbsp;	+
−	*Restricting indexing of bulk associations attributes in the parent, which can be achieved through a technical configuration.&nbsp;	+
−	<div class="image-green-border">[[File:547854 Ability to implement bulk association to support large volume data of associations.png|720px|547854 Ability to implement bulk association to support large volume data of associations]]</div>	+
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''609753 – Enabling FIPS (Federal Information Processing Standards) compliance in ICI'''</span>	+	<span style="color:#800080;">'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''</span>
−	With this release, ICI has enabled support for FIPS compliant encryption algorithms.	+	With this release, ICI provides new controls for multi-select and single-select choice attributes.&nbsp;
		+	Users can configure an alternate UI control for drop-downs with a limited number of values for choice attributes at contract type, global attribute, and template variable levels. This improves the user experience as the number of clicks and scrolls required to view options in a drop-down are considerably reduced and provides better readability in terms of post-selection data review. &nbsp;&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 33.png|720px|7.15 Release Notes Screenshot 33]]</div>
		+	Users can select:&nbsp;
		+
		+	*The radio button for single-select choice attributes.&nbsp;
		+	*The checkbox list for multi-select choice attributes.
		+
		+	The configuration applies across ICI for the creation and editing of agreement, amendment, associated document, masterdata, and contract request entities.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 34.png|720px|7.15 Release Notes Screenshot 34]]</div>
	&nbsp;		&nbsp;
−	== Mobile App Updates ==	+	<span style="color:#4B0082;">'''593421 – Labeling agreement document versions as per signature copy'''</span>
−	'''<span style="color:#008000;">629922/635972&nbsp;– ICI mobile application management support for Microsoft Intune</span>'''<br/> In our effort to consistently improve user experience and ensure the security of our users, ICI has extended support for Microsoft Intune in our Mobile Application Management (MAM).&nbsp;	+	While agreements go through various signature states till executed, users can now navigate to the “Versions” tab and easily identify which version of the agreement is internally signed, externally signed, or fully signed.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 35.png|720px|7.15 Release Notes Screenshot 35]]</div>
		+	&nbsp;
−	Our employees, customers and partners use mobile devices for personal and professional tasks. While ensuring productivity, we also want to prevent data loss, both - intentional and unintentional. The MAM app protection policies allow users to manage and protect their organization's data within an application.	+	<span style="color:#800080;">'''872309 – Providing flexibility for assembling associations tagged as clauses'''</span>
−	The ICI Mobile App which is available in the App/Play Store is ready to use for app protection policies but not for app configuration policies.&nbsp;	+	In ICI, on publishing and updating actions, all clauses are evaluated, assembled and changes are reflected in the agreement document. However, if associations are tagged in clauses, on “Assemble Contract” and “Send For Approval” actions, clauses do not get assembled and associations do not get populated in the agreement document.
−	Microsoft Intune is a scalable cloud service architecture that leverages cloud for insights and baselines for our security policies and configuration settings. It helps safeguard data that is not managed by ICI and used by employees, customers or partners to access work files.	+	As part of our continuous effort to provide flexibility to ICI users and improve the user experience, a key “Core.Agreement.EnableDynamicClauseAssemblyPostCreate” has been introduced.&nbsp;
−	The key benefits of making ICI MS Intune-compatible include:&nbsp;&nbsp; &nbsp;	+	*If the key is enabled, when an associated document is uploaded, the entire document will be automatically assembled (Clause, Attribute, Associations, Saved Search) on the “Assemble Contract” and “Send For Approval” actions.
		+	*If the key is not enabled, the ICI document will be assembled on “Publish” and “Edit Agreement” actions. Only associations will be assembled on the “Assemble Contract” and “Send For Approval” actions.
−	*Protecting company data at the App level, for both – managed and unmanaged devices, as the management is based on user identity.	+	'''Note: '''By default, the key is set to false.<br/> &nbsp;
−	*Ensuring App layer protections are in place. For example:&nbsp;	+
−	**Entering a pin to open the App in work context	+
−	**Controlling the sharing of data between Apps	+
−	**Preventing the saving of company App data to a personal storage location	+
−	*Supporting Mobile Device Management (MDM) in addition to MAM ensuring device protection and control over App management. For example:	+
−	**Entering a pin to access the device	+
−	**Deploying managed apps to the device	+
−	**Deploying apps to devices through your MDM solution	+
−	*Using App protection policies, with or without MDM, at the same time. For example, you may choose to use a company issued phone with both – MDM and App protection policies, whereas, a personal phone may be protected by only the App protection policies.	+
−	*Applying a MAM policy to the user without setting the device state. The user will get the MAM policy on both - the BYOD (bring-your-own-devices) and the Intune-managed device. You can also apply the MAM policy based on the managed state.	+
−	'''Note:''' The policies do not apply when using the App in personal context and does not affect end-user productivity.&nbsp;	+	== Mobile App Enhancement Details ==
−	ICI Administrators can configure the ICI mobile application as a managed App using Intune configuration policies. To avail the benefits of Intune MAM settings, users have to download the ICI application from the Intune store set by the ICI Administrator and set company portal policies on their mobile phones.	+	<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span>
−	Administrators can now:	+	Icertis mobile app users perform actions such as approve, reject, and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh on the mobile app.&nbsp;Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to refresh on these actions and improve usability automatically.<br/> &nbsp;
−	*Enroll the device in Microsoft Intune.	+	<span style="color:#800080;">'''850259 – Updating logo and ICM to new guidelines'''</span>
−	*Configure the access privileges for users and user groups for ICI Mobile application using Microsoft Intune policies.	+
−	*Pre-configure the system URL so that users do not need to enter it every time.	+	As part of our new branding, “ICM” has been updated to “ICI”, and the new logo has also been added to the mobile app.<br/> &nbsp;
−	*Manage and protect organization's data within an application.	+
		+	<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span>
		+
		+	Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.
	&nbsp;		&nbsp;
−	== ICI API Enhancements&nbsp; ==	+	<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span>
		+
		+	With this release, the UI WebView component for iOS has been deprecated.<br/> &nbsp;
		+
		+	== ICI API Enhancement Details&nbsp; ==
	<div class="image-green-border">		<div class="image-green-border">
−	<span style="color:#008000;">'''553319 – Additional APIs for amendments, contract requests and searches in ICI API 2.0'''</span>	+	<span style="color:#800080;">'''704069 – Enhancing ICI API 2.0 implementation'''</span>
−	With this release, some new APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for amendments, contract requests and searches.	+	With this release, support has been added for the script and integrated attributes. They are available as cascaded attributes for lookup fields when configured at the contract type level.&nbsp;
−	These include:	+	This is applicable for visualizing, retrieval, creation, and updating of the instances of the following entities:<br/> Contract Requests
−	*Amendment APIs&nbsp;	+	*Agreements
−	**In addition to the existing APIs to create amendments, new API are provisioned to create orphan amendments in the system.	+	*Associations
−	*Contract Request APIs	+	*Amendments
−	**In addition to the existing APIs to manage contract requests, new APIs have been added to support getting and adding associations in a contract request.	+
−	*Search APIs	+	New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.
−	**Search API have been added to allow users to query agreements and related entities across multiple contract types.	+
−	**Search APIs have been added to allow creating,&nbsp;executing and deleting saved searches.	+
	&nbsp;		&nbsp;
−	</div>
−	== Enhancements to ICI Add-ins&nbsp; ==
−	<span style="color:#008000;">'''619841 – Introducing the new and improved Icertis Experience for Word'''</span>	+	<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>
−	With this release, two ICI Add-ins, NegotiateAI and Icertis Experience for Word, have been merged to provide users a seamless experience.&nbsp;<br/> Icertis Experience for Word can be leveraged to create, edit and manage templates, clauses and agreements.&nbsp;	+	ICI already supports downloading agreements.
−	It is now possible for ICI Administrators to configure and setup Icertis Experience for Word.&nbsp;	+	As part of our efforts to continually improve ICI, new API endpoints have been added in this release to download associated documents of agreements and contract requests.
−	Using Icertis Experience for Word, users:	+	&nbsp;
−	*Can work with templates, clauses and agreements.&nbsp;	+	<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>
−	*Perform different tasks such as creating, editing and deleting template variables. &nbsp;	+
−	*Tag attributes, clauses, associations, signatories and template variables.&nbsp;	+
−	'''Note: &nbsp;'''	+	A new service bus topic has been created to publish messages about workflow operations. The messages will notify if any failures are encountered during workflow actions.
−	*Users can view and edit only those clauses and agreements for which they have Manage privilege in ICI.&nbsp;	+	As workflow APIs are asynchronous, customers using Actions API and API 2.0 get a return success code, only on the initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.
−	*To edit an agreement, a user needs to download the agreement document and open it in Icertis Experience for Word.&nbsp;	+
−	<div class="image-green-border">[[File:619841 Introducing the new and improved Icertis Experience for Word.png|720px|619841 Introducing the new and improved Icertis Experience for Word.png]]</div>	+
−	&nbsp;	+
−	<span style="color:#008000;">'''487082 – Ability to perform agreement workflow actions from Icertis Experience for Word'''</span>	+	Users will now get a definite response, with required details of the error and cause on services bus. Based on the topic notification, integration developers can take follow-up actions based on success and failure.<br/> &nbsp;
−	Previously, tasks related to template and clause management could be managed using Icertis Experience for Word. However, to manage agreement workflow related tasks, users had to switch to ICI Web.&nbsp;&nbsp;&nbsp;&nbsp;	+	<br/> <span style="color:#800080;">'''660859 – Supporting TrackingId in APIs'''</span>
−	Now, users can directly perform agreement actions such as ''Send for Approval, Approve, Reject,'' and''Recall'' from Icertis Experience for Word itself, instead of navigating to ICI Web.	+	To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;
−	<div class="image-green-border">[[File:487082 Ability to perform agreement workflow actions from Icertis Experience for Word.png|720px|487082 Ability to perform agreement workflow actions from Icertis Experience for Word.png]]</div>	+
		+	For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&nbsp;
		+
		+	In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused the failure of the agreement creation. An identifier has been added to resolve this issue which subsequent APIs for correlating from a logging perspective can pass.&nbsp;
		+
		+	The following API changes have been made to ensure that the existing implementation and code remains intact:
		+
		+	*Provided support for a “TrackingId” header in every logging request.&nbsp;
		+	*Users will receive the “TrackingId” provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return).
		+	*The called API path with query string will be logged in Kibana. In Kibana, developers must look for “CorrelationID” which maps the “TrackingId” used in API.<br/> &nbsp;
		+
		+	'''Note: '''The implementation of the "TrackingId" is optional and the value must be GUID only.&nbsp;Supported in API 1.0 as well.
		+
		+	This can be used for:
		+
		+	*Related API Calls
		+	*Async operations
		+	*Bulk operations
		+	*Status check operations &nbsp; &nbsp;
		+	</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">571651 – Ability to view deviations in Icertis Experience for Word</span>'''	+	== ICI Add-ins Enhancement Details ==
−	With this release, the deviated clauses will be highlighted in the latest version of the agreement within Icertis Experience for Word. Clause deviation details such as ''Status, Deviated by, Deviated on'' as well as a link to view the agreement in ICI are displayed.	+	<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>
−	<div class="image-green-border">[[File:571651 Ability to view deviations in Icertis Experience for Word.png|720px|571651 Ability to view deviations in Icertis Experience for Word.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>	+
−	== Enhancements to Artificial Intelligence Applications in ICI ==	+
−	<span style="color:#008000;">'''510546 – Establishing a contract lineage using AI'''</span>	+	ICI users may need to modify an agreement as per business requirements by adding a clause. The clauses are displayed by “Clause Group” in the clause library by default and then searched by the clause name.&nbsp;
−	510546 – Establishing a contract lineage using AI<br/> Contracts go through multiple transformations over a period of time. During the contract negotiations, multiple attributes and clauses get added or changed. Team members, statuses, commitments and associations also get added, updated or removed. Even after the contract is executed, many addendums get added subsequently; or multiple clauses get replaced with new ones in the amendments, and so on. With such a high number of transformations, it is difficult to keep track of which clause or attribute is in force for a contract.&nbsp;	+	Multiple filters can now be configured at the template and clause level to help users easily retrieve relevant data. This improves usability for customers having a large number of clauses and templates in their clause and template library.
−	ICI has improved usability by using AI so that users can now visualize the changes done to the contract over a period of time, so that all the changes made are visible in the contract at one go.&nbsp;<br/> <br/> Contract owners can now:&nbsp;	+	Users can now:
−	*Easily see the changes in the clauses, attributes, team members, statuses, versions, commitments and associations due to developments in the contract negotiation process or due to various amendments and addendums added subsequently.	+	*Filter and search clauses and templates by clause metadata in the clause and template library respectively.
−	*Get a consolidated view of changes by grouping them into weeks, months, quarters or years.	+	*Filter and search clauses and templates by extended clause metadata in the clause and template library respectively.
−	*View the previous and changed values of individual attributes, clauses, and so on.	+	*Perform&nbsp;free-text search on the clause and template content.
−	*Track the change history of individual attributes and clauses throughout the contract life cycle, with a single click.	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 36.png|720px|7.15 Release Notes Screenshot 36]]</div>
−	<div class="image-green-border">[[File:510546 Establishing a contract lineage using AI.png|720px|510546 Establishing a contract lineage using AI]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:510546 Establishing a contract lineage using AI2.png|720px|510546 Establishing a contract lineage using A2]]</div>	+
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''575397 – Improved AI discovery model'''</span>	+	&nbsp;
−	ICI’s existing discovery model discovers 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&nbsp;<br/> With this release, the process of discovering attributes and clauses has been improved to achieve better accuracy by training the in-built discovery model with a wide variety of agreements.&nbsp;	+	== AI Applications Enhancement&nbsp;Details ==
−	The existing ObligationAI model has been enhanced to discover the obligations in a more robust and accurate manner.<br/> <br/> Key highlights of this feature are:&nbsp;	+	<span style="color:#800080;">'''727318 – Enhancing AI-powered playbook in Icertis Experience for Word'''</span>
−	*The overall discovery accuracy of out-of-the-box attributes has been improved by more than 15%.	+	ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document and allows users to review and take corrective actions on them, and assess the risk when negotiators accept these exceptions. &nbsp;
−	*With the enhanced model, the discovered values of out-of-the-box attributes such as payment terms, notice period for termination, auto renewal, evergreen agreement, compliance standard mentioned in agreement, contract value, etc. are near perfect.	+
−	*ObligationAI model is improved to identify following types of obligations out-of-the-box:	+
−	**Contract deliverables, compliance and audit, performance related obligations, project prerequisites and assumptions, incident management, contract governance, payouts and invoicing as well as contract termination.	+
−	<div class="image-green-border">&nbsp;</div> <div class="image-green-border">'''<span style="color:#008000;">602198 – Support for user created attributes in NLP search</span>'''</div>	+
−	In the previous release, the ICI AI-enabled mode of searching supported querying on system and seeded attributes using a spoken language statement.	+
−	With this release, the functionality has been enhanced to support user defined attributes as well. For example, queries such as “''contracts in region as EMEA''” would fetch the correct results even if “region” is a display name of a user defined attribute. In addition to this, NLP search is also enhanced to consider string operators such as “''starts with''” and “''contains''”, for example, “''contracts where supplier name starts with Adobe''”.<br/> &nbsp;	+	The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word.&nbsp;
−	<span style="color:#008000;">'''575399 – UX revamp to display discovered attributes and original document side-by-side'''</span>	+	With this release:
−	Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the ''Document View'' in order to review the recommendations given by the AI algorithm.	+	*Negotiators can easily review the playbook exceptions found in deviated agreement clauses on the “Agreement Clause” page. &nbsp;
		+	*Negotiators now have an option to view playbook details in a separate resizable window as the details of the playbook position for a clause can be lengthy.
		+	*As AI may not be able to find all the playbook positions for a type of a contract, an option has been added to view all playbook positions for a selected type of the contract, with options to search and filter within, so that negotiators have a ready reference for all applicable playbook positions while reviewing the contract.
		+	*Negotiators can view all the applicable playbook positions for a selected agreement clause.&nbsp;
		+	*Negotiators can request approval for a playbook exception from the playbook “Details” page.&nbsp;
		+	*Legal administrators can add a new playbook position for a type of contract or edit the existing playbook position from within Icertis Experience for Word itself.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 37.png|720px|7.15 Release Notes Screenshot 37]]</div>
		+	<br/> &nbsp;
−	With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.	+	<span style="color:#800080;">'''575475 – Automating user feedback during clause review'''</span>
−	When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.	+	ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery recommends values to users, it is expected that users would select the correct value at the time of review. &nbsp;
−	<div class="image-green-border">[[File:575399 UX revamp to display discovered entities and original document side-by-side.png|720px|575399 UX revamp to display discovered entities and original document side-by-side.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	<span style="color:#008000;">'''575455 – Improved discovery process performance and parallel processing of multiple documents'''</span>	+
−	Previously, upon receiving multiple requests, the AI discovery model added them in a queue form and processed each document sequentially. The time taken to complete the discovery of documents was also considerably high.	+	During clause review of a discovered clause, AI suggests a list of library clauses to be matched with the discovered clause. If a user selects one of them or selects a completely new clause from the library, the AI algorithm learns from such user actions. These learnings are incorporated in the next discoveries to improve the accuracy of clause recommendations.&nbsp;
−	With this release, the discovery performance has been enhanced such that multiple documents can be processed simultaneously and within lesser time. Users can now start the discovery process for their document without waiting for other discovery processes to complete. A total of 20 documents can now be processed in parallel.	+	<br/> <br/> <span style="color:#800080;">'''539492 – Rearranging discovered clauses'''</span>
−	The duration of document discovery has now been significantly reduced. On an average, the time taken to complete the discovery process of a typical contract has been improved by more than 100%. For very large contracts with 100+ pages, the discovery performance has been improved by over 500%.	+	Clauses found using DiscoverAI in an agreement document are displayed with clause categories in the “Clause Discovery” section on the web UI. Sometimes, AI may identify the clause boundaries incorrectly. Users can now review and rearrange boundaries for such clauses on the “Clause Discovery” page. &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 38.png|720px|7.15 Release Notes Screenshot 38]]</div>
		+	In rearrangement mode, users can:&nbsp;
−	&nbsp;	+	*Merge multiple discovered clauses into a single clause or split a large discovered clause into multiple clauses.&nbsp;
		+	*Identify a section of the discovered clause as its sub-clause.
		+	*Rearrange the clause hierarchy in case of misclassification by AI. Users can change clause hierarchy and identify a clause as a parent or child or peer of another clause(s).
		+	*Change the AI recommended category of a clause. &nbsp;
		+	*Choose to view only the parent clauses.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 39.png|720px|7.15 Release Notes Screenshot 39]]<br/> &nbsp;</div>
		+	<span style="color:#800080;">'''770375 – Infusing attribute discovery in agreement creation workflow'''</span>
−	== Enhancements to Reports ==	+	Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Typically, users might have already entered attribute values by the time they trigger/perform the create/publish action, thereby making the attributes discovery process redundant. Also, two different attribute pages had to be maintained, with personalization and validations not being available on the attribute discovery page.&nbsp;
−	<span style="color:#008000;">'''570314 – All core SSRS reports to only include contract types classified as Contracting'''</span>	+	With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during the agreement creation process. Discovered values will then be auto-filled in empty attributes and users can view additional potential options for the discovered attributes.&nbsp;
−	ICI offers the functionality to classify ''Business Application Type/ Contracting'' agreement type at contract type level. With this release, core reports will be limited to ''Contracting'' business&nbsp;application type.	+	Users can:&nbsp;
−	<div class="image-green-border">[[File:7.12 Reporting 1.png|720px|7.12 Reporting 1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">	+
−	Users with access to standard and insights reports will only be able to see data related to agreements with ''Contracting'' business application type. Thus, the reporting data would not contain any sourcing agreements.	+
−	This is applicable to the following reports - Agreement Clause Content Report, Agreement Deviation Report, Agreement Pending Approval Report, Agreement Pending Execution Report, Approved Request Waiting for Contract Creation Report, Average Agreement Turnaround Time Report, Clause Deviations Report, Clause Profiling Report, CLM Activity Report, Cycle Time Report, Detailed Report, Expired Agreement Report, Expiring Agreement Report, Signature Type Report, Template Clause Report, Analytics Deviation Insights Report, Analytics Deviation Insights Report – KnowMore and Analytics Clause Insights Report.	+	*View the progress of the attribute discovery.&nbsp;
		+	*Identify AI discoverable attributes on the “Attributes” page of the agreement creation wizard.
		+	*View the values recommended by AI for discoverable attributes.
		+	*View the agreement document on the “Attributes” page itself, for quick validation of AI recommended values for discoverable attributes as well as attributes values already tagged in the agreement document
−	Only contracting reports are shown in the ''Contract Type'' filter.	+	'''Note: '''When an attribute discovery is triggered from the “Attributes” page, a two-column attributes layout is converted to a single column layout to accommodate the agreement document view.<br/> &nbsp;
−	</div> <div class="image-green-border">	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 40.png|7.15 Release Notes Screenshot 40]]</div>
−	[[File:7.12 Reporting 2.png|720px|7.12 Reporting 2.png]]	+
−	</div>	+
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''567137 – Ability to add datasets for associated documents in Power BI for obligation and management'''</span>	+	<span style="color:#800080;">'''727312 – Clause hierarchy discovery in text PDFs'''</span>
−	In order to have a comprehensive view of the state of obligation, compliance users needed to have self-serve ways to build reports and dashboards. Users have now been given the flexibility to build reports on obligation compliance across hierarches – from agreements and obligations to fulfillments and fulfillment evidences.&nbsp;	+	In the previous release, clause hierarchy discovery was introduced in well-formatted .docx agreements.
−	<br/> With this release, users have the option of slice and dice for viewing and narrowing down to the right type of obligations for any given context. Advanced analytics with Power BI is the ICI offering to let customers create and view custom reports. Users will now have Obligation Management application datasets for agreement, obligation and fulfillment entities in the Power BI data model as well.&nbsp;	+	With this release, the clause delineation functionality has been enhanced to support text PDF documents and Word documents that do not use any styles. This enhancement helps to get better clause delineation, eliminates a large number of incorrectly classified clauses, and allows users to review the parent clause and child clause individually.
−	With the additional data sets, users will be able to generate reports on Power BI such as for:	+	Clause discovery processor is now trained to identify sections and sub-sections in Word and PDF documents up to 3 levels. Support for formatting-based clause delineation has also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in a hierarchical format.<br/> &nbsp;
−	*The aggregate fulfillment status for a given obligation, especially for recurring fulfillments.	+	<span style="color:#800080;">'''727314 – A generalized framework to support additional languages in AI apps'''</span>
−	*Number of days it took for a fulfillment cycle, which is for an obligation or fulfillment to move from created to approved state.	+
−	<div class="image-green-border">[[File:7.12 Reporting 3.png|720px|7.12 Reporting 3.png]]</div>	+
−	&nbsp;	+
−	<span style="color:#008000;">'''657965 – Support for Service Principal Authentication method for Power BI'''</span>	+	In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.
−	ICI has now extended support for ''Service Principal Authentication'' method to authenticate Power BI resources for advanced analytics. It has been implemented as the default method of Power BI authentication for improved security. However, the option to continue with the current authentication method of using user credentials for Power BI is still available.	+	With this release, a language framework has been implemented for AI discovery which can support a large number of languages. Using this generalized framework, DiscoverAI, NegotiateAI, and DiscoverAI for legacy apps have been enhanced to support additional European languages – French, Dutch, Norwegian, and Swedish.&nbsp;
−	&nbsp;	+	Along with the clause and obligation discovery support, AI models would be able to discover attributes too, in all the supported languages.&nbsp;<br/> &nbsp;
−	<span style="color:#008000;">'''606134 – All Power BI Reports to only include contract types classified as Contracting'''</span><br/> While creating reports, users with access to Advanced Analytics will now be able to see Business Application Type field in the agreement table of the Power BI data models.	+	== Reports Enhancement Details ==
−	Since the Create Report functionality is common to sourcing and contracting, this field allows users to segregate data for sourcing and contracting.	+	<span style="color:#800080;">'''514593 – Introducing the&nbsp;Tagged Attributes Report'''</span>
		+	With this release, a new “Tagged Attributes Report”, which helps administrators understand the complete profile of an attribute and how it has been tagged across different clauses and templates. This provides them better visibility into attribute usage and saves them considerable time.
		+
		+	This report, available on the “Reports” tile, can be accessed based on the security groups’ configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable, Attribute tagged as Clause Extended Attribute and Attribute Display Name.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''769602 – Displaying clause extension attribute summary in the Clause Summary Report'''</span>
		+
		+	Previously, the “Clause Summary Report” displayed “Clause Summary” and “Clause Version Summary” sections on the report index page.
		+
		+	In this release, the report is being enhanced to display “Clause Extension Summary” which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information of the clause extension attributes. The “Clause Extension Version Summary” will display the latest values of clause extension attributes.&nbsp;<br/> &nbsp;
		+
		+	<br/> <span style="color:#800080;">'''514611 – Introducing the&nbsp;Notifications History Report'''</span>
		+
		+	ICI administrators can set up subscriptions for different entities, for notifications to be sent to subscribed users at the occurrence of certain events. Notifications can also be sent using the broadcast functionality. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity.&nbsp;
		+
		+	The default report is available for contract requests, agreements, and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities. This report displays a list of notifications sent for an entity, including details such as the event that triggered the notification, the message body, subject, the To, CC, BCC recipient names, and email addresses; along with other details such as the attachment filename or sent date and time.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 41.png|720px|7.15 Release Notes Screenshot 41]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''573000 – Sub-role included in User Profiling, Agreements Pending Approval and Detailed Reports'''</span><br/> ICI provides the ability to define sub-roles for the approver role. With this, all the capabilities of the approver are enabled for users at the sub-role level. This capability has now been extended to reports so that users can have relevant information and make informed decisions.&nbsp;	+	<span style="color:#800080;">'''742607 – Providing additional localization support in reports'''</span>
−	With this release, the User Profiling Report, Agreements Pending Approval Report and Detailed Report have now been modified to display the approver sub-roles such as Contract Admin, Legal Approver, and so on.	+	With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas:&nbsp;
		+
		+	*Contract type names, if the respective entity has locale resource key values in the database.&nbsp;
		+	*Drop-down with Yes/No values.
		+	*Graph and Time zone tooltips, if present in the report.
		+	*Column headers. &nbsp;
		+	*Any error or validation messages.
		+	*Informative messages such as “No data available”. &nbsp;
		+
		+	<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span>
		+
		+	Previously the "Agreement Status" filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&nbsp;
		+
		+	This filter is now also available for the "Agreement Deviation Report" and "Agreements Pending Execution Report". Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">573621 - Enhancement to reports processing error message</span>'''<br/> Previously, when viewing reports resulted in processing errors, the No data available message was displayed. This message has now been modified for clarity, as follows:<br/> An error occurred during report processing, if the issue persists kindly contact customer support team.	+	<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>
−	Reports impacted include Agreement Clause Content Report, Agreement Deviation Report, Agreements Pending Approval Report, Agreements Pending Execution Report, Analytics Clause Insights Report, Analytics Deviation Insights Know More Report, Analytics Deviation Insights Report, Approved Requests Waiting For Contract Creation Report, Attribute Information Report, Attribute Value Report, Average Agreement Turn Around Time Report, Clause Deviations Report, Clause Profiling Report, Clauses Pending Approval Report, CLM Activity Report, Cycle Time Report, Detailed Report, Expired Agreements Report, Expiring Agreements Report, Masterdata Information Report, Signature Type Report and User Profiling Report.	+	The “Cycle Time Report” displays the cycles for contract requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.
		+
		+	With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''601540 - Deprecating Template Clause Report as dashboard KPI'''</span><br/> With this release, the Template Clause Report will only be accessible from the Reports tile. It has been deprecated as dashboard KPI as it only identified the average number of clauses per template across ICI and displayed a single number on the dashboard. The performance slowed down the dashboard loading process as the KPI involved calculation and aggregation of data.	+	<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>
		+
		+	With this release, the user creating a PowerBI report can hyperlink "Agreement Code" using conditional formatting with the Web URL option, so that on clicking an agreement code, the user is navigated to the corresponding agreement in ICI.&nbsp;
	&nbsp;		&nbsp;
−	== Integrations ==	+	== Integration Details ==
−	<span style="color:#008000;">'''573373/573377/573379 – Generic Integration Framework to support contract requests, associations and amendments via ASB'''</span><br/> Previously, ICI supported a generic ASB adapter for inbound and outbound integration for agreements. With this release, support is provided for contract requests, associations and amendments.&nbsp;	+	<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
−	Using an external application, users will now be able to:	+	Signing agreements is often a combination of manual signatures and electronic signatures. ICI now provides a unified flexible signature workflow to its customers, thus improving the overall turnaround time and reducing the efforts of printing and scanning manually signed documents.
−	*Create and update contract requests in ICI.	+	*Introducing the hybrid signature process allows users to use manual and electronic signature mode in a single transaction.
−	*Create associations to an existing agreement or RFx record in ICI. Users will thus be able to manage purchase requisitions, purchase orders, sourcing events and similar tasks by sending associated data.	+
−	*Update amendments to an agreement on the created, updated, approved and executed actions.&nbsp;	+
−	*Add and update team information for agreements and contract requests via ASB.	+
−	*Validate mandatory attribute fields for masterdata, agreements, contract requests or amendments.	+
−	&nbsp;	+	'''Note: '''If the DocuSign console is enabled, then the user has the provision to tag the signatories after manual signatures.&nbsp;For other signature modes, ICI relies on the provisions facilitated by your signature provider.
−	<span style="color:#008000;">'''594454 – Support for JSON files and Blob connectors'''</span><br/> Previously, CSV files were supported for masterdata upload using ASB and SFTP, whereas text-based files were supported for uploads using SFTP.&nbsp;	+	*Enabling DocuSign console with ICI that allows users to:
		+	**Add and modify the signatories.
		+	**Change the signature sequence.
		+	**Preview documents in the DocuSign console.
		+	**Tag signatories in the DocuSign console.
		+	**Use Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign.<br/> &nbsp;
−	With this release, the file-based integration will additionally support JSON file format, while also supporting Blob connectors. Additionally, a new attribute Post Process Log has been added, which indicates the Service Bus topic to which the payload will be moved after its processing.&nbsp;	+	<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>
−	In addition to post process logs, persistent logs have also been introduced in the ICI database for all processing failures. These logs will be used for reporting purposes.	+	Previously, DocuSign integration provided support for sequential signatures.
−	&nbsp;	+	This capability has now been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process.
−	<span style="color:#008000;">'''554864/554868 – Support for request review and upload actions in Salesforce grid'''</span><br/> Previously, ICI users could manage and execute contract management tasks using Salesforce Classic and Lightning user interface. The Icertis Experience for Salesforce introduced support for the following actions at the grid level - Assemble, Download and Send for Approval.&nbsp;	+	Parallel signatories can now be configured using rules or the DocuSign console.<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 42.png|720px|7.15 Release Notes Screenshot 42]]</div>
		+	<br/> <span style="color:#800080;">'''701825– Supporting multiple vendors for electronic signature'''</span>
−	With this release, support has been extended for the Send for Review and Upload document actions, thus considerably improving usability. The action buttons displayed on the user interface are based on the privileges assigned to the user via role action mapping in ICI . The agreement can be sent for review to multiple users by selecting the users from the available list.	+	Previously, ICI supported one signature vendor within one instance of ICI.&nbsp;
−	'''Note:''' If a user wants to view or edit a contract record, they will still have to double-click the contract record which will open the contract details page in Salesforce.&nbsp;	+	Now, users have the flexibility to not only select multiple electronic signature vendors in the same instance but also select the signature provider at the agreement level, based on the business requirements.
		+
		+	Users now have the flexibility to:
		+
		+	*Configure any number of signature providers for a single ICI instance, as per business requirements.
		+	*Select the signature provider of choice, at the agreement or amendment level.
		+	*Define standard rules and conditions to automatically select the signature provider of choice, based on the organizational needs.
		+	*Use multiple accounts of the same signature provider or multiple accounts of different signature providers.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''537774 – Ability to configure automated contract/task creation based on Opportunity/Quote'''</span>	+	<span style="color:#800080;">'''751651 – Publishing success/failure notification message on ASB post data sync from Salesforce'''</span>
−	Previously, users could only manage contracts using the Icertis Experience for Salesforce. They did not have the option to automatically initiate a contract based on an Opportunity or Quote status.	+	Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any agreement document changes.
−	With this release, the contract creation process has been automated based on Opportunity or Quote status, thus increasing the productivity of Salesforce users.	+	With this release:
−	Salesforce Administrators can now:	+	*Document assembly or notification to third party applications can be triggered by consuming the notification message posted on ASB via custom task implementation. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”.
		+	*Upon completion of data sync for an opportunity, the Salesforce data sync task raises a “Data Sync Passed/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for each ICI entity related to the given opportunity. The message posted on ASB will display details such as Opportunity ID, ICI entity SysId and time stamp, among other information.<br/> &nbsp;
−	*Configure the Opportunity or Quote status which can automatically trigger the contract creation.	+	<span style="color:#800080;">'''796155 –&nbsp;Enhancements to the data flow between Salesforce/MS CRM and ICI'''</span>
−	*Configure the contract type which should be used to create the contract based on data from an Opportunity or Quote.	+
−	*Define the Type of Paper to be used as Own or Third Party.	+
−	*Configure automated contract creation or automated task creation to initiate the contract creation process:	+
−	**For auto-creation of contracts, the ICI Experience for Salesforce can be configured to create a combination of contracts to be auto-generated based on the opportunity or deal type.	+
−	**For auto-creation of tasks, Salesforce users will be able to create a contract using a single button click that will assemble all necessary documents for the type of contract to be created.	+
−	&nbsp;	+	Previously, when changes were made to any Salesforce entity, then the data would sync in all related ICI contracts/requests, irrespective of their state in ICI. For example, contracts in the "Waiting For External Signature" state would not be updated via ICI UI but would get updated via data sync.
−	<span style="color:#008000;">'''574458 – ICI task integration to Salesforce tasks'''</span>	+	With this release:
−	Previously, Salesforce users could manage all internal and external tasks within Salesforce itself, but not ICI tasks.&nbsp;	+	*Changes made to a record of an entity (for example, “Opportunity”) in Salesforce will not sync to corresponding ICI contracts if they are in “Waiting For External Signature”, “Waiting For Internal Signature” or “Expired” states.&nbsp;
		+	*The data will sync only for tracking attributes if the contract is in the "Executed" state.&nbsp;
−	With this release, Salesforce users can now manage ICI tasks from within Salesforce. ICI Administrators can configure ICI task integration with Salesforce so that the tasks created in ICI are pushed to Salesforce. This allows users to view task details with attributes such as ''Task Name'', ''Status'', ''Priority'', ''Due Date'' within Salesforce itself.	+	These enhancements to the data flow, done for configurability and consistency with the ICI user interface, will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.
−	&nbsp;	+	<br/> <span style="color:#800080;">'''674469 – Generating ICI notifications and enhancing Salesforce data sync'''</span>
−	'''<span style="color:#008000;">541825 – Integration with the new eSignature platform &nbsp;&nbsp;</span>'''	+	An alert mechanism is introduced for monitoring success and failure in Icertis Experience for Salesforce integrations, using ICI/Email notifications, so that end-users get notified about success/failure in data sync.&nbsp;
−	With this release, customers can now use ''Namirial eSignAnyWhere'' as their electronic signature platform to send the agreements electronically for signatures to internal and external signatories. The invited signatories receive an email notification with a link to the document to review and sign, or decline to sign, or to delegate the action. The agreement will be executed once the document is signed electronically by all the involved signatories.&nbsp;&nbsp;	+	With this release:
−	Contract administrators can track the status of the agreements sent for signature within ICI. They can also recall the agreement sent for signature, if it was not signed by all parties.	+	*Customers will get success/failure ICI notification for data sync as well as reverse sync; and if there are any failures/exceptions in the sync process (data/reverse), the system will retry the respective operation, based on the configured retry count.&nbsp;
		+	*Additional logging has been introduced for ICI-Salesforce integration messages. Depending on the message type (success/failure), the Kibana logs will contain correlation ID, status, and JSON details.&nbsp;
−	&nbsp;	+	<br/> <span style="color:#800080;">'''679797 –&nbsp;Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use'''</span>
−	<span style="color:#008000;">'''579067 – Ability to support additional electronic signature platforms'''</span><br/> ICI enhanced the adaptability/flexibility of the eSignature interface, by making it possible to develop and integrate adapter for any new electronic signature provider based on customer requirements.	+	Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user IDs and passwords for authentication and authorization of production systems in an enterprise. Security organizations also have stringent security policies which do not approve user Id or password authentication process.&nbsp;
−	&nbsp;	+	With this release, support is provided for JWT (JSON Web Token) Bearer OAuth, a secure authentication and authorization process. This makes the ICI integration with Salesforce more secure as the actual “Modified By” user from Salesforce is set as “Modified By” user in ICI for the corresponding ICI records during data sync.&nbsp;
−	'''<span style="color:#008000;">569172 – Enabling Electronic seal tag for signing agreement documents &nbsp;&nbsp;</span>'''<br/> Previously, users were able to sign agreements based on signature tags present in the agreement templates. &nbsp;&nbsp;	+	When entities in Salesforce are updated by a user, the process builder sends a message to the ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&nbsp;
−	With this release, ICI has extended the support for enabling electronic seal tags in templates that will be used for marking electronic seals during the signature process using DocuSign. The support of electronic seals will help the organization’s legal teams to certify the integrity and the origin of the contracts.	+	Users have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''580066 – Ability to redirect emails when testing Adobe Sign eSignature on other instances'''</span><br/> As a part of the signature process, emails to signatories are triggered via Adobe Sign, starting from when the agreement is sent for signature till the agreement is signed.&nbsp;	+	<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
−	With this release, when ICI is set up on non-production environments, Adobe Sign emails can be redirected to other email addresses, so that real business users are not flooded with emails that require no action from them while the instances are being set up for testing purpose. This can be achieved through a technical configuration.	+	Previously, reverse data sync flow in MS CRM used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&nbsp;
−	&nbsp;	+	ICI now uses the client ID and secret key, instead of user ID and password, for the authentication/authorization process between MS CRM and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&nbsp;
−	<span style="color:#008000;">'''Digital Adoption Integration – Whatfix (White labelled)'''</span><br/> Enterprise customers today use dozens of applications to conduct their business functions. The introduction of any new application introduces a steep learning curve which is the number one time and adoption killer. This integration will allow users to quickly ramp up on ICI UX paradigms, help new employees onboard, and allow customers to rapidly add custom business specific guided workflows if they choose to.&nbsp;<br/> This integration will provide the following to end users:&nbsp;	+	Users will have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.<br/> &nbsp;
−	*'''Self Help Box:''' With a list of walkthroughs and links to Icertis Help content i.e when a customer searches the self help, they will see Whatfix guided walkthroughs and links to ICI help articles.	+	== ICI Platform Tools Details ==
−	*'''Guided Walkthroughs:''' Customers have guided walkthroughs for core ICI scenarios which help them to use the ICI platform only. These include:	+
−	**How to create an agreement	+
−	**How to send an agreement for approval	+
−	**How to approve an agreement	+
−	**How to create a contract request&nbsp;	+
−	**How to edit the dashboardHow to search for an agreement	+
−	'''Note:''' These workflows will not replace and are not a substitute for the business and contracts specific Whatfix workflows customers use today.&nbsp;	+	'''<span style="color:#800080;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''
−	<div class="image-green-border">[[File:7.12 Whatfix RN.png|720px|7.12 Whatfix RN.png]]</div>	+
−	These core workflows have been created by Whatfix and will be enabled on a customer by customer basis during deployment. This is done via:	+
−	*Getting a specific EnterpriseId from Whatfix.	+	With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to target environments, thus reducing the manual efforts.
−	*Updating the following config keys with the EnterpriseID:	+
−	**Core.Integration.WhatfixEnterpriseId	+	The following entities are now supported:
−	**Core.Integration.WhatfixUriWithEnterpriseId	+
−	*Whitelisting the Whatfix.com domain within the Content Security Policy.	+	*Organizations (Orgs), Organization Groups (Org Groups)
		+	*Users, User Groups, Security Groups
		+	*Role Action Mapping
		+	*Currencies
		+	*Reasons
		+	*Attribute Group
		+	*SLA Matrix
		+	*Notification Category
		+	*Default Search Columns
		+	*Cascade Team
		+	*Application Settings
		+	*Global/Admin Saved Searches
		+
		+	'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.
	&nbsp;		&nbsp;
−	== ICI Platform Tools ==	+	== Partner Enablement ==
−	<span style="color:#008000;">'''588361 – P2P support for ICI'''</span>	+	<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
−	In the 7.11 release, some enhancements were made to the Promote To Production (P2P) tool such as Vulnerability and Penetration Testing (VAPT) fixes, testing open bugs in P2P engine, some validations in the P2P engine, and an improved user interface to provide support to P2P and DevOps teams.	+	Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&nbsp;
−	With this release, changes have been made in ICI to support the P2P engine. This functionality, provided to Administrators, can promote ICI configurations/modifications that are made to ICI configurations in pre-production environments to production environments. 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.	+	As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:
−	'''Note:''' UI changes on contract type, rule set, notification template are not included.	+	*'''ICI Coding Guidelines (version 2):'''&nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.
−	&nbsp;	+	*'''ICI Customization and Use Cases (version 2): '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript.
−	<span style="color:#008000;">'''561717 – Extended support for P2P'''</span>	+	*'''Working with ICI Tasks: '''Updated for the 7.15 release.
−	With this release, changes have been made in ICI to support the P2P engine. This functionality provided to Administrators can promote ICI configurations/modifications that are made to ICI configurations in pre-production environments to production environments.	+	*'''Working with ICI Hooks:&nbsp;'''Updated for the 7.15 release.
−	This functionality:	+	*'''ICI Developer Library:''' Updated for the 7.15 release.
−	*Provides AWS Support for File Copy in Auto P2P tool.	+	*'''Local Environment Setup using ICI Binaries:''' Updated for the 7.15 release.
−	*Supports for movement of Security Group, User Group and Rule.&nbsp;	+
−	*Gets the list of entities for which ES Sync has failed when ES Sync is not successful.	+
−	*Provides upfront validation for Source and Target DB version mismatch before actual P2P validation process starts.	+
−	*Gives an option to enable DB, ES and Store backup before P2P starts which is helpful for complex P2P.	+
−	*Gives a validation error if the same entity is added multiple times, so that P2P does not fail.	+
−	*Supports saved searches.	+
−	*Supports User groups, Security Groups and Org Groups.	+
−	*Supports terminated clauses and templates. This is required when a user makes a mistake, for example in language, and this already has been pushed to production.	+
−	*Provides validations of P2P task using a small tool to validate names of all clauses and templates, thus helping to resolve issues in naming CSV files, naming in ICI, etc.	+
−	*This is checked through VBA script. Also, users may need to manually verify Is Latest which may be in an issue in environments.	+
−	'''Note:''' Customers using ICI versions before 7.12 need to upgrade to use this feature.	+	*'''Self-Serve Tools:''''''&nbsp;'''Updated for the 7.15 release.
	&nbsp;		&nbsp;
−	== Partner Enablement ==	+	== Technical Requirements for Release 7.15 ==
−	<span style="color:#008000;">'''703386 – Icertis Software Development Kit for Partner Enablement'''</span>	+	The Icertis Contract Intelligence (ICI) Proposal Management application can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available in all environments.&nbsp;
−	Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction.&nbsp;	+	The software and hardware requirements for the client system as well as mobile application are listed in the table below.
−	As part of our continuous efforts to support our partners, we have introduced the Software Development Kit (SDK) to provide them with the resources and tools that they need while implementing ICI.	+	[[File:7.15 Technical Requirements - Operating Systems.PNG|720px|7.15 Technical Requirements - Operating Systems]]
−	In this release, we have created the following three documents:	+	[[File:7.15 Technical Requirements - Browser Compatability Matrix.PNG|720px|7.15 Technical Requirements - Browser Compatibility Matrix]]
−	*'''Working with ICI Tasks:''' This document provides an insight in to the ICI Task framework that will help partners to manage, execute and monitor tasks in ICI. It includes information on the design, configuration, deployment and troubleshooting of ICI tasks.	+	[[File:7.15 Technical Requirements - Other Requirements.PNG|720px|7.15 Technical Requirements - Other Requirements]]
−	*'''Working with ICI Hooks:''' This document provides information regarding the implementation and customization of hooks for new and adhoc requirements or modifications desired by ICI customers and partners. It includes information regarding the configuration, deployment and customizations of server-side and client-side hooks.	+
−	*'''Self-Serve Tools:''' This document serves as a self-serve tool guide allowing partners and customers to perform several tasks on their own with ease. It includes the information and workflow of the following tools - Search Sync Tool, Translations Editor Tool, Improved ICI Health Check Tool, Configurations Editor Tool and Promote to Production (P2P) Tool<br/> &nbsp;	+
−	== Technical Requirements for Release 7.14 ==	+	[[File:7.15 Technical Requirements - Smartphone Mobile App.PNG|720px|7.15 Technical Requirements - Smartphone Mobile App]]
−	The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below:	+	[[File:7.15 Technical Requirements - Special Requirements 1.PNG|720px|7.15 Technical Requirements - Special Requirements 1]]
−	[[File:Technical Requirements 1.png|720px|Technical Requirements 1]]	+	[[File:7.15 Technical Requirements - Special Requirements 2.PNG|720px|7.15 Technical Requirements - Special Requirements 2]]
−	[[File:Technical Requirements 2.png|720px|Technical Requirements 2]]	+	[[File:7.15 Technical Requirements - Special Requirements 3.PNG|720px|7.15 Technical Requirements - Special Requirements 3]]
		+
		+	[[File:7.15 Technical Requirements - MS Office Plugins 1.PNG|720px|7.15 Technical Requirements - MS Office Plugins 1]]
		+
		+	[[File:7.15 Technical Requirements - MS Office Plugins 2.PNG|720px|7.15 Technical Requirements - MS Office Plugins 2]]
		+
		+	[[File:7.15 Technical Requirements - Security.PNG|720px|7.15 Technical Requirements - Security]]
		+
		+	&nbsp;
−	[[File:Technical Requirements 3.2.png|720px|Technical Requirements 3.2.png]]	+	== Known Issues ==
−	[[File:Technical Requirements 4.png|720px|Technical Requirements 4]]	+	This section includes some issues that we are aware of and plan to resolve at the earliest:
−	[[File:Technical Requirements 5.PNG|720px|Technical Requirements 5]]	+	[[File:Known Issues.PNG|720px|7.15 Known Issues]]
	&nbsp;		&nbsp;
Line 673:		Line 895:
	&nbsp;		&nbsp;
−	'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|	+	'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|

---

Latest revision as of 05:14, 27 January 2021

ICI Release Notes - Release 7.15

List of Enhancements 7.15

The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.

The key enhancements of this release include:

• Enhancements to the ICI Application
  • User Experience
    • To ensure that the agreement document is generated with the correct clauses and metadata, we now can preview an agreement from the pre-draft stage to the Approved stage, enabling a comprehensive review before publishing the contract. 
    • Improved usability for the global user base and their individual UI language preferences via expanded localization coverage which now includes support for localized “Reason Codes”.
    • Friction-free collaboration enabled via the Collaboration Portal’s external user interface which now enables external users to search contract requests, agreements, associations and masterdata records. 
    • Improved document review process where the display order for clauses in the ICI web and in Icertis Experience for Word match the order in which the clauses are configured in the respective template and generated agreement.    
    • Improved usability whereby the attribute multi-selection interface, when creating an agreement, can be configured as either radio buttons or checkboxes to tailor the agreement creation experience per the contract type. 
    • Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export. 
    • Improved usability where the sequence of values displayed in a masterdata lookup drop-down can now be configured to have the most frequently accessed values available at the top of the list. 
       

• Workflow Enhancements
  • Greatly improved system availability during Publish operations where now only the contract types being published are not available during this system operation as opposed to the whole system being unavailable.
  • Improved usability including the ability to create instances of associations as part of the agreement creation wizard itself.
  • To continue bringing Extension Attributes capabilities at par with regular attributes, these are now quickly viewable for easy reference in the agreement entity’s “Agreement Clauses” tab.
  • Agreements can be Approved or Rejected from within an agreement notification email itself making it faster to take actions on an agreement and reducing turnaround time for approval cycles. 
  • Expanded contract request experience now includes the ability to request Contract Terminations.
  • Bulk actions support now extended to Terminating agreements in bulk to support situations that require it, such as regulatory changes, or business partner insolvency.  
  • To save time when re-instantiating a terminated agreement, due to reasons such as reviving a business relationship, you can now do so by simply adding amendments to the terminated agreement rather than by having to create a new agreement from scratch.
  • Simplified administration of the first run default user preference which can now be pre-set or updated for users based on their location or department.
  • Simplified signature status labels of “External”, “Internal,” and “Fully Signed” are shown in agreement versions.
  • Enhanced flexibility when executing a large volume of contracts by not requiring the immediate upload of documents to change the status to “Executed”. Instead, the agreement status will change from “Waiting For Signature” to “Executed – Document Upload Pending”.
  • Enabling sharing of Associated Documents as well via the email notifications that are triggered for an agreement.
  • For organizational changes or employee turnover, we now provide a data management interface that enables replacing users with multiple users on supported agreement entities.
  • Support for granularly defining which agreement attributes for a given contract type should be cascaded to the agreement’s amendments via the “Is Inherit On Amendments” flag at the agreement contract type and template variable level.
  • In addition to the currently available functionality of all attributes to be superseded capability, we now offer the ability to selectively supersede an attribute through rules. 
  • Conditional attributes’ comparison operators now support multiple complex conditions to dynamically display attributes based on a range of business scenarios.
  • Simplifying agreement workflow navigation by enabling the option to show a “No Team Available” message during workflows when a team is not needed.
  • Expanded support for special characters in the Attribute display name for contract requests, agreements, associations and masterdata.
  • Selectively download amendments with the corresponding parent and child associations in a zip package with corresponding sub-folders. 
  • Larger file size support when uploading (4GB) and downloading (6GB) larger files for masterdata and associations. 
  • Boost smart filter creation using string operators such as “Contains”, “Starts With”, “Does Not Contain” for the “Business Status” search facet.
  • Expanded support for automating the bulk upload of clauses and templates reducing the dependency on manual approvals and delays in onboarding clauses and templates.
  • Enhanced configurable labels for peer associations that define the contractual relationship. (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).

 

• Mobile App Updates
  • Enhancing the “Refresh” functionality for “Tasks” and “Commitment” tabs to continually show the latest changes in the status for mobile app users.

 

• Enhancements to ICI API 2.0
  • Improving the filtering and searching capability which now supports searching text inside clauses or templates to allow more powerful deep searches especially when searching across large libraries. 
  • Improved labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
  • Defining and updating clause groups as per business requirements for easy categorization and management. 

 

• Enhancements to ICI Add-ins
  • Icertis Experience for Word
    • Improving the filtering and searching capability with support for searching text inside clauses or templates to allow more powerful search especially when searching across large libraries. 
    • Improving labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
    • Defining and updating clause groups as per business requirements for easy categorization and management. 

 

• Enhancements to Artificial Intelligence Applications
  • Multiple enhancements to the AI-powered legal playbook capabilities:
    • Improved usability by enabling larger window views of the “Details” page and also including deviations. 
    • All the playbook positions for a contract type now have the option to search and filter. 
    • Administrators can create a new playbook record or update the existing one from within Icertis Experience for Word itself.
  • Improving the clause delineation logic so that users can rearrange the AI identified clause boundaries. You can now merge or split discovered clauses or selected text in a clause and also create sub-clauses within the discovered clause.
  • Extending the clause hierarchy discovery feature to support text PDFs in addition to .docx documents. 
  • Improving library clause recommendations for discovered clause based on learnings from user’s action in previous discoveries. 
  • Providing support for additional languages including “French”, “Dutch”, “Norwegian” and “Swedish” in AI apps.
  • Enabling users to flexibly leverage AI on-demand by manually triggering attribute discovery on an agreement from the “Attributes” page to accelerate workflows. Discovered values will be auto-filled in empty attributes, instead of redundant manual entry.
  • Enhancing and optimizing the performance of Machine Learning services to simplify deployment and run the workload on-demand while significantly reducing infrastructure management needs.

 

• Enhancements to Reports
  • Introducing the “Tagged Attributes Report” enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. This will help the Legal/admin users to assess the impact of configuration changes to the clauses and templates. 
  • Introducing the “Notifications History Report” for an entity, enabling users to track what notifications were sent to which recipient and when. This provides better visibility and compliance for the users.
  • Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.
  • Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.
  • Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis.  
  • Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.
  • Multiple localization enhancements within reports.

 

• Improving the Icertis Experience
  • Signature Workflow
    • Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid (manual and/or electronic) signature process enables users to add and modify signatories, preview the DocuSign console, and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).
    • Enabling the ICI platform to support more than one E-signature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.
    • Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. 
       
  • Icertis Experience for Salesforce
    • Providing the ability to send success and failure alerts for improved monitoring of messages.
    • Triggering document assembly for automatic data sync and displaying completion notification.
    • Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.
       
  • Icertis Experience for MS CRM
    • Providing server-to-server OAuth support, so that the adapter and the task service will use ‘client Id’ and ‘secret key’ from AKV, invoking the MS CRM APIs.

 

• Enhancements to Platform Tools
  • Enhancing ICI to allow administrators to promote additional configurable entities from pre-production to target environments. These include organizations and organization groups, users and user groups, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings, global and admin saved searches.

 

• Additions to Icertis Software Development Kit for Partner Enablement
  • With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.

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

 

ICI Application Enhancement Details

514613 – Introducing the ability to preview agreements before publishing

Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.

With this release, a preview functionality is being introduced, so that the primary owner or contract creator can review whether the selected template is appropriate, the rule-based clauses have been correctly added to the agreement, among other factors, and make changes to the agreement before the version is created. The preview document would also include tagged associated documents, coming through inline or inheritance associations.

A preview section is available on the “Verify” stage of agreement/amendment creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. The preview is available till the Approved state of the agreement/amendment.

Note: This functionality is configurable. It is not available by default and can be enabled or disabled for chosen contract types.

 

575640 – Creating associations on the create or edit wizard of agreement

Previously in ICI, contract authors had to create associations for agreements after the agreement is already created. However, in practical terms associations such as annexures, supporting documents, SLAs, product specifications, rate tables, and so on, are all an inherent part of agreement information that is critical to the business, and some associations are required to be created along with the agreement.

Hence, the ability to create association instances as part of agreement creation or update wizard is being introduced in this release. A separate page is displayed, when creating or updating the agreement or amendment, for the user to create, view, or delete inline associations. The user also has an option to select the columns and their order in the association grid. 

Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers.

Users can see localized reason codes as per their preferred language settings. 

The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.

 

614944 – Initiating termination for parent agreement from the contract request

In ICI, users create and execute a termination agreement on the main agreement instance to terminate an agreement. ICI has now extended this capability to initiate the termination from contract requests too. 

Users can now enable the termination process at the contract type level using the seeded attribute "Request for Termination", select the parent contract request, and create the termination contract on a contract request. The termination instance for the contract request will have all the common attribute values inherited if the inheritance is enabled. 

The termination record will be displayed as a peer association under the “Association” tab for the contract request. The access privileges for the contract requests termination process is controlled through role action mapping.

 

506398 – Enabling search for external users with login privileges

ICI’s collaboration portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself. 

In our continuous effort to improve usability, a search option has been introduced on contract requests, agreements, associations, and masterdata index pages, so that external users can easily search records. The attributes displayed as columns of the search grid are included as facets in the filter options to perform a more refined search.

 

514605 – Supporting extended clause attributes in agreements

In ICI, users can capture additional details for a clause in extension attributes. With this release, users can view these clause extension attributes on the agreement entity for easy reference while working with agreements. 

Users can now: 

• Select and save extension attributes to display in the grid view, via the “Default Search” column functionality.
• View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs.
• View the hyperlink “Show Clause Information”, which displays all clause extension attributes along with clause attributes, in the same window.

 

514615 – Streamlining the approval process over emails

The approval process has now been streamlined by allowing approvers to directly approve or reject an agreement from within the email itself, through a hyperlink to the webpage, instead of logging in to the system to do so. External users, who do not have access to ICI can now review or approve the documents from the notification email, instead of sending offline copies to do so and then uploading them to ICI. This reduces the overall turnaround time and increases productivity. 

The internal users are authenticated through the SSO/IDP before opening the page where the actions are to be taken. The external users are authenticated by sending them a code in the email, which has limited validity. 

With this release:

• Administrators can add tag an Approve/Reject link in the notification template.
• Approvers/reviewers can download the agreement, modify it and upload it back to ICI based on the access provided.
• Approvers can approve/reject the agreement or amendment from the email, only if the task approval or review is assigned to them. Based on the access, the user can approve or reject the agreement by entering notes or reasons for rejection respectively.

 

514643 – Ordering of clauses as tagged in an agreement

To improve the user experience, clauses are now displayed in the same order in the agreement document as they are tagged inside the agreement, on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.

 

617385 – Ability to define additional clause group under clause entity

Previously, ICI supported 3 clause groups – “Termination”, “Legal” and “None”.

With this release, this capability has been further enhanced so that the configurator can configure various clause group names in ICI. These clause groups can be categorized or grouped as per business requirements for better identification and negotiations during the contract workflow.

Administrators can now:

• Define and update clause groups.
• Edit, delete, activate or deactivate clause group entities.
• View additionally added clause group values in the clause entity when creating or editing a clause.
• Search agreement records or clauses on the index page on clause group attributes with added values.
   

514621 – Reviving terminated agreements

Users may terminate an agreement with the other party for various business reasons. To improve usability, ICI now provides the capability to add and execute amendments on a terminated agreement. This considerably saves time for users who may want to re-instantiate their existing relationship with the other party, as they no longer need to create an entirely new agreement and go through several workflows such as clause deviations clearance, template process, and so on.

Adding and executing an amendment on a terminated agreement will move the agreement back to the “Executed” or “Expired” state, based on its expiry date, thus reviving the terminated agreement. The system sets an identifier attribute "Is Termination Revived" for such revived base agreements, and users can use them in search filters, notification rules while configuring saved searches, and so on.

Note: By default, only primary owners and contract managers can add an amendment to the terminated agreement. The access privileges are controlled through role action mapping. 

514625 – Terminating agreements in bulk

Users may need to terminate agreements in bulk in many business scenarios such as regulatory changes, changes in product offerings, and so on. Users can now initiate the termination of agreements in bulk, thereby saving the time to terminate agreements one by one and reducing manual errors.

Bulk termination is carried out using ICI’s existing “Bulk Actions” process. The termination related attributes will be pre-selected, and the Workbook for the bulk action batch will be generated with the executed agreement records from the saved search, as per the selected contract type and termination contract type. 

Users can now: 

• Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch.  
• Generate and view a status report for agreements terminated in bulk. 
• Create termination agreements for “Draft”, “Published” or “Send for Approval” states, as per the batch Workbook configuration for bulk action.

Note: All prerequisite configurations applicable for the termination workflow should also be set for the bulk termination process.
 

555898 – Defining display sequence on lookup attributes at the contract type level

Previously in ICI, users could not define the display order for lookup attribute values in a drop-down on the UI that references masterdata. Users had to scroll through all the populated values to find the desired values during agreement creation.  

Configurators can now define and maintain the display sequence for selected masterdata records, starting from 1 to n, at the contract type level, using a seeded display sequence attribute. The values will thus be displayed at the top for easier and faster selection in lookup attributes.  

This display sequence setting is supported on the create, edit, and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause entities, and template variables. The display will follow the default alphabetical order if the display sequence is not configured in masterdata. 
 

 

558605 – Viewing amendments in grid view on the agreement details page

Previously in ICI, users could only view the agreement’s amendments in a “Tile” view, when opened from the left navigation pane on the agreement “Details” page. 

ICI now allows users to view amendments in the “Grid” view, and toggle between grid view or tile view. The grid view is the default view for amendments and supports all existing grid functionalities, such as standard search, filter, column selection, pagination, export to CSV/Excel, and so on.

 

561410 – Enhancing the multi-select drop-down 

The multi-select choice drop-down has been enhanced for better usability, data input, and post-selection data review of contract requests, agreements, amendments, and masterdata entities. 

Users can now: 

• View eight options in a drop-down list (instead of six), without scrolling. 
• View larger values with adjusted drop-down width, according to its size, in the post-selection view. 
• View all selected values at the top of the drop-down.
• Deselect the selected values, individually or all with a single click, without opening the drop-down.
   

 

620411 – Defining IN operator when applying lookup filters

In ICI, the configurator can filter the lookup masterdata table with “Must” and “Must Not” conditions, to achieve necessary business scenarios, while configuring a lookup attribute on contract types. 

With this release, ICI provides the ability to configure a lookup attribute using the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup master data attribute. 

Configurators can now: 

• Use the "IN” operator in the lookup filter attribute on agreement contract types. 
• View the applied filter on the “Attributes” page on the UI for the selected attribute. 
• Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute.  
   

 

573339 – Managing user preferences as part of profile management

Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on. 

ICI now provides administrators the capability to set preferences as default, for users, according to their locations or the offices they work in. This reduces the end user’s effort of setting up the ICI account with required parameters after the first log-in and presents the system with appropriate and specific pre-settings.   

Administrators can: 

• Set and manage preferences for a single user through a single user update, and for multiple users through the bulk process.
• View preference settings modifications details in the “History” tab for audit. 
• Search users based on parameters related to preference settings.

Users can: 

• Access the ICI system with appropriate details as default after the first login. 
• Override the default preference settings as per individual preferences.

 

604775 – Moving agreement to executed state without uploading the document

Previously in ICI, users could not move agreements and amendments from “Waiting For Signature” to “Executed” state, without uploading the supporting document, in case of manually signed agreements. 

With this release, users can now skip uploading the document, to move agreements from “Waiting For External Signature” or “Waiting For Internal Signature” to the “Executed - (Pending Signed Document)” state. 

Users can then search or create a saved search for such agreements and upload the required documents later using the “Upload Fully Signed Copy” action. Notifications can be configured to inform users about skipped document uploads so that users can cover for delays occurring due to the scan and upload process while executing a large volume of documents. 

This functionality is available for agreements, amendments, and orphan amendments.
 

614860 – Attaching associated documents to agreement notifications

ICI users can share the main agreement document as part of various email notifications that get triggered for the agreement from time to time. 

In addition to the main agreement document, users can now also send associated documents as part of various email notifications that get triggered for the agreement from time to time. Access to these documents can be controlled based on the type of document – internal, external, or restricted. For example, some documents may only be shared with internal users, some may be shared with internal and external users, whereas some may not be shared with anyone.

With this release:

• Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements, and amendments.
• Users can define:
  • The type of notification as internal or external. 
  • The type of associated document instance as internal, external, or restricted.
• Based on the type of notification and type of tagged associated documents, attachments are added to the email notification.
   

586492 – Defining different relationship types while associating peer instance

ICI allows users to define the linkage type as a parent, child, or peer while associating peer entities with each other.

With this release, users can define configurable labels for peer associations between existing contracts by configuring the “Linkage Type” masterdata. The configurable labels define various business relationships in the context of contracts. For example, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on. The labels can be activated or deactivated as per business requirements.

The configurable labels support the existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as a peer, with default peer linkage type label, defined in default peer mapping for amendment. 

Users can select configurable peer linkage type labels in the “Linkage Type” drop-down list and view them on various ICI functionalities such as:  

• Agreement creation workflows for peer entities, assignment, and initiate termination flow. 
• Associate and Inheritance icons.
• Bulk actions.
• Agreement creation through business APIs.
• Broadcast – “Attachments” tab and captured notes.

Note: Multiple configurable labels are not supported for parent and child linkage types, as there is specific business logic built with them in the ICI system.

 

619558 – Downloading amendments using download all functionality

ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements. 

With this release, users will download amendments of an agreement with corresponding parent-child associations in the downloaded zip package. This is supported on the selective download option too.

For ease of access, each selected amendment will be downloaded with its selected associations in separate folders. The folders are named “Amendment_1”, “Amendment_2”, and so on (from oldest to latest), instead of actual amendment names. This helps to overcome the Windows limitation of supporting 260 characters in the file path and gives users the flexibility while creating association’s names.

 

615291 – Configuring attributes inheritance for amendments at the contract type level

ICI already provided the capability to exclude specific agreement attributes from being copied to amendments through technical configuration, which applied to all agreement contract types by default. 

ICI now provides the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. Configurators can enable or disable the attribute’s inheritance for amendments, using the “Is Inherit On Amendments” flag, at the agreement contract type and template variable levels. Users can then copy these defined attribute values from base agreement to amendment during amendment creation. 

Note: 

• The technical configuration settings for excluding parent agreement attributes from its amendments will always take preference over the settings at agreement contract type and template level.
• The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.
   

614877 – Replacing a user with multiple users

In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees. 

Administrators can now: 

• Replace the user with one or more users, by selecting the entity and all/selective instances of that entity, and create a saved search for records to replace users.  
• Validate the replaced user role against the assigned role. 
• Get a notification on adding or completing a task. 
   

This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided to carry out these user management actions.

 

614963 – Superseding agreement values as per amendment using rules

In ICI, users could supersede all attributes of a parent agreement configured as ‘supersedable’ with values from its amendment, either manually using the “Supersede” action or automatically through the auto-supersede task. Users can now selectively supersede individual entities based on business conditions.

The administrator can control the supersede functionality for agreements by:

• Enabling auto supersede option at the contract type level.
• Configuring the “Supersede Rule” with “Is Supersede by Amendments” or “Is Supersede by Termination” options. 
• Selecting attributes in rule actions based on the selected Supersede On option. 

Users can view the attribute’s supersede value on the agreement and the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing ICI behavior.

 

615293 – Showing or hiding the No Team Available message

In ICI, users may encounter specific workflow configurations, such as the self-approval process, that do not require users added to the team. The “No Team Available” message, displayed in such cases, adds to the number of non-value clicks for users to continue. 

ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks. 

Administrators can: 

• Selectively enable or disable the “No Team Available” message window, at the entity contract type level, appearing at various states. 
• Disable the “No Team Available” message window altogether, at the instance level, for all entities. The instance level settings will override the entity level settings. 

Note: This capability is available across ICI for all entities, events, integrations and add-ins in ICI.

 

618345 – Defining complex conditional logic for attributes visibility

Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator. 

With this release, configurators can now set multiple, complex conditions to display ICI Web UI attributes dynamically, based on business scenarios. Configurators can define conditions for attributes for all entities, except for template variables. For example, the configurator can set conditions to display an attribute based on the selection of specific values in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality.  

Users can now: 

• Apply multiple and complex conditions to display an attribute by enhancing the enable expression (visibility expression) for contract requests, agreements, associations, and masterdata contract types. 
• Support conditional expressions for extension attributes.  
• Define conditions with different operators based on the selected attribute datatype. 
• View the conditional attribute value according to the value entered in the attribute on which a condition is set.

 

616901 – Applying facets to business status search filter

Business statuses are prominently used across all customers as they reflect the actual status in business terms compared to the system workflow status. Previously, the ICI search functionality supported filters on “Business Status” for users to narrow down results. However, manually selecting filters often becomes a tedious task in the case of several business statuses. 

To provide a better user experience and ease of use, faceted filters using string operators, such as “Contains”, “Exactly”, “Starts With” and “Does Not Contain” are being added to the “Business Status” filters.
 

 

694211 – Improving handling of exceptions for string combinations

Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions. 

ICI's parsing logic is now improved for handling string combinations with special and alphanumeric characters so that no errors are generated. This applies to all entities across ICI, where a combination of special characters, alphabets, and numbers can be used.
 

732929 – Uploading clauses and templates in bulk

New customers or new groups onboarding to ICI mostly have their templates and clauses already created in a separate file. Previously, manual efforts were needed to onboard the hundreds to thousands of templates and clauses. 

With this release, automation has been provided for bulk import using the “Legacy Upload” tool, which will reduce any human dependency, manual approvals, and delays for onboarding templates and clauses using the current capabilities. ICI administrators can now import templates and upload clauses to ICI in bulk.

Along with the tool, an XML specification document is also released which can be used for creating tags in the input document files of clauses and templates.
 

655507 – Uploading and downloading large files with the file path attribute

ICI now provides support for larger files. This is applicable to masterdata and associations.

Users can now:

• Upload files up to 4GB under the file selection attribute. 
• Upload files with all supported file extensions allowed in the file selection attribute.
• Download All/Download Package up to 6 GB.

ICI supports virus scanning of large files if the virus scan feature is enabled.
 

Note: This is not applicable for contract requests, agreements, associations with large files in the DocuSign/Adobe Sign association selection pop-up, document assembly, bulk actions, legacy upload, integrations (Salesforce, Workday, etc.), and APIs. The Upload/Download of the files would be supported for Azure and Windows Storage.

 

618994 – Supporting special characters in agreement templates and support to skip empty columns while a saved search/association is tagged in a template

Previously in ICI, attribute names did not support special characters apart from _ (underscore), & (ampersand), and space. 

Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash), : (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (period) can be used in the display name of attributes for contract requests, agreements, associations, and masterdata contract types. The same attribute display name, as provided by the configurator, will now be displayed including special characters.

In scenarios where the association or saved search is tagged as a table in the agreement, and a particular column of the table does not have any data, we have introduced a functionality to skip such empty columns. 

During template creation from Icertis Experience for Word, the configurator can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table. This property needs to be added manually in the “Content Control Properties”, at any position after the contract type GUID, separated by a '|' (pipe separator). This enables empty columns to be skipped in document assembly, thereby eliminating unnecessary empty columns in the agreement version. The order of the columns in the table is determined by the attributes in the display preference of the associated document contract type. 

Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export. 

 

573336 – Displaying drop-downs as radio buttons or checkbox list for user selection

With this release, ICI provides new controls for multi-select and single-select choice attributes. 

Users can configure an alternate UI control for drop-downs with a limited number of values for choice attributes at contract type, global attribute, and template variable levels. This improves the user experience as the number of clicks and scrolls required to view options in a drop-down are considerably reduced and provides better readability in terms of post-selection data review.   

Users can select: 

• The radio button for single-select choice attributes. 
• The checkbox list for multi-select choice attributes.

The configuration applies across ICI for the creation and editing of agreement, amendment, associated document, masterdata, and contract request entities.

 

593421 – Labeling agreement document versions as per signature copy

While agreements go through various signature states till executed, users can now navigate to the “Versions” tab and easily identify which version of the agreement is internally signed, externally signed, or fully signed.

 

872309 – Providing flexibility for assembling associations tagged as clauses

In ICI, on publishing and updating actions, all clauses are evaluated, assembled and changes are reflected in the agreement document. However, if associations are tagged in clauses, on “Assemble Contract” and “Send For Approval” actions, clauses do not get assembled and associations do not get populated in the agreement document.

As part of our continuous effort to provide flexibility to ICI users and improve the user experience, a key “Core.Agreement.EnableDynamicClauseAssemblyPostCreate” has been introduced. 

• If the key is enabled, when an associated document is uploaded, the entire document will be automatically assembled (Clause, Attribute, Associations, Saved Search) on the “Assemble Contract” and “Send For Approval” actions.
• If the key is not enabled, the ICI document will be assembled on “Publish” and “Edit Agreement” actions. Only associations will be assembled on the “Assemble Contract” and “Send For Approval” actions.

Note: By default, the key is set to false.
 

Mobile App Enhancement Details

773907 – Refreshing tasks and commitments

Icertis mobile app users perform actions such as approve, reject, and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh on the mobile app. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to refresh on these actions and improve usability automatically.
 

850259 – Updating logo and ICM to new guidelines

As part of our new branding, “ICM” has been updated to “ICI”, and the new logo has also been added to the mobile app.
 

773923 – Changing compatibility in Android 11

Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.

 

773917 – Deprecating the UI WebView component for iOS

With this release, the UI WebView component for iOS has been deprecated.
 

ICI API Enhancement Details 

 

ICI Add-ins Enhancement Details

668859 – Enhancing filtering and searching of clauses  

ICI users may need to modify an agreement as per business requirements by adding a clause. The clauses are displayed by “Clause Group” in the clause library by default and then searched by the clause name. 

Multiple filters can now be configured at the template and clause level to help users easily retrieve relevant data. This improves usability for customers having a large number of clauses and templates in their clause and template library.

Users can now:

• Filter and search clauses and templates by clause metadata in the clause and template library respectively.
• Filter and search clauses and templates by extended clause metadata in the clause and template library respectively.
• Perform free-text search on the clause and template content.

 

 

AI Applications Enhancement Details

727318 – Enhancing AI-powered playbook in Icertis Experience for Word

ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document and allows users to review and take corrective actions on them, and assess the risk when negotiators accept these exceptions.  

The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word. 

With this release:

• Negotiators can easily review the playbook exceptions found in deviated agreement clauses on the “Agreement Clause” page.  
• Negotiators now have an option to view playbook details in a separate resizable window as the details of the playbook position for a clause can be lengthy.
• As AI may not be able to find all the playbook positions for a type of a contract, an option has been added to view all playbook positions for a selected type of the contract, with options to search and filter within, so that negotiators have a ready reference for all applicable playbook positions while reviewing the contract.
• Negotiators can view all the applicable playbook positions for a selected agreement clause. 
• Negotiators can request approval for a playbook exception from the playbook “Details” page. 
• Legal administrators can add a new playbook position for a type of contract or edit the existing playbook position from within Icertis Experience for Word itself.

 

575475 – Automating user feedback during clause review

ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery recommends values to users, it is expected that users would select the correct value at the time of review.  

During clause review of a discovered clause, AI suggests a list of library clauses to be matched with the discovered clause. If a user selects one of them or selects a completely new clause from the library, the AI algorithm learns from such user actions. These learnings are incorporated in the next discoveries to improve the accuracy of clause recommendations. 

539492 – Rearranging discovered clauses

Clauses found using DiscoverAI in an agreement document are displayed with clause categories in the “Clause Discovery” section on the web UI. Sometimes, AI may identify the clause boundaries incorrectly. Users can now review and rearrange boundaries for such clauses on the “Clause Discovery” page.  

In rearrangement mode, users can: 

• Merge multiple discovered clauses into a single clause or split a large discovered clause into multiple clauses. 
• Identify a section of the discovered clause as its sub-clause.
• Rearrange the clause hierarchy in case of misclassification by AI. Users can change clause hierarchy and identify a clause as a parent or child or peer of another clause(s).
• Change the AI recommended category of a clause.  
• Choose to view only the parent clauses.

770375 – Infusing attribute discovery in agreement creation workflow

Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Typically, users might have already entered attribute values by the time they trigger/perform the create/publish action, thereby making the attributes discovery process redundant. Also, two different attribute pages had to be maintained, with personalization and validations not being available on the attribute discovery page. 

With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during the agreement creation process. Discovered values will then be auto-filled in empty attributes and users can view additional potential options for the discovered attributes. 

Users can: 

• View the progress of the attribute discovery. 
• Identify AI discoverable attributes on the “Attributes” page of the agreement creation wizard.
• View the values recommended by AI for discoverable attributes.
• View the agreement document on the “Attributes” page itself, for quick validation of AI recommended values for discoverable attributes as well as attributes values already tagged in the agreement document

Note: When an attribute discovery is triggered from the “Attributes” page, a two-column attributes layout is converted to a single column layout to accommodate the agreement document view.
 

 

727312 – Clause hierarchy discovery in text PDFs

In the previous release, clause hierarchy discovery was introduced in well-formatted .docx agreements.

With this release, the clause delineation functionality has been enhanced to support text PDF documents and Word documents that do not use any styles. This enhancement helps to get better clause delineation, eliminates a large number of incorrectly classified clauses, and allows users to review the parent clause and child clause individually.

Clause discovery processor is now trained to identify sections and sub-sections in Word and PDF documents up to 3 levels. Support for formatting-based clause delineation has also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in a hierarchical format.
 

727314 – A generalized framework to support additional languages in AI apps

In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.

With this release, a language framework has been implemented for AI discovery which can support a large number of languages. Using this generalized framework, DiscoverAI, NegotiateAI, and DiscoverAI for legacy apps have been enhanced to support additional European languages – French, Dutch, Norwegian, and Swedish. 

Along with the clause and obligation discovery support, AI models would be able to discover attributes too, in all the supported languages. 
 

Reports Enhancement Details

514593 – Introducing the Tagged Attributes Report

With this release, a new “Tagged Attributes Report”, which helps administrators understand the complete profile of an attribute and how it has been tagged across different clauses and templates. This provides them better visibility into attribute usage and saves them considerable time.

This report, available on the “Reports” tile, can be accessed based on the security groups’ configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable, Attribute tagged as Clause Extended Attribute and Attribute Display Name.
 

769602 – Displaying clause extension attribute summary in the Clause Summary Report

Previously, the “Clause Summary Report” displayed “Clause Summary” and “Clause Version Summary” sections on the report index page.

In this release, the report is being enhanced to display “Clause Extension Summary” which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information of the clause extension attributes. The “Clause Extension Version Summary” will display the latest values of clause extension attributes. 
 

514611 – Introducing the Notifications History Report

ICI administrators can set up subscriptions for different entities, for notifications to be sent to subscribed users at the occurrence of certain events. Notifications can also be sent using the broadcast functionality. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. 

The default report is available for contract requests, agreements, and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities. This report displays a list of notifications sent for an entity, including details such as the event that triggered the notification, the message body, subject, the To, CC, BCC recipient names, and email addresses; along with other details such as the attachment filename or sent date and time. 

 

742607 – Providing additional localization support in reports

With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas: 

• Contract type names, if the respective entity has locale resource key values in the database. 
• Drop-down with Yes/No values.
• Graph and Time zone tooltips, if present in the report.
• Column headers.  
• Any error or validation messages.
• Informative messages such as “No data available”.  

583297 – Filtering additional reports by agreement status

Previously the "Agreement Status" filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”. 

This filter is now also available for the "Agreement Deviation Report" and "Agreements Pending Execution Report". Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.

 

746607 – Enhancing the Cycle Time Report

The “Cycle Time Report” displays the cycles for contract requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.

With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.

 

737196 – Adding hyperlink in PowerBI for agreement code

With this release, the user creating a PowerBI report can hyperlink "Agreement Code" using conditional formatting with the Web URL option, so that on clicking an agreement code, the user is navigated to the corresponding agreement in ICI. 

 

Integration Details

605434 – Providing a unified flexible signature process

Signing agreements is often a combination of manual signatures and electronic signatures. ICI now provides a unified flexible signature workflow to its customers, thus improving the overall turnaround time and reducing the efforts of printing and scanning manually signed documents.

• Introducing the hybrid signature process allows users to use manual and electronic signature mode in a single transaction.

Note: If the DocuSign console is enabled, then the user has the provision to tag the signatories after manual signatures. For other signature modes, ICI relies on the provisions facilitated by your signature provider.

• Enabling DocuSign console with ICI that allows users to:
  • Add and modify the signatories.
  • Change the signature sequence.
  • Preview documents in the DocuSign console.
  • Tag signatories in the DocuSign console.
  • Use Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign.
     

641289 – Allowing parallel signatures using DocuSign

Previously, DocuSign integration provided support for sequential signatures.

This capability has now been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process.

Parallel signatories can now be configured using rules or the DocuSign console.
 

701825– Supporting multiple vendors for electronic signature

Previously, ICI supported one signature vendor within one instance of ICI. 

Now, users have the flexibility to not only select multiple electronic signature vendors in the same instance but also select the signature provider at the agreement level, based on the business requirements.

Users now have the flexibility to:

• Configure any number of signature providers for a single ICI instance, as per business requirements.
• Select the signature provider of choice, at the agreement or amendment level.
• Define standard rules and conditions to automatically select the signature provider of choice, based on the organizational needs.
• Use multiple accounts of the same signature provider or multiple accounts of different signature providers.

 

751651 – Publishing success/failure notification message on ASB post data sync from Salesforce

Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any agreement document changes.

With this release:

• Document assembly or notification to third party applications can be triggered by consuming the notification message posted on ASB via custom task implementation. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”.
• Upon completion of data sync for an opportunity, the Salesforce data sync task raises a “Data Sync Passed/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for each ICI entity related to the given opportunity. The message posted on ASB will display details such as Opportunity ID, ICI entity SysId and time stamp, among other information.
   

796155 – Enhancements to the data flow between Salesforce/MS CRM and ICI

Previously, when changes were made to any Salesforce entity, then the data would sync in all related ICI contracts/requests, irrespective of their state in ICI. For example, contracts in the "Waiting For External Signature" state would not be updated via ICI UI but would get updated via data sync.

With this release:

• Changes made to a record of an entity (for example, “Opportunity”) in Salesforce will not sync to corresponding ICI contracts if they are in “Waiting For External Signature”, “Waiting For Internal Signature” or “Expired” states. 
• The data will sync only for tracking attributes if the contract is in the "Executed" state. 

These enhancements to the data flow, done for configurability and consistency with the ICI user interface, will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.

674469 – Generating ICI notifications and enhancing Salesforce data sync

An alert mechanism is introduced for monitoring success and failure in Icertis Experience for Salesforce integrations, using ICI/Email notifications, so that end-users get notified about success/failure in data sync. 

With this release:

• Customers will get success/failure ICI notification for data sync as well as reverse sync; and if there are any failures/exceptions in the sync process (data/reverse), the system will retry the respective operation, based on the configured retry count. 
• Additional logging has been introduced for ICI-Salesforce integration messages. Depending on the message type (success/failure), the Kibana logs will contain correlation ID, status, and JSON details. 

679797 – Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use

Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user IDs and passwords for authentication and authorization of production systems in an enterprise. Security organizations also have stringent security policies which do not approve user Id or password authentication process. 

With this release, support is provided for JWT (JSON Web Token) Bearer OAuth, a secure authentication and authorization process. This makes the ICI integration with Salesforce more secure as the actual “Modified By” user from Salesforce is set as “Modified By” user in ICI for the corresponding ICI records during data sync. 

When entities in Salesforce are updated by a user, the process builder sends a message to the ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records. 

Users have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.

 

749083 – Supporting OAuth in the MS CRM adapter

Previously, reverse data sync flow in MS CRM used service user login credentials to invoke MS CRM APIs when data was updated in ICI. 

ICI now uses the client ID and secret key, instead of user ID and password, for the authentication/authorization process between MS CRM and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs. 

Users will have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.
 

ICI Platform Tools Details

514636 – Enhancing P2P Tool in ICI Admin user interface

With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to target environments, thus reducing the manual efforts.

The following entities are now supported:

• Organizations (Orgs), Organization Groups (Org Groups)
• Users, User Groups, Security Groups
• Role Action Mapping
• Currencies
• Reasons
• Attribute Group
• SLA Matrix
• Notification Category
• Default Search Columns
• Cascade Team
• Application Settings
• Global/Admin Saved Searches

Note: Customers using ICI versions before 7.15 will need to upgrade to use this feature.

 

Partner Enablement

703386 – Icertis Software Development Kit for Partner Enablement

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI. 

As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:

• ICI Coding Guidelines (version 2): This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.

• ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript.

• Working with ICI Tasks: Updated for the 7.15 release.

• Working with ICI Hooks: Updated for the 7.15 release.

• ICI Developer Library: Updated for the 7.15 release.

• Local Environment Setup using ICI Binaries: Updated for the 7.15 release.

• 'Self-Serve Tools:' Updated for the 7.15 release.

 

Technical Requirements for Release 7.15

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

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

 

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 | ICI Business Apps Release Notes |