Page 1 of 1

What's New in Version 8.1.8

Posted: Sat Jul 09, 2011 6:38 am
by Elisy
What's New in Version 8.1
This section briefly describes what's new in version 8.1
Applied Objects
  • The algorithm formed by the Register Record Wizard has been changed. Register records are not written explicitly, while modified record sets are written automatically.
  • The algorithm of filling expressions in the Register Record Wizard has been changed. A document attribute is considered appropriate for a register dimension or resource, if there is at least one type owned by both the attribute and the register dimension or resource.
  • For external data processors and reports the 1C:Enterprise script provides a functionality of obtaining a full name of a file used to load an external data processor and report.
  • If auto-numbering is used, you can correct a wrong maximum number. You do not need to terminate clients or restart the 1C:Enterprise server to implement this correction.
  • When document sequences are recovered interactively, the sequence recovery date is displayed in the status bar. It allows you to track the process and define its estimated completion time.
  • You can stop the interactive sequence recovery process by pressing Ctrl+Break.
  • New error diagnostics functionalities have been added for writing registers(accumulation, information, accounting, calculation registers and recalculations).
  • A more detailed error message is displayed, if data inconsistency is found in the lists of displacing and leading calculation types while writing calculation types.
  • A more detailed error message is displayed, if invalid changes are made to the lists of displacing, basic or leading calculation types.
  • The text presentation of a business process route point is now different from the presentation of a business process reference.
  • You can now subscribe to the all events of "Verify and repair" mechanism in "Restructuring InfoBase tables". For example, you can subscribe to all catalog events.
  • Filtering a change selection obtained by using the

    Code: Select all

    SelectChanges()
    method of the exchange plan manager is currently available.
  • If you attempt to open an external data processor or report interactively without having sufficient rights, a message is displayed.
Query Language
  • The current version provides new query language tables that allow you to access information on data change registration for objects included in exchange plans.
  • The current version has no restriction on using more than 256 tables in a query for file-based InfoBases and client-server variants if PostgreSQL or IBM DB2 is used as a DBMS.
  • The query language allows you to use multiple expressions in the "IN" or "NOT IN" construction.
  • The new

    Code: Select all

    REFPRESENTATION()
    function can be used If you disable the Usage property for a conditional appearance formatted field, and no formatted fields for the current conditional appearance element have the Usage property selected while this method is used, the Usage property is totally disabled for the conditional appearance element. If you disable the Usage property for a filter item included in a group, and the group has no other items with the Usage property selected while this method is used, the Usage property is disabled for the group as a whole. If you disable the Usage property for a conditional appearance formatted field, and no formatted fields for the current conditional appearance element have the Usage property selected while this method is used,the Usage property is totally disabled for the conditional appearance element.If you disable the Usage property for a filter item included in a group, and the group has no other items with the Usage property selected while this method is used, the Usage property is disabled for the group as a whole. To obtain a presentation for a reference value.
Data Composition System
  • The data composition schema wizard and the expression editor usability has been improved.
  • The data composition system now allows you to specify a parent field for dimension fields.
  • You can also set a value type for calculated fields of the data composition schema.
  • Report parameters can be hidden from users while being available for making changes in the 1C:Enterprise script.
  • The data composition schema allows you to specify a template for table resource areas.
  • It also provides a functionality of setting a grand total template.
  • A separate dialog box has been added to set up detail parameters for template areas of the data composition system.
  • The loaded composition template areas are placed at the beginning of a spreadsheet document. Separate areas are divided by blank rows.
  • When the data composition schema wizard loads a non-table group template, it sets rows as a template area.
  • The data composition schema wizard allows you to edit field and group templates in multiple languages.
  • The Execute() method of the

    Code: Select all

    DataCompositionDetailsProcess
    object has a parameter used to create additional menu items.
  • The

    Code: Select all

    DataCompositionAppearanceTemplateWizard
    object of the 1C:Enterprise script has been implemented.
  • The data composition system provides the following comparison types: "Not in Hierarchy", "Not in List", "Not in List by Hierarchy", "Does Not Contain", "Filled" and "Not Filled".
  • The

    Code: Select all

    ValueIsFilled()
    function has been implemented in the data composition system expression language.
  • Data composition settings parts can now be compared and merged in a data composition schema.
  • You can save settings of a report created in the data composition system into an XML file or load these settings from an XML file.
  • Reports can contain relative dates (for example, the beginning of this week,the end of the next month) and relative periods (for example, yesterday, from the beginning of this year, last month).
  • The data composition system allows you to quick-edit the most frequently used settings by hiding the settings that are rarely used.
  • When grouping by period field, the parent grouping period field is added automatically, if the parent grouping has not obtained the period field. For example, if grouping by day is set, parent groupings by month and year are created automatically.
  • The data composition system reports can now display a certain percentage of records in a grouping.
  • These reports can also display data at the specified level.
  • Conditional appearance parameter Color in Chart has been added for the data composition template. This parameter contains the color used to display a grouping in a chart.
  • The

    Code: Select all

    DataCompositionAreaTemplateChartGroupAppearance
    object has a new

    Code: Select all

    Format
    parameter that defines the format in chart series and points.
  • This version provides a functionality of setting a global selection for custom report fields.
  • The appearance template collection now includes the None template without appearance.The

    Code: Select all

    DataCompositionSettingsCompiler
    has the

    Code: Select all

    ExpandAutoFields
    method.
    You can edit the nested schema parameters in the nested schema settings editing dialog box of the data composition schema wizard.
  • For hierarchical groupings by hierarchical objects without groups, grouping records are formatted equally.
  • You can edit the nested schema parameters in the nested schema settings editing dialog box of the data composition schema wizard.
  • The Evaluate() function of the data composition system query language has the Evaluation Type parameter that defines grouping records (all or the current record only) for expression evaluation.
Background and Scheduled Jobs
  • File-based infobases allow you to change scheduled jobs without starting up the Job Scheduler.
  • The 1C:Enterprise script provides a functionality of checking the scheduledjobs schedule.
Integration Tools
  • The NTML (Integrated Security) authentication on the proxy-server, operating under Microsoft Windows OS, has been implemented for the HTTPConnection object.
  • In the current version you can create an XDTO factory based on a XML schema or schema set.When you edit the property of namespace usage in a Web service, you can select standard (predefined) namespaces in addition to specifying namespaces definedby the XDTO package set.
    When selecting a type for the value returned by a Web service operation or atype for the operation parameter, the valid namespaces are limited to thosespecified in a Web service by parents.
  • A more detailed error message is displayed, if invalid XML characters arewritten.
Full Text Data Search
  • The full text search now allows you to search for special symbols and their combinations. You should enclose these characters into quotation marks in the search string. Example: "()", "!!!".
  • The current version introduces a lower limit on the number of appropriate words in the full text index that requires you to narrow the search query. The message of narrowing the search query is now displayed, if there are more than 300 lookup words (previously, this number equaled 1000).
Script
  • The new Owner() method has been implemented for a value table/value tree row in the 1C:Enterprise script. This method is used to call the value table/value tree owning the row.
  • The new Owner() method has been implemented for a query results selection in the 1C:Enterprise script. This method is used to call the query result used to obtain the selection.
  • You can specify a file used to save a document for a spreadsheet and text document as well as a graphical and geographical schema in the 1C:Enterprise script.
Setting Access Rights
    A right to update the database configuration has been implemented. It allows you to update the database configuration both in the Designer and the command line without administrator rights. The update is performed on the 1C:Enterprise server.
    If you update the configuration using the command line, a special startup key specifies that the update should be performed on the server.
  • Roles now have the Assign Rights to New Objects checkbox. If the checkbox is unchecked, rights to new configuration objects are not set for the role.
Designer
  • The configuration verification mode now provides a functionality of verifying names of non-global common modules. The names should not match global context properties names.
  • The Syntax Assistant provides Help for all MetadataObject properties.
  • When you execute the Find References in Object command in the Designer, the search scope selection dialog box only displays references related to the object and its subordinate objects.
  • You can use multiple row selection and mark setting in the dialog box used to select types for a compound data type.
  • The properties palette allows you to view the picture set as a property value,if the configuration object owning this property is read-only (for example, if the configuration is fully supported).
  • The properties palette allows you to view the Content property of the Document journal Graph configuration object, if this configuration object is read-only (for example, if the configuration is fully supported).
  • Warning messages are displayed when you close the query wizard and configuration comparison dialog boxes.
Administration
  • Unused database fields are checked for default values. This check is a part of the infobase logical integrity check in the infobase test and repair mode.
  • A new Verify and repair mode "Restructuring InfoBase Tables" has been implemented. It is used to re-create infobase tables and is required to modify databases in compatible 1C:Enterprise versions. To enter this mode in the command line, use the -Rebuild key.
  • Custom settings (settings of a certain InfoBase and a certain user) are saved in the database. Custom settings can also be cleared by using the 1C:Enterprise script.
  • Storing passwords of users registered in the infobase has become safer. The current version stores password checksums calculated by SHA1 algorithm.
  • The user list editing form displays question mark pictures for users without assigned roles or authentication.
  • You can choose not to divide the event log by periods. In the file-based infobase storing the event log without periods is used by default; you are not recommended to change this mode.
  • The presentation of event log system events in various mechanisms of different system modes has been standardized.
  • The event log allows you to make selections by events that include each other.Improvements have been made to algorithms of using the Designer in StartupBatch Mode:
    • The database configuration update command (/UpdateDBCfg) can be used as a parameter for the following commands:
      • Load a configuration from a file (/LoadCfg);
      • Update the supported configuration (/UpdateCfg);
      • Update a configuration from the repository (/ConfigurationRepositoryUpdateCfg);
      • Load configuration files (/LoadConfigFiles).
    • The /RunEnterprise command line key can now be used to start up 1C:Enterprise after executing a batch command.
    • The /DumpResult command line key can now be used to specify a name for the file used to store the Designer result.
    • The /Visible command line key can now be used to make the batch command execution visible to the user. While the Designer is running, the splash window remains open.
  • The /EXECUTE command line key can be used to start up external data processors.The connection parameters for a certain infobase can be left blank.
  • The /ConfigurationRepositoryUpdateCfg key of the startup command line (update a configuration from the repository) now has the –force key. This key is used to confirm such operations as obtaining new configuration objects or deleting the existing objects in the batch mode.
  • The server cluster administration utility can display information on the amount of data transferred between the 1C:Enterprise server and the database server for each client connection.
  • The client-server variant administration utility allows you to change DBMS type, database server name, database name, database user name, database user password.
  • You can filter the technological log by event and property templates.
  • The technological log allows you to record information on errors in custom settings.
  • The technological log can also record deadlock data.
  • The technological log events related to the database have a new Trans property that indicates whether a transaction is active. This property facilitates the transaction lock analysis.
  • A message is displayed, when writing a dump for 1C:Enterprise 8.1 client termination.
  • You can obtain the database storage structure using both 1C:Enterprise terms and DBMS terms.
Ergonomics and Usability
  • The File menu now has the Print with Current Settings item for the Designer and1C:Enterprise startup mode.
  • You can select the whole text box, if you left-click the text.When you use your keyboard to enter an account code into a text box referencing the account, a comma is converted into a point, if the chart of accounts contains an account code mask and:
    • The mask has points;
    • The mask has no commas.
  • A form opened in desktop mode is displayed in the window panel, in the open windows list, and can be activated interactively.
  • Custom forms have a new AllowClose property that controls the functionality of interactively closing forms.
  • Some changes have been made to the procedure of closing docked windows merged into a tabbed window. Only an active tab is closed now.
  • Interactive user actions can be logged now. When you start up a client application with the /logui command line key, the logui.txt file is created to log interactive user actions. This log can be used to analyze the solution usability.
  • Accelerators have been added to select multiple rows in table boxes that display dynamic lists (from the current row to the list start, from the current row to the list end, all rows).The search algorithm for a spreadsheet document has been modified. If the specified string can be interpreted as a number, it also searches for a string that contains three-digit group separators and decimal separators.
    A nonbreaking space is equated to a space.
  • Some changes have been added to the dialog box that opens when you call the OpenValue() method or click the open text box button: displaying a value makes a type display impossible. New commands (Select and Open) have been added to the text box context menu.
    The Clear command behavior has been changed: it now deletes values instead of text.
Other Modifications
  • If you have insufficient rights to access tables used in the Report Builder or the data composition system, an error message is only displayed, if the resulting query uses a field from a table which cannot be accessed.
  • The RunApp() global context method now has the Wait for Completion parameter that allows you to wait until the running application is closed.
  • You can obtain information on the types of applied objects available through the COM connection. It facilitates processing OpenOffice object events.
  • The dialog boxes of table box list setup and display for columns without header title now display the localized name. If these columns contain a picture, the "Picture <number>" text is displayed; otherwise, the "Column<number>" text is displayed.
  • The Help search window displays the following text, if the specified word cannot be found: "Not Found: <Specified word>".
  • You can specify a header location for a spreadsheet document grouping.
  • The view text document comparison results dialog box now has the Show/Hide Line Splitters command.
  • A template with a graphical schema has been added.
Optimization
  • Using RAM has been optimized by storing large selections in temporary files on a hard disk drive.
    If you use large selections, you will need enough free space on hard disk drives that store temporary server and client files.
  • The 1C:Enterprise client computer uses less memory when it works with large configurations. Changes to the DBMS index structure have improved the platform performance and scalability:
    • Virtual register tables are obtained faster, for example, when you build reports.
    • Extra totals records are not locked so often when registers are updated.
    • When multiple users intensively work with data (view document or catalog lists,etc.), the system performance has improved.
    • Register totals are recalculated faster.
  • The existing infobase indexes are only modified after you test and repair them in the Restructuring Infobase Tables mode or after you restructure the corresponding configuration object.
  • Starting up the client application after you dynamically update large configurations now requires less time due to client cache optimization. In the client-server variant with Microsoft SQL Server 2000/2005 DBMS, the calculation of accumulation and accounting register totals now requires less time. The optimization has become possible through changing the DBMS table index structure.
    In the file-based infobases, less RAM is required to recalculate totals with multiple register records.
  • The execution of queries that contain a comparison with Undefined value and of some data update operations has been optimized.
  • Starting up 1C:Enterprise 8.1 in a terminal server environment now requires less RAM and time.
  • Some improvements have been made to the procedure of restructuring infobases after some frequent data structure changes.
  • The procedure of restructuring infobases with the modified database tables containing few records has been optimized.
  • The Select() method behavior has been improved for objects containing large tabular sections. If a standard data chunk cannot fit into RAM, it is automatically stored in a temporary file on a hard disk drive.
  • The concurrency of writing register record sets for a document sequence with dimensions has been increased due to optimizing the algorithm of sequence boundary movement.
  • The sequence boundary update mechanism has been improved to minimize datalocks.
  • The concurrency of writing documents included in document journals has been increased.
  • Writing documents with large tabular sections and writing into the information register has been improved.
  • Writing into the accounting register now requires less time.
  • Executing queries containing the "

    Code: Select all

    In Hierarchy
    " construction has been optimized.
  • Executing queries containing the IN construction has been optimized.
  • Web-service connection pool is now more secure in an increased load situation.
  • Calling spreadsheet document cell area properties programmatically is now faster.
  • Obtaining a COM connection from a connection pool is now faster.
  • The

    Code: Select all

    InternetMail
    object has a new functionality that allows you to reduce traffic when receiving messages from a mail server (

    Code: Select all

    GetUIDL()
    and

    Code: Select all

    CombinePartial()
    methods of the

    Code: Select all

    InternetMail
    object, as well as

    Code: Select all

    Partial
    and

    Code: Select all

    UID
    properties of the

    Code: Select all

    InternetMailMessage
    object).
  • Changing the order of configuration objects by using up and down commands in the configuration tree has been optimized.The working processes and the server agent respond to cluster register changes faster due to reducing the number of calls to the cluster manager.
  • The number of Debugger calls to the DNS-server has been decreased.
  • Custom settings stability has been increased. If internal errors occur while reading custom settings, the settings are ignored, but the system startup is not aborted.
  • When you display reports in a spreadsheet document, you can use the improved functionality of defining the width of text-containing cells.
  • The number of read data operations has been optimized for opening a form that contains table boxes with dynamic lists.
Transition from Version 8.1.7 to Version 8.1.8
[*]The configuration, infobase and external data processors conversion is not needed when transiting from 8.1.7 to 8.1.8.Attention!!!
When starting work with version 8.1.8 on working with earlier versions there are the following features:
  • When the Assign Rights to New Objects check box is checked for a role the way of processing rights for it in the 8.1.8 version will differ from ways of processing in earlier versions. If in earlier version of platform rights for such objects were set as allowed by default, then in version 8.1.8. they will be set as forbidden.
  • You can't use data composition schemas and data composition system report settings with new functionality in earlier versions.
  • The location of custom settings, concerning to the infobase. As a result,custom settings in version 8.1.8 may differ from those used in earlier versions.
  • In file-based variant the simultaneous operation with the same infobase is notsupported if users use different platform versions: 8.1.8 and 8.1.7.
Modifications that Require Configuration Changes or Influence System Behavior
  • The structure of database tables and indexes has been optimized. You needto perform full infobase conversion in order to get benefits from this feature.
    To do so you can use the "Verify and repair" mechanism in "Restructuring infobase tables" mode. In order to get benefits for separate configuration objects you should perform the conversion of tables, corresponding to given objects. For that you should make changes in metadata objects, which will lead to conversion during database configuration update.
  • In order to get access to the Changes registration tables using the query language you should perform the update of configuration database, which leads to the conversion of tables, in earlier versions. In case of you can't change the configuration to initialize the conversion (for example, the configuration is supported and changes are not allowed) you can use the "Verify and Repair"mechanism in the "Restructuring infobase tables" mode.
  • Data composition schemes modified in version 8.1.8 will not open in earlier versions of the platform.
  • OverallsTemplate and OverallsPlacement properties of the DataCompositionTemplateTableGroup object have been removed.
  • Presentations of the following data composition system comparison types have been modified:
    • In Hierarchy is renamed to In Group;
    • In List by Hierarchy is renamed to In List Group;
    • Not in Hierarchy is renamed to Not in Group;
    • Not in List by Hierarchy is renamed to Not in List Group.
  • The behavior of the Refresh() method of the DataCompositionSettingsComposerobject has been modified. If you disable the Usage property for a conditional appearance formatted field, and no formatted fields for the current conditional appearance element have the Usage property enabled while this method is used,the Usage property is totally disabled for the conditional appearance element.If you disable the Usage property for a filter item included in a group, and the group has no other items with the Usage property enabled while this method is used, the Usage property is disabled for the group as a whole.
  • After you replace the text in the selected text document area, the text remains selected.
  • GeographicalSchemaLayerSeries terms are replaced with GeographicalSchemaLayerDataSeries.
  • If you click a shaded Rights check box for all the edited rights of single-type objects, the check box is assigned the specified state. In earlier versions this check box was cleared.
  • A modified procedure is used to determine whether an address is owned by thecurrent computer: if an IP-address is separated by periods, it is not required in DNS (hosts); when setting up a server cluster and a central server, ensure that the addresses of the same servers match; different addresses of a single server are not checked for identity.
  • Changes to custom settings (settings of a certain infobase and a certain user)saved in a new platform version cannot be read in the previous platform versions.
  • You are not allowed to write log events by using 1C:Enterprise script, if identifiers of these events use combinations of "_$" and "$_" reserved for system events.