Preventing users from requesting to add the same member(s) across different requests
Hello EDM Team - we wanted to present an idea that came out of a recent governance process design cycle. Would it be possible in the future of EDM to reserve member names that are currently in flight? Or prompt a warning to the user that the member is not yet committed to EDM but it is currently being used in another request?
The issue we are trying to avoid is multiple users submitting requests to add the same GL segment value during a monthly governance cycle. This will be especially prevalent for organizations that use numeric range naming conventions for their GL segment values. If we take an example of 2000-2999 is the range for COGS Cost Centers and currently 2000-2100 are all used already, the next logical member to add would be 2101. If there are multiple end users submitting requests for new COGS CC’s in a month’s cycle, they will all see that the next logical segment value to add