Support scenario, when on a form record is saved, but the current user lost access to it.
The form MUST use the LOST_ACCESS mutation so set the flag, which activates the behavior:
do not throw the documentNotFound exception, because server did not return result
after saving the form
close the form on save
Form mounting now assign $formServices to store, so that store has power of closing forms.
While it is a practice to implement whole scenarios as store actions, including using
confirmation dialogs, it shall be ok to also closing forms there.
Add transformSaveRequest function to processing, which allows, for the first, order requests.
It is crucial, for example, to track requests, which revokes access from the current user,
because it is possible that in between requests user lost access to a document, and rest requests
won't be handled. So such kind of requests might be just put in the end of the request list.
But potentially, this function allows a lot of flexibility.
UChart: Fixed an error when rendering in dev mode, added an if statement to the watch to ensure that ChartJs is
available before attempting to render the chart.
processing store module, the save action now check dirty status of the form - if the form state is not dirty,
nothing happens, and client code now does not have to do that check
UNavbarUserButton: made user icon to be a circle 36x36 instead of ellipse 34x36
UTableEntity: not restore the filter value after removing a filter with the same column and condition.
Fixed by removing side effects of a Vue computed value [LDOC-2919]
MS SQL: allow unique index on nullable columns {"isUnique": true, "allowNull": true}
by adding where attr IS NOT NULL part. Other RDBMS allow such indexes w/o where condition
