[DX] GAP-23: Personal workspace connections show Unknown validation status when deploying to shared folder — no promotion path

[AlexBizon]

Summary

Connection bindings that reference connections in a user's personal workspace show ValidationResult: "Unknown" in the Package Requirements screen when deploying to a shared folder. There is no in-product mechanism to promote or share a connection from personal workspace to a shared folder — it must be recreated from scratch, losing the OAuth token.

Error (Package Requirements screen)

ValidationResult: "Unknown"
FolderType: "Personal"

Both Salesforce and DataFabric connection bindings showed this, even though the connection UUIDs were correct and the connections existed.

Root Cause

When deploying a process to a shared folder (e.g. Shared/Solution Invoice App), Orchestrator cannot guarantee that a personal workspace connection will be accessible at runtime (robots in the shared folder run under a different identity). The validator returns "Unknown" as a conservative signal rather than "Valid".

There is no in-product mechanism to:

• Promote a connection from personal workspace to a shared folder
• Share a connection without recreating it
• Transfer the OAuth token to the new connection

Workaround

Recreate the connections in the target folder via Integration Service. Update bindings.json connection keys and any config defaults to use the new UUIDs. For local development, personal workspace connections work fine.

Suggested Fix

1. Product: Add a "Copy to folder" or "Share to folder" action in the Integration Service connections UI. The current requirement to recreate connections loses the OAuth token and forces re-authentication.

2. Validation UX: Surface a clearer warning in the Package Requirements screen:

   "This connection is in a personal workspace and may not be accessible 
   when the process runs as a robot in a shared folder. 
   Consider recreating this connection in the target folder."
   

   The current "Unknown" status is opaque — developers spend time investigating the binding format rather than the folder context.

3. Documentation: Document that connections for production deployments should be created in the shared folder (not personal workspace), and that this must be done before the package is deployed.

Impact

• Severity: Medium
• Every developer who builds locally with personal workspace connections hits this when moving to production
• The only fix (recreate the connection) loses the OAuth token and requires full re-authentication