ICI Release Notes - Release 7.14[edit]


= ICI&nbsp;Release Notes - Release 7.14 =

== Overview of Release 7.14 ==

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

The key enhancements of this release include:

*<span style="color:#008000;">'''Enhancements to the ICI Application'''</span> 
**'''''User Experience''''' 
***Introducing a horizontal chevron which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron, namely Generate, Approve, Execute and Manage, prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. 
***Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement. 
***Facilitating one-click navigation from the ICI record to any related entities (multi-hierarchy level). For example, from RFx to Bid Response which would otherwise require multiple clicks. 
***Providing administrators the ability to configure access control for users who are not part of the team to sections or sub-sections in the left navigation pane at the contract type level. 
***Enhancing document usability by placing content control tags such that the end-user no longer views separate lines in the assembled document for assembled clauses that are not evaluated.   
**'''''Workflow Enhancements''''' 
***Displaying the organization unit path of the parent document by default as the path for the associated document, so that both parent and child documents have the same organization path at the time of creation and updation. 
***Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle. 
***Providing the ability to add amendments to expired agreements. &nbsp; 
***Adding a time zone attribute to provide enterprise organizations the flexibility to track the time zone or region-based activities as needed for the instance of the agreement. 
***Providing the capability to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications and allowing configuration of the sender’s email ID dynamically based on the specific contract type or instance of the record.&nbsp;     
*<span style="color:#008000;">'''Mobile App Updates'''</span> 
**Improving the usability of the mobile app by refreshing the agreement or requests list automatically after an approve, reject or request review action is performed.   
*<span style="color:#008000;">'''Enhancements to ICI API 2.0'''</span> 
**Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata.   

*<span style="color:#008000;">'''Enhancements to ICI Add-ins'''</span> 
**''Icertis Experience for Word'' 
***Displaying a set of 30 clauses per page with pagination for easy navigation between clauses listed on the clauses, clauses in templates and clauses in agreement pages. 
***Providing extended attributes within the add-in for creation and modification of clauses and templates. 
***Allowing the deviation approver to view and directly approve or reject clause deviations in an agreement from within the add-in. 
***Displaying a validation message in clause content control enabling users to insert and tag clauses at the correct location in the document before publishing it.   
**''Outlook Add-in'' 
***Enhancing the Outlook Add-in by providing the ability to upload email in .docx or .msg format as associated documents for an agreement from within Outlook.     
*<span style="color:#008000;">'''Enhancements to Artificial Intelligence Applications'''</span> 
**Introducing a legal playbook in the 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> 
**Introducing the Risk Assessment Report which is a trendline chart report that depicts the agreement aggregate risk score by their version. ICI’s AI algorithm identifies the playbook exceptions for a new version. 
**Introducing the Clause Summary Report to help clause administrators to understand and assess the impact of changes made to a clause. 
**Providing users the capability to generate a report as per the time zone of their choice from within the report itself.   
*<span style="color:#008000;">'''Improving the Icertis Experience'''</span> 
**Extending support for ICI dashboard widgets in the Icertis Experience for Salesforce Home page, so that users can perform all necessary actions from within Salesforce itself. 
**Supporting auto-renewal and reset expiry functionalities in Icertis Experience for Workday, thus saving time and avoiding data duplication. 
**Enhancing the generic integration framework to support custom pre- and post-processing hooks to considerably reduce implementation time, and allowing users to define and configure folder structure and file names as per the business requirement.   
*<span style="color:#008000;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span> 
**In release 7.12, the Software Development Kit (SDK) was released to support partners for technical configuration. With this release, documentation for ICI coding guidelines, ICI developer methods, local environment setup using ICI binaries, and ICI customization and use cases are also available.   

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

*Refer to the detailed ''[http://int-wiki.cloudapp.net:8086/ICIHelp7.14/index.php?title=ICI_Help Wiki]'' documentation for the explanation and capabilities of these and all other ICI features and functionalities. 
*Refer to the [[#_Technical_Requirements_for|Technical Requirements]] for the release in this document.&nbsp; 
*Partners can access the Icertis Software Development Kit documentation [https://icertis365.sharepoint.com/sites/PartnerPortal/Shared%20Documents/Forms/AllItems.aspx?newTargetListUrl=/sites/PartnerPortal/Shared%20Documents&viewpath=/sites/PartnerPortal/Shared%20Documents/Forms/AllItems.aspx&viewid=29700541-b0d8-4150-b240-6aee2bc1cd05&id=/sites/PartnerPortal/Shared%20Documents/ICM%20Platform/Release%20Management/SDK here]. Icertis internal teams click [https://icertis365.sharepoint.com/sites/PM/Release%20Management/Forms/AllItems.aspx?csf=1&web=1&e=Pe8IWc&cid=e164ee54-11c8-49ad-a151-cc535011c793&RootFolder=/sites/PM/Release%20Management/C7%20Release%20Notes/Platform%20Core/7.12&FolderCTID=0x0120001C0CCA4C67C5754298A23D6FBE35622E here] to access the documents. 

&nbsp;

== ICI Application Enhancements ==

<span style="color:#008000;">'''659853 – Upfront chevron view for agreement journey'''</span>

In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&nbsp;<br/> Users can view the current status of an agreement on the Agreement Index or Details page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&nbsp;<br/> With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.

The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:

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

2. Approve:&nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&nbsp;

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

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

'''Note''':&nbsp;

*The chevron view is only applicable to agreement contract type (agreements and amendments). 
*By default, the chevron is disabled; it can be enabled for selected contract types. 
*The chevron labels support localization. 

'''<span style="color:#008000;">512931 – Visibility of sections on the left navigation pane to non-team users</span>'''

The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&nbsp;<br/> This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.<br/> &nbsp;

<span style="color:#008000;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>

With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.
<div class="image-green-border">Configurators can:&nbsp;</div> 
*Configure a smart link across any ICI entity that defines the entity relationships. 
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. 

Users can:&nbsp;

*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp; 
*Access existing ICI grid’s capabilities such as such as export the smart link result or set to Excel/ CSV format for Smart Link results. 

Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.<br/> The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.<br/> For example, consider entities related in multi-level hierarchy as Agreement > Obligations > Fulfillments. Earlier, users had to navigate through obligations in order to access the child fulfillments. Users can now navigate directly from parent agreement to grandchild fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.<br/> &nbsp;

&nbsp;

'''<span style="color:#008000;">584439 – Introducing Contract Manager role for agreements&nbsp;</span>'''

In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement. This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&nbsp;<br/> Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.<br/> With this release:&nbsp;

*Assignment of the user against contract manager role in the team can be only achieved through event rules using action Add To Team. 
*Only one contract manager is available inside the agreement at any given point of time. 
*The contract manager will have provisions same as that of primary owner. 
*The contract manager name is displayed on the agreement Summary page. 
*Agreements can be searched using the contract manager name. 
*Managing adhoc modification for contract manager role user will be restricted inside the agreement Team tab similar to primary owner role user. 

&nbsp;

<span style="color:#008000;">'''714872 – Improved document usability'''</span>

Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&nbsp;

These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.

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.

With this release:

*All the content controls are put together in a single paragraph on any line with valid content. 
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. 
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. 
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&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. 

'''Note''':&nbsp;

*Only file-based clauses are supported. 
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. 
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. 
*Numbering at the template level is not supported. 
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. 
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. 

<span style="color:#008000;">'''555890 – Ability to create peer agreement from within the base agreement'''</span>

Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&nbsp;<br/> With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - Allow Peer Creation Wizard, Allow Multiple Instances and Allow Two-Way Linkage.

&nbsp;

<span style="color:#008000;">'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''</span>

Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.<br/> With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&nbsp;<br/> For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document now displays the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents have the same organization unit path at the time of creation as well as updation.

&nbsp;

This is applicable to the following associations:&nbsp;

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

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

&nbsp;

<span style="color:#008000;">'''575665 – Ability to capture multiple email IDs in a single data type'''</span>

Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.<br/> With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send the automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&nbsp;

Users can now:&nbsp;

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

&nbsp;

<span style="color:#008000;">'''583186 – Ability to add amendment on expired agreement'''</span>

Currently in ICI, users have to revive the agreement from expired to executed state by resetting its expiry date and can then add amendments to it.<br/> With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&nbsp;<br/> The Add Amendment action is configurable through role action mapping on the expired state of agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.<br/>  

<span style="color:#008000;">'''593928 – Ability to configure sender email ID for automated emails'''</span><br/> Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.<br/> With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&nbsp;<br/> Administrators can now:

*Configure the sender information while setting up the subscription under notifications using the specific user and/ or user attribute information in the agreement. 
*Configure the email addresses for Reply To in the subscriptions setup which recipients can revert to. 
*Send automated notifications from the configured email address with the configured Reply To user email addresses. 

&nbsp;

'''<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 the agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&nbsp;<br/> To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.

With this release:

*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). 
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. 
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. 
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. 
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. 

'''Note''':&nbsp;The time zone-based processing can be enabled for all the contract types across the ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.

&nbsp;

'''<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;<br/> With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&nbsp;<br/> The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.<br/> &nbsp;

<span style="color:#008000;">'''545126 – Availability of business status value in ICI event messages'''</span>

For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.<br/> With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.<br/> &nbsp;

<span style="color:#008000;">'''574034 – Ability to have flexible contract type extension'''</span>

ICI provides the flexibility to select and use masterdata attributes as extensions to agreements and associated documents at the time of instance creation. Users can create rules to add or remove these&nbsp;extended attributes&nbsp;to agreements and associated documents.

With this release, many ICI capabilities will now support the extension attributes in the same way as normal attributes.

Users can now:

*Configure conditional&nbsp;attributes,&nbsp;tracking&nbsp;attributes,&nbsp;computations&nbsp;(enable expressions)&nbsp;to use as&nbsp;extended&nbsp;attributes. 
*Save extension attributes selection as a template for reuse. 
*Control access privileges&nbsp;for&nbsp;extended&nbsp;attributes based on the user role. 
*Maintain audits for the&nbsp;extended&nbsp;attributes. 

&nbsp;

<span style="color:#008000;">'''551122 – Localization support for clauses into templates'''</span>

Previously in ICI, there was no provision to have localization of clauses that could be used to create agreements in different languages. Hence, users had to create multiple templates to be able to create agreements in different languages.

With this release, users can store the localized version of clauses and enable them when authoring and executing agreements. So, users can configure the template with localized clauses that can be used to create a localized agreement. This considerably reduces the efforts of creating and managing multiple templates to support different languages.

&nbsp;

<span style="color:#008000;">'''550181 – Rules implementation for localized masterdata attributes'''</span><br/> Previously, localization support for masterdata attributes was limited to display localized values in lookup attributes based on language set in User Preference. If the attribute had a lookup with a localized value, its rule would not get triggered as the rule was supported only in English.

With this release, users will be able to:

*Trigger a rule if the masterdata value has been localized on the agreement, contract request, association or the masterdata on the create/edit page.&nbsp; 
*Trigger a rule if any lookup type attribute is updated using Icertis Experience for Word.&nbsp; 
*Configure any rule type as all rules now have localization support. 
*Evaluation of localized values will be supported for all rule types given that the rule is configured in the English language. 

&nbsp;

<span style="color:#008000;">'''551105 – Ability to define nomenclature for Association Agreement Code for Peer and child entity'''</span>

Previously in ICI, tracking individual associated records such as line items, rounds and awards back to their related RFQ was tedious.

With this release, ICI provides a capability to define a custom agreement code with reference to the peer and parent-child contract type at the time of creating associations for that agreement contract type.

Users can now:

*Set a boolean attribute to define the custom nomenclature for the selected association contract type which can be either peer or parent-child.&nbsp; 
*Define the separator for the association agreement code with available options.&nbsp; 
*Define the parameters for the association agreement code from the available selection attributes such as parent attribute, selected association attributes and agreement code suffix.<br/> &nbsp; 
<div class="image-green-border">[[File:7.12 Custom Agreement Code 3.png|720px|7.12 Custom Agreement Code 3.png]]</div> 
'''Note:''' Users will be redirected to the ''Create Agreement ''wizard while creating associations for the agreement contract type that has custom nomenclature enabled.

&nbsp;

<span style="color:#008000;">'''550193 – Extended number of records while adding a table as an association'''</span>

ICI supports adding associations to an agreement in various forms, such as documents and tables.

With this release, ICI has now extended support to 200 records that can be assembled in an Association tagged as a table.

&nbsp;

<span style="color:#008000;">'''585000 – Ability to define parent-child relationship for peer associations'''</span>

ICI provides the functionality to attach associations to agreement entities. This functionality has now been enhanced with the ability to define the type of relationship (association) as Parent, Child or Peer. The Linkage Type field is enabled through technical configuration.

With this release, agreements can have only one association as a parent and all existing related agreements will be tagged as peer or child associations.
<div class="image-green-border">[[File:7.12 Linkage Type 10.png|720px|7.12 Linkage Type 10.png]]</div> 
&nbsp;

<span style="color:#008000;">'''574036 – Ability to configure and control access privileges based on role'''</span>

ICI now provides the capability to define new roles for agreements, amendments and associated documents as per business requirements and control their access using existing ICI functionalities (such as Role Action Mapping, Attribute Group Privileges and Security Groups).

'''Note:''' Custom roles do not support the workflow actions dependent upon other action requests (For example, workflow actions ''Approve'' and ''Reject'' for ''Send'' ''for'' ''Approval ''action).

&nbsp;

<span style="color:#008000;">'''645417 – Ability to create agreement with latest approved version while using Copy Agreement functionality'''</span>

Previously in ICI, the existing agreement’s template version was used to create a copy during ''Copy Record'' process even if the updated latest template was available in the system.

With this release, the source agreement’s latest approved template will be selected by default to create the copy.

&nbsp;

'''<span style="color:#008000;">547854 – Ability to implement bulk association to support large volume data of associations</span>'''<br/> The bulk associations capability has enabled ICI to handle large number of associations in the tune of thousands, by presenting itself as a lightweight association as well as tremendously improving performance.&nbsp;

The bulk association configuration has now been simplified by providing a Enable Bulk Processing flag at contract type definition level which triggers a set of defaults that has been intentionally restricted. The end user experience for the bulk association has not changed from the way that the conventional association is handled from the UI, rather the underlying data structure has been further enhanced to make it go the distance.&nbsp;

Performance has been the key while introducing and designing this new association, which has given way to the new type of instance, namely the Proxy Instance, which is retrieved in every GET call. The actual instances are referred by using this proxy instance, thereby reducing the load on the GET APIs. Specialized GET and SET APIs have also been introduced for bulk associations to improve its adaptability and ease-of-use.

Bulk associations have very effectively consumed the Elastic Search Bulk API to sync a large set of data at one go, rather than the traditional way of one instance at a time, adding to the boost in performance.

Bulk association is tweaked to be able to address the large data situation that Sourcing apps require, including:

*Disabling the workflow.&nbsp; 
*Restricting the system associations to just team.&nbsp; 
*Restricting document assembly.&nbsp; 
*Simplifying the association team by maintaining team at proxy level to use access level as ALL or NONE, using a layer over the existing robust ICI authorization.&nbsp; 
*Restricting indexing of bulk associations attributes in the parent, which can be achieved through a technical configuration.&nbsp; 
<div class="image-green-border">[[File:547854 Ability to implement bulk association to support large volume data of associations.png|720px|547854 Ability to implement bulk association to support large volume data of associations]]</div> 
&nbsp;

<span style="color:#008000;">'''609753 – Enabling FIPS (Federal Information Processing Standards) compliance in ICI'''</span>

With this release, ICI has enabled support for FIPS compliant encryption algorithms.

&nbsp;

== Mobile App Updates ==

'''<span style="color:#008000;">629922/635972&nbsp;– ICI mobile application management support for Microsoft Intune</span>'''<br/> In our effort to consistently improve user experience and ensure the security of our users, ICI has extended support for Microsoft Intune in our Mobile Application Management (MAM).&nbsp;

Our employees, customers and partners use mobile devices for personal and professional tasks. While ensuring productivity, we also want to prevent data loss, both - intentional and unintentional. The MAM app protection policies allow users to manage and protect their organization's data within an application.

The ICI Mobile App which is available in the App/Play Store is ready to use for app protection policies but not for app configuration policies.&nbsp;

Microsoft Intune is a scalable cloud service architecture that leverages cloud for insights and baselines for our security policies and configuration settings. It helps safeguard data that is not managed by ICI and used by employees, customers or partners to access work files.

The key benefits of making ICI MS Intune-compatible include:&nbsp;&nbsp; &nbsp;

*Protecting company data at the App level, for both – managed and unmanaged devices, as the management is based on user identity. 
*Ensuring App layer protections are in place. For example:&nbsp; 
**Entering a pin to open the App in work context 
**Controlling the sharing of data between Apps 
**Preventing the saving of company App data to a personal storage location   
*Supporting Mobile Device Management (MDM) in addition to MAM ensuring device protection and control over App management. For example: 
**Entering a pin to access the device 
**Deploying managed apps to the device 
**Deploying apps to devices through your MDM solution   
*Using App protection policies, with or without MDM, at the same time. For example, you may choose to use a company issued phone with both – MDM and App protection policies, whereas, a personal phone may be protected by only the App protection policies. 
*Applying a MAM policy to the user without setting the device state. The user will get the MAM policy on both - the BYOD (bring-your-own-devices) and the Intune-managed device. You can also apply the MAM policy based on the managed state. 

'''Note:''' The policies do not apply when using the App in personal context and does not affect end-user productivity.&nbsp;

ICI Administrators can configure the ICI mobile application as a managed App using Intune configuration policies. To avail the benefits of Intune MAM settings, users have to download the ICI application from the Intune store set by the ICI Administrator and set company portal policies on their mobile phones.

Administrators can now:

*Enroll the device in Microsoft Intune. 
*Configure the access privileges for users and user groups for ICI Mobile application using Microsoft Intune policies. 
*Pre-configure the system URL so that users do not need to enter it every time. 
*Manage and protect organization's data within an application. 

&nbsp;

== ICI API Enhancements&nbsp; ==
<div class="image-green-border">
<span style="color:#008000;">'''553319 – Additional APIs for amendments, contract requests and searches in ICI API 2.0'''</span>

With this release, some new APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for amendments, contract requests and searches.

These include:

*Amendment APIs&nbsp; 
**In addition to the existing APIs to create amendments, new API are provisioned to create orphan amendments in the system.   
*Contract Request APIs 
**In addition to the existing APIs to manage contract requests, new APIs have been added to support getting and adding associations in a contract request.   
*Search APIs 
**Search API have been added to allow users to query agreements and related entities across multiple contract types. 
**Search APIs have been added to allow creating,&nbsp;executing and deleting saved searches.   

&nbsp;
</div> 
== Enhancements to ICI Add-ins&nbsp; ==

<span style="color:#008000;">'''619841 – Introducing the new and improved Icertis Experience for Word'''</span>

With this release, two ICI Add-ins, NegotiateAI and Icertis Experience for Word, have been merged to provide users a seamless experience.&nbsp;<br/> Icertis Experience for Word can be leveraged to create, edit and manage templates, clauses and agreements.&nbsp;

It is now possible for ICI Administrators to configure and setup Icertis Experience for Word.&nbsp;

Using Icertis Experience for Word, users:

*Can work with templates, clauses and agreements.&nbsp; 
*Perform different tasks such as creating, editing and deleting template variables. &nbsp; 
*Tag attributes, clauses, associations, signatories and template variables.&nbsp; 

'''Note: &nbsp;'''

*Users can view and edit only those clauses and agreements for which they have Manage privilege in ICI.&nbsp; 
*To edit an agreement, a user needs to download the agreement document and open it in Icertis Experience for Word.&nbsp; 
<div class="image-green-border">[[File:619841 Introducing the new and improved Icertis Experience for Word.png|720px|619841 Introducing the new and improved Icertis Experience for Word.png]]</div> 
&nbsp;

<span style="color:#008000;">'''487082 – Ability to perform agreement workflow actions from Icertis Experience for Word'''</span>

Previously, tasks related to template and clause management could be managed using Icertis Experience for Word. However, to manage agreement workflow related tasks, users had to switch to ICI Web.&nbsp;&nbsp;&nbsp;&nbsp;

Now, users can directly perform agreement actions such as ''Send for Approval, Approve, Reject,'' and''Recall'' from Icertis Experience for Word itself, instead of navigating to ICI Web.
<div class="image-green-border">[[File:487082 Ability to perform agreement workflow actions from Icertis Experience for Word.png|720px|487082 Ability to perform agreement workflow actions from Icertis Experience for Word.png]]</div> 
&nbsp;

'''<span style="color:#008000;">571651 – Ability to view deviations in Icertis Experience for Word</span>'''

With this release, the deviated clauses will be highlighted in the latest version of the agreement within Icertis Experience for Word. Clause deviation details such as ''Status, Deviated by, Deviated on'' as well as a link to view the agreement in ICI are displayed.
<div class="image-green-border">[[File:571651 Ability to view deviations in Icertis Experience for Word.png|720px|571651 Ability to view deviations in Icertis Experience for Word.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> 
== Enhancements to Artificial Intelligence Applications in ICI ==

<span style="color:#008000;">'''510546 – Establishing a contract lineage using AI'''</span>

510546 – Establishing a contract lineage using AI<br/> Contracts go through multiple transformations over a period of time. During the contract negotiations, multiple attributes and clauses get added or changed. Team members, statuses, commitments and associations also get added, updated or removed. Even after the contract is executed, many addendums get added subsequently; or multiple clauses get replaced with new ones in the amendments, and so on. With such a high number of transformations, it is difficult to keep track of which clause or attribute is in force for a contract.&nbsp;

ICI has improved usability by using AI so that users can now visualize the changes done to the contract over a period of time, so that all the changes made are visible in the contract at one go.&nbsp;<br/> <br/> Contract owners can now:&nbsp;

*Easily see the changes in the clauses, attributes, team members, statuses, versions, commitments and associations due to developments in the contract negotiation process or due to various amendments and addendums added subsequently. 
*Get a consolidated view of changes by grouping them into weeks, months, quarters or years. 
*View the previous and changed values of individual attributes, clauses, and so on. 
*Track the change history of individual attributes and clauses throughout the contract life cycle, with a single click. 
<div class="image-green-border">[[File:510546 Establishing a contract lineage using AI.png|720px|510546 Establishing a contract lineage using AI]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:510546 Establishing a contract lineage using AI2.png|720px|510546 Establishing a contract lineage using A2]]</div> 
&nbsp;

<span style="color:#008000;">'''575397 – Improved AI discovery model'''</span>

ICI’s existing discovery model discovers 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&nbsp;<br/> With this release, the process of discovering attributes and clauses has been improved to achieve better accuracy by training the in-built discovery model with a wide variety of agreements.&nbsp;

The existing ObligationAI model has been enhanced to discover the obligations in a more robust and accurate manner.<br/> <br/> Key highlights of this feature are:&nbsp;

*The overall discovery accuracy of out-of-the-box attributes has been improved by more than 15%. 
*With the enhanced model, the discovered values of out-of-the-box attributes such as payment terms, notice period for termination, auto renewal, evergreen agreement, compliance standard mentioned in agreement, contract value, etc. are near perfect. 
*ObligationAI model is improved to identify following types of obligations out-of-the-box: 
**Contract deliverables, compliance and audit, performance related obligations, project prerequisites and assumptions, incident management, contract governance, payouts and invoicing as well as contract termination.   
<div class="image-green-border">&nbsp;</div> <div class="image-green-border">'''<span style="color:#008000;">602198 – Support for user created attributes in NLP search</span>'''</div> 
In the previous release, the ICI AI-enabled mode of searching supported querying on system and seeded attributes using a spoken language statement.

With this release, the functionality has been enhanced to support user defined attributes as well. For example, queries such as “''contracts in region as EMEA''” would fetch the correct results even if “region” is a display name of a user defined attribute. In addition to this, NLP search is also enhanced to consider string operators such as “''starts with''” and “''contains''”, for example, “''contracts where supplier name starts with Adobe''”.<br/> &nbsp;

<span style="color:#008000;">'''575399 – UX revamp to display discovered attributes and original document side-by-side'''</span>

Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the ''Document View'' in order to review the recommendations given by the AI algorithm.

With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.

When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.
<div class="image-green-border">[[File:575399 UX revamp to display discovered entities and original document side-by-side.png|720px|575399 UX revamp to display discovered entities and original document side-by-side.png]]</div> <div class="image-green-border">&nbsp;</div> 
<span style="color:#008000;">'''575455 – Improved discovery process performance and parallel processing of multiple documents'''</span>

Previously, upon receiving multiple requests, the AI discovery model added them in a queue form and processed each document sequentially. The time taken to complete the discovery of documents was also considerably high.

With this release, the discovery performance has been enhanced such that multiple documents can be processed simultaneously and within lesser time. Users can now start the discovery process for their document without waiting for other discovery processes to complete. A total of 20 documents can now be processed in parallel.

The duration of document discovery has now been significantly reduced. On an average, the time taken to complete the discovery process of a typical contract has been improved by more than 100%. For very large contracts with 100+ pages, the discovery performance has been improved by over 500%.

&nbsp;

== Enhancements to Reports ==

<span style="color:#008000;">'''570314 – All core SSRS reports to only include contract types classified as Contracting'''</span>

ICI offers the functionality to classify ''Business Application Type/ Contracting'' agreement type at contract type level. With this release, core reports will be limited to ''Contracting'' business&nbsp;application type.
<div class="image-green-border">[[File:7.12 Reporting 1.png|720px|7.12 Reporting 1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">
Users with access to standard and insights reports will only be able to see data related to agreements with ''Contracting'' business application type. Thus, the reporting data would not contain any sourcing agreements.

This is applicable to the following reports - Agreement Clause Content Report, Agreement Deviation Report, Agreement Pending Approval Report, Agreement Pending Execution Report, Approved Request Waiting for Contract Creation Report, Average Agreement Turnaround Time Report, Clause Deviations Report, Clause Profiling Report, CLM Activity Report, Cycle Time Report, Detailed Report, Expired Agreement Report, Expiring Agreement Report, Signature Type Report, Template Clause Report, Analytics Deviation Insights Report, Analytics Deviation Insights Report – KnowMore and Analytics Clause Insights Report.

Only contracting reports are shown in the ''Contract Type'' filter.
</div> <div class="image-green-border">
[[File:7.12 Reporting 2.png|720px|7.12 Reporting 2.png]]
</div> 
&nbsp;

<span style="color:#008000;">'''567137 – Ability to add datasets for associated documents in Power BI for obligation and management'''</span>

In order to have a comprehensive view of the state of obligation, compliance users needed to have self-serve ways to build reports and dashboards. Users have now been given the flexibility to build reports on obligation compliance across hierarches – from agreements and obligations to fulfillments and fulfillment evidences.&nbsp;

<br/> With this release, users have the option of slice and dice for viewing and narrowing down to the right type of obligations for any given context. Advanced analytics with Power BI is the ICI offering to let customers create and view custom reports. Users will now have Obligation Management application datasets for agreement, obligation and fulfillment entities in the Power BI data model as well.&nbsp;

With the additional data sets, users will be able to generate reports on Power BI such as for:

*The aggregate fulfillment status for a given obligation, especially for recurring fulfillments. 
*Number of days it took for a fulfillment cycle, which is for an obligation or fulfillment to move from created to approved state. 
<div class="image-green-border">[[File:7.12 Reporting 3.png|720px|7.12 Reporting 3.png]]</div> 
&nbsp;

<span style="color:#008000;">'''657965 – Support for Service Principal Authentication method for Power BI'''</span>

ICI has now extended support for ''Service Principal Authentication'' method to authenticate Power BI resources for advanced analytics. It has been implemented as the default method of Power BI authentication for improved security. However, the option to continue with the current authentication method of using user credentials for Power BI is still available.

&nbsp;

<span style="color:#008000;">'''606134 – All Power BI Reports to only include contract types classified as Contracting'''</span><br/> While creating reports, users with access to Advanced Analytics will now be able to see Business Application Type field in the agreement table of the Power BI data models.

Since the Create Report functionality is common to sourcing and contracting, this field allows users to segregate data for sourcing and contracting.

&nbsp;

<span style="color:#008000;">'''573000 – Sub-role included in User Profiling, Agreements Pending Approval and Detailed Reports'''</span><br/> ICI provides the ability to define sub-roles for the approver role. With this, all the capabilities of the approver are enabled for users at the sub-role level. This capability has now been extended to reports so that users can have relevant information and make informed decisions.&nbsp;

With this release, the User Profiling Report, Agreements Pending Approval Report and Detailed Report have now been modified to display the approver sub-roles such as Contract Admin, Legal Approver, and so on.

&nbsp;

'''<span style="color:#008000;">573621 - Enhancement to reports processing error message</span>'''<br/> Previously, when viewing reports resulted in processing errors, the No data available message was displayed. This message has now been modified for clarity, as follows:<br/> An error occurred during report processing, if the issue persists kindly contact customer support team.

Reports impacted include Agreement Clause Content Report, Agreement Deviation Report, Agreements Pending Approval Report, Agreements Pending Execution Report, Analytics Clause Insights Report, Analytics Deviation Insights Know More Report, Analytics Deviation Insights Report, Approved Requests Waiting For Contract Creation Report, Attribute Information Report, Attribute Value Report, Average Agreement Turn Around Time Report, Clause Deviations Report, Clause Profiling Report, Clauses Pending Approval Report, CLM Activity Report, Cycle Time Report, Detailed Report, Expired Agreements Report, Expiring Agreements Report, Masterdata Information Report, Signature Type Report and User Profiling Report.

&nbsp;

<span style="color:#008000;">'''601540 - Deprecating Template Clause Report as dashboard KPI'''</span><br/> With this release, the Template Clause Report will only be accessible from the Reports tile. It has been deprecated as dashboard KPI as it only identified the average number of clauses per template across ICI and displayed a single number on the dashboard. The performance slowed down the dashboard loading process as the KPI involved calculation and aggregation of data.

&nbsp;

== Integrations ==

<span style="color:#008000;">'''573373/573377/573379 – Generic Integration Framework to support contract requests, associations and amendments via ASB'''</span><br/> Previously, ICI supported a generic ASB adapter for inbound and outbound integration for agreements. With this release, support is provided for contract requests, associations and amendments.&nbsp;

Using an external application, users will now be able to:

*Create and update contract requests in ICI. 
*Create associations to an existing agreement or RFx record in ICI. Users will thus be able to manage purchase requisitions, purchase orders, sourcing events and similar tasks by sending associated data. 
*Update amendments to an agreement on the created, updated, approved and executed actions.&nbsp; 
*Add and update team information for agreements and contract requests via ASB. 
*Validate mandatory attribute fields for masterdata, agreements, contract requests or amendments. 

&nbsp;

<span style="color:#008000;">'''594454 – Support for JSON files and Blob connectors'''</span><br/> Previously, CSV files were supported for masterdata upload using ASB and SFTP, whereas text-based files were supported for uploads using SFTP.&nbsp;

With this release, the file-based integration will additionally support JSON file format, while also supporting Blob connectors. Additionally, a new attribute Post Process Log has been added, which indicates the Service Bus topic to which the payload will be moved after its processing.&nbsp;

In addition to post process logs, persistent logs have also been introduced in the ICI database for all processing failures. These logs will be used for reporting purposes.

&nbsp;

<span style="color:#008000;">'''554864/554868 – Support for request review and upload actions in Salesforce grid'''</span><br/> Previously, ICI users could manage and execute contract management tasks using Salesforce Classic and Lightning user interface. The Icertis Experience for Salesforce introduced support for the following actions at the grid level - Assemble, Download and Send for Approval.&nbsp;

With this release, support has been extended for the Send for Review and Upload document actions, thus considerably improving usability. The action buttons displayed on the user interface are based on the privileges assigned to the user via role action mapping in ICI . The agreement can be sent for review to multiple users by selecting the users from the available list.

'''Note:''' If a user wants to view or edit a contract record, they will still have to double-click the contract record which will open the contract details page in Salesforce.&nbsp;

&nbsp;

<span style="color:#008000;">'''537774 – Ability to configure automated contract/task creation based on Opportunity/Quote'''</span>

Previously, users could only manage contracts using the Icertis Experience for Salesforce. They did not have the option to automatically initiate a contract based on an Opportunity or Quote status.

With this release, the contract creation process has been automated based on Opportunity or Quote status, thus increasing the productivity of Salesforce users.

Salesforce Administrators can now:

*Configure the Opportunity or Quote status which can automatically trigger the contract creation. 
*Configure the contract type which should be used to create the contract based on data from an Opportunity or Quote. 
*Define the Type of Paper to be used as Own or Third Party. 
*Configure automated contract creation or automated task creation to initiate the contract creation process: 
**For auto-creation of contracts, the ICI Experience for Salesforce can be configured to create a combination of contracts to be auto-generated based on the opportunity or deal type. 
**For auto-creation of tasks, Salesforce users will be able to create a contract using a single button click that will assemble all necessary documents for the type of contract to be created.   

&nbsp;

<span style="color:#008000;">'''574458 – ICI task integration to Salesforce tasks'''</span>

Previously, Salesforce users could manage all internal and external tasks within Salesforce itself, but not ICI tasks.&nbsp;

With this release, Salesforce users can now manage ICI tasks from within Salesforce. ICI Administrators can configure ICI task integration with Salesforce so that the tasks created in ICI are pushed to Salesforce. This allows users to view task details with attributes such as ''Task Name'', ''Status'', ''Priority'', ''Due Date'' within Salesforce itself.

&nbsp;

'''<span style="color:#008000;">541825 – Integration with the new eSignature platform &nbsp;&nbsp;</span>'''

With this release, customers can now use ''Namirial eSignAnyWhere'' as their electronic signature platform to send the agreements electronically for signatures to internal and external signatories. The invited signatories receive an email notification with a link to the document to review and sign, or decline to sign, or to delegate the action. The agreement will be executed once the document is signed electronically by all the involved signatories.&nbsp;&nbsp;

Contract administrators can track the status of the agreements sent for signature within ICI. They can also recall the agreement sent for signature, if it was not signed by all parties.

&nbsp;

<span style="color:#008000;">'''579067 – Ability to support additional electronic signature platforms'''</span><br/> ICI enhanced the adaptability/flexibility of the eSignature interface, by making it possible to develop and integrate adapter for any new electronic signature provider based on customer requirements.

&nbsp;

'''<span style="color:#008000;">569172 – Enabling Electronic seal tag for signing agreement documents &nbsp;&nbsp;</span>'''<br/> Previously, users were able to sign agreements based on signature tags present in the agreement templates. &nbsp;&nbsp;

With this release, ICI has extended the support for enabling electronic seal tags in templates that will be used for marking electronic seals during the signature process using DocuSign. The support of electronic seals will help the organization’s legal teams to certify the integrity and the origin of the contracts.

&nbsp;

<span style="color:#008000;">'''580066 – Ability to redirect emails when testing Adobe Sign eSignature on other instances'''</span><br/> As a part of the signature process, emails to signatories are triggered via Adobe Sign, starting from when the agreement is sent for signature till the agreement is signed.&nbsp;

With this release, when ICI is set up on non-production environments, Adobe Sign emails can be redirected to other email addresses, so that real business users are not flooded with emails that require no action from them while the instances are being set up for testing purpose. This can be achieved through a technical configuration.

&nbsp;

<span style="color:#008000;">'''Digital Adoption Integration – Whatfix (White labelled)'''</span><br/> Enterprise customers today use dozens of applications to conduct their business functions. The introduction of any new application introduces a steep learning curve which is the number one time and adoption killer. This integration will allow users to quickly ramp up on ICI UX paradigms, help new employees onboard, and allow customers to rapidly add custom business specific guided workflows if they choose to.&nbsp;<br/> This integration will provide the following to end users:&nbsp;

*'''Self Help Box:''' With a list of walkthroughs and links to Icertis Help content i.e when a customer searches the self help, they will see Whatfix guided walkthroughs and links to ICI help articles. 
*'''Guided Walkthroughs:''' Customers have guided walkthroughs for core ICI scenarios which help them to use the ICI platform only. These include: 
**How to create an agreement 
**How to send an agreement for approval 
**How to approve an agreement 
**How to create a contract request&nbsp; 
**How to edit the dashboardHow to search for an agreement   

'''Note:''' These workflows will not replace and are not a substitute for the business and contracts specific Whatfix workflows customers use today.&nbsp;
<div class="image-green-border">[[File:7.12 Whatfix RN.png|720px|7.12 Whatfix RN.png]]</div> 
These core workflows have been created by Whatfix and will be enabled on a customer by customer basis during deployment. This is done via:

*Getting a specific EnterpriseId from Whatfix. 
*Updating the following config keys with the EnterpriseID: 
**Core.Integration.WhatfixEnterpriseId 
**Core.Integration.WhatfixUriWithEnterpriseId   
*Whitelisting the Whatfix.com domain within the Content Security Policy. 

&nbsp;

== ICI Platform Tools ==

<span style="color:#008000;">'''588361 – P2P support for ICI'''</span>

In the 7.11 release, some enhancements were made to the Promote To Production (P2P) tool such as Vulnerability and Penetration Testing (VAPT) fixes, testing open bugs in P2P engine, some validations in the P2P engine, and an improved user interface to provide support to P2P and DevOps teams.

With this release, changes have been made in ICI to support the P2P engine. This functionality, provided to Administrators, can promote ICI configurations/modifications that are made to ICI configurations in pre-production environments to production environments. This tool provides support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The elastic search sync is also supported by the tool.

'''Note:''' UI changes on contract type, rule set, notification template are not included.

&nbsp;

<span style="color:#008000;">'''561717 – Extended support for P2P'''</span>

With this release, changes have been made in ICI to support the P2P engine. This functionality provided to Administrators can promote ICI configurations/modifications that are made to ICI configurations in pre-production environments to production environments.

This functionality:

*Provides AWS Support for File Copy in Auto P2P tool. 
*Supports for movement of Security Group, User Group and Rule.&nbsp; 
*Gets the list of entities for which ES Sync has failed when ES Sync is not successful. 
*Provides upfront validation for Source and Target DB version mismatch before actual P2P validation process starts. 
*Gives an option to enable DB, ES and Store backup before P2P starts which is helpful for complex P2P. 
*Gives a validation error if the same entity is added multiple times, so that P2P does not fail. 
*Supports saved searches. 
*Supports User groups, Security Groups and Org Groups. 
*Supports terminated clauses and templates. This is required when a user makes a mistake, for example in language, and this already has been pushed to production. 
*Provides validations of P2P task using a small tool to validate names of all clauses and templates, thus helping to resolve issues in naming CSV files, naming in ICI, etc. 
*This is checked through VBA script. Also, users may need to manually verify Is Latest which may be in an issue in environments. 

'''Note:''' Customers using ICI versions before 7.12 need to upgrade to use this feature.

&nbsp;

== Partner Enablement ==

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

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction.&nbsp;

As part of our continuous efforts to support our partners, we have introduced the Software Development Kit (SDK) to provide them with the resources and tools that they need while implementing ICI.

In this release, we have created the following three documents:

*'''Working with ICI Tasks:''' This document provides an insight in to the ICI Task framework that will help partners to manage, execute and monitor tasks in ICI. It includes information on the design, configuration, deployment and troubleshooting of ICI tasks. 
*'''Working with ICI Hooks:''' This document provides information regarding the implementation and customization of hooks for new and adhoc requirements or modifications desired by ICI customers and partners. It includes information regarding the configuration, deployment and customizations of server-side and client-side hooks. 
*'''Self-Serve Tools:''' This document serves as a self-serve tool guide allowing partners and customers to perform several tasks on their own with ease. It includes the information and workflow of the following tools - Search Sync Tool, Translations Editor Tool, Improved ICI Health Check Tool, Configurations Editor Tool and Promote to Production (P2P) Tool<br/> &nbsp; 

== Technical Requirements for Release 7.14 ==

The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below:

[[File:Technical Requirements 1.png|720px|Technical Requirements 1]]

[[File:Technical Requirements 2.png|720px|Technical Requirements 2]]

[[File:Technical Requirements 3.2.png|720px|Technical Requirements 3.2.png]]

[[File:Technical Requirements 4.png|720px|Technical Requirements 4]]

[[File:Technical Requirements 5.PNG|720px|Technical Requirements 5]]

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