Managing the shared reuse layer

In order to maintain the continued success of your shared layer and the App Factory program, it is essential to keep your shared layer current. Adding new components, in addition to updating existing components, can help you to scale your program and enforce organizational standards.

Identify trends

It is not uncommon for your shared reuse layer to start small, including only the essentials at the beginning. Growing your shared layer into a robust library of reusable assets takes time. It is important to stay connected with your Community of Practice to identify trends and common gaps in your reuse layer. Use these trends to prioritize the next set of assets and components to be added. If a large number of app makers are requesting similar functionality, this would indicate a priority candidate to be added to your shared layer.

Exposing new components

After a reusable component is added to your shared layer, how is this exposed to the app makers? App Factory uses a Pega Platform feature called Relevant Records. By marking a rule as relevant, this rule is now accessible for all applications built on top of your shared reuse layer.

It is important to ensure that you are marking the correct rule as relevant. For example, if you have a process that you want to make available for your app makers, you only need to mark the flow rule as relevant. Marking the referenced rules of the flow as relevant, such as flow actions, can clutter and confuse app makers. Ensure that the right set of rules are propagated to the app makers to reduce confusion. Providing informational descriptions on the relevant rules can also help.

Suggest Edit

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.