We're currently exploring options on how to implement Source Control for all changes in code in the Hyperion Essbase & Planning (along with DIM). We plan to put everything that is changing into a Source control software including Rule Files, Calc Scritps, Report Scripts, Business Rules, Planning Forms, DIM Workflows, Mappings etc. Is there anyone who has implemented this and have a structure on what all can be source controlled and what cannot be? Also, any lessons learned that could help us plan better would be greatly appreciated.
Red Flag Submitted
Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Tek-Tips forums is a member-only feature.