Pulse 9.3.2 Release Notes
February 18, 2020
New Features and Enhancements
Re-architecture
The Pulse execution method is now refactored to use Hybrid instead of AWS Lambda. This update provides:
Outbound static IP's, for customers to whitelist requests from the Pulse IP addressed in their firewall. Previously, Pulse execution by AWS Lambda could not reach some customers' internal networks.
There is no longer a 6 Mb limitation for payloads as was the previous limitation using AWS Lambda.
Enhanced Dialogs
The following have been added to Pulse dialogs:
-
There is now a refresh icon in your Action View Log dialog. This allows you to refresh your action log without refreshing your entire page.
-
There is now a copy icon in the Trigger dialog. This will allow you to quickly and easily get your url.
Security
Core Node.js Modules Blacklisted
For security matters, all of the core Node.js modules are blacklisted. If users try to add any core Node.js modules in the action code, it will fail when running.
Example: having the action code require ('<module_name>')
Read this list of blacklisted core Node.js <module_name> (s.)
Pulse users are now only allowed to use these modules:
-
request,
-
xml2js,
-
@qasymphony/pulse-sdk,
-
@qasymphony/scenario-sdk
Bug Fixes
| Ticket # | Component | Description |
|---|---|---|
| NA | Database | With the migration from Mongo to PostgreSQL, Pulse webhooks were updated. Pulse now supports both of your updated and original webhooks. |
| 31428, 31607 | Import | There is no longer an issue importing files into Pulse. |
| 34361 | Pulse Access | Users were unable to access Pulse from the 9-box due to a change in the access token used for authentication into the app. This is now resolved. |