Ineffective: Metadata case sensitivity within EDM
We have noticed over time that Oracle metadata and corresponding properties are case sensitive and can cause issues if not typed exactly as it was created in downstream systems.
Content (please ensure you mask any confidential information):
Within EDM we use user defined attributes (UDAs) for department segment nodes. Those UDAs then get used in EPCM within allocation documentation. If the allocation in EPCM doesn't type the UDA exactly as EDM has created, the rule will not run. ex. EDM had departments using M_RIG_Scrum but EPCM in the rule was using M_RIG_SCRUM. How can we ensure this doesn't cause issues? Is there a functionality within EDM or downstream applications that could help prevent this complication?