cscott/ask-annie
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add chapters for session 857548090 (Haiku)

Browse Source
This commit is contained in:
Conan Scott
2026-03-24 10:04:49 +00:00
parent cc054f3a93
commit 9607028bf0
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
chapters/857548090.json Normal file
View File

@@ -0,0 +1,16 @@
[
{"timestamp": "2:49", "title": "Evolution of ST Routing Technologies", "summary": "ST routing evolved from script-based handling (pre-04/06) through unconditional routing, conditional routing (5.3), to modern orchestration (5.5+). Latest releases enhanced routing with step-level conditions, dynamic parameter passing, and flowchart-based operations. Requires ST 5.5 (February 2024 or newer) for all features."},
{"timestamp": "6:16", "title": "Orchestration Engine Architecture", "summary": "ST became an orchestration engine through transfer side definitions, dynamic parameters, pluggable protocol framework (S3, SFTP), connection reusability, scheduling enhancements with cronjob support, on-demand pulls from routing, step conditions, and variable passing between accounts."},
{"timestamp": "9:05", "title": "Scenario 1: Conditional Pull Operations", "summary": "Pull files triggered by marker file arrival instead of scheduled intervals. Partner uploads ready indicator file; ST triggers pull of other files in response. Download folder and pattern can be overridden using expressions parsed from trigger filename. Pull from Partner step currently supports only four standard protocols (HTTP, Generic, FTP, SSH)."},
{"timestamp": "22:17", "title": "System-to-Human Transfer Site for Email", "summary": "System-to-Human transfer site enables email delivery of files as attachments. Recent enhancement allows file attachment rather than just link delivery. Size restrictions configurable to prevent sending oversized files. Use in advanced routing same as SSH push operations for file distribution via email."},
{"timestamp": "27:45", "title": "Scenario 2: Flow Parameters and Timestamps", "summary": "Preserve initial timestamps across multi-step operations using Set Flow Parameters step (pluggable, requires download from support site). Saves parameter values early in workflow for reuse after long operations like PGP decryption. Supports any calculated value beyond timestamps — file names, encryption timings, processing flags. Variables usable in email notifications and subsequent routing steps."},
{"timestamp": "32:59", "title": "Flow Parameter Configuration", "summary": "Set Flow Parameters step accepts arbitrary variable names and expression language values. Override behavior options: Add New (fails if exists), Override (only sets if exists), or Add New Override (always sets). Can override standard routing variables like account.email. Variables stored in .STFS folders, not database."},
{"timestamp": "39:06", "title": "Scenario 3: Multi-Account Parameter Propagation", "summary": "Flow parameters set in first account automatically propagate to second account during Publish-to-Account. Variables preserve original sender context across account boundaries, enabling notification back to original file uploader upon file pickup or processing completion."},
{"timestamp": "41:40", "title": "Variable Persistence and Limitations", "summary": "Flow parameters and subscription attributes stored in .STFS folders inside subscription directories, not in database. If .STFS folders are cleaned or deleted, variables are lost. Long-delayed operations (downloads days later) still access variables if .STFS is intact. Critical to preserve .STFS folders for maintaining parameter availability."},
{"timestamp": "55:16", "title": "Scenario 4: Failover Routing with Status Tracking", "summary": "Conditional step execution enables fallback to secondary destination on primary failure. Continue on error/success conditions enable complex branching: succeed once, proceed only on failure, or always proceed. Useful for migration scenarios or load-balancing across multiple partners."},
{"timestamp": "58:34", "title": "Step Conditions and Flowchart Operations", "summary": "Every routing step supports exit condition: proceed on success only, proceed on error only, or proceed on both. Step conditions enable decision logic replacing linear execution with true flowchart logic. Next step runs only if previous step's exit status matches condition."},
{"timestamp": "64:03", "title": "Scenario 5: Tracking File Destinations", "summary": "Multi-push scenarios require tracking which destination received the file. Initialize flow parameters before push operations to flag success/failure states. Set parameters conditionally after each push based on previous step success status. Final variables indicate which push succeeded, enabling detailed status emails or Sentinel reporting."},
{"timestamp": "66:02", "title": "Parameter Initialization and Conditional Setting", "summary": "Set initial parameter values (e.g., none, error, not sent) before conditional logic to avoid null/undefined checking. After each push operation, conditionally set success flag using Add New Override behavior. Avoid relying on preceding step once parameters have been modified."},
{"timestamp": "73:15", "title": "Feature Parity and Enhancement Requests", "summary": "Advanced routing features not guaranteed in Flow Manager; CG being retired. Feature requests submitted via Ideas Portal at community portal. Higher votes increase approval likelihood. Account executives can escalate confidential business cases."},
{"timestamp": "80:17", "title": "Presentation Resources and Smart Quotes Warning", "summary": "Full presentation available as PDF with screenshots of all scenarios and variables for recreation. Note: Microsoft PowerPoint converts quotes to smart quotes — clear before pasting into ST configuration. This is a common cause of expression language failures."}
]