fix bugs after Grammarly checking in mixins.md

parent b36b730a
......@@ -16,7 +16,7 @@ To do this, in the file `req_reqList.meta` in the mixins section add the dataHis
Mixin has the following properties:
* mi_data_id - contains a copy of a record with a several version
* mi_dateFrom - record availability start time
* mi_dateTo - record aviability finish time
* mi_dateTo - record availability finish time
......@@ -32,7 +32,7 @@ Mixin has the following properties:
```
After execute the command in the console
After executing the command in the console
`ubcli generateDDL -u admin -p admin -host http://localhost:888 -autorun`
Go to the Request List section and see the new items in the context menu of the entries.
......@@ -49,7 +49,7 @@ Changes history allows see the versions of documents and edit them.
Mixin "softLock" is responsible for the logical blocking of EDITING entity records. The correct name is Pessimistic Lock (pessimistic lock)
It's useful in situations where you need to lock the document before editing so that another user does not change it during editing. And after the end of editing, the lock is removed. It should be noted that the server will NOT let UPDATE and DELETE perform on records that are not locked by the user!
Бывает 2 вида блокировки:
There are 2 types of locking:
* Persist/ltPersist - Permanent blocking. There is an unlimited amount of time until the command comes to remove the lock from the user who supplied it.
* Temp/ltTemp - Temporary blocking. Valid as long as the user does not remove it or take some time out from the start of the lock. Currently, the lockout timeout is 60 seconds.
......@@ -91,7 +91,7 @@ The administrator can manually unlock the document.
safeDelete is a boolean flag to use the soft delete function of the database. If false, the entry is permanently deleted from the database table. If true, then the record is marked remote but physically remains in the database table. The default value is false. In the enabled state of this property, the mixin adds the service attributes to the entity:
* mi_deleteDate – Date-time of soft removal of an entity record. By default, the value of this attribute is the date 31.12.9999. This is the value that indicates that the entry was NOT deleted. This field participates in many unique indices of the entity.
* mi_createUser – The identifier of the user who deleted the entry in entity. The attribute type - 'Entity' refers to the entity uba_user. The default is null.
* mi_createUser – The identifier of the user who deleted the entry in an entity. The attribute type - 'Entity' refers to the entity uba_user. The default is null.
Make it possible to delete subdepartments so that they remain in the memory of the applications in which they were specified during their action.
In the file `req_subDepart.meta` in mixins section add the following code and execute the command
......@@ -203,7 +203,7 @@ exports.formDef = {
```
In METHODS DEFINITION add the following code
In METHOD`S DEFINITION add the following code
```javascript
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment