Edit Data

LRM Web supports advanced data editing.  Future releases will extend the editing capabilities. 

BizActions

Both LRM Web Map View and Data Views support the POSTFIELDCHANGE, PRESAVE, POSTINSERT, POSTTRANSACTION, PREDELETE, POSTDELETE, POSTSAVE, and PREROWCHANGE BizActions.  It updates the attribute values if PostInsert returns updated values, but it does not for PostTransaction and PostSave as it assumes that PostTransaction and PostSave BizActions run the actions on the database directly (e.g. a stored procedure). 

BizActions of type WARN, VALIDATION and ACTION are supported

Expression markup involving “:OLD.” and “:NEW.” in source and target criteria are supported. 

BizRules

LOCK_INSERT, LOCK_DELETE and LOCK_FIELDS BizRules are enforced in Tree View, Data View and Query View modes.

LOCK_GIS, LINE_EVENT, LINE_EVENT_CONTINUOUS, POINT_EVENT, LINE_EVENT_NOOVERLAP, POINT_EVENT_NOOVERLAP BizRules are enforced.

VISIBLE_TABS business rules are applied to show and hide child context based on parent configuration and its criteria.

NO_CASCADE_DELETE is supported, preventing users from deleting records until all descendant records have been removed.

UNIQUE_FIELDS is supported, ensuring that values for specified fields are unique 

From Spatial View, Bizrules of severity WARN and ERROR are supported.  However, from Tabular View (Grid/Form/Query/etc.), WARN Bizrules are treated like ERROR in this release.

Note: The following tabular BizRules are not enabled yet, but will be added to future LRM releases:

1. CONTEXT_REQUIRED

2. START_BEFORE_END

3. CONSTRAIN_VALUE_RANGE

4. ADD_ALL_ELEMENTS

5. TABULAR_CURRENT_STATUS

6. AUTO_INCREMENT_FIELD

7. BLOCK_NAR

8. BLOCKSTRATUM_NODELETE

9. BLOCKACTIVITY_SUMAREA

10. TRACK_CREATION_INFO

11. TRACK_DELETION_INFO

12. XREF_UPDATE

13. TRACK_CHANGES

14. SET_RELATED_CONTEXT_KEY

15. MODIFY_GRID_DATES

16. EVENTSCHEDULE

17. POSTEVENTSCHEDULE

Checkboxes

The Data View supports checkboxes for contexts with boolean datatype (true/false) fields.

Edit Version

There is a system setting "VersionWebAutoManage" in the TFM_SYS_SETTING table that controls how web edits are committed to the traditional version tables to determine if changes are committed to a named version or to the SDE Default version. 

For LRM Web we recommend setting VersionWebAutoManage to “1” and this is the setting used for our hosted solutions.  This setting does not affect LRM Desktop.

1. VersionWebAutoManage = 0

   • Users will maintain their own version for editing data as in LRM Desktop.  By doing so, users will have to post / reconcile their version to SDE default otherwise changes will not be visible to others.  If you also use LRM Desktop, a refresh is needed on LRM desktop to see the updated data. 

2. VersionWebAutoManage = 1

   • SDE Default version is used.  Users will not require posting or reconciling versioned data.  At the same time, users cannot discard changes as in using a personal version.

Inserting into Child Contexts

Basic web editing now supports adding new records for child contexts not previously visible in the tree view.

Related Document

Related Documents can be opened and saved for configurations that use database storage or file system storage. Related documents are deleted if they are attached to a record being deleted if they are stored in the database. No warning is made at this time to indicate the related document has also been deleted.  Future releases will enhance the deleting capabilities to more closely match LRM Desktop behavior.

Required Fields

Required fields are indicated with headers in bold font.