From ICIHelp7.14
Jump to: navigation, search
 
(102 intermediate revisions by 4 users not shown)
Line 1: Line 1:
  
 
+
= ICI Release Notes - Release 7.14 =
  
= ICM Release Notes - Release 7.12 =
+
== Overview of Release 7.14 ==
  
== Overview of Release 7.12 ==
+
The 7.14 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICI functionalities and the user interface.
 
+
The 7.12 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICM functionalities and the user interface.
+
  
 
The key enhancements of this release include:
 
The key enhancements of this release include:
  
*<span style="color:#008000;">'''Enhancements to the ICM Application'''</span>  
+
*<span style="color:#008000;">'''Enhancements to the ICI Application'''</span>  
**Enhancing extended template attributes to make them searchable on the Template Index page, global search, advanced search and on the search in Icertis Experience for Word
+
**Enabling Download All button for expired agreements and amendments
+
**Enhancing the functionality of Associations added as tables with localization of table headers&nbsp;
+
**Providing localization support for clauses and templates to enable users to configure templates and create localized agreements&nbsp;
+
**Providing administrators the ability to add global favorites to entity detail pages&nbsp;
+
**Establishing the differentiation between Internal Reviewer and External Reviewer along with respective role-action mapping&nbsp;
+
**Introducing a Click to Sign process, whereby signatories can directly preview and accept agreements
+
**Enhancing bulk creation of agreements with an option at configuration level to set the target workflow action for the agreements to be created &nbsp;
+
**Provisioning users to preview Approvers when swapping primary clauses for alternate clauses
+
**Introducing online editing support for agreement documents to greatly improve operational efficiency for contract owners
+
**Enhancing commitments functionality with an option to send reminders
+
**Enhancing user experience by grouping buttons on all entities' index pages, among other major functionalities
+
**Providing the flexibility to control users' actions on agreements based on their roles
+
**Enhancing the agreement index page with a button which allows copying an existing agreement to create a similar agreement
+
**Enhancing metadata of clauses with the ability to add details which can be leveraged in searches and defining rules
+
**Extending the functionality to copy team roles for peer associations of contract requests /agreements/amendments
+
**Providing users the option to clone commitments from existing ones
+
**Enhancing Excel data upload functionality with validations on choice value attributes
+
**Extending bulk download/upload functionality to associated documents enabling users to create line items with extended attributes or associated document attributes
+
**Providing the flexibility for users to create line items using extended or associated document attributes
+
**Providing users the flexibility to specify attributes for bid analysis per RFx Item and to enter value for bid analysis attributes per supplier item bid
+
**Ability to have flexible contract type extension
+
**Enhancing user experience by allowing resizing of popup windows
+
**Supporting the trigger of rules in case of attributes which have been localized
+
**Extending the number of records that can be added while adding a table as an association
+
**Introducing the ability to uniquely identify records related to RFQs
+
**Introducing flexibility in defining roles other than default roles provided in ICM
+
**Providing support for auto-attachment functionality for agreements, amendments and contract requests
+
**Enhancing associations with the ability to explicitly define the type of relationship between the association and agreement/amendment as parent, child or peer
+
**Enhancing the functionality of copying associations with the flexibility to exclude attachments
+
**Introducing a virus scan option for files uploaded into ICM<br/> &nbsp; 
+
*<span style="color:#008000;">'''Enhancements to ICM API 2.0'''</span>
+
**Introducing some new APIs that will allow business applications to interact with ICM using standard API nomenclature for amendments, contract requests and searches 
+
  
*<span style="color:#008000;">'''Enhancements to ICM Add-ins'''</span>
+
*'''''User Experience'''''  
**Allowing users to stay on the document for further edits or reviews while publishing occurs in the background.  
+
**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.  
**Enhancing the Word Add-in to display deviated clauses within the plugin
+
**Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement.
**Introducing WordAI to enhance user experience by merging NegotiateAI and Icertis Experience for Word (previously known as Scribe)  
+
**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.
**Updating the logo for ICM Word Add-in  
+
**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.
**Providing users the ability to take workflow actions such as approve, reject, send for approval and others using Icertis Experience for Word<br/> &nbsp;    
+
**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.    
*<span style="color:#008000;">'''Enhancements to Artificial Intelligence Applications'''</span>
+
*'''''Workflow Enhancements'''''
**Establishing a contract lineage using AI so that users can visualize the changes done in the clauses, attributes, team members, statuses, versions, obligations and associations over the contract negotiation process or due to various amendments and addendums added subsequently
+
**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 parallel view of discovered attributes against the original document<br/> Enhancing the in-built discovery model to discover attributes from Statement of Work agreements  
+
**Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle.
**Enhancing the discovery performance to reduce time required for discovery of documents
+
**Providing the ability to add amendments to expired agreements. &nbsp;
**Enhancing natural language search query with support for user created attributes    
+
**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;">'''Enhancements to Reports'''</span>  
+
*<span style="color:#008000;">'''Mobile App Updates'''</span>  
**Configuring core SSRS and Power BI reports to include contract types classified as Contracting&nbsp;
+
**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.    
**Introducing additional support for associated documents enabling users to create custom reports in Power BI<br/> &nbsp; 
+
*<span style="color:#008000;">'''Improving the Icertis Experience'''</span>
+
**Providing configurators the ability to redirect emails to specific addresses when testing Adobe electronic signature on non-production instances
+
**Introducing the new eSignature platform experience
+
**Enabling Electronic seal tag for signing agreement documents
+
**Supporting creation of ICM entities and contracts using SAP S/4 HANA as well as supplier masterdata integration and masterdata lookup using S/4 HANA
+
**Enhancing generic integration framework to support contract requests, associations, amendments
+
**Enhancing Salesforce experience by providing users the ability to take request review and upload document actions from within the Salesforce grid&nbsp;
+
**Providing users the flexibility to manage ICM tasks from within Salesforce
+
**Providing Salesforce users the ability to configure auto creation of contracts    
+
  
*<span style="color:#008000;">'''Introducing ICM Platform Tools'''</span>  
+
*<span style="color:#008000;">'''Enhancements to ICI API 2.0'''</span>  
**Enhancing ICM support for the PToP tool to promote ICM configurations or modifications that are made to ICM configurations in pre-production environments to production environments
+
**Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata.    
**Providing support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups
+
**Providing support for elastic search sync<br/> &nbsp;    
+
  
These release notes provide an overview of the enhancements to ICM and the ICM experience for integrations. Refer to the technical requirements and known issues for the release in this document. Refer to the detailed Wiki documentation for the explanation and capabilities of these and all other ICM features and functionalities.
+
*<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.    
  
&nbsp;
+
*<span style="color:#008000;">'''Enhancements to Artificial Intelligence Applications'''</span>
 +
**Introducing a legal playbook in the NegotiateAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.
 +
**Enhancing DiscoverAI to identify the different levels within a clause through a distinct visual representation of clauses with sub-sections displayed in a delineated view during the clause discovery process.
 +
**Enhancing the ICI discovery models to support clause and obligation discovery for additional languages such as German, Spanish and Portuguese.
 +
**Improving the inbuilt DiscoverAI model to identify additional attributes such as City, State, Zip Code, and so on. 
  
== ICM Application Enhancements ==
+
*<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;">625385 – Global Search</span>'''
+
*<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.  
The previous search functionality in ICM required users to traverse through multiple pages of the search results, to locate the record they were searching for. The results were displayed in no particular order. Traversing through pages of records was an inconvenient and time-consuming process for users, especially in case of hundreds of matching result records.<br/> Now, the ICM search functionality has been entirely revamped to provide a better, more user-friendly experience. Users can now view relevant records on the very first page of the results.
+
**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.  
With this release:
+
  
*Search results are displayed in order of relevance to the entered search query, with the best match(es) appearing as the top-most or most relevant search result(s).  
+
*<span style="color:#008000;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>
*On the search details page through the Advanced Search button, the search mode radio button selected by default is Metadata. In case of Global Search, the default search mode is Combined, that is, search will be performed on both Metadata as well as Full Text. The default view here is the extended view.
+
**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.  
*Document text which matches the search query is highlighted.
+
*The search drop-down displays top 5 relevant search results. A View All Results link is displayed, clicking which opens the results details page.
+
*Hovering over the results in the drop-down displays details about the entity&nbsp;
+
*Additional matching results are displayed below each result.  
+
  
'''Note: '''The global attributes display name begin with AppSrc, so that they can be easily searched and identified.
+
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.
  
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''551111 – Grouping of actions on index page'''</span>
+
<span style="color: rgb(0, 119, 235); font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span>
  
Earlier, the applicable set of actions available for any entity were represented using icons across ICM. For example, the agreement index page had icons for View Agreement, Preview Document and View Smart Link actions. As part of our efforts to continuously improve ICM, multiple new actions are added for an entity over time. Hence, actions are now grouped together to improve the usability and user experience. &nbsp;
+
<span style="color:#008000;">'''659853 – Upfront chevron view of agreement journey'''</span>
  
<br/>  <br/> <span style="color:#008000;">'''586165 – Support for online editing of agreements'''</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;
  
As part of contract management, agreement and amendment documents regularly go through reviews where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature. To make changes or modifications to an agreement, ICM users previously had to download a copy, perform edits and upload it back to ICM. This created a version of the document in ICM.&nbsp;
+
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&nbsp;
  
Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but also audit information was often lost, it was not possible to trace what was approved and by whom.<br/> With this release, ICM offers online editing support for agreement documents creating radical operational efficiency for contract owners.&nbsp;<br/> It is now possible for:
+
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.
  
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session where more than one party can edit parallelly using existing MS Word capabilities.&nbsp;
+
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.
*An agreement document, which has been edited using online editing, to be published to ICM without any loss of information.  
+
  
'''Note:''' Only users with edit privileges on a document can participate in editing it online.
+
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:
  
&nbsp;
+
1.&nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.
  
<span style="color:#008000;">'''550178 – Enabling search for extended template metadata'''</span>
+
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;
  
Earlier in ICM, there were only predefined metadata for templates such as Name, Clause Code, Clause Group, and so on. To fulfill the requirements of some organizations, ICM provided the capability of extended template attributes to define additional custom metadata/attributes at the template level. However, users were not able to search templates based on these extended template attributes.<br/> Now, users can search and retrieve required templates using these extended attributes as search parameters in the global search, advanced search and the template index page.
+
3. '''Execute:&nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.
  
&nbsp;
+
4. '''Manage:&nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.
  
<span style="color:#008000;">'''572767 – Ability to download all associated documents of expired agreements and amendments'''</span>
+
'''Note''':&nbsp;
  
Earlier in ICM, users could download all the associated documents of an agreement or amendment for all other states but not when the agreement was in the Expired state.&nbsp;<br/> This capability is now also provided for expired agreements and amendments. This considerably improves usability as users no longer need to navigate to the respective Association tab to download the required documents one by one. The Administrator can now define access permissions so that the Download All button is available for authorized users allowing them to easily download all the associated documents of agreements and amendments for reference.&nbsp;
+
*The chevron view is only applicable to agreement contract type (agreement&nbsp;and amendment).  
 +
*By default, the chevron is disabled; it can be enabled for selected contract types.  
 +
*The chevron labels support localization.
 +
<div class="image-green-border">[[File:7.14 release note 1.png|720px|7.14 release note 1.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''<span style="color:#008000;">512931 – Visibility of sections on the left navigation pane to non-team users</span>'''
  
<br/>  <br/> <span style="color:#008000;">'''569901 – Ability to resize popup windows'''</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;
  
Previously, popup windows within ICM had a fixed size.<br/> Now, support has been provided for users to be able to resize the windows, thereby enhancing their ICM experience manifold. This helps users to easily read information on Lookup, Team Grid and Create Association windows.
+
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;
  
&nbsp;
+
<span style="color:#008000;">'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''</span>
  
<span style="color:#008000;">'''551117 – Associated document content including table headers in the preferred language'''</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.
  
Earlier in ICM, if the language preference was English and the user created an agreement using a German language template that had an association as a table, then the buyer could create the association instance and assemble the contract. However, the language for the entire assembled document would be German, but the association table header (title) would be in English.&nbsp;
+
Users can:&nbsp;
  
This functionality has been improved so that the table header also appears in the same language as the remaining text in the template. In the example above, the entire assembled document as well as the association table header would be in German.
+
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&nbsp;
 
+
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results.  
<br/> <span style="color:#008000;">'''571054 – Ability to add global favorites to entity details page'''</span>
+
<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;
ICM Administrators can already set default favorites so that specific users can access relevant information targeted for them using global favorites. These global favorites are added to the corresponding index page of the selected entity. With this release, this functionality is further enhanced such that the Administrators can now choose to add global favorites to the Entity Details page.&nbsp;
+
 
+
They can set different default favorites for different entities for their users. For example, a pinned favorite search for line items can have different relevance as compared to a pinned favorite search for bids. Having default favorites pinned makes it easy for users to easily identify the actions that they need to take. Having pinned default favorite saved searches at entity level also helps the users access relevant information from within an entity, rather than having to travel to the index page for the same.
+
 
+
ICM Administrators can now:
+
 
+
*Choose to add global favorites to Entity Details page for specific users to view them in the associated parent or peer entity's Details page.
+
*Have global favorites added by default to the corresponding selected entity's Index page.
+
*Choose to add global favorites to both entity details and index pages.  
+
 
+
Note:&nbsp;
+
  
*The global favorites will always be appended to the last for a user per entity type.&nbsp;  
+
'''<span style="color:#008000;">584439 – Introducing the Contract Manager role for agreements&nbsp;</span>'''
*A maximum of 4 global favorites are displayed to the user based on the security group’s permissions.<br/> &nbsp;
+
  
<span style="color:#008000;">'''572768 – Display internal and external reviewer roles based on user type'''</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.
  
The Request Review functionality in ICM allows users to request their agreements to be reviewed. Before sending an agreement for approval or signature, the contract author can leverage the Request Review option and add a user or user group as reviewer.&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;
  
Previously, if the selected reviewer was&nbsp;an internal user, or a user group of internal users exclusively, still the team role/user role was depicted as External Reviewer in the Team and the History tabs respectively, on the agreement Details page. &nbsp;&nbsp;<br/> With this release:&nbsp;
+
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.
  
*If the user or all the users in the user group added as a reviewer are internal users, the role displayed will be Internal Reviewer.
+
With this release:&nbsp;
*If the user or any one user in the user group added as a reviewer is an external or third party user, the role displayed will be External Reviewer
+
*Administrators will be able to define actions and action display names for different entities and states for internal and external reviewer roles, respectively.&nbsp;  
+
  
'''Note:''' This change does not apply to Send For Review functionality as that review happens only after an agreement is executed and is applicable only for internal users.
+
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&nbsp;''action.
 +
*Only one contract manager is available inside the agreement at any given point of time.
 +
*The contract manager will have provisions same as that of primary owner.
 +
*The contract manager name is displayed on the agreement summary page.
 +
*Agreements can be searched using the contract manager name.
 +
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user.  
  
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''551122 Localization support for clauses into templates'''</span>
+
<span style="color:#008000;">'''555890 Ability to create peer agreement from within the base agreement'''</span>
  
Previously in ICM, there was no provision to have localization of clauses that could be used to create agreements in different languages. Hence, the users had to create multiple templates to be able to create agreements in different languages.
+
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;
  
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 that can be used to create a localized agreement. This considerably reduces the efforts of creating and managing multiple templates to support different languages.
+
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;
 
&nbsp;
  
<span style="color:#008000;">'''568718 Additional Click to Sign signature option available for agreements'''</span>
+
<span style="color:#008000;">'''732038 Ability to use parent’s Organization Unit path when creating associated document'''</span>
  
ICM already supports electronic and manual signatures. With this release, a Click to Sign signature process is being introduced where the signatory can preview the agreement and indicate acceptance to the terms in the agreement. &nbsp;
+
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.
  
If the signatory accepts the terms and conditions by checking the box in the Preview window, it is used to mark the agreement as accepted and signed by the signatory. The signatory also has the usual option to reject the agreement for signing, with the agreement going back to the Draft state.&nbsp;
+
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&nbsp;
 +
<div class="image-green-border">[[File:7.14 release note 6.png|720px|7.14 release note 6.png]]</div>
 +
For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.
 +
<div class="image-green-border">[[File:7.14 release note 7.png|720px|7.14 release note 7.png]]</div>
 +
This is applicable to the following associations:&nbsp;
  
ICM Administrators who are authorized to create contract types can now add Click to Sign as an option in the signature type attribute. This would make this signature flow available for contracts of that type.&nbsp;
+
*Import of Association (Line Item)
 +
*Auto Attachment Association
 +
*Obligation/ Fulfillment (Association of Association)
  
&nbsp;
+
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.
 
+
<span style="color:#008000;">'''574611 – Ability to swap alternate clause from Clause Comparison Report and view approvers'''</span>
+
 
+
Previously in ICM, the substitute language of a clause was stored as an Alternate Clause to the Primary Clause. Contract authors had the provision to replace any Alternate Clause using the Clause Comparison Report. Whenever such clauses are replaced by alternate clauses, a certain set of approvers get triggered for the agreement.&nbsp;
+
 
+
With this release, contract authors are being provided with the capability to preview the list of approvers that will be triggered due to the clause swap.&nbsp;
+
 
+
Similarly, whenever new version of an agreement is created, the Content Control window which is now displayed now has a provision to preview the approvers that will be added or removed based on the changes made to the clause.
+
 
+
<br/> <br/> <span style="color:#008000;">'''568773 – Ability to create and send agreements for approval during bulk creation&nbsp;'''</span>
+
 
+
ICM allows contract authors to create multiple agreements from a single agreement with the provision of copying associations and attributes as required. Previously, these agreements created in bulk would be in Draft status. In order to send the bulk created agreements for approval, users had to either do it individually for each agreement or they had to configure a Saved Search and take a bulk action on it.
+
 
+
With this release, this feature has been enhanced with an option at configuration level to define if these agreements are to be published, or created and sent for approval as part of the creation process.&nbsp;<br/> A choice-type attribute Target Workflow Action has been added in the existing bulk configuration masterdata contract type. Administrators can now specify whether bulk created agreements should be sent for approval or not. When the Target Workflow Action attribute is set to Create and Send for Approval and bulk agreements are generated on the model agreement:&nbsp;
+
 
+
*Approvers get added to the agreement’s team based on the rules configured.
+
*Agreements will be sent for approval to the approver(s), and the agreement status will be updated to Waiting for Approval.
+
*If no approver is present in the agreement’s team, the agreement will be approved directly and its status will be updated as Approved.
+
 
+
By default, the agreements would be created in Draft status. Amendments can also be sent for bulk approval using the same functionality.<br/> Users can also decide whether the templates for bulk created agreements would be different or same than model agreement during bulk creation process. An attribute Enable Template ReEvaluation is added in existing bulk configuration masterdata contract type.&nbsp;
+
 
+
*When Enable Template ReEvaluation attribute is set to Yes, the Template Selection rules will be re-evaluated, and the first template from the list will be used for creating bulk agreements. The Template can be same or different than model agreement depending on the configured rules.&nbsp;
+
*When the Enable Template ReEvaluation attribute is set to No, the template used for bulk created and model agreements will be same.
+
 
+
Any Template selection rule configured for bulk creation will not be evaluated if Enable Template ReEvaluation value is No.
+
  
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''550187 Provision to send reminder notifications for commitments'''</span>
+
<span style="color:#008000;">'''575665 Ability to capture multiple email IDs in a single data type'''</span>
  
ICM has the provision to track the milestones in an agreement with the Commitment functionality. Initially, to ensure that these commitments are fulfilled in timely manner, automated reminders were sent. Now, users also have the capability to send reminders at any time using the Send Reminder option and customize the notification as well as trigger reminder notifications in bulk.&nbsp;
+
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.
  
<br/>  <br/> <span style="color:#008000;">'''572677 – Flexibility to control the agreement actions based on role of the user'''</span>
+
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;
  
ICM already allows controlling workflow actions for a user through role action mapping.&nbsp;ICM has extended support for other agreement actions that can also be controlled based on the user role, thus improving the overall access control for a user.&nbsp;
+
Users can now:&nbsp;
  
Users can now control:
+
*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.  
*Actions such as Compare Documents, Compare Clause Changes and Broadcast available to a user for an agreement.  
+
*Visibility of reports available in the agreement.
+
*Creation and disassociation of associated documents from an agreement.
+
*Linking and disassociation of peer association from an agreement.  
+
  
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''572781 – Ability to copy existing agreement from the agreement index page'''</span>
+
<span style="color:#008000;">'''583186 – Ability to add amendment on expired agreement'''</span>
  
Previously, ICM supported the copy existing agreement functionality from the agreement Details page. Now, the same functionality has been added on the agreement index page for better usability. With this, the user can perform the copy action without having to navigate into the individual agreement details page.
+
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.
  
Authorized users can now click an icon on the agreement index page to copy it to create a similar agreement. Along with the agreement, users now also have the ability to select any associated documents (parent-child or peer associations), commitments or obligations to be copied; where the Allow Copy with Association flag is set to True at the contract type level. If the association flag is set to False, a validation is displayed.
+
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;
  
&nbsp;
+
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.
 +
<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>
  
<span style="color:#008000;">'''551116 – Support for extended clause metadata'''</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.
  
Previously, users were not able to add more details to a clause. With this release, an entity for clause extension is being introduced which could help users in various ways, such as, when defining rules and searches.
+
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;
 
+
Users can now:
+
 
+
*Create contract types with defining attributes from masterdata, similar to the template/user extended entity.
+
*View the clauses extended entity attributes in the clause creation wizard.
+
*Configure rules using these attributes.
+
*Enter the values for clause extended attributes using Add-ins.
+
 
+
<br/>  <br/> <span style="color:#008000;">'''569900 – Ability to cascade team from contract request, agreement, amendment to its association'''</span>
+
 
+
Previously, ICM provided support to copy team role from contract request, agreement and its amendment to its parent child association. With this release, the support is being extended to copy team role from contract request, agreement or amendment to its peer associations.
+
 
+
A tile has been added under the configuration, where an authorized user can map all such team roles for a defined contract type to its parent-child as well as peer associations.
+
  
 
Administrators can now:
 
Administrators can now:
  
*Provide the capability to copy the entire or selective team of the entity (contract request, agreement or amendment) to its peer association.  
+
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement.  
*Copy all or selective team of the entity to its peer association on a parent or peer entity event.  
+
*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>'''
  
Users can now:
+
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.
  
*Sync/update the team of association when any team is added or removed from a contract request, agreement or amendment entity.
+
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.
*Capture audit logs while copying the team from the contract request, agreement or amendment entity to its peer association.
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''574034 – Ability to have flexible contract type extension'''</span>
+
 
+
ICM 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 extended attributes to agreement and associated documents.
+
 
+
With this release, many ICM features such as lookups, saving a search, saving as a template, and so on are further enhanced to manage the extended attributes in the same way as normal attributes. This considerably improves usability and simplifies the process for users who deal with hundreds of items and need to have multiple configurations.
+
 
+
Users can now:
+
 
+
*Configure conditional attributes, tracking attributes, computations (enable expressions) to use as extended attributes.&nbsp;
+
*Mark extended attributes as mandatory and validate. &nbsp;
+
*Control access privileges for extended attributes based on the user’s role.&nbsp;
+
*Maintain audits of the extended attributes.&nbsp;
+
*Exclude extended attributes from copy while creating an agreement by copying the existing agreement.&nbsp;
+
 
+
<br/> <span style="color:#008000;">'''551119 – Ability to copy and create existing commitments'''</span>
+
 
+
With this release, users have been provided with the capability to copy an existing commitment and generate new commitments from it. Users can also configure attributes to be excluded from being copied automatically. This considerably reduces time and effort required to create individual commitments.
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''550181 – Rules implementation for localized masterdata attributes'''</span>
+
 
+
Previously, localization support for masterdata attributes was limited to attributes only. If the attribute had a lookup 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 creation 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.
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''551105 – Ability to use attributes to identify unique line items'''</span>
+
 
+
Previously, RFQs and their multiple related records such as line items, rounds and awarding records were created without any associations. Users found it difficult to link RFQs to its related records.<br/> With this release, ICM offers a provision to define an agreement code that refers to both, the RFQ attribute and the current record attribute, at the time of linking the peer association to the agreement contract type.&nbsp;
+
 
+
Users can now:
+
 
+
*Set a flag to mark the peer association as child type at contract type level which will have normal association creation workflow.&nbsp;
+
*Define the value of agreement code from the agreement and its related association contract type.
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''550193 – Extended number of records while adding a table as an association'''</span>
+
 
+
ICM supports adding associations to an agreement in various forms, such as documents and tables. With this release, ICM has now extended support to 200 records that can be assembled in an Association tagged as a table.&nbsp;
+
 
+
<br/>  <br/> <span style="color:#008000;">'''568776 – Export and import capability for associated documents'''</span>
+
 
+
ICM provides a capability for bulk download (export) and upload (import) of line items from association grid using Excel. Now, users can create line items with extended attributes or associated document attributes based on the template selection and export/import through Excel into ICM.
+
 
+
Users can now:
+
 
+
*Select and add attributes from all attributes defined in masterdata contract type.
+
*Load Excel filled by the buyer (at the RFQ level) at the Round level to match the information.
+
*Create, edit and delete records in bulk using Excel.
+
*Manage import/ export of lookup attributes, conditional attributes, and attributes derived by computations or enabled expressions in bulk.
+
*Look up attributes in the same way as masterdata is looked up using Excel.
+
*Control the access privileges to import/export Excel based on the user’s role.
+
*Control access privileges for attributes in Excel based on the user’s role.
+
*Localize and display attributes and headers in the Excel.
+
*Validate data during import/export using Excel.
+
*Keep data in Excel in sync with data displayed on the user interface.
+
*Make attributes non-editable.
+
*Manage refreshing associations during import/export.
+
*Maintain and display audit of import/export operations.
+
*Generate log files for line items.
+
 
+
<br/> <span style="color:#008000;">'''574036 – Ability to configure and control access privileges based on role'''</span>
+
 
+
Previously, ICM users could only be assigned one of the default roles available in the system.&nbsp;
+
 
+
With this release, ICM provides users the capability to define new roles and control access by specifying privileges depending on their business requirement. The access to the newly defined roles can be controlled using existing capabilities in ICM (such as Security Groups, Role Action Mapping, etc.). This is applicable for agreements, amendments and associated documents.&nbsp;
+
 
+
With custom roles, users can:&nbsp;
+
 
+
*Control navigation pane access for agreement and associated documents.&nbsp;
+
*Control group access privileges and team actions.&nbsp;
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''574087 – Ability to add auto-attachments as associations via event rule'''</span>
+
 
+
As part of RFQ creation process, users need to add several documents as mandatory attachments to RFQs that may not change frequently. Previously, users had to attach multiple such documents manually to every RFQ which was a tedious and time consuming process.
+
 
+
ICM now has simplified the process by allowing users to attach predefined standard documents automatically to associations based on defined event rules.
+
 
+
Users can now:
+
 
+
*Maintain a repository of standard documents in masterdata.
+
*Define the mapping between associations for auto-attachments for agreements.
+
*Define rules and saved search to trigger the auto-attachment process for associations.
+
*Bifurcate auto-attachments from manual attachments when copying an agreement.
+
 
+
'''Note: '''This is applicable for agreements and amendments.
+
 
+
<br/> <span style="color:#008000;">'''585000 – Ability to define parent-child relationship for peer associations'''</span>
+
 
+
ICM 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.
+
  
 
With this release:
 
With this release:
  
*Only one parent agreement can be added to another (child) agreement.  
+
*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).  
*If an agreement has already been associated as a child of an agreement, then another agreement cannot be added to it as a parent.  
+
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities.  
*Amendments can be linked to agreements and vice-versa only with a peer type of relationship; parent or child type relationships are not allowed.
+
*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.  
*Amendments can also be associated to other amendments.
+
*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.  
*Only one amendment can be associated as a peer to another amendment.
+
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date.  
*All existing related agreements will be tagged as peer associations.
+
 
+
The option to define the relationship type is provided on the same window which opens up for linking/searching an agreement from the ‘+’ sign icon.
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''572764 – Ability to scan files for viruses when uploading to ICM'''</span>
+
 
+
With this release, ICM has added a generic virus scan framework which can be used to implement other virus scanning software. When configured, this will help to scan files for any malware and protect ICM against a wide variety of threats. It is applicable to the Word and Excel plugins as well.
+
 
+
Users can now:
+
 
+
*Scan all supported file formats by default during upload.  
+
*Scan files in bulk.
+
 
+
&nbsp;
+
  
<span style="color:#008000;">'''645417 Ability to create agreement with latest approved version while using Copy Agreement functionality'''</span>
+
'''Note''':&nbsp;The time zone-based processing can be enabled for all contract types across&nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.
 +
<div class="image-green-border">[[File:7.14 release note 10.png|720px|7.14 release note 10.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
'''<span style="color:#008000;">512930 Triggering service bus events for all actions</span>'''
  
Previously, In ICM, when the new agreement is created by coping existing agreement using the Copy Record functionality, it is created with the same version as the original agreement.&nbsp;
+
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;
  
ICM now provides the capability to choose the latest approved version of the template of the original agreement during copy to create the new agreement.
+
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;
  
'''Note: '''The Copy Record functionality does not change for third party paper.
+
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;
  
<br/>  <br/> '''<span style="color:#008000;">572756 Ability to exclude auto-attached documents from the copied association</span>'''
+
<span style="color:#008000;">'''545126 Availability of business status value in ICI event messages'''</span>
  
ICM now allows attaching standard documents from the masterdata repository for associations automatically based on the defined event rule.
+
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.
  
When an association with auto-attached documents is replicated by copying, there is a need to exclude auto-attached documents from the copied association. This is required to avoid duplication of association records and unnecessary upload of files into the ICM repository as the new created record will have its own auto-attached documents.
+
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.
  
ICM provides a flag or identifier to separate associations into manual and auto-attachment associations.
+
== Mobile App Updates ==
  
Users can now:
+
'''<span style="color:#008000;">660965 – Refresh agreement list on approval</span>'''
  
*Select auto-attachment associations when an agreement is sent for signature along with the bundled association.  
+
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;
*Download all associations of an agreement in the ZIP format.&nbsp;<br/> &nbsp;  
+
  
== ICM API Enhancements&nbsp; ==
+
In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.
 +
<div class="image-green-border">[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]<br/> &nbsp;</div>
 +
== ICI API Enhancements&nbsp; ==
 
<div class="image-green-border">
 
<div class="image-green-border">
<span style="color:#008000;">'''553319 Additional APIs for amendments, contract requests and searches in ICM API 2.0'''</span>
+
<span style="color:#008000;">'''607867 ICI API 2.0 Implementation'''</span>
  
With this release, some new APIs have been introduced that will allow business applications to interact with ICM using standard API nomenclature for amendments, contract requests and searches.
+
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.
  
These include:
+
Enhancements include:
  
*Amendment APIs&nbsp;  
+
*Addition of Masterdata APIs&nbsp;  
**In addition to the existing APIs to create amendments, new API are provisioned to create orphan amendments in the system. 
+
**Users can now update the masterdata instance
*Contract Request APIs
+
**UserName field is returned in Get Team API as part of the response.   
**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, editing, executing and deleting saved searches.   
+
</div> <div class="image-green-border">&nbsp;</div>
+
== Enhancements to ICM Add-ins&nbsp; ==
+
  
<span style="color:#008000;">'''619841 – Introducing Icertis Experience for WordAI'''</span>
+
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well.
 +
</div>  
 +
== Enhancements to ICI Add-ins&nbsp; ==
  
With this release, two of the ICM Add-ins - NegotiateAI and Icertis Experience for Word have been merged into Icertis Word.AI to provide users a seamless experience.&nbsp;<br/> Icertis Word.AI can be leveraged to create, edit and manage templates, clauses and agreements.&nbsp;
+
<span style="color:#008000;">'''714872 – Improved document usability'''</span>
  
Using Icertis Word.AI, it is now possible for:&nbsp;
+
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;
  
*ICM Administrators to configure and setup Icertis Word.AI.&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.
*Other users to 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 ICM. &nbsp;
+
*To edit an agreement, a user needs to download the agreement document and open it in Word.AI.&nbsp;
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''571651 – Provision to show clause deviations in Icertis Experience for Word'''</span>
+
 
+
Previously, users were able to view deviations in agreement clauses through the agreement details page. With this release, users can now see within the Word Add-in, any such clauses which have been tagged/added in an agreement and which are deviated. The details of the deviated clause are also displayed through Word Add-in.
+
  
 +
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.
 +
<div class="image-green-border">[[File:7.14 release note 4.png|720px|7.14 release note 4.png]]</div> <div class="image-green-border">&nbsp;</div>
 
With this release:
 
With this release:
  
*A list of deviations is displayed in Agreement Clauses tab for an agreement or amendment’s document version.&nbsp;
+
*All the content controls are put together in a single paragraph on any line with valid content.  
*Clauses that are added using the Add Deviation option through the Word Add-in are also displayed.  
+
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.
*View information regarding the deviated clauses such as Status, Deviated By, Deviated On in the Word Add-in as well as a View in ICM link.  
+
*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;
  
The deviation clauses are visible based on role action mapping as per existing ICM flow. They are searchable, so users can easily navigate to a particular clause in the agreement document and view the highlighted content of those clauses in Word Add-in.
+
*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.
<br/> '''Note:&nbsp;'''
+
*Location-specific (such as center-justified) rule-based clauses cannot be tagged.  
 
+
*Numbering at the template level is not supported.  
*The deviation clauses are only displayed for the latest version of the agreement.  
+
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.  
*Users cannot perform the deviation approval flow from the Word Add-in.  
+
*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.  
 
+
<br/> <span style="color:#008000;">'''487082 – Ability to take workflow actions using 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 related tasks, users had to switch between ICM and the Word Add-in. &nbsp;
+
 
+
ICM now enables the users to accomplish agreement related workflow actions such as approving, rejecting or recalling an approved agreement directly using Icertis Experience for Word. This considerably reduces the turnaround time and improves the user experience. User can view the updated status of the agreements on the Versions tab, History tab and Audit Trail on the ICM Web.
+
  
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''574616 Icertis logo updation in Icertis Experience for Word'''</span>
+
<span style="color:#008000;">'''660390 Ability to show more clauses per group'''</span>
 
+
With this release, the ICM Word Add-in logo has been replaced with the improved logo for Icertis Experience for Word.<br/> &nbsp;
+
 
+
== Enhancements to Artificial Intelligence Applications in ICM ==
+
 
+
<span style="color:#008000;">'''510546 – Establishing a contract lineage using AI'''</span>
+
  
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, obligations, associations also get added, updated or removed. Once the contract is executed, many addendums are added later or multiple clauses are replaced with new clauses in the amendments, etc. With such high number of transformations, it is difficult to keep track of which clause or attribute is in force.&nbsp;
+
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.
  
ICM has now improved usability by using AI so that users can now easily see the changes in the clauses, attributes, team members, statuses, versions, obligations and associations due to developments in the contract negotiation process or due to various amendments and addendums added subsequently in one go. This helps contract owners to learn from these changes and devise an optimal negotiation strategy for further engagement with customers or vendors.
+
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.
 +
<div class="image-green-border">[[File:7.14 release note 12.png|720px|7.14 release note 12.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
<span style="color:#008000;">'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''</span>
  
Contract owners can now:&nbsp;
+
In ICI, users capture additional details for clauses and templates in the extended attributes.
  
*Identify 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;
+
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.
*Visualize how the attribute values are changed over a period of time.&nbsp;  
+
<div class="image-green-border">[[File:7.14 release note 13.png|720px|7.14 release note 13.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">'''<span style="color:#008000;">664488 – Ability to take deviation workflow actions from Icertis Experience for Word</span>'''</div>
*Visualize how the clauses and their languages have changed over a period of time.&nbsp;  
+
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.
*Visualize how the statuses of agreements have changed over a period of time.&nbsp;
+
  
 +
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.
 +
<div class="image-green-border">[[File:7.14 release note 14.png|720px|7.14 release note 14.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.14 release note 15.png|720px|7.14 release note 15.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''</span></div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.14 release note 16.png|720px|7.14 release note 16.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''</span></div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.</div>
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''575397 – Improved discovery based on existing customer data'''</span>
+
== Enhancements to Artificial Intelligence Applications in ICI ==
  
ICM’s existing discovery model discovers 15 attributes and more than 40 clauses from MSA or NDA type agreement documents.&nbsp;
+
<span style="color:#008000;">'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''</span>
  
With this release, the process of discovering attributes and clauses is improved for better accuracy by training the in-built discovery model with wide variety of agreements. ICM discovery model now discovers out-of-the-box attributes from SOW type of agreements.&nbsp;
+
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.
  
The existing ObligationAI approach, which was model based, is now replaced by AI and Rule-based approach to discover obligations more accurately.
+
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.
  
Contract negotiators can now:&nbsp;
+
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.
  
*Identify clauses and attributes from multiple MSA, NDA, IT MSA, SOW contract types more accurately and automatically using DiscoverAI and NegotiateAI apps.&nbsp;
+
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.
*Identify obligations from MSA, NDA and SOW contract types more accurately and automatically with ObligationAI.  
+
<div class="image-green-border">[[File:7.14 release note 17.png|720px|7.14 release note 17.png]]</div>
*Select a discovery model specific to contract types to discover attributes and clauses with better accuracy as compared to other models.  
+
Negotiators can now:
  
<br/> <span style="color:#008000;">'''575399 – UX revamp to display discovered attributes and original document side-by-side'''</span>
+
*Define the structure and setup the playbook by configuring a masterdata in ICI.
 +
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range.
 +
*Use artificial intelligence to identify and highlight the playbook exceptions in the document.
 +
*Review all discovered exceptions that are listed down on the page and take corrective actions as required.
 +
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores.
 +
*Review the version-wise cumulative risk using a risk report.
 +
<div class="image-green-border">[[File:7.14 release note 18.png|720px|7.14 release note 18.png]]</div>  
 +
By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.
  
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.
+
<br/> <span style="color:#008000;">'''575450 – Supporting clause hierarchy in .docx agreements'''</span>
  
With this release, when contract negotiators trigger the discovery process, they can view the progress of AI discovery on the agreement Details page. They will be able to view:
+
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.
  
*The progress of all four discovery processes.  
+
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;
*The percentage of discovery process completed for each of discovery process and the overall discovery process.  
+
*The approximate time it would take to complete the individual discovery process and the overall discovery process.  
+
  
Contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, etc. are displayed along with the agreement document. An option is now available to launch side-by-side view of the document along with the discovered entities. Using this option, users can view different sections for discovered clauses, attributes, tables and obligations.&nbsp;
+
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.
 +
<div class="image-green-border">[[File:7.14 release note 19.png|720px|7.14 release note 19.png]]</div> <div class="image-green-border"><br/> '''Note''':&nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&nbsp;</div>
 +
&nbsp;
  
Contract negotiators also have an option to search within the agreement document. The results are highlighted to the user and a count is displayed. Users can also save any changes made in the individual discovery sections.
+
'''<span style="color:#008000;">663666 – Enhancing inbuilt discovery model to include additional attributes&nbsp;</span>'''
  
&nbsp;
+
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&nbsp;
  
<span style="color:#008000;">'''575455 Ability to process multiple documents simultaneously during the discovery process'''</span>
+
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;
  
Previously, upon receiving multiple requests, the AI discovery model added them in a queue form and processed each document individually. With this release, the discovery performance has been enhanced such that multiple documents can be processed simultaneously and within lesser time.
+
<span style="color:#008000;">'''575466 – Support for additional languages in AI apps&nbsp;'''</span>
  
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.
+
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&nbsp;
  
The duration for a document discovery to be completed depends on the number of pages in a document. For example, discovery process for a .docx file with 10 pages and 1 table will take 120 seconds to complete; whereas one with 500 pages and 15 tables will take 1800 seconds.
+
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.
  
&nbsp;
+
With this release:
  
<span style="color:#008000;">'''602198 – Support for user created attributes in NLP search'''</span>
+
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration.
 
+
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document.  
Previously, the ICM AI enabled mode of searching allowed users to search agreements 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 “contract value above 20000 USD”, “contract value below 20000 USD”, “contract value between 20000 USD and 2000000 USD” and so on, can be entered to search contracts of a certain value.<br/> &nbsp;
+
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI.
 +
*While discovering or matching the clause from clause library, document language is taken into consideration.
 +
*The additional languages are supported while discovering similar clauses.  
  
 
== Enhancements to Reports ==
 
== Enhancements to Reports ==
  
<span style="color:#008000;">'''570314 All core SSRS reports to only include contract types classified as Contracting'''</span>
+
<span style="color:#008000;">'''514594 Capability of time zone in reports'''</span>
  
ICM offers the functionality to classify Business Type/ Contracting agreement type at contract type level. With this release, core reports will be limited to Contracting business application type.
+
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.
 +
<div class="image-green-border">With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.<br/> &nbsp;</div>
 +
<span style="color:#008000;">'''514609 – Introducing the Clause Summary Report'''</span>
  
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.
+
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;
  
This is applicable to the following reports:
+
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 Clause Content Report&nbsp;
+
*Agreement Deviation Report
+
*Agreements Pending Approval Report
+
*Agreements Pending Execution Report
+
*Average Agreement Turn Around Time Report
+
*Clauses Pending Approval Report
+
*Expiring Agreements Report
+
*Templates Pending Approval Report
+
*Cycle Time Report&nbsp;
+
*Detailed Report&nbsp;
+
*Attribute Value Report&nbsp;
+
*Template Clause Report&nbsp;
+
*Clause Profiling Report&nbsp;
+
*Clause Deviations Report
+
*Expired Agreements Report&nbsp;
+
*Approved Requests Waiting For Contract Creation Report
+
*Signature Type Report&nbsp;
+
*CLM Activity Report&nbsp;
+
*Clause Insights Report
+
*Deviation Insights Report
+
 
+
<br/> <span style="color:#008000;">'''606134 – All Power BI Reports to only include contract types classified as Contracting'''</span>
+
 
+
Users with access to Power BI dashboards will now only see data of agreements with business application type as Contracting while accessing the Business Summary, Legal Summary and Legal Details reports.
+
 
+
Since the Custom report is common to sourcing and contracting, having a filter which is configurable makes the experience more user-friendly than only restricting the create report for contracting use cases only.
+
 
+
&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;
+
 
+
With this release, users have the option for 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 ICM offering to let customers create and view custom reports. Users will now have OM 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.
+
 
+
<br/> <span style="color:#008000;">'''657965 – Support for Service Principal Authentication method for Power BI'''</span>
+
 
+
ICM 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;">'''573000 – Sub-role included in Detailed and User Profiling Reports'''</span>
+
 
+
ICM 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 Detailed Report, User Profiling Report and Agreements Pending Approval Report have now been modified to display the Approver sub-roles such as Contract Admin, Legal Approver and others.
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''573621 - Enhancement to reports processing error message'''</span>
+
 
+
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 persist kindly contact customer support team.''
+
 
+
&nbsp;
+
 
+
<span style="color:#008000;">'''601540 - Unavailability of Template Clause Report as Dashboard KPI'''</span>
+
 
+
With this release, the Template Clause Report has been deprecated from the Dashboard KPIs. However, it will still be accessible from the Reports tile.
+
 
+
&nbsp;
+
  
 +
This default report is accessible from the Admin category of reports and its access is based on Security Groups.
 +
<div class="image-green-border">[[File:7.14 release note 20.png|720px|7.14 release note 20.png]]<br/> &nbsp;</div>
 
== Integrations ==
 
== Integrations ==
  
<span style="color:#008000;">'''541825 Integration with the new eSignature platform &nbsp;&nbsp;'''</span>
+
<span style="color:#008000;">'''554867 Support for ICI dashboard in Icertis Experience for Salesforce'''</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;
+
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;
  
Contract administrators can track the status of the agreements sent for signature within ICM. They can also recall the agreement sent for signature, if it was not signed by all parties.
+
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;
  
<br/> <span style="color:#008000;">'''569172 – Enabling Electronic seal tag for signing agreement documents &nbsp;&nbsp;'''</span>
+
Salesforce users can now:&nbsp;
  
Previously, users were able to sign agreements based on signature tags present in the agreement templates. &nbsp;&nbsp;
+
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&nbsp;
 +
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&nbsp;  
 +
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab.
 +
<div class="image-green-border">[[File:7.14 release note 21.png|720px|7.14 release note 21.png]]</div> <div class="image-green-border">&nbsp;</div>
 +
<span style="color:#008000;">'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''</span>
  
With this release, ICM 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.
+
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&nbsp;
  
&nbsp;
+
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&nbsp;
  
<span style="color:#008000;">'''579067 – Ability to support additional electronic signature platforms'''</span>
+
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.<br/> <br/> '''Note''':&nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.
 
+
Just like support has been extended to Namirial eSignAnyWhere in addition to DocuSign and Adobe Sign for electronic signatures, ICM has enhanced adaptability by making it possible to implement and integrate any other electronic signature provider as well based on customer requirements.
+
  
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''572516 SAP S/4 Supplier masterdata integration &nbsp;'''</span>
+
<span style="color:#008000;">'''635822 Support for pre- and post-processing in Generic Integration Framework'''</span>
  
The Icertis Experience for SAP S/4 HANA allows users to search, display and select S/4 HANA masterdata required for completing the contracting process within ICM.
+
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;
  
The ICM Experience for S/4 HANA adapter:
+
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:
  
*Allows periodic data sync between S/4 HANA masterdata and ICM masterdata tables.  
+
*Pre-process inbound data through file-based integrations.  
*Can be configured such that ICM Admin ca configure the data sync jobs and the related entity mappings.
+
*Pre-process inbound and outbound data through ASB-based integrations.  
*Is agnostic to masterdata entity i.e. it is generic enough to support any masterdata that the customer would like to sync from S/4 HANA into ICM to complete contracting business process.&nbsp;
+
  
Some key use cases that customers should be able to configure the adapter to include:
+
ICI administrators will now be able to:&nbsp;
  
*Supplier master data from S/4 HANA to ICM.  
+
*Enable or disable the hook as part of file-based and ASB integration.
*Material/Items master data from S/4 HANA to ICM.  
+
*Pass parameters to the hook for executing a custom logic.  
*Payment master (Terms, Types) from S/4 HANA to ICM.  
+
*Enable or disable the hook at file or record level.
 +
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook.  
 +
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record. 
 +
*Execute any custom logic in the system for a file or record when a hook is configured.
 +
*Complete GIF process even when custom logic encounters any error while processing a record or file.  
  
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''572517 – SAP S/4 HANA masterdata lookup&nbsp;'''</span>
+
<span style="color:#008000;">'''635823&nbsp;– Support for defining folder structure in Generic Integration Framework'''</span>
  
With this release, ICM and ICM business applications (Sourcing and Obligation Management) have been integrated with SAP S/4 HANA to render masterdata lookup from SAP S/4 HANA.
+
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.
  
<br/>  <br/> <span style="color:#008000;">'''573373 – Generic integration framework to support contract requests via ASB'''</span>
+
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.
  
Previously, ICM supported a generic ASB adapter for inbound and outbound integration for Agreements. With this release, support is provided for creating contract requests for agreements. Users will now be able to create and update Contract Requests in ICM using an external application.
+
With this release, users have:&nbsp;
  
&nbsp;
+
*Support for single or multiple folders in the folder structure.
 
+
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format).  
<span style="color:#008000;">'''573377 – Generic integration framework to support associations via ASB'''</span>
+
*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.  
Previously, ICM supported a generic ASB adapter for inbound and outbound integration only for agreements. With this release, support is provided for creating contract requests for the agreements. Users will now be able to create and update contract requests in ICM using an external application. &nbsp;
+
 
+
The ASB adapter will pick the JSON payload from the message queue and create associations to an existing agreement or RFx record in ICM. Users will thus be able to manage purchase requisitions, purchase orders, sourcing events and similar tasks by sending associated data. &nbsp;
+
  
 
&nbsp;
 
&nbsp;
  
<span style="color:#008000;">'''573379 – Generic integration framework to support amendments via ASB'''</span>
+
== Partner Enablement ==
  
Contract amendments are an integral part of business flow and the support for amendment integration is critical for businesses. With this release, the generic integrations ASB adapter will be able to update amendments to an agreement on the created, updated, approved and executed actions.&nbsp;
+
<span style="color:#008000;">'''703386 – Icertis Software Development Kit for Partner Enablement'''</span>
  
&nbsp;
+
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;
  
<span style="color:#008000;">'''594454 – Additional connector support for JSON file format'''</span>
+
As part of our continuous efforts to support our partners, we have created the following documents in this release:
  
Previously CSV files were supported for masterdata upload using ASB and SFTP, while text based files were supported for uploads using SFTP.&nbsp;
+
*'''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.
  
With this release, the file based integration will additionally support JSON file format, while also supporting blob connectors.
+
*'''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.  
  
&nbsp;
+
*'''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;'''
  
<span style="color:#008000;">'''554864/554868 – Support for request review and upload actions in Salesforce grid'''</span>
+
*'''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.  
 
+
Previously, ICM 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. &nbsp;The action buttons displayed on the user interface are based on the privileges assigned to the user via role action mapping in ICM . 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;
 
&nbsp;
  
<span style="color:#008000;">'''537774 – Ability to create contracts based on Opportunity or Quote'''</span>
+
== Technical Requirements for Release 7.14 ==
  
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.&nbsp;
+
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.
  
With this release, the contract creation process has been automated based on opportunity or quote status, will increase the productivity of sales users.<br/> Sales Admin users can now:
+
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]
  
*Configure the opportunity or quote status which can automatically trigger the contract creation.  
+
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]
*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 manual contract creation by creating a task for the opportunity (for which a contract needs to be created).&nbsp;
+
**If there is a task to manually create a contract, Sales 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 i.e. follow the same steps as above.
+
**For auto creation of contracts, the ICM for Salesforce will determine the dependencies for the contract. For example, if the opportunity is for an extension, the existing master agreement for the account will be identified and an appropriate contract type such as an order form will be selected and associated with it. 
+
  
Additionally, Salesforce users will receive a Task and/or Chatter notification whenever a contract is automatically created.
+
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]
  
&nbsp;
+
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]
  
<span style="color:#008000;">'''580066 – Ability to redirect emails when testing Adobe Sign eSignature on other instances'''</span>
+
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]
 
+
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. However, when ICM is set up on non-production environments, these emails need to be redirected (or overridden) 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.
+
 
+
<br/>  <br/> <span style="color:#008000;">'''574458 – ICM task integration to Salesforce tasks'''</span>
+
 
+
Previously, Salesforce users could manage all internal and external tasks within Salesforce itself. However, they could not manage ICM tasks from within Salesforce. &nbsp;
+
 
+
With this release, ICM users can now:&nbsp;
+
 
+
*Manage ICM tasks from within Salesforce. The tasks created in ICM are pushed to Salesforce that allows to view the summary of the tasks with the attributes such as Task Name, Status, Priority, Due Date. &nbsp;
+
*View the task details after it is available in Salesforce.&nbsp;
+
*Configure ICM task integration with Salesforce. &nbsp;
+
  
 
&nbsp;
 
&nbsp;
 
== ICM Platform Tools ==
 
 
<span style="color:#008000;">'''588361 – PToP support for ICM'''</span>
 
 
The 7.11 release, some enhancements were made to the Promote To Production (PToP) tool such as Vulnerability and Penetration Testing (VAPT) fixes, testing open bugs in PToP engine, some validations in the PToP engine, and an improved user interface to provide support to PToP and DevOps teams.
 
 
With this release, changes have been made in ICM to support the PToP engine. This functionality, provided to administrators, can promote ICM configurations/modifications that are made to ICM 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;
 
&nbsp;
  
<span style="color:#008000;">'''561717 – PToP support for Daimler'''</span>
+
'''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;|
 
+
With this release, changes have been made in ICM to support the PToP engine. This functionality, provided to Administrators, can promote ICM configurations/modifications that are made to ICM configurations in pre-production environments to production environments.
+
 
+
This functionality:
+
 
+
*Provides AWS Support for File Copy in Auto PToP 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 PToP starts which is helpful for complex PToP.
+
*Gives a validation error if the same entity is added multiple times, so that PToP does not fail.
+
*Supports saved searches.
+
*Supports User groups, Security Groups and Org Groups (which is done through manual PToP in Daimler).
+
*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 PToP task using a small tool in Daimler to validate names of all clauses and templates, thus helping to resolve issues in naming CSV files, naming in ICM, 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 ICM version before 7.12 need to upgrade to use this feature.<br/> &nbsp;
+
 
+
== Technical Requirements for Release 7.12 ==
+
 
+
The Icertis Contract Management base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below:
+
 
+
[[File:7.11 Release Notes Technical Requirements 001.png|720px|7.11 Release Notes Technical Requirements 001.png]]
+
 
+
[[File:7.11 Release Notes Technical Requirements 2.png|720px|7.11 Release Notes Technical Requirements 2.png]]
+
 
+
[[File:7.11 Release Notes Technical Requirements 03.png|720px|7.11 Release Notes Technical Requirements 03.png]]
+
 
+
[[File:7.11 Release Notes Technical Requirements 4.png|720px|7.11 Release Notes Technical Requirements 4.png]]<br/> [[File:7.11 Release Notes Technical Requirements 05.png|720px|7.11 Release Notes Technical Requirements 05.png]]
+
 
+
&nbsp;
+
 
+
== Known Issues for Release 7.12 ==
+
 
+
&nbsp;
+

Latest revision as of 12:24, 1 October 2020

ICI Release Notes - Release 7.14

Overview of Release 7.14

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

The key enhancements of this release include:

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

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

 

ICI Application Enhancements

659853 – Upfront chevron view of agreement journey

In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination. 

Users can view the current status of an agreement on the Agreement Index or Details page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs. 

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

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

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

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

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

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

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

Note

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

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

The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract. 

This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.
 

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

With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.

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

Users can: 

  • Click on the left navigation link from an agreement contract type that will render the smart link result in grid. 
  • Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results.
7.14 release note 2.png
 
Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.
 
The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.

For example, consider entities related in multi-level hierarchy as Agreement > Obligations > Fulfillments. Earlier users had to navigate through obligations in order to access the child fulfillments.
 
Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.

7.14 release note 3.png

 

584439 – Introducing the Contract Manager role for agreements 

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

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

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

With this release: 

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

 

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

Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it. 

With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - Allow Peer Creation Wizard, Allow Multiple Instances and Allow Two-Way Linkage.

 

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

Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.

With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability. 

7.14 release note 6.png

For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.

7.14 release note 7.png

This is applicable to the following associations: 

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

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

 

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

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

With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way. 

Users can now: 

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

 

583186 – Ability to add amendment on expired agreement

Currently in ICI, users have to revive the agreement from Expired to Executed state by resetting its expiry date and then add amendments to it.

With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment. 

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

7.14 release note 8.png

593928 – Ability to configure sender email ID for automated emails

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

With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record. 

Administrators can now:

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

593938 – Time Zone support for date-dependent automated processes

In ICI, there are scheduled jobs that perform certain actions on agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.

To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.

With this release:

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

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

7.14 release note 10.png
 

512930 – Triggering service bus events for all actions

For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI. 

With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated. 

The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.
 

545126 – Availability of business status value in ICI event messages

For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.

With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.

Mobile App Updates

660965 – Refresh agreement list on approval

Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically. 

In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.

7.14 release note 11.png
 

ICI API Enhancements 

607867 – ICI API 2.0 Implementation

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

Enhancements include:

  • Addition of Masterdata APIs 
    • Users can now update the masterdata instance
    • UserName field is returned in Get Team API as part of the response.
  • Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well.

Enhancements to ICI Add-ins 

714872 – Improved document usability

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

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

With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.

7.14 release note 4.png
 

With this release:

  • All the content controls are put together in a single paragraph on any line with valid content.
  • One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause.
  • An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules.
  • If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph. 
  • Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document.
7.14 release note 5.png
 

Note

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

 

660390 – Ability to show more clauses per group

With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.

This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.

7.14 release note 12.png
 

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

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

These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.

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

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

Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.

7.14 release note 14.png
 
7.14 release note 15.png
 
 
660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word
 
Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.
 
Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.
 
This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.
 
7.14 release note 16.png
 
 
667815 – Ability to upload email as association of an agreement using Outlook Add-in
 
Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in. 
 
With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.
 
Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.

 

Enhancements to Artificial Intelligence Applications in ICI

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

With this release, ICI is introducing a legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.

Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.

Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.

The exceptions are identified by the NegotiateAI app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.

7.14 release note 17.png

Negotiators can now:

  • Define the structure and setup the playbook by configuring a masterdata in ICI.
  • Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range.
  • Use artificial intelligence to identify and highlight the playbook exceptions in the document.
  • Review all discovered exceptions that are listed down on the page and take corrective actions as required.
  • Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores.
  • Review the version-wise cumulative risk using a risk report.
7.14 release note 18.png

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


575450 – Supporting clause hierarchy in .docx agreements

Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.

With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on. 

Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.

7.14 release note 19.png

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

 

663666 – Enhancing inbuilt discovery model to include additional attributes 

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

With this release, identification of the following 9 additional attributes has been introduced - City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone.
 

575466 – Support for additional languages in AI apps 

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

In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.

With this release:

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

Enhancements to Reports

514594 – Capability of time zone in reports

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

With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.
 
The Time Zone parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.
 

514609 – Introducing the Clause Summary Report

Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes. 

With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity. 

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

7.14 release note 20.png
 

Integrations

554867 – Support for ICI dashboard in Icertis Experience for Salesforce

In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks. 

With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI. 

Salesforce users can now: 

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

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

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

With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday. 

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

Note: Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.

 

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

Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa. 

With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:

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

ICI administrators will now be able to: 

  • Enable or disable the hook as part of file-based and ASB integration.
  • Pass parameters to the hook for executing a custom logic.
  • Enable or disable the hook at file or record level.
    • When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook.
    • When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.
  • Execute any custom logic in the system for a file or record when a hook is configured.
  • Complete GIF process even when custom logic encounters any error while processing a record or file.

 

635823 – Support for defining folder structure in Generic Integration Framework

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

Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.

With this release, users have: 

  • Support for single or multiple folders in the folder structure.
  • A folder and file naming convention which is flexible and configurable via masterdata (in JSON format).
  • Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change.
  • A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used.

 

Partner Enablement

703386 – Icertis Software Development Kit for Partner Enablement

Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide them with the resources and tools that they need while implementing ICI. 

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

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

 

Technical Requirements for Release 7.14

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

7.14 release note 22.png

7.14 release note 23.png

7.14 release note 24.png

7.14 release note 25.png

7.14 release note 26.png

 

 

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