Accessing Dev Studio features in App Studio

From PegaWiki
This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search



Description Using Dev Studio to develop application functionality in App Studio
Version as of 8.5
Application Platform
Capability/Industry Area Low-Code Application Development



Until App Studio is completely built out you will find yourself having to go into Dev Studio to complete some work. That's perfectly reasonable, but it's important to keep some things in mind, so that the functionality that you build surfaces itself in App Studio as well as it can.

Before you begin[edit]

Firstly, if you're unclear whether a specific piece of functionality is available in App Studio, please ask. You can ask questions at the Collaboration Center.

If you are certain that the feature doesn't exist in App Studio, ask yourself:

  • What is the priority of this requirement?
    • Could it be moved to the next MLP?
    • Could this requirement be met in a slightly different way using capabilities that do exist out of the box (OOTB)?

Process/Steps[edit]

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.
  • 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.

Results[edit]

  • Ultimately, we are responsible for helping our clients build applications using best practices that are as easy to upgrade and maintain in the future as possible. Best practice means using OOTB App Studio features as often as possible.
  • In the end, it is critically important that App Studio accurately reflects the application in terms of case types, data objects, personas, channels, etc. If you can't look at the app and understand it in App Studio, you aren't doing it right.

Call to Action: We are looking for examples of Dev Studio functionality built in a way that surfaces in App Studio. Please submit your examples!

Related content[edit]