hi everyone in this session I will be presenting you how we can render flow-based playbooks as process based playbooks in SAR workspace today in case of flow based playbooks the response does generated by the flows are rendered as a related list under the security instant later analysts can finish these response tasks one by one and he can mark them as close completed in case of crosses based playbooks processes can be configured using the process automation designer wherein the process owner can configure the lanes and activities within a process later these activities can be accessed from The Playbook experience tab of the security instant from the workspace flow based playbooks and process based playbooks are two different solutions that we have today The Playbook experience component that you see under the workspace it is not compatible with the flow-based playbooks that we built from the flow designer in order to truly migrate all the flow-based playbooks as processes in the process automation designer it is going to take lot of time because customers has already implemented hundreds of such flow designer based playbooks in order to solve this problem we have come up with a solution wherein we are creating processes around these flows and these process will help reading the response tasks generated by the flows and render them within the security instant Playbook experience tab of the workspace so now let me show you how we can generate these wrapper process so we have a page Built For This called as wrapper process generator wherein you can select the scr flows and generate wrapper process for them now let me select a flow security incident phishing manual and generate a wrapper process for this flow here it will ask the lens to be generated in the wrapper process for this Flow by default we are selecting all the lanes optionally you can also select the end link so this end line will ensure all the response tasks of the flow are completed before the process can be ended let's click on generate so this will take some time to generate the wrapper process now the wrapper process is generated as you can see in the results you can notice few things after generating the wrapper process the flow is prefixed with the underscore P this is to indicate that there is a wrapper process already generated for this flow and the process is prefixed with underscore F this is to differentiate the wrapper processes from the original processors that were built directly on the process automation designer now let's open a process and understand how it is configured so this is a wrapper process that we just generated as you can see it consists all the lanes that we selected during the generation process draft analysis contain eradicate recover review and it consists the activities like launch flow based Playbook followed by steps in all the lanes and in the end Lane there is the end Playbook activity so these are the utility activity definitions and the launch flow based Playbook it is responsible for invoking the flow based Playbook that we have in the flow designer and the steps activity definition it is responsible for reading the response task generated by the flow based Playbook and render them in the workspace Playbook experience tab and the end Playbook activity it will ensure all the response tasks of the flow based Playbook are completed before this process can be finished and we can also check the trigger condition of this wrapper process which is actually copied from the flow based Playbook since it is already copied to avoid the duplicate scenario of invoking the same Playbook twice we have nullified the trigger condition of the Flow by setting the trigger condition to C side equal to zero now let me show you that yeah as you can see here the trigger condition of the flow based Playbook is now set to 6 at equal to zero now let me show you the runtime experience of the wrapper process that we generated from the workspace so before we do that let's activate the wrapper process it is now activated now let's go to the workspace and from the security incident let's invoke the wrapper process that we just generated by using the add Playbook form action select the wrapper process and add the Playbook now it started showing the Playbook tab under which we can see the Playbook that has already started running as you can notice the steps activity that we have in the wrapper process it has started reading the response tasks generated by the flow and rendering them as tiles within the activity card now analyst can interact with these response tasks just like how he is accessing related list of the security incident from the classic UI he can open this response task in a model dialog it says acknowledge user submission and ask user if they have interacted with the email and he finishes his job and marks this response task as closed complete now the floor resumes and it will create subsequent response task and they will be automatically pulled by this steps activity does the email have any threat indicators is our next response task let's assume there are no response tasks and analyst will say no and Save enough now the flow will resume based on the response of the previous task and it will create the subsequent response tasks in this case since we chose a node to the response task does email have any threat indicators and there is no point of doing the further investigation the process has kept contain eradicate recover and it took the security incident directly to review and in the review we have a response task called notify user and update them on the conclusions of the investigation and the analyst finishes updating the summary and notifies the user and you can mark this response task as close complete once all the response tasks are done in the last Lane since there are no response task pending he can simply attempt to complete which will finish the Playbook to summarize we have started with the differences between flow based playbooks and the process based playbooks and we have discussed about the problem that customer is facing since he has hundreds of flow based playbooks today in his environment it is difficult to migrate the mass process based playbooks and then we discussed about the solution with the help of wrapper process using which we can render the response charge generated by the flows in the SAR workspace and we have also shown how we can generate the wrapper process using the tool uh using the tool wrapper process generator and finally we have shown the runtime experience of the wrapper process generator sorry wrapper process that we just that we generated from the scr workspace thank you team