Adding more flexIDs to one Concourse workspace

We found a very common case that an engagement will get a new FlexId when renewing the contract. But team won't create a new workspace on Concourse. Therefore the new created flexID won't have a concourse workspace tie to it. Manual mapping is time consuming and easy to make mistake. it would be very helpful to allow user add a new flexID to the existing workspace.

Natasha Liu
Mar 17 2022
Released

New Idea

Post comment

Admin

Courtney Powers commented

April 14, 2023 18:04

Hi everyone! Thank you again for voting and commenting on this idea! Good news, this feature has been released, you can now add up to 3 Flex IDs to a workspace! Click here to see the Yammer post announcement and check out this gif to get started!

Attachments Open full size
Vieroslava Figueroa commented

February 06, 2023 18:44

Is there an ETA for when this is planned to be released?

Attachments Open full size
Peter Dela Cruz commented

November 14, 2022 18:04

C&DS needs this...for change orders, extensions, and when FLEXIDs change

Attachments Open full size
Giuseppe Mangano Hillman commented

October 19, 2022 16:18

We need this too. Thank you.

Attachments Open full size
Sarath Chand Kasinadhuni commented

August 30, 2022 17:56

Totally agree, it makes better sense to map the Concourse Workspace to the contract vs individual flexes/wbs codes within the same contract.

Attachments Open full size
Alice Louie commented

August 30, 2022 17:39

Please allow multiple flexes, multiple codes to be associate with 1 concourse file. For recurring engagements such as SOX, IA, compliance, we need to modify throughout the year. Just spent 30 mins. updating concourse trackers for each line item.

Attachments Open full size
Missy Wilson commented

July 20, 2022 14:21

Thank you for submitting this idea - we’re excited to see the interest it generated! We recently established a Concourse research team that is completely focused on exploring user generated ideas like this. They recently released this survey to gather additional feedback. If you haven't already done so, please respond to the survey so we can move this idea forward!

Attachments Open full size
Ann Lang commented

June 21, 2022 15:39

Agree. This is causing a lot of unecessary admin work

Attachments Open full size
Eric Lucha commented

June 21, 2022 13:49

Second Jen's comment - this is an extremely common issue and is causing end user struggles for the adoption network. If there's any way we could prioritize this functionality for the next release, I would be a strong supporter of that change.

Attachments Open full size
Jennifer Schulte commented

June 21, 2022 13:30

I agree. Additionally, we often have client projects where we create multiple Flex IDs for various workstreams but all the work is tied back to one contract/SoW.

1) We need Concourse to be configured so our teams can enter more than one Flex ID when they create a Concourse workspace.
2) and they need to be able to modify the Flex IDs after the Concourse workspace is created, so they can add new Flex IDs in situations where the Flex ID wasn't available when the workspace was created (i.e., it didn't exist yet).

Attachments Open full size