Tables used in WorkFlow

[VaibhavP5059517]

hey All,
I have started learning about Workflow and wanted to know that how its data is being stored in ServiceNow.
How they are connected and how to configure, and also its comparison with flow designer.

[VaibhavP5059517]

Hey @Mark Manders ,
I am learning Workflow because I have to convert the workflows to flow designers as workflow is deprecated and my organization wants to shift to flow designer.

[Dr Atul G- LNG]

https://developer.servicenow.com/dev.do#!/learn/courses/australia/app_store_learnv2_flowdesigner_aus...

[Ankur Bawiskar]

@VaibhavP5059517 

when it comes to workflow it's stored in different tables

Workflow tables  -> everything shared here

for flow check the tables in sys_db_object table by searching as this

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Dr Atul G- LNG]

https://www.servicenow.com/docs/r/build-workflows/legacy-workflow/getting-started-workflows.html 

Workflow support

Important:

As of the Zurich release, new customers no longer receive the legacy workflows created and published by ServiceNow, Inc.. All legacy workflow functionality has been replaced by Workflow Studio content. Only customers who upgraded from prior versions retain the ability to use and edit existing legacy workflows. While all customers retain the ability to create legacy workflows, you are strongly encouraged to instead use Workflow Studio to create process automation content. Only Workflow Studio will receive new features and enhancements.

[Tanushree Maiti]

Hi @VaibhavP5059517 

In ServiceNow, a traditional Workflow is stored as a parent record in the Workflow Definition table (wf_workflow), while its individual activities and design steps are maintained in the Workflow Activity table (wf_activity).

However, ServiceNow now strongly promotes Flow Designer as the preferred automation framework. Unlike traditional workflows, Flow Designer uses a more modern, modular architecture where automation logic is organized into Flows, Subflows, and Actions, providing greater reusability, maintainability, and scalability.