Hi everyone,
I'm currently working facing one challenge with manual case merging, and I’ve noticed that the associated playbook continues to run even after the cases are merged.
Is there any automated way to detach or stop the playbook from the original case during or after a manual merge?
Any suggestions or best practices would be appreciated!
Thanks in advance!
+10Hi
Thanks for posting your question to the community!
Currently there is no direct automated way to detach or stop a playbook from running on an original case during or after a manual merge in SecOps.
However, some community members have suggested workarounds or alternative approaches that can be found in this post: Case Merge conversation
Hope this helps.
Hi
Thanks for posting your question to the community!
Currently there is no direct automated way to detach or stop a playbook from running on an original case during or after a manual merge in SecOps.
However, some community members have suggested workarounds or alternative approaches that can be found in this post: Case Merge conversation
Hope this helps.
Hello
Thank you for confirming that there’s currently no direct automated way to detach or stop a playbook from running on the original case during or after a manual merge in SecOps.
I’ve already tried all the suggested workarounds, but unfortunately, none of them meet my requirements.
I’ll wait for this feature to become available in SecOps. Thanks again for your support.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
