. The maximum size of this property is 255 characters. OutSystems Service Studio 4.1 Help
eSpace Properties
To access the properties of an eSpace (An application or a part of an application that implements a set of services, gathered in a single project. Each service can be presented in a different flow.), you have to select the eSpace, in the eSpace tree, and set the properties directly on the Properties window or by pressing More....
The eSpace properties are described below.
Name of the eSpace. See rules for naming elements.
Free text that describes the eSpace. Useful
for documentation purpose. You can edit the text by directly typing it
in the property or in the description editor which opens by clicking . The maximum size of this property is 255 characters.
Database type considered by developers when writing the SQL in advanced queries. This property is merely informative and is important for communication and knowledge transfer between developers. The possible values are: SqlServer, Oracle, or (both).
In addition, OutSystems Service Studio executes some validations to your advanced queries to check if the SQL you type-in is compliant with the Database type specified in this property. If this SQL is not correct, a warning message is presented and you should fix your statements.
The Database property must be according to the OutSystems Hub Database, otherwise a warning message is presented and you should either specify the exact database type or select (both). Also you should confirm that your advanced queries are compliant with the database.
Indicates in what application server environment the eSpace is ready to run. The possible values are: .NET, J2EE, or (both). This property allows Service Studio to validate your eSpace concerning the application server, for example multi-tenant eSpaces are not allowed in a J2EE application server. It is also important for communication and knowledge transfer between developers.
In addition, OutSystems Service Studio executes some validations to check if your eSpace is supported in a J2EE application server. For example, if you are using the IntegratedSecurityGetDetails action, a warning message is presented since Integrated Authentication is not implemented in J2EE application servers.
The Application Server property must be set according to the OutSystems Hub Server, otherwise a warning message is presented and you should either specify the exact application server or select (both).
Indicates whether the eSpace is multi-tenant or not. By default, an eSpace is single-tenant. Learn more about multi-tenant eSpaces.
Multi-tenant eSpaces are only available in .NET environments, therefore when the Application Server Type has the value J2EE or (both) an error message is presented.
Indicates whether the eSpace can share its end-users with other User Subscriber eSpaces, enabling the end-user to authenticate once, in one eSpace, and gain access to the any unified eSpace . Learn more about Single sign-on.
Indicates the eSpace that provides end-users to this eSpace, enabling the end-user to authenticate once, in one eSpace, and gain access to the any unified eSpace . See Select User Provider eSpace.
List of the locales (String that uniquely identifies the language as specified in RFC 1766 standard.) to which the eSpace is localized (Add support for a specific language or locale to a multilingual application.) when it uses multilingual support. By default, this property is empty. Once you add multilingual resources (language resources (Files packed with the oml that contain the text translations for the languages supported by the eSpace. You must have a resource file for each language.) or image resources (Files packed with the oml that contain the images translations for the languages supported by the eSpace. For each localized image, you must have a resource file per language.)) to the oml (Stands for: OutSystems Markup Language), through the Multilingual command line tool, this property is automatically updated with the languages of the added resources. Learn more about Multilingual Support.
Read-only.
Default Validation Messages for inputs
Available when you press the "More..." button, in the Web Validation tab.
List of default messages presented at runtime when the validation fails. You can change these default messages here.
This property only applies to Web flows.
Available when you press the "More..." button, in the SMS tab.
Default encoding used by OutSystems Platform when sending an SMS. If not specified, all the SMSs are sent with this encoding.
Available when you press the "More..." button, in the SMS tab.
Default phone slot that handles the SMS. This property allows you to overwrite an SMS previously sent. The possible values are:
(None): no specific phone slot is used.
1 , …, 7: the message is sent to the phone slot you specify.
Learn more about replacing an SMS previously sent.
Available when you press the "More..." button, under the SMS tab.
Indicates whether the result of the delivery report is registered or not by OutSystems Platform. The possible values are:
Off: The result of the deliver report is not registered.
Failure only: The result of the delivery report is registered only when the message was not delivered. The Delivery Report system action, if it exists, is executed for the messages that failed.
On: The result of the delivery report is always registered. The Delivery Report system action, if it exists, is always executed (even for the messages that failed).
When you use delivery reports,
you must be aware that this feature has a considerable impact on performance.
Available when you press the "More..." button, in the Mobile Web tab.
Indicates the maximum width, in pixels. that a standard device supports. This parameter helps you define the height and width of your images. When the Width property of the Image created in the eSpace is bigger than this parameter, OutSystems Service Studio presents a warning message.
Available when you press the "More..." button, in the eSpace JavaScript tab.
JavaScript code that is global to your eSpace, i.e. you can invoke these JavaScript functions in any element of your eSpace. At run-time, the eSpace JavaScript code is placed in a separate file, the reference for which is added to each HTML page generated by OutSystems Platform.
Available when you press the "More..." button, in the Advanced tab.
Allows you to specify how the session identifier is exchanged between the Web browser and the OutSystems Hub Server. The session identifier is sent to the browser on its first request and, from then on is used in each interaction. This identifier allows OutSystems Hub Server to retrieve session variable information for each user. Learn more about Hub Server session.
The possible values are:
If this option is unchecked, which is the default, the session identifier is sent back and forth in the URL. For example:
http://hostname/app/(5hig6h65u3acnfup5oeaox45)/Home.aspx
Sending the session identifier
in the URL is available only in .NET environments, specified by the Application Server
Type eSpace property. If this property has
the value J2EE or (both)
a warning
message is presented, notifying you that, in the J2EE environment,
the session identifier must be sent in a Web Browser Cookie.
If this option is checked, then the session identifier is exchanged through the Web Browser cookies. The URL will then look something like:
http://hostname/app/home.jsf
This way of managing the session identifier allows you to have more understandable URLs as well as being a more standard and secure form of handling this information.
You cannot use cookies in
SMS flows and, if you try to do so, an error
message is presented to you. Furthermore, it is not advisable that
you use cookies in Mobile Web flows as some mobile devices do not support
cookies. In this case, a warning
message is presented.
You can, therefore, only use cookies safely in eSpaces that have exclusively Web flows.
Available when you press the "More..." button, in the Advanced tab.
Allows you to specify how web screens are handled by the Web Browsers. By default, this property has the value Standards.
The possible values are:
Standards: the browser will comply with W3 Standards, using the following doctype:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
See how HTML Tags are generated for this mode.
Quirks: the browser will comply with older browsers' behavior, using the following doctype:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
See how HTML Tags are generated for this mode.
eSpaces from releases prior
to 4.0 were generated for older browsers so they are upgraded to Quirks
rendering mode to maintain compatibility.
See Also