phase-3-tercen-integration

To migrate a mock Tercen widget, replace the mock data services with real Tercen data services using the sci_tercen_context and sci_tercen_client. This requires a Phase 2 mock widget and a real taskId or projectId to enable actual data access.

Real Tercen service integration supports data flows including projections, file downloads, write-back operations, entity navigation, and workflow execution. These flows are structured using enforced Flow A-E patterns to ensure proper data handling.

Yes, a real taskId or projectId is required to connect your widget to Tercen data services. The integration process must start from a Phase 2 mock widget and uses these identifiers to access actual project data.

After swapping mocks for real Tercen services and setting up the data flows, complete the build and deployment steps to move your widget to production. This ensures the Phase 2 mock widget becomes a production-ready application.

Starting from a Phase 2 mock widget is required because the Phase 3 integration specifically replaces existing mock data services with real ones. Attempting integration without this baseline mock structure bypasses the enforced Flow A-E patterns needed for proper context creation.