Changes that require configuration changes




  • Current user name is written in the UserName field when unloading the event log to XML. Full user name is written in the 8.1 version compatibility mode.
  • When the event log is written as .XML in 8.1 version compatibility mode the names of UserID, EventName and MetadataName elements do not change.
  • Data about authentication parameters are written in the Data field, not in the Comment field, for the Authentication and Authentication error event log events.
  • Unloading from collection Data and Metadata fields (structures and arrays) is not performed when unloading the event log to XML or to a value table in the 8.1 version compatibility mode.
  • HTML-handling features return tags in uppercase in the 8.1 version compatibility mode.
  • When modifying the functional option values new values are available in current session right after modification both in thick client and external connection, regardless to where the modification was made. In other session the modified functional options values become available on server right after modification, and not later than 20 minutes after modifictation in thick client and external connections.
  • User without administrative rights can not modify a value of CannotChangePassword property of the InfoBaseUser object. The behaviour is not changed in the 8.1 version compatibility mode (this modification is possible).
  • When using field from nested queries in + or - query language operations, when only NULL value is obtained, the error of query language is displayed. The abnormal terination executed in previous versions, starting from 8.1.12.
  • The OnClose handler is called when trying to close modal form on timeout expiration (in managed and ordinary form). The behaviour is not changed in the 8.1 version compatibility mode (the handler is not called).
  • Data composition template data set names are generated on language, corresponding with configuration script variant.
  • If the balance fields are obtained in the nested query, then in the external query these fields are considered balance, and totals are calculated by these fields like balance fields. The behaviour is not changed in the 8.1 version compatibility mode (balance fields, obtained from the nested query are not considered balance fields and totals are calculated by them like ordinary fields).
  • Exception is generated, if the EndOfPeriod parameter has value less then BeginOfPeriod parameter when executing query, where data is received from the RecordsWithExtDimensions, DrCrTurnovers and BalanceAndTurnovers virtual tables of the accounting register, and also BalanceAndTurnovers virtual table of the accumulation register.
  • In the managed form text box specifying the MarkIncomplete property to False is cancelled on text editing start and when performing interactive selection from the choice form, calculator, calendar and dropdown list. At the same time when specifying value in data, connected with the texbox, the MarkIncomplete property value is set automatically depending on value being specified, if the AutoMarkIncomplete property is set.
  • Modified names of automatically generated managed form elements (commands, command groups, etc.). Automatically generated form element names are generated on language, corresponding to script variant, not on the platform interface language.
  • If a business process has the Task creating privileged mode property enabled, then the privileged mode is used on business process start for all operations with tasks and to complete the business process, and when closing task for all operation with other tasks and for all operations with the business process itself.
  • Reading objects and writing records is performed in transaction. The shared lock is set for record sets when reading in managed mode. Conrol for coordinated reading the object tabular sections and record set records is provided.

Table of contents


Comments
0
Add comment