Hello, my team here has always used the Classic UI for incident management. It was until recently we implemented the Service Operations workspace and I have had to make small tweaks here and there. Using the Classic UI when we create an incident, we can close it and it would never exist. This was nice when we would create an incident and then throughout the conversation, we realized something else happened and it no longer needed to be created. We would close the incident and it would just cease to exist. Maybe we made an interaction only instead. Now that we use the Service Operations Workspace, we will create interactions based off our conversations at the service desk and if needed we will create an incident. We go ahead and create an incident from the interaction, and it creates an incident and automatically saves it. Therefore, the incident is born. There have been a few cases where we create the incident, but again, it turns out that no incident is needed, and we close it (literally with the X button). When we close it though what Service Operations workspace is doing is auto saving the incident so that it is born. I do not want it created at all. Is there any way to disable this auto save function in service operations workspace? For further clarification I attached a screenshot of the incident log, I never clicked the SAVE button. It took about 20 seconds from creation for this to appear in the history of the incident. This issue does not happen using classic UI.
 
 
Hello @Andrew Meza
To disable the autosave for Incidents created from an Interaction record change the system property com.snc.incident.create_from_interaction.save to false.
if my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
Kind regards
Misgana D.
