WebOffice Standard Reference > WebOffice Category

Note: Edit functionality requires a valid WebOffice 10 R3 web editing license as well as ArcGIS Server Standard or ArcGIS Server Advanced as well as ArcGIS Server Workgroup or Enterprise for storing and managing the edited data.

Note that WebOffice 10 R3 editing is tightly integrated with WebOffice UserManagement. In User Management Admin Web you can e.g. configure a Client ID for a user group in order to automatically set the value of the Client ID field in the edit layer for this object when the user creates the object.

Note that to enable the Editing Tool at least one layer from an ArcSDE Geodatabase has to be included in a related AGS Map Service.

Use Edit layers for providing Edit functionality in the WebOffice 10 R3 clients. Edit functionality is available by using the Edit toolbar button

The Edit tool must be configured and activated – see chapter Editing for details.

If you would like to know about handling and work flows of the Edit tool in the WebOffice html client, then please see WebOffice html client online help.

Edit functionality in WebOffice html client is characterized by:

•Simple feature editing,

•Non topological editing,

•Data may be stored into any ArcGIS Server Basic (ArcSDE) workspace (i.e. it may be a Workgroup or Enterprise Edition. Note anyway that WebOffice 10 R3 checks if it is licensed for the corresponding ArcGIS Server Edition),

•Data may be stored into non versioned feature class, versioned feature class or feature class with activated ‘Save edits to base’s option,

•Vertex snap is available for exact digitizing,

•Full integration with SynerGIS UserManagement module (i.e. only enable specific roles to edit specific layers or objects).

Note: If you edit into a versioned feature class then WebOffice 10 R3 automatically performs the edits into the version used for the layer in the served ArcMap document. This way edits can be immediately displayed in the map service.

Note: It is recommended to use WebOffice 10 R3 webediting especially to implement simple decentralized edit tasks performed by many different users in different locations.

Note: it is possible to edit on a feature class with a different geographic projection then the main map service (the Edit Layer will get re-projected on-the-fly by ArcGIS). Anyway there may be some precision problems depending on the projection parameters. Therefore it is recommended to edit on feature classes only that have the same projection like the main map used for display.

Note: Editing features of a layer that has a joined table or layer in ArcMap is supported. Please consider, that the fields of the joined table cannot be used as edit fields.

Edit tool form in WebOffice html client

Note: With WebOffice 10 R3 more than four edit fields are shown in the edit tool for at one glance without scrollbar, if your display resolution allows it.

Edit layers configuration

The Edit layer configuration specifies in which way you want to edit on a specific layer of a map service.

An Edit layer configuration may contain the subsequent list of child elements:

•'Editing fields' specifies on which fields the user may edit,

•'List of lookup definitions' specifies the lookup values visible in the WebOffice client,

•'List of available edit actions' specifies which edit actions will be available for the user,

•'Edit user' specifies the database user for actually editing the geodata,

•'Snap layers' specifies the available snap layers for this Edit layer,

•'Integrated editing application' which will enable users to do attribute edits in an application different from WebOffice 10 R3 client,

•'Copy from layers' specifies all layers available in the 'Copy from' edit action to copy objects from a layer to the edit layer,

•'Object Assigment layers' specifies the layers to be used as source layers for object assignment.

Hint for Editing fields: If no Editing fields are configured, then users can change the object geometry only.

Hint for Integrated editing application: In WebOffice 10 R3 it is not necessary to configure Editing fields if the fields get edited using an Integrated editing application.

Hint: If ArcGIS Server Workgroup is used then no edit user can be configured. Instead the corresponding operating system user is used automatically.

Property	Description
Layer ID	Layer ID of the edit layer in the used map service.
Alias name of edit layer	Alias name for edit layer (for user interface edit layer drop down list box).
Usage hint	Short usage hint that will be displayed in the top right corner. Note: This parameter is WebOffice flex client specific.
Edit mode	Edit mode: •Attributes + Geometry: Attributes and geometry of the object get edited, •Attributes: Only attribute data of the object gets edited. The user is not able to change the geometry of the object at all, •Geometry: Only geometry of the object gets edited.
Default edit layer?	Specifies the default edit layer. If multiple edit layers are configured as default edit layer, then the first edit layer in the list is used as default edit layer.
Map View for edit layer	Specifies a specific map view/representation model to be displayed when choosing the edit layer. If no map view is configured then the current map does not get changed at all and the map does not get updated when selecting the edit layer. Tip: If you want to assure a specific map view when the user is about to start editing, then use this option.
External ID	External ID used in parameterized calls to WebOffice for identifying the edit layer.
Pixel tolerance for vertex selection	Pixel tolerance for vertex selection controls how sensitive selection of vertex points using the mouse pointer is. If the mouse pointer is within this distance of an object vertex point, then the user is able to select the vertex point.
Dimensioning	Support for doing simple dimensioning. Only effects the creation of polylines. If used (Yes) only two-point dimensioning per working step is supported. This also impacts several construction tools. Optionally chain dimensions can be created.
Use UM editing config?	If "Yes" is configured, the Editing configuration for User Management is being used for this edit layer, provided that is has been configured in the application configuration under Common -> User Management. If "No" is configured, the metadata (such as create time stamp, create user, change time stamp, change user) of an edit action are not being saved. Also, the functionality of a "logical delete" is disabled, that means that objects of this layer will be deleted physically. Note: This allows editing on this layer in the case that "Editing configuration for User Management" is present, but the current edit layer does not provide the columns that are necessary to store the metadata.
Use Multiple Object Editing?	Specifies whether editing of object attributes for an object selection (multiple objects) is possible for the user. Editing multiple object attributes at once (one interaction) may increase user efficiency considerably.

Edit layer configuration

Edit Layers