Wrike
[Bug] Wrike new event trigger for TaskCustomFieldChanged
Issue Description: The new event trigger for TaskCustomFieldChanged was not generating datapills from the response payload, such as value, taskId, oldValue, and customFieldId. This was preventing users from utilizing these datapills in their actions.
Fix Description: The issue was fixed by adding event-specific fields to the TaskCustomFieldChanged output schema and removing duplicates. Also, since folderId wasn't in the TaskCustomFieldChanged payload, its schema was deleted. This ensures datapills are correctly generated for user actions.
Sage Live[Bug] Sage Intacct connection getting cached
Issue Description: Users have reported an issue with the Sage Intacct connection on Sagelive. The connection form is not updating with new login details and defaults to the initial set of credentials used. Additionally, after disconnecting and reconnecting, the system does not prompt for a password and automatically reconnects.
Fix Description: We resolved the Sage Intacct connection issue caused by an uncleared Session ID saved in settings. Adding the Session ID as a hidden password type to the connection schema is now cleared upon disconnection. Changes or attempts to connect without a password trigger reauthorization, preventing using old credentials and requiring a password for new sessions.
Magento
[Bug] Missing datapills in get customer by id
Issue Description: Users reported an issue where certain fields in the output, specifically "disable_auto_group_change", "extension_attributes", and "custom_attributes", were not visible as datapills in the output schema of the action.
Fix Description: We have addressed this issue by adding the missing datapills "disable_auto_group_change", "extension_attributes", and "custom_attributes" to the output schema. Now, all output fields should be visible as datapills.
Azure Monitor
[Bug] Azure monitor no validation on mandatory fields allows empty connection to be made
Issue Description: Users could create an empty Azure monitor connection by not entering the required Workspace ID and Shared Key fields. This resulted in audit log streaming errors as there was no valid connection to stream to.
Fix Description: We have now added validation to check if the necessary parameters exist when creating an Azure monitor connection. This will prevent users from creating an empty connection. Additionally, we have provided hints to assist users in finding the keys.
ZoomInfo
[Bug] ZoomInfo connection is frequently getting disconnected
Issue Description: Our client has reported frequent disconnections with their ZoomInfo connection. Despite having the correct permissions and API access, the connection is lost after a few days and needs to be manually reconnected.
Fix Description: The issue was that the credentials were not refreshed when using a custom action in ZoomInfo. This was caused by the absence of an acquire block in the custom action definition, which supports the common 'Authorization' logic for standard and custom actions. This issue has now been resolved.
QuickBase
[Enhancement] The name and logo for the QuickBase connector need to be updated
The name and logo for the Quickbase Connector have been successfully updated.
[Bug] Chunking is happening in the middle of the CSV lines, causing import failure
Issue Description: The connector incorrectly divided the CSV lines, leading to import failures. This issue was particularly prevalent with large CSV files. The connector was not always dividing at the end of the CSV lines but often in the middle of a line or word, causing import issues.
Fix Description: We have addressed the issue by improving the error logic with CSV files with more columns. We have also corrected the number of records processed in the output. This should resolve the import failures and ensure that the number of records processed matches the actual number in the CSV file.
JWT Tool
[Bug] Rsa private key in the connection is in plain text
Issue Description: The JWT Tool displayed the RSA private key in plain text, a security concern.
Fix Description: The issue has been resolved by updating the field control type to 'password'. Now, the RSA private key will not be displayed in plain text, enhancing the security of the JWT Tool.
