|2678||Agiloft Integration Hub powered by Workato||The new Agiloft Integration Hub makes it easy to connect your KB to over 200 enterprise integrations using
Workato, an integration-enablement platform. With these connections, you can trigger purchase orders when
contracts are signed, send contract data to your billing platform for invoicing, notify your team in Slack or
Microsoft Teams when deals close, and much more.
The Integration Hub includes a Templates folder with recipes specific to Agiloft, and it offers a library of pre-built recipes for popular apps, which makes the process simpler, quicker, and more intuitive. You can also create your own recipes from scratch on the Recipes tab.
After you've set up some integrations in the Hub, you can quickly check their status using the Dashboard tab.
The Integration Hub is an add-on that requires additional licensing. When you've purchased the add-on and set it up, you can access it at Setup > Integration Hub. To learn more about how to set up and use the Integration Hub, see Integration Hub and Workato's own documentation here.
|2687||Connect KBs to Mulesoft with new Agiloft connector||
Easily connect Agiloft with your software ecosystem using the Mulesoft platform, where you can now add the new Agiloft connector. When you're connected to Agiloft in Mulesoft, you can configure your connector to do any or all of the following:
To leverage this new connector, log in to Mulesoft and add the Agiloft connector through Exchange. From there, configure the KB you want to connect to.
If multiple users need to work with the connector on the Mulesoft platform, or if one user needs to connect to multiple KBs, configure a connector for each user-KB combination. Access to KB data is controlled by the permissions attached to the Agiloft credentials you use to configure the Agiloft connector in Mulesoft.
For more information about connectors in Mulesoft, see Mulesoft's Introduction to Anypoint Connectors. For detailed guidance on adding the Agiloft connector and configuring it in Mulesoft, see Mulesoft's documentation about configuring connectors. The connector integrates with Agiloft using REST API calls with the JSON request/response format over an HTTPS connection.
|2680||Sync CPQ with the Salesforce managed package||If you use Configure, Price, Quote (CPQ) with Salesforce, you can now leverage that information when you sync
to Agiloft by including linked product information in contracts, and keeping the product list up to date in both
systems. The new CPQ sync is easy to set up with the existing Salesforce managed package.
With CPQ included in your Agiloft sync, contracts automatically include any linked products when they sync back to Agiloft. Your product lists also stay in sync, so users can create contracts in either system while pulling from the same list of products. If you want to use only one of these features, you can easily disable the other.
Whether you've already installed the Salesforce managed package or you're installing it for the first time, you can access this setting by logging in to Salesforce and using the App Launcher to search for and open Agiloft Configuration. At the bottom of the Field Mapping tab, select Include CPQ and click Upload Mapping. This automatically creates new SF Contract Product and SF Product tables in Agiloft, and creates or updates the necessary sync configurations to connect everything in both systems.
For more information about integrating with Salesforce, see Salesforce Integration.
|2688||New outbound webhook system||The new outbound webhook system was created for use with the Integration Hub, but can also be a useful
alternative method for integrating your KB with other systems and apps. With webhooks, your Agiloft system
can send out notifications when certain events happen, so that external systems can then request updated
information from Agiloft.
For example, you could notify an external system when a new Contract record is created, so that system can then request that contract data from Agiloft. This push-based model requires fewer API requests overall, tends to be simpler to build, and provides real-time updates.
You can create, edit, and delete webhooks in the Setup > Integration > Webhooks Setup menu, which lists all webhooks in your system. You can also create webhooks in Agiloft using the new POST /ewws/webhooks API call. Webhooks can run when a record is created or edited, after any applicable rules have run.
For details about Agiloft webhooks, including how they work and how you can configure them, see Webhooks.
|2679||View and test REST API methods directly in your system||
Explore convenient, interactive documentation of our REST API methods and responses now available using Swagger. The documentation is available directly in your KB, for the most up-to-date and KB-specific information, at Setup > System > View REST Documentation.
The documentation inside your KB showcases REST information using the fields and tables specific to your system. You can even call the API from the documentation to test it out. In addition, the values and parameters included in REST calls can now be formatted in JSON.
|2681||Easily share links to specific records||
You can use the new Copy Link option to easily share a record with coworkers or vendors, or even send it to yourself for quick reference. Open the record you want to share, click the ellipses menu in the top left corner, and click Copy Link. This copies the URL to your clipboard so you can paste it into an email, instant message, notebook, and more.
These links are encrypted for security, and they respect user permissions, so you don't need to worry about them getting forwarded to a third party. If you click a link to a record in a KB you're already working in, the link opens right away so you can get right to work. Otherwise, you're prompted to log in, and then brought directly to view the record. If you need to make changes, simply click Edit.
You can even include a record link using the new deeplink() function, which is available in Formula Help on the Functions tab. For example, you might use it in an approval notification so that you can also include a link to the contract being approved.
Note that this feature requires you have a value set in the Hotlink Server Root URL global variable (Setup > System > Manage Global Variables). This global variable is also used for hotlinks in email templates, so if you use those, it's probably already configured.
|2692||Internal Comments in the Agiloft Word App||
Collaborate on contracts with the rest of your team right in the Agiloft Word app using the new Comments section. These comments make it easy to communicate with your colleagues without leaving comments embedded in the actual Word document, so you can share the Word file with third parties without your comments included. Your comments are stored in your Agiloft KB, rather than the Word file itself.
To deploy this, go to Setup > Integrations > Word Add-in and click Upgrade. This automatically adds the necessary Comments field to your Contract table, and will also update your KB with any other new features of the Word app. If you want to see and post comments in your KB also, simply add the new field to your Contract layout.
For more details on installing and configuring the app, see Agiloft Contract Assistant for Word.
|2693||Additional updates for the Word app||Beyond the addition of the Comments tab, the Agiloft Contract Assistant for Microsoft Word has more
improvements to offer.
|2685||Updated design of Quick Search filters, buttons, and settings||The new Quick Search pane continues to improve, now sporting minor but notable updates to filters, buttons,
|2690||Updates to the layout editor||
The new layout editor has been improved in a few additional ways. You can now:
|2698||Turn on the new user interface more easily||
Enabling the new user interface is now simpler, relying only on the setting you choose in the navigation menu. The Use New GUI setting has been removed from Setup > Look and Feel > Power User Interface.
To enable the new interface for a set of users, go to Setup > Look and Feel > Navigation Menu Setup and edit their navigation menu. Then, you can set the Navigation Menu Location on the General tab to Top, which both relocates the navigation menu and enables the new user interface across the system.
For more information about the navigation menu, see Navigation Menu Setup.
|2686||Updated scheduling options added to Chart Collections||
Chart Collections now offer the same improved frequency options on the Schedule tab as the other types of reports. These options are more intuitive, and they also offer more granular control when creating schedules. For example, you can now schedule a Chart Collection to be distributed every two weeks on Monday at 12:00.
|2691||New warning about unsaved changes in split view||
To avoid unintentional lost work, you will now see a warning if you're editing a record in split view and you open a different record without clicking Save. For users who frequently work in split view and don't need the reminder, you can disable the warning.
If you turn the warning off, but later want to re-enable it, you can do so from User Menu > Preferences > General Preferences. The setting can also be changed globally from Setup > Look and Feel > General Preferences.
|2706||Fixed password change timeout during login||Previously, database-related timeouts and delays could occur when an external user changed their password
directly after logging in for the first time. Now, these timeouts and delays do not occur.
|2705||Support added for nested linked actions in syncs||Previously, entity sets containing nested linked actions could cause a sync to fail, and would display an "Error
exporting: null" error message. Now, nested linked actions no longer cause the sync to fail.
|2703||Fixed an issue with conditional visibility for multi-choice fields||
Previously, in some situations, multi-choice fields that were conditionally visible would appear even when the visibility conditions were not met. For example, a multi-choice field that is conditionally visible only for Employment Agreements might appear on a Contract record for a Non-Disclosure Agreement, and might appear in the History tab as if they had been modified.
Now, this issue is fixed.
|2702||Fixed sync options||
The sync options to "Make the ability to edit this field conditional" and "Make this main table default Action Bar for" now work as intended. Previously, they were not applied to new teams or groups added during the sync.
|2701||Secure hotlink fix||
Hotlinks are now generated properly for users with usernames containing umlauts.
|2700||Fixed record lock on External Sync error||
Previously, failed External Syncs locked the record where the sync error occurred. Now, the record is properly released instead of remaining locked.
|2699||Validation bypass errors fixed in the Word app||Previously, ignoring error messages in the Agiloft Contract Assistant for Word could allow you to bypass certain
validation checks, such as Contract Start Date being after Contract End Date. Now, error messages prevent
further action until they are addressed.
|2696||Fix to diff reports||Previously, diff reports sometimes contained false positives for Actions. Now, these reports accurately reflect
This release features performance optimization for the following, which will now work faster in some situations:
|2710||Improved permissions handling on History view||
Field-level permissions are now taken into account when you view record history. When you view a History entry that includes changes to fields you don't have permission to view, those values are now hidden.
|2707||New KB Alias option to make renaming KBs easier||
If you've considered changing the name of your KB, but avoided it because you have a lot of customizations, now is the time to reconsider. The new KB alias option in the admin console allows you to give your KB a new name, but specify its past name as an alias. This allows existing configurations to continue working, without needing to update the KB name everywhere it appears.
For example, REST calls you've set up will continue working after you change names, if you provide the old name as an alias.
If you need to change the KB name again in the future, you can add more aliases to the list.
|2711||Improved email template hotlinks handling||
Email template hotlinks now behave as expected when they contain field values with spaces and special symbols.
|2712||Fixed DocuSign envelope status updates||Improved DocuSign envelope status updates so they aren't blocked by Linked Record actions.|
|2709||Upgraded MySQL and Openjdk||MySQL5 has been upgraded to version 5.7.38. Openjdk has been upgraded to version JDK 8u332.|