Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
This idea has been merged into another idea. To comment or vote on this idea, please visit CONC-I-1886 Multiple Salesforce IDs in a Concourse Project Space.
Put Simply:
The current 1:1 relationship between Salesforce Opportunity ID (SFID) and Concourse workspace blocks the ability to recreate or relaunch engagements during pilot testing, specially when the workspace creation fails.
Why it Matters:
Piloting requires frequent workspace recreation, but without the ability to link multiple workspaces to the same SFID, teams are unable to launch ePro. This stalls progress and creates manual workarounds.
Additional Context:
Each SFID can currently only be tied to one workspace.
During pilots, workspaces are frequently deleted or recreated, but SFIDs remain unchanged.
The inability to reuse SFIDs for new workspaces blocks downstream actions like ePro launch.
Acceptance Criteria:
Make SFID available for use, if the workspace using the SFID
has failed,
is closed
is a test workspace
Ensure system can differentiate between active and inactive workspaces tied to the same SFID.
Provide mechanism to clean up or archive deprecated workspaces post-pilot.
Guest
A salesforce ID can be used to create only one workspace, but given we are piloting there is a constant need to recreate the workspaces and we are unable to tie it back to the SFID and not having an id blocks the ability to launch epro.
Can we temporarily lift the 1:1 relation between SFID - Workspace and make it 1:Many
Closing this request as it was identified during pilot and is working as designed for the system. The long term solution around SF IDs will be tracked via https://pwc.aha.io/ideas/ideas/CONC-I-1886 . Please navigate to Idea 1886 "Multiple Salesforce IDs in a Concourse Project Space", review, upvote and add any comments if you are interested in a similar idea.