Add simulated database integration relationships
This commit is contained in:
@@ -25,6 +25,8 @@ The initial landscape contains Website, API, ERP, CRM and Email Platform plus tw
|
||||
- Use typed Data Flow, Deployment, Dependency and Source Repository relationships. Development playback includes the simulated Bitbucket commit → Azure DevOps build → website deployment journey.
|
||||
- Model physical operations alongside software with Physical Location and Business Operation categories, plus Physical Goods and Human Task relationships. The Warehouse preset includes receiving, storage, picking, dispatch and returns with clearly labelled physical-goods ports and fictional shipment payloads.
|
||||
- Run the mixed Physical goods receipt demo: SAP purchase order → Supplier shipment → Warehouse → Warehouse Operative decision → Warehouse Management System → SAP confirmation. Physical locations remain independent from their software systems; all transfers are simulated and inspectable.
|
||||
- Model persistent database integrations separately from activity: Direct Database Access, Scheduled Import, Replication / Sync and File Transfer. Configure access mode, trigger/frequency, source tables/views/queries, destination, authoritative source and an optional simulated mapping. Live query requests and returned database rows are separate connections; scheduled imports identify downstream copies such as Sitecore items.
|
||||
- Compare the example Sitecore live-query and scheduled-import scenarios for the fictional Product / Literature / Webinar Management application and MSSQL database. Database payloads are sample rows/JSON only; no database connection or inventory/accounting engine is implemented.
|
||||
- Place reusable Website, CRM, ERP, Email Platform, Analytics and API presets, selecting only the capabilities needed for each instance.
|
||||
- Browse the layered preset library from the Presets tab: searchable system/product catalog entries, shared capabilities, deployment layouts and starter kits. Entries include tags, version metadata and official documentation sources; favourites are stored locally.
|
||||
- Inspect labelled capability ports and fictional action payloads, expand node actions, and save customised systems as private browser-local presets.
|
||||
|
||||
Reference in New Issue
Block a user