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
Core api multiple entries error #32412
Conversation
…ore-api-multiple-entries-error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, please see my comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look OK, but do we still need to check if the Core API integration is enabled if we use this script?
Also was this tested successfully on XSOAR 8? You can forward an EML file to a phishing inbox, it should trigger that flow in the playbook
…ore-api-multiple-entries-error
…om/demisto/content into ay-core-api-multiple-entries-error
@idovandijk |
Concerning testing this on XSOAR 8, I checked the script UploadFile by creating a new playbook that uses it, and saw that it is able to run on multiple entry IDs, and upload the attachments to the relevant incident. |
Need to verify that the newly uploaded files show up in the layout |
Status
Related Issues
fixes: https://jira-dc.paloaltonetworks.com/browse/XSUP-31868
Description
Added the option to run the command core-api-multipart subsequently in the playbook Process Email - Generic v2 by using the automation UploadFile with the option isArray: true.
Must have