So .... now that Skuid has it's own platform, it also has it's own "server side" possibilities.
Why not it's own server side action framework workflow? I'd even go ape and make a super cool set of workflow UX for Process Boxes, If/Else Routing, Looping, etc, etc, etc. Similar to Salesforce Flow, but way way better. We'd models and action framework.
We could then make use of these more complex/common in a single location from other Skuid Pages or Workflows!!!
Use Case 1: Large Data Processing Requirement. Client needs to process records across 1+ Skuid Connection and thus requiring a more distributed server load processing.
Use Case 2: A multi Skuid Workflow called from one Skuid Page Action Framework action.
Use Case 3: Create one Skuid Workflow that is called from multiple Skuid pages.
Use Case 4: Help with an Import Component to supplement ETL.
I'm just scratching the surface but the possibilities are awesome.
Why not it's own server side action framework workflow? I'd even go ape and make a super cool set of workflow UX for Process Boxes, If/Else Routing, Looping, etc, etc, etc. Similar to Salesforce Flow, but way way better. We'd models and action framework.
We could then make use of these more complex/common in a single location from other Skuid Pages or Workflows!!!
Use Case 1: Large Data Processing Requirement. Client needs to process records across 1+ Skuid Connection and thus requiring a more distributed server load processing.
Use Case 2: A multi Skuid Workflow called from one Skuid Page Action Framework action.
Use Case 3: Create one Skuid Workflow that is called from multiple Skuid pages.
Use Case 4: Help with an Import Component to supplement ETL.
I'm just scratching the surface but the possibilities are awesome.