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.

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.

549900 – Supporting localized reason code values as per logged in user language

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.

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.

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

704069 – Enhancing ICI API 2.0 implementation

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.

This is applicable for visualizing, retrieval, creation, and updating of the instances of the following entities:
Contract Requests

Agreements
Associations
Amendments

New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.

756815 – Downloading associated document API

ICI already supports downloading agreements.

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.

731961 – Provisioning success or failure message for workflow operations

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.

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.

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.

660859 – Supporting TrackingId in APIs

To work with ICI entities, at times, multiple API calls are needed to complete an operation.

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

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.

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

Note: The implementation of the "TrackingId" is optional and the value must be GUID only. Supported in API 1.0 as well.

This can be used for:

Related API Calls
Async operations
Bulk operations
Status check operations

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:

Contents

ICI Release Notes - Release 7.15[edit]

Overview of Release 7.15[edit]

ICI Application Enhancements[edit]

Mobile App Updates[edit]

ICI API Enhancements [edit]

Enhancements to ICI Add-ins [edit]

Enhancements to Artificial Intelligence Applications in ICI[edit]

Enhancements to Reports[edit]

Integrations[edit]

ICI Platform Tools[edit]

Partner Enablement[edit]

Technical Requirements for Release 7.15[edit]

Latest revision as of 05:14, 27 January 2021

Contents

ICI Release Notes - Release 7.15

List of Enhancements 7.15

ICI Application Enhancement Details

Mobile App Enhancement Details

ICI API Enhancement Details

ICI Add-ins Enhancement Details

AI Applications Enhancement Details

Reports Enhancement Details

Integration Details

ICI Platform Tools Details

Partner Enablement

Technical Requirements for Release 7.15

Known Issues

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Tools

@@ Line 2: / Line 2: @@
 = ICI&nbsp;Release Notes - Release 7.15 =
-== <span style="color:#800080;">Overview of Release 7.15</span> ==
+== List of Enhancements&nbsp;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.
@@ Line 10: / Line 10: @@
 *<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>
 **'''''User Experience'''''
-***Introducing &nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation.
+***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;
-***Providing &nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally.
+***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”.
-***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results.
+***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;
-***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience.
+***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;
-***Viewing amendments in the grid view by default, for ease of use.
+***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;
-***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience.
+***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;
-***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels.
+***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;
-***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.
-**'''''Workflow Enhancements'''''
+*'''''Workflow Enhancements'''''
-***Introducing &nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability.
+**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.
-***Allowing &nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience.
+**Improved usability including the ability to create instances of associations as part of the agreement creation wizard itself.
-***Viewing clause extension attributes on the agreement entity for easy reference.
+**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.
-***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles.
+**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;
-***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch.
+**Expanded contract request experience now includes the ability to request Contract Terminations.
-***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&nbsp;
+**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;
-***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &nbsp;
+**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.
-***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable.
+**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.
-***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents.
+**Simplified signature status labels of “External”, “Internal,” and “Fully Signed” are shown in agreement versions.
-***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately.
+**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”.
-***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &nbsp; entities with one or more users, by selecting a subset of an entity &nbsp; or on all instances of the entity, for all records available for the user.
+**Enabling sharing of Associated Documents as well via the email notifications that are triggered for an agreement.
-***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level.
+**For organizational changes or employee turnover, we now provide a data management interface that enables replacing users with multiple users on supported agreement entities.
-***Providing the capability to control the supersede functionality for agreements by configuring rules.
+**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.
-***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios.
+**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;
-***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks.
+**Conditional attributes’ comparison operators now support multiple complex conditions to dynamically display attributes based on a range of business scenarios.
-***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata.
+**Simplifying agreement workflow navigation by enabling the option to show a “No Team Available” message during workflows when a team is not needed.
-***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access.
+**Expanded support for special characters in the Attribute display name for contract requests, agreements, associations and masterdata.
-***Supporting larger files for masterdata and associations.
+**Selectively download amendments with the corresponding parent and child associations in a zip package with corresponding sub-folders.&nbsp;
-***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results.
+**Larger file size support when uploading (4GB) and downloading (6GB) larger files for masterdata and associations.&nbsp;
-***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters.
+**Boost smart filter creation using string operators such as “Contains”, “Starts With”, “Does Not Contain” for the “Business Status” search facet.
-***Providing the ability to configure filter on a lookup attribute &nbsp; with the “IN” operator on agreement contract type and template variables.&nbsp;
+**Expanded support for automating the bulk upload of clauses and templates reducing the dependency on manual approvals and delays in onboarding clauses and templates.
-***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation.
+**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.).
-***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates.
-***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).
+&nbsp;
 *<span style="color:#800080;">'''Mobile App Updates'''</span>
-**Enhancing &nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users.
+**Enhancing the “Refresh” functionality for “Tasks” and “Commitment” tabs to continually show the latest changes in the status for mobile app users.
-**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.
+&nbsp;
 *<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>
-**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments.
+**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;
-**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break.
+**Improved labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
-**Provisioning success or failure message for workflow operations.
+**Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;
+&nbsp;
 *<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>
 **'''''Icertis Experience for Word'''''
-***Supporting &nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session.
+***Improving the filtering and searching capability with support for searching text inside clauses or templates to allow more powerful search especially when searching across large libraries.&nbsp;
-***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries.
+***Improving labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
-***Improving labeling of internal, external and fully signed copies of agreements for easy identification.
+***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;
-***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;
-***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses.
+&nbsp;
-***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.
 *<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>
-**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word.
+**Multiple enhancements to the AI-powered legal playbook capabilities:
-**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause.
+***Improved usability by enabling larger window views of the “Details” page and also including deviations.&nbsp;
-**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration.
+***All the playbook positions for a contract type now have the option to search and filter.&nbsp;
-**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries.
+***Administrators can create a new playbook record or update the existing one from within Icertis Experience for Word itself.
-**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights.
+**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.
-**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&nbsp;
+**Extending the clause hierarchy discovery feature to support text PDFs in addition to .docx documents.&nbsp;
-**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&nbsp;
+**Improving library clause recommendations for discovered clause based on learnings from user’s action in previous discoveries.&nbsp;
-**Improving &nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.
+**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.
+&nbsp;
 *<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.
+**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 notifications sent to users.
+**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.&nbsp;
+**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 attribute version.
+**Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.
-**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information.
+**Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis. &nbsp;
-**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability.
+**Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.
-**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI.
+**Multiple localization enhancements within reports.
-**Enhancing localization support in reports.
+&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 signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).<br/> Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.<br/> Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &nbsp;
+***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 failures alerts for improved monitoring of messages.
+***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.
+***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 task service will use client Id and secret key from AKV, invoking MS CRM APIs.&nbsp;
+***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.
+&nbsp;
 *<font color="#800080">'''Enhancements to Platform Tools'''</font>
-**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.
+**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.
+&nbsp;
 *<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.
-These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.
+These release notes provide an overview of the enhancements to ICI, the mobile app, the ICI experience for integrations, and so on.
 &nbsp;
-== <span style="color:#800080;"><span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span></span> ==
+== <span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancement Details</span> ==
-<span style="color:#800080;">'''659853 – Upfront chevron view of agreement journey'''</span>
+<span style="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</span>
-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;
+Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.
-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;
+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.
-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.
+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.
-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.
+'''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;
-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:
+<span style="color:#800080;">'''575640 – Creating associations on the create or edit wizard of agreement'''</span>
-.&nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.
+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.
-.'''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;
+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;
+<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>
+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.
+<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>
+Users can see localized reason codes as per their preferred language settings.&nbsp;
+<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.
-. '''Execute:&nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.
+&nbsp;
-. '''Manage:&nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.
+<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from the contract request'''</span>
-'''Note''':&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;
-*The chevron view is only applicable to agreement contract type (agreement&nbsp;and amendment).
+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.
-*By default, the chevron is disabled; it can be enabled for selected contract types.
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 7.png|720px|7.15 Release Notes Screenshot 7]]</div>
-*The chevron labels support localization.
+&nbsp;
-<div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''512931 – Visibility of sections on the left navigation pane to non-team users'''</span></div>
-The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&nbsp;
-This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.<br/> &nbsp;
+'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''
-<span style="color:#800080;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>
+ICI’s collaboration portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself.&nbsp;
-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.
+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.
-<div class="image-green-border">Configurators can:&nbsp;</div>
-*Configure a smart link across any ICI entity that defines the entity relationships.
+&nbsp;
-*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities.
+<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:
+*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.
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 11.png|720px|7.15 Release Notes Screenshot]]</div>
+&nbsp;
+<span style="color:#800080;">'''514643 – Ordering of clauses as tagged in an agreement'''</span>
+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.
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 12.png|720px|7.15 Release Notes Screenshot 12]]</div>
+&nbsp;
+<span style="color:#800080;">'''617385&nbsp;– Ability to define additional clause group under clause entity'''</span>
+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>
+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;
+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;
+<span style="color:#800080;">'''558605 – Viewing amendments in grid view on the agreement details page'''</span>
+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;
+<span style="color:#800080;">'''561410 – Enhancing the multi-select drop-down&nbsp;'''</span>
+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;
+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;
+<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>
+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;
+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;
+Configurators can now:&nbsp;
+*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;
+<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>
+Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;
+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;
+Administrators can:&nbsp;
+*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;
-*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp;
+*Access the ICI system with appropriate details as default after the first login.&nbsp;
-*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results.
+*Override the default preference settings as per individual preferences.
-<div class="image-green-border">&nbsp;</div> <div class="image-green-border">Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.</div> <div class="image-green-border"><br/> For example, consider&nbsp;entities related in multi-level hierarchy as ''Agreement > Obligations > Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.</div> <div class="image-green-border"><br/> &nbsp;</div>
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 18.png|720px|7.15 Release Notes Screenshot 18]]</div>
-<span style="color:#800080;">'''584439 – Introducing the Contract Manager role for agreements&nbsp;'''</span>
+&nbsp;
+<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading the document'''</span>
+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;
+This functionality is available for agreements, amendments, and orphan amendments.<br/> &nbsp;
+<span style="color:#800080;">'''614860 – Attaching associated documents to agreement notifications'''</span>
+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;
+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.&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;
-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.
+<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>
-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;
+ICI allows users to define the linkage type as a parent, child, or peer while associating peer entities with each other.
-Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.
+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.
-With this release:&nbsp;
+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;
-*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&nbsp;''action.
+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;
-*Only one contract manager is available inside the agreement at any given point of time.
-*The contract manager will have provisions same as that of primary owner.
-*The contract manager name is displayed on the agreement summary page.
-*Agreements can be searched using the contract manager name.
-*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user.
+*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;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>
+<span style="color:#800080;">'''619558 – Downloading amendments using download all functionality'''</span>
-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;
+ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements.&nbsp;
-With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.
+With this release, 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;
+<span style="color:#800080;">'''615291 – Configuring attributes inheritance for amendments at the contract type level'''</span>
+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;
+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;'''
+*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:#800080;">'''614877 – Replacing a user with multiple users'''</span>
+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;
+Administrators can now:&nbsp;
+*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;
+*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;
-<span style="color:#800080;">'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''</span>
+<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</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.
+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, 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;
+*Enabling auto supersede option at the contract type level.
-<div class="image-green-border">For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.</div> <div class="image-green-border">This is applicable to the following associations:&nbsp;</div>
+*Configuring the “Supersede Rule” with “Is Supersede by Amendments” or “Is Supersede by Termination” options.&nbsp;
-*Import of Association (Line Item)
+*Selecting attributes in rule actions based on the selected Supersede On option.&nbsp;
-*Auto Attachment Association
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 28.png|720px|7.15 Release Notes Screenshot 28]]</div>
-*Obligation/ Fulfillment (Association of Association)
+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;
-The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.
+<span style="color:#800080;">'''615293 – Showing or hiding the No Team Available message'''</span>
+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;
+ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks.&nbsp;
+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;
-<span style="color:#800080;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>
+<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>
-Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.
+Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator.&nbsp;
-With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&nbsp;
+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;
-*Capture multiple valid internal or external email addresses while working on agreements/ requests.
+*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;
-*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.
+*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;
+<span style="color:#800080;">'''616901 – Applying facets to business status search filter'''</span>
+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;
+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.15 Release Notes Screenshot 31.png|720px|7.15 Release Notes Screenshot 31]]</div>
 &nbsp;
-<span style="color:#800080;">'''583186 – Ability to add amendment on expired agreement'''</span>
+<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>
-Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.
+Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&nbsp;
-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;
+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;
-The ''Add Amendment ''action is configurable through role action mapping on the expired state of&nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.
+<span style="color:#800080;">'''732929 – Uploading clauses and templates in bulk'''</span>
-<div class="image-green-border">&nbsp;</div>
-<span style="color:#800080;">'''593928 – Ability to configure sender email ID for automated emails'''</span>
-Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.
+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;
-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;
+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.
-Administrators can now:
+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;
-*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement.
+<span style="color:#800080;">'''655507 – Uploading and downloading large files with the file path attribute'''</span>
-*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to.
-*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses.
-<div class="image-green-border">&nbsp;</div>
-<span style="color:#800080;">'''593938&nbsp;– Time Zone support for date-dependent automated processes'''</span>
-In ICI, there are scheduled jobs that perform certain actions on&nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.
+ICI now provides support for larger files. This is applicable to masterdata and associations.
-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.
+Users can now:
-With this release:
+*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.
-*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).
+ICI supports virus scanning of large files if the virus scan feature is enabled.<br/> &nbsp;
-*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities.
-*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance.
-*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance.
-*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date.
-'''Note''':&nbsp;The time zone-based processing can be enabled for all contract types across&nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.
+'''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.
-<div class="image-green-border">&nbsp;</div>
-<span style="color:#800080;">'''512930 – Triggering service bus events for all actions'''</span>
-For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&nbsp;
+&nbsp;
-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;
+<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 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;
+Previously in ICI, attribute names did not support special characters apart from _ (underscore), & (ampersand), and space.&nbsp;
-<span style="color:#800080;">'''545126 – Availability of business status value in ICI event messages'''</span>
+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.
-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.
+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;
-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.
+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;
-== <span style="color:#800080;">Mobile App Updates</span> ==
+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;
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 32.png|720px|7.15 Release Notes Screenshot 32]]</div>
+&nbsp;
-<span style="color:#800080;">'''660965 – Refresh agreement list on approval'''</span>
+<span style="color:#800080;">'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''</span>
-Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically.&nbsp;
+With this release, ICI provides new controls for multi-select and single-select choice attributes.&nbsp;
-In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.
+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.14 release note 11.png|720px|7.14 release note 11.png]]<br/> &nbsp;</div>
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 33.png|720px|7.15 Release Notes Screenshot 33]]</div>
-== <span style="color:#800080;">ICI API Enhancements&nbsp;</span> ==
+Users can select:&nbsp;
-<div class="image-green-border">
-<span style="color:#800080;">'''607867 – ICI API 2.0 Implementation'''</span>
-With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.
+*The radio button for single-select choice attributes.&nbsp;
+*The checkbox list for multi-select choice attributes.
-Enhancements include:
+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;
-*Addition of Masterdata APIs&nbsp;
+<span style="color:#4B0082;">'''593421 – Labeling agreement document versions as per signature copy'''</span>
-**Users can now update the masterdata instance
-**UserName field is returned in Get Team API as part of the response.
-*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well.
+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>
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 35.png|720px|7.15 Release Notes Screenshot 35]]</div>
-== <span style="color:#800080;">Enhancements to ICI Add-ins&nbsp;</span> ==
+&nbsp;
+<span style="color:#800080;">'''872309 – Providing flexibility for assembling associations tagged as clauses'''</span>
+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.&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.
+'''Note: '''By default, the key is set to false.<br/> &nbsp;
+== Mobile App Enhancement Details ==
+<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span>
+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;
-<span style="color:#800080;">'''714872 – Improved document usability'''</span>
+<span style="color:#800080;">'''850259 – Updating logo and ICM to new guidelines'''</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;
+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;
-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.
+<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span>
-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.
+Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.
-<div class="image-green-border">With this release:</div>
-*All the content controls are put together in a single paragraph on any line with valid content.
-*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.
-*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.
-*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&nbsp;
-*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.
-<div class="image-green-border">'''Note''':&nbsp;</div>
-*Only file-based clauses are supported.
-*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template.
-*Location-specific (such as center-justified) rule-based clauses cannot be tagged.
-*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.
-*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.
 &nbsp;
-<span style="color:#800080;">'''660390 – Ability to show more clauses per group'''</span>
+<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span>
-With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.
+With this release, the UI WebView component for iOS has been deprecated.<br/> &nbsp;
-This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.
+== ICI API Enhancement Details&nbsp; ==
-<div class="image-green-border">&nbsp;</div>
+<div class="image-green-border">
-<span style="color:#800080;">'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''</span>
+<span style="color:#800080;">'''704069 – Enhancing ICI API 2.0 implementation'''</span>
-In ICI, users capture additional details for clauses and templates in the extended attributes.
+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 extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.
+This is applicable for visualizing, retrieval, creation, and updating of the instances of the following entities:<br/> Contract Requests
-<div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''</span></div>
-Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.
+*Agreements
+*Associations
+*Amendments
+New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.
-Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.
-<div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''</span></div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''</span></div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.</div>
 &nbsp;
-== <span style="color:#800080;">Enhancements to Artificial Intelligence Applications in ICI</span> ==
+<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>
-<span style="color:#800080;">'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''</span>
+ICI already supports downloading agreements.
-With this release, ICI is introducing a legal playbook in Icertis Experience for Word&nbsp;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.
+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.
-Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.
+&nbsp;
-Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.
+<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>
-The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.
+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.
-<div class="image-green-border">Negotiators can now:</div>
-*Define the structure and setup the playbook by configuring a masterdata in ICI.
-*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range.
-*Use artificial intelligence to identify and highlight the playbook exceptions in the document.
-*Review all discovered exceptions that are listed down on the page and take corrective actions as required.
-*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores.
-*Review the version-wise cumulative risk using a risk report.
-<div class="image-green-border">By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.</div>
-<br/> <span style="color:#800080;">'''575450 – Supporting clause hierarchy in .docx agreements'''</span>
-Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.
+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.
-With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&nbsp;
+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;
-Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.
+<br/> <span style="color:#800080;">'''660859 – Supporting TrackingId in APIs'''</span>
-<div class="image-green-border">'''Note''':&nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&nbsp;</div>
+To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;
+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;
-<span style="color:#800080;">'''663666 – Enhancing inbuilt discovery model to include additional attributes&nbsp;'''</span>
+== ICI Add-ins Enhancement Details ==
-The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&nbsp;
+<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</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;
+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&nbsp;free-text search on the clause and template content.
+<div class="image-green-border">[[File:7.15 Release Notes Screenshot 36.png|720px|7.15 Release Notes Screenshot 36]]</div>
+&nbsp;
+&nbsp;
-With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.<br/> &nbsp;
+== AI Applications Enhancement&nbsp;Details ==
-<span style="color:#800080;">'''575466 – Support for additional languages in AI apps&nbsp;'''</span>
+<span style="color:#800080;">'''727318 – Enhancing AI-powered playbook in Icertis Experience for Word'''</span>
-Previously, the ICI clause and obligation discovery models were primarily based on the English language.&nbsp;
+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;
-In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.
+The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word.&nbsp;
 With this release:
-*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration.
+*Negotiators can easily review the playbook exceptions found in deviated agreement clauses on the “Agreement Clause” page. &nbsp;
-*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document.
+*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.
-*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI.
+*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.
-*While discovering or matching the clause from clause library, document language is taken into consideration.
+*Negotiators can view all the applicable playbook positions for a selected agreement clause.&nbsp;
-*The additional languages are supported while discovering similar clauses.
+*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;
-== <span style="color:#800080;">Enhancements to Reports</span> ==
+<span style="color:#800080;">'''575475 – Automating user feedback during clause review'''</span>
-<span style="color:#800080;">'''514594 – Capability of time zone in reports'''</span>
+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;
-ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.
+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;
-<div class="image-green-border">With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.<br/> &nbsp;</div>
-<span style="color:#800080;">'''514609 – Introducing the Clause Summary Report'''</span>
-Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&nbsp;
+<br/> <br/> <span style="color:#800080;">'''539492 – Rearranging discovered clauses'''</span>
-With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&nbsp;
+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;
-This default report is accessible from the Admin category of reports and its access is based on Security Groups.
+*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>
+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;
+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;
+Users can:&nbsp;
+*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
+'''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 class="image-green-border">[[File:7.15 Release Notes Screenshot 40.png|7.15 Release Notes Screenshot 40]]</div>
 &nbsp;
-== <span style="color:#800080;">Integrations</span> ==
+<span style="color:#800080;">'''727312 – Clause hierarchy discovery in text PDFs'''</span>
+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.<br/> &nbsp;
+<span style="color:#800080;">'''727314 – A generalized framework to support additional languages in AI apps'''</span>
+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.&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;
+== Reports Enhancement Details ==
-<span style="color:#800080;">'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''</span>
+<span style="color:#800080;">'''514593 – Introducing the&nbsp;Tagged Attributes Report'''</span>
-In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&nbsp;
+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.
-With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&nbsp;
+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;
-Salesforce users can now:&nbsp;
+<span style="color:#800080;">'''769602 – Displaying clause extension attribute summary in the Clause Summary Report'''</span>
-*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&nbsp;
+Previously, the “Clause Summary Report” displayed “Clause Summary” and “Clause Version Summary” sections on the report index page.
-*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&nbsp;
-*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab.
-<div class="image-green-border">&nbsp;</div>
-<span style="color:#800080;">'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''</span>
-The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&nbsp;
+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;
-With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&nbsp;
+<br/> <span style="color:#800080;">'''514611 – Introducing the&nbsp;Notifications History Report'''</span>
-These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.<br/> <br/> '''Note''':&nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.
+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;
-<span style="color:#800080;">'''635822 – Support for pre- and post-processing in Generic Integration Framework'''</span>
+<span style="color:#800080;">'''742607 – Providing additional localization support in reports'''</span>
-Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&nbsp;
+With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas:&nbsp;
-With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:
+*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;
-*Pre-process inbound data through file-based integrations.
+<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span>
-*Pre-process inbound and outbound data through ASB-based integrations.
-ICI administrators will now be able to:&nbsp;
+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;
-*Enable or disable the hook as part of file-based and ASB integration.
+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.
-*Pass parameters to the hook for executing a custom logic.
-*Enable or disable the hook at file or record level.
-**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook.
-**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.
-*Execute any custom logic in the system for a file or record when a hook is configured.
-*Complete GIF process even when custom logic encounters any error while processing a record or file.
 &nbsp;
-<span style="color:#800080;">'''635823&nbsp;– Support for defining folder structure in Generic Integration Framework'''</span>
+<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>
-Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.
+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.
-Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.
+With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.
-With this release, users have:&nbsp;
+&nbsp;
-*Support for single or multiple folders in the folder structure.
+<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>
-*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format).
-*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change.
+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;
-*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used.
 &nbsp;
+== Integration Details ==
+<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
+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.&nbsp;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.<br/> &nbsp;
+<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>
+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.<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>
+Previously, ICI supported one signature vendor within one instance of ICI.&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;
-== <span style="color:#800080;">ICI Platform Tools</span> ==
+<span style="color:#800080;">'''751651 – Publishing success/failure notification message on ASB post data sync from Salesforce'''</span>
+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.<br/> &nbsp;
+<span style="color:#800080;">'''796155 –&nbsp;Enhancements to the data flow between Salesforce/MS CRM and ICI'''</span>
+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.&nbsp;
+*The data will sync only for tracking attributes if the contract is in the "Executed" state.&nbsp;
+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.
+<br/> <span style="color:#800080;">'''674469 – Generating ICI notifications and enhancing Salesforce data sync'''</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 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;
+<br/> <span style="color:#800080;">'''679797 –&nbsp;Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use'''</span>
+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;
+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;
+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;
+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;
+<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
+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;
+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;
+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;
+== ICI Platform Tools Details ==
 '''<span style="color:#800080;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''
-With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.<br/> The following entities are now supported:
+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)
@@ Line 465: / Line 833: @@
 &nbsp;
-== <span style="color:#800080;">Partner Enablement</span> ==
+== Partner Enablement ==
 <span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
@@ Line 473: / Line 841: @@
 As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:
-*'''ICI Coding Guidelines (version 2)''':&nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.
+*'''ICI Coding Guidelines (version 2):'''&nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.
 *'''ICI Customization and Use Cases (version 2): '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript.
@@ Line 479: / Line 847: @@
 *'''Working with ICI Tasks: '''Updated for the 7.15 release.
-*'''Working with ICI Hooks: '''Updated for the 7.15 release.
+*'''Working with ICI Hooks:&nbsp;'''Updated for the 7.15 release.
-*'''ICI Developer Library: '''Updated for the 7.15 release.
+*'''ICI Developer Library:''' Updated for the 7.15 release.
-*'''Local Environment Setup using ICI Binaries: '''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.
+*'''Self-Serve Tools:''''''&nbsp;'''Updated for the 7.15 release.
 &nbsp;
-== <span style="color:#800080;">Technical Requirements for Release 7.15</span> ==
+== Technical Requirements for Release 7.15 ==
-The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.
+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;
-[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]
+The software and hardware requirements for the client system as well as mobile application are listed in the table below.
-[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]
+[[File:7.15 Technical Requirements - Operating Systems.PNG|720px|7.15 Technical Requirements - Operating Systems]]
+[[File:7.15 Technical Requirements - Browser Compatability Matrix.PNG|720px|7.15 Technical Requirements - Browser Compatibility Matrix]]
+[[File:7.15 Technical Requirements - Other Requirements.PNG|720px|7.15 Technical Requirements - Other Requirements]]
+[[File:7.15 Technical Requirements - Smartphone Mobile App.PNG|720px|7.15 Technical Requirements - Smartphone Mobile App]]
+[[File:7.15 Technical Requirements - Special Requirements 1.PNG|720px|7.15 Technical Requirements - Special Requirements 1]]
+[[File:7.15 Technical Requirements - Special Requirements 2.PNG|720px|7.15 Technical Requirements - Special Requirements 2]]
+[[File:7.15 Technical Requirements - Special Requirements 3.PNG|720px|7.15 Technical Requirements - Special Requirements 3]]
+[[File:7.15 Technical Requirements - MS Office Plugins 1.PNG|720px|7.15 Technical Requirements - MS Office Plugins 1]]
+[[File:7.15 Technical Requirements - MS Office Plugins 2.PNG|720px|7.15 Technical Requirements - MS Office Plugins 2]]
+[[File:7.15 Technical Requirements - Security.PNG|720px|7.15 Technical Requirements - Security]]
+&nbsp;
-[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]
+== Known Issues ==
-[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]
+This section includes some issues that we are aware of and plan to resolve at the earliest:
-[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]
+[[File:Known Issues.PNG|720px|7.15 Known Issues]]
 &nbsp;
@@ Line 507: / Line 895: @@
 &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;|