Case and Flow Designing
Hi All,
I have 10 different Cases and each case has New, Renewal & Cancel functionalities/flows.
What is the best way of designing having Framework and Implementation layers ?
I am assuming that all 10 different cases will be at Implementation and common NEW,RENEWAL & CANCEL at Framework.Could someone please suggest a good feasible approach/solution/design.
Pegasystems Inc.
US
Are there any sibling dependencies between these 10 cases or can all 10 cases be maintained and executed independently within their own application?
If so you could define an application that defines the three stages - that application declaring it can be used as a built-on application within that application rule's Application wizard tab.
Each of the ten cases can be created within their own application, the previously mentioned 3-stage app being specified as the app to build on in the New Application wizard.
Each of these single-case applications would also declare that they can be used as a built-on application within their respective application rules.
You can then define an implementation/production app that is built-on these 10 single-case applications.
As opposed to defining a single framework app with 10 cases that have no dependency on each other - essentially defining a monolithic framework app, you instead build on 10 separately maintainable, testable, and deployable applications.
Other implementation/production apps can be defined that only require a subset of the 10 case types. Each case type app can be developed and tested by a different a Team.
When a case type is versioned, the application in which it is contained can be versioned.
DevOps pipelines are based on applications. it is simpler and more expedient to deploy smaller modular applications to a repository than one huge monolithic application.
Are there any sibling dependencies between these 10 cases or can all 10 cases be maintained and executed independently within their own application?
If so you could define an application that defines the three stages - that application declaring it can be used as a built-on application within that application rule's Application wizard tab.
Each of the ten cases can be created within their own application, the previously mentioned 3-stage app being specified as the app to build on in the New Application wizard.
Each of these single-case applications would also declare that they can be used as a built-on application within their respective application rules.
You can then define an implementation/production app that is built-on these 10 single-case applications.
As opposed to defining a single framework app with 10 cases that have no dependency on each other - essentially defining a monolithic framework app, you instead build on 10 separately maintainable, testable, and deployable applications.
Other implementation/production apps can be defined that only require a subset of the 10 case types. Each case type app can be developed and tested by a different a Team.
When a case type is versioned, the application in which it is contained can be versioned.
DevOps pipelines are based on applications. it is simpler and more expedient to deploy smaller modular applications to a repository than one huge monolithic application.
Also, other development teams on their own development servers can point to the server where each case-type specific application is developed then do a rebase of that application from the application rule present on their server.