Upload or Connect?
Uploading and connecting both register data as a Resource. They differ in where the bytes live.
Two columns. Upload: file bytes in your organization’s platform storage, metadata on the platform. Connect: file bytes in the third-party app, a link and metadata on the platform, and an agent fetching the file when a job runs.
static/img/training/upload-vs-connect.png
Caption: Upload stores the bytes. Connect stores a link.
Upload
- The bytes go to the storage your organization set up for the platform.
- The platform records the metadata.
- Best for files on your computer.
Connect
- The bytes stay in the third-party app.
- The platform stores a link and the metadata.
- When a job runs, an authorized agent fetches the file from the app.
- Best for data managed in a PLM system, a requirements tool, or a cloud drive.
Either way, you get a Resource with an ID, a revision history, access controls, sharing, and job support.
Apps you can connect
- PLM and PDM: PTC Windchill, Siemens Teamcenter, 3DEXPERIENCE Enovia, and 3DEXPERIENCE CATIA
- MBSE model repositories: Teamwork Cloud and IBM Rhapsody Model Manager
- Requirements and lifecycle management: IBM DOORS, IBM DOORS Next, IBM EWM, and IBM ETM
- Issue tracking and knowledge bases: Atlassian Jira and Atlassian Confluence
- Cloud documents and collaboration: Microsoft 365 (SharePoint), Google Drive, and Google Chat
The list keeps growing, and your organization may enable only some of these apps. See Third Party App Integrations for the current list.
Think about your own team: which data should stay in its system of record, and which should you upload?