The OutSystems Platform allows you to easily develop, deploy, and monitor your web and mobile applications.

The goal of this guide is to demonstrate what the OutSystems Platform can do for you. It is not intended to be a detailed tutorial, an installation guide, or reference guide. If you want to learn how to set up the OutSystems Platform and start developing your own applications, go check the online training.

Instead of reading about OutSystems Platform benefits and features, lets see a typical use case in action.

1. Develop the App

Lets say your sales team has asked you to create a new mobile application to manage accounts, contacts, and opportunities.

Instead of diving head-first and create everything from scratch, OutSystems incentives you to reuse existing apps and components made by the community, and to customize them to your needs.

So in your development environment:

  1. Connect to your environment;
  2. On your application list, click 'Install';
  3. Search for the 'Mobile Sales' app, and click 'Preview' to try it online;
  4. Click on 'Instal...' to install it on your environment.

After the application is installed notice that:

2. Deploy the App for Testing

To allow the sales team to test the application, let's deploy it to a testing environment: Quality Assurance.

  1. In your environment management console, click 'Manage all environments' at the right hand side to navigate to the infrastructure management console;
  2. Click on the Mobile Sales Application;
  3. Click 'Deploy...' to deploy it to Quality Assurance.

3. Change the App

The sales team is impressed with the application. They only asked if we could emphasize the company address since it's too small. Since we want to delight them, lets display the address on a map:

  1. Install the 'GoogleStaticMap' component from the Forge;
  2. In the Sales app, create a dependency to the newly installed component (using the button);
  3. Drag the map block to the screen;
  4. Fill-in the parameters;
  5. Remove the text that was displaying the address;
  6. Publish the new version.

4. Deploy to Production

Again, lets push the application to Quality Assurance using the infrastructure management console. The team tests it, and everyone is excited. So it's time to deploy our application to Production, the environment where end-users are going to use the application.

The only problem is that this time we don't have permissions to do so. We need to ask Jane from the Operations Team to do it for us.

Jane deploys the Sales application to Production, using the infrastructure management console.

5. Do Runtime Configurations

When Jane finishes deploying the application, she still needs to perform some runtime configurations.

In this case she configures the way currency values are displayed in the application. The application centralizes the logic to format currency values in a single place, and makes it customizable at runtime. When the deployment is finished:

  1. Click 'Configure' to go to the Production environment management console;
  2. Click on 'Site properties';
  3. Clear the value of the 'GroupSeparator' variable.

6. Monitor the App

The infrastructure management console allows Jane to have a birds-eye view on the performance of all applications. At any time she can see if the performance of an application has decreased, or if it has any errors.

To ensure we know if our application is being adopted by the sales team, and if the application performance decreases over time, Jane sends us a weekly performance report.

7. Get Feedback from End-Users

To get end-user feedback about Mobile Sales, Jane does the following:

  1. Opens the infrastructure management console;
  2. In the environment she wants to get feedback about the application, she opens the drop-down menu, and selects the feedback option;
  3. Then she enables feedback for the Mobile Sales application and sets which end-users can submit it.

Learn more about handling user feedback.

See Also

Workspace Overview