= 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 the user experience, intelligence, analytics, intuitiveness, and usability by continually improving the user interface and functionalities.

The key enhancements of this release include:

***To ensure that the agreement document is generated with the correct clauses and metadata, we now can preview an agreement from the pre-draft to the Approved stage, enabling a comprehensive review before publishing the contract.   

***Improved usability for the global user base and their individual user interface (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 UI 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 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 the “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'''''

**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 is 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 such as “External”, “Internal,” and “Fully Signed” are now shown in agreement versions.

**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 amendment via the “Is Inherit On Amendments” flag at the agreement contract type and template variable levels.  

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

**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) files for masterdata and associations. 

**Boost smart filter creation using string operators such as “Contains”, “Starts With”, or “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.). 

*<span style="color:#800080;">'''Mobile App Updates'''</span>  

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

**Providing support for the script and integrated attributes as cascaded attributes for lookup fields when configured at the contract type level. This is applicable for retrieval, creation, and update of the instances of contract requests, agreements, associations, and amendments.  

**Adding the identifier “TrackingId” which can be passed by subsequent API calls for logging and troubleshooting errors.

 

 

*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>

***Improving the filtering and searching capability which now supports searching text inside clauses or templates to allow more powerful deep searches especially when searching across large libraries.  

***Improved labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.

***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;    

**Multiple enhancements to the AI-powered legal playbook capabilities:

***Improved usability by enabling larger window views of the “Details” page, 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 an existing one from within Icertis Experience for Word itself.  

**Improving the clause delineation logic so that users can rearrange the AI-identified clause boundaries. You can now merge or split discovered clauses or selected text in a clause and also create sub-clauses within the discovered clause.  

**Extending the clause hierarchy discovery feature to support text PDFs in addition to .docx documents.&nbsp;

**Improving library clause recommendations for discovered clauses based on learnings from user’s actions in previous discoveries.&nbsp;

**Providing support for additional languages including “French”, “Dutch”, “Norwegian” and “Swedish” in AI apps.

**Enabling users to flexibly leverage AI on-demand by manually triggering attribute discovery on an agreement from the “Attributes” page to accelerate workflows. The 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.   

**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 conformity for the users.  

**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.

**Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.

**Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis.&nbsp;

**Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.  

**Multiple localization enhancements within reports.   

***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 vendor 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;

***Providing the ability to send success and failure alerts for improved monitoring of messages.  

***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.<br/> &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.    

 

*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>

**

***With this release, the following SDK documents have been updated – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, and Self-Serve Tools.<br/>     

 

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

 

<span style="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</span>

 

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

 

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

 

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

<span style="color:#800080;">'''575640 – Creating associations on the create or edit wizard of agreement'''</span>

 

Previously in ICI, contract authors had to create associations for agreements after the agreement was 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 the 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.&nbsp;

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 2.png|720px|7.15 Release Notes Screenshot 2]]<br/>  

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

 

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

<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from the contract request'''</span>

To terminate an agreement in ICI, users create and execute a termination agreement on the main agreement instance. This capability is now extended to initiate the termination from contract requests as well.

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;

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

Internal users are authenticated through the SSO/IDP before opening the page where the actions are to be taken. 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>  

<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”.&nbsp;

 

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

 

 

<div class="image-green-border">[[File:7.15 Release - Screenshot for Feature 514643.png|720px|514643]]</div>  

<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 they can be used in search filters, notification rules while configuring saved searches, and so on.

<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;">'''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 menu 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 masterdata 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;&nbsp;

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 14.png|720px|7.15 Release Notes Screenshot 14]]</div>  

<span style="color:#800080;">'''558605 – Viewing amendments in grid view on the agreement details page'''</span>

 

Users can now view amendments in the “Grid” view, and toggle between grid or tile view. The grid view is the default 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 - Screenshot for Feature 558605.png|720px|558605]]</div>  

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

*Deselect the selected values, individually or all with a single click, without opening the drop-down.  

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 16.png|720px|7.15 Release Notes Screenshot 16]]</div>  

<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 masterdata attribute.&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;

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

Administrators now have 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 in setting up their ICI account with the required parameters after the first login and presents the system with appropriate and specific pre-configured settings. &nbsp;&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 modification details in the “History” tab for audit.  

*Search users based on parameters related to preference settings.  

 

 

*Access the ICI system with appropriate details as default, after the first login.&nbsp;  

<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;">'''604775 – Moving agreement to executed state without uploading the document'''</span>

 

 

<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.&nbsp;

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

 

 

*Administrators can 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.  

<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>

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

<span style="color:#800080;">'''619558 – Downloading amendments using download all functionality'''</span>

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, users can 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>  

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 24.png|720px|7.15 Release Notes Screenshot 24]]</div>  

<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 applies to all agreement contract types by default.&nbsp;

Configurators now have the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. They 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.&nbsp;

Users can then copy these defined attribute values from base agreement to amendment during amendment creation.&nbsp;

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

*The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.

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

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

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

<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</span>

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 27.png|720px|7.15 Release Notes Screenshot 27]]</div>  

*Selecting attributes in rule actions based on the selected Supersede On option.&nbsp;

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

<div class="image-green-border">[[File:7.15 Release Notes Screenshot 29.png|720px|7.15 Release Notes Screenshot 29]]</div>

<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>

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

With this release, configurators can now set multiple, complex conditions to display ICI Web UI attributes dynamically, based on business scenarios. They can define conditions for attributes of 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;

&nbsp;Users can now:&nbsp;

*Apply multiple and complex conditions to display an attribute by enhancing the enable expression (Visibility Expression) for contract requests, agreements, associations, and masterdata contract types.&nbsp;  

*Support conditional expressions for extension attributes. &nbsp;  

*Define conditions with different operators based on the selected attribute data type.&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 by all customers as they reflect the actual status in business terms as compared to the system workflow status. Previously, the ICI search functionality supported filters on “Business Status” for users to refine results. However, manually selecting filters often becomes a tedious task in case there are several business statuses.&nbsp;

<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>

Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&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.

 

 

With this release, the bulk import functionality using the “Legacy Upload” tool has been automated, 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.

<span style="color:#800080;">'''655507 – Uploading and downloading large files with the file path attribute'''</span>

*Upload files up to 4GB under the file selection attribute.&nbsp;  

'''Note:&nbsp;'''This is not applicable for contract requests, agreements, or 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.

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

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

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.

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;<br/> 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.&nbsp;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;

Amendments to an agreement are now available in the 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 - Screenshot for Feature 618994.png|720px|618994]]</div>  

<span style="color:#800080;">'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''</span>

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 is considerably reduced and provides better readability in terms of post-selection data review. &nbsp;&nbsp;&nbsp;

Users can select:&nbsp;

*The radio button for single-select choice attributes.&nbsp;  

*The checkbox list for multi-select choice attributes.  

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

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

&nbsp;

 

<span style="color:#800080;">'''850259 – Updating logo and ICM to new guidelines'''</span>

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

<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span>

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

 

<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span>

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

 

<span style="color:#800080;">'''863795&nbsp;– Support for context-based translations in ICI'''</span>

<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>

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.

<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>

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 the service bus. Based on the topic notification, integration developers can take follow-up actions based on success and failure.

<br/> <span style="color:#800080;">'''660859 – Supporting TrackingId in APIs'''</span>

 

For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow”, “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature”.&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 can pass for correlating from a logging perspective.&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 be returned).

*The called API path with the query string will be logged in Kibana. In Kibana, developers must look for “CorrelationId” which maps the “TrackingId” used in the API.<br/> &nbsp;

 

 

 

*Status check operations&nbsp; &nbsp;&nbsp;  

== ICI Add-ins Enhancement Details ==

<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 clause and template 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.

&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 English, 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 can now discover attributes too, in all the supported languages.&nbsp;

<span style="color:#800080;">'''742607 – Providing additional localization support in reports'''</span>

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

*Contract type names, if the respective entity has locale resource key values in the database.&nbsp;

*Graph and Time zone tooltips, if present in the report.  

*Column headers. &nbsp;

*Any error or validation messages.  

*Informative messages such as “No data available”. &nbsp;

<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span>

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

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

<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>

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.&nbsp;

 

== Integration Details ==

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.

With this release, the ICI signature process has been enhanced as follows:

*The hybrid signature process has been introduced that allows the usage of manual and electronic signature modes 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.

 

 

 

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.

 

 

 

Users now have the flexibility to:

 

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.

*Document assembly or notification to third party applications can be triggered by consuming the notification message posted on Azure Service Bus (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 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.

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

*The data will sync only for tracking attributes if the contract is in the "Executed" state.&nbsp;

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

*Customers will get success/failure ICI notifications for data sync as well as reverse sync. 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>

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.

 

<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>

 

 

 

 

 

<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations, and maximize customer satisfaction. The Software Development Kit (SDK) was introduced to provide the resources and tools needed while implementing ICI.&nbsp;

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

*'''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 related code.  

*'''Working with ICI Tasks: '''Updated for the 7.15 release.  

*'''Working with ICI Hooks:&nbsp;'''Updated for the 7.15 release.

 

 

 

*'''Self-Serve Tools:'''&nbsp;Updated for the 7.15 release.  

== Technical Requirements for Release 7.15 ==