Repository Enhancements
"Select All” Option Available in Reports
We’ve introduced a “Select All” feature in Reports. This new option allows users to select all contracts matching a search term with just one click and is available on fields that are type “Select Box”. When “Select All” is chosen, further filter selection becomes disabled to ensure data consistency across the desired set.
Export Limit Increased for CSV Reports
The maximum number of exportable rows for CSV format has been increased from 1 million to 1.5 million. This enhancement supports larger dataset export in CSV format, enabling more comprehensive data analysis of your report.
Entities Added to Contracted Products View
We’ve added “Party” and “Other Party” columns to the Contracted Products View. When you add them as additional columns, this update allows users to view products by contracting entity, providing a comprehensive overview of all contracts - including those from acquired companies within the same account. This update is available in both the Pramata Platform and CRM.
Expanded Integration Resources in Pramata's Integrations Hub
We're excited to introduce new integration resources in Pramata's Integrations Hub, enhancing your ability to connect Pramata with essential external applications and services. This release includes new tiles for:
- DocuSign
- Salesforce
- Microsoft Dynamics 365
Each tile provides quick access to detailed installation and setup guides, empowering users to efficiently configure integrations between Pramata and these popular platforms.
Pre-Signature Enhancements
Contract Request Reassignment: Change Requestor for Open Requests
We're excited to introduce a new capability that allows Admin users and request Assignees to change the Requestor for open contract requests. This feature streamlines workflow management, especially when handling requests from employees who have left the company.
Key Highlights
- Edit the “Submitted by” field in the right panel of the Request details view to reassign requests to any active user with contract request access.
- When a Requester is changed / updated, the change is tracked in Audit Trails.
- Email notifications sent to the new Requestor.
Contract Request APIs: Enhancing Cross-System Visibility
We're introducing new Contract Request APIs to improve visibility and integration of contract workflow information across your systems. These APIs enable real-time access to contract request details, allowing you to seamlessly incorporate this data into other platforms, such as your CRM for more accurate pipeline reporting.
The Contract Request APIs consist of two main components:
- Request API - Retrieves contract request numbers based on specified 'submitted on date' range filters.
-
Request Details API - Provides information about a specific contract request, including:
- Submitted By: who submitted a request
- Request Type: specific values vary based on each organization but typical examples are “Sales Agreements”, “NDAs”, etc.
- Description: typically captures a descriptive statement about what the request is for
- Account: this is the name of the account the request is related to
- Submitted On Date: date when request was initially submitted
- Assignee: person assigned to work on the request
- Status: the current status of the request inside the workflow. Values vary by organization.
- Pramata number: in case a request results in a signed document, this captures the document identifier (Pramata Number) for the signed contract that is related to the request (Contract Request #).
These APIs allow your IT teams to build integrations that do things like track the progress of contract requests, identify who's working on them, and understand their current status—all from within your existing systems in real-time.
Learn more on APIs here.
Enhanced Request Navigation
The tables within the Queue menu now features clickable Request Numbers, opening detailed information in new tabs while preserving the original list view. This functionality extends to exports, where a "View Contract Request" hyperlink allows direct access to the contract request details page.
Option to Remove 'Waiting for Signature' Status
In response to user feedback, we've added the ability to delete the 'Waiting for Signature' status from workflows, offering more flexibility in managing request statuses.
This status can now be removed, provided that:
- It is not set as the Default Status for Auto-Generated Contracts
- There are no open requests associated with it
AI Design Studio
AI Design Studio UI Enhancements
The AI Design Studio module has undergone significant updates to improve user experience and functionality.
Key Highlights
- The “Generative AI” module is now renamed to “AI Design Studio”
- Audit Logs and LLM Configuration have now moved from “Experiences” to a new “Advanced” submenu
- New submenu added: Provision Models (more on that below)
Introducing New ‘Provision Models’ Builder
We're excited to introduce a brand new feature called “Provision Models”. This feature allows users to build custom models that define the definitions for the provisions and clauses that they are interested in analyzing. Provision Models will eventually be the foundation for multiple use cases in our platform. For now, they are the foundation for any Playbook development. In order to have a Negotiation Playbook, you will first need to create a Provision Model that can be leveraged in the construction of a Negotiation Playbook.
Playbook Builder Improvements
The Playbook Builder has been revamped with some major updates:
- Users now need to associate a Provision Model to a Playbook during setup. The Provision Model defines the Provisions and Clauses your Playbook will be focused on analyzing.
- Dedicated sections introduced to store Preferred Positions, Fallback Positions, and Restricted Positions. By having dedicated spots to store this vs. keeping it in one generic “Business Context and Negotiation Strategy” section, Playbook Analysis will be much more precise.
MS Word-Add in Enhancements
Party Perspective
We've integrated Party Perspective feature into the Word Add-in. This enhancement automatically identifies parties (Customer or Vendor) for tailored contract analysis.
Key Highlights
- Party Selection: Users can choose from identified parties or add new ones, with selections saved for future sessions.
- Playbook Analysis Refresh: Changing the selected party triggers a new analysis for optimal relevance.
Minimalistic Redlining
Our new minimalistic redlining feature in MS Word is designed to make only the most essential changes to contracts, in line with our playbook recommendations. This approach aims to minimize the number of words edited, keeping alterations as subtle as possible to avoid alarming the other party. By making precise, targeted edits, we maintain the integrity of the original text while achieving the desired contractual outcomes.
Issues Fixed
| Issues | Fix |
| Repository | |
| Analytics: “Unpin from Analytics” icon missing from saved reports in full screen and minimized views, preventing removal from Analytics module. | The issue has been resolved. |
| Analytics: In generated reports where columns with yes/no type answers are added, the values are displaying incorrectly as 0 and 1 instead of Yes and No. | The issue has been resolved. |
| Pre-Signature | |
| Queue > Request Details: Changes made to the field labels from the Settings menu were not reflecting for the old contract requests. | The issue has been resolved. |
| Queue > Request Details > Audit Trails: Changes made to the workflow were not captured in Audit Trails. | The issue has been resolved. |
| Queue > Open Requests: Sorting the Amount column displayed the incorrect order. | The issue has been resolved. |
| Queue > Request Details > Send for Approval: Typed characters would not clear after selecting the approver name in the Approver(s) field. | The issue has been resolved. |
| Queue > Open Request > Edit Form Responses: Workflow deleted request types remain visible in the dropdown menu, leading to errors when selected and submitted. | The issue has been resolved. |
| KPIs/Metrics: Request Type search functionality in Filters is not functioning correctly. | The issue has been resolved. |
| Queue > Open Requests > Approval History tab: Blank screen displayed when no approval history existed for a request. | Added the message "No Approvals Yet" when a contract request has no approval history. |
| Email Notifications for SFDC Users: SFDC users received email notifications with a Contract Request link that incorrectly directed them to the Pramata Platform, even when they lacked access to the Contract Request module in the Pramata Platform |
For users with access to both CRM and Pramata platforms:
|
| AI Design Studio | |
| Gen AI Assist (Reports): IntelliExperience launch fails with unspecified error. |
The issue has been resolved. |