Integrated Editing Application |
  
|
Integrated Editing Application |
|
Specifies an integrated editing application used for editing attribute data and relations of the object created and edited with WebOffice 10 R3 (WebOffice 10 R3 maintains the geometry and the object key only). Using an Integrated editing application is especially useful if a big set of attributes and/or related objects need to be edited/maintained: WebOffice 10 R3 is not designed to implement complex attribute edit forms.
If an Integrated editing application is used, then each time the user submits an edit transaction to WebOffice 10 R3, a HTTP GET or POST request is sent from WebOffice 10 R3 to the Integrated editing application. The request contains information on the used edit action as well as one the changed object (OBJECTID).
Note: The Integrated editing application may either be developed by a partner (e.g. Geonis attribute editor provides such functionality) or by the customer itself. Please contact SynerGIS if you want to know more about Integrated editing applications (web-support@mysynergis.com).
Integrated editing application - WebOffice Category
Property |
Description |
Application name |
Name of external web application used for display in WebOffice client. |
Popup window width |
If using popup windows for displaying external contents the size of the popup window can be configured. |
Popup window height |
If using popup windows for displaying external contents the size of the popup window can be configured |
Buttons available? |
Provide button ("Yes") or hyperlink ("No") in user interface. Five different standard icons are provided, however, any other icon can be configured. This property has no effect on applications with static hyperlink. |
Icon for application call |
In WebOffice folder pub/images ten icons are available (extapp_01.gif to extapp_10.gif). Icons need to have a size of 16x16 pixels. |
Access control ID |
Access control ID needed for access control based on usermanagment module. If an ID is configured here (e.g. "LINK_ALKIS_COLORMAP") and WebOffice usermanagement module is used then the user role is checked whether it provides the necessary application right or not (according to the example the application right would be LINK_ALKIS_COLORMAP). If the necessary application right is not available then the button/link for accessing the external application will not be available in the WebOffice search result page. |
Base URL |
Full base URL of external web application. The web application must be able to process the parameterized request (Edit actions and object keys of edited objects are passed). |
Use HTTP Get? |
Pass parameters to external application via HTTP Get ("true") or HTTP Post ("false"). |
Call application automatically? |
Specifies whether during execution of a specific WebOffice edit action, the integrated Editing application is called automatically ("Yes") or not ("No"). If "No" then the user must click a button in the WebOffice edit form to call the integrated editing application. |
Pass user context? |
Used for UserManagement secured projects. Specifies if the user context of the user logged on to WebOffice will get passed in the HTTP header. The external application gets the following information: x-syn-login = <username> x-syn-application-roles = <list of application roles> x-syn-group = <group name>
Note: If providing a user context to an external application the URL will be redirected (URL changes from http://extserver/extpage.htm?...to http://webofficeserver/webofficeapplication/synredirect?...) Therefore all paths used in the external Application have to be full qualified! |
Call application with delete? |
Specifies whether during execution of the WebOffice edit action "Delete" the integrated Editing application is called automatically ("Yes") or not ("No"). If "No" then the integrated Editing application does not get any information about deletion of the object in WebOffice. Note: Regarding the configuration of this attribute, we recommend the following scenarios: •"No": If the GIS and the application access the same data, no action shall be caused by delete. •"Yes": If the GIS and the application access differing data (connected by a key), delete shall cause an action. |
Integrated editing application configuration