When designing an eSpace use the Run and Debug in the '<user>' Personal Area (or simply called Run) operation to execute and test the eSpace.
Use this operation instead of the 1-Click Publish when you don't want that your changes interfere with other developers' work since the eSpace is hosted in your Personal Area. However, unlike the 1-Click Publish, the eSpace versions that you Run are not stored in the Platform Server and you won't be able to download or roll back to any of them.
Running the eSpace
To run your eSpace proceed as follows:
Open the Debugger menu and select the Run and Debug in the '<user>' Personal Area option (or use the F6 shortcut key);
If you aren't connected yet to a Platform Server, you're presented with the Select Server Window: select the server, enter your credentials, and establish the connection.
The progress of the run is displayed on the Run tab of the Lower Pane.
In case of success, select the Entry Point from the Entry drop list and click on Open in Browser button.
The Entry drop list contains all Entry Points of the Entry eSpace: by default it is the current eSpace, however, if you have consumer eSpaces, you are allowed to select one of them as the Entry eSpace and choose another Entry Point, changing the life cycle of your eSpace to the life cycle of a Producer eSpace.
Learn how to Debug Reused eSpaces.
In case of errors, your eSpace is invalid, and you have to fix all errors and then click on the Retry Run button on the Lower Pane.
Besides running an eSpace in your Personal Area, you can also execute it in the Public Area. Learn more about Executing an eSpace.
Detailing the Steps of the Run
The operation of running an eSpace involves the following steps:
Save: this is an optional step that is performed only if your eSpace was opened from a file or was already saved to a file.
Updating: uploads and updates the eSpace in the Personal Area of the Platform Server you are connected to.
If the Entry eSpace is a Consumer eSpace, then it is also updated in the Personal Area. Learn how to Debug Reused eSpaces.
Finally, the Debugger is started so that you can debug your eSpace in your Personal Area.
Because the OutSystems Platform Database is shared between the Public Area and the Personal Areas, the Run operation fails if one of the following is occurring:
Another developer is executing a 1-Click Publish of the eSpace;
Another developer is connected to the Platform Server with your credentials and is executing the Run of the eSpace.
Permissions for Running
To execute the 1-Click Publish operation you must have the following permissions:
If using LifeTime: either through the Applications page or the Users & Roles page; you must have (at least) the Change & Deploy security level for the application of the eSpace; if necessary, contact your administrator to grant you the required permissions.
If not using LifeTime: check your permissions in Service Center in the My Settings link (at the top right corner) and check out your Security Settings, eSpaces Granted, Extensions Granted and Solutions Granted; you must be a Developer and have (at least) the Publish security level for the eSpace; if necessary, contact your Service Center administrator to grant you the required permissions.
Debug an eSpace | Select an Entry eSpace | Executing an eSpace | Personal Area | Public Area | Overview of eSpace Life Cycle