2STUDIO5 Qut Systems
OutSystems Service Studio 4.1 Help
Overview of eSpace Life Cycle
The diagram below represents the eSpace life cycle.
In this diagram you can easily identify two different cycles for both single and multi-developer environments: the personal cycle and the team cycle. The personal cycle concerns the iterative process where the developer is designing the eSpace and running it in a Personal Area, protected from the rest of the developers. The team cycle, on the other hand, is the iterative process where all the developers collaborate to publish a single version of the eSpace, available to all developers and end-users.
If you are working in a single-developer environment you can also take advantage of both cycles, since you might want to experiment and evaluate the eSpace without interfering with the version that end-users are using, therefore running it in your Personal Area. There are performance benefits in the development process if you decide to run the eSpace in your Personal Area.
The personal cycle allows each developer to design his/her own eSpace and experiment with it in their own Personal Area. The Personal Area is an area stored in the OutSystems Hub Server you are connected to and with reserved rights concerning its management.
The Personal cycle, fully supported by OutSystems Service Studio, is divided into the following steps:
Design the eSpace in your workspace. See how to Design the eSpace
Run the eSpace in your Personal Area. See how to Run the Personal Area
Collect the feedback from this personal test and do one of the following:
Return to step 1.
Publish your eSpace, making it available to all users, as explained below in the Team cycle.
Once you have run the eSpace in your Personal Area, you can test it. See Execute the eSpace in Personal Area.
The team cycle allows developers to publish eSpaces in the Publish Area, which is an area stored in the OutSystems Hub Server you are connected to, available for all developers and users.
The Team cycle, fully supported by OutSystems Service Studio, is divided into the following steps:
Design the eSpace in your workspace. If you are working in a multi-developer scenario, each developer will design components or parts of the application. See how to Design the eSpace
If you are working in a multi-developer scenario, aggregate the developer contributions in a single eSpace, using the Multi-developer tools provided by OutSystems Service Studio.
Publish the eSpace in the Publish Area. See 1-Click Publish.