Navigation:  Introduction to WebOffice map widget > Supported Parameters > Administration Parameters

•roles

Use this parameter to pass the user role from 3rd party web application to WebOffice map widget.

Note that the specified use case for running WebOffice map widget with a 3rd party web application is to run WebOffice 10R3 in trusted mode, i.e. 3rd party application will take care of user authentication and will only pass a user role (no user login, no password) to the WebOffice map widget.

It requires WebOffice 10R3 to run in UserManagement mode using Authentication type HTTP. A correct configuration of the Authentication type HTTP (Portal URL, HTTP Referrer of 3rd party Web Application, Use user roles only=Yes) must be set.

 

If e.g. in the WebOffice UserManagement database a user role 'editor' is available then use roles=editor .

 

 

•password

Using the password parameter it is possible to access the WebOffice 10R3 project. The password is passed in clear text.

(See section ‘roles’ for more information on best practices concerning userless login to WebOffice map widget.)

 

•user

User Login for accessing the WebOffice 10R3 project, if e.g. the WebOffice user login is 'xyz' then use user=xyz .

Note: The parameter user and parameter password are tied together. Both must be defined otherwise the request will not be successful. WebOffice map widget supports WebOffice usermanagement only for users that are members of only ONE group in WebOffice usermanagement.

 

•getversion_mw

Use the parameter getversion_mw=true in order to detect the version of WebOffice map widget.

Note: It's necessary to use this parameter in combination with the parameter callback_getversion_mw.

The version is shown in terms of majorversion.minorversion.timestamp (e.g. 10.3.201305120941).

The current version of the WebOffice map widget can also be found in the file SynServiceClient.js (<Tomcat>/webapps/<WebOffice application>/client_mapwidget/Scripts) in the parameter this.version.

 

•useXD

Use this parameter in order to activate Cross Domain Scripting.

Note: For further information, on how to implement this parameter, see chapter Cross Domain Scripting.

 

•return_error_codes

Use this parameter (return_error_codes=true) to get the error code number in case of an error. If false, the usual error name (e.g. SERVER.FATAL.NO_PROJECT_CONFIG) will be thrown.

Note: Optional you can get the error code number in a callback function. See chapter callback_error for details.

Note: The usual error codes are language-independant. If you get the error code numbers, you can display corresponding error messages in the sup. application.