You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page:
Return to Release Notes.
The 7.9 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience and intuitiveness by continually improving the ICM user interface.
The key enhancements of this release include:
</ul>
These Release Notes provide an overview of enhancements to ICM and the ICM Experience for Integrations. Refer to the detailed Wiki documentation for explanation and capabilities of these and all other ICM features and functionalities.
420230 – Extend Contract Type definition to be able to describe the Application Type
ICM offers the ability to determine the Application Type (Contracting, Sourcing, Proposal, Obligation Management, and Supplier Lifecycle Management) when creating a Contract Type. This is possible with the inclusion of two new Choice type Attributes, Business Application Type and Business Application Category at the Contract Type level. This feature helps effortlessly drive Business Application on the ICM platform. These Attributes are applicable for Agreements and Associated Document Contract Types, after the Business Application is enabled through a technical configuration. The access privileges for Business Applications such as Sourcing, are driven through Security Groups.
452265 – Ability to compare any 2 versions of the document
Previously, users could only see the comparison between the last and the current version of the Agreement. This functionality has now been enhanced so that the user can compare any two of the available versions of the Agreement as required.
408652 – Displaying an Announcement Banner
ICM has now improved user experience by providing the capability of displaying a scrolling banner message to inform users of a scheduled event or an announcement. For example, you can inform users that a maintenance activity is scheduled in 24 hours. A banner will scroll at the top of the ICM window alerting the users of the downtime, so that they can plan their work accordingly. This can be achieved through Application Settings by toggling the Show announcement banner field to Yes and entering the message to be displayed in the Announcement message box.
456074/439569/439668/467828 – Enhancements to Bulk Upload
ICM has now enhanced usability by making the following enhancements to the Bulk Upload functionality so that you can:
382235 – Power BI Integration with ICM
With this release, in effort to improve Power BI usability, some changes have been made and some additional functionalities have been added.
288372 – Inclusion of Clauses and Clause properties in Search facets
ICM has further enhanced the search capabilities by allowing searches on Agreements, Amendments, and Advanced Search based on Clause usage. This allows users to prioritize the Agreements they plan to work based on Clause usage, thus being able to tackle high-risk Agreements first and mitigating risks.
You can now search and filter Agreements using the following Clause categories: Clause Group, Clause Language, Clause Name, Is Alternate Clause, Is Dependent Clause, Is Deviated, Is Editable, Is Mandatory, Perform Deviation Analysis, Primary Clause, and Clause Code.
Note: Clause Description, Clause Text, Linked Primary Clauses, Clause Status, Linked Primary Template Clause, and search based on Clause text area are also not supported in Clause categories.
397346 – Ability to create Rule with Has A Value condition
With this release, the Has A Value condition has been enhanced to include all Data Types and system defined Attributes such that Rules can be set up for an Attribute having any value.
For example, you want to set up a Rule so that an Approver John Doe should approve the Contract if a discount is applicable to it, irrespective of the value of the discount. Then, user can add a Rule using the Has A Value condition, such that John Doe is added as an Approver, if the discount has a value of 5%, 10% or whatever value is desired.
Earlier this condition supported only a limited set of user defined and system Attributes, but now it has been enhanced to support all Data Types and additional system Attributes. It is now also available for the following Contract Type Attributes and Data Types: Contract Type Lookup, Contract Type Multi-Select Lookup, Choice, Multi-Select Choice, Number, Currency, Percentage, Date, DateTime, and URL. In addition, it is also available for system Attributes such as Template Name and Type Of Paper.
408653 – Enhancing Rules to support Power Set conditions for multi-select data
Currently, ICM supports only the Contains/Does Not Contain conditions for multi-select data. The Contains operator does not check whether all selected values of the Attribute are a subset of expected values, but only checks for any one of them. Thus, when the Rules were evaluated, even the Templates, Approvers, Clauses, etc. that are not required get executed.
To avoid this confusion, Rules have been further augmented so that the user can configure conditions for power sets (i.e. cases where the user wants a Rule to be executed only if the entity field contains a subset of the configured values). This is achieved by introducing the new operator, Subset of, which is applicable to only multi-select lookup that supports evaluation of string, number, user, percentage and email data types only.
Let’s consider the example of a Template Selection Rule to select multiple products using the Subset of operator. Suppose, the Rule is defined such that Template 1 should be selected if the selection is a subset of Products A, B, C, then:
419834 –Localization of Masterdata Attributes to support bilingual Agreements/Templates
Earlier, ICM did not directly support bilingual Agreements and Templates. As a result, users had to tag multiple Attributes in a Template for different languages thereby ending up duplicating multiple attributes in a Contract Type.
To simplify this process and facilitate bilingual templates, ICM has introduced the ability to tag the same Masterdata localized Attribute multiple times for different languages which can be tagged in a bilingual Template. This allows the user to manage the same Attribute with a different language in the same Template or Agreement. The support for bilingual templates allows the user to specify the second language for the Template and also be able to tag localized Attributes in the Template with the second language.
Note:
386571 – Enhancements in AI Apps
The Negotiate AI, Obligation AI and Visualize AI app have been merged to the ICM platform and these apps have been enhanced to improve their usability.
Note:These apps are available in ICM through a technical configuration. They work on Microsoft Office 2016 for Windows version 16.0.4390.1000 or later, and Office .JS installed.
334171 – Enhancements in Email Outlook Plugin (.JS version)
With this release, a new .JS version of the ICM Outlook Plugin has been introduced. The overall turnaround time for the author is reduced as he no longer needs to download the documents received over email to the local machine, then switch applications and log in to ICM, search the Agreement and then upload the documents.
The provisioned user can now:
The configuration of the Outlook Add-in is driven by the Masterdata, whereas the list of Agreements and their details are configured by the Saved Searches. You can configure multiple saved searches. This is available for MS Outlook online as well as the Desktop client.
397327 – Ability to drive dependency of Template Variables on Agreement Attributes
With this release, ICM has extended support to Template Variables being conditional to the value of the Attributes that are part of a Contract Type. The user can track the dependency between the Contract Type Attribute and Template Variable as well as eliminate the creation of duplicate Attributes between them.
This can be achieved by any user with Manage access on Template Management tile by enabling the Is Conditional flag for each Template Variable when creating or editing a Template. When Is Conditional is On, a user is able to set a dependent condition on the Template Variable by using Depends on Contract Type Attribute flag On and its related Depends On Attribute drop-down and Depends On Value field.
The following conditions decide the dependency between the Template Variable and Contract Type Attribute:
For each selected Attribute from Depends On Attribute drop-down list, the user can then enter the Depends On Value that will drive the dependency.
384321 – Deviation Tracking when Association is tagged as a Table
Previously, modifications made to Associations or Saved Search (such as adding or removing rows/columns or changing the values in individual cells) that were tagged as a table in a Template did not reflect in the new version of the Agreement document.
With this release, redlining of these changes will be visible on the Versions tab of the Agreement Document, thus allowing the contract negotiator to make informed decisions accordingly.
Note: Deviation tracking and reverse sync of the changed table data to the respective Association instances is not supported. ICM Scribe supports this capability unlike ICM .Net Add-in but provides limited information. Table comparison is only shown when cell values get changed not when empty cells get added or removed.
275838 – All Reports should display Date and Time in Time Zone set by user in User Preferences
With this release, all reports now display the Date and Time in the Time Zone set by the user in User Preferences.
Previously, all date related columns and parameters in all ICM reports were displayed in the UTC Time Zone in the mm/dd/yyyy format. This led to a discrepancy with the dates displayed in ICM which were as per the locale settings in the user preferences. With this release, all reports will also display the Date and Time as per the Time Zone set by the user in the user preferences.
However, the following points need to be noted:
385409 – New Reports added to KPIs
Earlier, only few reports were available on the Dashboard as KPI. Now, the user can also add the following reports as KPI tiles (through Security Groups) for user accessibility:
For example, the Signature Type Report KPI depicts the percentage of electronic signature in ICM. If the number of electronic signatures is 6 and the number of manual signatures is 83, then the KPI is calculated as 6/83+6 = 6/89 (total number of agreements). Therefore, the percentage of electronic signatures is 6 (which is the number displayed on the KPI tile on the Dashboard).
The reports that were already present as KPIs on the Dashboard included the Agreement Deviation Report, Agreements Pending Approval Report, Agreements Pending Execution Report, Average Agreement Turn Around Time Report, Clauses Pending Approval Report, Expiring Agreements Report, and theTemplates Pending Approval Report.
370460 – ICM Integration with MS Teams
By integrating the ICM platform with MS Teams, users can collaborate for contract authoring, negotiations, etc. This not only provides a better, seamless user experience, but also helps to discuss ideas or exchange files, and in turn significantly improve the cycle time. You can ping, chat with members within or outside the Agreement Team. The chat will be saved in the MS Teams History.
Through this integration, we support:
348588 – Configuring Field Set from Salesforce to ICM using Rest API
With this release, a new field called Field Set Name has been introduced that can be configured using the Configuration page which is accessible through the managed application available in Salesforce AppExchange. When the integration is triggered from Salesforce, the Adapter can read the metadata and send only the Attributes defined for the entity Field Set. If the Field Set is not defined, the Adapter sends all the Attributes for that entity.
Note: It is necessary to create a new Field Set for every Salesforce entity. The field set determines the fields that the user can edit in a particular Salesforce entity instead of having to select each field individually. For example, a Field Set created for an Opportunity can have fields such as Opportunity Name, Opportunity ID, etc.
397315 – Create mapping between Template Variable for Agreements and SFDC fields
The ICM Salesforce Adapter allows mapping of Salesforce entities and their Attributes to be integrated with ICM for data flow from Salesforce to ICM (Forward Sync) as well as ICM to Salesforce (Reverse Sync). This was previously done using Client App Entity Mapping on the Masterdata Configuration page which allows mapping the ICM Attributes from Contract Types, but not from Agreement Templates.
With this release, Administrators can now use Attributes defined at Template level to store critical external data as part of the Agreement and sync with Salesforce, thus avoiding data duplication and redundancy in the process.
384529 – Executed PDF from ICM to Workday
Customers using Workday ERP application to manage their procure-to-pay process want to have end-to-end integration to Icertis Contract Management (ICM) platform for managing their procurement process.
Icertis platform already supports integration to Workday Financials and HCM via an Adapter. As part of this integration, contracts authored in the ICM platform can be sent to Workday via the Adapter and attached to Workday contracts in .docx format.
Now, with the help of Event based configuration in the Adapter, it is possible to send the Agreement document in .PDF or .docx format to Workday for a specific event.
344436 – Support for Print, sign and upload (Wet Signed Copy) and sync back in ICM
Adobe Sign provides users the capability of signing documents manually using Print, sign and upload option. However, earlier when the Agreement Document was Wet signed and uploaded, it did not get synced back to ICM, and the Agreement would get blocked in that state. With this release, ICM supports syncing back the signed Agreement document and changed status, so that the user can proceed with the workflow as expected.
Note:
The Icertis Contract Management base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available in all the environments, and specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in one of the groups: Users, User.
You can view and copy the source of this page:
Return to Release Notes.