Store and access structured data between processes and applications
Data Source Type | Description |
---|---|
RESTful System | Traditional integration with external REST APIs |
FlowX Database | Connection to the internal FlowX Database for data persistence |
Access Data Sources
Accessing Data Sources in the navigation menu
Add a new Data Source
Adding a new FlowX Database data source
Configure the collection
Configuring the collection
Create the collection
Navigate to collection
Access Documents tab
Browse documents
Search and filter
Access operations list
Create new operation
Creating a new operation for a FlowX Database collection
Select operation type
Selecting the operation type
Name the operation
Define the operation parameters
Configuring operation parameters
Test the operation
Testing an operation
Save the operation
Database node in a workflow
Add Data Source node
Configure data source
Data Source node configuration
Configure operation parameters
Configuring operation parameters
Set response key
Example: Using filter parameter in find operation
Example: Using process variables in parameters
Example: List active customers
Example: Find products by category and price
Setup
Create Customer collection
Define operations
Customer support process
Customer support workflow with FlowX DB
Benefits demonstrated
Operation fails with filter error
Problem
Solution
Documents not appearing in results
Problem
Solution
Performance issues with large result sets
Problem
Solution
Insert operation fails
Problem
Solution
When should I use Data Search vs. FlowX Database?
What types of data should I store in FlowX Database?
Can I share FlowX Database collections between different projects?
Why doesn't FlowX Database support automatic data migration?
Can I store different types of documents in the same collection?
How does FlowX Database solve cross-process data sharing?
What's the relationship between FlowX Database and the nosql-db-runner service?