-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Update Zoho Survey per feedback from their team #12438
Comments
Hello everyone, I have tested this PR and there're some test cases failed or needed improvement. Please check the test report below for more information |
Hello everyone, I have tested this PR and there're some test cases failed or needed improvement. Please check the test report below for more information |
Hi everyone, all test cases are passed! Ready for release! |
Our development team has requested make following changes on the "New survey response" trigger.
An extra field - "Others" is displayed for every survey event. This is not a survey field. Please refer to the attached screenshot (Select_event_trigger.png).
By default for all API responses we send the responses in an encoded HTML entity format. Please decode the HTML entities in all API responses such as portal list, survey list, department list, collector list, distribution list.
Sample responses "&" should be converted to "&", "'" should be converted to ' , ' should be converted to '.
Please process the Events in the "New survey response" trigger based on the "key" using the "Get survey fields/variables" API. As per the current implementation, when a survey field is modified in the survey, the flow is getting failed. The label should be used for user readability and the other logic should be implemented using the survey field "key". Please note that "key" is the unique identifier for a survey field. We will send "key" in the webhook responses and in the "Get survey fields/variables" API . The survey fields label in the "Get survey field/variables" API may contain duplicate values and it can be edited by the end user.
The text was updated successfully, but these errors were encountered: