GUIDS, Config Portability, and Rules need a data resolution solution to span platforms

We’ve had severe issues with GUID mismatches/duplication, config portability, and rules since 9.1.8. Some of the direction provided for backfreshing is just down right impractical for very active system like ours.  What is needed is a very granular repair process for GUIDs across the typical 3 design platforms (Dev, PLTE/TEST, Prod).  There should be something like a dependency diagram that you can map the data across the three platforms (Dev to PLTE and Dev to Prod) and dynamically fix and/or re-route error situations.  There should also be a method to create exceptions based on platform so Dev, PLTE, and Prod security can be unique to purpose which would allow everything to be ported.  Items (screens/workflows) that have unique security based on platform (Person Details for example) need to have config portability update what is ported to match what is in the dependency diagram for each of the platforms.

  • Guest
  • Aug 11 2017
  • Reviewed by Alemba Product Manager
  • Attach files