240 lines
11 KiB
JSON
240 lines
11 KiB
JSON
[
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 0,
|
|
"timestamp": "0:50",
|
|
"timestamp_sec": 50,
|
|
"title": "Evolution of ST Routing Capabilities",
|
|
"summary": "ST routing evolved from script-based system (pre-4.6) through application framework (4.6-5.2) to advanced routing (5.3) and orchestration features in the last 1.5 years. Modern MFTS can leverage orchestration to improve old workflows and handle disconnected systems lacking global visibility.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 1,
|
|
"timestamp": "3:40",
|
|
"timestamp_sec": 220,
|
|
"title": "Three Foundational ST Improvements",
|
|
"summary": "Transfer site definitions now support dynamic parameters like download folders. Application framework allows adding protocols and controlling connections per site individually. History tracking prevents unwanted deletion of files after download, and SSH connections can be reused for efficiency.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 2,
|
|
"timestamp": "5:09",
|
|
"timestamp_sec": 309,
|
|
"title": "Scheduling Enhancements and On-Demand Pulling",
|
|
"summary": "ST moved from pure admin UI to cron job scheduling for finer control. On-demand pull from inside routing enables pulling files based on conditions within routes, allowing reactive rather than time-based file retrieval without separate schedulers.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 3,
|
|
"timestamp": "6:49",
|
|
"timestamp_sec": 409,
|
|
"title": "Scenario 1: Conditional On-Demand Pull",
|
|
"summary": "Pull files from a remote site only when triggered by a specific condition (e.g., a .ready file arriving). Supports SFTP, FTP, HTTP, HTTPS only; not yet available for pluggable sites. Pulled files are treated as individual transfers, not as a batch in the same sandbox.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 4,
|
|
"timestamp": "10:03",
|
|
"timestamp_sec": 603,
|
|
"title": "On-Demand Pull Limitations and Workarounds",
|
|
"summary": "Pulled files cannot be combined into a single sandbox; must be published separately if processing together is needed. Multiple source locations require separate pull steps. Override download folders enable pulling from multiple folders on same site without creating separate transfer sites.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 5,
|
|
"timestamp": "13:00",
|
|
"timestamp_sec": 780,
|
|
"title": "Pull Configuration Details and File Patterns",
|
|
"summary": "Use globbing patterns (e.g. *.* for all files with extension) to specify which remote files to pull. Destination folder can be same subscription or different; if different, triggers subscription on destination folder.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 6,
|
|
"timestamp": "15:05",
|
|
"timestamp_sec": 905,
|
|
"title": "Pull Triggering Mechanisms",
|
|
"summary": "Pulls are triggered by file arrival, not continuous monitoring. Trigger can be internal app upload, external partner file, API upload, scheduler, or folder monitor. Multiple independent pulls within route can step on each other \u2014 unlike scheduler, they have no built-in protection.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 7,
|
|
"timestamp": "24:30",
|
|
"timestamp_sec": 1470,
|
|
"title": "Pull Behavior on No Files and Empty Wildcard",
|
|
"summary": "If pull returns no files, route continues as success. Use remote-no-files trigger combined with wildcard-is-empty condition to handle zero-file scenarios specifically.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 8,
|
|
"timestamp": "36:39",
|
|
"timestamp_sec": 2199,
|
|
"title": "Scenario 2: Set Flow Attributes for Variable Passing",
|
|
"summary": "New step allows setting variables (timestamps, metadata) at any point in route for reuse later. Variables stored in .STFS folder, not database. Enables tracking when files arrived, how long processing took, or passing protocol/source info between accounts without embedding in filenames.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 9,
|
|
"timestamp": "38:15",
|
|
"timestamp_sec": 2295,
|
|
"title": "Flow Attributes Implementation and Expression Language",
|
|
"summary": "Add new parameters or override existing ones using expression language. Can reference transfer.protocol, account names, dates, other flow attributes. Multiple set-flow-attributes steps can chain together creating breadcrumbs of processing history for email notifications or downstream consumption.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 10,
|
|
"timestamp": "46:21",
|
|
"timestamp_sec": 2781,
|
|
"title": "Scenario 3: Passing Variables Between Accounts",
|
|
"summary": "Set flow parameters in one account, publish file to second account, and second account's routing can use those same variables. Original protocol, timestamp, sender email propagate to downstream routing via .STFS, enabling multi-account orchestration with shared context.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 11,
|
|
"timestamp": "51:21",
|
|
"timestamp_sec": 3081,
|
|
"title": "Flow Attributes Storage and Persistence",
|
|
"summary": "Flow parameters saved to .STFS folder structure per file, not database. If .STFS is deleted, variables disappear. Variables persist for downstream processing as long as .STFS survives file lifecycle.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 12,
|
|
"timestamp": "58:06",
|
|
"timestamp_sec": 3486,
|
|
"title": "Multi-Account Routing with Core ID Tracking",
|
|
"summary": "Files retain same core ID across multi-account daisy-chaining. Publish file to second account, set flow variables describing first account processing. Second account routing can condition on or report those variables, enabling end-to-end tracking without database dependencies.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 13,
|
|
"timestamp": "61:00",
|
|
"timestamp_sec": 3660,
|
|
"title": "Scenario 4: Error Handling with Conditional Routing",
|
|
"summary": "New checkbox allows routing to proceed on both success and failure with different steps for each outcome. Each step can now specify success-only, failure-only, or both conditions independently. Previous limitation was proceed-on-error applied globally for all downstream steps.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 14,
|
|
"timestamp": "62:00",
|
|
"timestamp_sec": 3720,
|
|
"title": "Conditional Step Execution Based on Prior Status",
|
|
"summary": "Use previous step's exit status to run steps conditionally. Example: send file to primary location; if failure then send to backup. Different failure types (push, PGP, pull errors) trigger same fallback step, enabling non-linear routing with multiple paths.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 15,
|
|
"timestamp": "73:36",
|
|
"timestamp_sec": 4416,
|
|
"title": "Scenario 5: Tracking Route Path with Flow Variables",
|
|
"summary": "Initialize variables at route start (main_server=no, backup_server=no). When main push succeeds, set main_server=yes. On backup attempt if main failed, set backup_server=yes. Final publish shows which server actually processed the file using yes/no combinations.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "850846395",
|
|
"video_url": "https://vimeo.com/850846395",
|
|
"chapter_index": 16,
|
|
"timestamp": "80:06",
|
|
"timestamp_sec": 4806,
|
|
"title": "Reporting Flow Attributes to Sentinel",
|
|
"summary": "Flow attributes not visible in Sentinel by default. To report, map flow parameter to unused Sentinel variable field using expression syntax (dollar sign prefix). All mapped variables publish for files with flow parameters; not conditional. Alternative: use flow variables in emails or downstream subscriptions.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
}
|
|
] |