Skip to main content


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

Managing application inventory

Updated on December 6, 2021

Plan the development of your application, manage the workload in your team, and prioritize your work accordingly by following the application backlog on your Inventory landing page. The Inventory landing page lists features, personas, and draft data associations across your Microjourney, so that your team can map items to specific releases.

By analyzing the application inventory, you can also determine how different elements of your application, such as personas and case types, interact with each other.

You associate personas and data objects with case types when you plan your Microjourney. By making these associations, you can clearly visualize the data and participants that your business processes require. After you create these associations, or draft relationships, you can analyze your application inventory, so that you can prioritize work by checking releases associated with personas and data objects. You can also group and filter personas and data objects for a better understanding of how these elements are related. For more detailed planning, on the Inventory page, you can also manage your application features. For example, you can associate a feature with a release, so that you can estimate your work more accurately.

Before you begin: Define the main elements of your application:
  1. In the navigation pane of App Studio, click Overview.
  2. In the Application profile section, click Manage.
  3. On the Inventory tab, in the Inventory section, select the items of information that you want to view:
    • To manage draft personas, click Persona.
    • To manage draft data objects, click Data.
    • To manage application features, click Features.
  4. Organize the list of items to display only the information that you need:
    • To group items, click Group, and then select the grouping method that you want to apply, for example Complexity.
    • To display only selected information about items, click Fields, and then select the fields that you want to display, for example Channel and Status.
    • To change how the information is displayed, click Density, and then select a format that you want to apply, for example Compact.
  5. Update the information to reflect the latest changes that you make in your application by clicking Edit details, and then performing the following actions in the Edit details window:
    • To change the iteration of your application in which you want to implement the item, in the Release list, select a release.
    • To change the amount of time that the development team needs to implement the item, in the Complexity list, select a new value.
    • To provide more information about an item, such as business value, in the Comment text box, enter some additional description.
    • To mark the item as implemented, select the Mark as done check box.
  6. Click Submit.
For example: The following figure shows the Persona of an application inventory with personas associated with case types in the application. In the example, the inventory applies grouping by a case type.
Application inventory
The Persona tab of the application inventory.

Adding features to application inventory

Get a quick overview of the functionalities that your development team needs to implement by adding features to your application inventory. When you analyze your application inventory, you can conveniently plan your application development in a more detailed way.

For example, you can create features that represent language packs and case types to ensure that you deliver an application that meets the requirements defined with your stakeholders. During application development, your team then turns features into usable functionalities.
Before you begin: To reuse features, add built-on applications to your current application. For more information, see Adding built-on applications.

You can assign each feature a complexity level. Complexity indicates the time and effort that a team needs to implement a feature and impacts further estimation of the time required for application development.

  1. In the navigation pane of App Studio, click Overview.
  2. In the Application profile section, click Manage.
  3. In the Inventory section, click Feature map.
  4. Add a feature to your application:
    ChoicesActions
    Reuse a feature from a built-on application
    1. Hover over the features list, and then click AddAdd from existing features.
    2. In the Add from existing features dialog box, in the Feature list, select a feature to reuse.
    3. Optional: To manage your features in a more convenient way, from the Category list, select a category that best describes your feature.For example: Select Security.
    4. In the Release list, associate the feature with the iteration of your application.
    5. Optional: To modify the feature for your current application, in the Complexity list, select an option that indicates how much time a development team needs to implement the feature.
      Feature complexity impacts estimation of project completion time. Complex features elongate the estimated application development process.
    6. Optional: To provide more information about the feature, in the Comment text box, enter some additional description.For example: Enter text that describes the business value of this feature and provides an overview of what users can do when the development team implements the feature.
    7. Optional: To communicate that the feature is ready, select the Mark as done check box.
      Features that you mark as done have no impact on development time estimations.
    8. Optional: To add more features, click Submit & add another, and then repeat steps 4.b through 4.g.
    9. Click Submit.
    Create a new feature
    1. Hover over the features list, and then click AddAdd new feature.
    2. In the Add new feature dialog box, in the Name field, enter some text that uniquely identifies the feature.
    3. Optional: To manage your features in a more convenient way, from the Category list, select a category that best describes your feature.For example: Select Security.
    4. Optional: To associate the feature with the iteration of your application, in the Release list, select a release.
    5. To indicate how much time a development team needs to implement the feature, in the Complexity list, select a relevant option.
      Feature complexity impacts estimation of project completion time. Complex features elongate the estimated application development process.
    6. Optional: To provide more information about the feature, in the Comment text box, enter some additional description.For example: Enter text that describes the business value of this feature and provides an overview of what users can do when the development team implements the feature.
    7. Optional: To communicate that the feature is ready, select the Mark as done check box.
      Features that you mark as done have no impact on development time estimations.
    8. Optional: To add more features, click Submit & add another, and then repeat steps 4.b through 4.g.
    9. Click Submit.
For example: The following figure shows the Features tab of the application inventory, with features grouped by category:
Features in an inventory
Application inventory with features grouped by category.
What to do next: Calculate the time and effort that you need to deliver your application. For more information, see Estimating application development.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us