Application Object

Updated 1 week ago by Copado Solutions


Many companies are beginning to manage their innovation centers as a product organization. This includes treating their applications as “products” and being able to categorize their work as applications, features, and user stories. The top level concept is that of an application. This is often a single application, but it could be a collection of sub-applications or in the case of Salesforce, something as fuzzy as Sales Cloud. The application context data model looks like this: 

Application object relationship diagram

What Is An Application?

An application or product is produced to create value for a group of customers and to the organization it provides. An application can be made up of many sub-applications which can also contain features. An application needs a name that people can remember and should clearly have benefits for the customer defined. An application should adapt with time, trends, and changes to the market in order for it to stay relevant. An application may or may not have a revenue stream. 

Application vs. Project 

A project is a defined scope of work that is to be delivered and completed in a specific time frame and with a specific budget. Projects have a well-defined beginning and end. Applications can continue to live beyond a specific start and end date. Applications continue to be developed and can live until their end of life. 

Copado Application Object

Application relationships


Copado enables you to track everything related to your applications. You can group your user stories into applications, sub-applications and features.

Application record Details page

On the Application detail page you can find relevant information about the app, such as the name, the description, the product manager and its related parent application, if any. The Description field will give you the opportunity to add more details about your application with rich-text input. 

You can use the Stability field to define the operational status of your application and specify if it is: 

  • Stable
  • Uncertain 
  • Unstable.

You can also indicate the release status of your application and sub-applications with the Release Status field. Applications and products released go through several phases during their life. These are the phases an application’s release status goes through:

  • Definition
  • Development
  • Pilot 
  • Beta
  • GA (General Availability)

If your application has been released to all customers, you can select GA (General Availability). If the application is still being defined you can choose Definition or Development. You may have built a pilot project or released a beta version for a specific group of users to try it before it becomes available to everyone, in which case you can set this field to Pilot or Beta.

Sub-Applications, Features, and Epics

The Application record includes three related lists, Sub-Applications, Features and Epics

If your application is made up of smaller apps, you can link them via the Sub-Applications related list. If you want to see all the features that are part of an application, you can easily do that from the Features related list, This is what the Application record looks like.

Sub-application, feature and epic related lists

How did we do?