Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Creating a safe playground

Updated on December 13, 2019

The shared reuse layer is not only for reusable components. It is equally important to use this layer to provide a safe playground for your App makers. The environment in which makers build their applications should not allow them to get into trouble.

Enable security

How can security settings be configured for the entire low-code, citizens developer program? This can be solved in the shared reuse layer. Create template access groups for each potential role. Give these roles the expected privileges and access. App makers can then extend the templates for the roles that they need. By creating access templates, the risk for security configuration issues are greatly reduced. Access templates also allow for predefined roles and privileges to be reused. This is especially important when setting up reusable assets, which require security.

Practice managers can also configure authentication services in your shared layer. For example, Sample Inc. wants to use single sign on (SSO). The practice managers configure the authentication service for single sign on. All of the applications on the system can then begin using SSO. Having this configured in the shared layer allows a single source of truth for authenticating users across all applications. Additionally, the app makers do not have to configure this on their own, which can require technical expertise.

Document best practices

It is important to document the best practices recommended by the practice committee and coaches. This helps to guide app makers when they build their own applications. Policies for naming conventions and case structures can help to keep standards, quality, and ease future maintenance in the applications.

One way to expose best practices to the app makers is through extending the App Studio help link. The help link is accessed when in edit mode by clicking the question mark icon at the top of the page.

Help link location

This launches the help page, which is displayed in the following image. Adding your best practices in this location provides an easy avenue for guiding app makers when building applications. If the help links are extended at your shared layer, all App makers can see the added help articles.

Getting started page

To learn more about extending the App Studio help links, see Data-driven UI framework.

Configure App Studio options

App Studio is the easiest and fastest way for app makers to build their low-code applications. The options presented to them in App Studio can be configured in the shared layer.

For example, you might want to disable the ability for app makers to add users to their application. You can hide this page at the shared layer to disable it for all low-code applications. For more information on how to configure App Studio, see Customizing App Studio.

Configure New App Wizard options

In a low-code App Factory program, you will often create new applications. Your organization might have specific requirements that are captured as a part of the Pega New App Wizard. This wizard can be extended to meet the needs of your organization. For example, Sample Inc. might want to capture a mission statement for each application.

For more information on how to extend the New Application Wizard, see Extending the New Application wizard.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us