Oracle Agile ACP utility and it associated Document process
I am working on Best practices of capturing Agile Business configurations. As of now there is not standard approach.
Most of us manage the configurations release wise in Excel template prepared based on Admin reports. Some of us document by copy, paste the configs from Java Client.
Configuration associated with PX
Configurations associated with Modifications as per security data model
Configurations OOTB
Every release has code, configurations and documentation FSD, TSD.
Oracle provides ACP, But it has it own set of complexities, How it can be
managed to be part of CIs with other collateral and maintain traceability.
However, ACP utility and its associated supporting document for traceability is a area that has scope of simplification.
Can you please share thought and ideas for Best practices. As the ACP and document have to be managed environment wise, release wise.
How we can achieve continuous release model and maintain configuration changes at traceability for every issue, bug fix and enhancements.
Honestly Paritosh I have seen this handled in a few ways. Having many conversations where admins point to the out-of-box reports. Others using a series of complex spreadsheets to manage. Personally I have even considered creating a second database to track all the joins and dependencies. At the end of the day this is a fairly large commitment and you will need to ask yourself if all the work is worth the benefit. Even though Admins struggle at times, they always seem to overcome so there has never been a sufficient ROI to pursue this rigorously.
I am not sure, how soon oracle agile will be transformed into fully developed cloud application. In any case, Devops model will be defacto for Agile software development mode.
I was tinkering on how agile plm admin and development can be boxed i