Question1Replies222Views SreekumarK8778 Member since 2014 10 posts GM Onstar Posted: 3 years agoLast activity: 3 years 2 months ago Closed Best practices of packaging application and its dependenciesBest practices of packaging application and its dependenciesWe have a number of applications that reuse common components. There are few options how these dependencies created:Package each component in its own Ruleset and include this Ruleset in the new application Ruleset stackExample“Application 1”App1App1IntApp1DataAppCommonDataAppCommonIntService1RulesetService2Ruleset“Application 2”App2App2IntApp2DataAppCommonDataAppCommonIntService1RulesetService2RulesetPackage all common components in single application (of type framework) and “built on” the new application on this frameworkCommon FW appAppCommonDataAppCommonInt“Application 1” built on “Common FW app”App1App1IntApp1DataService1RulesetService2Ruleset“Application 2” built on “Common FW app”App2App2IntApp2DataService1RulesetService2RulesetPackage each component in its own application and “built on” the new application on all common components applicationsItem 3 exampleService1 AppService1RulesetService2 AppService2RulesetCommon FW appAppCommonDataAppCommonInt“Application 1” built “Service1 App”, “Service2 App”, “Common FW app”App1App1IntApp1Data“Application 2” built “Service1 App”, “Service2 App”, “Common FW app”App2App2IntApp2DataWhat is the best practice from prospective of code maintenance and deployment? Low-Code App Development Low-Code App Development Installation and Deployment ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoSudhakarReddy PEGA replied to SreekumarK8778Hi, Please use the reusable components in organisation level or unit level, these are going to helpful for all applications specific to that organisation or unit.