Properties, methods, and features of the overlay locks edit individual lines in GroupEdit
GroupEdit supports the ability to lock editing of individual rows. This allows a correct simultaneous editing of objects in
GroupEdit and on separate forms.
Locks are managed using the following properties, methods and events.
AllowRowLockingis responsible for enabling edit mode lock.
DisableRow(DataObject dataObject)locks the row with the specified data object for input. Row lock means the impossibility of data entry and allocation in gray.
EnableRow(DataObject dataObject)removes the lock with the string specified with the data object.
IsRowDisabled(DataObject dataObject)allows you to test the blocked string or not.
LockDataObject(DataObject dataObject)locks an object for exclusive editing in GroupEdit (the lock is through the mechanism of
LockService. Object locks can be taken off the call
UnlockDataObjector when the form is closed.
BeginEditwhen you start editing the attribute of an object.
EndEditwhen you are finished editing attribute of the object.
1.When the form opens, the aggregator it is necessary to impose a lock on all objects detaily due to the following reasons
- no need to write for the ordered detailov separate treatment, since the change of the ordered attribute also leads to a change of the object and the misalignment with open формой;
- on the form of the aggregator can be implemented in some business transaction that changes detaily.
2.When you open the form for editing GE checks locks on every object in GE and in the presence of locking is locking a row for input.
3.When you start editing a specific data object in GE checks locks on every object in GE and if there is a lock, locks the string and issues a warning to the user.
4.For the locked input rows is not available the delete operation.