View source for Accessing Dev Studio features in App Studio

Accessing Dev Studio features in App Studio / ← Surfacing Dev Studio in App Studio

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in one of the groups: Users, editor, pegaemployee.
• The action you have requested is limited to users in one of the groups: pegaemployee, editor, Administrators.

---

You can view and copy the source of this page.

== Process/Steps == If there is no way around using Dev Studio, make sure to develop the functionality in Dev Studio so that it is a reusable piece of functionality that enhances the App Studio experience. Here are some things to keep in mind: * Embellishment of an application in Dev Studio needs to be done in a way that enhances the App Studio experience by providing, for example, more reusable assets in the form of flow utilities, new step types, or a new UI template. ** You can surface some rules and features in App Studio see [https://community.pega.com/knowledgebase/articles/application-development/86/relevant-records-rule-reuse Relevant records for rule reuse]. * If you are building in Dev Studio, only do as much work as you have to and then move back to App Studio as soon as possible. * Try to use OOTB App Studio features as much as possible - especially for MLP1. Making something work with an existing product capability is more valuable than bending to an exact specification from a client. Sometimes you will be able to provide something that is even better (not to mention more upgradable) by using the OOTB features.

Return to Surfacing Dev Studio in App Studio.