Unveil the 𝗙𝗹𝗼𝘄 𝗗𝗲𝘀𝗶𝗴𝗻𝗲𝗿 (FD) data model
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2023 03:45 AM
🔊🔊🔊🔊🔊🔊🔊
The following post is based on a linkedin post and is shared here for visibility. Credit goes to author @Nicola Attico
🔊🔊🔊🔊🔊🔊🔊
While many of us are acquainted with the main elements of FD, its data model remains slightly hidden. Recognizing this data model can be invaluable, whether creating apps, crafting reports or merely trying to grasp the system's internals.
Here are its main layers and tables' names that you can use to explore quickly.
🔴 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝗹𝗮𝘆𝗲𝗿: This layer primarily handles the runtime data, managing the progression and results of flows and their steps.
- Flow engine context (sys_flow_context)
- Flow engine context report (sys_flow_report)
- Flow statistics (sys_flow_stats)
- Flow engine log entry (sys_flow_logNNNN)
🔵 𝗧𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗹𝗮𝘆𝗲𝗿: Acting as the initiation point, this layer defines what events or conditions will initiate the flow processes.
- Trigger (sys_flow_trigger)
- Trigger instance (sys_hub_trigger_instance)
- Trigger Definition (sys_hub_trigger_definition)
- Trigger category (sys_hub_trigger_category)
- Trigger flow connector (sys_hub_trigger_input|output)
⚫️ 𝗙𝗹𝗼𝘄𝘀 & 𝘀𝘂𝗯𝗳𝗹𝗼𝘄𝘀 𝗹𝗮𝘆𝗲𝗿: Core to the design, this layer encompasses the main processes and any subsidiary workflows, ensuring logical sequencing.
- Flow base (sys_hub_flow_base)
- Flow (sys_hub_flow)
- Flow snapshot (sys_hub_flow_snapshot)
🟡 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 𝗹𝗮𝘆𝗲𝗿: A modular layer containing reusable elements and logic sequences that can be integrated into various flows.
- Component (sys_hub_flow_component)
- Flow logic instance (sys_hub_flow_logic)
- Action instance (sys_hub_action_instance)
- Subflow instance (sys_hub_subflow_instane)
🟤 𝗙𝗹𝗼𝘄 𝗹𝗼𝗴𝗶𝗰 𝗹𝗮𝘆𝗲𝗿: The brain behind the operations defines the conditions, decisions, and logical pathways the flow should adhere to.
- Flow logic instance (sys_hub_flow_logic)
- Flow logic definition (sys_hub_flow_logic_definition)
- Flow logic variable|input (sys_hub_flow_logic_variable|input)
🟣 𝗔𝗰𝘁𝗶𝗼𝗻𝘀 𝗹𝗮𝘆𝗲𝗿: Acting as the doers, this segment encompasses the specific tasks, outputs, and operations the flow should execute.
- Action type base (sys_hub_action_type_base)
- Action type snapshot (sys_hub_action_type)
- Action input|output (sys_hub_action_input|output)
- Action plan (sys_hub_action_plan)
🟠 𝗦𝘁𝗲𝗽𝘀 𝗹𝗮𝘆𝗲𝗿: Breaking down the process, this layer itemizes each step, its definitions, and the input or output specifications.
- Step instance (sys_flow_step_instance)
- Step definition (sys_flow_step_definition)
- Step input|output (sys_hub_flow_step_definition_input|output)
- 1,405 Views