After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
Fixed issues for
Release 5.3.5
Date resolved | Issue number | Description |
---|---|---|
2022-09-19 | PSAAS-9413 | Generating container report gets timeout with high CPU utilization or creating 9000+ page long report |
2022-09-19 | PSAAS-9793 | Custom field message has broken link to documentation |
2022-09-19 | PSAAS-9910 | Bulk Edit of Playbooks allow setting playbooks that are in draft mode to active |
2022-09-14 | PSAAS-9319 | Webserver log level setting in admin UI is not respected |
2022-09-14 | PSAAS-10158 | Upgrades may fail on PrepSystem step due to a cp failure with "Text File Busy" |
2022-08-30 | PSAAS-9935 | When running soar-prepare-system, the prompt for setting the Splunk SOAR user's password is overwritten by a progress spinner |
2022-08-23 | PSAAS-9781 | On privileged systems the phantom daemons may be started as the root user after a system reboot. |
Known issues for | Compatibility with related Splunk products |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.3.5
Feedback submitted, thanks!