Update mixins.md

parent 9653f24a
......@@ -39,7 +39,7 @@ Go to the Request List section and see the new items in the context menu of the
![dataHistory_menu](img/mixins/dataHistory_menu.png)
New version suggests specifying a new date (it should be greater than the current date) of the document's relevance and changing the data to new ones - they will not be displayed in the current version.
Changes history allows see the versions of documents and edit them.
Changes history allows you to see the versions of documents and edit them.
![dataHistory_versions](img/mixins/dataHistory_versions.png)
......@@ -48,7 +48,7 @@ Changes history allows see the versions of documents and edit them.
## SoftLock
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!
It's useful in situations where you need to lock the document before editing so that other users can't modify it at the same time as you. Then, 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!
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.
......@@ -326,14 +326,14 @@ Ext.define('RequestList.reassignAll', {
```
If done correctly, the form req_depart will look like.
If done correctly, the form req_depart will look like:
![reassignTo_dialog](img/mixins/reassignTo_dialog.png)
At this stage, the form of selection from the list of departments only checks on the client side, whether the selected department is equal to the current one.
At this stage, the form of selection (from the list of departments) checks whether the selected department is equal to the current one only on the client side.
To change the data on the server side, you need to describe the server method "reassignDep", which is specified in the url parameter of the function $App.connection.xhr()
Create on the folder `models\requests` the file `req_depart.js` with following code.
Create the `req_depart.js` file in the `models\requests` folder and add there the following code:
```javascript
......@@ -387,6 +387,6 @@ me.reassignDep = reassignDep;
Restart the UB server and make sure if the created functionality works correctly.
Restart the UB server and make sure that created functionality works correctly.
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