0 Replies Latest reply on Jul 15, 2013 1:37 PM by ltan

    Design Recommendations for Evolving Business Needs


      Hi All,

      Over time it is feasible that business needs will evolve. This could include changing the data that is captured within business processes as well as workflows, changing core shell information, to having to reorganize the initially designed shell hierarchy.

      Wanted to find out from past experiences what guidelines/best practices/considerations there could be to prevent unintentionally designing shell hierarchy, shells and business processes that are either too inflexible for change or create major effort and rework in implementing it?


      Look forward to hearing any thoughts around this.


      Many Thanks