.To access the properties of a module, you have to select the module
name in the tree on the right, and set the properties directly on the
Properties pane, or in some cases by clicking .
The eSpace properties are described below.
Name of the module. See rules for naming elements.
Free text that describes the module. 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 2000
characters.
Indicates the DBMS type considered by developers when writing SQL. This property is merely informative and is important for communication and knowledge transfer between developers. The possible values are: MySQL, Oracle, SqlServer, or (All).
In addition, the development environment executes some validations to your SQL queries to check if the SQL you type in is compliant with the DBMS type specified in this property. If this SQL is not correct, a warning message is presented and you should fix your statements.
The DBMS property must be according to the OutSystems Platform Database, otherwise a warning message is presented and you should either specify the exact database type or select (All). Also you should confirm that your queries are compliant with the database.
Indicates in what application server environment the module is ready to run. The possible values are: .NET, J2EE, or (both). This property allows the development environment to validate your module concerning the application server, for example multi-tenant modules are not allowed in a J2EE application server. It is also important for communication and knowledge transfer between developers.
In addition, the development environment executes some validations to check if your module 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 Platform Server, otherwise a warning message is presented and you should either specify the exact application server or select (both).
Indicates whether the module can share its end-users with other User Subscriber eSpaces, enabling the end-user to authenticate once, in one module, and gain access to the any unified module. Learn more about Single Sign-On.
Indicates the module that provides end-users to this module, enabling the end-user to authenticate once, in one module, and gain access to the any unified module. Select end-user provider from the modules in the list; by default its the module itself. Learn more about Single Sign-On.
The icon identifies the module in the element tree of the development environment.
Allows you to specify:
The Default Theme for your application screens. Learn more about Themes;
The version of jQuery that is used in all web screens of the module. Learn more about the jQuery API.
Web global JavaScript for your module. Learn more about JavaScript.
Double-click on the property name or click
on to open the JavaScript editor.
List of default messages presented at runtime when an input validation fails. You can change these default messages here.
These properties only apply to Web Flows.
List of properties applied to your module's SMS design.
Default encoding used by OutSystems Platform when sending an SMS. If not specified, all the SMSs are sent with this encoding.
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.
Indicates whether the result of the delivery report is registered or not by OutSystems Platform. The possible values are:
Off: the result of the delivery report is not registered.
Failure only:
the result of the delivery report is registered only when
the message is not delivered and the 
OnDeliveryReport
action (if it exists) is executed for the messages that failed.
On: the result
of the delivery report is always registered and the
OnDeliveryReport
action (if it exists) is executed for all messages (even for
the ones that failed).
When you use delivery reports, you must be aware that this feature has a considerable impact on performance.
List of advanced properties for your module.
Allows you to specify how the session identifier is exchanged between the Web browser and the Platform 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 Platform Server to retrieve session variable information for each user. Learn more about Platform Server sessions.
The possible values are:
If this option is set to 'Yes', which is the default, 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.
If this option is set to 'No', 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.
You cannot use cookies in SMS flows and, if you try to do so, an error message is presented to you.
You can, therefore, only use cookies safely in modules that have exclusively Web flows.
Indicates whether the module is Multi-tenant or not. By default, a module is single-tenant. Learn more About Multi-Tenancy.
Allows you to specify how web screens are handled by Web browsers. By default, this property is HTML5.
The possible values are:
HTML 5 (recommended): the browser will interpret the generated output as standard HTML 5, using the following doctype:
<!DOCTYPE HTML>
See how HTML Tags are generated for this mode.
XHTML Transitional: it's an almost standard mode, 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, in particular IE6, using the following doctype:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
See how HTML Tags are generated for this mode.
Click here for more W3 information on doctypes.
Allows you to specify the namespace to be used in the description section and the type section of the WSDL generated by this module.
If not specified, the namespace that is used is the following:
.Net Stack
General Namespace of the WSDL: http://<ModuleName>/WebServiceName/
Namespace of the WSDL Schema: http://www.outsystems.com
Java Stack
General Namespace of the WSDL: http://www.outsystems.com
Namespace of the WSDL Schema: http://www.outsystems.com