212 lines
9.5 KiB
JSON
212 lines
9.5 KiB
JSON
[
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 0,
|
|
"timestamp": "0:07",
|
|
"timestamp_sec": 7,
|
|
"title": "Creating Accounts via REST API Subscriptions",
|
|
"summary": "Subscription directories are created when users first log in or when files are pushed/pulled. Manual filesystem operations should be avoided. Publish to account operations automatically create target folders unless explicitly disabled.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 1,
|
|
"timestamp": "4:42",
|
|
"timestamp_sec": 282,
|
|
"title": "External Scripts for File Validation and Quarantine",
|
|
"summary": "External scripts (Bash/Python) can perform sanity checks on outbound files with yes/no decision logic. Return codes (0=success, non-zero=failure) control routing. Failed files can be discarded by deletion from sandbox or routed conditionally. Process-only-result-from-preceding-step checkbox prevents empty file processing.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 2,
|
|
"timestamp": "7:12",
|
|
"timestamp_sec": 432,
|
|
"title": "Sandbox Lifecycle and File Handling in Routes",
|
|
"summary": "Sandboxes are destroyed immediately after route completion. Files can be deleted within scripts to prevent downstream processing. Step-level condition checks based on preceding step exit status prevent processing of bad files.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 3,
|
|
"timestamp": "9:54",
|
|
"timestamp_sec": 594,
|
|
"title": "File Movement in Scripts vs Routing Steps",
|
|
"summary": "File movement via scripts adds invisible overhead and performance cost. Recommended: use routing steps (publish to account, send to server) with conditional success/failure branches for transparency, auditability, and reporting.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 4,
|
|
"timestamp": "14:02",
|
|
"timestamp_sec": 842,
|
|
"title": "Ad Hoc File Transfer with Account Templates",
|
|
"summary": "Ad hoc file sharing uses account templates with LDAP authentication. Rotating pool of 5 templates is acceptable. File-sharing ad hoc creates dynamic links to centralized base folder; ad hoc mailbox and package folder settings apply only to message-based ad hoc, not file sharing.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 5,
|
|
"timestamp": "16:42",
|
|
"timestamp_sec": 1002,
|
|
"title": "Ad Hoc Base Folder and Link Architecture",
|
|
"summary": "Ad hoc files store in centralized base folder with user-specific links created on-the-fly. Unlike regular subscriptions where files go into user folders, ad hoc provides single package with multiple access points. Package folder settings irrelevant for file-sharing use case.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 6,
|
|
"timestamp": "21:17",
|
|
"timestamp_sec": 1277,
|
|
"title": "Protocol Batch Size Error and Database Tuning",
|
|
"summary": "Batch size default 100 controls protocol command writes. Increase to 150 if error occurs daily on standard cluster; enterprise clusters tolerate higher values. Batch-size tuning affects database write performance under load.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 7,
|
|
"timestamp": "23:40",
|
|
"timestamp_sec": 1420,
|
|
"title": "File Retention Period Integer Validation Error",
|
|
"summary": "Misconfiguration warning in file maintenance application: retention period must be integer. Check server configuration and account-level overrides for typos, commas, or dots. Error does not prevent operation (defaults to no cleanup with -1).",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 8,
|
|
"timestamp": "28:47",
|
|
"timestamp_sec": 1727,
|
|
"title": "Storage Quota Limitations and Monitoring Alternatives",
|
|
"summary": "No built-in folder size limit exists due to multithreaded architecture. Feature under consideration for future release. Alternative: OS-level monitoring or Sentinel correlation rules with alerts at thresholds, followed by account disable if quota exceeded.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 9,
|
|
"timestamp": "31:37",
|
|
"timestamp_sec": 1897,
|
|
"title": "Transfer Log Partitioning and Maintenance Schedule",
|
|
"summary": "Partition days to prebuild creates daily partitions for transfer log retention. Always run maintenance daily as recommended. Non-daily schedules affect partition-dropping behavior differently than daily runs.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 10,
|
|
"timestamp": "36:40",
|
|
"timestamp_sec": 2200,
|
|
"title": "Folder Access Restriction via ACLs and File Restrictions",
|
|
"summary": "No UI control to hide folders from directory listings; authorization plugin required for custom visibility. Use access file directory restriction (DENY) to prevent upload/download/open. SSH clients ignore hidden dot-prefix folders by default for less-technical users.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 11,
|
|
"timestamp": "39:35",
|
|
"timestamp_sec": 2375,
|
|
"title": "Subscription Upload Restriction Placement and Strategy",
|
|
"summary": "Restrict uploads to specific folders rather than entire filesystem access when possible. Upload restrictions are cleaner than directory access denial which returns access-denied errors to users. Combine restrictions with dot-prefix naming convention for dual visibility control.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 12,
|
|
"timestamp": "43:01",
|
|
"timestamp_sec": 2581,
|
|
"title": "Pull Failure Notifications via Conditional Routing",
|
|
"summary": "Configure notifications for pull connection failures in subscription advanced routing. Separate success/failure routes with conditional triggers: pull with transfer status failure. Create new routing package route triggered on failure, add mail notification step, reorder with first-matching policy.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 13,
|
|
"timestamp": "46:09",
|
|
"timestamp_sec": 2769,
|
|
"title": "Pull Empty File Handling and Post-Download Notifications",
|
|
"summary": "Uncheck 'no files found sends to routing' when empty pulls are expected. Use 'on failure' checkbox to trigger routing only on connection failures. Post-download notifications fire when users download files, useful for publish-to-account acknowledgment workflows.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
},
|
|
{
|
|
"video_id": "981433083",
|
|
"video_url": "https://vimeo.com/981433083",
|
|
"chapter_index": 14,
|
|
"timestamp": "50:32",
|
|
"timestamp_sec": 3032,
|
|
"title": "Route Ordering and Conditional Triggering Best Practices",
|
|
"summary": "Use conditional route expressions (transfer status = success/failure) instead of step-level proceed settings. First-matching policy prevents error-path processing on positive routes. Conditional logic at route level provides transparency, auditability, and reporting visibility vs invisible script-level file moves.",
|
|
"transcript": "",
|
|
"is_demo": false,
|
|
"frame_description": null,
|
|
"source": "ask-annie",
|
|
"series": "ST Best Practices Q&A"
|
|
}
|
|
] |