23 lines
4.4 KiB
JSON
23 lines
4.4 KiB
JSON
[
|
|
{"timestamp": "0:03", "title": "Template routing issue: subscription attributes not populating", "summary": "A user explains that variables defined at subscription level work in composite routes but don't seem to carry over in template routes."},
|
|
{"timestamp": "0:54", "title": "Use case walkthrough: inbound trigger → pull from partner → push back", "summary": "Clarifies the scenario: an inbound protocol flow captures identifiers, then uses them to pull a remote file and return it to the caller."},
|
|
{"timestamp": "4:02", "title": "Guidance: terminology + next step via support case", "summary": "Confirms template vs composite route terminology and recommends opening a support case to diagnose why attributes aren't passed."},
|
|
{"timestamp": "5:17", "title": "Feature highlight: custom transcoding tables (demo)", "summary": "Shows how to define custom transcoding tables at server level and reuse them across transfer profiles."},
|
|
{"timestamp": "11:24", "title": "Q&A: multiple transcoding tables supported", "summary": "Confirms you can register and maintain multiple custom tables for different partner needs."},
|
|
{"timestamp": "12:22", "title": "New capability: using SecureTransport as an S3 server (S3 commands supported)", "summary": "Explains S3 access to the platform (list/create/upload, including multipart), available since an October release."},
|
|
{"timestamp": "14:06", "title": "Account setup for S3 access: access key behavior", "summary": "Covers how S3-style access keys are configured and that the strings can be defined by the admin (not necessarily generated by the product)."},
|
|
{"timestamp": "16:19", "title": "Security posture: enabling S3 without broadly opening HTTPS", "summary": "Discusses constraints where only specific ports/protocol exposure is allowed and the need to confirm the cleanest S3-only setup."},
|
|
{"timestamp": "17:42", "title": "Deployment architecture: standalone server + dual edge pattern", "summary": "Describes a non-cluster setup using virtualization for scalability and separate edge nodes for internet vs extranet/VPN partner access."},
|
|
{"timestamp": "18:44", "title": "Migration story: moving from a legacy gateway + rebuilding flows", "summary": "Explains migration constraints (limited migration tooling), rebuilding configurations, and a passive gateway design where jobs trigger push/pull."},
|
|
{"timestamp": "22:07", "title": "Upgrade strategy: Sunday maintenance + test-by-cloning production", "summary": "Shares an approach to validate upgrades by cloning the production VM to simulate real volume and trimming history before DB migrations."},
|
|
{"timestamp": "25:15", "title": "Preview: new file tracking UI + navigation improvements", "summary": "Shows the redesigned file tracking experience and how to drill into inbound→outbound relationships."},
|
|
{"timestamp": "28:19", "title": "Monitoring challenge: linking multi-subscription trigger file patterns", "summary": "Highlights why end-to-end tracking is harder when one subscription triggers another (empty file trigger → pull → store → second subscription)."},
|
|
{"timestamp": "29:09", "title": "Introducing Workbench: fleet health + end-to-end monitoring", "summary": "Presents Workbench as a monitoring/administration layer for multiple MFT nodes with health status indicators and centralized visibility."},
|
|
{"timestamp": "33:24", "title": "Predictive alerting question: late/missing/abnormal file detection", "summary": "Asks about anomaly-style alerts (late, missing, size anomalies) and is directed to Workbench capabilities/roadmap via account team."},
|
|
{"timestamp": "35:09", "title": "Next sessions + how to submit questions in advance", "summary": "Encourages sending questions ahead of future virtual sessions for better coverage."},
|
|
{"timestamp": "35:40", "title": "Invitation to in-person user group + agenda highlights", "summary": "Discusses attending the in-person event and what topics will be covered."},
|
|
{"timestamp": "37:52", "title": "Migration effort reflections: scale + partner outreach", "summary": "Notes the practical reality of migrating hundreds of partners and the time/coordination it requires."},
|
|
{"timestamp": "43:17", "title": "Suggested future topics: feature-focused sessions (e.g., S3)", "summary": "Requests more capabilities/new features sessions and confirms those topics are planned for future events."},
|
|
{"timestamp": "44:21", "title": "Wrap-up and goodbyes", "summary": "Confirms no further questions and closes the session."}
|
|
]
|