Connectors Release Notes - 2024.03 (continued-1)

[breogan-ouvina]

Other releases 

Dropbox
[Enhancement] Bidirectional sync support 

Two new actions have been introduced to enhance the support for Dropbox bidirectional sync: 'Copy file' and 'Delete file'. Additionally, we updated the hint, title, and description for the 'Upload large file using file contents' action and deprecated the 'Upload file using file contents' action. These changes enhance the functionality and usability of Dropbox's bi-directional sync support. 

Stripe 
[Enhancement] Support API key authentication 

We have successfully implemented API key authentication for our Stripe connector. We also updated the logo for a refreshed look. 

SMS by Workato 
[Bug] Twilio SMS is not rate-limited 

Issue Description: We identified an issue with our Twilio SMS Connector in the production environment. Using Workato's Twilio API, the connector did not have a limit on the SMS in one recipe. This meant an individual could send unlimited SMS messages using a single transaction. 

Fix Description: We have implemented a rate limit for the SMS connector. Please note that this rate limit will only apply to new users. Existing users will still be able to send unlimited SMS messages. We have also added a feature flag to existing users through migration. 

Email by Workato 
[Bug] Email is not rate-limited 

Issue Description: There was a need to introduce a rate limit on the email connector to manage the volume of emails being sent. 

Fix Description: A rate limit for the email connector has been introduced, affecting only new users by limiting their email-sending capabilities. Existing users remain unaffected, retaining their ability to send unlimited emails, and will receive a feature flag via a migration process. 

[Enhancement] The hint for the “To” field needs revision 

The hint for the 'To' field has been updated to clearly indicate that multiple email addresses can be entered, separated by a comma. 

Jira 
[Bug] Jira updated issue webhook 

Issue Description: There was an issue with the Jira updated issue webhook, where it was causing an exception when a blank webhook was received. 

Fix Description: The issue has been resolved. Now, when a blank webhook is received, Jira will not create events on the updated issue webhook, preventing the exception from occurring. 

[Bug] Failed jobs are called twice 

We have addressed an issue in the Jira service desk connector where the API was mistakenly called twice for failed jobs, affecting actions like 'Get comment by ID', 'Get issues in the queue', and 'List comments'. The issue is now fixed; the API will be called once for failed requests, aligning with the behaviour of successful API calls.

[Bug] Parent field in does not accept issue key 

Issue Description: Users reported an issue with the Parent Field in Jira not accepting the Issue Key. Instead, it was returning a 400 bad request error. The field was supposed to accept both issue key and issue ID per the instructions. 

Fix Description: The issue was caused by the system mistaking the parent key for the parent ID. The system is modified to identify whether 'Create issue' and 'Update issue' actions receive an integer or a key in the Parent field. It then selects either "parent": {"id":"parentId"} or "parent":{"key":"parentKey"} for the payload, allowing Jira's Parent Field to accept both issue key and ID accurately. 

SuccessFactors 
[Bug] Search record action is not populating the search fields 

Issue Description: Our customer reported an issue with the search record action. The search fields were not populating when they selected different record types. This happens even when switching between old and new connections. 

Fix Description: The problem was caused by a picklist API call limit, affecting schema generation. The system now adjusts for this limit; if a data object's picklist hits it, it will be set to nil. For schema generation with a present or nil picklist, the old mechanism is used or an empty picklist shows respectively, allowing code entry via the toggle field. 

[Bug] Trigger closure bug 

Issue Description: A bug affects event closure, causing old events to be incorrectly re-selected. This is due to a recent update which modified the conversion process for date and time fields, leading to a loss of zone information. Consequently, this has resulted in incorrect timestamps being set and used in subsequent operations, fetching slightly older records than intended. 

Fix Description: We have addressed the issue with the incorrect setting of event closure in SuccessFactors. The fix involves correctly parsing the timestamp fetched from the last modified record before it is used in the next operation. This ensures that the correct timestamps are used, preventing the re-selection of old events. 

Amazon S3 
[Bug] Upload file action in S3 fails when object name starts with "/" 

Issue Description: Users encountered errors uploading files to Amazon S3 if the object name started with "/" despite no recent changes from their side. This function had worked correctly before. 

Fix Description: The problem was fixed by adjusting the path-building logic, which previously led to wrong path construction and incorrect host identification for filenames beginning with "/". An 'override_default_path' flag was introduced to override the default base URL in custom actions while maintaining existing logic for current actions. 

BIM 360
[Bug] Internal error on upload file action 

Issue Description: Our clients report a BIM 360 connection issue affecting file uploads between 10mb to 20mb, causing internal errors and impacting data migration and synchronization across projects. Despite adjustments to thread and file chunks, the problem remains. A resolution is needed by March 20 for a scheduled migration on March 22. 

Fix Description: Our team has successfully addressed the issue with the BIM 360 connection. Clients should now be able to upload files of all sizes without encountering internal errors. 

Salesforce
[Bug] Wrong link in connection configuration 

Issue Description: Customers have reported issues with the Salesforce connection frequently disconnecting. This issue was traced back to customers using the incorrect link in the Custom Domain URL. They were using the Salesforce lightning link instead of the Salesforce classic link. 

Fix Description: We have updated the connection configuration hints to specify the correct link for the 'Organization/community custom domain URL'. This should guide customers to use the Salesforce classic link and prevent the connection from disconnecting. 

Hubspot
[Bug] Archived datapill is not available in the trigger 

Issue Description: Our client reported an issue with the Hubspot trigger: New Contact. The problem was that the Archived datapill was not available in the output of the trigger. 

Fix Description: We have addressed this issue by adding the missing datapills. Now, the Archived datapill is available in the output step of the Hubspot trigger: New Contact. 

TableStorage
[Bug] Workato data tables filter value UI issues 

Issue Description: Two issues were found in the Workato Data tables' Search records action. First, mapping a datapill as a filter for an integer showed '0' instead of the actual datapill, which didn't happen with strings. Second, using formula mode for integers had the same issue and added an extra '=' for strings. 

Fix Description: The issues with the Search records action in the Workato Data tables have been resolved. Now, when mapping a datapill to filter value for an integer or number column type, the correct datapill is displayed. The extra '=' previously displayed for string has also been removed. 

[Enhancement] Treat empty string as null for relations column 

Issue Description: Currently, when using the TableStorage Connector, if a datapill from a skipped condition is used, an empty string is generated instead of a null value. This results in an API error when creating entries with a record ID. 

Fix Description: The issue has been resolved by ensuring that when a blank or non-ID relation field is provided in an add, update, or upsert action, a null ID is passed instead of an empty string. This prevents the API error from occurring. 

[Bug] Triggers not picking records if since date set in past 

Issue Description: The triggers were not picking up records if the 'since' date was set in the past. The issue was identified when setting up a new record trigger and selecting a 'since' date from 3 or 4 months ago. 

Fix Description: The issue has been resolved by updating the 'since' field hint to inform users about the API restrictions. Due to platform limitations, the Workato DB API does not support fetching changes from over 30 days ago. This information is now clearly communicated to the user. 

[Bug] Data tables field name not available 

Issue Description: Our customer found that the output from the search action only provides the API ID for fields, not the field names. This has made it difficult for them to map using the field names. The Python workaround is time-consuming and must be repeated when they move to production, as the keys will change. 

Fix Description: We have addressed this issue by introducing a new schema field, 'output_format', in the Workato database. This will allow users to control the output type (ID or column names) depending on their preference.

Coupa
[Bug] Coupa remit to address fields are missing 

We have addressed an issue where users could not create a supplier due to missing remit-to-address fields. The error was caused by the required fields - City, Postal, and Country - not being available. 

We have now added support to add or override fields using the schema designer in the Create/Update action. This will ensure all necessary fields are available and correctly marked as required. 

Outlook
[Bug] Outlook trigger does not pick up all events 

Issue Description: The Outlook trigger sometimes fails to detect all events, especially when an email is received twice with a new attachment but the same subject, leading to only one or no jobs being created instead of two. 

Fix Description: We have resolved this issue by adjusting the New Email trigger filter to 'LastModifiedDateTime' instead of 'ReceivedDateTime'. This change ensures that emails received after ATP scanning are picked up. Even if an email is overwritten by a new one after ATP scanning, it will be treated as a new one, and our trigger will process a new job. 

[Bug] 404 error inside trigger 

Issue Description: Our users reported an issue with the Outlook integration where a production recipe checking for Calendar events was returning consistent trigger errors. This issue was not resolved by restarting or copying the recipe. 

Fix Description: We have addressed this issue by implementing a fix to handle the '404 Not Found' error. This ensures the production recipe can successfully check for Calendar events without encountering the previous errors. 

[Bug] Time zone not supported when creating event in Outlook 

Issue Description: Users were experiencing an error when attempting to create an event in Outlook due to an unsupported timezone value, specifically 'Eastern Time (US and Canada)'. 

Fix Description: The issue has been resolved by implementing two changes. 

1. An offset field was added to provide the next page offset. 
2. A timezone picklist was introduced to display the timezones supported by the Outlook API. This ensures that users can only select from the supported timezone values, preventing the occurrence of the error. 

Netsuite
[Bug] Issue when updating an address 

Issue Description: Customers are facing a problem updating addresses in NetSuite due to an error message "Internal ID or External ID is required," even after providing the needed internal ID. This prevents them from updating customer information across all environments, making it a high-priority issue. 

Fix Description: The issue was fixed by altering how NetSuite Subrecords are managed. Before, independently updating Subrecords like addresses caused errors. Any changes to Subrecords must be made within the context of an operation on its parent record. For example, the customer record must be updated to update a customer's address. This adjustment applies to creating, updating, and upserting standard records. 

[Bug] Return_from_action in NetSuite updated_object trigger 

Issue Description: There was an issue with the "updated_object" trigger in Netsuite, which was causing an accidental error. This was due to an unintentional overwrite in a shared method, which was causing a failure in checking against unintended method calls for triggers. 

Fix Description: The issue has been resolved by fixing the unintended overriding of closure. This fix impacts several areas, including:

1. Search custom object 
2. Search records 
3. execute saved search (standard and custom objects) 
4. all bulk triggers 
5. all batch triggers 
6. new classification record trigger 
7. get case comments 
8. new and new/updated records in a saved search (standard and custom objects) 
9. new or new/updated records (standard and custom objects) 

Microsoft Sharepoint
[Bug] Sharepoint unable to retrieve files folder 

Issue Description: There were issues retrieving files and folders from Microsoft Sharepoint, particularly when the folder name has a "%" sign. This resulted in a null result when attempting to retrieve the list of files within the folder. 

Fix Description: The issue has been resolved by modifying the retrieval method. Now, the system uses a decoded URL to retrieve the desired files and folders accurately. Please note that this fix does not involve changes to the user interface. 

Azure Blob Storage
[Bug] Azure storage blob webhook returning 200 even when the recipe is stopped 

We've improved the Azure Blob Storage feature, addressing issues with the Azure Storage New Blob Trigger losing notifications when inactive. Webhooks sent a 200 (OK) response even when stopped. 

We've now improved webhook-based triggers for more dynamic support in Azure blob storage, adding support for more blob events beyond the original 'Blob.Created' event. We've also added support for the 'management.azure.com' scope needed by the new trigger, configurable at the connection level. 

Note that Azure API requires separate tokens for different resource scopes; hence, we've introduced a 'mgmt_token' parameter in 'shared_account.connection_properties' for management scope tokens. 

Zendesk
[Enhancement] Zendesk get comments payload mislabelling 

The issue has been addressed by correctly updating the label to 'Comment ID' from 'Ticket ID'. This change ensures an accurate representation of data in the output schema. 

Freshdesk
[Enhancement] Deprecate platform Freshdesk connector 

The Freshdesk platform connector has been successfully deprecated. Please note that this will not affect any running recipes. Shopify.

[Bug] New updated order 

We resolved a customer-reported issue with the missing ID field under Shipping Lines in Shopify Trigger: New/Updated Order. The ID field is now accessible in the App Data Tree for datapill mapping, impacting create order, update order, get the order by ID actions, and new/updated order triggers, including batch triggers. 

CONTINUES ON NEXT POST