Editing Configuration for User Management

If using edit functionality as well as WebOffice usermanagement the fields configured in this configuration element are used to automatically store information like:

the user who edited or created the object and

the time stamp when the edit transaction or create transaction was committed.

 

icon_comment

If configured, the fields for creating user and changing user have to be in the feature class and of type text with a minimum length of 20.

If configured, the fields for creating time stamp and changing time stamp have to be in the feature class and of type date if using Oracle or SQL Server (optional text (minimum length 20)).

The four mentioned fields are mandatory and have to exist in the feature class.

The field for client specific values (CLIENT_ID) may also be configured. If you do not want to use a client ID do not edit the default value! If editing, a field in the feature class is mandatory.

If physical deletion is set to No, a field of type text for the logical delete operation is mandatory and has to exist in the feature class and the respective definition query has to be specified in the layer properties.

On project configuration level it is possible to deactivate the Editing configuration for UserManagement for certain edit layers. This way editing on the corresponding layer can be made available, although it does not provide the columns that are necessary to store the metadata.

icon_cross-reference

For configuration details see parameter Use UM editing config in chapter Edit Layers.

 

icon_comment

ArcGIS provides a similar feature called editor tracking to document user and time regarding feature creation/editing. Consider the following points if you are also using ArcGIS editor tracking:

othe attribute fields storing WebOffice usermanagement creating user and changing user (i.e. by default CREATE_BY and CHANGE_BY) MUST NOT be the same as are used for editor tracking (ArcGIS default names: created_user, last_edited_user)!

othe attribute fields storing WebOffice usermanagement create time stamp and change time stamp (i.e. by default CREATE_DAT and CHANGE_DAT) may overlap with the ones used by editor tracking (ArcGIS default names: created_date, last_edited_date). Be aware that in this case, time stamps saved by WebOffice 10.9 SP1 may be overwritten by ArcGIS editor tracking.

oHowever, VertiGIS will recommend the use of ArcGIS editor tracking only if separate attribute fields for the WebOffice 10.9 SP1 Editing Configuration for User Management and ArcGIS editor tracking are configured.

 

Editing configuration for user management configuration

Editing configuration for user management configuration

 

Property

Description

Field for storing user id of creating user

Field for storing user id of creating user.

Default value: CREATE_BY

Field for storing user id of changing user

Field for storing user id of changing user.

Default value: CHANGE_BY

Field for storing create time stamp

Field for storing create time stamp.

Default value: CREATE_DAT

icon_comment

Field needs to be of type DATE

Field for storing change time stamp

Field for storing change time stamp.

Default value: CHANGE_DAT

icon_comment

Field needs to be of type DATE

Field for storing client specific value

Field for storing client specific value. The client specific value can be configured in a group inside the WebOffice usermanagement rights repository.

icon_cross-reference

See chapter WebOffice User Management for details.

Delete objects physically?

Determines whether to physically (true) or logically (false) delete objects.

In case of logical delete the field for logical delete operation is used to store the information whether the object has been deleted or not.

icon_comment

In order to use these field, do not forget to specify the according definition query in the layer properties.

Example: DELETED = false

Field for logical delete operation

Field of type text for logical delete operation.

WebOffice 10.9 SP1 writes the value true in the field when deleting logically. Thus, the other value should be false. It is possible to use a text domain at the field where the codes are true or false.

Editing configuration for UserManagement properties