From ICIHelp7.14
Jump to: navigation, search
 
(215 intermediate revisions by 5 users not shown)
Line 1: Line 1:
  
−
= ICM Release Notes - Release 7.9 =
+
= ICI Release Notes - Release 7.14 =
  
−
== Overview of Release 7.9 ==
+
== Overview of Release 7.14 ==
  
−
The 7.9 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience and intuitiveness by continually improving the ICM user interface.
+
The 7.14 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICI functionalities and the user interface.
  
 
The key enhancements of this release include:
 
The key enhancements of this release include:
  
−
*Enhancements in AI applications such as providing the Agreement/Clause Similarity functions and some UX improvements in the Negotiate AI app, supporting Obligation discovery on Templates and incorporating user actions feedback in the Obligation AI app, adding some hooks in the Visualize AI app to support custom visualization, and adding support for Table discovery in the Discover AI app.
+
*<span style="color:#008000;">'''Enhancements to the ICI Application'''</span>  
−
*Improving the ICM infrastructure to determine the Application Type (Contracting, Sourcing, Proposal, Obligation Management, and Supplier Lifecycle Management) when creating a Contract Type.
+
−
*Allowing multiple stakeholders to collaborate within ICM itself, thus eliminating the need for using external tools such as Email, Skype, etc.
+
−
*Enhancing Search filters to include Team roles. The search capabilities have been further improved to allow searching of Agreements and Associated documents based on Clause usage, so that users can tackle the high risk Agreements first and mitigate risks.
+
−
*Improving usability by allowing the comparison of any two versions of the Agreement document, displaying a banner for an announcement or scheduled event, Introducing the bulk import tool to import Templates/Clauses in bulk along with tagging and rules, enhancing bulk upload capability to create an assignment or initiate termination, provision users, and add team members when creating or updating an Agreement/Amendment.
+
−
*Introducing the ability to tag the same Masterdata localized Attribute multiple times to support bilingual Templates within ICM.
+
−
*Improving the ability to create Rules by introducing new conditions such as ''Has A Value'' and supporting Power Set conditions for multi-select data&nbsp;
+
−
*Extending support to Template Variables to be able to track the dependency between the Contract Type Attributes and Template Variables.
+
−
*Improving Power Business Intelligence (BI) usability by making some UX related changes, displaying the Power BI Dashboard on the Advanced Analytics tile and improving the user experience.
+
−
*Refining Reports to display the Date and Time as per user preferences in addition to more reports now being available on the Dashboard as KPIs.
+
−
*Improving the Icertis Experience by: <ul style="list-style-type:circle;">
+
−
</ul>  <li>Introducing a new .JS version of the ICM Outlook Plugin to be able to upload the next version of the Agreement Document and Associated Document, or creating a new Association instance and the uploading the Associated Document received over Email to the Agreement, thus reducing the overall turnaround time for the author.</li>
+
−
<li>Introducing a new field for Salesforce users named ''Field Set Name'' so that the Adapter reads the metadata and sends only the Attributes defined for the entity when the integration is triggered from Salesforce. It also allows using Attributes defined at the Template level to store critical data as part of the Agreement and sync with Salesforce, thus avoiding data duplication and redundancy in the process.</li>
+
−
<li>Collaborating with Microsoft Team to provide a seamless user experience when authoring contracts, negotiations, or when discussing ideas and exchanging files, and in turn significantly improving the cycle time.</li>
+
−
<li>Configuring the ICM Workday Adapter so that Executed Agreements can be attached as .PDF, instead of .docx.</li>
+
−
<li>Providing the capability to upload a manually signed copy of an Agreement document using the ''Print, sign and upload'' capability of Adobe Sign, and supporting redlining in Associations tagged as a Table in a Template or Agreement document, in addition to allowing the user to send supporting documents along with the main Agreement for signature when using Adobe Sign.</li>
+
−
</ul>
+
  
−
These Release Notes provide an overview of enhancements to ICM and the ICM Experience for Integrations. Refer to the detailed Wiki documentation for explanation and capabilities of these and all other ICM features and functionalities.
+
*'''''User Experience'''''
 +
**Introducing a horizontal chevron which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron, namely Generate, Approve, Execute and Manage, prominently communicate an entity’s journey including the previous, current and possible future states of the agreement.
 +
**Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement.
 +
**Facilitating one-click navigation from the ICI record to any related entities (multi-hierarchy level). For example, from RFx to Bid Response which would otherwise require multiple clicks.
 +
**Providing administrators the ability to configure access control for users who are not part of the team to sections or sub-sections in the left navigation pane at the contract type level.  
 +
**Enhancing document usability by placing content control tags such that the end-user no longer views separate lines in the assembled document for assembled clauses that are not evaluated. 
 +
*'''''Workflow Enhancements'''''
 +
**Displaying the organization unit path of the parent document by default as the path for the associated document, so that both parent and child documents have the same organization path at the time of creation and updation.
 +
**Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle.
 +
**Providing the ability to add amendments to expired agreements. &nbsp;
 +
**Adding a time zone attribute to provide enterprise organizations the flexibility to track the time zone or region-based activities as needed for the instance of the agreement.
 +
**Providing the capability to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications and allowing configuration of the sender’s email ID dynamically based on the specific contract type or instance of the record.&nbsp; 
 +
 
 +
*<span style="color:#008000;">'''Mobile App Updates'''</span>
 +
**Improving the usability of the mobile app by refreshing the agreement or requests list automatically after an approve, reject or request review action is performed. 
 +
 
 +
*<span style="color:#008000;">'''Enhancements to ICI API 2.0'''</span>
 +
**Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata. 
 +
 
 +
*<span style="color:#008000;">'''Enhancements to ICI Add-ins'''</span>
 +
**''Icertis Experience for Word''
 +
***Displaying a set of 30 clauses per page with pagination for easy navigation between clauses listed on the clauses, clauses in templates and clauses in agreement pages.
 +
***Providing extended attributes within the add-in for creation and modification of clauses and templates.
 +
***Allowing the deviation approver to view and directly approve or reject clause deviations in an agreement from within the add-in.
 +
***Displaying a validation message in clause content control enabling users to insert and tag clauses at the correct location in the document before publishing it. 
 +
**''Outlook Add-in''
 +
***Enhancing the Outlook Add-in by providing the ability to upload email in .docx or .msg format as associated documents for an agreement from within Outlook.   
 +
 
 +
*<span style="color:#008000;">'''Enhancements to Artificial Intelligence Applications'''</span>
 +
**Introducing a legal playbook in the NegotiateAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.
 +
**Enhancing DiscoverAI to identify the different levels within a clause through a distinct visual representation of clauses with sub-sections displayed in a delineated view during the clause discovery process.
 +
**Enhancing the ICI discovery models to support clause and obligation discovery for additional languages such as German, Spanish and Portuguese.
 +
**Improving the inbuilt DiscoverAI model to identify additional attributes such as City, State, Zip Code, and so on. 
 +
 
 +
*<span style="color:#008000;">'''Enhancements to Reports'''</span>
 +
**Introducing the Risk Assessment Report which is a trendline chart report that depicts the agreement aggregate risk score by their version. ICI’s AI algorithm identifies the playbook exceptions for a new version.
 +
**Introducing the Clause Summary Report to help clause administrators to understand and assess the impact of changes made to a clause.
 +
**Providing users the capability to generate a report as per the time zone of their choice from within the report itself. 
 +
 
 +
*<span style="color:#008000;">'''Improving the Icertis Experience'''</span>
 +
**Extending support for ICI dashboard widgets in the Icertis Experience for Salesforce Home page, so that users can perform all necessary actions from within Salesforce itself.
 +
**Supporting auto-renewal and reset expiry functionalities in Icertis Experience for Workday, thus saving time and avoiding data duplication.
 +
**Enhancing the generic integration framework to support custom pre- and post-processing hooks to considerably reduce implementation time, and allowing users to define and configure folder structure and file names as per the business requirement. 
 +
 
 +
*<span style="color:#008000;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>
 +
**In release 7.12, the Software Development Kit (SDK) was released to support partners for technical configuration. With this release, documentation for ICI coding guidelines, ICI developer methods, local environment setup using ICI binaries, and ICI customization and use cases are also available. 
 +
 
 +
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.
  
 
&nbsp;
 
&nbsp;
  
−
== ICM Application Enhancements ==
+
<span style="color: rgb(0, 119, 235); font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span>
  
−
<span style="color:#008000;">'''420230 – Extend Contract Type definition to be able to describe the Application Type &nbsp;'''</span><br/> ICM offers the ability to determine the Application Type (Contracting, Sourcing, Proposal, Obligation Management, and Supplier Lifecycle Management) when creating a Contract Type. This is possible with the inclusion of two new Choice type Attributes, Business Application Type and Business Application Category at the Contract Type level. This feature helps effortlessly drive Business Application on the ICM platform. These Attributes are applicable for Agreements and Associated Document Contract Types, after the Business Application is enabled through a technical configuration. The access privileges for Business Applications such as Sourcing, are driven through Security Groups.<br/> &nbsp;
+
<span style="color:#008000;">'''659853 – Upfront chevron view of agreement journey'''</span>
−
<div class="image-green-border"><span style="color:#008000;">'''390639 – Collaboration in Contracts &nbsp;'''</span><br/> Previously, stakeholders involved in the contracting/sourcing process used to communicate via external tools such as Email, Skype, etc. Managing these conversations that involved multiple stakeholders and multiple discussions was a cumbersome task. With this release, ICM has eliminated the need to use external tools and created a dedicated space available within the Agreement itself.&nbsp;<br/> To collaborate, multiple stakeholders involved in the contracting/sourcing process can:</div>
+
−
*Use the Collaboration tab available inside the Agreement&nbsp;
+
−
*Provision an internal/external Team member to communicate with other internal or external team member(s) by creating Topics and posting messages in it
+
−
*Provision users to send and receive attachments along with the message
+
−
*Provision users to mark the topic as closed once discussion is concluded.
+
−
*Send Email notification to participants when messages are posted in the topic
+
−
<div class="image-green-border">This can be achieved by setting the Enable Collaboration flag to Yes for the Agreement Contract Type, which displays a Collaboration tab on the Agreement Details page. To prevent data loss, once Collaboration is enabled for a Contract Type, it cannot be disabled.&nbsp;<br/> &nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">'''<span style="color:#008000;">400058 – Enhance Search filters to include Team members and their Roles</span>'''&nbsp;</div> <div class="image-green-border">With this release, ICM now supports the ability to search entities based on any user roles so that users can keep track of the Agreements that they are responsible for review and approvals. Users can apply other filters along with the team role to derive out-of-the-box saved search KPIs that help them manage Agreements and Amendments faster and easily.&nbsp;<br/> You can now search, and filter Agreements based on any user roles using the following Categories – Team Member: Role Name, Is Group, Role Display Name, and User Name. &nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">
+
−
'''<span style="color:#008000;">382235 – Power BI Integration with ICM&nbsp;</span>'''<br/> With this release, in effort to improve Power BI usability, some changes have been made and some additional functionalities have been added.
+
  
−
*The following UX related changes have been made:
+
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;
−
**Last Updated On text is changed to Data Source updated successfully&nbsp;
+
−
**The Refresh icon (which shows the minimum time of refresh cycle among all datasets) is changed to the Refresh page button 
+
−
*If the session is going to time out, the Advanced Analytics page will display the standard ICM time out alert to the user.
+
−
*The Save your report option is now available for global reports. Users can save a copy of the report. It is visible in the user’s My Reports section and can be modified as required. If special characters are added to the report name, an error message will be displayed.
+
−
*You can edit the saved global report using the Edit Report Name option. If special characters are added when renaming a report, an error message will be displayed.
+
−
*You can also delete this report using the Delete Report option if it is no longer relevant.
+
−
*Power BI Dashboard is now available in the Advanced Analytics section. The Advanced Analytics tile now displays the following 3 tabs:
+
−
**''Business Summary:'' displays the following based on the defined KPIs and the authorization of the user (for example, Finance Head):
+
−
***Agreement Summary such as Top Agreements by Value, Top Expiring Agreements, etc. (based on the defined KPIs).
+
−
***Deviations Summary such as Deviated Agreements and Contract Value (s) by Org Unit, Deviated Agreements by Contract Type, etc.&nbsp;
+
−
***Expiring Agreements such as Expiring Agreements by Month, Agreements marked for Auto-Renewal, etc.&nbsp;
+
−
***Cycle Time Report such as Cycle Time (in Days) by Contract Types, Trend of Cycle Time by Month, etc.&nbsp;
+
−
***Configuration Statistics such as Distribution of Templates by Contract Types, Clauses by Category, etc.&nbsp; 
+
−
**''Legal Summary:'' displays the following based on the defined KPIs and the authorization of the user (for example, Legal Head).
+
−
**''Legal Details:'' displays the legal details at a more granular level based on the defined KPIs and the authorization of the user (for example, Legal Head). 
+
−
*When creating reports, you can configure Power BI such that you can select what data you want to view. For example, you can only view the Agreements and Templates, but hide the Clauses. The same applies when asking a question.&nbsp;  
+
  
 +
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 horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.
 +
 +
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.
 +
 +
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:
 +
 +
1.&nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.
 +
 +
2.'''Approve:'''&nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&nbsp;
 +
 +
3. '''Execute:&nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.
 +
 +
4. '''Manage:&nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.
 +
 +
'''Note''':&nbsp;
 +
 +
*The chevron view is only applicable to agreement contract type (agreement&nbsp;and amendment).
 +
*By default, the chevron is disabled; it can be enabled for selected contract types.
 +
*The chevron labels support localization.
 +
<div class="image-green-border">[[File:7.14 release note 1.png|720px|7.14 release note 1.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''<span style="color:#008000;">512931 – Visibility of sections on the left navigation pane to non-team users</span>'''
 +
 +
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:#008000;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>
 +
 +
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.
 +
<div class="image-green-border">Configurators can:&nbsp;</div>
 +
*Configure a smart link across any ICI entity that defines the entity relationships.
 +
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities.
 +
 +
Users can:&nbsp;
 +
 +
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp;
 +
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results.
 +
<div class="image-green-border">[[File:7.14 release note 2.png|720px|7.14 release note 2.png]]</div> <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/> [[File:7.14 release note 3.png|720px|7.14 release note 3.png]]</div>
 
&nbsp;
 
&nbsp;
−
</div>
 
−
<span style="color:#008000;">'''452265 – Ability to compare any 2 versions of the document'''</span><br/> Previously, users could only see the comparison between the last and the current version of the Agreement. This functionality has now been enhanced so that the user can compare any two of the available versions of the Agreement as required.
 
  
−
<span style="color:#FF0000;">Note:</span> The Agreement document version comparison always takes place between a higher version on the right panel and a lower version on the left panel.
+
'''<span style="color:#008000;">584439 – Introducing the Contract Manager role for agreements&nbsp;</span>'''
 +
 
 +
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.
 +
 
 +
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&nbsp;
 +
 
 +
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.
 +
 
 +
With this release:&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.
 +
*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.  
  
 
&nbsp;
 
&nbsp;
  
−
'''<span style="color:#008000;">408652 – Displaying an Announcement Banner</span>'''<br/> ICM has now improved user experience by providing the capability of displaying a scrolling banner message to inform users of a scheduled event or an announcement. For example, you can inform users that a maintenance activity is scheduled in 24 hours. A banner will scroll at the top of the ICM window alerting the users of the downtime, so that they can plan their work accordingly.&nbsp;This can be achieved through Application Settings by toggling the Show announcement banner field to Yes and entering the message to be displayed in the Announcement message box.
+
<span style="color:#008000;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>
  
−
<br/> <span style="color:#008000;">'''408644 – Pub Sub Implementation – Beta version'''</span><br/> The beta version of the Pub Sub is now enabled. Due to this implementation:
+
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;
  
−
*The Task service should run without any errors (Kibana and Event Logs)
+
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''.
−
*On starting the Task service topics, their respective Subscriptions should get created automatically
+
−
*Emails should get triggered for configured notifications
+
−
*DocuSign should work
+
  
 
&nbsp;
 
&nbsp;
  
−
<span style="color:#008000;">'''428153 – Promote to Production (P2P) Enhancements – Beta version'''</span><br/> The beta version of the Promote to Production tool is now enabled. This functionality, provided to Administrators, can promote ICM configurations/modifications made to ICM configurations in pre-production environments to production environments.&nbsp;<br/> This tool provides support for Contract Types, Contract Type Attributes, Clauses and Templates (along with the documents), Notification Templates, Rules, Masterdata, Users, User Groups and Security Groups. The elastic search sync is also supported with the tool.<br/> <span style="color:#FF0000;">Note: </span>This tool does not support the movement of Agreements and Amendments.&nbsp;<br/> &nbsp;
+
<span style="color:#008000;">'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''</span>
  
−
<span style="color:#008000;">'''456074/439569/439668/467828 &nbsp;– Enhancements to Bulk Upload - Beta version'''</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.
  
−
The beta version of the Bulk Upload functionality has been enhanced. This allows you to:
+
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;
 +
<div class="image-green-border">[[File:7.14 release note 6.png|720px|7.14 release note 6.png]]</div>
 +
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 class="image-green-border">[[File:7.14 release note 7.png|720px|7.14 release note 7.png]]</div>
 +
This is applicable to the following associations:&nbsp;
  
−
*Provision users (which was earlier available only for Legacy Upload)  
+
*Import of Association (Line Item)  
−
*Add Team members when creating an Agreement or Amendment
+
*Auto Attachment Association
−
*Add Team members when updating Agreement or Amendment&nbsp;
+
*Obligation/ Fulfillment (Association of Association)
−
*Create Assignment and initiate the Termination of Agreements
+
 
 +
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.
  
 
&nbsp;
 
&nbsp;
  
−
=== Enhancements to Rules ===
+
<span style="color:#008000;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>
  
−
<span style="color:#008000;">'''288372 – Inclusion of Clauses and Clause properties in Search facets&nbsp;'''</span><br/> ICM has further enhanced the search capabilities by allowing searches on Agreements, Amendments, and Advanced Search based on Clause usage. This allows users to prioritize the Agreements they plan to work based on Clause usage, thus being able to tackle high-risk Agreements first and mitigating risks.<br/> You can now search and filter Agreements using the following Clause categories: Clause Group, Clause Language, Clause Name, Is Alternate Clause, Is Dependent Clause, Is Deviated, Is Editable, Is Mandatory, Perform Deviation Analysis, Primary Clause, and Clause Code.<br/> <span style="color:#FF0000;">Note: </span>Clause Description, Clause Text, Linked Primary Clauses, Clause Status, Linked Primary Template Clause, and search based on Clause text area are also not supported in Clause categories.&nbsp;<br/> &nbsp;
+
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.
  
−
'''<span style="color:#008000;">397346 – Ability to create Rule with ''Has A Value ''condition</span>'''&nbsp;<br/> With this release, the Has A Value condition has been enhanced to include all Data Types and system defined Attributes such that Rules can be set up for an Attribute having any value.<br/> For example, you want to set up a Rule so that an Approver John Doe should approve the Contract if a discount is applicable to it, irrespective of the value of the discount. Then, user can add a Rule using the Has A Value condition, such that John Doe is added as an Approver, if the discount has a value of 5%, 10% or whatever value is desired.&nbsp;<br/> Earlier this condition supported only a limited set of user defined and system Attributes, but now it has been enhanced to support all Data Types and additional system Attributes. It is now also available for the following Contract Type Attributes and Data Types: Contract Type Lookup, Contract Type Multi-Select Lookup, Choice, Multi-Select Choice, Number, Currency, Percentage, Date, DateTime, and URL. In addition, it is also available for system Attributes such as Template Name and Type Of Paper.&nbsp;<br/> &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;
  
−
<span style="color:#008000;">'''408653 – Enhancing Rules to support Power Set conditions for multi-select data&nbsp;'''</span><br/> Currently, ICM supports only the Contains/Does Not Contain conditions for multi-select data. The Contains operator does not check whether all selected values of the Attribute are a subset of expected values, but only checks for any one of them. Thus, when the Rules were evaluated, even the Templates, Approvers, Clauses, etc. that are not required get executed.<br/> To avoid this confusion, Rules have been further augmented so that the user can configure conditions for power sets (i.e. cases where the user wants a Rule to be executed only if the entity field contains a subset of the configured values). This is achieved by introducing the new operator, Subset of, which is applicable to only multi-select lookup that supports evaluation of string, number, user, percentage and email data types only.<br/> Let’s consider the example of a Template Selection Rule to select multiple products using the Subset of operator. Suppose, the Rule is defined such that Template 1 should be selected if the selection is a subset of Products A, B, C, then:&nbsp;
+
Users can now:&nbsp;
  
−
*If the user selects any subset of products {A,B,C} like A,B or B,C or A,C or A,B,C, then Template 1 will be available for selection
+
*Capture multiple valid internal or external email addresses while working on agreements/ requests.
−
*If the user selects any subset of products {A,B,C} & any other product like A,B,C,D or A,B,E, then Template 1 will NOT be available for selection
+
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.
  
 
&nbsp;
 
&nbsp;
  
−
=== Enhancements to Templates ===
+
<span style="color:#008000;">'''583186 – Ability to add amendment on expired agreement'''</span>
  
−
<span style="color:#008000;">'''419834 – Localization of Masterdata Attributes to support bilingual Agreements/Templates &nbsp;'''</span><br/> Earlier, ICM did not directly support bilingual Agreements and Templates. As a result, users had to tag multiple Attributes in a Template for different languages thereby ending up duplicating multiple attributes in a Contract Type.<br/> To simplify this process and facilitate bilingual templates, ICM has introduced the ability to tag the same Masterdata localized Attribute multiple times for different languages which can be tagged in a bilingual Template. This allows the user to manage the same Attribute with a different language in the same Template or Agreement. The support for bilingual templates allows the user to specify the second language for the Template and also be able to tag localized Attributes in the Template with the second language.<br/> <span style="color:#FF0000;">Note:'''&nbsp;'''</span>
+
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.
  
−
*It only supports string Attributes.  
+
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;
−
*Localization of Masterdata Attributes is applicable for - Template level support for Primary/Secondary language, Word Add-in (.NET and Scribe), Agreement and Clause tags, Document Assembly, and Rule-based Assembly.  
+
 
−
*Rules will be evaluated in English for the Masterdata localized Attributes.  
+
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.
−
*Advanced Search also supports the localization of Masterdata Attributes.  
+
<div class="image-green-border">[[File:7.14 release note 8.png|720px|7.14 release note 8.png]]<br/>  </div>
−
*It is not applicable for Associations, Template Variables, Reverse Sync, and support tags on the Parent Agreement Clause.<br/> &nbsp;  
+
<span style="color:#008000;">'''593928 – Ability to configure sender email ID for automated emails'''</span>
−
<div class="image-green-border"><span style="color:#008000;">'''275828 &nbsp;– Clause and Template Harmonization – Beta version'''</span>  
+
 
−
The beta version of the Legacy Upload functionality now provides an option to upload Templates and Clauses in bulk. This allows users to upload Templates, Clauses, Template Metadata, Extended Template Entity Metadata, Template Variables, Clause Metadata, Template Team and Clause Team. It also supports auto-tagging of Templates, Clauses, Template Variables, Contract Type Attributes, Associations and Signatories.&nbsp;<br/> <span style="color:#FF0000;">Note:</span> To enable auto-tagging, the details need to be provided in a set format/syntax.&nbsp;
+
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.
 +
 
 +
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;
 +
 
 +
Administrators can now:
 +
 
 +
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement.
 +
*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">[[File:7.14 release note 9.png|720px|7.14 release note 9.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''<span style="color:#008000;">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.
 +
 
 +
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.
 +
 
 +
With this release:
 +
 
 +
*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).  
 +
*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.
 +
<div class="image-green-border">[[File:7.14 release note 10.png|720px|7.14 release note 10.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''<span style="color:#008000;">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;
 +
 
 +
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;
 +
 
 +
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;
 +
 
 +
<span style="color:#008000;">'''545126 – Availability of business status value in ICI event messages'''</span>
 +
 
 +
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.
 +
 
 +
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.
 +
 
 +
== Mobile App Updates ==
 +
 
 +
'''<span style="color:#008000;">660965 – Refresh agreement list on approval</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;
 +
 
 +
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.
 +
<div class="image-green-border">[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]<br/> &nbsp;</div>  
 +
== ICI API Enhancements&nbsp; ==
 +
<div class="image-green-border">
 +
<span style="color:#008000;">'''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.
 +
 
 +
Enhancements include:
 +
 
 +
*Addition of Masterdata APIs&nbsp;  
 +
**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.
 
</div>  
 
</div>  
−
== Enhancements to Artificial Intelligence Apps in ICM ==
+
== Enhancements to ICI Add-ins&nbsp; ==
 +
 
 +
<span style="color:#008000;">'''714872 – Improved document usability'''</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;
 +
 
 +
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:#008000;">'''386571 – Enhancements in AI Apps&nbsp;'''</span><br/> The Negotiate AI, Obligation AI and Visualize AI app have been merged to the ICM platform and these apps have been enhanced to improve their usability.
+
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.
 +
<div class="image-green-border">[[File:7.14 release note 4.png|720px|7.14 release note 4.png]]</div> <div class="image-green-border">&nbsp;</div>  
 +
With this release:
  
−
*The ''Negotiate AI ''app has been enhanced to provide the following functionality for an ICM user in context of a contract being viewed in MS Word:
+
*All the content controls are put together in a single paragraph on any line with valid content.
−
**Agreement Clause Similarity functionality
+
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.
−
**Agreement Similarity functionality
+
*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.
−
**UX improvements 
+
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&nbsp;
−
*The ''Obligation AI ''app has been enhanced to:
+
*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.
−
**Incorporate user actions feedback in subsequent obligation discovery without extensive re-training of the model
+
<div class="image-green-border">[[File:7.14 release note 5.png|720px|7.14 release note 5.png]]</div> <div class="image-green-border">&nbsp;</div>
−
**Support Obligation discovery on Templates 
+
'''Note''':&nbsp;
−
*The ''Visualize AI'' app has been enhanced using hooks that have been provided to support custom visualization. These hooks will be present at the following stages:  
+
−
**Data Fetching
+
−
**Data Transformation
+
−
**Data Rendering 
+
  
−
<span style="color:#FF0000;">Note:&nbsp;</span>These apps are available in ICM through a technical configuration. They work on Microsoft Office 2016 for Windows version 16.0.4390.1000 or later, and Office .JS installed.
+
*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;
 
&nbsp;
−
<div class="image-green-border"><span style="color:#008000;">'''387056 – Add support for Table Discovery&nbsp;'''</span><br/> With this release, the''Discover AI ''app has been further enhanced to include Table discovery. Along with Clause and metadata, ICM now also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the Details page on the Table Discovery tab, so that relevant action can be taken on them as required. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&nbsp;<br/> The table discovery allows you to:</div>
 
−
*Discover the Associated Document data and the Association type if present in the uploaded Agreement document
 
−
*Update the table if needed
 
−
*Create a new Associated Document in ICM once the data is finalized
 
−
<div class="image-green-border"><span style="color:#FF0000;">Note: </span>Only .docx document format is supported.&nbsp;<br/> &nbsp;</div>
 
−
== Enhancements to ICM Add-ins ==
 
  
−
'''<span style="color:#008000;">334171 – Enhancements in Email Outlook Plugin (.JS version) &nbsp;</span>'''<br/> With this release, a new .JS version of the ICM Outlook Plugin has been introduced. The overall turnaround time for the author is reduced as he no longer needs to download the documents received over email to the local machine, then switch applications and log in to ICM, search the Agreement and then upload the documents.<br/> The provisioned user can now:
+
<span style="color:#008000;">'''660390 – Ability to show more clauses per group'''</span>
  
−
*Upload the next version of the Agreement document received over an Email to the Agreement
+
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.
−
*Upload the next version of the Associated document (supporting Attachments) received over an Email to the Agreement
+
−
*Create a new Association instance and then upload the Associated Document received over an Email to the Agreement
+
  
−
The configuration of the Outlook Add-in is driven by the Masterdata, whereas the list of Agreements and their details are configured by the Saved Searches. You can configure multiple saved searches. This is available for MS Outlook online as well as the Desktop client.&nbsp;
+
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.
 +
<div class="image-green-border">[[File:7.14 release note 12.png|720px|7.14 release note 12.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
<span style="color:#008000;">'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''</span>
  
−
'''<span style="color:#008000;">397327 – Ability to drive dependency of Template Variables on Agreement Attributes&nbsp;</span>'''<br/> With this release, ICM has extended support to Template Variables being conditional to the value of the Attributes that are part of a Contract Type. The user can track the dependency between the Contract Type Attribute and Template Variable as well as eliminate the creation of duplicate Attributes between them.&nbsp;<br/> This can be achieved by any user with Manage access on Template Management tile by enabling the Is Conditional flag for each Template Variable when creating or editing a Template. When Is Conditional is On, a user is able to set a dependent condition on the Template Variable by using Depends on Contract Type Attribute flag On and its related Depends On Attribute drop-down and Depends On Value field.&nbsp;<br/> The following conditions decide the dependency between the Template Variable and Contract Type Attribute: &nbsp;
+
In ICI, users capture additional details for clauses and templates in the extended attributes.
  
−
*When ''Depends on'' ''Contract Type Attribute'' is ''On,&nbsp;''then it displays the Contract Type Attribute in the ''Depends On Attribute'' drop-down list.&nbsp;  
+
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.
−
*When ''Depends on'' ''Contract Type Attribute'' is ''Off,'' then it displays the Template Variable in the''Depends On Attribute'' drop-down list.&nbsp;
+
<div class="image-green-border">[[File:7.14 release note 13.png|720px|7.14 release note 13.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">'''<span style="color:#008000;">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.
  
−
For each selected Attribute from ''Depends On Attribute'' drop-down list, the user can then enter the ''Depends On Value ''that will drive the dependency.&nbsp;<br/> &nbsp;
+
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">[[File:7.14 release note 14.png|720px|7.14 release note 14.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.14 release note 15.png|720px|7.14 release note 15.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''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">[[File:7.14 release note 16.png|720px|7.14 release note 16.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''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;
 +
 
 +
== Enhancements to Artificial Intelligence Applications in ICI ==
 +
 
 +
<span style="color:#008000;">'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''</span>
 +
 
 +
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.
 +
 
 +
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.
 +
 
 +
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.
 +
 
 +
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.
 +
<div class="image-green-border">[[File:7.14 release note 17.png|720px|7.14 release note 17.png]]</div>
 +
Negotiators can now:
 +
 
 +
*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">[[File:7.14 release note 18.png|720px|7.14 release note 18.png]]</div>
 +
By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.
 +
 
 +
<br/> <span style="color:#008000;">'''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.
  
−
<span style="color:#008000;">'''384321 – Deviation Tracking when Association is tagged as a Table&nbsp;'''</span><br/> Previously, modifications made to Associations or Saved Search (such as adding or removing rows/columns or changing the values in individual cells) that were tagged as a table in a Template did not reflect in the new version of the Agreement document.&nbsp;<br/> With this release, redlining of these changes will be visible on the Versions tab of the Agreement Document, thus allowing the contract negotiator to make informed decisions accordingly.&nbsp;<br/> <span style="color:#FF0000;">Note: </span>Deviation tracking and reverse sync of the changed table data to the respective Association instances is not supported. ICM Scribe supports this capability unlike ICM .Net Add-in but provides limited information. Table comparison is only shown when cell values get changed not when empty cells get added or removed.&nbsp;
+
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;
  
 +
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.
 +
<div class="image-green-border">[[File:7.14 release note 19.png|720px|7.14 release note 19.png]]</div> <div class="image-green-border"><br/> '''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>
 
&nbsp;
 
&nbsp;
 +
 +
'''<span style="color:#008000;">663666 – Enhancing inbuilt discovery model to include additional attributes&nbsp;</span>'''
 +
 +
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;
 +
 +
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;
 +
 +
<span style="color:#008000;">'''575466 – Support for additional languages in AI apps&nbsp;'''</span>
 +
 +
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&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.
 +
 +
With this release:
 +
 +
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration.
 +
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document.
 +
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI.
 +
*While discovering or matching the clause from clause library, document language is taken into consideration.
 +
*The additional languages are supported while discovering similar clauses.
  
 
== Enhancements to Reports ==
 
== Enhancements to Reports ==
  
−
<span style="color:#008000;">'''275838 – All Reports should display Date and Time in Time Zone set by user in User Preferences &nbsp;'''</span><br/> With this release, all reports now display the Date and Time in the Time Zone set by the user in User Preferences.&nbsp;<br/> Previously, all date related columns and parameters in all ICM reports were displayed in the UTC Time Zone in the mm/dd/yyyy format. This led to a discrepancy with the dates displayed in ICM which were as per the locale settings in the user preferences. With this release, all reports will also display the Date and Time as per the Time Zone set by the user in the user preferences.&nbsp;
+
<span style="color:#008000;">'''514594 – Capability of time zone in reports'''</span>
  
−
However, the following points need to be noted:
+
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.
 +
<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:#008000;">'''514609 – Introducing the Clause Summary Report'''</span>
  
−
*The UTC format disclaimer has been removed.  
+
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;
−
*When reports are exported to CSV format, the Date and Time format of the Date columns will be as per the user's local machine format, not as per the User Preferences set in ICM.  
+
−
*In all the reports where dates are input parameters, the default value of parameter on first time load&nbsp;will be displayed as per UTC time zone (as SSRS report server has UTC time zone set). However, when the user inputs any date thereafter, the reports will be generated as per the user's local time zone.
+
−
*If the Date format selected is ''dd-mmm-yy'', then there is technical limitation of displaying same format for dates in parameter section, as it converts the Date to Month and vice versa. Hence, as a workaround, the Date format in the report parameter is displayed as ''mmmm dd,yyyy''. However, the Date format in report data will be shown as per the user preferences only.
+
−
*All other date formats remain unimpacted.
+
  
−
<span style="color:#008000;">'''385409 – New Reports added to KPIs&nbsp;'''</span><br/> Earlier, only few reports were available on the Dashboard as KPI. &nbsp;Now, the user can also add the following reports as KPI tiles (through Security Groups) for user accessibility:
+
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;
  
−
*''Cycle Time Report:'' Average cycle time of all Agreement of all Contract Types in Days
+
This default report is accessible from the Admin category of reports and its access is based on Security Groups.
−
*''Template Clause Report: ''Average number of Clauses per Template with Template and Clause Is Latest = Yes
+
<div class="image-green-border">[[File:7.14 release note 20.png|720px|7.14 release note 20.png]]<br/> &nbsp;</div>
−
*''Expired Agreements Report:'' Count of Agreements expired in the last 30 days
+
== Integrations ==
−
*''Approved Requests for Contract Initiation Report: ''Count of Requests pending for Contract initiation
+
−
*''Signature Type Report:'' Percentage of Contracts with electronic signature with no decimal digits (% sign to be shown)
+
−
*''User Login Report:'' Count of Users logged in last 30 days
+
−
*''CLM Activity Report:'' Count of Contracts executed in last 30 days
+
  
−
For example, the Signature Type Report KPI depicts the percentage of electronic signature in ICM. If the number of electronic signatures is 6 and the number of manual signatures is 83, then the KPI is calculated as 6/83+6 = 6/89 (total number of agreements). Therefore, the percentage of electronic signatures is 6 (which is the number displayed on the KPI tile on the Dashboard).
+
<span style="color:#008000;">'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''</span>
  
−
The reports that were already present as KPIs on the Dashboard included the ''Agreement Deviation Report, Agreements Pending Approval Report, Agreements Pending Execution Report, Average Agreement Turn Around Time Report, Clauses Pending Approval Report, Expiring Agreements Report, ''and the''Templates Pending Approval Report.''
+
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, 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;
 +
 
 +
Salesforce users can now:&nbsp;
 +
 
 +
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&nbsp;
 +
*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">[[File:7.14 release note 21.png|720px|7.14 release note 21.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
<span style="color:#008000;">'''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;
 +
 
 +
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;
 +
 
 +
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.
  
 
&nbsp;
 
&nbsp;
  
−
== Integrations ==
+
<span style="color:#008000;">'''635822 – Support for pre- and post-processing in Generic Integration Framework'''</span>
  
−
=== Integrations with Collaboration Tools ===
+
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;
  
−
<span style="color:#008000;">'''370460 – ICM Integration with MS Teams&nbsp;'''</span><br/> By integrating the ICM platform with MS Teams, users can collaborate for contract authoring, negotiations, etc. This not only provides a better, seamless user experience, but also helps to discuss ideas or exchange files, and in turn significantly improve the cycle time. You can ping, chat with members within or outside the Agreement Team. The chat will be saved in the MS Teams History.&nbsp;<br/> Through this integration, we support:
+
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:
  
−
*Exposing ICM Bot through the Teams app
+
*Pre-process inbound data through file-based integrations.
−
*Querying for a filtered list of Agreements using ICM Bot
+
*Pre-process inbound and outbound data through ASB-based integrations.
−
*Querying My Pending Tasks using the ICM Bot&nbsp;
+
−
*General ICM FAQ
+
  
−
=== Icertis Experience for&nbsp;Salesforce ===
+
ICI administrators will now be able to:&nbsp;
  
−
<span style="color:#008000;">'''348588 – Configuring Field Set from Salesforce to ICM using Rest API&nbsp;'''</span><br/> With this release, a new field called Field Set Name has been introduced that can be configured using the Configuration page which is accessible through the managed application available in Salesforce AppExchange. When the integration is triggered from Salesforce, the Adapter can read the metadata and send only the Attributes defined for the entity Field Set. If the Field Set is not defined, the Adapter sends all the Attributes for that entity. &nbsp;<br/> <span style="color:#FF0000;">Note: </span>It is necessary to create a new Field Set for every Salesforce entity. The field set determines the fields that the user can edit in a particular Salesforce entity instead of having to select each field individually. For example, a Field Set created for an Opportunity can have fields such as Opportunity Name, Opportunity ID, etc.&nbsp;
+
*Enable or disable the hook as part of file-based and ASB integration.
 +
*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.  
  
−
<span style="color:#008000;">'''397315 – Create mapping between Template Variable for Agreements and SFDC fields'''</span>&nbsp;<br/> The ICM Salesforce Adapter allows mapping of Salesforce entities and their Attributes to be integrated with ICM for data flow from Salesforce to ICM (Forward Sync) as well as ICM to Salesforce (Reverse Sync). This was previously done using Client App Entity Mapping on the Masterdata Configuration page which allows mapping the ICM Attributes from Contract Types, but not from Agreement Templates.<br/> With this release, Administrators can now use Attributes defined at Template level to store critical external data as part of the Agreement and sync with Salesforce, thus avoiding data duplication and redundancy in the process.<br/> &nbsp;
+
&nbsp;
  
−
=== Icertis Experience for&nbsp;Workday ===
+
<span style="color:#008000;">'''635823&nbsp;– Support for defining folder structure in Generic Integration Framework'''</span>
  
−
<span style="color:#008000;">'''384529 – Executed PDF from ICM to Workday&nbsp;'''</span><br/> Customers using Workday ERP application to manage their procure-to-pay process want to have end-to-end integration to Icertis Contract Management (ICM) platform for managing their procurement process.&nbsp;<br/> Icertis platform already supports integration to Workday Financials and HCM via an Adapter. As part of this integration, contracts authored in the ICM platform can be sent to Workday via the Adapter and attached to Workday contracts in .docx format.&nbsp;<br/> Now, with the help of Event based configuration in the Adapter, it is possible to send the Agreement document in .PDF or .docx format to Workday for a specific event.&nbsp;<br/> &nbsp;
+
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.
  
−
=== Enhancements to Adobe Sign and DocuSign ===
+
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.
  
−
<span style="color:#008000;">'''344436 – Support for Print, sign and upload (Wet Signed Copy) and sync back in ICM&nbsp;'''</span><br/> Adobe Sign provides users the capability of signing documents manually using Print, sign and upload option. However, earlier when the Agreement Document was Wet signed and uploaded, it did not get synced back to ICM, and the Agreement would get blocked in that state. With this release, ICM supports syncing back the signed Agreement document and changed status, so that the user can proceed with the workflow as expected.<br/> <span style="color:#FF0000;">Note:&nbsp;</span>
+
With this release, users have:&nbsp;
  
−
*If the Wet Signatures Only option is checked, then system mandates all the users to sign the Agreement document using the Print, sign and upload option of Adobe Sign.&nbsp;
+
*Support for single or multiple folders in the folder structure.  
−
*If the Wet Signatures Only option is not checked, then users can either sign it electronically or use the Print, sign and upload option to sign it manually. However, in this case if any user signs using the Print, sign and upload option, since all the Signature tags will be lost, Adobe Sign will add an additional page to the end of Agreement document that will have signature tags for subsequent signatories who are yet to sign.&nbsp;
+
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format).  
−
*Attribute sync back to ICM will only work for the first signatory. Once Adobe Sign’s Print-Sign-Upload option is used, Attribute tags are not available for subsequent signatories who are yet to sign the document.  
+
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change.  
−
*In case of parallel signatures, the Wet Signature option is not applicable. If the Wet Signature Only option is checked, then the Agreement will be stuck in the Approved state.&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.  
−
<div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''430578 – Send Additional Supporting Documents to Adobe Sign&nbsp;'''</span><br/> The current Send for Signature functionality only allows users to send the main Agreement for signature. It does not allow users to add the supporting documents along with the main Agreement document. With this release, ICM will support Preview and sending of the associated documents (Attachments) along with the main Agreement for signature.&nbsp;<br/> <span style="color:#FF0000;">Note:</span> Only Agreement specific tags will be displayed in the Agreement document when reviewing and signing it. After the Agreement document is signed, only Agreement will be synchronized with ICM again.&nbsp;</div> <div class="image-green-border">The Associated Documents (attachments in the Word or PDF format that is associated to the main Agreement) will be available for selection when sending it for signature.&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
+
−
== Technical Requirements for Release 7.9 ==
+
  
−
The Icertis Contract Management base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available in all the environments, and specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.
+
&nbsp;
  
−
[[File:Technical Requirements 1.PNG|Technical Requirements 1]]
+
== Partner Enablement ==
  
−
[[File:Technical Requirements 2.PNG|Technical Requirements 2]]
+
<span style="color:#008000;">'''703386 – Icertis Software Development Kit for Partner Enablement'''</span>
  
−
[[File:Technical Requirements 3.PNG|Technical Requirements 3]]
+
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 them with the resources and tools that they need while implementing ICI.&nbsp;
 +
 
 +
As part of our continuous efforts to support our partners, we have created the following documents in this release:
 +
 
 +
*'''ICI Coding Guidelines''':&nbsp;This document helps developers to follow specific guidelines and best practices while coding. This will help them reduce time in development, reduce errors, maintain consistency and enhance collaboration. The document focuses primarily on the .Net framework as platform and C# as the object-oriented programming language.
 +
 
 +
*'''ICI Developer Library''': This document provides a detailed insight into the ICI developer methods library used for various functions and functionalities. It provides a detailed listing of all the methods in ICI development covering multiple parameters such as the summary of the functionality, dependencies, input parameters, return parameters, exceptions and code snippets on how to call the methods.
 +
 
 +
*'''Local Environment Setup using ICI Binaries''': This document provides guidance to Icertis partner developers on how to set up and deploy ICI on their development machines using ICI’s deployable binaries and packages. These binaries and packages are published by Icertis for every GA version.&nbsp;'''&nbsp;'''
 +
 
 +
*'''ICI Customization and Use Cases: '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations.
 +
 
 +
&nbsp;
 +
 
 +
== Technical Requirements for Release 7.14 ==
 +
 
 +
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.
 +
 
 +
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]
 +
 
 +
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]
 +
 
 +
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]
 +
 
 +
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]
 +
 
 +
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]
 +
 
 +
&nbsp;
 +
 
 +
&nbsp;
  
−
[[File:Technical Requirements 4.PNG|Technical Requirements 4]]
+
'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|

Latest revision as of 12:24, 1 October 2020

ICI Release Notes - Release 7.14

Overview of Release 7.14

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

The key enhancements of this release include:

  • Enhancements to the ICI Application
  • User Experience
    • Introducing a horizontal chevron which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron, namely Generate, Approve, Execute and Manage, prominently communicate an entity’s journey including the previous, current and possible future states of the agreement.
    • Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement.
    • Facilitating one-click navigation from the ICI record to any related entities (multi-hierarchy level). For example, from RFx to Bid Response which would otherwise require multiple clicks.
    • Providing administrators the ability to configure access control for users who are not part of the team to sections or sub-sections in the left navigation pane at the contract type level.
    • Enhancing document usability by placing content control tags such that the end-user no longer views separate lines in the assembled document for assembled clauses that are not evaluated.
  • Workflow Enhancements
    • Displaying the organization unit path of the parent document by default as the path for the associated document, so that both parent and child documents have the same organization path at the time of creation and updation.
    • Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle.
    • Providing the ability to add amendments to expired agreements.  
    • Adding a time zone attribute to provide enterprise organizations the flexibility to track the time zone or region-based activities as needed for the instance of the agreement.
    • Providing the capability to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications and allowing configuration of the sender’s email ID dynamically based on the specific contract type or instance of the record. 
  • Mobile App Updates
    • Improving the usability of the mobile app by refreshing the agreement or requests list automatically after an approve, reject or request review action is performed.
  • Enhancements to ICI API 2.0
    • Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata.
  • Enhancements to ICI Add-ins
    • Icertis Experience for Word
      • Displaying a set of 30 clauses per page with pagination for easy navigation between clauses listed on the clauses, clauses in templates and clauses in agreement pages.
      • Providing extended attributes within the add-in for creation and modification of clauses and templates.
      • Allowing the deviation approver to view and directly approve or reject clause deviations in an agreement from within the add-in.
      • Displaying a validation message in clause content control enabling users to insert and tag clauses at the correct location in the document before publishing it.
    • Outlook Add-in
      • Enhancing the Outlook Add-in by providing the ability to upload email in .docx or .msg format as associated documents for an agreement from within Outlook.
  • Enhancements to Artificial Intelligence Applications
    • Introducing a legal playbook in the NegotiateAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.
    • Enhancing DiscoverAI to identify the different levels within a clause through a distinct visual representation of clauses with sub-sections displayed in a delineated view during the clause discovery process.
    • Enhancing the ICI discovery models to support clause and obligation discovery for additional languages such as German, Spanish and Portuguese.
    • Improving the inbuilt DiscoverAI model to identify additional attributes such as City, State, Zip Code, and so on.
  • Enhancements to Reports
    • Introducing the Risk Assessment Report which is a trendline chart report that depicts the agreement aggregate risk score by their version. ICI’s AI algorithm identifies the playbook exceptions for a new version.
    • Introducing the Clause Summary Report to help clause administrators to understand and assess the impact of changes made to a clause.
    • Providing users the capability to generate a report as per the time zone of their choice from within the report itself.
  • Improving the Icertis Experience
    • Extending support for ICI dashboard widgets in the Icertis Experience for Salesforce Home page, so that users can perform all necessary actions from within Salesforce itself.
    • Supporting auto-renewal and reset expiry functionalities in Icertis Experience for Workday, thus saving time and avoiding data duplication.
    • Enhancing the generic integration framework to support custom pre- and post-processing hooks to considerably reduce implementation time, and allowing users to define and configure folder structure and file names as per the business requirement.
  • Additions to Icertis Software Development Kit for Partner Enablement
    • In release 7.12, the Software Development Kit (SDK) was released to support partners for technical configuration. With this release, documentation for ICI coding guidelines, ICI developer methods, local environment setup using ICI binaries, and ICI customization and use cases are also available.

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

 

ICI Application Enhancements

659853 – Upfront chevron view of agreement journey

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. 

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. 

With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.

The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.

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:

1. Generate: Displays the list of actions taken by the user on the agreement before it is published.

2.Approve: 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. 

3. Execute: Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.

4. Manage: Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.

Note: 

  • The chevron view is only applicable to agreement contract type (agreement and amendment).
  • By default, the chevron is disabled; it can be enabled for selected contract types.
  • The chevron labels support localization.
7.14 release note 1.png
 

512931 – Visibility of sections on the left navigation pane to non-team users

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. 

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.
 

659725 – Ability to easily navigate to related entities in multi-level hierarchy

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.

Configurators can: 
  • Configure a smart link across any ICI entity that defines the entity relationships.
  • Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities.

Users can: 

  • Click on the left navigation link from an agreement contract type that will render the smart link result in grid. 
  • Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results.
7.14 release note 2.png
 
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.
 
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.

For example, consider entities related in multi-level hierarchy as Agreement > Obligations > Fulfillments. Earlier users had to navigate through obligations in order to access the child fulfillments.
 
Users can now navigate directly from parent agreement to 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.

7.14 release note 3.png

 

584439 – Introducing the Contract Manager role for agreements 

In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.

This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process. 

Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.

With this release: 

  • Assignment of the user against contract manager role in the team can be only achieved through event rules using the Add To Team action.
  • 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 agreementTeam tab similar to primary owner role user.

 

555890 – Ability to create peer agreement from within the base agreement

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. 

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.

 

732038 – Ability to use parent’s Organization Unit path when creating associated document

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.

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. 

7.14 release note 6.png

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

7.14 release note 7.png

This is applicable to the following associations: 

  • Import of Association (Line Item)
  • Auto Attachment Association
  • Obligation/ Fulfillment (Association of Association)

The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.

 

575665 – Ability to capture multiple email IDs in a single data type

Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.

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. 

Users can now: 

  • Capture multiple valid internal or external email addresses while working on agreements/ requests.
  • Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.

 

583186 – Ability to add amendment on expired agreement

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.

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. 

The Add Amendment action is configurable through role action mapping on the expired state of the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.

7.14 release note 8.png
 

593928 – Ability to configure sender email ID for automated emails

Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.

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. 

Administrators can now:

  • Configure the sender information while setting up the subscription under Notifications using the specific user and/ or user attribute information in the agreement.
  • 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.
7.14 release note 9.png
 

593938 – Time Zone support for date-dependent automated processes

In ICI, there are scheduled jobs that perform certain actions on 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.

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.

With this release:

  • 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).
  • 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: The time zone-based processing can be enabled for all contract types across 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.

7.14 release note 10.png
 

512930 – Triggering service bus events for all actions

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. 

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. 

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.
 

545126 – Availability of business status value in ICI event messages

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.

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.

Mobile App Updates

660965 – Refresh agreement list on approval

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. 

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.

7.14 release note 11.png
 

ICI API Enhancements 

607867 – ICI API 2.0 Implementation

With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.

Enhancements include:

  • Addition of Masterdata APIs 
    • 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.

Enhancements to ICI Add-ins 

714872 – Improved document usability

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. 

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.

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.

7.14 release note 4.png
 

With this release:

  • 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. 
  • 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.
7.14 release note 5.png
 

Note: 

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

 

660390 – Ability to show more clauses per group

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.

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.

7.14 release note 12.png
 

707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word

In ICI, users capture additional details for clauses and templates in the extended attributes.

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.

7.14 release note 13.png
 
 
664488 – Ability to take deviation workflow actions from Icertis Experience for Word

Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.

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.

7.14 release note 14.png
 
7.14 release note 15.png
 
 
660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word
 
Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.
 
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.
 
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.
 
7.14 release note 16.png
 
 
667815 – Ability to upload email as association of an agreement using Outlook Add-in
 
Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in. 
 
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.
 
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.

 

Enhancements to Artificial Intelligence Applications in ICI

662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word

With this release, ICI is introducing a legal playbook in Icertis Experience for Word 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.

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.

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.

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.

7.14 release note 17.png

Negotiators can now:

  • 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.
7.14 release note 18.png

By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.


575450 – Supporting clause hierarchy in .docx agreements

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.

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. 

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.

7.14 release note 19.png

Note: Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document. 

 

663666 – Enhancing inbuilt discovery model to include additional attributes 

The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents. 

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.
 

575466 – Support for additional languages in AI apps 

Previously, the ICI clause and obligation discovery models were primarily based on the English language. 

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.

With this release:

  • Additional language support is available in NegotiateAI and DiscoverAI for legacy migration.
  • Discovered clauses and obligations are displayed and then linked back to the matching text in the original document.
  • Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI.
  • While discovering or matching the clause from clause library, document language is taken into consideration.
  • The additional languages are supported while discovering similar clauses.

Enhancements to Reports

514594 – Capability of time zone in reports

ICI reports display the date and time values based on the Time Zone selected in the Locale Settings under Preferences.

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

514609 – Introducing the Clause Summary Report

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. 

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. 

This default report is accessible from the Admin category of reports and its access is based on Security Groups.

7.14 release note 20.png
 

Integrations

554867 – Support for ICI dashboard in Icertis Experience for Salesforce

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. 

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. 

Salesforce users can now: 

  • Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab. 
  • View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets. 
  • Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab.
7.14 release note 21.png
 

583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday

The Icertis Experience for Workday supports Create and Update events for agreements and amendments. 

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. 

These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.

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

 

635822 – Support for pre- and post-processing in Generic Integration Framework

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. 

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:

  • Pre-process inbound data through file-based integrations.
  • Pre-process inbound and outbound data through ASB-based integrations.

ICI administrators will now be able to: 

  • Enable or disable the hook as part of file-based and ASB integration.
  • 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.

 

635823 – Support for defining folder structure in Generic Integration Framework

Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.

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, users have: 

  • Support for single or multiple folders in the folder structure.
  • 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.
  • 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.

 

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 them with the resources and tools that they need while implementing ICI. 

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

  • ICI Coding Guidelines: This document helps developers to follow specific guidelines and best practices while coding. This will help them reduce time in development, reduce errors, maintain consistency and enhance collaboration. The document focuses primarily on the .Net framework as platform and C# as the object-oriented programming language.
  • ICI Developer Library: This document provides a detailed insight into the ICI developer methods library used for various functions and functionalities. It provides a detailed listing of all the methods in ICI development covering multiple parameters such as the summary of the functionality, dependencies, input parameters, return parameters, exceptions and code snippets on how to call the methods.
  • Local Environment Setup using ICI Binaries: This document provides guidance to Icertis partner developers on how to set up and deploy ICI on their development machines using ICI’s deployable binaries and packages. These binaries and packages are published by Icertis for every GA version.  
  • ICI Customization and Use Cases: This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations.

 

Technical Requirements for Release 7.14

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.

7.14 release note 22.png

7.14 release note 23.png

7.14 release note 24.png

7.14 release note 25.png

7.14 release note 26.png

 

 

Related Topics: Agreement Management | Association Management | Compliance Management | Template Management | Clause Management | Configuration | Reports | Advanced Analytics | User Administration | ICI Tools |  Icertis Business Apps | AIML | ICI Add-ins | ICI Mobile_App | ICI Business Apps Release Notes |

Retrieved from "https://iciwikiapac.icertis.com:14443/ICIHelp7.14/index.php?title=Release_Notes&oldid=15511"