From ICIHelp8.2
Jump to: navigation, search
 
(117 intermediate revisions by 6 users not shown)
Line 1: Line 1:
  
−
= ICI Release Notes - Release 7.14 =
+
= ICI Release Notes - Release 8.2 =
  
−
== Overview of Release 7.14 ==
+
Apart from new features and enhancements, this document contains information on:
  
−
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.
+
*[[#_Technical_Requirements_1|Technical Requirements]]
 +
*[[#_Accessibility_Conformance|Accessibility Conformance]]
 +
*[[#_Known_Issues|Known Issues]]
  
−
The key enhancements of this release include:
+
Refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.2/index.php?title=ICI_Help Wiki] documentation (also found in your ICI help section) for details on all ICI features and functionalities.
  
−
*<span style="color:#008000;">'''Enhancements to the ICI Application'''</span>
+
= New Features and Enhancements =
  
−
*'''''User Experience'''''
+
== Contract Authoring & Management&nbsp; ==
−
**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>
+
=== Amend contracts preserving previously negotiated terms ===
−
**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>
+
'''What''' – When users amend a contract, they now have a choice to either use the base agreement or a previously negotiated and amended contract. Along with the contract version, users can also choose the associations to copy to the amendment.
−
**''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>
+
'''Advantages''' – Maintaining a history of the original agreement and all amendments is now possible. This helps in auditing the changes made to contracts over time.
−
**Introducing a legal playbook in the WordAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.  
+
−
**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>
+
'''How''' – Options to choose the amendment and copy associations to the amendment are now available when creating an amendment. Users can associate and inherit documents such as NDA, SOW, etc.
−
**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>  
+
'''Value''': Compliance | User Experience<br/> '''For''': Legal Team | Authors | Contract Managers<br/> '''Feature ID''': 1233193
−
**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>
+
=== Send multiple agreements packaged in a single envelope for electronic signature ===
−
**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.
+
'''What''' – Earlier, agreement could be bundled only with its associations and sent for electronic signature. With this release you can also bundle peer agreements in a single package for electronic signing.
  
−
&nbsp;
+
'''Advantages – '''Eliminates the need to send one agreement at a time for signature, thereby saving time. Provisions setting a sequence in which the agreements must be signed and facilitates reordering if required.
  
−
<span style="color: rgb(0, 119, 235); font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span>
+
'''How - '''Existing Esign functionality is enhanced to package peer agreements as a single bundle and send it for electronic signature.
  
−
<span style="color:#008000;">'''659853 – Upfront chevron view of agreement journey'''</span>
+
'''Value''': User Experience | Contract Building Performance<br/> '''For''': Contract Owners | Legal Compliance Team<br/> '''Feature ID''': 1369302
  
−
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;
+
=== Quickly create and edit contract types in bulk using excel workbook ===
  
−
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;
+
'''What''' – ICI now allows its users to edit and create contract types in bulk using the Microsoft Excel workbook. User can also edit multiple attributes for multiple contract types at once.
  
−
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.
+
'''Advantages'''
  
−
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.
+
Contract type (CT) changes happen frequently in the implementation phase, the feedbacks from the customers regarding the changes in the CT have to be earlier implemented one by one for each CT in ICI UI. Now, this changes and edits can be done in one go using this feature.
  
−
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:
+
Creating and editing multiple contract types at once will reduce time involved in configuring large contract types.
  
−
1.&nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.
+
'''How'''
  
−
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;
+
A button “Bulk Contract Type” is now added under “Configure” tile.
  
−
3. '''Execute:&nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.
+
Users can generate pre-seeded contract type workbook, with 2 tabs in excel, contact type, and contract type attributes.
  
−
4. '''Manage:&nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.
+
'''Value''': User Experience<br/> '''For''': Admins | Legal Team | Contract Managers<br/> '''Feature ID''': 1342050
  
−
'''Note''':&nbsp;
+
== Icertis Experiences ==
  
−
*The chevron view is only applicable to agreement contract type (agreement&nbsp;and amendment).
+
=== Rules functionality added to Icertis Experience for Word ===
−
*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;
+
'''What''' – Users can now create rules for assembling the clause and define the rules for selecting the template from within Microsoft Word to display clauses in agreements based on specified conditions. Existing rules can also be viewed or edited from Microsoft Word.
  
−
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;
+
'''Advantages – '''Provides a familiar and intuitive interface for legal teams and contract authors to create conditional agreement templates.
  
−
<span style="color:#008000;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>
+
Reduced turnaround time, instead of switching while creating the clause and template
  
−
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.
+
'''How – '''Users can define conditions for selecting a clause or template while assembling of clauses and selection of templates from Microsoft Word.
−
<div class="image-green-border">Configurators can:&nbsp;</div>  
+
<div class="image-green-border">[[File:8.2 RN 01.png|300px|8.2 RN 01.png]]&nbsp;&nbsp;[[File:8.2 RN 02.png|300px|8.2 RN 02.png]]</div>  
−
*Configure a smart link across any ICI entity that defines the entity relationships.
+
'''Value''': User Experience<br/> '''For''': Legal Team<br/> '''Feature ID''': 1117626
−
*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;
+
=== Outlook Add-in – Labeling and validation for emails added to ICI ===
  
−
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp;
+
'''What – '''Every email uploaded in ICI will now display an Outlook category label, that helps users know if the email is already added in ICI. Additionally, a validation is also displayed if user tries uploading same emails twice. Users can customize the outlook category label as per the needs.
−
*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;
+
  
−
'''<span style="color:#008000;">584439 – Introducing the Contract Manager role for agreements&nbsp;</span>'''
+
'''Advantages – '''Avoid uploading duplicate email conversations in ICI.
  
−
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.
+
'''How – '''This feature is available as part of Icertis Experience for Outlook.
 +
<div class="image-green-border">[[File:8.2 RN 03.png|600px|8.2 RN 03.png]]</div>
 +
'''Value''': User Experience<br/> '''For''': Contract Managers | Legal Teams<br/> '''Feature ID''': 1341557&nbsp;
  
−
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;
+
=== Revamping ICI Salesforce User Experience ===
  
−
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.
+
'''What''' – Revamping the ICI Salesforce user interface to give a better user experience, with addition of features and enhancement under agreement related sub tabs.
  
−
With this release:&nbsp;
+
The following agreement sub tabs can now be seen with new capabilities:
  
−
*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.
+
*Associations sub tab
−
*Only one contract manager is available inside the agreement at any given point of time.
+
*Amendment sub tab
−
*The contract manager will have provisions same as that of primary owner.
+
*Note sub tab
−
*The contract manager name is displayed on the agreement summary page.
+
*Team sub tab
−
*Agreements can be searched using the contract manager name.
+
*Collaboration sub tab  
−
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user.
+
  
−
&nbsp;
+
Some new features include:
  
−
<span style="color:#008000;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>
+
Hyperlink added in the first column of the association list grid navigating to the association details page within ICI Salesforce platform.
  
−
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;
+
Ability to preview the document from amendments sub tab.
  
−
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''.
+
The collaborations tab is now revamped from ICI Iframe to Salesforce native look and feel, with capability to view more messages.
  
−
&nbsp;
+
'''Advantages '''– This revamp will be giving a more consistent and familiar user experience with enhanced look and feel inline with Salesforce native user experience across tabs, subtabs and actions for sales personas.
  
−
<span style="color:#008000;">'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''</span>
+
'''How''' – Below are few screenshots of the revamped ICI Salesforce platform.
  
−
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.
+
New ICI Salesforce Agreement Details screen
 +
<div class="image-green-border">[[File:8.2.RN 1.png|720px|8.2.RN 1.png]]</div>
 +
New Add Note Dialog box
 +
<div class="image-green-border">[[File:8.2.RN 2.png|720px|8.2.RN 2.png]]</div>
 +
'''Value''': User Experience<br/> '''For''': Sales Team<br/> '''Feature ID''': 1356012
  
−
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;
+
=== Salesforce – Visibility of products and services sold to customers ===
−
<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;
+
  
−
*Import of Association (Line Item)
+
'''What''' – ICI Salesforce experience users can now view the list of all the products and services sold to the customer under “Agreement Lines” subtab.
−
*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.
+
'''Advantages – '''With visibility to Agreement lines through this feature, Sales Executives will be able to identify Cross-sell, up-sell opportunities to pursue relevant sales, and request amendment to appropriate contract.
  
−
&nbsp;
+
'''How – '''A new subtab “Agreement Lines” is added for account object displaying all the active product and services sold to the customer. The products displayed under agreement line subtab are fetched via ICI saved searches.
 +
<div class="image-green-border">[[File:8.2.RN 3.png|720px|8.2.RN 3.png]]</div>
 +
'''Note: '''The “Agreement Lines” displays only active products and services from executed contracts.
  
−
<span style="color:#008000;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>
+
'''Value''': User Experience<br/> '''For''': Sales Managers | Sales Executive<br/> '''Feature ID''': 1192973
  
−
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.
+
== Enhancements – Mobile App Experience ==
  
−
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;
+
[[File:8.2 RN 32.PNG|720px|8.2 RN 32.PNG]]
  
−
Users can now:&nbsp;
+
== Administration & Configuration ==
  
−
*Capture multiple valid internal or external email addresses while working on agreements/ requests.
+
=== Enhanced ICI startup validation architecture ===
−
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients.
+
  
−
&nbsp;
+
'''What''' – A new validation framework for configuration keys and related metadata to resolve incorrect or missing keys and ensure seamless startup of ICI instances.
  
−
<span style="color:#008000;">'''583186 – Ability to add amendment on expired agreement'''</span>
+
'''Advantages – '''Timely validation of configuration keys and guardrails to prevent unnecessary startup blockers.
  
−
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.
+
'''How – '''At startup, the validation framework checks for configuration keys that are inconsistent or incorrect and restores those to default values thereby preempting any startup issues. Technical admins can view and investigate the validation logs on the self-service portal.
  
−
With this release, 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;
+
'''Value''': Reliability, Supportability<br/> '''For''': Administrators<br/> '''Feature ID''': 1373024
  
−
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.
+
=== Configure E-Signature Integrations within ICI ===
−
<div class="image-green-border">[[File:7.14 release note 8.png|720px|7.14 release note 8.png]]<br/>  </div>
+
−
<span style="color:#008000;">'''593928 – Ability to configure sender email ID for automated emails'''</span>
+
  
−
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.
+
'''What''' – E- signature configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
  
−
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;
+
'''Advantages '''– This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team.&nbsp;
  
−
Administrators can now:
+
'''How''' – Technical administrators can configure E- sign providers (DocuSign and AdobeSign) from the E-sign configuration page.
 +
<div class="image-green-border">[[File:8.2 RN 04.png|720px|8.2 RN 04.png]]</div>
 +
'''Value''': Self-service<br/> '''For''': Technical admins<br/> '''Feature ID''': 1180879
  
−
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement.
+
=== Integrated Config keys validation framework ===
−
*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.
+
'''What''' – ICI now has the capability to check incorrect values, difference in data types, and inconsistency in configuration data. The utility can be run prior to starting an application and the report and errors reported can be used to help find a solution.
  
−
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.
+
'''Advantages – '''Helps prevent issues that occur during application startup.
  
−
With this release:
+
'''How – '''At the start of an ICI instance, the disparity in the configuration keys is identified, and the incorrect keys are set to the default value. All such changes are recorded in the self-service portal so that the technical admins can investigate the errors.
  
−
*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).
+
'''Value''': Self-service &nbsp;<br/> '''For''': Administrators<br/> '''Feature ID''': 1373030
−
*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.
+
=== Configure SSO integrations within ICI ===
−
<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;
+
'''What''' – SSO configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
  
−
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;
+
'''Advantages '''– This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team.&nbsp;
  
−
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;
+
'''How''' – Technical administrators can configure SSO integrations (SAML, WS-Fed and O-Auth) from the SSO configuration page.
 +
<div class="image-green-border">[[File:8.2 RN 05.png|720px|8.2 RN 05.png]]</div>  
 +
'''Value''': Self-service &nbsp;<br/> '''For''': Technical admins<br/> '''Feature ID''': 1180896
  
−
<span style="color:#008000;">'''545126 – Availability of business status value in ICI event messages'''</span>
+
=== Customer-specific SAML/OAuth SSO Configurations ===
  
−
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.
+
'''What – '''In a multitenant instance of Icertis Contract Intelligence, SSO configurations are now moved from a single configuration file to separate configuration files for each tenant. These configurations can now also be modified from within Icertis Contract Intelligence.
  
−
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.
+
'''Advantages''' –
  
−
== Mobile App Updates ==
+
*Site reliability and stability - SSO issues affecting one tenant do not impact other tenants.
 +
*Self-service - Technical admin users can configure SSO without intervention from Icertis teams.
  
−
'''<span style="color:#008000;">660965 – Refresh agreement list on approval</span>'''
+
'''How – '''Users with the right permissions can make SSO configuration changes from the Tenant.config file. The changes can also be made from within ICI by Technical Admin users.
  
−
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;
+
'''Value: '''Self-service, Reliability, Supportability<br/> '''For:''' Technical Admins<br/> '''Feature ID: '''1317384
  
−
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.
+
=== Error-handling framework ===
−
<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.
+
'''What '''– A centralized and industry-standard error handling framework for faster troubleshooting, analysis and resolution of issues. The list of error codes and related data is cataloged & documented, which will act as a standard reference for all error codes in the ICI platform.
  
−
Enhancements include:
+
The framework provides the following features:
  
−
*Addition of Masterdata APIs&nbsp;
+
Detailed and structured data to determine severity, origin, module, area & source of the error.
−
**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.  
+
No unhandled exceptions emanating from the system.
−
</div>
+
−
== Enhancements to ICI Add-ins&nbsp; ==
+
  
−
<span style="color:#008000;">'''714872 – Improved document usability'''</span>
+
Detailed logging is done in a central repository like Kibana.
  
−
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;
+
For ICI Instances where AppInsights is available, a correlation id helps to track calls and correlate the complete chain of events that led to the error.
  
−
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.
+
'''Why '''– Eliminates time required to locate and understand the issue and reduces the overall time needed to fix issues.
  
−
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.
+
'''How '''– ExceptionHandler attribute is introduced, which will have following Origin, Area, Module, Sub Module in the form of code.
−
<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:
+
  
−
*All the content controls are put together in a single paragraph on any line with valid content.
+
For example: 50000030021360X8013153 (shown on User Interface)
−
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.
+
−
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules.
+
−
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&nbsp;
+
−
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document.
+
−
<div class="image-green-border">[[File:7.14 release note 5.png|720px|7.14 release note 5.png]]</div> <div class="image-green-border">&nbsp;</div>
+
−
'''Note''':&nbsp;
+
  
−
*Only file-based clauses are supported.
+
Breakdown of the code is as follows:
−
*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;
+
5 – Severity
  
−
<span style="color:#008000;">'''660390 – Ability to show more clauses per group'''</span>
+
00 – Origin (First parameter of Exception Handling attribute)
  
−
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.
+
00 – Source (mostly internal)
  
−
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.
+
03 – Area (Second parameter of Exception Handling attribute)
−
<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>
+
  
−
In ICI, users capture additional details for clauses and templates in the extended attributes.
+
002 – Module (Third parameter of Exception Handling attribute)
  
−
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.
+
136 – SubModule (Fourth parameter of Exception Handling attribute)
−
<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.
+
  
−
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.
+
0X8013153 – Standard C# HResult which can be googled to see the exception type
−
<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 ==
+
Class decorators for Exception Handling
  
−
<span style="color:#008000;">'''662334/716399 – Introducing AI powered Playbook in WordAI&nbsp;'''</span>
+
['''ExceptionHandler''' (exceptionOrigin: ExceptionOrigin.Core, exceptionArea: ExceptionArea.CLM, module: ExceptionAreaModule.CLM_AdminTask, submodule: ExceptionAreaSubModule.CLM_AdminTask_Root)]
  
−
With this release, ICI is introducing a legal playbook in the WordAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.
+
When an error occurs, the error code is displayed on the error message, see the screenshot below.&nbsp;&nbsp;
 +
<div class="image-green-border">[[File:8.2 RN 33.PNG|400px|8.2 RN 33.PNG]]</div>
 +
'''Value: '''Supportability<br/> '''For: '''Partner Developers | Any Application User | Troubleshooters<br/> '''Feature ID''': 1373034
  
−
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.
+
=== Administration & Configuration Enhancements ===
  
−
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.
+
[[File:8.2 RN 34.PNG|720px|8.2 RN 34.PNG]]
  
−
The exceptions are identified by the WordAI 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.
+
== Reporting Analysis ==
−
<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.
+
=== Dashboard and Power BI reports for Supplier Evaluation ===
−
*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 task 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>
+
'''What – '''An interactive Supplier Evaluation dashboard with the following features is now available out-of-the-box:
  
−
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.
+
Interactive graphs for status of evaluation cases, evaluation distribution by performance, and ageing in review or approval states.
  
−
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;
+
Enlists the top and poor performing suppliers based on a host of filters like evaluation type, period of evaluation, supplier name and more.
  
−
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.
+
Captures evaluations that are awaiting supplier inputs for missing documents.
−
<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;
+
  
−
'''<span style="color:#008000;">663666 – Enhancing inbuilt discovery model to include additional attributes&nbsp;</span>'''
+
360-degree supplier performance score card about different evaluations, KPI and performance trend over a time period.
  
−
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;
+
Capture supplier documents/ certificates that are expired or expiring within 5 days.
  
−
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;
+
'''Advantages –'''
  
−
<span style="color:#008000;">'''575466 – Support for additional languages in AI apps&nbsp;'''</span>
+
Information is represented visually and is easier to consume and track.
  
−
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&nbsp;
+
Assist the procurement team in setting up the right expectations and manage supplier relationships.
  
−
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.
+
Insights into poorly performing suppliers can help in planning proactive performance improvement.
  
−
With this release:
+
'''How – '''The dashboard and reports can be accessed from the Supplier Management -> Dashboard.
  
−
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration.
+
'''Pre-requisite''': HTTP Artifact binding should be supported by the respective IDP server to enable this feature.
−
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document.  
+
<div class="image-green-border">[[File:8.2 RN 15.png|720px|8.2 RN 15.png]]</div>
−
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI.  
+
'''Value: '''Analytics&nbsp;| User experience<br/> '''For: '''Vendor Management Office | Procurement Department | Business Analysts| Legal Team<br/> '''Feature ID: '''1235347
−
*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 ==
+
=== New filters added to Agreement and Amendment based SSRS reports ===
  
−
<span style="color:#008000;">'''514594 – Capability of time zone in reports'''</span>
+
'''What – '''The following filters are now available on UI for DRF Agreements Pending Approval and DRF Expired Agreements reports:
  
−
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.
+
Contract Type
−
<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>
+
  
−
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;
+
Org Unit
  
−
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;
+
Agreement Owner
  
−
This default report is accessible from the Admin category of reports and its access is based on Security Groups.
+
Agreement Status
−
<div class="image-green-border">[[File:7.14 release note 20.png|720px|7.14 release note 20.png]]<br/> &nbsp;</div>
+
−
== Integrations ==
+
  
−
<span style="color:#008000;">'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''</span>
+
Created Date (Created Date From, Created Date To)
  
−
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;
+
Time Zone
  
−
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;
+
'''Note''': These reports are default and cannot be customized as of now.
  
−
Salesforce users can now:&nbsp;
+
'''Advantages – '''One or more filters can be applied to help view the data in contextual slices.
  
−
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&nbsp;
+
'''How – '''The filters can be applied from the respective reports page, which can be accessed from the Default Reports tab.
−
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&nbsp;
+
<div class="image-green-border">[[File:8.2 RN 16.png|720px|8.2 RN 16.png]]</div>  
−
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab.  
+
'''Value: '''Self-service<br/> '''For: '''Managers | Legal Team | Decision Makers<br/> '''Feature ID: '''1346718
−
<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;
+
=== Self-Service Configuration page for creating custom SSRS reports and dynamic views ===
  
−
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;
+
'''What – '''Technical users can create or modify dynamic views and create or modify SSRS reports from the self-service configurations page. Some knowledge of technical column names and JSON is necessary to make the modifications.
  
−
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.
+
'''Advantages – '''Provides a simpler path to customize reports and can be done by technical users without intervention from Icertis teams.
  
−
&nbsp;
+
'''How – '''Users with technical role ‘Report admin’ can access the Report Configurations tab on the System Configuration – Self-Service page and create and modify the dynamic views and SSRS DRF reports.
 +
<div class="image-green-border">[[File:8.2 RN 17.png|720px|8.2 RN 17.png]]</div>
 +
'''Value: '''Self-service<br/> '''For: '''Configuration Admin | External implementation partners<br/> '''Feature ID: '''1346720
  
−
<span style="color:#008000;">'''635822 – Support for pre- and post-processing in Generic Integration Framework'''</span>
+
== APIs ==
  
−
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&nbsp;
 
  
−
With this release, 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:
+
=== API Management Service ===
  
−
*Pre-process inbound data through file-based integrations.  
+
'''What – '''API management is a key infrastructure of API offering working as a façade and controlling layer for use of ICI APIs. It consists of—a gateway which controls the flow of APIs from the integrating application to ICI API server, a management portal to configure the usage policies and an information portal called API Hub.
−
*Pre-process inbound and outbound data through ASB-based integrations.  
+
  
−
ICI administrators will now be able to:&nbsp;
+
With the API Management, the following is possible for customers:
  
−
*Enable or disable the hook as part of file-based and ASB integration.
+
*Enforcing usage quota limit
−
*Pass parameters to the hook for executing a custom logic.
+
*Rate limiting (throughput throttling) of API calls (by default set to 5 API calls per min)
−
*Enable or disable the hook at file or record level.
+
*Monitoring and getting reports on usage of APIs
−
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook.
+
−
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record. 
+
−
*Execute any custom logic in the system for a file or record when a hook is configured.
+
−
*Complete GIF process even when custom logic encounters any error while processing a record or file.
+
  
−
&nbsp;
+
'''How – '''All customers using Icertis APIs can use the APIM gateway URLs as API URLs. For new customers, the APIs are automatically routed through APIM. For the existing customers that are already using APIs, they must make a configuration change to connect to APIM. The Icertis team will provide the exact API gateway URLs.
  
−
<span style="color:#008000;">'''635823&nbsp;– Support for defining folder structure in Generic Integration Framework'''</span>
+
'''Note''': The API Hub capability where users can get the information about APIs, try out the endpoints and get API usage reports is described as a separate feature below in the release notes.
  
−
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.
+
'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
  
−
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.
+
=== Icertis API Hub–A New Developer Experience for Working with APIs ===
  
−
With this release, users have:&nbsp;
+
'''What – '''The new Icertis API Developer Experience is simple, secure, and immersive for the developers.
  
−
*Support for single or multiple folders in the folder structure.
+
As an API developer, the new Icertis API Developer Experience allows you to discover and interact with the ICI APIs. Developers can find recommendations for making API requests, inputs for each endpoint, and authentication methods. Based on the subscription key, the developers can make API calls for the API products.
−
*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.  
+
  
−
&nbsp;
+
We have divided the API endpoints into distinct categories to facilitate access and search. Reports include data points like the number of API calls, response time, APIs used, etc.
  
−
== Partner Enablement ==
+
'''Advantages''' –
  
−
<span style="color:#008000;">'''703386 – Icertis Software Development Kit for Partner Enablement'''</span>
+
*Smoother developer on-boarding and learning experience
 +
*Real-time usage reports provide transparency
  
−
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;
+
'''How – '''You must have the APIM Dev Portal User role assigned to access the new APIM Developer experience. Contact your system administrator for access.
  
−
As part of our continuous efforts to support our partners, we have created the following documents in this release:
+
Additional notes:
  
−
*'''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.
+
*You can use OAuth or token-based authentication method
 +
*An additional fee is required to use the access-based certificate authentication method
  
−
*'''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.
+
'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
  
−
*'''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;'''
+
=== Framework for the composite API ===
  
−
*'''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.  
+
'''What''' – This release introduces “Single Response – Composite APIs” to eliminate creation of wrappers over ICI Platform’s APIs while using them.
  
 +
The Composite API Framework supports the following features:
 +
 +
API endpoint for supporting composite structure
 +
 +
Request and Response representation
 +
 +
Validation framework for composition
 +
 +
Orchestration logic for composite requests
 +
 +
Referencing field's structure and usage
 +
 +
'''Advantages''' – The framework helps simplify the implementation and makes the integration more efficient. How - API developer can work on ICI entities via single composite API request to trigger series of APIs calls in a single API call and get multiple request results in a single response body.
 +
 +
'''Value''': User Experience | Ease of Use | Improved Efficiency<br/> '''For''': API Developers | Administrators<br/> '''Feature ID''': 1182667
 +
 +
=== API Endpoint Changes ===
 +
 +
[[File:8.2 RN 06.PNG|720px|8.2 RN 06.PNG]]
 +
 +
[[File:8.2 RN 07.PNG|720px|8.2 RN 07.PNG]]
 +
 +
[[File:8.2 RN 08.PNG|720px|8.2 RN 08.PNG]]
 +
 +
[[File:8.2 RN 09.PNG|720px|8.2 RN 09.PNG]]
 +
 +
[[File:8.2 RN 10.PNG|720px|8.2 RN 10.PNG]]
 +
 +
[[File:8.2 RN 11.PNG|720px|8.2 RN 11.PNG]]
 +
 +
[[File:8.2 RN 12.PNG|720px|8.2 RN 12.PNG]]
 +
 +
== AI Applications ==
 +
 +
=== Beta Feature – Refer existing obligations when reviewing AI-discovered obligations ===
 +
 +
'''What''' – AI-discovered obligations are automatically categorized in a category and sub-category when presented for review and confirmation. When reviewing discovered obligations users can now refer to existing obligations in approved state belonging to the same category, sub-category and related agreements. Changing the category and sub-category, displays the relevant set of approved obligations.
 +
 +
'''Advantages''' –
 +
 +
Referring '''Library Obligations''' can help you get a standard position/scope/language to be used while setting up a newly discovered obligation
 +
 +
Referring from '''Related Agreements''' helps you understand what obligations from parent (peer) contracts are to be set at the child level specially in case of back-to-back contracting (e.g., checking customer contracts and passing on the related obligations in supplier contracts)
 +
 +
'''How – '''Users can review AI-discovered obligations from the Review Obligation drawer, which can be accessed from the “Review Discovered Obligation” page.
 +
 +
Review Obligation drawer displaying Approved Obligations in Library Obligation
 +
<div class="image-green-border">[[File:8.2 RN 35.PNG|720px|8.2 RN 35.PNG]]</div>
 +
'''Note:''' Library Obligations are to be added manually. Please refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.2/index.php?title=ICI_Obligation_Management#Obligation_Library OM wiki] on how to setup an Obligation Library.
 +
 +
Review Obligation drawer displaying Approved Obligations in Related Agreements
 +
<div class="image-green-border">[[File:8.2 RN 36.PNG|720px|8.2 RN 36.PNG]]</div>
 +
'''Note: '''Time needed to display Obligations from related agreements may vary depending upon the number of Linked agreements and count of Obligations within them.
 +
 +
'''Value''': Efficiency | Time Saving<br/> '''For''': Legal Team | Contract Managers<br/> '''Feature ID''': 1366783
 +
 +
== Sourcing ==
 +
 +
The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application.
 +
 +
=== Converting RFI to RFP or RFQ ===
 +
 +
'''What''' – ICI Sourcing application now allows creating an RFP or RFQ from an RFI from which the suppliers are shortlisted. Users can create multiple RFP’s or RFQ’s from a single RFI.&nbsp;
 +
 +
'''Advantage''' – Saves time when creating an RFP or RFQ by allowing shortlisted suppliers to be selected from a previously completed RFI. &nbsp;
 +
 +
'''How''' – Users can use the “Create from RFI” button from the Sourcing index page or from the Create RFP/RFQ option on the RFI that is in “Bidding Closed” state.
 +
 +
'''Value''': User Experience<br/> '''Feature ID''': 1328960&nbsp;&nbsp;
 +
 +
=== Shortlist Suppliers in RFx ===
 +
 +
'''What''' – An enhancement has been made to the existing '''Shortlist''' feature that allows buyers to select and shortlist specific suppliers for the next procurement stage. For example, from RFI to RFP or RFQ or from one round to another in the same RFX. The supplier Shortlist can be modified in certain RFx statuses.
 +
 +
'''Advantage''' – Helps accessing preferred suppliers quickly or remove them from the “Suppliers” page thereby saving time.
 +
 +
'''How''' – A “Shortlist Supplier” option is added on the “Suppliers” page. &nbsp;
 +
<div class="image-green-border">[[File:8.2.RN 4.png|500px|8.2.RN 4.png]]</div>
 +
'''Value''': User Experience<br/> '''For''': Buyer and Administrator users<br/> '''Feature ID''': 1341682&nbsp;&nbsp;
 +
 +
=== Sourcing Enhancements ===
 +
 +
[[File:8.2.RN T4.PNG|720px|8.2.RN T4.PNG]]
 +
 +
== Obligation Management ==
 +
 +
The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application
 +
 +
=== Auto-create Obligations from Associations data ===
 +
 +
'''What''' – ICI Platform now facilitates improved Obligation intake from source Association records. An Obligation is automatically created from any defined associations such as Deliverables, SLA, Risk Assessments. For example, if a SOW has ‘Deliverable’ as an association, then the user can directly convert that deliverable into an Obligation.
 +
 +
'''Advantages''' – Streamlines and simplifies creation of Delivery Dates, Milestones, SLAs, Risk Assessments, and other obligations from associated records, improving process efficiency. Auto-creation of Obligations enhances tracking compliance centrally using Obligation Management.
 +
 +
'''How – '''You can use the “Create Obligation” menu option from the Associations object list view or details page.
 +
<div class="image-green-border">[[File:8.2.RN 5.png|720px|8.2.RN 5.png]]</div>
 +
'''Value''': User Experience | Contract Building | Managing Obligations | Process Efficiency<br/> '''For''': Risk Managers | Contract Administrators<br/> '''Feature ID''': 649740
 +
 +
=== Use “Date” & “DateTime” Attributes from Holding Agreement for Obligation Scheduling ===
 +
 +
'''What – '''Due'''dates and end dates for obligations can now be selected from any of the date attributes of the agreement.'''
 +
 +
'''Advantages'''
 +
 +
Eliminates the need for an Obligation creator to know specific dates.
 +
 +
Consistency in Obligation dates used across various members / obligation creators
 +
 +
Reduces the extra effort required in referring to Date Attributes of holding agreement entity (for example, Effective Date / Expiry Date) and use them in Obligation creation.
 +
 +
'''How – '''Two new attributes have been added to the Obligation Contract Type – “Select Due Date From” and “Select End Date From”. You can select a specific date value from the given options. The date value selected will be as per the actual date defined in the Agreement. For example, if you select “Expiry Date” value, an Obligation will be created with an expiry date that is same as the expiry date for the Agreement.
 +
<div class="image-green-border">[[File:8.2.RN 6.png|600px|8.2.RN 6.png]]</div>
 
&nbsp;
 
&nbsp;
  
−
== Technical Requirements for Release 7.14 ==
+
'''Value''': User Experience<br/> '''For''': Contract Operations<br/> '''Feature ID''': 913820
  
−
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.
+
=== Obligation Management Enhancements ===
  
−
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]
+
[[File:8.2.RN T5.PNG|720px|8.2.RN T5.PNG]]
  
−
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]
+
== Supplier Relationship Management ==
  
−
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]
+
ICI Supplier Relationship Management application is certified to work with the 8.2 release
  
−
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]
+
=== Supplier Profile and Supplier Master records synchronization ===
  
−
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]
+
'''What''' – Supplier product and service categories are now automatically synced in the following events:
 +
 
 +
On supplier qualification, the product/service category updates get copied to the Supplier Master category field.
 +
 
 +
Buyers update the Supplier Master the information is synced with the Supplier Profile.
 +
 
 +
Buyers update the Supplier Profile the information is synced with Supplier Master.
 +
 
 +
'''Advantage''' – Supplier records are consistent and can be consumed across all Icertis applications.
 +
 
 +
'''How''' – If a supplier record in the database is modified depending on the conditions defined, the other relevant records also get updated automatically.&nbsp;
 +
 
 +
'''Value''': Efficiency<br/> '''For''': Buyer users<br/> '''Feature ID''': 1420117
 +
 
 +
=== Supplier Relationship Management Enhancements ===
 +
 
 +
[[File:8.2.RN T7.PNG|720px|8.2.RN T7.PNG]]
  
 
&nbsp;
 
&nbsp;
 +
 +
== Rebates Enhancements ==
 +
 +
Rebates App in ICI Platform is enhanced to improve the usability and thereby improve the overall user experience, scalability and robust calculations. The Rebates App extends support for Big Data, AI, and Dynamic JSON. The enhancements in Rebates App can be summarized as below:
 +
 +
'''Refined seeded data model:'''
 +
 +
*Minimal configuration and data reusability to make Rebates app more scalable.
 +
*Standardized naming conventions to avoid any conflicts with other apps.
 +
*Normalized data has improved Calculation Engine’s efficiency by 50%.
 +
*Dynamic JSON for Rebate program data eliminates the need to have distinct rebates and payout calculation for every business unit in an organization. The enhanced calculation engine extracts JSON data from the Agreement and its associated documents and maps it with the newly configured attributes.
 +
*Background tasks optimized to support big data such as calculation engine processing large invoice and agreement datasets. As an example, for performance testing, it took 35 seconds (approximately) to process 170,000 &nbsp;records (approximately) as compared to 1 minute (approximately) for 5000 records (approximately) in the earlier version.
 +
*Rebate program attributes are a part of associated document instead of an agreement, which enables handling multiple rebate programs within a contract. This also reduces the number of attributes in an agreement, that improves the performance of agreement creation.
 +
*Standardized attributes management by allowing 16-digit numbers with 6 decimal places.
 +
*Generic Product, Location, and Customer hierarchies allow customizing configuration and mapping it to the calculation engine.
 +
*Previously, configuration supported only up to 10 customer details as these details were part of the Agreement itself. However, now these details are migrated as Associated documents to support unlimited customer details.
 +
 +
'''Power BI Reporting:'''
 +
 +
*Intuitive dashboard with advanced analytics on the rebate agreement distribution and accruals accumulation.
 +
*Out-of-the-box reports added in Power BI, which were earlier focused on Accruals, are now aligned with the overall performance of Rebates.
 +
*Improved visibility for Rebates payout calendar with the next payout dates.
 +
 +
=== Risk Management Enhancements ===
 +
 +
[[File:8.2.RN T6.PNG|720px|8.2.RN T6.PNG]]
 +
 +
== Technology Updates ==
 +
 +
=== HTTP Artifact Binding Support for SSO Integration ===
 +
 +
'''What – '''In addition to HTTP POST and HTTP Redirect, ICI now supports HTTP Artifact binding for SSO (Single Sign-On) integration along with other IdPs like ADFS.
 +
 +
'''Advantages – '''With improved security, exchanging sensitive data across Id Provider (IdP) and Service Provider (SP) becomes more authenticated and trustworthy. This prevents intervention of any malicious party.
 +
 +
'''How – '''Administrator or Implementation Partner can choose between HTTP POST, HTTP Redirect and HTTP Artifact binding for SSO (Single Sign-On) integration, on the IdP server side.
 +
 +
'''Value: '''Secure Authentication Process<br/> '''For: '''All ICI Users<br/> '''Feature ID: '''1342076
 +
 +
=== Microsoft retiring basic authentication for SMTP ===
 +
 +
'''What '''– Microsoft is retiring basic authentication for SMTP, and it would be necessary for customers using basic authentication to move to an alternate service. ICI now supports modern authentication with support for Microsoft Graph API.
 +
 +
'''Why '''– Provide support for modern authentication methods & ensure service continuity even after Microsoft retires basic authentication later this year (Oct 1, 2022).
 +
 +
'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
 +
 +
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
 +
 +
=== Microsoft retiring Outlook REST API ===
 +
 +
'''What''': The Icertis Outlook Add-In that currently uses the Outlook REST API will now use Microsoft Graph API.
 +
 +
Configurations are required for Outlook Add-In at the time of implementing or upgrading Icertis Contract Intelligence to work with Microsoft Graph API.
 +
 +
'''Why''': Microsoft has announced that Outlook REST API will be deprecated in the month of November, 2022.
 +
 +
'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
 +
 +
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
 +
 +
=== Support for StartTLS protocol ===
 +
 +
'''What''' – Adding support for the StartTLS protocol through NuGet MailKit for authentication and notification. StartTLS protocol command is used to inform the email server that the email client wants to upgrade from an insecure connection to a secure one using TLS or SSL.<br/> <br/> '''Why''' – Customers have the option to use the StartTLS protocol, which supports enhanced security.
 +
 +
'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
 +
 +
'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
 +
 +
=== Bootstrap upgrade from version 4.5.2 to 5.1.3 ===
 +
 +
'''What''' – The Bootstrap library has been upgraded from version 4.5.2 to 5.1.3. The support for Bootstrap library version 4.5.2 ends by Q3 2022. 4.5.2 is compatible with the new version.
 +
 +
'''Why''' – To address security vulnerabilities.
 +
 +
'''TFS ID''': 1459132<br/> &nbsp;
 +
 +
=== Web Application Firewall & Azure Front Door ===
 +
 +
'''What''' –
 +
 +
Implementing Azure Front Door (AFD) with the following settings:
 +
 +
Web Application Firewall (WAF) in diagnostic mode
 +
 +
Prevention Rule in AFD to restrict access from embargo countries.
 +
 +
'''Advantages – '''WAF & AFD help prevent against common exploits and vulnerabilities.
 +
 +
'''How – '''It can be configured, deployed, and managed via the Azure Portal, PowerShell, and CLI (command-line interface).
 +
 +
'''Value''': Security<br/> '''For''': Administrators<br/> '''Feature ID''': 951438
  
 
&nbsp;
 
&nbsp;
  
−
'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|
+
= Technical Requirements =
 +
 
 +
The Icertis Contract Intelligence (ICI) application can be accessed from any device with an Internet connection and a supported browser. All features may not be available in all environments.
 +
 
 +
The software and hardware requirements for the client system as well as the mobile application are listed in the table below:
 +
 
 +
[[File:8.2.RN T8.PNG|720px|8.2.RN T8.PNG]]
 +
 
 +
[[File:8.2.RN T9.PNG|720px|8.2.RN T9.PNG]]
 +
 
 +
[[File:8.2.RN T10.PNG|720px|8.2.RN T10.PNG]]<br/> [[File:8.2.RN T11.PNG|720px|8.2.RN T11.PNG]]
 +
 
 +
[[File:8.2.RN T12.PNG|720px|8.2.RN T12.PNG]][[File:8.2.RN T13.PNG|720px|8.2.RN T13.PNG]]
 +
 
 +
[[File:8.2.RN T14.PNG|720px|8.2.RN T14.PNG]]
 +
 
 +
[[File:8.2.RN T15.PNG|720px|8.2.RN T15.PNG]]<br/> [[File:8.2.RN T16.PNG|720px|8.2.RN T16.PNG]]<br/> [[File:8.2.RN T17.PNG|720px|8.2.RN T17.PNG]]
 +
 
 +
[[File:8.2.RN T18.PNG|720px|8.2.RN T18.PNG]]
 +
 
 +
= Accessibility Conformance =
 +
 
 +
We ran accessibility conformance tests on the Icertis Contract Intelligence platform and Business Apps for Web Content Accessibility Guidelines 2.1 for Level A and Level AA standards. We did not evaluate for Level AAA standards.
 +
 
 +
While most of the product functionality has at least one method that meets the criterion without any known defects, some functionality of the product may not meet the conformance criteria. The full report is published in the following documents and can be made available on request:
 +
 
 +
ICI Platform Accessibility Conformance Report
 +
 
 +
ICI AI/ML Accessibility Conformance Report
 +
 
 +
ICI Reporting Accessibility Conformance Report
 +
 
 +
ICI Obligation Management Accessibility Conformance Report
 +
 
 +
ICI Sourcing Accessibility Conformance Report
 +
 
 +
ICI Proposal Management Accessibility Conformance Report
 +
 
 +
ICI SRM Accessibility Conformance Report
 +
 
 +
ICI Risk Management Accessibility Conformance Report
 +
 
 +
= Known Issues =
 +
 
 +
This section includes some issues that we are aware of and plan to resolve at the earliest:
 +
 
 +
[[File:8.2.RN T19.PNG|720px|8.2.RN T19.PNG]]
 +
 
 +
&nbsp;'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Associations|Association Management]] | [[Compliances|Compliance Management]] | [[Templates|Template Management]] | [[Clauses|Clause Management]] | [[Configure|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]]&nbsp;

Latest revision as of 13:09, 29 September 2022

Contents

ICI Release Notes - Release 8.2

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

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

New Features and Enhancements

Contract Authoring & Management 

Amend contracts preserving previously negotiated terms

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

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

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

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

Send multiple agreements packaged in a single envelope for electronic signature

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

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

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

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

Quickly create and edit contract types in bulk using excel workbook

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

Advantages

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

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

How

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

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

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

Icertis Experiences

Rules functionality added to Icertis Experience for Word

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

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

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

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

8.2 RN 01.png  8.2 RN 02.png

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

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

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

Advantages – Avoid uploading duplicate email conversations in ICI.

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

8.2 RN 03.png

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

Revamping ICI Salesforce User Experience

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

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

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

Some new features include:

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

Ability to preview the document from amendments sub tab.

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

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

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

New ICI Salesforce Agreement Details screen

8.2.RN 1.png

New Add Note Dialog box

8.2.RN 2.png

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

Salesforce – Visibility of products and services sold to customers

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

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

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

8.2.RN 3.png

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

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

Enhancements – Mobile App Experience

8.2 RN 32.PNG

Administration & Configuration

Enhanced ICI startup validation architecture

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

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

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

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

Configure E-Signature Integrations within ICI

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

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

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

8.2 RN 04.png

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

Integrated Config keys validation framework

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

Advantages – Helps prevent issues that occur during application startup.

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

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

Configure SSO integrations within ICI

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

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

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

8.2 RN 05.png

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

Customer-specific SAML/OAuth SSO Configurations

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

Advantages –

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

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

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

Error-handling framework

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

The framework provides the following features:

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

No unhandled exceptions emanating from the system.

Detailed logging is done in a central repository like Kibana.

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

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

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

For example: 50000030021360X8013153 (shown on User Interface)

Breakdown of the code is as follows:

5 – Severity

00 – Origin (First parameter of Exception Handling attribute)

00 – Source (mostly internal)

03 – Area (Second parameter of Exception Handling attribute)

002 – Module (Third parameter of Exception Handling attribute)

136 – SubModule (Fourth parameter of Exception Handling attribute)

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

Class decorators for Exception Handling

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

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

8.2 RN 33.PNG

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

Administration & Configuration Enhancements

8.2 RN 34.PNG

Reporting Analysis

Dashboard and Power BI reports for Supplier Evaluation

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

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

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

Captures evaluations that are awaiting supplier inputs for missing documents.

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

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

Advantages –

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

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

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

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

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

8.2 RN 15.png

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

New filters added to Agreement and Amendment based SSRS reports

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

Contract Type

Org Unit

Agreement Owner

Agreement Status

Created Date (Created Date From, Created Date To)

Time Zone

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

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

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

8.2 RN 16.png

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

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

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

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

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

8.2 RN 17.png

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

APIs

API Management Service

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

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

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

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

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

For: API Developers | Administrators
Feature ID: 1182735

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

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

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

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

Advantages –

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

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

Additional notes:

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

For: API Developers | Administrators
Feature ID: 1182735

Framework for the composite API

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

The Composite API Framework supports the following features:

API endpoint for supporting composite structure

Request and Response representation

Validation framework for composition

Orchestration logic for composite requests

Referencing field's structure and usage

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

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

API Endpoint Changes

8.2 RN 06.PNG

8.2 RN 07.PNG

8.2 RN 08.PNG

8.2 RN 09.PNG

8.2 RN 10.PNG

8.2 RN 11.PNG

8.2 RN 12.PNG

AI Applications

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

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

Advantages –

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

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

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

Review Obligation drawer displaying Approved Obligations in Library Obligation

8.2 RN 35.PNG

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

Review Obligation drawer displaying Approved Obligations in Related Agreements

8.2 RN 36.PNG

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

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

Sourcing

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

Converting RFI to RFP or RFQ

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

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

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

Value: User Experience
Feature ID: 1328960  

Shortlist Suppliers in RFx

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

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

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

8.2.RN 4.png

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

Sourcing Enhancements

8.2.RN T4.PNG

Obligation Management

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

Auto-create Obligations from Associations data

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

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

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

8.2.RN 5.png

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

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

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

Advantages

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

Consistency in Obligation dates used across various members / obligation creators

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

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

8.2.RN 6.png

 

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

Obligation Management Enhancements

8.2.RN T5.PNG

Supplier Relationship Management

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

Supplier Profile and Supplier Master records synchronization

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

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

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

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

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

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

Value: Efficiency
For: Buyer users
Feature ID: 1420117

Supplier Relationship Management Enhancements

8.2.RN T7.PNG

 

Rebates Enhancements

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

Refined seeded data model:

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

Power BI Reporting:

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

Risk Management Enhancements

8.2.RN T6.PNG

Technology Updates

HTTP Artifact Binding Support for SSO Integration

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

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

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

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

Microsoft retiring basic authentication for SMTP

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

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

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

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

Microsoft retiring Outlook REST API

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

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

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

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

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

Support for StartTLS protocol

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

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

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

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

Bootstrap upgrade from version 4.5.2 to 5.1.3

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

Why – To address security vulnerabilities.

TFS ID: 1459132
 

Web Application Firewall & Azure Front Door

What –

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

Web Application Firewall (WAF) in diagnostic mode

Prevention Rule in AFD to restrict access from embargo countries.

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

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

Value: Security
For: Administrators
Feature ID: 951438

 

Technical Requirements

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

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

8.2.RN T8.PNG

8.2.RN T9.PNG

8.2.RN T10.PNG
8.2.RN T11.PNG

8.2.RN T12.PNG8.2.RN T13.PNG

8.2.RN T14.PNG

8.2.RN T15.PNG
8.2.RN T16.PNG
8.2.RN T17.PNG

8.2.RN T18.PNG

Accessibility Conformance

We ran accessibility conformance tests on the Icertis Contract Intelligence platform and Business Apps for Web Content Accessibility Guidelines 2.1 for Level A and Level AA standards. We did not evaluate for Level AAA standards.

While most of the product functionality has at least one method that meets the criterion without any known defects, some functionality of the product may not meet the conformance criteria. The full report is published in the following documents and can be made available on request:

ICI Platform Accessibility Conformance Report

ICI AI/ML Accessibility Conformance Report

ICI Reporting Accessibility Conformance Report

ICI Obligation Management Accessibility Conformance Report

ICI Sourcing Accessibility Conformance Report

ICI Proposal Management Accessibility Conformance Report

ICI SRM Accessibility Conformance Report

ICI Risk Management Accessibility Conformance Report

Known Issues

This section includes some issues that we are aware of and plan to resolve at the earliest:

8.2.RN T19.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 

Retrieved from "https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&oldid=25258"