Stable version 11.2.2 (Compatible with OutSystems 11)

Other versions available for 10 and Older

Uploaded

on 4 Sep

OutSystems

4.8

(31 ratings)

Details

The Service Center Factory Configuration application allows you to change the configuration of the components of your Service Center Factory.

The Service Center Factory Configuration application allows you to change the configuration of the components of your Service Center Factory. You can customize Service Center known Configurations for an eSpace or create Shared Configurations that will apply to several eSpaces, such as specifying a default proxy for web service calls. This and other common samples of Shared Configurations have been already created for you and are available as pre-made samples.

Feature List

Customize the Default Proxy for Web References
Add a Custom Handler
Configure Integrated Authentication for Java
Customize HttpRuntime parameters
Screen to configure Platform "hidden" configurations

Warning: This component is not supported in Personal or Trial environments. Personal and Trial are offered on shared infrastructure where advanced configurations may affect other users and are therefore not supported.

Release notes (11.2.2)

Adds two settings "Hide Internal Database Error Message Details" and "Database Default Error Message". When 'Hide Internal Database Error Message Details' is enabled and "Database Default Error Message" is populated with a custom message, that message will be returned in case of a database error. If left empty, a generic error message is returned instead. (R11DT-2561).

Adds a setting "Enable range validation and timezone invariant DateTime in Mobile/Reactive". Similar to what happens with Null Dates (described in 'Enable timezone shifts for null dates in Mobile/Reactive'), the types Date and Time can also shift when the device timezone changes. E.g. a user has an unsubmitted form with an appointment Time or a Date of birth. Then, daylight saving time changes or they cross a border to another country/state. The Date and Time may shift 1 hour or 1 day causing them to be submitted with incorrect values. To fix this behavior, we reimplemented DateTimes so that only DateTimes are sensitive to timezone shifts. Null Dates, Dates, and Times will always have the same value after being created, regardless of the timezone. E.g. if the user selects an appointment at 7:00:00 AM, this object will always be 7:00:00 AM and won't change to 6:00:00 AM if timezone shifts -1 hour. By default, this implementation revamp includes the fix 'Enable timezone shifts for null dates in Mobile/Reactive'. Additionally, we now impose a validity range between [#1900-01-01 00:00:00#, #3000-12-31 23:59:59#] as officially documented for Date and DateTime. Any new/existing date outside this range is handled as a null date. Finally, when saving any DateTime in the local DB, it is stored in UTC. Please note that this is an opt-in feature to ensure these changes do not affect existing applications that might rely on dates outside the supported range or expect Dates and Times to be affected by timezones. It is advised a careful impact analysis on your applications before enabling this feature. (R11DT-2572)

License (11.2.2)

BSD-3 license (https://opensource.org/licenses/BSD-3-Clause)

Reviews (7)