Files
srv1c-web-8.3.27.2342/distr/docs/en/V8Update.htm
T
2026-10-09 15:28:00 +03:00

1597 lines
3.3 MiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head><title>V8Update</title><meta http-equiv="X-UA-Compatible" content="IE=edge"></meta><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></meta><style>body { font-family: Verdana, Arial, Helvetica, sans-serif; line-height:1.5}
a[href^="http://"] { font-weight: bold }
p, div { max-width:1000px; margin: 0em }
p.versions {margin: 1em}
ul { max-width:1000px; margin-top:0.5em; margin-bottom: 0.5em }
li > ul { line-height:1.25 }
table { border: solid transparent; border-collapse: collapse; width: 100%; table-layout: fixed; word-wrap: break-word; }
thead { color: rgb(0,0,0); background-color: rgb(244,236,197); border-color: rgb(192,192,192); }
td { border: 1px solid rgb(192,192,192); border-bottom: none; vertical-align: top; text-align: left; padding: 4px }
td.docborder1 { border: 1px solid rgb(192,192,192); border-bottom: none; border-top: none; vertical-align: top; text-align: left; padding: 4px }
td.docborder2 { border: 1px solid rgb(192,192,192); border-bottom: none; vertical-align: top; text-align: left; padding: 4px }
.tagSelected {background-color: #4444FF; color: white; }.term {color:rgb(172,51,51); font-family:Courier-New; font-size: 110%; }
.interface {color:rgb(53,53,255); }
tr.compat, li.compat { background-color: rgb(251,248,243); }</style></head><body><h1>1C:Enterprise 8</h1><p class="versions"><a href="#807fae8f-094d-11ef-963f-0050569f678a">Version 8.3.27</a></p><p class="versions"><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a">Version 8.3.26</a></p><p class="versions"><a href="#7c3108e4-256a-11ee-963f-0050569f678a">Version 8.3.25</a></p><p class="versions"><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a">Version 8.3.24</a></p><p class="versions"><a href="#801127d0-e1af-11ec-aa69-0050569f678a">Version 8.3.23</a></p><p class="versions"><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a">Version 8.3.22</a></p><p class="versions"><a href="#bb572410-f9ba-11eb-8371-0050569f678a">Version 8.3.21</a></p><p class="versions"><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a">Version 8.3.20</a></p><p class="versions"><a href="#cacd4ced-ca96-11ea-8371-0050569f678a">Version 8.3.19</a></p><p class="versions"><a href="#cfd09ff9-5899-11ea-8371-0050569f678a">Version 8.3.18</a></p><p class="versions"><a href="#9f36892b-eb6c-11e9-8371-0050569f678a">Version 8.3.17</a></p><p class="versions"><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a">Version 8.3.16</a></p><p class="versions"><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a">Version 8.3.15</a></p><p class="versions"><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a">Version 8.3.14</a></p><p class="versions"><a href="#199f74c5-0668-11e8-a3f7-0050569f678a">Version 8.3.13</a></p><p class="versions"><a href="#e4150058-9163-11e7-a3f7-0050569f678a">Version 8.3.12</a></p><p class="versions"><a href="#717c2d01-026f-11e7-a3f7-0050569f678a">Version 8.3.11</a></p><p class="versions"><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a">Version 8.3.10</a></p><p class="versions"><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a">Version 8.3.9</a></p><p class="versions"><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a">Version 8.3.8</a></p><p class="versions"><a href="#e7682089-abaa-11e4-b1db-0050569f678a">Version 8.3.7</a></p><p class="versions"><a href="#eb969ada-881f-11e3-b57b-e61f135f174b">Version 8.3.6</a></p><p class="versions"><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b">Version 8.3.5</a></p><p class="versions"><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b">Version 8.3.4</a></p><p class="versions"><a href="#4288e495-1835-11e2-b237-e61f135f174b">Version 8.3.3</a></p><p class="versions"><a href="#e729b97c-1831-11e2-b237-e61f135f174b">Version 8.3.2</a></p><p class="versions"><a href="#e729b97b-1831-11e2-b237-e61f135f174b">Version 8.3.1</a></p><details style="cursor: pointer" id="func_list"><summary>List of functionalities.</summary><p style="cursor: default"><div id="tags"><a href="#" class="tagSelected" id="action_0" onclick="onTagClick(this, 0); return false;">All functionalities</a>, <a href="#" class="" id="action_1" onclick="onTagClick(this, 1); return false;">Compatibility mode</a>, <a href="#" onclick="onTagClick(this, 88); return false;" id="action_88">1C:Enterprise language</a>, <a href="#" onclick="onTagClick(this, 69); return false;" id="action_69">1C:Enterprise script</a>, <a href="#" onclick="onTagClick(this, 183); return false;" id="action_183">1C:Enterprise software system</a>, <a href="#" onclick="onTagClick(this, 112); return false;" id="action_112">A client application form</a>, <a href="#" onclick="onTagClick(this, 110); return false;" id="action_110">Access rights</a>, <a href="#" onclick="onTagClick(this, 162); return false;" id="action_162">Access to mobile device features</a>, <a href="#" onclick="onTagClick(this, 82); return false;" id="action_82">Accounting registers</a>, <a href="#" onclick="onTagClick(this, 42); return false;" id="action_42">Accumulation registers</a>, <a href="#" onclick="onTagClick(this, 11); return false;" id="action_11">Add-ins</a>, <a href="#" onclick="onTagClick(this, 124); return false;" id="action_124">Administration</a>, <a href="#" onclick="onTagClick(this, 10); return false;" id="action_10">Administration tools</a>, <a href="#" onclick="onTagClick(this, 166); return false;" id="action_166">Advanced error handling</a>, <a href="#" onclick="onTagClick(this, 101); return false;" id="action_101">Analytics - charts</a>, <a href="#" onclick="onTagClick(this, 100); return false;" id="action_100">Analytics - dashboards</a>, <a href="#" onclick="onTagClick(this, 102); return false;" id="action_102">Analytics - desktop</a>, <a href="#" onclick="onTagClick(this, 106); return false;" id="action_106">Analytics - expression language</a>, <a href="#" onclick="onTagClick(this, 103); return false;" id="action_103">Analytics - other</a>, <a href="#" onclick="onTagClick(this, 72); return false;" id="action_72">Analytics - sources</a>, <a href="#" onclick="onTagClick(this, 71); return false;" id="action_71">Analytics system</a>, <a href="#" onclick="onTagClick(this, 170); return false;" id="action_170">Application appearance</a>, <a href="#" onclick="onTagClick(this, 23); return false;" id="action_23">Applied objects</a>, <a href="#" onclick="onTagClick(this, 177); return false;" id="action_177">Attribute fill checks</a>, <a href="#" onclick="onTagClick(this, 51); return false;" id="action_51">Automated testing</a>, <a href="#" onclick="onTagClick(this, 167); return false;" id="action_167">Autorun</a>, <a href="#" onclick="onTagClick(this, 120); return false;" id="action_120">Background and scheduled jobs</a>, <a href="#" onclick="onTagClick(this, 173); return false;" id="action_173">Backups</a>, <a href="#" onclick="onTagClick(this, 49); return false;" id="action_49">Binary data</a>, <a href="#" onclick="onTagClick(this, 13); return false;" id="action_13">Binary data storage</a>, <a href="#" onclick="onTagClick(this, 121); return false;" id="action_121">Calculation registers</a>, <a href="#" onclick="onTagClick(this, 148); return false;" id="action_148">Calendars</a>, <a href="#" onclick="onTagClick(this, 55); return false;" id="action_55">Catalogs</a>, <a href="#" onclick="onTagClick(this, 63); return false;" id="action_63">Charts</a>, <a href="#" onclick="onTagClick(this, 156); return false;" id="action_156">Charts of accounts</a>, <a href="#" onclick="onTagClick(this, 159); return false;" id="action_159">Charts of calculation types</a>, <a href="#" onclick="onTagClick(this, 114); return false;" id="action_114">Charts of characteristic types</a>, <a href="#" onclick="onTagClick(this, 14); return false;" id="action_14">Client application</a>, <a href="#" onclick="onTagClick(this, 59); return false;" id="action_59">Client application form</a>, <a href="#" onclick="onTagClick(this, 70); return false;" id="action_70">Client application installation</a>, <a href="#" onclick="onTagClick(this, 122); return false;" id="action_122">Client applications</a>, <a href="#" onclick="onTagClick(this, 178); return false;" id="action_178">Client/server interaction</a>, <a href="#" onclick="onTagClick(this, 4); return false;" id="action_4">Collaboration system</a>, <a href="#" onclick="onTagClick(this, 91); return false;" id="action_91">Collaboration System</a>, <a href="#" onclick="onTagClick(this, 86); return false;" id="action_86">Command interface</a>, <a href="#" onclick="onTagClick(this, 58); return false;" id="action_58">Common attributes / Data separation</a>, <a href="#" onclick="onTagClick(this, 36); return false;" id="action_36">Common objects</a>, <a href="#" onclick="onTagClick(this, 118); return false;" id="action_118">Configuration comparison and merging</a>, <a href="#" onclick="onTagClick(this, 180); return false;" id="action_180">Configuration comparison reports</a>, <a href="#" onclick="onTagClick(this, 38); return false;" id="action_38">Configuration extensions</a>, <a href="#" onclick="onTagClick(this, 134); return false;" id="action_134">Configuration extensions,</a>, <a href="#" onclick="onTagClick(this, 153); return false;" id="action_153">Configuration installation</a>, <a href="#" onclick="onTagClick(this, 2); return false;" id="action_2">Configuration properties</a>, <a href="#" onclick="onTagClick(this, 67); return false;" id="action_67">Configuration repositories</a>, <a href="#" onclick="onTagClick(this, 136); return false;" id="action_136">Cross-platform architecture</a>, <a href="#" onclick="onTagClick(this, 169); return false;" id="action_169">Cryptography</a>, <a href="#" onclick="onTagClick(this, 8); return false;" id="action_8">Cryptography support</a>, <a href="#" onclick="onTagClick(this, 5); return false;" id="action_5">Data Accelerator</a>, <a href="#" onclick="onTagClick(this, 22); return false;" id="action_22">Data accelerator</a>, <a href="#" onclick="onTagClick(this, 97); return false;" id="action_97">Data access restrictions</a>, <a href="#" onclick="onTagClick(this, 126); return false;" id="action_126">Data analysis</a>, <a href="#" onclick="onTagClick(this, 25); return false;" id="action_25">Data composition system</a>, <a href="#" onclick="onTagClick(this, 90); return false;" id="action_90">Data Composition System</a>, <a href="#" onclick="onTagClick(this, 64); return false;" id="action_64">Data display</a>, <a href="#" onclick="onTagClick(this, 105); return false;" id="action_105">Data exchange</a>, <a href="#" onclick="onTagClick(this, 68); return false;" id="action_68">Data history</a>, <a href="#" onclick="onTagClick(this, 73); return false;" id="action_73">Database configuration update</a>, <a href="#" onclick="onTagClick(this, 142); return false;" id="action_142">Database configuration updates</a>, <a href="#" onclick="onTagClick(this, 7); return false;" id="action_7">Database copies</a>, <a href="#" onclick="onTagClick(this, 117); return false;" id="action_117">Database operations</a>, <a href="#" onclick="onTagClick(this, 19); return false;" id="action_19">DBMS operations</a>, <a href="#" onclick="onTagClick(this, 143); return false;" id="action_143">Defined types</a>, <a href="#" onclick="onTagClick(this, 135); return false;" id="action_135">Designer</a>, <a href="#" onclick="onTagClick(this, 152); return false;" id="action_152">Developer tools</a>, <a href="#" onclick="onTagClick(this, 171); return false;" id="action_171">Development methodology</a>, <a href="#" onclick="onTagClick(this, 20); return false;" id="action_20">Development tools</a>, <a href="#" onclick="onTagClick(this, 75); return false;" id="action_75">Distributed infobases</a>, <a href="#" onclick="onTagClick(this, 164); return false;" id="action_164">Document journals</a>, <a href="#" onclick="onTagClick(this, 33); return false;" id="action_33">Documentation</a>, <a href="#" onclick="onTagClick(this, 27); return false;" id="action_27">Dumping configurations to files/Restoring configurations from files</a>, <a href="#" onclick="onTagClick(this, 133); return false;" id="action_133">Dumping/loading configurations to files</a>, <a href="#" onclick="onTagClick(this, 92); return false;" id="action_92">Dynamic list</a>, <a href="#" onclick="onTagClick(this, 43); return false;" id="action_43">Dynamic lists</a>, <a href="#" onclick="onTagClick(this, 182); return false;" id="action_182">Dynamic update</a>, <a href="#" onclick="onTagClick(this, 53); return false;" id="action_53">Error handling</a>, <a href="#" onclick="onTagClick(this, 39); return false;" id="action_39">Event log</a>, <a href="#" onclick="onTagClick(this, 179); return false;" id="action_179">Export to Microsoft Excel</a>, <a href="#" onclick="onTagClick(this, 62); return false;" id="action_62">External data sources</a>, <a href="#" onclick="onTagClick(this, 80); return false;" id="action_80">External reports and data processors</a>, <a href="#" onclick="onTagClick(this, 119); return false;" id="action_119">File infobase Queries</a>, <a href="#" onclick="onTagClick(this, 154); return false;" id="action_154">File mode</a>, <a href="#" onclick="onTagClick(this, 78); return false;" id="action_78">File operations</a>, <a href="#" onclick="onTagClick(this, 113); return false;" id="action_113">Formatted document</a>, <a href="#" onclick="onTagClick(this, 111); return false;" id="action_111">Formatted documents</a>, <a href="#" onclick="onTagClick(this, 21); return false;" id="action_21">Full-text search</a>, <a href="#" onclick="onTagClick(this, 104); return false;" id="action_104">Functional options</a>, <a href="#" onclick="onTagClick(this, 137); return false;" id="action_137">Geographical schemas</a>, <a href="#" onclick="onTagClick(this, 54); return false;" id="action_54">Global search</a>, <a href="#" onclick="onTagClick(this, 83); return false;" id="action_83">HTML support</a>, <a href="#" onclick="onTagClick(this, 93); return false;" id="action_93">Infobase operations</a>, <a href="#" onclick="onTagClick(this, 24); return false;" id="action_24">Infobase users</a>, <a href="#" onclick="onTagClick(this, 44); return false;" id="action_44">Infobase verification and repair</a>, <a href="#" onclick="onTagClick(this, 16); return false;" id="action_16">Information registers</a>, <a href="#" onclick="onTagClick(this, 107); return false;" id="action_107">Input by string</a>, <a href="#" onclick="onTagClick(this, 46); return false;" id="action_46">Integration service</a>, <a href="#" onclick="onTagClick(this, 96); return false;" id="action_96">Interface</a>, <a href="#" onclick="onTagClick(this, 125); return false;" id="action_125">InterfaceConfiguration extensions</a>, <a href="#" onclick="onTagClick(this, 37); return false;" id="action_37">Internet-enabled functionality</a>, <a href="#" onclick="onTagClick(this, 57); return false;" id="action_57">JSON support</a>, <a href="#" onclick="onTagClick(this, 74); return false;" id="action_74">Licensing system</a>, <a href="#" onclick="onTagClick(this, 15); return false;" id="action_15">Linux</a>, <a href="#" onclick="onTagClick(this, 84); return false;" id="action_84">Localization</a>, <a href="#" onclick="onTagClick(this, 163); return false;" id="action_163">Location tools</a>, <a href="#" onclick="onTagClick(this, 184); return false;" id="action_184">Lock manager</a>, <a href="#" onclick="onTagClick(this, 18); return false;" id="action_18">macOS</a>, <a href="#" onclick="onTagClick(this, 115); return false;" id="action_115">Managed forms</a>, <a href="#" onclick="onTagClick(this, 52); return false;" id="action_52">Managed locks</a>, <a href="#" onclick="onTagClick(this, 87); return false;" id="action_87">Metadata objects</a>, <a href="#" onclick="onTagClick(this, 144); return false;" id="action_144">Mobile application</a>, <a href="#" onclick="onTagClick(this, 32); return false;" id="action_32">Mobile application builder</a>, <a href="#" onclick="onTagClick(this, 123); return false;" id="action_123">Mobile Application Builder</a>, <a href="#" onclick="onTagClick(this, 174); return false;" id="action_174">Mobile application development</a>, <a href="#" onclick="onTagClick(this, 128); return false;" id="action_128">Mobile applications</a>, <a href="#" onclick="onTagClick(this, 31); return false;" id="action_31">Mobile client</a>, <a href="#" onclick="onTagClick(this, 48); return false;" id="action_48">Mobile device-specific features</a>, <a href="#" onclick="onTagClick(this, 30); return false;" id="action_30">Mobile platform</a>, <a href="#" onclick="onTagClick(this, 132); return false;" id="action_132">Multimedia support</a>, <a href="#" onclick="onTagClick(this, 161); return false;" id="action_161">Multimedia tools</a>, <a href="#" onclick="onTagClick(this, 165); return false;" id="action_165">National settings</a>, <a href="#" onclick="onTagClick(this, 66); return false;" id="action_66">Navigation links</a>, <a href="#" onclick="onTagClick(this, 129); return false;" id="action_129">OData interface</a>, <a href="#" onclick="onTagClick(this, 147); return false;" id="action_147">OData operations</a>, <a href="#" onclick="onTagClick(this, 176); return false;" id="action_176">OpenID authentication</a>, <a href="#" onclick="onTagClick(this, 131); return false;" id="action_131">Operating system</a>, <a href="#" onclick="onTagClick(this, 146); return false;" id="action_146">Ordinary forms</a>, <a href="#" onclick="onTagClick(this, 34); return false;" id="action_34">PDF document operations</a>, <a href="#" onclick="onTagClick(this, 79); return false;" id="action_79">Pictures</a>, <a href="#" onclick="onTagClick(this, 138); return false;" id="action_138">Platform algorithms</a>, <a href="#" onclick="onTagClick(this, 95); return false;" id="action_95">Predefined data</a>, <a href="#" onclick="onTagClick(this, 77); return false;" id="action_77">Print tools</a>, <a href="#" onclick="onTagClick(this, 150); return false;" id="action_150">Printing</a>, <a href="#" onclick="onTagClick(this, 168); return false;" id="action_168">Printing documents</a>, <a href="#" onclick="onTagClick(this, 108); return false;" id="action_108">Printing tools</a>, <a href="#" onclick="onTagClick(this, 85); return false;" id="action_85">Processing PDF documents</a>, <a href="#" onclick="onTagClick(this, 45); return false;" id="action_45">Queries</a>, <a href="#" onclick="onTagClick(this, 94); return false;" id="action_94">Regional settings</a>, <a href="#" onclick="onTagClick(this, 139); return false;" id="action_139">Server cluster</a>, <a href="#" onclick="onTagClick(this, 6); return false;" id="action_6">Server clusters</a>, <a href="#" onclick="onTagClick(this, 40); return false;" id="action_40">Settings storage</a>, <a href="#" onclick="onTagClick(this, 116); return false;" id="action_116">Software licensing</a>, <a href="#" onclick="onTagClick(this, 140); return false;" id="action_140">Special tools</a>, <a href="#" onclick="onTagClick(this, 9); return false;" id="action_9">Speech recognition</a>, <a href="#" onclick="onTagClick(this, 50); return false;" id="action_50">Speech synthesis</a>, <a href="#" onclick="onTagClick(this, 60); return false;" id="action_60">Spreadsheet document</a>, <a href="#" onclick="onTagClick(this, 26); return false;" id="action_26">Spreadsheet documents</a>, <a href="#" onclick="onTagClick(this, 47); return false;" id="action_47">Standalone server</a>, <a href="#" onclick="onTagClick(this, 98); return false;" id="action_98">Standalone serverDumping configurations to files/Restoring configurations from files</a>, <a href="#" onclick="onTagClick(this, 12); return false;" id="action_12">Standard functions</a>, <a href="#" onclick="onTagClick(this, 76); return false;" id="action_76">Storing settings</a>, <a href="#" onclick="onTagClick(this, 141); return false;" id="action_141">System enumerations</a>, <a href="#" onclick="onTagClick(this, 35); return false;" id="action_35">System operation safety</a>, <a href="#" onclick="onTagClick(this, 29); return false;" id="action_29">System requirements</a>, <a href="#" onclick="onTagClick(this, 17); return false;" id="action_17">Technological log</a>, <a href="#" onclick="onTagClick(this, 160); return false;" id="action_160">Telephony</a>, <a href="#" onclick="onTagClick(this, 127); return false;" id="action_127">Temporary storages</a>, <a href="#" onclick="onTagClick(this, 181); return false;" id="action_181">Text operations</a>, <a href="#" onclick="onTagClick(this, 157); return false;" id="action_157">Thick client</a>, <a href="#" onclick="onTagClick(this, 175); return false;" id="action_175">Thin client access over the Internet</a>, <a href="#" onclick="onTagClick(this, 158); return false;" id="action_158">Third-party software</a>, <a href="#" onclick="onTagClick(this, 89); return false;" id="action_89">URLs</a>, <a href="#" onclick="onTagClick(this, 61); return false;" id="action_61">Using the clipboard</a>, <a href="#" onclick="onTagClick(this, 28); return false;" id="action_28">Web client</a>, <a href="#" onclick="onTagClick(this, 151); return false;" id="action_151">Web client and web service publishing tools</a>, <a href="#" onclick="onTagClick(this, 81); return false;" id="action_81">Web client, web service, and HTTP service publishing tools</a>, <a href="#" onclick="onTagClick(this, 172); return false;" id="action_172">Web links</a>, <a href="#" onclick="onTagClick(this, 155); return false;" id="action_155">Web services</a>, <a href="#" onclick="onTagClick(this, 65); return false;" id="action_65">Web services and HTTP services</a>, <a href="#" onclick="onTagClick(this, 3); return false;" id="action_3">WebSocket operations</a>, <a href="#" onclick="onTagClick(this, 149); return false;" id="action_149">Window management</a>, <a href="#" onclick="onTagClick(this, 99); return false;" id="action_99">Window-based interface</a>, <a href="#" onclick="onTagClick(this, 145); return false;" id="action_145">xBase support</a>, <a href="#" onclick="onTagClick(this, 56); return false;" id="action_56">XML and XDTO support</a>, <a href="#" onclick="onTagClick(this, 41); return false;" id="action_41">ZIP archive operations</a>, <a href="#" onclick="onTagClick(this, 130); return false;" id="action_130">Встроенный язык</a>, <a href="#" onclick="onTagClick(this, 109); return false;" id="action_109">Сlient application form</a>.</div></p></details><h1><a name="807fae8f-094d-11ef-963f-0050569f678a">Version 8.3.27</a></h1><p title="Версия 8.3.27" class="tag_0"><a name="807fae9e-094d-11ef-963f-0050569f678a"></a>Version 8.3.27 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#807fae90-094d-11ef-963f-0050569f678a">New functionality and changes</a></li><li><a href="#807fae91-094d-11ef-963f-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#807fae92-094d-11ef-963f-0050569f678a">Optimization</a></li><li><a href="#807fae93-094d-11ef-963f-0050569f678a">Changes that affect system behavior</a></li><li><a href="#807fae94-094d-11ef-963f-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#807fae95-094d-11ef-963f-0050569f678a">Renamed objects</a></li><li><a href="#807fae96-094d-11ef-963f-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#807fae98-094d-11ef-963f-0050569f678a">Library updates
</a></li><li><a href="#807fae99-094d-11ef-963f-0050569f678a">Demo configuration changes</a></li><li><a href="#807fae9a-094d-11ef-963f-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#807fae9b-094d-11ef-963f-0050569f678a">Transition from the previous version to the version 8.3.27</a></li></ul><h2><a name="807fae90-094d-11ef-963f-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.27" class="compat tag_2 tag_1"><td><a name="19898a67-0bae-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>New value for the<span class="interface"> Compatibility mode </span>configuration property: <span class="interface">Version 8.3.26</span>.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.25 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.26 or earlier can now run on version 8.3.27 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.27 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.26 after the migration to version 8.3.27. Even if you have disabled the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.27" class="tag_3"><td><a name="243a0257-0956-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 3); return false;">WebSocket operations</a>.<br></td><td>Now 1C:Enterprise can function as a WebSocket client. This feature is available for the thin, thick, and web clients and the 1C:Enterprise server.
You can create WebSocket clients in the "<span class="interface">Common - WebSocket clients</span>" branch of the configuration object tree.
New global context properties: <span class="term">WebSocketClientConnectionHandlers </span>and <span class="term">WebSocketClients</span>.</td><td>This feature was not provided.</td><td>1C:Enterprise applications can function as a WebSocket client.</td></tr><tr title="Версия 8.3.27" class="tag_4"><td><a name="2ed1b428-0d41-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: global search can search by context conversation messages. The maximum number of found messages (for both noncontext and context conversations) is 20.</td><td>Previously, global search only searched in noncontext conversation messages. The maximum number of found messages was 15.</td><td>Expanded global search features.</td></tr><tr title="Версия 8.3.27" class="tag_5 tag_6"><td><a name="5a39c020-12b3-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 5); return false;">Data Accelerator</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The Data Accelerator now allows you to choose how the database is stored: either entirely in RAM, or using both RAM and disk space.
You can set the storage directory using the standard mechanism for changing data storage directories for cluster services (specifically, the <span class="term">DataAcceleratorService</span>). This functionality is supported by all cluster server administration tools.
The <span class="term">DatabaseCopiesManager.Add()</span> method has a new <span class="term">DataAcceleratorDataStorageVariant </span>parameter that allows you to specify the location of the Data Accelerator database. Introduced a new property: <span class="term">DatabaseCopyManager.DataAcceleratorDataStorageVariant</span>.
The standard database copy management tool now supports this feature in both the new copy creation dialog and the list of database copies.</td><td>Until now, the Data Accelerator only stored the database in RAM. This meant that in the event of an unexpected shutdown of the Data Accelerator or the server cluster, the database had to be repopulated from the main database, causing delays or even the inability to generate required reports.</td><td>Now, the Data Accelerator can be set up so that it doesn't require repopulating the database upon restart. This change ensures quicker access to the data you need.</td></tr><tr title="Версия 8.3.27" class="tag_7"><td><a name="f0e6d415-12ba-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Now you can get detailed information about the database copy state. With this information, you can evaluate the current database copy state, the copy update state, and so on. You can now run database copy updates in the background using a system background job.
New method: <span class="term">DatabaseCopiesManager.UpdateInBackgroundMode()</span>.<p>New method: <span class="term">DatabaseCopyManager.GetCopyInfo()</span>.
You can view the state of selected copy instances in the standard database copy management tool. The copy update is now started in the background.</p></td><td>This feature was not provided.<p>You could get only the date of the last data replication.</p></td><td>Advanced troubleshooting when operating with database copies.</td></tr><tr title="Версия 8.3.27" class="tag_8"><td><a name="b3eb118e-1697-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>You can now check the status of certificates at any point in the past. Use the <span class="term">UniversalVerificationDate </span>parameter of the crypto manager's <span class="term">CheckCertificate()</span> and <span class="term">CheckCertificateAsync()</span> methods.
New features for cryptography certificates include:<ul><li>Checking the validity period of the private key. Use the <span class="term">UniversalStartDateOfPrivateKey </span>and <span class="term">UniversalEndDateOfPrivateKey </span>properties of the <span class="term">CryptoCertificate </span>object.</li><li>Retrieving a list of certificate extensions. Use the <span class="term">CertificateExtensions </span>property of the <span class="term">CryptoCertificate </span>object.</li><li>Obtaining certificate extensions in raw form. Use the <span class="term">CertificateExtensionsAsRawData </span>property of the <span class="term">CryptoCertificate </span>object.</li><li>Identifying the algorithms used to generate the public key and signature, along with obtaining the digital signature itself. Use the <span class="term">PublicKeyAlgorithm</span>, <span class="term">SignatureAlgorithm</span>, and <span class="term">SignatureValue </span>properties of the <span class="term">CryptoCertificate </span>object.</li></ul><p>The <span class="term">CryptoCertificate.Extensions</span> property is deprecated. Instead, use <span class="term">CryptoCertificate.CertificateExtensions</span>.</p></td><td>These features were not provided.</td><td>Enhanced the cryptography certificate functionality. You can now verify that the private key is usable (i.e., it hasn’t expired).</td></tr></table><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae91-094d-11ef-963f-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.27" class="tag_4"><td><a name="780ad767-0952-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The thin client running on Linux now supports video calls.</td><td>On Linux, you could only use video calls in the web client.</td><td>Advanced collaboration system features.</td></tr><tr title="Версия 8.3.27" class="tag_9 tag_10"><td><a name="db4494d3-0b91-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 9); return false;">Speech recognition</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Upgrade: the tool for managing local speech recognition is updated.<ul><li>New checkbox for the dialog box for creating a client/server infobase: <span class="interface">Deny local speech recognition</span>.</li><li>New parameter for the <span class="interface">conf.cfg </span>file located in the infobase directory (for the file infobase): <span class="term">DisableLocalSpeechToText</span>.</li><li>In the dialog box for adding a file infobase, the <span class="interface">Deny local speech recognition</span> checkbox is deleted.</li><li>The<span class="term"> /DisableLocalSpeechToText </span>command-line option of the client application startup is deleted.</li></ul></td><td>Previously, other tools were used to manage local speech recognition:<ul><li>In the dialog box for adding an infobase, the <span class="interface">Deny local speech recognition</span> checkbox was available.</li><li>The <span class="term">/DisableLocalSpeechToText </span>command-line option of the client application startup was available.</li></ul></td><td>Local speech recognition management is unified with other similar 1C:Enterprise tools.</td></tr><tr title="Версия 8.3.27" class="tag_6"><td><a name="b0360c2c-0d3c-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When an abnormal termination dump is generated by the cluster monitoring tool, the <span class="term">SIGABRT </span>signal is used to complete the process and generate the dump.</td><td>When an abnormal termination dump was generated by the cluster monitoring tool, the <span class="term">SIGSEGV </span>signal was used to complete the process and generate the dump.</td><td>When 1C support analyzes abnormal termination dumps, it will be easier to distinguish between dumps generated by the cluster monitoring tool (<span class="term">SIGABRT</span>) and dumps generated as a result of critical application errors (<span class="term">SIGSEGV</span>).</td></tr><tr title="Версия 8.3.27" class="tag_11 tag_6"><td><a name="9ccbe078-0d40-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Now you can forcibly terminate the session with isolated attachment of add-ins, even if the session to terminate is waiting for an add-in method execution.</td><td>Previously, you could not forcibly terminate the session with isolated attachment of add-ins if the session to terminate was waiting for an add-in method execution.</td><td>Improved server cluster administration. Reduced the number of situations when the administrator cannot terminate the session which locks the normal operation of the system.</td></tr><tr title="Версия 8.3.27" class="tag_4"><td><a name="6b06265f-11f1-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>During video calls, you can inform call participants about the desire to speak out or ask a question (raise your hand). Several people can raise their hand simultaneously.<p>Information about the raised hand is displayed in the frame of the user who raised their hand. The number of participants who raised their hand is also displayed in the video call window. Users who raised their hand are displayed in the order they raised it (the earlier they raised their hand, the higher they will be in the list).</p><p>If the user who raised their hand leaves the video call, the system will lose their raise status. After returning, this user will need to raise their hand again if it is still necessary.</p></td><td>This feature was not provided.</td><td>In conversations of group video calls, it will become easier to "request the floor", while the number of attempts by participants to interrupt each other will not decrease.</td></tr><tr title="Версия 8.3.27" class="tag_12 tag_13"><td><a name="778e6e47-12a8-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>The interface of the standard <span class="interface">Binary data storage management </span>function is improved to make the function more user-friendly and convenient.</td><td>The interface of the standard <span class="interface">Binary data storage management</span> function was less user-friendly and convenient.</td><td>Improved interface of the standard <span class="interface">Binary data storage management</span> function.</td></tr><tr title="Версия 8.3.27" class="tag_14"><td><a name="84b233e7-12be-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>When starting a client application with a base configuration, a form with a progress indicator will be displayed for analyzing the configuration and hardware of the current computer.</td><td>Previously, when starting a client application with a base configuration, while analyzing the configuration and hardware of the current computer, the user was not informed in any way about what the client application was doing. As a result, it looked like the system was "hanging".</td><td>We expect this feature to reduce the number of user complaints about system freezes when starting base configurations (especially with a large amount of metadata).</td></tr><tr title="Версия 8.3.27" class="tag_10"><td><a name="270c89e2-16b1-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New optional parameter for the command to complete the background update of the Designer agent (<span class="term">config update‑db-cfg --background-finish</span>): <span class="term">--session-terminate</span>. It allows you to manage the forced termination of active sessions if you need to set an exclusive database lock.<p>New optional parameter for the background update completion command (<span class="term">config update‑db-cfg --background-finish</span>) and the interactive configuration update command (<span class="term">config update-db-cfg</span>) of the Designer agent: <span class="term">--session-terminate-message</span>. It allows you to specify the reason for terminating the session on the client.</p></td><td>This feature was not provided.</td><td>Unified interactive behavior of Designer and the behavior in agent mode.</td></tr></table><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae92-094d-11ef-963f-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.27" class="tag_13"><td><a name="282ac087-0ba1-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>New feature: data writing to the built-in binary data storage is improved.</td><td>Writing to the built-in binary data storage took more time.</td><td>Faster data writing to the built-in binary data storage.</td></tr><tr title="Версия 8.3.27" class="tag_8 tag_15"><td><a name="e3040761-0bac-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Now the cryptography manager creates a certificate chain faster on Linux. </td><td>Previously, the cryptography manager needed more time to create a certificate chain on Linux. </td><td>Faster creation of a certificate chain by the cryptography manager on Linux. </td></tr><tr title="Версия 8.3.27" class="tag_16"><td><a name="abbfea3a-0c4d-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>If the information register record was previously read from the infobase, then when calling the <span class="term">Write()</span> method of the information register record manager in replacement mode, the current values of key fields are checked to match the values of the read record. If the key fields match, the current record is updated.</td><td>If the information register record was previously read from the infobase, then when calling the <span class="term">Write()</span> method of the information register record manager in replacement mode, writing was always performed in two steps: deleting an existing record and writing a new one.</td><td>Faster writing of single information register records if all key fields of the record remain unchanged during writing.</td></tr><tr title="Версия 8.3.27" class="tag_17"><td><a name="ba94c3f2-0d25-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>The deletion of outdated technological log files does not lock user operations and is performed in the background.</td><td>The deletion of outdated technological log files could lock user operations (if the number of deleted files was large) and was performed by the server cluster in synchronous mode.</td><td>Reduced impact of technological operations of the server cluster on user operations.</td></tr><tr title="Версия 8.3.27" class="tag_18"><td><a name="c3092107-11cb-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br></td><td>New features: the client application operation is optimized when running on macOS. Rendering of client application windows and scrolling of large spreadsheet documents is accelerated.</td><td>Previously, when the client application was running on macOS, the speed was low, and displaying and scrolling the contents of the client application windows took a long time.</td><td>Optimized operation of the client application when running on macOS.</td></tr><tr title="Версия 8.3.27" class="tag_19 tag_6"><td><a name="b2bc608f-11da-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Deletion of temporary tables (and their indexes) is accelerated when running on the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.</td><td>Deletion of temporary tables (and their indexes) took more time when running on the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.</td><td>Accelerated deletion of temporary tables (and their indexes) when running on the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.</td></tr><tr title="Версия 8.3.27" class="tag_20"><td><a name="3bf850f7-11f8-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Now you can build a metadata index in Designer in the background.<p>To disable it, use the <span class="term">/DisableBackgroundIndexBuild </span>command-line option.</p></td><td>Previously, metadata index building started in Designer when this index was first used by the user. This locked the execution of the requested operation until the index was generated.</td><td>The first use of the following operations can be accelerated after changing the metadata: searching for references to the configuration object, deleting the configuration object, and renaming the configuration object. This will happen if the metadata index managed to rebuild in the background.</td></tr><tr title="Версия 8.3.27" class="tag_14"><td><a name="333a52b1-1286-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The time of the first thin client startup in a file infobase is reduced after performing the following operations:<ul><li>Creating a new infobase.</li><li>Restoring an infobase from a DT file.</li><li>Restoring a configuration from a CF file.</li><li>Updating an infobase configuration.</li></ul></td><td>Previously, the first thin client startup in a file infobase took more time.</td><td>Reduced time of the first thin client startup in a file infobase in some cases.</td></tr><tr title="Версия 8.3.27" class="tag_20"><td><a name="b817e1b3-1286-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The search for references to configuration objects, as well as the operations that use this search (renaming the configuration object and deleting the configuration object) are optimized in Designer.</td><td>Previously, search for references to configuration objects in Designer took more time.</td><td>Accelerated search for references to configuration objects and the related operations (renaming and deleting the configuration object) in Designer.</td></tr><tr title="Версия 8.3.27" class="tag_19 tag_6"><td><a name="171297bf-12c3-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The server cluster operation under load is optimized when using the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.</td><td>The server cluster operation under load when using the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems was non-optimal.</td><td>Optimized the server cluster operation under load when using the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.</td></tr><tr title="Версия 8.3.27" class="tag_21"><td><a name="8b663114-6454-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>The algorithm of generating a full-text search index is improved to reduce the index volume. You can see the improvement on full-text search indexes of a great size (over 10 GB).</td><td>The previous algorithm generated indexes of a greater size.</td><td>Reduced full-text search index volume for great indexes (over 10 GB).</td></tr><tr title="Версия 8.3.27" class="tag_19"><td><a name="e1fe8950-66d5-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Upgrade: temporary table cleanup takes less time when using the Microsoft SQL Server and PostgreSQL DBMS (and inherited DBMS) in case of heavy load on infobases with many tables.</td><td>Previously, temporary table cleanup took more time when using the Microsoft SQL Server and PostgreSQL DBMS (and inherited DBMS) in case of heavy load on infobases with many tables.</td><td>Faster temporary table cleanup when using the Microsoft SQL Server and PostgreSQL DBMS (and inherited DBMS) in case of heavy load on infobases with many tables.</td></tr><tr title="Версия 8.3.27" class="tag_22"><td><a name="d098ed05-b3be-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>Some types of queries, including queries to columns with variable length, are optimized.
Improved Data accelerator stability in case of low RAM during query execution.</td><td>Some types of queries, including queries to columns with variable length, required more computer resources.
Data accelerator was unstable when executing queries in case of a lack of RAM.</td><td>Improved Data Accelerator performance.</td></tr><tr title="Версия 8.3.27" class="tag_21"><td><a name="edcc9aa5-b3bf-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>A computer now uses less RAM when generating and merging full-text search indexes.</td><td>Generating and merging full-text search indexes required more RAM.</td><td>Reduced RAM consumption when generating and merging full-text search indexes.</td></tr></table><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae93-094d-11ef-963f-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.27" class="compat tag_23 tag_1"><td><a name="b4702858-0c44-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>New property for a metadata object that describes a table: <span class="term">LineNumberLength</span>. You can use this property to manage the number of rows that can be saved in the applied object table. The allowed property values are 5, 6, 7, 8, and 9. The property cannot be changed in the extension.<p>This change is not implemented in 8.3.26 compatibility mode.</p></td><td>An applied object table could not contain more than 99,999 rows (the length of the row number is 5 decimal places).</td><td>You can manage the number of rows that can be saved in the applied object table. If necessary, you can save 999,999,999 rows in the object table.</td></tr><tr title="Версия 8.3.27" class="tag_24 tag_10 tag_14"><td><a name="d9314d71-11bf-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 24); return false;">Infobase users</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>You can authentiate over an email. Email authetication is unavailable when using the parameterized launch mode.<p>New property: <span class="term">InfoBaseUser.EmailAuthe</span><span class="term">ntication</span>. </p><p>New methods for the <span class="term">AdditionalAuthenticationSettingsManager</span> object: <span class="term">SetEmailAuthenticationSettings()</span> and <span class="term">GetEmailAuthenticationSettings()</span>.</p><p>New object: <span class="term">EmailAuthenticationSettings</span>.</p><p>New property: <span class="term">PasswordRecoverySettings.VerificationCodeEffectivePeriod</span>.</p><p>New system enumeration value: <span class="term">AuthenticationMode.EmailAuthentication</span>.</p><p>New command of the command-line for the client application startup: <span class="term">/EmailAuth</span>.</p><p>For the <span class="term">type </span>attribute of the <span class="term">method </span>element of the <span class="interface">default.vrd </span>file (<span class="term">point.authentication.</span><span class="term">logon</span><span class="term">View</span>) new email value.</p><p>There is now more information for event log events:</p><ul><li><span class="term">_$User$_.New</span>,</li><li><span class="term">_$User$_.NewError</span>,</li><li><span class="term">_$User$_.Upd</span><span class="term">ate</span>,</li><li><span class="term">_$User$_.UpdateError</span>,</li><li><span class="term">_$InfoBase$_.AdditionalAuthenticationSettingsUpdate</span>,</li><li><span class="term">_$InfoBase$_.</span></li></ul><p>We will inform you about the launch of the standard service for sending emails with a confirmation code for signing in via email in an information letter.</p></td><td>This feature was not provided.</td><td>Extended the list of infobase authentication options.</td></tr><tr title="Версия 8.3.27" class="tag_10"><td><a name="1085dcdf-11f7-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Application installation utilities (autorun and SetupV8, <a href="http://1c-dn.com/library/autorun_application/" target="_blank">Read more</a>.) now can define the format of the application distribution package: unpacked or a ZIP archive. When an archive is found, the utilities will automatically unpack this archive, then install and delete temporary files.</td><td>The application installation utilities were able to work only with unpacked application distribution packages. The user needed to unpack the distribution package manually and then run the installer.</td><td>Simplified installation of applications.</td></tr><tr title="Версия 8.3.27" class="tag_13"><td><a name="13a49183-11fa-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>You can create an external binary data storage within the S3 container. For example, if the number of containers a user can create is limited. You can specify a path to the binary data storage inside the S3 container.<p>New property: <span class="term">BinaryDataExternalStorageConnectionParameters.Directory</span>.</p><p>You can split import a file to the storage if there is a size limit for data to transfer. The part size is selected automatically.</p><p>A file is split received from the storage. A file part equals 100 MB and you cannot set up the size.</p><p>New processing of the request quantity limitation for the S3 container. If there is a limit to the number of requests, the read/write request execution is attempted multiple times with delay. You have 4 attempts maximum. Timeout between attempts does not exceed 20 seconds.</p></td><td>These features were not provided.</td><td>External binary data storage helps to consider some S3 container limitations.</td></tr><tr title="Версия 8.3.27" class="tag_6 tag_13 tag_10"><td><a name="9d264961-12a4-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The 1C:Enterprise server cluster administration tools now include features for managing binary data storage:<ul><li>New 1C:Enterprise language object: <span class="term">AdministrationBinaryDataStorage</span>.
New method: <span class="term">AdministrationInfoBase.GetBinaryDataStorages</span>.</li><li>New interface for the COM connector: <span class="term">IBinaryDataStorageInfo</span>. New methods for the <span class="term">IWorkingProcessConnection </span>interface: <span class="term">GetInfoBaseBinaryDataStorages()</span>, <span class="term">ClearBinaryDataStorageUnusedSpace()</span>, <span class="term">CreateBinaryDataStorageFullBackup()</span>, <span class="term">CreateBinaryDataStorageDifferentialBackup()</span>, <span class="term">LoadBinaryDataStorageFullBackup()</span>, <span class="term">LoadBinaryDataStorageDifferentialBackup()</span>.</li><li>New object in the Java administration server interface: <span class="term">IBinaryDataStorageInfo</span>. New methods for the <span class="term">IAgentAdminConnection </span>object: <span class="term">getBinaryDataStorages()</span>, <span class="term">сlearBinaryDataStorageUnusedSpace()</span>, <span class="term">createBinaryDataStorageFullBackup()</span>, <span class="term">createBinaryDataStorageDifferentialBackup()</span>, <span class="term">loadBinaryDataStorageFullBackup()</span>, <span class="term">loadBinaryDataStorageDifferentialBackup()</span>.</li><li>New mode for the <span class="interface">rac </span>utility: <span class="term">binary-data-storage</span>. Specified parameter assignment for the Infobase mode (available in the built-in utility help).</li><li>New mode for the <span class="interface">ibcmd </span>utility: <span class="term">binary-data-storage</span>.</li><li>Now you can view binary data storages connected to the infobase when using the cluster administration console and the<span class="interface"> </span><span class="interface">Server management </span>function. New subordinate item of the <span class="interface">Binary data storage </span>for the infobase detail<span class="interface"> </span>item.</li></ul></td><td>These features were not provided. Binary data storage administration was only possible by using the storage API.</td><td>Administrating binary data storages is now similar to administrating other server clusters.</td></tr><tr title="Версия 8.3.27" class="tag_4"><td><a name="5823691a-16a0-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>To integrate the collaboration system with WhatsApp, you can send a template message to a user who has not yet written to the integration user (a new user).<p>New property for the <span class="term">CollaborationSystemConversation </span>and <span class="term">CollaborationSystemConversationsFilter </span>objects: <span class="term">ExternalID</span>.</p><p>For WhatsApp integration, the <span class="term">ExternalID </span>property is filled with the phone number of the integration user.</p><p>For a WebHook conversation, users specified as default integration users are automatically added to the conversation if, upon receiving the first message, the conversation has no users other than an external integration user.</p></td><td>This feature was not provided.</td><td>The application can start a conversation with a user if integration with WhatsApp is used.</td></tr><tr title="Версия 8.3.27" class="compat tag_25 tag_1"><td><a name="2e368ea2-16ae-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Now you can use formatted strings (templates, conditional appearance, using 1C:Enterprise language functions that return a formatted string, and other) during output to a spreadsheet document in the data composition system. Formatted strings are ignored during output to the chart.<p>Interactive tools for data composition system now support formatted strings.</p><p>New appearance items for the <span class="term">DataCompositionAreaTemplateFieldAppearance.AvailableParameters </span>object: <span class="term">BackColor</span>, <span class="term">TextColor</span>, <span class="term">Font</span>, <span class="term">MarkNegatives</span>, <span class="term">Picture</span>, and <span class="term">TextPositionRelativeToPicture</span>.
The <span class="term">Text </span>appearance item of the <span class="term">DataCompositionAppearance.AvailableParameters</span> object now supports the <span class="term">FormattedString </span>type.</p><p>The <span class="term">Presentation()</span> function of the expression language of the data composition system returns a value of the <span class="term">FormattedString </span>type if the type of the parameter value is also <span class="term">FormattedString</span>.</p><p>This change is not implemented in 8.3.26 compatibility mode.</p></td><td>The data composition system did not support formatted strings.<p>For cells that display multiple fields, the appearance was applied to the whole cell. </p><p>The <span class="term">Presentation()</span> function of the expression language of the data composition system returned an empty string for a value of the <span class="term">FormattedString </span>type.</p></td><td>Expanded appearance features when outputting a report based on the data composition system to a spreadsheet document.</td></tr><tr title="Версия 8.3.27" class="compat tag_26 tag_1"><td><a name="f93c3ef6-16ae-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When you set a value of the <span class="term">FormattedString </span>type to the cell parameter of a spreadsheet document, the parameter formatting is saved in the resulting document. For this, the resulting cell becomes a cell with a formatted text.<p>The basic format for the inserted parameter value is:</p><ul><li>For a cell with a parameter: the cell format.</li><li>For a simple cell with a template: the cell format.</li><li>For a formatted cell with a template: the format of the first "[" character in the parameter name.</li></ul><p>This change is not implemented in 8.3.26 compatibility mode.</p></td><td>This feature was not provided. <p>The set value was reduced to plain text, the text type of the resulting cell remained the same as the text type of the cell with the parameter in the template.</p></td><td>Expanded spreadsheet document appearance features.</td></tr><tr title="Версия 8.3.27" class="tag_7"><td><a name="15aa3f6a-17fe-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Upgrade: changed the system behavior when updating data in a database copy that runs on Microsoft SQL Server using replication <span class="term">Version 2</span>. If, during data replication, a new infobase table cannot be connected to the change data capture (CDC), all tables that were previously connected to the change data capture continue to be updated. After updating, an exception of the <span class="term">DatabaseCopyError </span>category is thrown with a text describing the issue and containing a list of tables that are not connected to the tool. For a batch update, an exception is thrown after updating only if all tables added to the change data capture (CDC) are ready to run queries.<p>To retry connecting new tables to the change data capture, update the copy data again while reducing the load on the original infobase.</p></td><td>The system behavior when updating data in a database copy running on Microsoft SQL Server using replication <span class="term">Version 2</span> was different. If, during data replication, a new database table could not be connected to the change data capture (CDC), the update was stopped and the source text of the SQL Server error, which was difficult to understand, was displayed to the user.</td><td>Improved diagnostics and system behavior in case of issues when updating data in a database copy running on Microsoft SQL Server.</td></tr><tr title="Версия 8.3.27" class="tag_27"><td><a name="cda44886-5b94-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is 2.20.</td><td>The format version of configuration dump to XML files was 2.19.</td><td>Configuration dump to XML files supports new platform features.</td></tr><tr title="Версия 8.3.27" class="tag_7 tag_5"><td><a name="9f3e5a5b-9856-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br><a href="#" onclick="onTagClick(this, 5); return false;">Data Accelerator</a>.<br></td><td><ul><li>If a low memory error occurs while executing an SQL query on a database copy hosted in the Data Accelerator, the copy is not turned off.</li><li>If the query settings for the database copy allow the query to be executed on another copy (or on the primary database), the query is executed without any error notification to the user.</li><li>Conversely, if the query settings do not permit execution on another copy (or on the primary database), the query terminates with an error. The user receives an error message based on the platform mechanism used. In this case, the Data Accelerator error is the cause of the error displayed.</li></ul></td><td>If a low memory error occurs while executing an SQL query on a database copy hosted in the Data Accelerator, the query is terminated with an error and the copy is marked as turned off. When you turn on the copy later, it will be fully updated.</td><td>Reduced number of unexpected query terminations when accessing database copies in the Data Accelerator. Reduced frequency of unexpected full data updates in Data Accelerator-hosted database copies.</td></tr><tr title="Версия 8.3.27" class="tag_5"><td><a name="92c52005-9859-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 5); return false;">Data Accelerator</a>.<br></td><td>Data Accelerator authentication and connection errors are categorized under <span class="term">ErrorCategory.DatabaseCopyError</span>.</td><td>Data Accelerator authentication and connection errors are categorized under <span class="term">ErrorCategory.StoredDataError</span>.</td><td>Authentication and connection errors in Data Accelerator have been more accurately categorized and described to better reflect actual usage scenarios.</td></tr><tr title="Версия 8.3.27" class="tag_25"><td><a name="8a2bd98f-98e1-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If the Value property of the <span class="term">DataCompositionAreaTemplateValueCollectionCell </span>object is set to <span class="term">Undefined</span>, XDTO serialization of such object does not result in an error.</td><td>If the Value property of the <span class="term">DataCompositionAreaTemplateValueCollectionCell </span>object was set to <span class="term">Undefined</span>, XDTO serialization of such object resulted in an error.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae94-094d-11ef-963f-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.27" class="tag_28 tag_29"><td><a name="f04c75a1-0bad-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft Windows XP, Windows Vista, Server 2003, and Server 2008 are no longer supported.<p>For the web client in Mozilla Firefox, the web browser version must be 68 or later.</p></td><td>Previously, 1C:Enterprise supported Microsoft Windows XP, Windows Vista, Server 2003, and Server 2008.<p>For the web client in Mozilla Firefox, the web browser version had to be 52 or later.</p></td><td>Ended support of outdated operating systems and web browsers.</td></tr><tr title="Версия 8.3.27" class="tag_6 tag_24 tag_10"><td><a name="4136b18d-11ba-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 24); return false;">Infobase users</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can allocate user sessions by production servers. The allocation is performed using functionality assignment rules. Users are grouped either by name or by assignment rule key.<p>New property: <span class="term">InfoBaseUser.AssignmentRuleKey</span>. You can edit this property using the standard user list tools in Designer in 1C:Enterprise mode.</p><p>New additional parameters for functionality assignment rules: <span class="term">UserName </span>and <span class="term">UserAssignmentRuleKey</span>.</p></td><td>This feature was not provided.<p>Sessions of new users were allocated by production servers sequentially in accordance with the load balancing tools.</p></td><td>You can transfer sessions of individual users or user groups to production servers.</td></tr><tr title="Версия 8.3.27" class="tag_6 tag_10"><td><a name="235367a5-11cd-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can set up the schedule for restarting working processes of server cluster. You can set the schedule for the entire cluster as well as for each working process individually (it has the priority over the entire server cluster schedule). Cluster working processes (if multiple) are restarted sequentially. Schedule format is same as the <span class="interface">cron </span>utility schedule format (in the Linux OS). The <span class="interface">Restart interval </span>parameter of the server cluster properties is deprecated and not used for operations.<p>Now you can disable a specific working process.
The 1C:Enterprise language objects now have:</p><ul><li>New object property: <span class="term">AdministrationCluster.RestartSchedule</span>.</li><li>New object property: <span class="term">AdministrationWorkServer.RestartSchedule</span>.</li><li>New method object: <span class="term">AdministrationWorkProcess.</span><span class="term">TurnOff</span><span class="term">().</span></li></ul><p>Objects of the COM interface of the server cluster administration now have: </p><ul><li>New object property: <span class="term">IClusterInfo.RestartShcedule</span>.</li><li>New object property: <span class="term">IWorkingServerInfo.RestartSchedule</span>.</li><li>New object property:<span class="term"> IWorkingProcessInfo.TurnedOn</span>.</li><li>New object method: <span class="term">IServerAgentConnection.TurnOffWorkingProcess().</span></li><li>The<span class="term"> IClusterInfo.LifeTimeLimit </span>property is deprecated and not recommended to use.</li><li>The <span class="term">IWorkingProcessInfo.IsEnable() </span>method is deprecated.</li></ul><p>Interface administration objects from Java now have:</p><ul><li>New object methods: <span class="term">IClusterInfo getRestartShcedule() </span>and <span class="term">setRestartShcedule().</span></li><li>New object methods for <span class="term">IWorkingServerInfo</span>: <span class="term">getRestartShcedule()</span> and <span class="term">setRestartShcedule()</span>.</li><li>New object property: <span class="term">IWorkingProcessInfo.TurnedOn()</span>.</li><li>New object method: <span class="term">IAgentAdminConnection.turnOffWorkingProcess(</span><span class="term">)</span>.</li><li><span class="term">The IWorkingProcessInfo.isEnable() </span>method is deprecated.</li></ul><p>The <span class="interface">rac </span>utility now have the following start line commands:</p><ul><li><span class="term">--restart-schedule </span>for the <span class="term">cluster </span>and <span class="term">server </span>modes.</li><li><span class="term">--turn-off</span> for the <span class="term">p</span><span class="term">rocess </span>mode.</li></ul></td><td>This feature was not provided.<p>Previously, you could specify a working process restart interval counted off only from the working process restart point.</p></td><td>Now setting up restart time for working processes of the server cluster is more flexible.</td></tr><tr title="Версия 8.3.27" class="tag_20"><td><a name="07be5911-1285-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>After a Designer agent runs the <span class="term">infobase-tools restore-ib</span> command:<ul><li>Warning that it is required to reconnect to the Designer agent is displayed (interactive in text mode, informative when displaying results in a json file).</li><li>The infobase session is terminated. SSH connection is terminated.</li><li>The Designer agent is not restarted.</li><li>To continue operations, reconnect to the infobase (the Designer agent process remains the same).</li></ul></td><td>After a Designer agent ran the <span class="term">infobase-tools restore-ib </span>command:<ul><li>Warning that the Designer agent is restarted was displayed.</li><li>The Designer agent was restarted.</li><li>To continue operations, it was necessary to reconnect to the infobase, but the Designer agent process was different.</li></ul></td><td>Synchronized Designer agent behavior with the standalone server behavior when performing the same operation.</td></tr></table><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae95-094d-11ef-963f-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.27" class="tag_0"><td><a name="82e0696d-11cd-11ef-963f-0050569f678a"></a>English name of the <span class="term">AdministrationWorkProcess.Enable</span><span class="term"> </span>object property. The former name is supported for compatibility purposes.
</td><td><ul><li><span class="term">Enable</span>.</li></ul></td><td><ul><li><span class="term">TurnedOn.</span></li></ul></td></tr><tr title="Версия 8.3.27" class="tag_0"><td><a name="e81bf9a1-12a7-11ef-963f-0050569f678a"></a>Name of the standard function for binary data storage management.</td><td><ul><li>Binary data storage management.</li></ul></td><td><ul><li>Binary data storages management.</li></ul></td></tr></table><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae96-094d-11ef-963f-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.27" class="tag_30 tag_31"><td><a name="fe63b7fd-7585-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile version of 1C:Enterprise now supports Android 15. The mobile version of 1C:Enterprise supports Android versions 5 - 15.</td><td>Previously the mobile 1C:Enterprise version supported Android versions 5 - 14.</td><td>Now the mobile 1C:Enterprise version supports the latest Android versions.</td></tr></table><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae98-094d-11ef-963f-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.27" class="tag_0"><a name="ee2557e7-9dcc-11f0-a153-0050569f678a"></a>The ImageMagick library is updated to version 7.1.2-3.</li><li title="Версия 8.3.27" class="tag_0"><a name="6c38388a-dbee-11f0-a153-0050569f678a"></a>The libpng library is updated to version 1.6.54.</li></ul><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae99-094d-11ef-963f-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.27" class="tag_0"><a name="c3f60114-c455-11ef-963f-0050569f678a"></a>You can use a formatted string in data composition system templates in the <span class="term">PriceList </span>report.<p>
</p></li><li title="Версия 8.3.27" class="tag_0"><a name="26d298ac-c456-11ef-963f-0050569f678a"></a>New example of using asynchronous creation of an add-in object (the <span class="interface">AddIn.Scanner.BarcodeReader</span> object type) when using the barcode scanner driver.<p>
</p></li></ul><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae9a-094d-11ef-963f-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.27" class="tag_3"><td><a name="fd28f856-c43a-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 3); return false;">WebSocket operations</a>.<br></td><td>New method to get the WebSocket connection state: <span class="term">WebSocketClient.GetConnectionState()</span>.<p>New ID: <span class="term">WebSocket</span>. It is used to describe the system object related to WebSocket in the event log, debugger, and so on.</p></td><td>You could find out the WebSocket connection state only after receiving the corresponding object. It was impossible to get the connection state from the WebSocket client.<p>It was impossible to identify actions with WebSockets that occurred in the event log, debugger, and so on.</p></td><td>Simplified check of WebSocket client connection state.<p>Simplified identification of objects related to WebSockets in the event log, debugger, and so on.</p></td></tr><tr title="Версия 8.3.27" class="tag_20"><td><a name="46f579f9-eabf-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>When using EDT, unlimited growth of metadata cache used by Designer and the thick client is excluded.</td><td>Previously, when using EDT, there was sometimes an unlimited growth of metadata cache used by Designer and the thick client. This led to an unexpected depletion of free space on the hard drive where metadata cache (user profile) was located.</td><td>Excluded unlimited growth of metadata cache. Significantly reduced probability of running out of free space on the hard drive where metadata cache was located due to the increase in the cache file size.</td></tr><tr title="Версия 8.3.27" class="tag_32"><td><a name="988e12b1-f5c0-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile 1C:Enterprise version 8.3.27 is now supported in the mobile application builder.</td><td>Mobile 1C:Enterprise version 8.3.27 was not supported in the mobile application builder.</td><td>Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.</td></tr><tr title="Версия 8.3.27" class="tag_29"><td><a name="56f1204e-03d9-11f0-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following Linux distribution packages are no longer supported:<ul><li>Alt Linux 8 SP.</li></ul></td><td>Previously, 1C:Enterprise supported the following Linux distribution packages:<ul><li>Alt Linux 8 SP.</li></ul></td><td>Outdated Linux distribution packages are no longer supported.</td></tr><tr title="Версия 8.3.27" class="tag_33"><td><a name="23c1b2a8-03f8-11f0-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>The documentation and Syntax Assistant now specify that picture sets (in ZIP archives) can be used in form item properties of the client application.</td><td>Previously, the documentation and Syntax Assistant did not indicate that picture sets (in ZIP archives) could be used in form item properties of the client application.</td><td>Updated platform documentation.</td></tr><tr title="Версия 8.3.27" class="tag_34"><td><a name="8cf2bc61-3087-11f0-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 34); return false;">PDF document operations</a>.<br></td><td>1C:Enterprise now supports the JBig2 format for displaying and printing PDF documents.</td><td>The JBig2 format was not supported when displaying and printing PDF documents.</td><td>Improved PDF format support.</td></tr><tr title="Версия 8.3.27" class="tag_29 tag_19"><td><a name="8518e960-30b1-11f0-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro 1С: 13.20, 13.21, 14.17, 14.18, 15.12, 15.13.</li><li>Postgres Pro Standard: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.</li><li>Postgres Pro Enterprise: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.</li><li>Postgres Pro CERT Standard: 14.17.1, 14.18.1, 15.12.1, 15.13.1.</li><li>Postgres Pro CERT Enterprise: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.</li></ul><p>DBMS version bitness: x86-64, E2k, ARM64.</p><p>The products are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These Postgres Pro DBMS versione were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.27" class="tag_29 tag_19"><td><a name="f0244548-30b1-11f0-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro 1С: 16.8, 16.9, 17.4, 17.5.</li><li>Postgres Pro Standard: 16.8.1, 16.9.1, 17.4.1, 17.5.1.</li><li>Postgres Pro Enterprise: 16.8.1, 16.9.1, 17.5.1.</li><li>Postgres Pro CERT Standard: 16.8.1, 16.9.1, 17.4.1, 17.5.1.</li><li>Postgres Pro CERT Enterprise: 16.8.1, 16.9.1, 17.5.1.</li></ul><p>DBMS version bitness: x86-64, E2k, ARM64.</p><p>The products are supported in 1C:Enterprise version 8.3.22 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These Postgres Pro DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.27" class="tag_19 tag_29"><td><a name="23e31cf0-3197-11f0-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Pangolin DBMS version 6.4.2. and 6.5.1.
Supported processors: x86-64.
Supported operating systems are defined by a DBMS vendor.</td><td>Previously, 1C:Enterprise did not support these Pangolin DBMS versions.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.27" class="tag_30 tag_31"><td><a name="c5545581-535e-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile version for Android now supports Google's new requirements for operations with images and video files. The appearance of the file selection dialog box has changed in terms of photo and video selection.<p>To enable support for the new requirements, rebuild the mobile application with a new mobile version and publish it.</p></td><td>The mobile version for Android did not support Google's new requirements for operations with images and video files.</td><td>Implemented support for Google's new requirements for operations with images and video files in the mobile version for Android.</td></tr><tr title="Версия 8.3.27" class="tag_35 tag_33"><td><a name="7eb41f5b-5727-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 35); return false;">System operation safety</a>.<br><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>The documentation now contains information that during the execution of some configuration object and subscription handlers, unsafe operation protection is disabled. After the handler is executed, unsafe operation protection is enabled again (if it was enabled before the handler was called).<p>To enable unsafe operation protection in event handlers manually, use the implemented <span class="term">SetUnsafeActionProtectionDisabled()</span> and <span class="term">GetUnsafeActionProtectionDisabled()</span> global context methods. The methods are not available in the extension.</p></td><td>The documentation did not contain information that unsafe operation protection is disabled in event handlers of object modules.<p>It was impossible to return unsafe operation protection if it was necessary in the event handler.</p></td><td>You can use unsafe operation protection when the platform disables this protection.</td></tr><tr title="Версия 8.3.27" class="tag_35"><td><a name="88f73137-5732-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 35); return false;">System operation safety</a>.<br></td><td>When you open a URL using an HTML document field, unsafe operation protection is active if enabled. To enable this mode, use the user property or the <span class="interface">conf.cfg </span>configuration file.<p>The positive answer to the system's question is recorded by user and infobase. The negative answer is not recorded, and the confirmation request is displayed the next time you try to open the URL.</p></td><td>When you opened a URL using an HTML document field, unsafe operation protection was not active.</td><td>Improved system security when using the HTML document field.</td></tr><tr title="Версия 8.3.27" class="tag_36"><td><a name="fc133da5-784e-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>If, when solving (by any algorithm) a system of equations or its part using the <span class="term">SystemOfLinearEquationsCalculation </span>object, the exact solution cannot be obtained with the specified accuracy (in the <span class="term">AdequateAccuracy </span>property) in the specified number of iterations (in the <span class="term">IterationCount </span>property), the solution that was found in the specified number of iterations is returned, but it may not correspond to the specified accuracy criterion.</td><td>If, when solving a system of equations or its part using the <span class="term">SystemOfLinearEquationsCalculation </span>object, the exact solution was not obtained with the specified accuracy (in the <span class="term">AdequateAccuracy </span>property) in the specified number of iterations (in the <span class="term">IterationCount </span>property), the solution of the system or its part was reset to zero.</td><td>If the exact solution of a system of linear equations cannot be obtained with the specified accuracy in the specified number of iterations, a solution that may not meet the specified accuracy criterion is returned.</td></tr><tr title="Версия 8.3.27" class="tag_19 tag_29"><td><a name="c9a6a6b3-7bf5-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Tantor:<ul><li>SE 1C DBMS versions 14.17.0, 15.12.0, 15.14.2, 15.15.0, 16.8.0, 16.10.2, 16.11.0, 17.5.0, 17.6.0, 17.7.0.</li><li>Certified 1C versions 15.12, 15.14.1, 16.8, 16.10.0, 16.11.0.</li></ul><p>Processor architectures supported by DBMS: x86-64.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously, 1C:Enterprise did not support these Tantor DBMS versions.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.27" class="tag_26"><td><a name="55a42b74-30c3-11f0-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Converting a spreadsheet document into a compact format will always be completed in an adequate time.</td><td>Converting a spreadsheet document into a compact format could lead to an emergency system shutdown.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.27" class="tag_15 tag_29"><td><a name="699034b2-dbe9-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>1C:Enterprise now supports Mos.OS Server for the Intel architecture.</td><td>This feature was not provided.</td><td>Extended list of supported operating systems.</td></tr><tr title="Версия 8.3.27" class="tag_19 tag_29"><td><a name="cf11d33a-dfe2-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports PostgreSQL DBMS version 18 (x86-64).</td><td>This PostgreSQL DBMS version was not supported.</td><td>Reduced number of certificate check errors when accessing Russian websites.</td></tr><tr title="Версия 8.3.27" class="tag_4"><td><a name="63ca4b62-01b1-11f1-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: improved audio transmission (including improved noise reduction and echo cancellation) when making video calls in the collaboration system. Improved stability of video calls.</td><td>The collaboration system had issues with sound in video calls.</td><td>Improved sound handling in the collaboration system.</td></tr><tr title="Версия 8.3.27" class="tag_4"><td><a name="f7d98575-0e55-11f1-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can now integrate the collaboration system with MAX instant messaging systems.</td><td>This feature was not provided.</td><td>Advanced features for collaboration system integration with instant messaging systems.</td></tr><tr title="Версия 8.3.27" class="tag_24 tag_10 tag_14"><td><a name="b9d09484-29bf-11f1-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 24); return false;">Infobase users</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>If the standard 1C email service is used for authentication operations (such as email authentication or password recovery), the ITS portal user credentials must be specified in the client application. In other words, anonymous sending of emails is no longer supported. The protocol of interaction between the platform and the standard email service is changed. When configuring a custom SMTP service for user authentication or password recovery via email, you can now set up authentication on the mail server.<p>New properties for the <span class="term">GetPasswordRecoverySettings </span>and <span class="term">GetEmailAuthenticationSettings </span>objects: <span class="term">SMTPSecureAuthenticationOnly</span>, <span class="term">TokenAuthentication</span>, <span class="term">AccessToken</span>, and <span class="term">Sender</span>.</p></td><td>If the standard 1C email service was used for authentication operations (such as email authentication or password recovery), anonymous access to the mail server was used to send emails.</td><td>Improved security of sending emails when using the standard 1C email sending service.</td></tr><tr title="Версия 8.3.27" class="tag_37"><td><a name="b8d880f1-31ae-11f1-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>New feature: an intermediate certificate of the Federal Treasury of the Russian Federation is added to the <span class="interface">cacert.pem </span>and <span class="interface">cacertnx.pem</span> files.</td><td>The intermediate certificate of the Federal Treasury of the Russian Federation was missing in the <span class="interface">cacert.pem </span>and <span class="interface">cacertnx.pem </span>files.</td><td>Reduced number of connection errors with the Unified Information System in procurement.</td></tr></table><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="807fae9b-094d-11ef-963f-0050569f678a">Transition from the previous version to the version 8.3.27</a></h2><ul><li title="Версия 8.3.27" class="tag_0"><a name="807fae9c-094d-11ef-963f-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.27.
</li><li title="Версия 8.3.27" class="tag_0"><a name="807fae9d-094d-11ef-963f-0050569f678a"></a>Some features that are added in version 8.3.27 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li></ul><p><a href="#807fae8f-094d-11ef-963f-0050569f678a"><small>Table of contents</small></a></p><h1><a name="9959bdf4-6c0c-11ee-963f-0050569f678a">Version 8.3.26</a></h1><p title="Версия 8.3.26" class="tag_0"><a name="9959be03-6c0c-11ee-963f-0050569f678a"></a>Version 8.3.26 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.26" class="tag_0"><a name="c5ab4893-f256-11ee-963f-0050569f678a"></a>Data accelerator graduated out of beta.<p>Data accelerator requires CORP license. </p></p><hr></hr><ul><li><a href="#9959bdf5-6c0c-11ee-963f-0050569f678a">New functionality and changes</a></li><li><a href="#9959bdf6-6c0c-11ee-963f-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#9959bdf7-6c0c-11ee-963f-0050569f678a">Optimization</a></li><li><a href="#9959bdf8-6c0c-11ee-963f-0050569f678a">Changes that affect system behavior</a></li><li><a href="#9959bdf9-6c0c-11ee-963f-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#9959bdfb-6c0c-11ee-963f-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#9959bdfe-6c0c-11ee-963f-0050569f678a">Demo configuration changes</a></li><li><a href="#9959bdff-6c0c-11ee-963f-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#9959be00-6c0c-11ee-963f-0050569f678a">Transition from the previous version to the version 8.3.26</a></li></ul><h2><a name="9959bdf5-6c0c-11ee-963f-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.26" class="compat tag_2 tag_1"><td><a name="d9552e35-6c0c-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>New value for the<span class="interface"> Compatibility mode </span>configuration property: <span class="interface">Version 8.3.25</span>.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.24 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.25 or earlier can now run on version 8.3.26 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.26 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.25 after the migration to version 8.3.26. Even if you have disabled the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.26" class="tag_20"><td><a name="edd0b21f-6cb9-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Now you can notify the client application from the server without using the collaboration system.<p>New global context property: <span class="term">ClientNotifications</span>.</p><p>New property: <span class="term">BackgroundJob.ParentSessionNumber</span>.</p><p>New client notification service for the cluster manager.</p><p>New parameter for the standalone server: <span class="term">--clnt-notif-data</span>.</p><p>This feature is available only for a PROF license.</p></td><td>Previously, you could notify the client application from the server either using the collaboration system or by constantly polling the server by the client application to get the necessary information.</td><td>You can notify the client application from the server without using the collaboration system or constantly polling the server by the client application, which reduces system performance.</td></tr><tr title="Версия 8.3.26" class="tag_38"><td><a name="66a85847-6e7f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Now you can create native document journals in extensions. Such journals can include any system documents.</td><td>This feature was not provided.</td><td>Advanced configuration extension features.</td></tr><tr title="Версия 8.3.26" class="tag_23 tag_20"><td><a name="dfd5127a-6f2f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Now you can get datasets from the infobase filtered by reference list.<p>New method for the <span class="term">CatalogManager</span>, <span class="term">DocumentManager</span>, <span class="term">ChartOfCharacteristicTypesManager</span>, <span class="term">ChartOfAccountsManager</span>, <span class="term">ChartOfCalculationTypesManager</span>, <span class="term">ExchangePlanManager</span>, <span class="term">BusinessProcessManager, </span>and <span class="term">TaskManager</span> objects: <span class="term">SelectByRefs()</span>.</p></td><td>This feature was not provided.</td><td>Simplified batch processing of an object list when the list is known in advance. However, not all objects may be changed.</td></tr><tr title="Версия 8.3.26" class="tag_16"><td><a name="913edac5-6f33-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>For a record set of an independent information register, you can now update information register records that have the same key fields as the records present in the record set.<p>New system enumeration value: <span class="term">ReplacementMode.Update</span>.</p></td><td>This feature was not provided.</td><td>Simplified and improved mass update of records in the information register. For example, it is required to fill a new register resource or attribute with a fixed value after adding this resource.</td></tr><tr title="Версия 8.3.26" class="tag_39"><td><a name="9908eff6-7188-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>Implemented the following event log events:<ul><li><span class="interface">Users. Changing access rights</span> (<span class="term">_$User$_.PermissionChange</span>). Generated when user access rights are changed.</li><li><span class="interface">Infobase. Changing role</span> (<span class="term">_$InfoBase$_.RoleUpdate</span>). Generated when the application role changes. A separate event log event is generated for each role.</li><li><span class="interface">Infobase. Changing session start lock</span> (<span class="term">_$InfoBase$_.SessionLockChange</span>). Generated if the infobase session start lock is set.</li><li><span class="interface">Infobase. Error changing session start lock</span> (<span class="term">_$InfoBase$_.SessionLockChangeError</span>). Generated if an error occurs when setting the infobase session start lock.</li><li><span class="interface">Infobase. Modifying regional settings </span>(<span class="term">_$InfoBase$_.RegionalSettingsChange</span>). Generated if the regional infobase settings are changed.</li><li><span class="interface">Infobase. Error changing regional settings </span>(<span class="term">_$InfoBase$_.RegionalSettingsChangeError</span>). Generated if an error occurs while changing the regional infobase settings.</li><li><span class="interface">Infobase. Error deleting infobase data </span>(<span class="term">_$InfoBase$_.EraseDataError</span>). Generated when an error occurs while deleting infobase or data area data.</li><li><span class="interface">Infobase. Error changing configuration</span> (<span class="term">_$InfoBase$_.ConfigUpdateError</span>). Generated if an error occurs while saving the configuration.</li><li><span class="interface">Infobase. Error during background database configuration update</span> (<span class="term">_$InfoBase$_.DBConfigBackgroundUpdateError</span>). Generated if an error occurs during a background database configuration update.</li><li><span class="interface">Infobase. Adding database configuration extension</span> (<span class="term">_$InfoBase$_.DBConfigExtensionInsert</span>). Generated when adding an infobase configuration extension.</li><li><span class="interface">Infobase. Error adding database configuration extension</span> (<span class="term">_$InfoBase$_.DBConfigExtensionInsertError</span>). Generated when an error occurs while adding an infobase configuration extension.</li><li><span class="interface">Infobase. Deleting database configuration extension</span> (<span class="term">_$InfoBase$_.DBConfigExtensionDelete</span>). Generated when an infobase configuration extension is deleted.</li><li><span class="interface">Infobase. Error deleting database configuration extension </span>(<span class="term">_$InfoBase$_.DBConfigExtensionDeleteError</span>). Generated when an error occurs while deleting the infobase configuration extension.</li><li><span class="interface">Infobase. Changing exclusive access mode to current area</span> (<span class="term">_$InfoBase$_.ExclusiveModeChange</span>). Generated when the exclusive access mode to the infobase or data area is changed.</li><li><span class="interface">Infobase. Error changing exclusive access mode to current area </span>(<span class="term">_$InfoBase$_.ExclusiveModeChangeError</span>). Generated when an error occurs while changing the exclusive access mode to the infobase or data area.</li><li><span class="interface">Infobase. Changing administrative parameters</span> (<span class="term">_$InfoBase$_.AdministrationParametersChange</span>). Generated when the infobase parameters are changed in the server cluster.</li><li><span class="interface">Infobase. Changing security profile</span> (<span class="term">_$InfoBase$_.SecurityProfileChange</span>). Generated for each infobase whose settings contain a security profile to change.</li><li><span class="interface">Session. Changing current area</span> (<span class="term">_$Session$_.DataZoneChange</span>). Occurs when the current data area is changed.</li><li><span class="interface">Session. Error changing current area</span> (<span class="term">_$Session$_.DataZoneChangeError</span>). Occurs when an error occurs while changing the current data area.</li><li><span class="interface">Session. Connecting external data processor</span> (<span class="term">_$Session$_.ExternalDataProcessorConnect</span>). Occurs when connecting to an external data processor session.</li><li><span class="interface">Session. Error connecting external data processor </span>(<span class="term">_$Session$_.ExternalDataProcessorConnectError</span>). Occurs when an error occurs when connecting to an external data processor session.</li><li><span class="interface">Session. Connecting external report</span> (<span class="term">_$Session$_.ExternalReportConnect</span>). Occurs when connecting to an external report session.</li><li><span class="interface">Session. Error connecting external report </span>(<span class="term">_$Session$_.ExternalReportConnectError</span>). Occurs when an error occurs when connecting to an external report session.</li><li><span class="interface">Session. Attaching add-in</span> (<span class="term">_$Session$_.AddInAttach</span>). Occurs when connecting to an add-in session.</li><li><span class="interface">Session. Error attaching add-in</span> (<span class="term">_$Session$_.AddInAttachError</span>). Occurs when an error occurs when connecting to an add-in session.
There is now more information for event log events:</li><li><span class="term">_$InfoBase$_.ConfigUpdate</span>.</li><li><span class="term">_$InfoBase$_.DBConfigUpdate</span>.</li><li><span class="term">_$InfoBase$_.DBConfigUpdateError</span>.</li><li><span class="term">_$InfoBase$_.DBConfigExtensionUpdate</span>.</li><li><span class="term">_$InfoBase$_.DBConfigExtensionUpdateError</span>.</li></ul></td><td>These features were not provided.</td><td>Extended list of logged actions to facilitate system administration.</td></tr><tr title="Версия 8.3.26" class="tag_39"><td><a name="09180d67-718e-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>Now you can manage writing of audit events of access rights to the event log. By default, writing of audit events is disabled. Audit events of access rights include:<ul><li><span class="term">_$InfoBase$_.RoleUpdate</span></li><li><span class="term">_$User$_.PermissionChange</span></li><li><span class="term">_$InfoBase$_.AdministrationParametersChange</span></li><li><span class="term">_$InfoBase$_.SecurityProfileChange.</span></li></ul><p>New parameter for the <span class="interface">conf.cfg </span>file: <span class="term">EnableAccessRightAuditEventsWrite</span>.</p><p>New checkbox for dialog boxes for editing cluster parameters in the cluster management console and the standard <span class="interface">Server management</span> data processor: <span class="interface">Allow writing audit events of access rights</span>.</p><p>For the <span class="interface">rac </span><span class="interface">cluster list </span>and<span class="interface"> rac cluster info </span>commands, the <span class="term">allow-access-right-audit-events-recording</span> parameter is now displayed. New parameter for the <span class="interface">rac cluster insert </span>and <span class="interface">rac cluster update </span>commands: <span class="term">--allow-access-right-audit-events-recording</span>.</p><p>New property: <span class="term">AdministrationCluster.EnableAccessRightAuditEventsWrite</span>. New property:<span class="term"> IClusterInfo.AllowAccessRightAuditEventsRecording</span>. New method: <span class="term">IServerAgentConnection.SetAllowAccessRightAuditEventsRecording()</span>.</p><p>New methods in the Java administration server interface for the <span class="term">IClusterInfo </span>object: <span class="term">isAllowAccessRightAuditEventsRecording()</span> and <span class="term">setAllowAccessRightAuditEventsRecording()</span>.</p><p>New parameter for the command line of the standalone server startup (<span class="interface">ibsrv</span>): <span class="term">--access-right-audit-events-recording</span>. New parameter for the configuration file of the standalone server for the <span class="term">server </span>section:<span class="term"> access-right-audit-events-recording</span>.</p><p>The "<span class="interface">Allow writing audit events of access rights</span>" feature requires a CORP license.</p></td><td>These features were not provided.</td><td>Now you can enable audit events of access rights when necessary.</td></tr><tr title="Версия 8.3.26" class="tag_40"><td><a name="48166e39-71a8-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 40); return false;">Settings storage</a>.<br></td><td>New default settings. The default setting is valid for all users who do not have the custom setting. The custom setting is prioritized. To save and delete the default settings, the Data administration right is required. Any infobase user can select and use the default setting.<p>New methods for the <span class="term">StandardSettingsStorageManager </span>object: <span class="term">LoadDefaultSetting()</span>, <span class="term">SaveDefaultSetting()</span>, <span class="term">DeleteDefaultSetting()</span>, and <span class="term">SelectDefaultSettings()</span>.</p><p>The standard 1C:Enterprise interface does not allow performing any actions with the default settings. To perform such actions, develop an appropriate dialog box.</p><p>It is recommended that application developers use the default settings, instead of copying settings to new users in bulk.</p></td><td>This feature was not provided.<p>Previously, to set previously made settings to a new user, you needed to copy these settings from the settings of another user.</p></td><td>Simplified the administrator work on the initial customization of the application to the needs of users (including those who are not yet created in the infobase). You no longer need to copy settings to all (or only new) infobase users if it is necessary to change any default settings for all users.</td></tr><tr title="Версия 8.3.26" class="tag_10"><td><a name="21e902e6-724b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can check user passwords for compromise. You can check passwords using the standard 1C:Enterprise platform list, your own list of invalid passwords, as well as specify the address of an Internet password check service. Now you can specify that it is necessary to check passwords in additional authentication settings, infobase settings, and user password policy.<p>New features for the <span class="term">AdditionalAuthenticationSettings </span>objects:</p><p>The <span class="term">PasswordCompromiseCheck </span>property.
The <span class="term">SetPasswordCompromiseCheckSettings()</span> and <span class="term">GetPasswordCompromiseCheckSettings()</span> methods.
New global context methods: <span class="term">SetUserPasswordCompromiseCheck()</span>, <span class="term">GetUserPasswordCompromiseCheck()</span>, </p><p><span class="term">SetActionOnUserPasswordRequirementsViolationOnAuthentication</span><span class="term">()</span>, <span class="term">GetActionOnUserPasswordRequirementsViolationOnAuthentication(</span><span class="term">)</span>, and <span class="term">CheckPasswordCompromise()</span>.</p><p>New properties for the <span class="term">UserPasswordPolicy </span>object: <span class="term">PasswordCompromiseCheck </span>and <span class="term">ActionOnPasswordRequirementsViolationOnAuthentication</span>.</p><p>New system enumeration property: <span class="term">PasswordPolicyComplianceCheckResult</span><span class="term">.DoesNotSatisfyCompromiseCheckRequirements</span>.</p><p>New object property: <span class="term">InfobaseUser.PasswordDoesNotSatisfyRequirements</span>.</p><p>Implemented the following event log events:</p><ul><li><span class="interface">Session. Password violates authentication requirements </span>(<span class="term">_$Session$_.PasswordRequirementsViolationOnAuthentication</span>). Generated during authentication if the user password violates the requirements.</li><li><span class="interface">Session. Error of service for password compromise check upon authentication</span> (<span class="term">_$Session$_.PasswordCompromiseCheckServiceErrorOnAuthentication</span>). Generated during authentication if an error using the service for password compromise check occurs.</li><li><span class="interface">Infobase. Error of service for password compromise check</span> (<span class="term">_$InfoBase$_.PasswordCompromiseCheckServiceError</span>). Generated when an error occurs when accessing the service for password compromise check.</li><li><span class="interface">Infobase. Changing list of password compromise check</span> (<span class="term">_$InfoBase$_.PasswordCompromiseCheckListUpdate</span>). Generated when the password compromise check list is changed.</li><li><span class="interface">Infobase. Error changing list of password compromise check</span> (<span class="term">_$InfoBase$_.PasswordCompromiseCheckListUpdateError</span>). Generated when an error occurs when changing the password compromise check list.
There is now more information for event log events:</li><li><span class="term">_$User$_.New</span></li><li><span class="term">_$User$_.NewError</span></li><li><span class="term">_$User$_.Update</span></li><li><span class="term">_$User$_.UpdateError</span></li><li><span class="term">_$InfoBase$_.ParametersUpdate</span></li><li><span class="term">_$InfoBase$_.ParametersUpdateError</span></li><li><span class="term">_$InfoBase$_.UserPasswordPolicyNew</span></li><li><span class="term">_$InfoBase$_.UserPasswordPolicyUpdate</span></li><li><span class="term">_$Session$_.PasswordChangeError</span></li><li><span class="term">_$InfoBase$_.AdditionalAuthenticationSettingsUpdate</span></li><li><span class="term">_$InfoBase$_.AdditionalAuthenticationSettingsUpdateError</span>.</li></ul></td><td>This feature was not provided.</td><td>Now you can lock specifying "well-known" passwords and passwords that cannot be assigned due to corporate restrictions.</td></tr><tr title="Версия 8.3.26" class="tag_38"><td><a name="e7ebb769-73fe-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Now you can edit the <span class="term">Package </span>and <span class="term">Namespace </span>properties of an adopted XDTO package, as well as the <span class="term">XDTOPackages </span>property of an adopted web service in the configuration extension.<p>For the XDTO package, the specified properties are replaced with the same properties from the extension. For web services, the list of packages in the resulting configuration is supplemented with the value from the extension.</p></td><td>This feature was not provided.</td><td>Advanced configuration extension features.</td></tr><tr title="Версия 8.3.26" class="tag_7"><td><a name="ba031a0d-748f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>When restoring an infobase from a DT file, data synchronization with database copies that are configured in the original infobase is locked (except for the Data accelerator copy). The administrator can allow using copies using the standard <span class="interface">Database copy management </span><span class="interface">data processor</span> in the restored infobase. The standard data processor also displays the owner of each copy configured in the infobase (except for the Data accelerator copy).<p>New methods for the database copy manager: <span class="term">SetCopyDatabaseUseByThisCopy()</span>.</p><p>New method for the database copy manager: <span class="term">GetInformationOnCopyDatabaseUse()</span>.</p><p>The <span class="term">Update()</span> method of the database copy manager generates an exception if the database to update is used by another infobase.</p><p>It is recommended to analyze the tools for updating database copies in applications and implement (if necessary) informing the administrator about issues that arise when updating database copies.</p></td><td>This feature was not provided.<p>Previously, after restoring the infobase from the DT file and starting the application, all configured copies began to update (if the DBMS on which the copies were located were available to the restored infobase). This could lead to violation of information integrity in the copies (compared with the original infobase).</p></td><td>When you create an infobase copy (for example, for testing), data from the infobase copy will not go to the database copies that the original infobase uses. So, data in the copies will be protected from updating with incorrect information.</td></tr><tr title="Версия 8.3.26" class="tag_19"><td><a name="3023bdc3-74ac-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Now you can create arbitrary indexes for the following configuration objects: catalogs, documents, document journals, information registers, accumulation registers, accounting registers, calculation registers, business processes, tasks, charts of characteristic types, charts of accounts, exchange plans, and sequences. When creating an index, configuration fields and attributes are specified, not the physical database fields. The platform performs the required conversion automatically while saving the configuration. You cannot create an index that will contain more than 16 physical database fields.<p>The built-in system indexes are not editable and are not shown in Designer tools. Indexes are added and deleted upon infobase restructuring.</p><p>New property for configuration objects that support creation of additional indexes: <span class="term">AdditionalIndexes</span>.</p><p>The <span class="term">GetDBStorageStructureInfo()</span> method returns information about additional indexes if they are specified in the configuration in the <span class="term">Indexes </span>column. New column in the value table that describes table index fields (<span class="term">Indexes.Fields</span>): <span class="term">FieldType</span>.This column describes the index field type.</p><p>You cannot create or change additional indexes in the configuration extension.</p><p>Be careful when creating additional indexes. Remember that additional indexes can lead not only to positive consequences (faster data acquisition), but also to negative ones: slowing down writing to the infobase, increasing the disk space occupied by database files, and slowing down scheduled database operations.</p><p>This features requires a CORP license.</p></td><td>This feature was not provided.<p>Previously, you could create additional indexes only for the DBMS.</p></td><td>If necessary, you can create additional database indexes that can speed up the execution of specialized application queries.</td></tr><tr title="Версия 8.3.26" class="tag_14"><td><a name="36303eb5-77ce-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Now users can authenticate using a QR code.<p>New checkbox in the user parameters: <span class="interface">QR code authentication</span>. New property: <span class="term">InfobaseUser.QRCodeAuthentication</span>.</p><p>New item for the <span class="interface">default.vrd</span> file: <span class="term">&lt;mobileApps&gt;</span>.</p><p>There is now more information for event log events:</p><ul><li><span class="term">_$User$_.New</span>.</li><li><span class="term">_$User$_.Update</span>.</li><li><span class="term">_$Session$_.Authentication</span>.</li><li><span class="term">_$Session$_.AuthenticationError</span>.</li><li><span class="term">_$Session$_.AuthenticationFirstFactor</span>.</li></ul></td><td>This feature was not provided.</td><td>If you are authenticated in any infobase using a mobile application, you may not enter a password to get access to the same database from another device. Just scan the QR code displayed by the authentication form from a mobile device.</td></tr></table><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9959bdf6-6c0c-11ee-963f-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.26" class="tag_4"><td><a name="debe8985-7336-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can select the window (application) to display to subscribers during screen sharing in a thin client or during a collaboration system video call.<p>You can set up display mode of collaboration system notifications during screen sharing: Show entire message, Show only sender, and Hide messages.</p></td><td>Previously, you could only select a monitor (if there were several monitors) to display to subscribers during screen sharing in a thin client or during a collaboration system video call. You could not select a window (application) to display.<p>During screen sharing, video call subscribers could see all collaboration system notifications.</p></td><td>The load on the communication channel during screen sharing can be reduced as you can select to display not the entire monitor, but only the selected application window, which often does not occupy the entire selected monitor/desktop.<p>During a video call, you can manage display of collaboration system notifications. This will positively affect the video call privacy.</p></td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="d67ea705-733b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The video and image quality of the displayed screen in case of network issues is enhanced. If the channel bandwidth deteriorates, the image quality must be proportionally reduced. Screen sharing must not be interrupted.</td><td>Previously, if the communication channel quality deteriorated, the video stream could be interrupted (both regular video and screen sharing) or freeze.</td><td>Enhanced video quality (including screen sharing) in case of communication channel issues.</td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="1a75e289-73e8-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The following features are implemented when using collaboration system video calls in the thin client:<ul><li>You can enable automatic adjustment of the microphone gain level. New checkbox in the collaboration system settings: <span class="interface">Automatic microphone volume control</span>. The setting is disabled by default. The setting is stored on the client computer by microphones.</li><li>You can select noise suppression mode: <span class="interface">Quiet background noise</span> (default), Loud speech<span class="interface">, noises</span>, and <span class="interface">Noise suppression is off</span>. The setting is stored on the client computer by microphones.</li></ul></td><td>Previously, you could not control the microphone gain level and noise suppression mode when using video calls in the collaboration system.</td><td>You can enable the mode when the collaboration system will automatically amplify the quiet and dampen the too loud voice of the subscriber. You can also manage noise suppression and echo cancellation systems.</td></tr><tr title="Версия 8.3.26" class="tag_12"><td><a name="6da1d625-772c-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>The setup form is redesigned for the standard Data change history data processor:<ul><li>New feature: search fields by configuration objects, tables, and fields.</li><li>The system now displays that a specific setting is performed in 1C:Enterprise mode or in Designer.</li><li>You can set standard settings for the configuration object(s) from metadata.</li><li>You can clear the data history.</li><li>You can display the difference between the current history settings and the settings made in the metadata.</li></ul></td><td>These features were not provided.</td><td>Advanced settings of data change history.</td></tr><tr title="Версия 8.3.26" class="tag_10 tag_14"><td><a name="9df1fbb9-77cf-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>New feature: improved client application update. If the required version is not available on the client computer, the required client application starts downloading immediately. In the form that displays the download process, you can cancel downloading or sign in to the infobase using a web client if the database is accessed over HTTP(s).</td><td>If the required version of the client application was missing on the client computer when trying to sign in to the infobase, the system first prompted to choose what to do next: update the client application or sign in to the infobase using the web client. If you selected to update the client application, the client application downloading and installing started.</td><td>Faster client application update.</td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="b5adef94-ea97-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>When you make video calls in thin and web clients, the load on the CPU and network channel of the client computer is reduced. The load on the CPU and network no longer depends on the number of participants in the call.<p>For that, the administrator must do the following:</p><ul><li>Update the collaboration system servers to version 26 or later.</li><li>Update 1C:Enterprise to version 8.3.26 or later.</li><li>Update the Janus video server to version 1.0.4 or later.</li></ul></td><td>Previously, when you made video calls in thin and web clients, there was an increased load on the CPU and network channel of the client computer. The larger the number of participants in the video call, the higher was the load on the CPU and network.</td><td>Reduced system load when making group calls. Now you can increase the number of users who can simultaneously participate in a video call.</td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="6caf2f60-f1af-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The video call interface on the external user website and the website chat is now similar to the same interface in client 1C:Enterprise applications.</td><td>The video call interface on the external user website and the website chat was different from the same interface in client 1C:Enterprise applications.</td><td>Extended website capabilities for external users.</td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="1f264980-f1b2-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The following changes are made to the interface for enabling screen sharing of the collaboration system video call in the thin client:<ul><li>The order of monitors is changed to the system one (corresponds to the horizontal placement of monitors).</li><li>When selecting a screen or application to share, the <span class="interface">OK </span>and <span class="interface">Cancel </span>buttons are removed. The demonstration starts immediately after you select the required object.</li><li>The screen or window choice form is reduced in vertical dimensions to fit on low-resolution screens.</li></ul></td><td>Previously, the interface for enabling screen sharing of the collaboration system video call in the thin client had the following behavior:<ul><li>The monitors were in alphabetical order.</li><li>To select a screen or window to share, it was necessary to select the object to share and click <span class="interface">OK</span>.</li><li>The screen or window choice form did not fit vertically on low-resolution screens.</li></ul></td><td>Improved interface for selecting a monitor or window to share in the thin client.</td></tr><tr title="Версия 8.3.26" class="tag_17"><td><a name="8a58d3f6-f1b5-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>Now you can track RAM consumption by full-text search. New item for the <span class="interface">logcfg.xml</span> file: <span class="term">&lt;systemmemoryprofile&gt;</span>. Information on RAM consumption is displayed in the <span class="term">&lt;system&gt;</span> events.<p>Tracking settings and descriptions of generated events are not documented. This feature is designed for 1C Company specialists.</p></td><td>Previously, you could not track RAM consumption by full-text search.</td><td>If there are issues with RAM consumption by full-text search, 1C specialists can provide the ready-made <span class="interface">logcfg.xml</span> file, and receive technological log files to analyze the situation and solve the arisen issues.</td></tr><tr title="Версия 8.3.26" class="tag_28 tag_14"><td><a name="8ff1131e-3231-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Users with operating systems earlier than Windows 7 get notified that operating systems are not supported in version 8.3.27 and the operating system update is recommended.<p>The warning is shown once a month for a unique user combination, an infobase, and a client/web browser kind (if the web client is used).</p></td><td>The warning about supporting obsolete versions of the Windows operating system was not shown.</td><td>A user gets notified that the operating system in use cannot open the following version of the 1C:Enterprise.</td></tr></table><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9959bdf7-6c0c-11ee-963f-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.26" class="tag_6"><td><a name="2d677a4b-6e85-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New feature: optimized use of processor, RAM, and session data by a 1C:Enterprise server cluster.</td><td>Previously, the resources of the computer running the 1C:Enterprise server cluster were not used effectively enough.</td><td>Improved performance and scalability of the 1C:Enterprise server cluster.</td></tr><tr title="Версия 8.3.26" class="tag_20"><td><a name="62f8744b-6f4c-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New feature: optimized check for circular references when the corresponding mode is enabled.</td><td>Previously, the check for circular references with the corresponding mode enabled took more time.</td><td>Reduced overheads introduced by the circular reference check. This will reduce the time required to analyze a problematic operation.</td></tr><tr title="Версия 8.3.26" class="tag_20"><td><a name="ef41ac9d-716c-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New feature: optimized the first Designer startup after loading the configuration.</td><td>After loading the configuration, the first Designer startup took a long time.</td><td>Faster first Designer startup after loading the configuration.</td></tr><tr title="Версия 8.3.26" class="tag_20"><td><a name="19fed963-74c2-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New feature: reduced time for restarting the client application from Designer.</td><td>Restarting the client application from Designer took a long time.</td><td>Reduced time for restarting the client application from Designer.</td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="42e208b7-796b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New features for the collaboration system:<ul><li>Search through the list of conversations is optimized.</li><li>When changing the list of conversation participants (the <span class="term">CollaborationSystemConversation.Participants</span> property), only changes are written.</li><li>The request from the 1C:Enterprise server to the collaboration system server is executed every 45 seconds. If the action was not performed during this time, an exception is thrown.</li></ul></td><td>Previously, for the collaboration system:<ul><li>Search through the list of conversations took more time.</li><li>When the list of conversation participants was changed (the <span class="term">CollaborationSystemConversation.Participants</span> property), the entire list was written.</li><li>The request from the 1C:Enterprise server to the collaboration system server was executed without timeout. This could cause the 1C:Enterprise server freezes.</li></ul></td><td>Improved performance of the collaboration system server.</td></tr><tr title="Версия 8.3.26" class="tag_21"><td><a name="f671f8ea-eaab-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>When using full-text search on large infobases, RAM consumption is now reduced.<p>For that, re-index the full-text search index.</p><p>1C:Enterprise platform version 8.3.25 and earlier will clear the index if it was built by version 8.3.26.</p></td><td>Previously, full-text search on large infobases required a large amount of RAM.</td><td>Full-text search requires fewer resources for operation.</td></tr></table><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9959bdf8-6c0c-11ee-963f-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.26" class="tag_40"><td><a name="f6912b4c-6c1b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 40); return false;">Settings storage</a>.<br></td><td>Now you can get access to standard settings storages even if custom settings storages are set.<p>New global context methods: </p><p><span class="term">GetStandardReportsVariantsStorage()</span>, <span class="term">GetStandardURLExternalDataStorage()</span>, <span class="term">GetStandardFormDataSettingsStorage()</span>, <span class="term">GetStandardCommonSettingsStorage()</span>, <span class="term">GetStandardDynamicListsUserSettingsStorage()</span>, and <span class="term">GetStandardReportsUserSettingsStorage()</span>. The methods return values of the <span class="term">StandardSettingsStorageManager </span>type.</p></td><td>Previously, if custom settings storages were set in the application, it was impossible to access the corresponding standard storage.</td><td>You can transfer settings from the standard storage to the custom one when updating the configuration if the new application version contains a custom settings storage that replaces the standard storage.</td></tr><tr title="Версия 8.3.26" class="tag_6 tag_10"><td><a name="1520f31f-6cd9-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can specify alternative data directories for some server cluster services. When you specify an alternative directory, data transfer is not performed automatically. You need to transfer data manually. The structure of data directories does not change during transfer.<p>You can set up directory transfer in the cluster console and in the standard<span class="interface"> Server management </span>data processor.</p><p>New methods for the <span class="term">AdministrationWorkServer </span>object: <span class="term">CreateServiceSetting()</span>, <span class="term">GetServiceSetting()</span>, <span class="term">GetServiceSettings()</span>, and <span class="term">GetServiceDataDirectoriesForTransfer()</span>.</p><p>The <span class="term">AdministrationWorkServer.SpeechToTextModelDirectory</span> property is deprecated.</p><p>New methods for the <span class="term">IServerAgentConnection</span> COM connector object: <span class="term">CreateServiceSetting()</span>, <span class="term">GetServiceSettings()</span>, <span class="term">RegServiceSetting()</span>, <span class="term">DeleteServiceSetting()</span>, <span class="term">GetServiceDataDirsForTransfer()</span>, <span class="term">GetServiceSettingByID()</span>, <span class="term">GetServiceSettingByParams()</span>, <span class="term">GetSettingActive()</span>, and <span class="term">ApplyServiceSettings()</span>.</p><p>The <span class="term">IWorkingServerInfo.SpeechToTextModelDirectory</span> property is deleted.</p><p>New methods for the <span class="term">IAgentAdminConnection </span>Java interface object: <span class="term">createServiceSetting()</span>, <span class="term">getServiceSettings()</span>, <span class="term">regServiceSetting()</span>, <span class="term">deleteServiceSetting()</span>, <span class="term">getServiceDataDirsForTransfer()</span>, <span class="term">getServiceSettingByID()</span>, <span class="term">getServiceSettingByParams()</span>, <span class="term">getSettingActive()</span>, and <span class="term">applyServiceSettings()</span>.</p><p>The <span class="term">IAgentAdminConnection.SpeechToTextModelDirectory</span> property is deleted.</p><p>New mode for the <span class="interface">rac</span> utility: <span class="term">service-setting</span>. The <span class="term">--speech-to-text-model-directory </span>parameter is deleted for the <span class="term">insert </span>and <span class="term">update </span>commands of the server mode.</p><p>Specifying alternative data directories for some server cluster services requires a CORP license.</p></td><td>This feature was not provided.<p>Previously, you could transfer directories only using the operating system used. This was not obvious to the user.</p></td><td>You can place cluster data on different disk drives to improve overall system performance.</td></tr><tr title="Версия 8.3.26" class="tag_13"><td><a name="5ae9aa7e-6d7f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>You can specify configuration objects whose data can be placed in the binary data storage. You can specify objects both in Designer and during execution (from 1C:Enterprise language or using a standard function).<p>New methods for the binary data storage manager: <span class="term">SetStoredDataContent()</span>, <span class="term">GetStoredDataContent()</span>, <span class="term">SetUsingAsStorageByDefault()</span>, and <span class="term">GetUsingAsStorageByDefault()</span>.</p><p>New properties for the manager of the external binary data storage: <span class="term">StoredDataContent </span>and <span class="term">StorageByDefault</span>.</p><p>New properties for attributes and resources of the <span class="term">ValueStorage </span>type configuration objects: <span class="term">BinaryDataStorageLocationUse </span>and <span class="term">BinaryDataStorageLocationUseField</span>.</p><p>The standard <span class="interface">Binary data storage management </span>data processor is improved.</p></td><td>This feature was not provided.<p>There was only a limit on the minimum amount of binary data that got into the external storage. It was impossible to limit the configuration objects whose data could enter the binary data storage.</p></td><td>You can manage writing data to the binary data storage not only by configuration object attributes, but also by specific data that is written to the infobase.</td></tr><tr title="Версия 8.3.26" class="tag_41"><td><a name="2187b2ed-6db4-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>You can unpack archives of the following formats: GZIP, RAR, 7-ZIP, XZ, and TAR. You cannot pack into these formats.<p>New objects: <span class="term">ArchiveFileReader </span>and <span class="term">ArchiveFileWriter</span>.</p><p>New property: <span class="term">ErrorCategory.UnsupportedFormat</span>.</p><p>The <span class="term">ZipFileReader</span>, <span class="term">ZipFileWriter</span>, and related objects are deprecated.</p><p>
</p></td><td>This feature was not provided.</td><td>You can get data in archives that are packed not only in ZIP file format.</td></tr><tr title="Версия 8.3.26" class="tag_6"><td><a name="38d5ce0d-6f19-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>You can change the parameters of the disconnection tracking system without restarting the cluster processes. This feature is implemented for all administrative tools: cluster console, COM connection, Java administration interface, and administration server.<p>New properties for the <span class="term">AdministrationCluster </span>object: <span class="term">PingPeriod </span>and <span class="term">PingTimeout</span>. New properties for the <span class="term">IClusterInfo </span>object: </p><p><span class="term">PingPeriod </span>and <span class="term">PingTimeout</span>.</p><p>You can edit the <span class="interface">Ping timeout </span>and the <span class="interface">Ping period </span>parameters in the form for editing cluster parameters in the cluster console and the standard <span class="interface">Server management </span>function.</p><p>New parameters for the <span class="term">rac cluster update </span>command: <span class="term">--ping-period </span>and <span class="term">--ping-timeout</span>. Information on the current values of the<span class="term"> --ping-period </span>and <span class="term">--ping-timeout</span> parameters is added to the result of the <span class="term">rac cluster info </span>command.</p><p>New methods in the Java administration server interface for the <span class="term">IClusterInfo </span>object: <span class="term">getPingPeriod()</span>, <span class="term">setPingPeriod()</span>, <span class="term">getPingTimeout()</span>, and <span class="term">setPingTimeout()</span>.</p></td><td>You could change the parameters of the disconnection tracking system only by restarting the cluster processes, as these parameters were specified in the command line to start the server agent (<span class="interface">ragent</span>).</td><td>Server cluster administrators can set up a connection check system without restarting cluster processes. With this feature, they can set up the cluster in the current network conditions or perform long-running internal operations (for example, data migration).</td></tr><tr title="Версия 8.3.26" class="tag_16 tag_42"><td><a name="5181d380-6f3e-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br></td><td>Now you can update and delete records (in addition to adding and replacing them) of subordinate information and accumulation registers. <span class="term">ReplacementMode.Join</span> write mode is not supported. The behavior is similar to the behavior of independent information registers.
The function is managed by the <span class="term">ExtendedReplaceMode </span>property of the register record set. The property has an effect only when operating with subordinate information and accumulation registers. If the property has the <span class="term">True </span>value, you can delete and replace records, change the <span class="term">LineNumber </span>property of a set record, and specify supported values of the <span class="term">ReplacementMode </span>system enumeration as the <span class="term">Replace </span>parameter value of the <span class="term">Write() </span>method for the subordinate information and accumulation registers.</td><td>Previously, you could only add and fully replace the records existing in the infobase for a record set of subordinate information and accumulation registers.</td><td>In some scenarios, you can significantly speed up operations with subordinate information registers and accumulation registers.</td></tr><tr title="Версия 8.3.26" class="compat tag_7 tag_1"><td><a name="a1d10c63-74bc-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Errors that occur when executing a query to a database copy DBMS are divided into recoverable and non-recoverable errors. Recoverable errors do not disable a database copy and allow further execution of queries from the application to such copy. Unrecoverable errors result in disabling a database copy and do not allow further query execution from the application.<p>The list of recoverable and non-recoverable errors differs in version 8.3.24 compatibility mode and with compatibility mode disabled.</p></td><td>Previously, any error that occurred when executing a query to a database copy DBMS led to disconnecting such copy from the infobase and did not allow further query execution in such copy. </td><td>If you try to run a query on a database copy that does not take into account possible data features, an exception will be thrown. The database copy will not be disabled, and other queries will be able to run queries in this copy.</td></tr><tr title="Версия 8.3.26" class="tag_34"><td><a name="bcf900a3-74cc-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 34); return false;">PDF document operations</a>.<br></td><td>Now you can define page parameters in a PDF document.<p>New property: <span class="term">PDFDocument.Pages</span>.</p><p>New optional parameter for the <span class="term">AddRepresentationObject()</span>, <span class="term">AddRepresentationObjectAsync()</span>, <span class="term">AddSignature()</span>, and <span class="term">AddSignatureAsync()</span> methods of the <span class="term">PDFDocument </span>object: <span class="term">ConsiderPageOrientation</span>.</p></td><td>This feature was not provided.</td><td>Advanced PDF document features.</td></tr><tr title="Версия 8.3.26" class="tag_14 tag_39 tag_10 tag_28"><td><a name="bc818325-7729-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>New feature: updated client application authentication form. Now you can display all available authentication types on the authentication form and quickly select the required authentication type. The system can store the last user authentication parameters for thin, thick, and web clients. The last 4 names of successfully authenticated users are now displayed in the user selection list. The authentication splash is displayed before the authentication dialog box appears and after successfully signing in to the infobase.<p>The payload used by the client application upon JWT authentication is changed.</p><p>To disable any authentication method, either prohibit this authentication method or change the password of the compromised user(s). If the password is changed, all stored access tokens become invalid.</p><p>New command of the client application startup: <span class="term">/ResetSavedAuth</span>. It resets the parameters of the last successful authentication.</p><p>New additional user authentication parameters: <span class="interface">Allow saving authentication</span>, <span class="interface">Save authentication by default</span>, and <span class="interface">Saved authentication lifetime</span>.</p><p>New methods for the manager of additional authentication settings: <span class="term">GetAuthenticationAutoSaveSettings</span><span class="term">()</span> and <span class="term">SetAuthenticationAutoSaveSettings</span><span class="term">()</span>.</p><p>New element for the <span class="term">&lt;point&gt;</span> element of the <span class="interface">default.vrd</span> file: <span class="term">&lt;authentication&gt;</span>. You can use it to set up the default authentication type and the available authentication types for this infobase.</p><p>There is now more information for event log events:</p><ul><li><span class="term">_$InfoBase$_.AdditionalAuthenticationSettingsUpdate</span>.</li><li><span class="term">_$Session$_.Authentication</span>.</li><li><span class="term">_$Session$_.AuthenticationError</span>.</li><li><span class="term">_$Session$_.AuthenticationFirstFactor</span>.</li></ul></td><td>These features were not provided.<p>The system could remember the last authenticated user only when using the OpenID Connect authentication.</p></td><td>Improved the interface of the user authentication dialog box. You can set the required authentication type as the default one. The system stores data for re-entry for all authentication types.</td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="99dbfc4b-77d6-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>In group conversations, you can now search in the participant list.<p>For group conversations with a large number of participants (more than 100 participants), you can load the participant list asynchronously. No more than 3,000 participants can participate in a group conversation.</p><p>You can create conversations with Read only mode. Such conversations do not allow you to add or change these conversations. You can change them using 1C:Enterprise language. New property: <span class="term">CollaborationSystemConversation.ReadOnly</span>.</p></td><td>Previously, you could not search for participants in group conversations.<p>The list of group conversation participants was always loaded immediately.</p><p>You could have an unlimited number of participants in conversations.</p><p>You could not create conversations unavailable for editing.</p></td><td>Improved collaboration system operations with group conversations with a large number of participants.</td></tr><tr title="Версия 8.3.26" class="tag_43"><td><a name="efb95e73-77f2-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Now you can manage what to display on the search string form of the dynamic list. Now you can enable and disable the search string, as well as disable the search string if it is impossible to effectively use full-text search. This feature is only available from 1C:Enterprise language via the system settings storage.
New object: <span class="term">DynamicListViewSettings</span>.<p>New settings for the system settings storage: <span class="term">DynamicListViewSettings </span>and <span class="term">DynamicListsViewSettings</span>.</p></td><td>This feature was not provided.<p>In some cases, full-text search used by the search string could be ineffective or incorrect.</p></td><td>You can specify that it is required to use the search string for both a specific dynamic list and all dynamic lists of the application.</td></tr><tr title="Версия 8.3.26" class="compat tag_13 tag_1"><td><a name="123d24a2-78b3-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>Now you can use block binary data storage in the 1C:Enterprise infobase (only in client/server mode). In<span class="interface"> version 8.3.25</span> and earlier compatibility mode, you can enable and disable the feature using the <span class="interface">Block binary data storage mode configuration</span> property. In other cases, the feature is always enabled and cannot be disabled.<p>For the built-in binary data storage, you can now manage where binary data which must be written to the binary data storage will be stored: only in the binary data storage or both in the infobase and storage. If data is stored both in the infobase and storage, the infobase will stay operational if the built-in binary data storage is destroyed or lost.</p><p>New methods for the binary data storage manager: <span class="term">GetBinaryDataStorageBinaryDataCopiesPlacementMode()</span> and <span class="term">SetBinaryDataStorageBinaryDataCopiesPlacementMode()</span>.</p></td><td>This feature was not provided.<p>When the binary data storage was connected, you could store data only in this storage.</p></td><td>You can convert an infobase that stores binary data larger than 1 GB between Microsoft SQL Server and PostgreSQL.<p>Improved reliability of storing binary data when using external binary data storages. If binary data is stored both in the infobase and binary data storage, to back up data, it is enough to back up the infobase.</p></td></tr><tr title="Версия 8.3.26" class="tag_44 tag_13"><td><a name="74c8dae6-78bb-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 44); return false;">Infobase verification and repair</a>.<br><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>If, when checking the binary data storage integrity (during infobase verification and repair), infobase objects with a binary data error were found (the binary data storage is unavailable, binary data is deleted from the storage or does not exist in the storage), the system outputs information that will identify the problematic object.</td><td>Previously, when checking the binary data storage integrity (during infobase verification and repair), if binary data errors occurred, the system did not identify the problematic objects.</td><td>Simplified identification of objects that have issues with binary data transferred to the binary data storage.</td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="ddb735e9-7968-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now 1C:Enterprise supports attachments for integration of the webhook type.<p>New optional parameters for the <span class="term">createMessage </span>collaboration interface request: <span class="term">data </span>and <span class="term">datаType</span>. New property for the <span class="term">CollaborationSystemMessage </span>object: <span class="term">StringDataFormat</span>.</p></td><td>This feature was not provided.</td><td>The integration of the webhook type can transfer data to 1C:Enterprise.</td></tr><tr title="Версия 8.3.26" class="tag_4"><td><a name="0c539fb8-7a35-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can invite external users to conversations and video calls. The invitation is sent via a special URL. Both external and internal users can follow the URL. The invitation may allow users to fully participate in the conversation or participate only in video calls. It is specified when generating the invitation.<p>You can get a URL when creating a new conversation, in the dialog box for adding conversation/video call participants, or in the menu of the out-of-context conversation form.</p><p>The user interface of the collaboration system is improved to provide new features.</p><p>Now you can revoke all issued invitations to participate in the conversation.</p><p>New method for the collaboration system manager: <span class="term">GetInviteUrlToConversation()</span>.</p></td><td>Previously, you could not connect an external or internal user to a video call via a URL. You needed to invite an external user to the website for external users and only then start a video call.</td><td>Users will be able to connect to video calls manually. The existing participants do not need to call a new participant.</td></tr><tr title="Версия 8.3.26" class="tag_27"><td><a name="1d03097b-eb6b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is 2.19.</td><td>The format version of configuration dump to XML files was 2.18.</td><td>Configuration dump to XML files supports new platform features.</td></tr><tr title="Версия 8.3.26" class="tag_45"><td><a name="5da406ef-fb1f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If the type collection acts as an operand of the <span class="term">SUM()</span> and <span class="term">AVG()</span> query language functions, the result of the functions will be a number without dimension limitation.<p>An accounting register resource with a type collection will have a length of 38 digits and a precision described by the type collection.</p></td><td>If the type collection acted as an operand of the <span class="term">SUM()</span> and <span class="term">AVG()</span> query language functions, the result of the functions was a number with parameters (length and precision) specified in the type collection.<p>Previously, an accounting register resource with a type collection had parameters (length and precision) described by the type collection.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.26" class="tag_46 tag_47"><td><a name="accdca36-0859-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>Now the documentation shows that the standalone server does not support integration services. The change is made to the documentation starting from version 8.3.21.</td><td>Previously, the documentation did not show that the standalone server does not support integration services.</td><td>Fixed error in the documentation.</td></tr><tr title="Версия 8.3.26" class="compat tag_7 tag_1"><td><a name="451dfc46-085b-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Now when you set the query text (the <span class="term">Query.Text </span>property) or call the <span class="term">Query </span>object methods, it does not change the values of the <span class="term">DatabaseCopiesUse </span>and <span class="term">UsedDatabaseCopies </span>properties of the <span class="term">Query </span>object.<p>This change is not implemented in 8.3.25 compatibility mode.</p></td><td>Previously, when you set the query text (the <span class="term">Query.Text </span>property) or called the <span class="term">Query </span>object methods, it set the <span class="term">Query.DatabaseCopiesUse </span>property to <span class="term">DatabaseCopiesUse.Auto </span>and cleared the <span class="term">Query.UsedDatabaseCopies </span>property.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9959bdf9-6c0c-11ee-963f-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.26" class="tag_10"><td><a name="f9d2ad74-6e83-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can select the following hash algorithm of 1C:Enterprise infobase user passwords: SHA-1, SHA-256, SHA-512, and PBKDF2-HMAC-SHA256. The hash algorithm is configured in the infobase parameters. If the hash algorithm differs from SHA-1, you can run the infobase only using 1C:Enterprise version 8.3.26 and later.<p>The PBKDF2-HMAC-SHA256 hash algorithm support is added for the <span class="term">DataHashing </span>object.</p><p>New global context methods: <span class="term">GetUserPasswordHashAlgorithmType()</span>, <span class="term">SetUserPasswordHashAlgorithmType()</span>, <span class="term">EvaluateStoredUserPasswordValue()</span>, and <span class="term">CheckUserPasswordComplianceWithStoredValue()</span>.</p><p>New system enumeration property: <span class="term">HashFunction.PBKDF2SHA256</span>.</p><p>New property: <span class="term">InfobaseUser.PasswordHashAlgorithmType</span>.</p><p>Data of the <span class="term">_$InfoBase$_.ParametersUpdate</span>, <span class="term">_$InfoBase$_.ParametersUpdateError</span>, <span class="term">_$User$_.New</span>, <span class="term">_$User$_.NewError</span>, <span class="term">_$User$_.Update</span>, and <span class="term">_$User$_.UpdateError </span>event log events now contains information about the used hash algorithm.</p></td><td>Previously, the SHA-1 algorithm was always used to hash passwords of 1C:Enterprise infobase users.</td><td>You can use more robust hash algorithms for infobase user passwords.</td></tr><tr title="Версия 8.3.26" class="tag_14 tag_10"><td><a name="cf5e50cf-72f9-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now 1C:Enterprise supports USIA protocol version 3.34.<p>New parameter for the <span class="term">clientconfig</span> section of the OpenID Connect provider details in the <span class="interface">default.vrd file</span>: <span class="term">client_certificate_hash</span>. It is required for the new protocol version.</p><p>You can still use the previous version of the USIA protocol.</p></td><td>This feature was not provided.</td><td>Now 1C:Enterprise supports the latest USIA protocol version.</td></tr><tr title="Версия 8.3.26" class="tag_10"><td><a name="3df92ac5-7334-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can specify the inactivity period time after which the user session will be forcibly terminated. This feature is implemented in thin, thick, mobile, and web clients. This feature is not provided in Designer. Before the session termination, the user will receive a warning. If they respond to this warning, they can cancel the forced session termination.<p>New parameters in the dialog box to set up infobase parameters: <span class="interface">Time for inactive session termination notification</span> and <span class="interface">Inactive session termination timeout</span>.</p><p>New global context methods: <span class="term">SetInactivityTimeForTerminateSessionNotification()</span>, <span class="term">GetInactivityTimeForTerminateSessionNotification()</span>, <span class="term">SetInactivityTimeForTerminateSession()</span>, and <span class="term">GetInactivityTimeForTerminateSession()</span>.</p><p>There is now more information for event log events:</p><ul><li><span class="term">_$InfoBase$_.ParametersUpdate</span>.</li><li><span class="term">_$InfoBase$_.ParametersUpdateError</span>.</li></ul><p>To forcibly terminate sessions due to inactivity, a CORP license is required.</p></td><td>This feature was not provided.</td><td>Reduced risk of unauthorized access to infobase data.<p>Reduced license consumption by disabling users who do nothing in the infobase for a long period of time.</p></td></tr><tr title="Версия 8.3.26" class="compat tag_46 tag_1"><td><a name="140785c7-2180-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br></td><td>Upgrade: the <span class="term">MaximumCount </span>parameter of the <span class="term">SelectMessages()</span> method of the integration service channel manager is used in accordance with the name: messages of the integration service channel are returned in the quantity that does not exceed the value specified in the parameter.<p>This change is not implemented in 8.3.25 compatibility mode.</p></td><td>When calling the <span class="term">SelectMessages()</span> method of the integration service channel manager, the value of the <span class="term">MaximumCount </span>parameter was ignored. The method always returned all messages of the integration service channel.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.26" class="compat tag_46 tag_1"><td><a name="17193785-2186-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br></td><td>If in the filter structure of the <span class="term">SelectMessages()</span> method of the integration service channel manager, the <span class="term">CorrelationId </span>filter parameter is set to the value of a zero UUID (NIL UUID, a value of zeros only), messages whose request message ID is equal to the zero UUID are returned.<p>This change is not implemented in 8.3.25 compatibility mode.</p></td><td>If in the filter structure of the <span class="term">SelectMessages()</span> method of the integration service channel manager, the <span class="term">CorrelationId </span>filter parameter was set to the value of a zero UUID (NIL UUID, a value of zeros only), such filter value was ignored and all channel messages were returned.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9959bdfb-6c0c-11ee-963f-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.26" class="tag_30 tag_31 tag_32 tag_48"><td><a name="eea79b7d-fb20-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>1C:Enterprise mobile version now supports RuStore mobile services:<ul><li>In-app purchases.</li><li>Push notifications.</li><li>Cartography and operations with coordinates.</li><li>Evaluation of applications in the store.</li></ul><p>If a built mobile application supports all mobile services, RuStore services have a higher priority than other mobile services. Now you can enable/disable RuStore service management modules (similar to Google and Huawei mobile services), as well as specify the parameters required to successfully build applications for RuStore in the mobile application builder.</p><p>New system enumeration values: <span class="term">DeliverableNotificationSubscriberType.RMS</span> and <span class="term">InAppPurchaseService</span>.<span class="term">RuStoreInAppPurchase.RuStoreInAppPurchase</span>.</p><p>The <span class="term">GetAccessToken() </span>method of the manager for sending deliverable notifications considers using RuStore services.</p></td><td>1C:Enterprise mobile version did not support RuStore mobile services. You were unable to develop mobile applications that could not be distributed through the Google Play and Huawei AppGallery stores.</td><td>More mobile services are now supported.</td></tr></table><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9959bdfe-6c0c-11ee-963f-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.26" class="tag_0"><a name="4555933d-217f-11ef-963f-0050569f678a"></a>New example of using the default settings. You can find the example in the "<span class="interface">Form settings management</span>" data processor. New item in the Configuration Guide: <span class="interface">Typical Development techniques - Default settings</span>.</li><li title="Версия 8.3.26" class="tag_0"><a name="6900cbb5-217f-11ef-963f-0050569f678a"></a>Now you can remember user authentication in the additional authentication settings.<p>
</p></li><li title="Версия 8.3.26" class="tag_0"><a name="a1df54fd-217f-11ef-963f-0050569f678a"></a>In the infobase settings, the password hash algorithm is set to SHA-256.</li></ul><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9959bdff-6c0c-11ee-963f-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.26" class="tag_7 tag_38"><td><a name="0361eb1f-5ece-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>If an extension that adds data (or contains its own data objects) is attached to the infobase, the tables of those objects cannot be transferred to a copy of the infobase. If the copy already has those tables, they will be removed during the update.</td><td>If such extensions were attached, 1C:Enterprise would not work properly. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.26" class="tag_21"><td><a name="a7c747bf-5ef5-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Faster merging of full-text search indexes. Increased computer CPU usage during the merge. Complete merging is now only possible when you call the <span class="term">UpdateIndex() </span>method of the full-text search manager with the <span class="term">EnableJoining </span>parameter set to <span class="term">True</span>. </td><td>Previously, merging full-text search indexes took longer. Complete merging could occur when a new batch of data was added to the search index.</td><td>Faster merging of full-text search indexes. Unpredictable complete merging of indexes when adding new data has been eliminated.</td></tr><tr title="Версия 8.3.26" class="tag_19 tag_44"><td><a name="46bdc37f-69ee-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 44); return false;">Infobase verification and repair</a>.<br></td><td>New infobase parameter: <span class="interface">Use additional indexes</span>. New methods: <span class="term">SetAdditionalIndexesUsage()</span> and <span class="term">GetAdditionalIndexesUsage()</span>. When the parameter is enabled, the CORP license availability is checked.<p>New infobase verification and repair mode: <span class="interface">Check and enable CORP functionality</span>.</p><p>New parameter of the <span class="term">/IBCheckAndRepair </span>command: <span class="term">-CheckAndEnableCORPFunctionality</span>.</p></td><td>This feature was not provided.</td><td>Now you can manage creation of additional indexes in the infobase.</td></tr><tr title="Версия 8.3.26" class="tag_19 tag_29"><td><a name="0e52dee6-86cd-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>IBM Db2 of all versions up to 10.1 (inclusive) is no longer supported.<p>Only IBM Db2 version 11.1 is supported.</p></td><td>Previously, IBM Db2 versions 9.1, 9.5, 9.7, and 10.1 were supported.</td><td>Obsolete IBM Db2 versions are no longer supported.</td></tr><tr title="Версия 8.3.26" class="tag_29 tag_19"><td><a name="61b48d9c-b2d2-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro Enterprise: 12.20.2, 13.16.2, 14.13.2, 15.8.2;</li><li>Postgres Pro CERT Enterprise: 13.16.2, 14.13.2, 15.8.2;</li></ul><p>DBMS version bitness: x86-64, E2k, ARM64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>These Postgres Pro DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.26" class="tag_29 tag_19"><td><a name="bd56ade0-b2e3-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro 1C: 17.0;</li><li>Postgres Pro Standard: 17.0.1;</li><li>Postgres Pro Enterprise: 16.4.2;</li><li>Postgres Pro CERT Enterprise: 16.4.2.</li></ul><p>DBMS version bitness: x86-64, E2k, ARM64.
The products are supported in 1C:Enterprise version 8.3.22 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>These Postgres Pro DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.26" class="tag_29 tag_15"><td><a name="3721652c-b2ec-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The following Linux distribution packages are no longer supported:<ul><li>CentOS 7</li><li>Oracle Linux 7</li><li>Red Hat Enterprise Linux 7</li><li>Astra Linux Common Edition 2.12</li></ul></td><td>Previously, 1C:Enterprise supported the following Linux distribution packages:<ul><li>CentOS 7</li><li>Oracle Linux 7</li><li>Red Hat Enterprise Linux 7</li><li>Astra Linux Common Edition 2.12</li></ul></td><td>Outdated Linux distribution packages are no longer supported.</td></tr><tr title="Версия 8.3.26" class="tag_29 tag_19"><td><a name="e3adf3a9-ce69-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro 1С: 12.22, 13.18, 14.15, 15.10</li><li>Postgres Pro Standard: 12.22.1, 13.18.1, 14.15.1, 15.10.1</li><li>Postgres Pro Enterprise: 12.22.1, 13.18.1, 14.15.1, 15.10.1</li><li>Postgres Pro CERT Standard: 14.15.1, 15.10.1</li><li>Postgres Pro CERT Enterprise: 13.18.1, 14.15.1, 15.10.1.</li></ul><p>DBMS version bitness: x86-64, E2k, ARM64.</p><p>The products are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These Postgres Pro DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.26" class="tag_29 tag_19"><td><a name="2c946b89-ce6a-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro 1С: 16.6, 17.2</li><li>Postgres Pro Enterprise: 16.6.1</li><li>Postgres Pro CERT Standard: 16.6.1, 17.2.1</li><li>Postgres Pro CERT Enterprise: 16.6.1.</li></ul><p>DBMS version bitness: x86-64, E2k, ARM64.</p><p>The products are supported in 1C:Enterprise version 8.3.22 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These Postgres Pro DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.26" class="tag_37 tag_10"><td><a name="8bc576d5-d25a-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>OpenID authentication is considered a priority authentication method if this method is configured for the infobase. The general authentication form is displayed only if the user has explicitly performed the logout operation in the OpenID authentication provider, or the provided username and password cause a provider authentication error. In all other cases, the system tries to use the customized authentication before displaying any input forms to the user.<p>If OpenID Connect authentication is configured for the infobase, when the web client is launched, an attempt is made to authenticate with the provider using the parameters of the last successful authentication. The general authentication form will be displayed if the web client has failed to authenticate with OpenID Connect.</p></td><td>If OpenID authentication was configured for the infobase, a login confirmation dialog (containing a list of available authentication types) was displayed each time a user tried to sign in.</td><td>Application authentication has become more straightforward and expected.</td></tr><tr title="Версия 8.3.26" class="tag_29 tag_19"><td><a name="240adcac-d32a-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro Enterprise: 17.2.1.</li></ul><p>DBMS version bitness: x86-64, E2k, ARM64.</p><p>The products are supported in 1C:Enterprise version 8.3.22 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.26" class="tag_32"><td><a name="eccc361a-eabf-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile 1C:Enterprise version 8.3.26 is now supported in the mobile application builder.</td><td>Mobile 1C:Enterprise version 8.3.26 was not supported in the mobile application builder.</td><td>Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.</td></tr><tr title="Версия 8.3.26" class="tag_19 tag_29"><td><a name="35d1a001-eac0-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Tantor SE 1C DBMS versions 14.15.0, 15.10.0 and 16.6.0.<p>Supported processors: ARM64 and x86-64.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Tantor SE DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.26" class="tag_14 tag_10"><td><a name="ff4240b6-ef5f-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The protocol of OpenID provider implemented in the 1C:Enterprise platform is changed to ensure backward compatibility. We recommend that you update the client applications.<p>For the thin client version 8.3.26, the default authentication flag is saved when using an OpenID provider that runs on the 1C:Enterprise platform version 8.3.25 and earlier.</p><p>An OpenID provider that runs on the 1C:Enterprise platform version 8.3.26 can service client applications version 8.3.25 and earlier.</p></td><td>For the thin client version 8.3.26, the default authentication flag was not displayed or remembered when using an OpenID provider that runs on 1C:Enterprise platform version 8.3.25 and earlier.<p>Client applications of version 8.3.25 and earlier received unexpected responses from an OpenID provider running on the 1C:Enterprise platform version 8.3.26. As a result, their correct operation was impossible.</p></td><td>Restored backward compatibility of the OpenID provider version 8.3.26 and client applications of earlier versions. Client applications of version 8.3.26 can operate with the OpenID provider version 8.3.25 and earlier.</td></tr><tr title="Версия 8.3.26" class="tag_49"><td><a name="14837690-5747-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 49); return false;">Binary data</a>.<br></td><td>If you try to simultaneously delete and read a database record containing binary data, no binary data reading errors occur.</td><td>Previously, if you tried to simultaneously delete and read a database record containing binary data, binary data reading errors could occur.</td><td>Eliminated the issue that might occur when simultaneously trying to delete and read a record containing binary data.</td></tr></table><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9959be00-6c0c-11ee-963f-0050569f678a">Transition from the previous version to the version 8.3.26</a></h2><ul><li title="Версия 8.3.26" class="tag_0"><a name="9959be01-6c0c-11ee-963f-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.26.
</li><li title="Версия 8.3.26" class="tag_0"><a name="9959be02-6c0c-11ee-963f-0050569f678a"></a>Some features that are added in version 8.3.26 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li></ul><p><a href="#9959bdf4-6c0c-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h1><a name="7c3108e4-256a-11ee-963f-0050569f678a">Version 8.3.25</a></h1><p title="Версия 8.3.25" class="tag_0"><a name="7c3108f3-256a-11ee-963f-0050569f678a"></a>Version 8.3.25 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.25" class="tag_0"><a name="7a779a88-26fd-11ee-963f-0050569f678a"></a>The binary data storage graduated out of beta.<p>The binary data storage requires CORP license.</p></p><hr></hr><ul><li><a href="#7c3108e5-256a-11ee-963f-0050569f678a">New functionality and changes</a></li><li><a href="#7c3108e6-256a-11ee-963f-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#7c3108e7-256a-11ee-963f-0050569f678a">Optimization</a></li><li><a href="#7c3108e8-256a-11ee-963f-0050569f678a">Changes that affect system behavior</a></li><li><a href="#7c3108e9-256a-11ee-963f-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#7c3108ea-256a-11ee-963f-0050569f678a">Renamed objects</a></li><li><a href="#7c3108eb-256a-11ee-963f-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#7c3108ee-256a-11ee-963f-0050569f678a">Demo configuration changes</a></li><li><a href="#7c3108ef-256a-11ee-963f-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#7c3108f0-256a-11ee-963f-0050569f678a">Transition from the previous version to the version 8.3.25</a></li></ul><h2><a name="7c3108e5-256a-11ee-963f-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.25" class="compat tag_2 tag_1"><td><a name="47731ab2-26df-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>New value for the <span class="interface">Compatibility mode</span> configuration property: <span class="interface">Version 8.3.24</span>.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.23 was available.
</td><td>Configurations developed using 1C:Enterprise platform version 8.3.24 or earlier can now run on version 8.3.25 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.25 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.24 after the migration to version 8.3.25 even if you have disabled the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.25" class="tag_50"><td><a name="9a3d4731-26e1-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 50); return false;">Speech synthesis</a>.<br></td><td>Now you can use speech synthesis.<p>Implemented the following methods for the speech manager: <span class="term">StartTextToSpeech()</span>, <span class="term">StopTextToSpeech()</span>, <span class="term">Synthesize()</span>, and <span class="term">GetTextToSpeechAvailableVoices()</span>.</p><p>New objects: <span class="term">TextToSpeechVoiceDescription</span>, <span class="term">TextToSpeechVoiceParameterDescription</span>, <span class="term">TextToSpeechVoiceParameterValueDescription</span>.</p><p>Speech synthesis is not supported on Windows XP and Windows Server 2003.</p></td><td>Previously, 1C:Enterprise platform did not contain built-in speech synthesis tools.</td><td>Now you can use speech synthesis. Now you can use the platform tools to implement voice interfaces with users.</td></tr><tr title="Версия 8.3.25" class="tag_36"><td><a name="76ad26e3-26ea-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>New global context method: <span class="term">CallSleep()</span>. The method is available only on the server. The method is unavailable in server calls initiated from the client application.</td><td>This feature was not provided.</td><td>Now you can terminate the execution of code in 1C:Enterprise language in server code (background and scheduled jobs, Internet services, and other).</td></tr><tr title="Версия 8.3.25" class="tag_13 tag_10"><td><a name="3d590d67-26eb-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New tool for Designer: <span class="interface">Main menu - Administration - Binary data storage management</span>. It is similar to the standard <span class="interface">Binary data storage management</span> function.</td><td>Managing the binary data storage was not available in Designer.</td><td>In Designer, you can now perform the same set of operations as when using the standard function. You could only call the function if the client application with this infobase was successfully started.</td></tr><tr title="Версия 8.3.25" class="tag_13"><td><a name="36861edc-26fd-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>New feature for the binary data storage: deduplication of binary data chunks in the Microsoft Compound Binary File format (CBF, files of Microsoft Office 2003 and earlier). This process is not controlled by the user. Files that have not been accessed for more than 2 months are deduplicated.</td><td>This feature was not provided. Previously, only whole files were deduplicated.</td><td>When you store a large number of files of Microsoft Office 2003 and earlier, you can reduce the disk space for storing this data by eliminating duplicate chunks of such files.</td></tr><tr title="Версия 8.3.25" class="tag_45"><td><a name="bc063c24-27b4-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>New capabilities for the query language:<ul><li>Add data to a previously created temporary table (the <span class="term">ADD </span>clause is implemented).</li><li>Index a temporary table by field sets (the <span class="term">INDEX BY SETS </span>clause is implemented).</li><li>Create unique indexes in temporary tables (implemented the <span class="term">UNIQUE </span>option for the <span class="term">INDEX BY </span>and <span class="term">INDEX BY SETS </span>clauses).</li></ul><p>New features for the <span class="term">QuerySchemaSelectQuery </span>object:</p><ul><li>New property: <span class="term">Indexes</span>.</li><li>New property: <span class="term">TableToAdd</span>.</li><li>The <span class="term">Index </span>property is deprecated.</li></ul><p>We recommend that you use new features in the following cases:</p><ul><li>You select data from one temporary table, combine it with other data, and place in a new temporary table.</li><li>You execute multiple queries to the same temporary table with filter or merging by different fields (field sets).</li></ul></td><td>These features were not provided.</td><td>Advanced temporary table features in the query language.</td></tr><tr title="Версия 8.3.25" class="tag_38"><td><a name="480f375c-2ab6-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Now you can adopt business processes and tasks. For adopted objects, you can change a business process route map. This map fully replaces a route map of the extended configuration when you import an extension.</td><td>These features were not provided.</td><td>Advanced configuration extension features.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="0f67d5c3-2b8e-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When you add a new production server, you can disable the assignment of any functionality to this server. To do this, create a forbidding functionality assignment rule. It will be applied automatically.<p>New features:</p><ul><li>New checkbox in the dialog box for creating a new production server: <span class="interface">Set forbidding functionality assignment rule</span>.</li><li>New parameter for the <span class="term">IServerAgentConnection.RegWorkingServer()</span> COM connection method: <span class="term">SetProhibitingFunctionalityAssignmentRule</span>.</li><li>New parameter for the <span class="term">IAgentAdminConnection.regWorkingServer()</span> Java interface method: <span class="term">AddProhibitingAssignmentRule</span>.</li><li>New parameter for the <span class="term">server</span> mode of the <span class="interface">RAC</span> utility: <span class="interface">add-prohibiting-assignment-rule</span>.</li><li>New parameter for the <span class="term">AdministrationWorkServer.Write()</span> method: <span class="term">SetProhibitingFunctionalityAssignmentRule</span>.</li></ul></td><td>This feature was not provided.<p>Previously, new functionality was immediately assigned to a new production server. This could lead to various errors as the new production server was not fully configured.</p></td><td>Simplified setup of a new production server by the administrator after adding the server to the server cluster.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="028b2472-2b91-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can select a security profile from the list of existing security profiles for the <span class="interface">Security profile</span> and <span class="interface">Safe mode security profile </span>fields of the infobase properties. For the <span class="interface">Resource consumption counter</span> field of the properties of the resource consumption limit, you can select a counter name from the list of existing resource consumption counters.<p>You can still enter names of security profiles and resource consumption counters manually if needed.</p><p>These features are implemented in the cluster console and the standard data processor of server cluster management.</p></td><td>These features were not provided. Previously, you could enter names of security profiles and resource consumption counters only manually.</td><td>Reduced the risk of incorrect input for:<ul><li>Security profile name while editing the infobase properties.</li><li>Name of the resource consumption counter while editing resource consumption limits.</li></ul></td></tr><tr title="Версия 8.3.25" class="tag_10"><td><a name="d2cb127a-2b92-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>In the file infobase, the list of places where 1C:Enterprise searches for the<span class="term"> ExternalSessionManagementRequired </span>and <span class="term">ExternalSessionManagementConnectionString </span>parameters in the <span class="interface">conf.cfg </span>files is extended.</td><td>In the file infobase, 1C:Enterprise searched for the <span class="term">ExternalSessionManagementRequired </span>and <span class="term">ExternalSessionManagementConnectionString </span>parameters in the <span class="interface">conf.cfg </span>file. This file was located in the infobase directory or by a path specified in the <span class="term">ConfLocation </span>parameter of the configuration file located in the infobase directory.</td><td>Now you can manage the placement of settings of the external session management service more flexibly in the file infobase.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="3dc242e4-2b98-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can manage the load on server clusters for infobases with low user activity:<ul><li>Minimum period to start scheduled jobs without active users.</li><li>Maximum shift to start scheduled jobs without active users.</li><li>Delay in configuration export by a working process without active users.</li></ul><p>New features:</p><ul><li>New infobase parameters in the cluster console and the standard data processor: <span class="interface">Delay in configuration export by a working process</span>, <span class="interface">Minimum period to start scheduled jobs</span>, and <span class="interface">Maximum shift to start scheduled jobs</span>.</li><li>New COM connection properties of the <span class="term">IInfoBaseInfo </span>object: <span class="term">ConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers</span>, <span class="term">MinimumScheduledJobsRunningPeriodWithoutActiveUsers</span>, and <span class="term">MaximumScheduledJobsStartShiftWithoutActiveUsers</span>.</li><li>New Java interface methods of the <span class="term">IInfoBaseInfo </span>object: <span class="term">getConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers()</span>, <span class="term">setConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers()</span>, <span class="term">getMinimumScheduledJobsStartPeriodWithoutActiveUsers()</span>, <span class="term">setMinimumScheduledJobsStartPeriodWithoutActiveUsers()</span>, <span class="term">getMaximumScheduledJobsStartShiftWithoutActiveUsers()</span>, and <span class="term">setMaximumScheduledJobsStartShiftWithoutActiveUsers()</span>.</li><li>New parameters of the <span class="term">infobase </span>mode of the <span class="interface">RAC </span>utility: <span class="term">configuration-unload-delay-by-working-process-without-active-users</span>, <span class="term">minimum-scheduled-jobs-start-period-without-active-users</span>, and <span class="term">maximum-scheduled-jobs-start-shift-without-active-users</span>.</li><li>New properties for the <span class="term">AdministrationInfoBase </span>object: <span class="term">ConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers</span>, <span class="term">MinScheduledJobsStartPeriodWithoutActiveUsers</span>, and <span class="term">MaxScheduledJobsStartShiftWithoutActiveUsers</span>.</li></ul></td><td>This feature was not provided.</td><td>Now you can manage the scheduled job behavior for infobases with low user activity easier and faster.</td></tr><tr title="Версия 8.3.25" class="tag_10 tag_17"><td><a name="8374109a-2b9c-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>New features:<ul><li>You can manage the placement of technological log files: in a directory structure or in a flat file list. New attribute of the <span class="term">log </span>item of the <span class="interface">logcfg.xml </span>file for technological log setup: <span class="term">placement</span>.</li><li>You can set up log file rotation: by the time or by a log file size. You can specify rotation criteria: a file size and a rotation period. New attributes of the <span class="term">log </span>item of the <span class="interface">logcfg.xml </span>file for technological log setup: <span class="term">rotation</span>, <span class="term">rotationsize</span>, and <span class="term">rotationperiod</span>.</li><li>You can set up compression for outdated technological log files. Compression is performed in the background during the log file rotation. New attribute of the <span class="term">log </span>item of the <span class="interface">logcfg.xml </span>file for technological log setup: <span class="term">compress</span>.</li><li>You can save technological log files in the JSON format. New attribute of the <span class="term">log </span>item of the <span class="interface">logcfg.xml </span>file for technological log setup: <span class="term">format</span>.</li></ul><p>You can disable automatic deletion of technological log files by specifying 0 in the <span class="term">history </span>attribute of the <span class="term">log </span>item of the<span class="interface"> logcfg.xml </span>file for technological log setup. In this case, use external tools to clear the technological log directory. Changed the algorithm for deleting technological log files. Canceled the check for unknown technological log files in the directory.</p><p>Implemented a new property that describes a severity level of technological log events: <span class="term">level</span>.</p></td><td>These features were not provided.</td><td>Advanced features for generating the 1C:Enterprise technological log. For example, you can use it in external log analysis tools.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="86e99451-2b9f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can provide performance indicators (metrics) of the server cluster in the OpenMetrics format for the cluster administration server (<span class="interface">ras</span>) and the standalone server (<span class="interface">ibsrv</span>). Implemented a set of HTTP request parameters that will allow you to limit the set of received metrics.<p>New commands for the command line of the cluster administration server: <span class="term">monitor-address</span>, <span class="term">monitor-port</span>, and <span class="term">monitor-base</span>. To access metrics, use 1C:Enterprise authentication.</p><p>New parameters for the command line of the standalone server: <span class="term">monitor-address</span>, <span class="term">monitor-port</span>, and <span class="term">monitor-base</span>. New section of the <span class="term">gates </span>section for the standalone server configuration file: <span class="term">monitor</span>. The section includes the following parameters: <span class="term">address</span>, <span class="term">port</span>, and <span class="term">base</span>. Authentication is not required to access metrics.</p><p>To use metrics in OpenMetrics format, a CORP license is required.</p></td><td>This feature was not provided.</td><td>Advanced features for generating the 1C:Enterprise technological log. For example, you can use it in external log analysis tools.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="6fc0d582-2ba0-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented a new event log mode (without the infobase) for the standalone server management utility (<span class="interface">ibcmd</span>): You can export the event log in the XML and JSON formats and export the log event model as an XSD schema. New command: <span class="term">eventlog</span>.</td><td>This feature was not provided.</td><td>Simplified the event log receipt for analysis with external tools.</td></tr><tr title="Версия 8.3.25" class="tag_7"><td><a name="60cadb6b-2bb2-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Now 1C:Enterprise supports a new tool for database backup update (version 2) for PostgreSQL. To enable this tool, make sure all the following conditions are met:<ul><li>PostrgeSQL version 10 or later.</li><li>The DBMS is installed or updated from a distribution package provided by 1C Company.</li><li>The DBMS configuration file has the <span class="term">wal_level=logical</span> parameter set.</li><li>In the standard data processor for database backup management, the standard replication version 2 is enabled for the selected infobase.</li></ul></td><td>Previously, 1C:Enterprise supported the new tool for database backup update (version 2) only for Microsoft SQL Server.</td><td>When you use the new tool for database backup update, the update speed increases.</td></tr><tr title="Версия 8.3.25" class="tag_8"><td><a name="d74b4f02-2bb6-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>Now 1C:Enterprise supports the ACH.1 format in the base64 encoding in cryptography methods.</td><td>This feature was not provided.</td><td>Now you can process ACH.1 data (certificates, revocation lists, and PKCS#7 data) directly in the base64 encoding without prior conversion into binary data.</td></tr><tr title="Версия 8.3.25" class="tag_16"><td><a name="700b8265-2bb9-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>Implemented additional record modes for a record set of an independent information register:<ul><li>Merge. In this case, records whose key fields match with the record set to be saved are updated in the infobase. The remaining set records are simply added to the register.</li><li>Delete. In this case, records whose key fields match with the records included in the record set are deleted from the infobase.</li></ul><p>New system enumeration that describes possible options for saving a record set of the information register: <span class="term">ReplacementMode</span>. For the <span class="term">InformationRegisterRecordSet.Write()</span> method, you can specify a value of the <span class="term">ReplacementMode </span>system enumeration type as a value of the <span class="term">Replace </span>parameter in addition to the <span class="term">Boolean </span>type value.</p><p>The <span class="term">BeforeWrite()</span> and <span class="term">OnWrite()</span> event handlers and the respective subscription handlers receive a value of the <span class="term">Replacing </span>parameter as it was passed to the <span class="term">Write() </span>method of the record set of the information register.</p></td><td>Previously, you could only add or fully replace the existing infobase records of a record set of an independent information register.</td><td>In some scenarios, you can significantly speed up operations with independent information registers.</td></tr><tr title="Версия 8.3.25" class="tag_51"><td><a name="9a034813-2c54-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>Extended automated configuration testing capabilities:<ul><li>New method: <span class="term">TestedFormTable.CopyRow()</span>.</li><li>New <span class="term">GetParent()</span> method for the following objects: <span class="term">TestedClientApplicationWindow</span>, <span class="term">TestedCommandInterfaceGroup</span>, <span class="term">TestedCommandInterfaceButton</span>, <span class="term">TestedForm</span>, <span class="term">TestedFormField</span>, <span class="term">TestedFormGroup</span>, <span class="term">TestedFormButton</span>, <span class="term">TestedFormTable</span>, and <span class="term">TestedFormDecoration</span>.</li><li>New methods for the <span class="term">TestedFormField</span> object: <span class="term">TitleIsShown()</span>.</li><li>New method for the form field extension for the tested formatted document: <span class="term">ClickFormattedDocumentHyperlink()</span>.</li><li>New feature for the <span class="term">TestedFormField.WriteContentToFile()</span> method: you can save content to a file with a different name if the document in the field has already been saved. New <span class="term">SaveAs</span> method parameter.</li><li>New HTML document extension for the tested form field. It allows you to perform actions similar to the formatted document field.</li><li>New methods to expand a form field for a tested spreadsheet document: <span class="term">TextIsWithinAreaBounds()</span> and <span class="term">IncludedInMergedArea()</span>.</li><li>New method for the <span class="term">TestedFormDecoration</span> and <span class="term">TestedFormField</span> objects that display a formatted document: <span class="term">GetFormattedStringHyperlinksPresentations()</span>.</li><li>New method for cases when a form field displays a spreadsheet document: <span class="term">TestedFormField.ExecuteChoiceFromDetailsMenu()</span>.</li><li>New method: <span class="term">TestedApplication.ClearFileDialogResult()</span>.</li><li>New methods for the <span class="term">TestedForm</span> object: <span class="term">GetChoiceListPresentation(), CurrentEnable()</span>, and <span class="term">CurrentReadOnly()</span>.</li><li>New property: <span class="term">TestedClientApplicationWindow.URL</span>.</li><li>New global context method: <span class="term">CurrentSessionIsTested()</span>.</li></ul></td><td>These features were not provided.</td><td>Extended automated application testing capabilities.</td></tr></table><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108e6-256a-11ee-963f-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.25" class="tag_12 tag_10 tag_6"><td><a name="fa133d5a-26ff-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New feature: you can save and restore administered server parameters for the <span class="interface">Server management </span>standard data processor (the <span class="interface">Cluster parameters</span> button). The parameters are saved to an XML file. The file structure is not documented.<p>Creating a new connection to a server cluster and commands for saving and restoring the cluster list are grouped in the <span class="interface">Connections </span>button.</p></td><td>The <span class="interface">Server management</span> standard data processor did not support saving or restoring parameters of administered server clusters to a file or from a file.</td><td>It is now easier to transfer server cluster parameter settings between computers, for example, when you deploy identical clusters.</td></tr><tr title="Версия 8.3.25" class="tag_52"><td><a name="457695da-278e-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>When you use an accounting register, managed lock absorption is triggered before managed lock escalation. As a result, concurrent operation with the accounting register increases.</td><td>Previously, when you used an accounting register, managed lock escalation was triggered earlier than lock absorption. As a result, concurrent operation with the accounting register could become impossible.</td><td>Increased concurrent operation with an accounting register.</td></tr><tr title="Версия 8.3.25" class="tag_4 tag_18 tag_28"><td><a name="40f1bffd-2797-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>New feature: you can use video calls in Safari version 13 or later running macOS.</td><td>Video calls were not supported in Safari.</td><td>Video calls are now supported in Safari running macOS.</td></tr><tr title="Версия 8.3.25" class="tag_10"><td><a name="0b01d0b2-2af2-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>If an error occurs when importing the distribution package of a client application over HTTP, the error message text includes not only the error code, but also a text description (if available).</td><td>If an error occurred when importing the distribution package of a client application over HTTP, the error message text included only the error code.</td><td>Simplified troubleshooting of issues that occur when importing the distribution package of a client application over HTTP.</td></tr><tr title="Версия 8.3.25" class="tag_53 tag_6 tag_10"><td><a name="9c920c24-2c7f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When a session is closed and a server call is terminated from Designer, 1C:Enterprise language, the resource consumption tool, or through the administration tools, if the session data file was not deleted, the user will see a session termination reason message. The message will be displayed upon the next server call even if the session was deleted not during the server call.<p>New system enumeration property: <span class="term">ErrorCategory.ForcedShutdown</span>. This category includes all exceptions related to terminating a server call using administration tools and all exceptions related to closing a session using platform tools (from Designer, from 1C:Enterprise language, or through administration tools).</p></td><td>The user could not see the text that might have been specified by the administrator in case of forced user session termination.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_53 tag_6 tag_10"><td><a name="c73cdaa8-2c81-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now<span class="term"> </span>you can specify a session termination reason message to be displayed to the user in the dialog box of user session termination from Designer when updating the database configuration.<p>New parameter for the (<span class="interface">ibcmd</span>) <span class="term">infobase restore </span>and <span class="term">config apply </span>commands of the standalone server management utility: <span class="term">session-terminate-message</span>. This parameter allows you to specify a text with a session termination reason to be displayed to the user.</p><p>If the <span class="term">session-terminate </span>command-line option of the <span class="interface">ibcmd </span>utility instructs to terminate user sessions, and the <span class="term">session-terminate-message </span>parameter is not specified, the utility will wait for you to enter a message in the console and will keep running only after the message is entered.</p></td><td>Previously, when you terminated user sessions from Designer, you could not specify a text with a user session termination reason.<p>The standalone server management utility (<span class="interface">ibcmd</span>) did not allow you to specify a text to be displayed to the user as a session termination reason.</p></td><td>Now you can specify a text with a session termination reason when sessions are terminated while updating the infobase configuration from Designer or using the standalone server management utility.</td></tr></table><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108e7-256a-11ee-963f-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.25" class="tag_54"><td><a name="794ae429-2797-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 54); return false;">Global search</a>.<br></td><td>Accelerated global search operations.</td><td>Global search operations took more time.</td><td>Accelerated global search operations.</td></tr><tr title="Версия 8.3.25" class="tag_6"><td><a name="a0d381fc-2799-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Optimized metadata loading when loading the configuration in client/server mode.<p>Reduced time required to connect the first client to the infobase. Faster startup of the first infobase session on a working process that has not yet serviced sessions of this infobase.</p></td><td>In client/server mode, configuration metadata loading was time-consuming. It took a long time to the first infobase session on a working process that has not yet serviced sessions of this infobase.</td><td>Faster startup of the first infobase session on a working process that has not yet serviced sessions of this infobase.</td></tr><tr title="Версия 8.3.25" class="tag_47"><td><a name="d589eb01-2799-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>Faster startup of a standalone server in file and client/server modes.</td><td>Standalone server startup was time-consuming.</td><td>Faster startup of a standalone server in file and client/server modes.</td></tr><tr title="Версия 8.3.25" class="tag_20"><td><a name="270c627f-279a-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Optimized the global replacement in the configuration in Designer.</td><td>Previously, the global replacement in the configuration took a lot of time.</td><td>Optimized the global replacement in the configuration in Designer.</td></tr><tr title="Версия 8.3.25" class="tag_20"><td><a name="6dadccab-279a-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Optimized search for references to configuration objects in Designer.</td><td>Previously, search for references to configuration objects was time-consuming.</td><td>Optimized search for references to configuration objects in Designer.</td></tr><tr title="Версия 8.3.25" class="tag_6"><td><a name="3e42b3a0-27b0-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Optimized CPU and RAM in a server cluster (with fault tolerance level 2 or higher), improved reliability and speed of server state replication under high loads and the overall cluster stability under high loads.</td><td>When running a highly loaded server cluster with fault tolerance level 2 or higher, the cluster used more computer resources and was less stable.</td><td>Optimized server cluster computer resources and improved server cluster reliability and stability.</td></tr><tr title="Версия 8.3.25" class="tag_21"><td><a name="492750c9-2ab8-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Optimized use of RAM by the full-text search engine.<p>For that, re-index the full-text search index.</p></td><td>The full-text search engine did not optimally utilize the computer RAM.</td><td>Reduced RAM consumption by the full-text search engine and improved application stability.</td></tr><tr title="Версия 8.3.25" class="tag_7"><td><a name="9b0d2518-2aea-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Selecting a copy on which to run the query is now faster.</td><td>Selecting a copy on which to run the query took more time.</td><td>Improved application performance when it is necessary to select a database copy on which to run the query before running the query.</td></tr><tr title="Версия 8.3.25" class="tag_4"><td><a name="6b4f7a07-2af2-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>When you make video calls in the thin client, the load on the CPU and network channel of the client computer is reduced.</td><td>When you made video calls in the thin client, the load on the CPU and network channel of the client computer was higher.</td><td>The load on the CPU and network channel of the client computer during video calls in the thin client is reduced.</td></tr><tr title="Версия 8.3.25" class="tag_4"><td><a name="83e3a286-2af3-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The load on the CPU and network channel of the collaboration system server is reduced when you make group video calls using the thin client.<p>For that:</p><ul><li>update the platform to version 8.3.25.</li><li>update the collaboration system server to version 25.</li><li>update the Janus video server on the collaboration system server to version 1.0.4.</li></ul></td><td>When you made group video calls using the thin client, there was an increased load on the CPU and network channel of the collaboration system server.</td><td>Using thin clients for group video calls improves the quality of video calls and increases the number of users in a single group video call.</td></tr><tr title="Версия 8.3.25" class="tag_19"><td><a name="888d1db8-7d57-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Creating object tables and writing record sets of information and accumulation registers is improved.</td><td>Creating object tables and writing record sets of information and accumulation registers took more time.</td><td>Improved creation of object tables and writing record sets of information and accumulation registers.</td></tr><tr title="Версия 8.3.25" class="tag_7"><td><a name="29f86c07-7984-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Improved performance of initial database copy filling.</td><td>Initial database copy filling took more time.</td><td>Improved performance of initial database copy filling.</td></tr></table><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108e8-256a-11ee-963f-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.25" class="tag_4"><td><a name="c0abb7a4-27cb-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can change the administrator of the collaboration system subscriber. You can keep the list of administrators of the collaboration system subscriber. You can change the email address for the collaboration system user.<p>New methods for the collaboration system manager: <span class="term">GetNewAdministrationKey()</span>, <span class="term">SendTemporaryCode()</span>, <span class="term">AddToSubscriberAdministrators()</span>, <span class="term">ExcludeFromSubscriberAdministrators()</span>, and <span class="term">SetSubscriberEmail()</span>. </p><p>New property: <span class="term">CollaborationSystemUser.SubscriberAdministrator</span>. </p><p>New property: <span class="term">CollaborationSystemUsersFilter.SubscriberAdministrator</span>.</p><p>Updated the <span class="interface">Collaboration system management</span> standard function.</p></td><td>This feature was not provided. Previously, you could not change the subscriber administrator.</td><td>Now you can restore access to a collaboration system subscriber when access to the subscriber registration email has been lost.</td></tr><tr title="Версия 8.3.25" class="tag_10"><td><a name="420e5bf7-2acc-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>An error is generated when saving (by any means) an infobase user with a specified operating system username exceeding 128 characters.</td><td>When saving an infobase user with a specified operating system username exceeding 128 characters:<ul><li>If an infobase user was saved in Designer, the session was abnormally terminated.</li><li>If an infobase user was saved using 1C:Enterprise language, the value was ignored and no error was generated.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="f01ce891-2ae7-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>For the <span class="term">Data </span>property of a <span class="term">CLSTR </span>event (when the <span class="term">Event </span>property is set to <span class="term">performance update</span>), the displayed data that describes the current performance indicators of the cluster processes is documented.</td><td>The data that is displayed in the <span class="term">Data</span> property of a <span class="term">CLSTR</span> event (when the <span class="term">Event</span> property is set to <span class="term">performance update</span>) was not documented.</td><td>Updated the system documentation.</td></tr><tr title="Версия 8.3.25" class="tag_38"><td><a name="c0feb9e3-2aef-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: you can include attributes added by a configuration extension to extended objects in native and adopted filter criteria.<p>New feature: you can change the <span class="interface">Command parameter type</span> property in extensions for common commands and configuration object commands.</p><p>New feature: you can change the <span class="interface">Selection form</span> property in extensions for constants, attributes, resources, dimensions, and fields of external data sources.</p><p>New feature: you can add native subordinate subsystems to adopted subsystems in extensions. New feature: you can disable modification when attaching an extension for the <span class="interface">Content </span>property of adopted subsystems. Adopted subsystems are edited in the properties panel, similar to other adopted configuration objects.</p></td><td>These features were not provided.</td><td>Advanced configuration extension features.</td></tr><tr title="Версия 8.3.25" class="tag_16 tag_55"><td><a name="5db6eab7-2ba9-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br><a href="#" onclick="onTagClick(this, 55); return false;">Catalogs</a>.<br></td><td>New feature: for dimensions of an independent information register and the <span class="term">Owner </span>standard catalog attribute, you can specify what actions will be taken during infobase restructuring when the set of types that describe the type of the corresponding object is reduced. Now you can:<ul><li>Disable type editing.</li><li>Convert values to a new set of types.</li><li>Delete records that match the deleted types.</li></ul><p>New property for an independent information register dimension and the <span class="term">Owner </span>standard catalog attribute: <span class="interface">Type shrinking mode</span>. New properties for the <span class="term">StandardAttributeDescription </span>and <span class="term">Dimension </span>metadata objects: <span class="term">TypeReductionMode</span>.</p></td><td>This feature was not provided.<p>An attempt was always made to convert the value for an information register dimension. Type shrinking was always blocked for the <span class="term">Owner </span>standard catalog attribute.</p></td><td>Now it is easier to develop configuration objects (information registers and subordinate catalogs) that are processed only using 1C:Enterprise language, but the types include a large number of other configuration objects.</td></tr><tr title="Версия 8.3.25" class="tag_22"><td><a name="e7d2c3d2-7d59-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>New feature: parallel update of all used Data accelerator instances if a scalable Data accelerator is used (Data accelerator is running on more than one production server of the server cluster) and a database copy is located on more than one Data accelerator instance.<p>An update error on a single Data accelerator instance will not stop the entire Data accelerator update. All instances except for the one where the error occurred will be updated.</p></td><td>Previously, Data accelerator instances were updated sequentially, one by one. If an error occurred while updating one instance, the process was terminated. As a result, all Data accelerator instances that followed the one with an error had incorrect data.</td><td>Reduced data update time if Data accelerator consists of several instances.</td></tr><tr title="Версия 8.3.25" class="tag_27"><td><a name="63a6569a-8512-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is 2.18.</td><td>The format version of configuration dump to XML files was 2.17.</td><td>Configuration dump to XML files supports new platform features.</td></tr></table><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108e9-256a-11ee-963f-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.25" class="compat tag_56 tag_1"><td><a name="f52dbccd-27c5-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>In XDTO serialization of charts of accounts, properties corresponding to common attributes are placed after properties corresponding to accounting flags.<p>This change is not implemented in 8.3.24 compatibility mode.</p></td><td>In XDTO serialization of charts of accounts, properties corresponding to common attributes were placed before properties corresponding to accounting flags.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="adda1a4b-2ab7-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When a server cluster is started, all the required data is immediately read from the cluster list and cluster registry files. In case of errors reading this data, the server cluster is not started and the detected errors are recorded in the technological log.</td><td>When a server cluster was started, data from the cluster list and cluster registry files was read as needed. Errors that could occur when reading these files resulted in hard-to-diagnose errors during cluster operation.</td><td>Simplified administration for errors that may occur when reading the cluster list and cluster registry at server cluster startup.</td></tr><tr title="Версия 8.3.25" class="tag_4"><td><a name="4a5ff6fe-2abf-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Upgrade: you can place the button panel in collaboration system messages (including integrations with various external systems).<p>Collaboration system message actions are deprecated. It is recommended that you replace the collaboration system actions on the button panel.</p><p>New property for the <span class="term">CollaborationSystemMessage </span>object: <span class="term">SourceMessage</span><span class="term">.</span><span class="term">ButtonPanel</span>.
New method for the <span class="term">CollaborationSystemIntegration </span>object: <span class="term">MessageButtonPanelButtonActionSupported()</span>.</p><p>New event handler for the collaboration system bot module: </p><p><span class="term">CollaborationSystemMessageButtonPanelButtonClickProcessing()</span>.</p><p>New event handler for the application module: </p><p><span class="term">OnCollaborationSystemMessageButtonPanelButtonClick()</span>.</p><p>The following properties and methods are deprecated:</p><ul><li>Property <span class="term">CollaborationSystemMessage.Actions</span>.</li><li>Methods <span class="term">AttachMessageActionHandler()</span> and <span class="term">DetachMessageActionHandler()</span> for the collaboration system manager.</li><li>Application module event handler <span class="term">OnCollaborationSystemMessageActionChoice()</span>.</li><li>Objects <span class="term">CollaborationSystemMessageActionCollection </span>and <span class="term">CollaborationSystemMessageAction</span>.</li></ul></td><td>There was an option to set actions for collaboration system messages that was not available in integration messages.</td><td>Now you can implement a single visual interface of interaction between a collaboration system user and an information system (bot interface), which looks uniformly in all collaboration system messages.</td></tr><tr title="Версия 8.3.25" class="tag_10"><td><a name="255badda-2ac8-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can no longer specify the same email address (in different registers) for different infobase users. If you try to save a second user with an existing email address, an exception will be thrown.</td><td>You could specify the same email address (in different registers) for different infobase users.</td><td>Removed possible ambiguity in identifying a user by email address.</td></tr><tr title="Версия 8.3.25" class="tag_10"><td><a name="9b5ec1a5-2aca-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Accelerated email address uniqueness verification when saving users.<p>For that, we recommend that you run the infobase verification and repair in repair mode. This will create the necessary index for the user table and speed up the email address uniqueness verification.</p><p>The email address length cannot exceed 128 characters.</p></td><td>When you saved an infobase user, the email uniqueness verification was time-consuming.<p>The email address length could exceed 128 characters.</p></td><td>Accelerated email address uniqueness verification when saving users.</td></tr><tr title="Версия 8.3.25" class="tag_10 tag_6"><td><a name="ed1bf253-2acc-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New properties for the <span class="term">AdministrationSeance </span>object:<ul><li><span class="term">CurrentDBMSCallDuration</span>.</li><li><span class="term">LastDBMSCallTime</span>.</li></ul></td><td>This feature was not provided.
These properties were available in other system administration interfaces, but were missing from the <span class="term">AdministrationSeance </span>object.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="b659ed47-2ae1-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>A resource consumption counter with the "server call" registration period counts each session of a single user as a separate object. Combining different sessions of a single user is preserved for counters whose data registration period is other than "server call".</td><td>A resource consumption counter with the "server call" registration period summarized the indicators of all sessions of a single user.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="7c4214ae-2ae5-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented correct processing of termination of a server call executing a DBMS call using a resource consumption counter:<ul><li>When a session is terminated, an error specified by the administrator is displayed and the session is terminated.</li><li>When a call is terminated, an error specified by the administrator is displayed and the terminated server call is not repeated.</li></ul></td><td>The termination of a server call executing a DBMS call using a resource consumption counter was processed incorrectly:<ul><li>First, a DBMS call was terminated. Then a counter restriction was triggered.</li><li>When a server call was terminated, the DBMS call was repeated. When a session was deleted, a bad connection error was displayed and then the session was deleted.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_6 tag_10"><td><a name="e84244ad-2ae5-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented correct display of used CPU time values for resource consumption counters.</td><td>Used CPU time values for resource consumption counters may have been displayed incorrectly.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_56 tag_57"><td><a name="41b721fb-2c54-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br><a href="#" onclick="onTagClick(this, 57); return false;">JSON support</a>.<br></td><td>New feature: you can explicitly specify a value type during XDTO serialization (in XML or JSON) of values that dot not exist in the data model (for an open content model). New parameter for the <span class="term">XDTODataObject.Add()</span> method: <span class="term">TypeAssignment</span>.<p>When reading data using the <span class="term">XDTOFactory </span>object, you can now specify how to determine the type of the value to be read if the value does not exist in the content model. New parameter for the <span class="term">ReadXML()</span> and <span class="term">ReadJSON()</span> methods of the <span class="term">XDTOFactory </span>object: <span class="term">TypeAssignment</span>.</p></td><td>During XDTO serialization of a value missing from the data model, the type of such value was not written to the resulting file.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_10"><td><a name="0b768bbd-2c83-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Information about closed infobase sessions is saved to:<ul><li>Client/server mode and standalone server mode: <span class="interface">snccntx.dat </span>file.</li><li>File mode: <span class="interface">1Cv8snc.1CD </span>file in the infobase directory. The file is not deleted when the last infobase session ends.</li></ul><p>Information about closed sessions is stored for a week. Old information is cleared once an hour.</p></td><td>This feature was not provided.</td><td>Upgrade: storage of information about closed infobase sessions.</td></tr><tr title="Версия 8.3.25" class="tag_4"><td><a name="b7b73e2e-611a-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: a set of methods, availability, and behavior in different client applications are unified for the following collections: <span class="term">CollaborationSystemAttachmentCollection</span>, <span class="term">CollaborationSystemMessageButtonPanelButtonRow</span>, and <span class="term">CollaborationSystemMessageButtonPanelButtonRows</span>.</td><td>The following collections had different sets of methods, availability, and behavior in different client applications: <span class="term">CollaborationSystemAttachmentCollection</span>, <span class="term">CollaborationSystemMessageButtonPanelButtonRow</span>, and <span class="term">CollaborationSystemMessageButtonPanelButtonRows</span>.</td><td>Unified description and behavior of similar object collections in the collaboration system. Eliminated unexpected system behavior.</td></tr></table><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108ea-256a-11ee-963f-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.25" class="tag_0"><td><a name="c9e72377-26e1-11ee-963f-0050569f678a"></a>Standard speech processing.</td><td><ul><li>Speech recognition management.</li></ul></td><td><ul><li>Speech service management.</li></ul></td></tr></table><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108eb-256a-11ee-963f-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.25" class="tag_30 tag_31 tag_48"><td><a name="67a26d50-2af1-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Now you can use the speech recognition tool in the mobile version of 1C:Enterprise:<ul><li>Mobile platform. Allows you to use only a cloud-based speech recognition service.</li><li>Mobile client. Allows you to use both a cloud-based and a local speech recognition tool.</li></ul><p>Implemented the corresponding objects, properties, and methods of 1C:Enterprise language in the mobile version of 1C:Enterprise.</p></td><td>This feature was not provided.</td><td>You can use speech recognition on mobile devices.</td></tr><tr title="Версия 8.3.25" class="tag_48 tag_30 tag_31 tag_4"><td><a name="1c1be600-418e-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now the mobile version supports sharing files from a mobile application through standard interfaces of the mobile operating system.<p>Now the collaboration system supports sharing the entire message, the selected text of a message or a message input field, or a message attachment.</p><p>New global context property: <span class="term">DeviceDataSharingTools</span>. New feature for the<span class="term"> MultimediaData </span>object: a constructor of an object from a file.</p><p>New values for the <span class="term">CollaborationSystemStandardCommand </span>system enumeration: <span class="term">ShareMessage </span>and <span class="term">ShareAttachment</span>. You can only use these commands in the mobile client.</p></td><td>This feature was not provided.</td><td>Now it is easier to use third-party data processing applications that are generated in a mobile application built on the mobile version of 1C:Enterprise.</td></tr><tr title="Версия 8.3.25" class="tag_30 tag_31 tag_29"><td><a name="21237661-5610-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>iOS versions 9 and 10 are no longer supported
iOS versions 13, 14, 15, and 16 are now supported.</td><td>The mobile version of 1C:Enterprise supported iOS versions 9 and 10.</td><td>The list of supported iOS versions is updated. The mobile version of 1C:Enterprise supports iOS versions 11, 12, 13, 14, 15, and 16.</td></tr><tr title="Версия 8.3.25" class="tag_32"><td><a name="3f3d3fd2-5ba3-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>To build mobile applications, use Java version 17 or later.<p>To build mobile applications using mobile version 8.3.25, use:</p><ul><li>Mobile application builder version 8.3.25.</li><li>Java version 17 or later (Java version 19 or later is recommended)</li></ul><p>To build mobile applications using earlier platform versions, use:</p><ul><li>Mobile application builder version 8.3.25.</li><li>Java version 17 or later.</li></ul><p>When using Java versions 8–16, you can still build mobile applications using mobile version 8.3.24 or earlier versions.</p></td><td>To build mobile applications, Java versions from 8 to 13 were used. The build tools did not allow you to use Java version 14 or later.</td><td>Now there are new tools for building Android mobile applications.</td></tr><tr title="Версия 8.3.25" class="tag_30 tag_31 tag_48"><td><a name="37be8b5b-5c3c-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>New values for the <span class="term">BarcodeType </span>system enumeration: <span class="term">QRCode</span>, <span class="term">DataMatrix</span>, <span class="term">PDF417</span>, <span class="term">Aztec</span>, <span class="term">MaxiCode</span>, <span class="term">UPCA</span>, <span class="term">UPCE</span>, <span class="term">EAN13</span>, <span class="term">EAN8</span>, <span class="term">Codabar</span>, <span class="term">Code93</span>, <span class="term">Code128</span>, <span class="term">RSS14</span>, <span class="term">RSSExpanded</span>, <span class="term">Code39</span>, and <span class="term">ITF</span>.<p>For the <span class="term">ShowBarcodeScanning()</span> method, the <span class="term">BarcodeType </span>parameter can have an array of values that describe what barcode types are expected in this scanning. A mobile application keeps a single list of scannable barcode types across all supported mobile platforms.</p><p>Improved barcode recognition quality.</p><p>The scan window on Android is now larger.</p></td><td>The <span class="term">ShowBarcodeScanning()</span> method did not support accurately specifying the list of expected barcodes. The barcode recognition quality was worse. The list of supported scannable barcode types depended on the platform for which the mobile application was being built.</td><td>Improved barcode scanning quality. When you specify expected barcodes accurately, this can reduce the CPU load during scanning, resulting in lower power consumption during barcode scanning.</td></tr><tr title="Версия 8.3.25" class="tag_48"><td><a name="db48b6df-6807-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Now the mobile version allows you to offer the user to rate the application and provide feedback in the application store of the corresponding mobile operating system from 1C:Enterprise language.<p>New global context method: <span class="term">ShowInputAppRate()</span>.</p></td><td>This feature was not provided.</td><td>Allows you to offer users to send ratings and reviews to the application store without leaving the application. Ratings and reviews affect the overall application ranking in search results. Applications that have more ratings and reviews are more commonly offered to the users.</td></tr><tr title="Версия 8.3.25" class="tag_32"><td><a name="e5e34fba-699b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>When you build Android-based mobile applications, the builder will check whether the added manifest element of the application you build is already available in the manifest. If the element you add is already in the manifest, it is not added again.</td><td>Previously, when you built Android-based mobile applications, the builder did not check whether the added manifest element of the application you built was already available in the manifest.</td><td>Reduced the number of difficult-to-diagnose errors when building Android-based mobile applications which occur when, for example, add-ins require a permission that is already requested upon building by another add-in or the application. As a result of the change, duplicate records will not be included in the resulting manifest of the application being built. This will allow you to build an application that was previously built with errors.</td></tr><tr title="Версия 8.3.25" class="tag_30 tag_31 tag_48"><td><a name="420d6684-0852-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>1C:Enterprise 8 now supports the Firebase Cloud Messaging service on HTTP v1 for sending push notifications. The service is supported in version 8.3.25.43 and later mobile versions. To use push notifications, modify the application in terms of getting and using an access token for the Firebase Cloud Messaging service on HTTP v1.<p>The <span class="term">GetAccessToken()</span> method of the manager for sending deliverable notifications is used to get an access token (changes are made to the type and content of the method parameters).</p><p>The <span class="term">Send()</span> method of the manager for sending deliverable notifications uses the previously received access token.</p></td><td>Previously, the 1C:Enterprise mobile platform did not support the Firebase Cloud Messaging service on HTTP v1. It supported the previous service version, which is disabled by Google.</td><td>Updated support for the Android push notification service.</td></tr></table><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108ee-256a-11ee-963f-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.25" class="tag_0"><a name="5b1627c4-a499-11ee-963f-0050569f678a"></a>For the <span class="term">OfficeManager</span> collaboration system bot, actions in messages are replaced with buttons (<span class="interface">Setup</span> and <span class="interface">Check now</span>).</li><li title="Версия 8.3.25" class="tag_0"><a name="3dfb9b2c-a49d-11ee-963f-0050569f678a"></a>New feature: an example of writing a record set of the information register in merge mode in the <span class="term">EditPrices</span> data processor.<p>
</p></li><li title="Версия 8.3.25" class="tag_0"><a name="77efe704-f1bf-11ee-963f-0050569f678a"></a>Now you can edit the parameters for sending push notifications via Huawei Push Kit in the <span class="term">PushNotificationsSetup </span>common form.</li><li title="Версия 8.3.25" class="tag_0"><a name="2f2e7a1a-f1c0-11ee-963f-0050569f678a"></a>In the <span class="term">StoredFiles </span>catalog list form, you can share the catalog item content with other applications on a mobile device (the <span class="term">ShareFile </span>form command).<p>
</p></li></ul><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108ef-256a-11ee-963f-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.25" class="tag_22 tag_29"><td><a name="fc89e940-a612-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Now you can run Data accelerator on Astra Linux, ALT Linux, and RED OS.<p>For the exact version numbers, see the documentation.</p></td><td>Data accelerator was not supported on Astra Linux, ALT Linux, and RED OS.</td><td>Extended list of operating systems that support Data accelerator.</td></tr><tr title="Версия 8.3.25" class="compat tag_36 tag_1"><td><a name="c6eab845-e141-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The error of generating UUIDs of versions 3 and 5 when using the <span class="term">UUID</span> object is fixed. This change is not implemented in 8.3.24 compatibility mode.<p>New method: <span class="term">GetUUIDWithCompatibilitySupport()</span>. It will allow getting a UUID with an error (as in previous platform versions) with compatibility mode disabled. It is not recommended to use this method for any other purpose.</p></td><td>Previously, when generating UUIDs of versions 3 and 5 using the <span class="term">UUID</span> object, UUIDs were generated with an error. The result did not fully meet the RFC 4122 standard.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_56"><td><a name="7e9c97c6-eda7-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>The size of the XML item value cannot exceed 100,000,000 characters.</td><td>Previously, the size of the XML item value could not exceed 10,000,000 characters. This value was not documented.</td><td>Reduced the number of errors that occurred as the actual size of the XML document item exceeded the maximum size.</td></tr><tr title="Версия 8.3.25" class="tag_30 tag_31 tag_48"><td><a name="c99011b8-f1b8-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Now you can use speech synthesis in the mobile version of 1C:Enterprise. New feature: <span class="interface">Speech synthesis</span>.</td><td>Previously, the mobile version of 1C:Enterprise did not support speech synthesis.</td><td>Advanced 1C:Enterprise mobile platform features. You can implement voice prompts for certain application processes in mobile applications based on the 1C:Enterprise mobile platform.</td></tr><tr title="Версия 8.3.25" class="tag_29 tag_19"><td><a name="d4b52cf5-1cf9-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 16.2</li><li>Postgres Pro Standard 16.2.1</li><li>Postgres Pro Enterprise 16.2.1</li><li>DBMS version bitness: x86-64.</li></ul><p>The versions are supported in 1C:Enterprise 8.3.22 and later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>These versions of Postgres Pro DBMS were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_29 tag_19"><td><a name="b0741210-0858-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 12.18, 13.14, 14.11, 15.6</li><li>Postgres Pro Standard 12.18.2, 13.14.2, 14.11.2, 15.6.2</li><li>Postgres Pro Enterprise 12.18.2, 13.14.2, 14.11.2, 15.6.2</li><li>DBMS version bitness: x86-64.</li></ul><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>Previously these versions of Postgres Pro DBMS were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_32"><td><a name="3be90bbe-2fd6-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile 1C:Enterprise version 8.3.25 is now supported in the mobile application builder.</td><td>Mobile 1C:Enterprise version 8.3.25 was not supported in the mobile application builder.</td><td>Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.</td></tr><tr title="Версия 8.3.25" class="tag_29 tag_19"><td><a name="b1917f18-5bb3-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td><ul><li>Support of the following Postgres Pro DBMS versions is implemented:
Postgres Pro 1C: 12.19, 13.15, 14.12, 15.7, 16.3;</li><li>Postgres Pro Standard: 12.19.2, 13.15.2, 14.12.2, 15.7.2, 16.3.1;</li><li>Postgres Pro Enterprise: 12.19.2, 13.15.2, 14.12.2, 15.7.2, 16.3.1.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously these versions of Postgres Pro DBMS were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_29 tag_19"><td><a name="cc4ac54c-5bb3-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro 1C: 16.3;</li><li>Postgres Pro Standard: 16.3.1;</li><li>Postgres Pro Enterprise: 16.3.1.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.22 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously these versions of Postgres Pro DBMS were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_29 tag_19"><td><a name="ed5f215c-5bb6-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro Standard: 13.15.2, 14.12.2, 15.7.2;</li><li>Postgres Pro Enterprise: 13.15.2, 14.12.2, 15.7.2.</li></ul><p>DBMS version bitness: E2k. </p><p>The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously these versions of Postgres Pro DBMS were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_29 tag_19"><td><a name="12f71812-5bb7-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro Standard: 16.3.1;</li><li>Postgres Pro Enterprise: 16.3.1.</li></ul><p>DBMS version bitness: E2k. The products are supported in 1C:Enterprise version 8.3.22 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously these versions of Postgres Pro DBMS were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_44"><td><a name="9cf12552-5e19-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 44); return false;">Infobase verification and repair</a>.<br></td><td>Optimized one of the steps in the infobase verification and repair process (<span class="interface">Check logical infobase integrity &gt; Other</span>). This step is required when upgrading to version 8.3.25 for faster interaction with infobase users.</td><td>Previously, this step took a significant amount of time.</td><td>Reduced the time needed to restructure the user list.</td></tr><tr title="Версия 8.3.25" class="tag_30 tag_31 tag_29"><td><a name="3ddbf64f-770b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The mobile version of 1C:Enterprise now supports Android 14. The mobile version of 1C:Enterprise supports Android versions 5.0 - 14.<p>When a mobile application runs on Android 14 and later, if the mobile application uses the functionality of the <span class="interface">Picture and video library</span>, users can not only completely allow or deny access to the library, but also specify individual images or videos to provide access to.</p></td><td>Previously the mobile 1C:Enterprise version supported Android versions 5.0 - 13.</td><td>Now the mobile 1C:Enterprise version supports the latest Android versions.</td></tr><tr title="Версия 8.3.25" class="tag_29 tag_19"><td><a name="fd910636-7cbf-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>13.16, 14.13, 15.8;</li><li>Postgres Pro Standard: 12.20.1, 13.16.1, 14.13.1, 15.8.1;</li><li>Postgres Pro Enterprise: 12.20.1, 13.16.1, 14.13.1, 15.8.1;</li><li>Postgres Pro CERT Standart: 14.13.1, 15.8.1.</li><li>Postgres Pro CERT Enterprise: 13.16.1, 14.13.1, 15.8.1.</li></ul><p>DBMS version bitness: x86-64, E2k, ARM64.</p><p>The products are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously these versions of Postgres Pro DBMS were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_29 tag_19"><td><a name="337a97c2-7cc0-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro 1C: 16.4;</li><li>Postgres Pro Standard: 16.4.1;</li><li>Postgres Pro Enterprise: 16.4.1;</li><li>Postgres Pro CERT Standart: 16.4.1;</li><li>Postgres Pro CERT Enterprise: 16.4.1.</li></ul><p>Разрядность версий СУБД: x86-64, E2k, ARM64.</p><p>The products are supported in 1C:Enterprise version 8.3.22 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously these versions of Postgres Pro DBMS were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_14 tag_58"><td><a name="4270759d-879a-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>Now 1C:Enterprise supports OpenID Connect authentication (including USIA authentication) in separated infobases.<p>Client applications that use OpenID Connect authentication support the <span class="term">/Z</span> option of the client startup string.</p><p>In the <span class="interface">default.vrd </span>file, you can pass the separator values to the URL specified in the<span class="term"> redirect_uri </span>parameter of the OpenID provider description section.</p></td><td>Previously, 1C:Enterprise did not support OpenID Connect authentication in separated infobases.</td><td>Simplified OpenID Connect authentication in separated infobases.</td></tr><tr title="Версия 8.3.25" class="tag_59"><td><a name="2a5118f3-b3b3-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>Values of form attributes with the <span class="term">Arbitrary </span>type are correctly restored from the form settings.<p>We recommend that application developers analyze the usage of stored attributes of this type.</p></td><td>Previously, values of form attributes with the <span class="term">Arbitrary </span>type were not restored from the form settings.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.25" class="tag_15 tag_29"><td><a name="b4be743a-c4fe-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>1C:Enterprise now supports MOC 12 Linux distribution package. The distribution package runs on x86-64 processors.</td><td>The distribution package was not supported.</td><td>Extended list of supported Linux distribution packages.</td></tr><tr title="Версия 8.3.25" class="tag_19 tag_29"><td><a name="23d67d8c-c507-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Tantor SE 1C DBMS versions 14.13.0, 15.8.0 and 16.4.1.<p>Supported processors: x86-64.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Tantor SE DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.25" class="tag_36"><td><a name="b017f790-c518-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The sequence in which property values are filled when using the <span class="term">FillPropertyValues()</span> method on Linux is changed. The sequence of properties may vary depending on the 1C:Enterprise version and the operating system used.<p>We do not recommend that you use the <span class="term">FillPropertyValues()</span> method to set property values that change the value of other properties. For example, do not apply this method to the <span class="term">PrintParametersKey </span>property as setting this property may replace values of other properties.</p></td><td>The sequence in which property values were filled when using the <span class="term">FillPropertyValues()</span> method on Linux was different.</td><td>Changed sequence in which property values are filled when using the <span class="term">FillPropertyValues()</span> method on Linux.</td></tr><tr title="Версия 8.3.25" class="tag_19 tag_38 tag_58"><td><a name="c2a2191d-d27d-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>The reliability of the platform is improved when there are several working processes or production servers in the cluster, to which connections can be assigned from a single separated infobase that uses extensions.</td><td>Previously, when there were several working processes or production servers in the cluster, to which connections could be assigned from a single separated infobase using extensions, the platform was unstable and could lead to unexpected errors.</td><td>Improved reliability of the platform with a distributed infobase, which uses extensions.</td></tr><tr title="Версия 8.3.25" class="tag_10"><td><a name="33f8f36f-eacc-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When creating an infobase, all installed configuration templates will be displayed in the creation dialog box. The <span class="term">AppVersion </span>property of the configuration template manifest is ignored when filling the template list.</td><td>Previously, when creating the infobase, the creation dialog box displayed only those templates that contain values <span class="term">8.2</span> and <span class="term">8.3</span> in the <span class="term">AppVersion </span>property of the configuration template manifest file.</td><td>You can create configurations from templates created by 1C:Enterprise version 8.5.1 and later.</td></tr><tr title="Версия 8.3.25" class="tag_35 tag_60"><td><a name="b9f60407-58c5-11f0-a153-0050569f678a"></a><a href="#" onclick="onTagClick(this, 35); return false;">System operation safety</a>.<br><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br></td><td>When you open a spreadsheet document from a file, unsafe operation protection is active if enabled. If the spreadsheet document contains OLE objects and the document is opened in a client application running Windows, a warning is displayed. To enable unsafe operation protection, use the user property or the <span class="interface">conf.cfg </span>configuration file.<p>The positive answer to the system's question is recorded by user and infobase. The negative answer is not recorded, and the confirmation request will be displayed the next time you try to open a spreadsheet document with OLE objects.</p></td><td>When you opened a spreadsheet document from a file, unsafe operation protection was not used.</td><td>Improved system security when opening spreadsheet documents containing OLE objects from a file.</td></tr></table><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="7c3108f0-256a-11ee-963f-0050569f678a">Transition from the previous version to the version 8.3.25</a></h2><ul><li title="Версия 8.3.25" class="tag_0"><a name="7c3108f1-256a-11ee-963f-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.25.
</li><li title="Версия 8.3.25" class="tag_0"><a name="7c3108f2-256a-11ee-963f-0050569f678a"></a>Some features that are added in version 8.3.25 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.25" class="tag_0"><a name="a06b3dd2-2ab8-11ee-963f-0050569f678a"></a>To make the full-text search engine use less RAM, clear the full-text search index and recreate it on platform version 8.3.25.</li><li title="Версия 8.3.25" class="tag_0"><a name="6e5c3343-2ae6-11ee-963f-0050569f678a"></a>It is recommended that you check and repair the logical integrity of the infobase using the verify and repair feature. Just select the "<span class="interface">Other</span>" category of the "<span class="interface">Check logical infobase integrity</span>" item. This will:<ul><li>Speed up the creation of infobase users that require an email address.</li><li>Speed up authentication with OpenID Connect and access tokens if the mapping key is the infobase user's email address.</li><li>Speed up the code retrieval operation when recovering the password. </li></ul><p>It is recommended that you perform this operation every time the infobase is updated to 1C:Enterprise version 8.3.25, including after the rollback to the previous platform version and the subsequent return to version 8.3.25.</p></li></ul><p><a href="#7c3108e4-256a-11ee-963f-0050569f678a"><small>Table of contents</small></a></p><h1><a name="9cfe5ba1-7d2f-11ed-963f-0050569f678a">Version 8.3.24</a></h1><p title="Версия 8.3.24" class="tag_0"><a name="9cfe5bb0-7d2f-11ed-963f-0050569f678a"></a>Version 8.3.24 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#9cfe5ba2-7d2f-11ed-963f-0050569f678a">New functionality and changes</a></li><li><a href="#9cfe5ba3-7d2f-11ed-963f-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#9cfe5ba4-7d2f-11ed-963f-0050569f678a">Optimization</a></li><li><a href="#9cfe5ba5-7d2f-11ed-963f-0050569f678a">Changes that affect system behavior</a></li><li><a href="#9cfe5ba6-7d2f-11ed-963f-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#9cfe5ba7-7d2f-11ed-963f-0050569f678a">Renamed objects</a></li><li><a href="#9cfe5ba8-7d2f-11ed-963f-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#9cfe5bab-7d2f-11ed-963f-0050569f678a">Demo configuration changes</a></li><li><a href="#9cfe5bac-7d2f-11ed-963f-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#9cfe5bad-7d2f-11ed-963f-0050569f678a">Transition from the previous version to the version 8.3.24</a></li></ul><h2><a name="9cfe5ba2-7d2f-11ed-963f-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.24" class="compat tag_2 tag_1"><td><a name="0d805097-9178-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>New value for the <span class="interface">Compatibility mode </span>configuration property: <span class="interface">Version 8.3.23</span>.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.22 was available.
</td><td>You can run configurations developed in versions 8.3.23 and earlier in version 8.3.24 without changing the configuration and data structures. This way, you can migrate to version 8.3.24 without changing the configuration, then make required changes, and disable compatibility mode. You can also use version 8.3.23 after migration to version 8.3.24. You can do it both before you disable compatibility mode and after you enable it again.
</td></tr><tr title="Версия 8.3.24" class="tag_37"><td><a name="e912308a-9183-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Now you can use CryptoPro to establish a secure HTTP connection. You can manage the check mode of server certificate revocation using 1C:Enterprise language.<p>New object: <span class="term">CryptoProSecureConnection</span>. New system enumeration: <span class="term">ServerTLSCertificateRevocationCheckMode</span>. New property: <span class="term">OpenSSLSecureConnection.ServerTLSCertificateRevocationCheckMode</span>. New parameter for the <span class="term">OpenSSLSecureConnection </span>object constructor: <span class="term">ServerTLSCertificateRevocationCheckMode</span>.</p><p>New feature: the <span class="term">HTTPConnection</span> object constructor can get the <span class="term">CryptoProSecureConnection </span>object as a <span class="term">SecureConnection</span> parameter value.</p></td><td>Previously you were unable to use CryptoPro to establish a secure HTTP connection. Managing the check mode of server certificate revocation using 1C:Enterprise language was unavailable. </td><td>Advanced secure HTTP connection features. </td></tr><tr title="Версия 8.3.24" class="tag_9"><td><a name="ab6ec6e6-918d-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 9); return false;">Speech recognition</a>.<br></td><td>Now you can restrict local speech recognition for 1C:Enterprise system using the following tools:<ul><li>The <span class="term">/DisableLocalSpeechToText </span>command-line option.</li><li>The "<span class="term">disstt</span>" parameter of the infobase connection string.</li><li>The <span class="term">AdministrationInfoBase.DisableLocalSpeechToText </span>property of the object for server cluster administration.</li><li>The<span class="term"> IInfoBaseInfo.DisableLocalSpeechToText </span>property of the COM object for server cluster administration.</li><li>The<span class="term"> setDisableLocalSpeechToText()</span> and <span class="term">getDisableLocalSpeechToText() </span>methods of the <span class="term">InfoBaseInfo </span>Java interface object for server cluster administration.</li><li>New infobase property for the server cluster administration utility (<span class="interface">rac</span>): <span class="term">disable-local-speech-to-text</span>.</li><li>The <span class="term">disable-local-speech-to-text </span>parameter of the standalone server startup (including in the configuration file).</li><li>You can manage this feature in the standard data processor for server management.</li></ul></td><td>This feature was not provided.
Previously you were unable to restrict local speech recognition.</td><td> Now you can forcibly restrict local speech recognition. However, you can still use remote speech recognition.</td></tr><tr title="Версия 8.3.24" class="tag_13"><td><a name="1120b696-91a7-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>Now you can use any external data storage accessible over Amazon S3 as a binary data storage. New global context property: <span class="term">BinaryDataExternalStorages</span>. To access the settings of a binary data storage and an external binary data storage, the <span class="term">Administration </span>right is required. The standard function of binary data storage management is now improved.<p>To use the S3 storage as an external binary data storage, a CORP license is required.</p><p>This feature is provided solely for beta testing purpose. To use the S3 storage as an external binary data storage during beta testing, a testing license is required. Without it, the feature is unavailable.</p><p>
</p><p>
</p></td><td>This feature was not provided.<p>Previously you were able to store binary data only on the computer running 1C:Enterprise server cluster.</p><p>
</p></td><td>Advanced binary data storage features.
</td></tr><tr title="Версия 8.3.24" class="tag_13"><td><a name="df288af6-91aa-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>Now you can eliminate duplicates of repeating data (deduplication). Deduplication occurs both when writing data and in the background.
New properties for the <span class="term">BinaryDataStorageInformatio</span>n object: <span class="term">StoredDataSizeOnDisk</span> and <span class="term">DeduplicatedItemsCount</span>.</td><td>This feature was not provided.</td><td>A binary data storage can take up less disk drive space if the same data is placed in the storage.</td></tr><tr title="Версия 8.3.24" class="tag_13"><td><a name="c8c3e3e6-95a2-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>When using a binary data storage, you can now do the following:<ul><li>Get statistical information about the binary data storage.</li><li>Clear the storage of unused data.</li><li>Clear and back up the binary data storage at the same time.</li></ul><p>New manager methods of the binary data storage: <span class="term">GetInformation()</span>, <span class="term">ClearUnusedSpaceByUniversalDate()</span>, and <span class="term">GetBackupCreationUniversalDate()</span>. New global context method: <span class="term">GetDatabaseAndBinaryDataStorageDataSize()</span>.</p><p>New parameter for the <span class="term">CreateFullBackup() </span>and <span class="term">CreateDifferentialBackup()</span> manager methods of the binary data storage: <span class="term">UniversalDateUntilWhichPerformClearing</span>.</p><p>New feature: the standard <span class="interface">Binary data storage management</span> function now displays the information about the binary data storage and has tools to clear the storage of deleted data.</p></td><td>These features were not provided.</td><td>Advanced administration features of the binary data storage.</td></tr><tr title="Версия 8.3.24" class="tag_47 tag_13"><td><a name="40f33a00-91ab-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>Now the standalone server supports binary data storages.<p>New<span class="term"> --binary-storage-data </span>command is implemented for the command line of the standalone server startup.</p></td><td>This feature was not provided.</td><td>Now the standalone server allows using binary data storages.</td></tr><tr title="Версия 8.3.24" class="tag_61"><td><a name="27b2034c-9311-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 61); return false;">Using the clipboard</a>.<br></td><td>Now you can use the operating system clipboard. New global context property: <span class="term">ClipboardTools</span>.<p>New event handlers for the application module and the client application form module:<span class="term"> OnPasteFromClipboard</span>.</p><p>New methods for the <span class="term">FileRef </span>object<span class="term">: GetAsStringAsync() </span>and <span class="term">GetAsBinaryDataAsync().</span></p><p>The clipboard is unavailable on mobile devices.</p></td><td>This feature was not provided.</td><td>Now you can use the clipboard of the current operating system.</td></tr><tr title="Версия 8.3.24" class="tag_10 tag_38"><td><a name="f079746e-9328-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Now you can restructure tables of infobase configuration extensions while verifying and repairing the infobase:<p>New item in the <span class="interface">Verify and repair infobase</span> dialog box: <span class="interface">Restructuring of configuration extension tables</span>.
New parameter for the<span class="term"> /IBCheckAndRepair </span>command of Designer batch mode: <span class="term">RebuildConfigurationExtensions</span>.
If the verification process detects that there is no extension table, such table will be created if the verification and repair mode is enabled.</p></td><td>This feature was not provided.</td><td>Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features.</td></tr><tr title="Версия 8.3.24" class="tag_10 tag_38"><td><a name="e8e6a508-9329-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Now you can verify and repair an infobase in specific separated infobase areas:<p>New capabilities in the <span class="interface">Verify and repair infobase</span> dialog box: you can specify data areas for running verification and repair.
New parameter for the<span class="term"> /IBCheckAndRepair </span>command of Designer batch mode: <span class="term">-Z</span>. It allows you to specify data areas for running verification and repair.
If no separators are specified, the verification and repair operation is performed for the entire infobase.
</p></td><td>This feature was not provided.</td><td>Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features.</td></tr><tr title="Версия 8.3.24" class="tag_10 tag_38"><td><a name="9ba77c38-932a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>If only the <span class="interface">Check logical integrity of configuration extensions</span> or <span class="interface">Restructuring of configuration extension tables</span> parameters are selected when you configure infobase verification and repair, exclusive mode for the entire infobase is not required and not set.<p>The following locks are set for each processed area:</p><ul><li>Separated lock if only verification is selected.</li><li>Exceptional lock if the verification and repair operation is selected, and it is required to repair the infobase.</li></ul><p>An area lock error does not interrupt the entire verification and repair process but moves it to the next data area.</p></td><td>This feature was not provided.</td><td>Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features.</td></tr><tr title="Версия 8.3.24" class="tag_4"><td><a name="354adc6e-932b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can exchange files with WhatsApp if the collaboration system is integrated with it.</td><td>This feature was not provided.</td><td>Advanced features for integration with instant messaging systems.</td></tr><tr title="Версия 8.3.24" class="tag_38 tag_62"><td><a name="d02dcd5a-9591-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>Now you can create your own external data sources:<ul><li>Tables and fields for external data source tables.</li><li>External data source functions.</li><li>Dimension tables, dimension table fields, dimensions, and resources of external data source cubes.</li></ul><p>Now you can adopt external data sources. When several configuration extensions change adopted object properties, object property values are obtained from the last extension in the list.</p></td><td>This feature was not provided.</td><td>Advanced configuration extension features.</td></tr><tr title="Версия 8.3.24" class="tag_20"><td><a name="1a7f679a-959b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New features for a conditional breakpoint when debugging applications:<ul><li>Enable or disable a breakpoint using the checkbox in the dialog box of breakpoint condition settings.</li><li>Open the dialog box by pressing <span class="interface">Ctrl+F9</span>.</li><li>Perform more actions in the field for editing the breakpoint triggering condition.</li><li>Specify that the breakpoint must be triggered when called from a particular configuration method. You can specify the method name using regular expressions. The regular expression dialect is similar to the dialect of regular expressions in 1C:Enterprise language.</li><li>Set a breakpoint triggering condition based on the number of hits in a text line in 1C:Enterprise language.</li><li>Specify actions to perform when hitting a breakpoint:</li><ul><li>Display a message in the message window.</li><li>Display an expression evaluation result.</li><li>Display the call stack of 1C:Enterprise language.</li><li>Display the number of hits in the breakpoint.</li><li>For all the listed actions, you can choose not to stop after performing an action but to continue running 1C:Enterprise language. </li></ul></ul><p>Enable a disabled breakpoint by pressing <span class="interface">F9 </span>on it. </p><p>Move a breakpoint within the module using the mouse and the keyboard.</p><p>Copy and insert a breakpoint using the clipboard.</p></td><td>Previously the dialog box for editing conditional breakpoints contained only a simple string for editing the breakpoint condition.<p>When you pressed <span class="interface">F9 </span>on a disabled breakpoint, the breakpoint was deleted and all the settings were lost.</p><p>You were unable to transfer breakpoints using the keyboard, the mouse, and the clipboard.</p></td><td>Simplified application debugging. Extended breakpoint capabilities. Enhanced setting of conditions for conditional breakpoints.</td></tr><tr title="Версия 8.3.24" class="compat tag_63 tag_25 tag_1"><td><a name="5b6c711a-95a6-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Changed the display of pie and doughnut charts, including 3D charts. Now you can manage the display of pie and doughnut charts. When rendering pie and doughnut charts, the value of the <span class="term">LabelLocation </span>property is applied.<p>New properties for the <span class="term">Chart </span>object: <span class="term">BeginAngle</span>, <span class="term">EndAngle</span>, and <span class="term">Chart3DDepth</span>.</p><p>For the <span class="term">Chart.LabelLocation</span> property, the default value will be <span class="term">Auto</span>.</p><p>New properties for the <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroupOutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance</span> data composition system objects: <span class="term">ChartType.BeginAngle</span>, <span class="term">ChartType.EndAngle</span>, and <span class="term">ChartType.Chart3DDepth</span>.</p><p>This change is not implemented in version 8.3.23 compatibility mode.</p></td><td>These features were not provided.<p>For the <span class="term">Chart.LabelLocation </span>property, the default value was <span class="term">Edge</span>.</p></td><td>Advanced display features for pie charts.</td></tr><tr title="Версия 8.3.24" class="tag_64"><td><a name="9029ee8a-0c08-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New pictures in the picture library:<ul><li><span class="term">FormattedString</span></li></ul></td><td>The listed pictures were not available in the picture library.</td><td>The picture library is upgraded.</td></tr></table><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5ba3-7d2f-11ed-963f-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.24" class="tag_12"><td><a name="a4ff667e-91b4-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>Now you can manage the history usage settings of the standard<span class="interface"> Data change history </span>function.</td><td>This feature was not provided.</td><td>You can manage the data change history directly from the standard function without any third-party tools.</td></tr><tr title="Версия 8.3.24" class="tag_4"><td><a name="f3e3bd78-9315-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can mark messages as read in collaboration system conversations. You can see the mark in a thin client, a thick client, and a web client. In a mobile client, the mark is not displayed. However, other client applications show that a message is read in the mobile client.<p>You can see the read status in context conversations where the number of message senders and recipients is less than 100. You can also see the read status in noncontext conversations where:</p><ul><li>There is no "All users" participant.</li><li>There are other participants besides you.</li><li>Total number of conversation participants is less than 100.</li></ul></td><td>This feature was not provided.</td><td>Collaboration system conversations are now more user-friendly.</td></tr><tr title="Версия 8.3.24" class="tag_4"><td><a name="2d6b56bc-9318-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>When you send a message in a noncontext conversation, the conversation moves to the top in all your sessions in the infobase. This change is implemented in the thin, thick, and web clients.</td><td>Previously, the order of your noncontext conversations in several sessions could differ.</td><td>Collaboration system conversations are now more user-friendly.</td></tr><tr title="Версия 8.3.24" class="tag_65"><td><a name="41c8f524-932c-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>Now you can specify how many background jobs must run to perform the initial population of copy tables for the standard function of database copy management. New parameter in the <span class="interface">Database copy parameters </span>form: <span class="interface">Number of filling jobs</span>.</td><td>This feature was not provided.<p>Previously the initial population of copy tables required four background jobs. You could not change this number manually. You could only use 1C:Enterprise language for this purpose.</p></td><td>Now the administrator can manage the volume of the initial population of database copy tables.</td></tr><tr title="Версия 8.3.24" class="tag_17"><td><a name="fef4eac0-9344-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>When you run thin and thick client applications, you can now generate a technological log using the video module of the collaboration system. You can also generate abnormal termination dumps for the video module. You can configure it using the standard file for the technological log setup: <span class="interface">logcfg.xml</span>.<p>If you use 32-bit 1C:Enterprise running on a 64-bit operating system, you cannot use an external application to create abnormal termination dumps. Abnormal termination of the video module is dumped during the process.</p><p>New technological log events: <span class="term">&lt;VIDEOCALL&gt;</span>,<span class="term"> &lt;VIDEOCONN&gt;</span>, <span class="term">&lt;VIDEOSTATS&gt;</span>.</p></td><td>This feature was not provided.</td><td>Now you can send the information to the technical support easier and faster when you face any issues with the video module of the collaboration system.</td></tr><tr title="Версия 8.3.24" class="tag_10"><td><a name="6f401d07-9348-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now installed platform versions can be deleted automatically. They will be deleted with a separate process with a lower priority. The deletion process will not affect your operations. You can set up the parameters to automatically delete versions in the dialog box of the interactive launcher setup.<p>Now you can specify one or several system versions that must not be automatically deleted.</p><p>New parameters for the <span class="interface">1cestart.cfg </span>and <span class="interface">1cescmn.cfg </span>configuration files: <span class="term">AutoUninstall</span>, <span class="term">AutoUninstallVersionsAfter</span>, <span class="term">DontUninstallVersion</span>.</p></td><td>This feature was not provided.<p>Previously you had to delete unused versions manually or write batch files to delete them.</p></td><td>Simplified system administration in terms of deleting 1C:Enterprise versions that you no longer use.</td></tr><tr title="Версия 8.3.24" class="tag_28"><td><a name="26149299-966f-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>When you perform some long-running operations in the web client, the mouse cursor switches from the main mode to "busy".</td><td>In the web client, the cursor was always in the main mode.</td><td>The web client is now more user-friendly.</td></tr><tr title="Версия 8.3.24" class="tag_38 tag_26"><td><a name="cac63ef9-966f-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Now it is faster to receive a template that was extended with multiple configuration extensions for the first time. The extended template is cached for further use.<p>The cache is stored until you change the template to be extended or the extension that contains an improvement for this template.</p></td><td>Previously, the first receipt of a template extended with multiple configuration extensions took more time.</td><td>Templates that are extended with multiple configuration extensions are now faster and easier to use.</td></tr><tr title="Версия 8.3.24" class="tag_4"><td><a name="e482f875-f19d-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Upgrade: identification and display of the speaker in the videoconference window is updated. Speaker display and videoconference window behavior in various client applications are unified.</td><td>Previously, speaker identification and videoconference window display were different and varied in different client applications.</td><td>Improved videoconference window interface. It became easier to understand what user is talking or transmitting noise through the microphone at the moment.</td></tr></table><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5ba4-7d2f-11ed-963f-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.24" class="tag_7"><td><a name="42013594-923d-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Initial population of a database copy for metadata objects with tables is now faster.</td><td>Initial population of a database copy for metadata objects with tables took more time.</td><td>Initial population of a database copy for metadata objects with tables is now faster.</td></tr><tr title="Версия 8.3.24" class="tag_6"><td><a name="4072b810-9340-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Server cluster computers (network, RAM, and CPUs) have become less loaded when there are many users. The server cluster is now more stable.</td><td>When there were many users, the server cluster consumed more RAM, CPUs, and network connections.</td><td>Improved server cluster stability in configurations with a large number of users.</td></tr><tr title="Версия 8.3.24" class="tag_6 tag_10"><td><a name="cbf70b3f-9346-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Optimized logical and referential integrity check in client/server mode when verifying and repairing infobases.<p>New parameter for the <span class="term">/IBCheckAndRepair </span>command of Designer batch mode: <span class="term">-JobsCount</span>. It identifies the number of system background jobs used for infobase verification and repair.</p></td><td>Infobase was verified and repaired sequentially by infobase tables.</td><td>Infobase verification and repair now take less time.</td></tr><tr title="Версия 8.3.24" class="tag_4"><td><a name="636fc943-9347-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Improved sound quality during video calls.</td><td>Sound quality during video calls was worse.</td><td>Improved sound quality during video calls.</td></tr><tr title="Версия 8.3.24" class="tag_21"><td><a name="65876e33-9349-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Improved relevance of full-text search results.<p>For this upgrade to take effect, clear the full-text search index and recreate it on platform version 8.3.24.</p><p>1C:Enterprise platform versions 8.3.23 and earlier will clear the index if it was built by platform version 8.3.24.</p></td><td>Previously, full-text search returned results ordered by a set of criteria that ensured low result relevance.</td><td>Improved relevance of full-text search results.</td></tr><tr title="Версия 8.3.24" class="tag_21"><td><a name="297740d3-934a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Data indexing by full-text search now takes less time. The size of intermediate files used for indexing is reduced.</td><td>Data indexing for full-text search took more time and required more space for temporary files used for indexing.</td><td>Data indexing for full-text search takes less time.</td></tr></table><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5ba5-7d2f-11ed-963f-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.24" class="tag_19"><td><a name="4ef0549e-9587-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Now you can terminate unnecessary sessions of a user and continue the current session after user authentication. You can do it if there are other sessions of this user in this infobase after authentication and you cannot start a new session without closing them.<p>This feature is implemented after authentication is fully completed in the following situations:</p><ul><li>An error occurred when establishing exclusive access to an infobase or a data area.</li><li>There are not enough client licenses.</li><li>Starting a session is denied by the external session management service.</li></ul></td><td>This feature was not provided.</td><td>Simplified solution of issues that arise during user authentication when limiting the number of sessions after an unnecessary application freezes, crashes, or is unavailable.</td></tr><tr title="Версия 8.3.24" class="tag_27"><td><a name="7d7990df-05f0-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is 2.17.</td><td>The format version of configuration dump to XML files was 2.16.</td><td>Configuration dump to XML files supports new platform features.</td></tr></table><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5ba6-7d2f-11ed-963f-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.24" class="tag_15"><td><a name="777514ba-9276-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>1C:Enterprise installer for Linux is supplied in a zip archive. The archive includes the <span class="interface">installAsRoot </span>application, which allows you to easily perform installation on behalf of the superuser (<span class="interface">root</span>).<p>During the installation, an attempt is made to install all the Linux components necessary for the platform to run. If the attempt fails, the batch manager message is displayed as an error message.</p><p>During the installation, only one shortcut to the interactive launcher is created. To create other shortcuts, use the <span class="interface">Create shortcuts </span>launcher option or the <span class="term">desktops_icons</span> parameter of the batch system installation.</p><p>During the installation, a platform uninstaller shortcut is created.</p><p>Shortcut names created by the installer became shorter and better reflect the actions the shortcuts perform. Shortcut names are now displayed in several lines.</p></td><td>Previously it was more complicated to install 1C:Enterprise on Linux.<p>The installer did not attempt to install the Linux components necessary for the system to run.</p><p>Error messages displayed during the installation were not clear enough.</p></td><td>Simplified installation, startup, and uninstallation of 1C:Enterprise on a computer running Linux.</td></tr><tr title="Версия 8.3.24" class="tag_47"><td><a name="ca31f2cc-9278-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>During database configuration update, the standalone server outputs the ID of the new infobase generation to the standard output stream.<p>New feature: mode of partial import of external properties for selective metadata object import from xml files. In this mode, you do not need to import metadata objects these properties belong to. You can also import form modules without importing the forms. New partial parameter for the following commands:</p><ul><li><span class="term">config load-config-from-files </span>command of the Designer agent and the SSH gateway of the standalone server.</li><li><span class="term">/LoadConfigFromFiles </span>command of Designer batch mode.</li><li><span class="term">infobase config import </span>command of the standalone server management utility (<span class="interface">ibcmd</span>).</li></ul></td><td>This feature was not provided.</td><td>Database configuration update by a standalone server is now faster in some scenarios.</td></tr><tr title="Версия 8.3.24" class="compat tag_66 tag_1"><td><a name="b8c2e93e-9280-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 66); return false;">Navigation links</a>.<br></td><td>URLs generated with the <span class="term">GetInfoBaseURL() </span>method in the URL receipt dialog box with the selected <span class="interface">External link </span>checkbox contain separators that you can use in the current session of the separated infobase. If you receive a link in the web client or thin client connected via the web server, the URL will contain separators that do not generate the infobase address. You can specify the separators similarly to the <span class="term">Z </span>command-line option of the client application startup.<p>When you start the client application with the <span class="term">URL </span>parameter, the application searches for the client application based on the separator values specified in the URL. Similar actions are performed when you follow an external URL from the <span class="interface">Go to link </span>dialog box, from the global search string, and using the <span class="term">GoToURL() </span>method.</p><p>This change is not implemented in version 8.3.23 compatibility mode.</p></td><td>URLs generated with the <span class="term">GetInfoBaseURL() </span>method in the URL receipt dialog box with the selected <span class="interface">External link </span>checkbox did not contain values of the current session separators for the separated infobase.</td><td>When you follow an external URL generated in a separated infobase, the values of the separators that were used in the session where the URL was received are considered. You will open objects in the same data area where you received the URL.</td></tr><tr title="Версия 8.3.24" class="compat tag_43 tag_1"><td><a name="7453e76e-930a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Now you can exclude fields that are of the flexible type and contain more than 100 types from the list of dynamic list fields that can be used to order the list.<p>This upgrade is ignored in 8.3.23 version compatibility mode.</p></td><td>The list of fields that you can use to order a dynamic list was not limited by the size of the flexible type of a dynamic list field.</td><td>Now when you configure a dynamic list, you are less likely to create a sorting that will slow down the dynamic list operation or lead to the list malfunction. It can happen due to a DBMS error that occurs when you try to display the list.</td></tr><tr title="Версия 8.3.24" class="tag_64 tag_59 tag_60"><td><a name="47e41294-930e-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br></td><td>Spreadsheet documents now support a formatted string in cells and pictures. You can export such spreadsheet documents to the following formats:<ul><li>Microsoft Office OpenXML (Microsoft Word 2007 and later) and HTML in full.</li><li>Microsoft Office OpenXML Spreadsheet (Microsoft Excel 2007 and later), OpenDocument Spreadsheet (*.ods), and PDF with some limitations:</li><ul><li>Exporting pictures and hyperlinks embedded in formatted strings is not supported.</li><li>Background color export is not supported.</li><li>Font color export to XLS (Microsoft Excel 95-2003) is not supported.</li></ul></ul><p>In the spreadsheet document editor, you can switch between a regular and formatted string. You can edit a formatted string.</p><p>New event for a spreadsheet document field: <span class="term">URLProcessing</span>.</p><p>The <span class="term">Text </span>property of the <span class="term">SpreadsheetDocumentRange </span>and <span class="term">SpreadsheetDocumentDrawing </span>objects can be of the <span class="term">String </span>or <span class="term">FormattedString </span>type.</p><p>The mobile platform does not support the formatted string.</p></td><td>This feature was not provided.</td><td>Now you can improve spreadsheet document appearance.</td></tr><tr title="Версия 8.3.24" class="tag_67"><td><a name="d43b8d16-933d-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>Now you can set up the configuration repository so that it is required to specify a password when creating a user.<p>The repository creation assistant now has a page with password requirements: minimum password length and password complexity check. You can edit these parameters in the repository administration dialog box. If you specify the minimum password length as 0, it will be possible to create users without entering a password.</p><p>In the repository user list, you can see a column with all user passwords.</p><p>New parameters for the <span class="term">/ConfigurationRepositoryCreate </span>command of Designer batch mode: <span class="term">-MinPasswordLength </span>and <span class="term">-CheckPasswordComplexity</span>.</p><p>New parameters for the global <span class="interface">cfgrepo.conf </span>settings file of the configuration repository: <span class="term">cfgrepo.users.minPasswordLength </span>and <span class="term">cfgrepo.users.checkPasswordComplexity</span>.</p><p>It is recommended that administrators of configuration repositories analyze user lists in repositories they administer and set passwords for all users.</p></td><td>You were unable to set up the configuration repository so that it required a password when creating a user.</td><td>Now it is less likely that any repository user without a password changes the configuration located in the repository.</td></tr><tr title="Версия 8.3.24" class="tag_68"><td><a name="8acfd828-958b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>Changes made in the <span class="term">OnWrite() </span>event handlers are not included in a data version to save.</td><td>A data version that was saved to the history included changes made in the <span class="term">OnWrite()</span> event handlers.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.24" class="tag_8"><td><a name="7938b0e5-9666-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>Now it is easier to initialize the cryptography manager. You can use the cryptography manager wizard where you need to select only the interactive mode. Parameters for each operation are identified by the operation context.<p>Now you can specify encryption, hash, and signature algorithms that you will use to perform an operation using the OID algorithm. You can still specify algorithms by naming them but OID is better for clear identification.</p><p>Now you can set the priority for hash and encryption algorithms. New properties for the cryptography manager: <span class="term">HashAlgorithmDefinition </span>and <span class="term">EncryptAlgorithmDefinition</span>.</p><p>Now you can receive certificates not only from encrypted or signed data but also from an arbitrary certificate storage. New methods for the cryptography manager: <span class="term">GetCertificates()</span> and <span class="term">GetCertificatesAsync()</span>. Do not use the following methods as they are outdated: <span class="term">GetCertificatesFromSignature()</span>, <span class="term">GetCertificatesFromSignatureAsync()</span>, and <span class="term">BeginGettingCertificatesFromSignature()</span>.</p><p>Now you can search for a key container for the used certificate on the local computer. New methods for the cryptography manager: <span class="term">FindKeyContainer()</span> and <span class="term">FindKeyContainerAsync()</span>.</p><p>Now you can specify a certificate and an access password to the private key that can be used to decrypt data. New parameters for the <span class="term">Decrypt()</span>, <span class="term">DecryptAsync()</span>, and <span class="term">BeginDecrypting()</span> methods: <span class="term">Certificate </span>and <span class="term">PrivateKeyAccessPassword</span>.</p><p>New property: <span class="term">CryptoModuleInformation.CryptoModuleType</span>.</p></td><td>Previously, you had to specify a cryptography module name, type, and path when initializing the cryptography manager.<p>You were able to specify algorithms used for an operation only by the name.</p><p>You were unable to specify the priority for hash and encryption algorithms. Algorithms specified in the cryptography manager methods could be ignored when performing an operation.</p><p>You were unable to receive a list of certificates from encrypted data. You were able to receive the list only from the data signature (the <span class="term">GetCertificatesFromSignature()</span>, <span class="term">GetCertificatesFromSignatureAsync()</span>, and <span class="term">BeginGettingCertificatesFromSignature() </span>cryptography manager methods).</p><p>You were unable to check whether there was a key container for the used certificate on the computer.</p><p>When you decrypted data, you could specify only one recipient of decrypted data.</p></td><td>Simplified operations with the cryptography manager in main scenarios.</td></tr><tr title="Версия 8.3.24" class="tag_47"><td><a name="589d6f93-052e-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>Removed the following standalone server parameters:<ul><li>The <span class="term">--debug-server-password</span> parameter of the <span class="interface">ibsrvr </span>utility.</li><li>The <span class="term">password </span>parameter of the<span class="term"> debug - server </span>section of the standalone server configuration file.</li></ul><p>If you specify the deleted parameters, it will not cause an error. The parameters are ignored.</p></td><td>Previously the standalone server parameters mistakenly specified that users could set a password to access the debug server on the standalone server. The specified password was never used.</td><td>Eliminated the error in the standalone server parameters.</td></tr></table><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5ba7-7d2f-11ed-963f-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.24" class="tag_0"><td><a name="87008dc0-c3e9-11ed-963f-0050569f678a"></a>English name of the <span class="term">NotifyDescription </span>parameter in 1C:Enterprise language methods.</td><td><ul><li><span class="term">NotifyDescription</span>.</li></ul></td><td><ul><li><span class="term">CallbackDescription</span>.</li></ul></td></tr></table><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5ba8-7d2f-11ed-963f-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.24" class="tag_30 tag_32"><td><a name="99aeda9e-9264-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Now compatibility mode processing in the mobile platform corresponds to the similar platform behavior on a personal computer.<p>Designer exports information about the configuration compatibility mode to the <span class="interface">1cema.xml </span>and <span class="interface">1cemca.xml </span>files.</p><p>The mobile application builder considers the compatibility mode when building mobile applications. If the configuration compatibility mode does not correspond to the mobile version used to build the mobile application, the build will be completed with errors.</p></td><td>Previously, the compatibility mode depended on the version of the mobile platform where you initially created the infobase or updated the configuration.<p>The mobile application builder did not check the compatibility mode between the configuration and the mobile platform used to build the mobile application.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.24" class="tag_30 tag_31"><td><a name="91a365f6-9281-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Mobile platform and mobile client with standalone mode now support type collections.</td><td>This feature was not provided.</td><td>Advanced 1C:Enterprise mobile platform features.</td></tr><tr title="Версия 8.3.24" class="tag_30 tag_31 tag_48"><td><a name="c4e14927-934a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The mobile platform and the platform for a personal computer are now available on the server for the following objects: <span class="term">MultimediaData</span>, <span class="term">DocumentScanningQualityParameters</span>, and <span class="term">DocumentScanningPage</span>.</td><td>This feature was not provided.</td><td>Simplified operations with documents that are scanned not to be sent to the recognition service but to be saved to the infobase.</td></tr><tr title="Версия 8.3.24" class="tag_30 tag_31 tag_32 tag_48"><td><a name="a4e31f01-b669-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Now the mobile version of 1C:Enterprise supports Huawei Mobile Services (HMS). You can use the map and get an address by coordinates and vice versa, use geolocation zones, notifications, ads, and in-app purchases.<p>New system enumeration value: <span class="term">DeliverableNotificationSubscriberType.HPK</span>. New parameter for the <span class="term">GetAccessToken() </span>method of the manager for sending deliverable notifications: <span class="term">SubscriberType</span>. The method contains three parameters now. The <span class="term">GetAccessToken() </span>method with two parameters is now outdated.</p><p>New system enumeration value: <span class="term">InAppPurchaseService.HuaweiInAppPurchase</span>.</p><p>In the mobile application builder, you can now specify which services the built mobile application will support (including the ability to disable both services). If both service sets are used on a mobile device, the Google service set has the priority (you cannot set the priority). Now you can disable both service sets if the built application does not use the mobile service features (the built application size will decrease). You cannot publish the built application to the Huawei AppGallery store from the mobile application builder.</p></td><td>Previously, Huawei Mobile Services (HMS) were not supported in the mobile version of 1C:Enterprise. You were unable to use the full mobile version capabilities on Huawei devices.</td><td>More mobile services are now supported.</td></tr><tr title="Версия 8.3.24" class="tag_31 tag_9"><td><a name="c293cc21-b66b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 9); return false;">Speech recognition</a>.<br></td><td>Now you can use speech recognition in the mobile client (including in standalone mode). Speech recognition is not supported on mobile devices. Server methods of speech recognition are not supported in the mobile application server and the mobile standalone server.<p>New functionality: <span class="term">SpeechToText</span>. If this functionality is not required in the application you build, an attempt to access the speech recognition tools in the built application will cause a runtime exception.</p></td><td>Speech recognition was not supported in the mobile client.</td><td>Advanced 1C:Enterprise mobile client features.</td></tr><tr title="Версия 8.3.24" class="tag_30 tag_31 tag_29"><td><a name="b448c3b5-e018-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The mobile version of 1C:Enterprise now supports Android 13. The mobile version of 1C:Enterprise no longer supports Android 4.4. The mobile version of 1C:Enterprise supports Android versions 5.0 - 13.<p>To upload a mobile application to the Google Play store, build a mobile application using the mobile version 8.3.24.40 or later.</p><p>When you run a mobile application on Android 13 and later versions:</p><ul><li>The <span class="interface">Notification position</span> permission will be used. The permission describes why the user needs notifications in the mobile device shade. This permission is used when geofences, notifications, video calls, and audio recording are applied.</li><li>To access the audio library and the picture and video library, install the appropriate functionality similar to iOS. If you use the previous Android versions, the <span class="interface">Audio playback and vibration</span> functionality will be used.</li></ul></td><td>Previously the mobile 1C:Enterprise version supported Android versions 4.4-12.<p>After November 1, 2023, you will not be able to upload mobile applications built using mobile versions earlier than version 8.3.24.40 to the Google Play store.</p></td><td>Now the mobile 1C:Enterprise version supports the latest Android versions.</td></tr><tr title="Версия 8.3.24" class="tag_48"><td><a name="ed137f87-e366-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The mobile application no longer requires a user permission to access the application document directory.<p>If the <span class="interface">Access to all files</span> functionality is disabled, you will see a message that the required functionality is disabled when you try to access files outside the data directory.</p><p>New functionality: <span class="interface">Geofences</span>. It manages operations with geofences.</p></td><td>When you started an application for the first time, the system requested access to the application's document directory.<p>When you tried to access a file outside the application's document directory, a file access error was generated.</p><p>Operations with geofences depended on the <span class="interface">Geolocation in background</span> functionality.</p></td><td>Eliminated unexpected system behavior.<p>The collaboration system behavior is more logical.</p></td></tr><tr title="Версия 8.3.24" class="tag_30 tag_31 tag_48"><td><a name="10e4c561-fe03-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>On the mobile version, you can get files that the user shared from other applications on a mobile device. When you set up the feature, you can specify that the mobile application will process some specific file extensions or all extensions.<p>New global context property: <span class="term">LaunchShareRequestData</span>. New event handler of the application module: <span class="term">IncomingShareRequestCommandGenerateProcessing()</span>. New properties for the <span class="term">MobileApplicationFunctionalities </span>system enumeration: <span class="term">IncomingShareRequests </span>and <span class="term">AllIncomingShareRequestsTypesProcessing</span>.</p></td><td>This feature was not provided.</td><td>In a 1C:Enterprise-based mobile application, you can now receive files that were shared from other applications using a standard feature of the respective mobile operating system.</td></tr></table><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5bab-7d2f-11ed-963f-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.24" class="tag_0"><a name="5a79977f-0c0b-11ee-963f-0050569f678a"></a>When you print a sales invoice, a formatted string is provided in the spreadsheet document. In the print form header, the amount in words is shown in bold.<p>
</p></li><li title="Версия 8.3.24" class="tag_0"><a name="11d46e26-0c0c-11ee-963f-0050569f678a"></a>New way to apply the clipboard:<ul><li>In the <span class="term">Products </span>catalog item form, you can insert a picture from the clipboard. The inserted picture replaces the current image of the item.</li><li>New command in the <span class="term">Order </span>document form. With the command, you can copy the order number and the goods specified in the document to the clipboard.</li></ul></li><li title="Версия 8.3.24" class="tag_0"><a name="ac059582-9988-11ee-963f-0050569f678a"></a>New example of processing a file shared with a mobile application. New application module handler: <span class="term">IncomingShareRequestCommandGenerateProcessing()</span>. It implements the <span class="interface">Add file... </span>menu item.</li></ul><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5bac-7d2f-11ed-963f-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.24" class="compat tag_69 tag_1"><td><a name="34de9fc3-172d-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>If the <span class="term">Find() </span>table method cannot find the search string and the list of search columns has only a <span class="term">LineNumber </span>column, the search in other columns is not executed.<p>Analyze the method and eliminate possible unexpected behavior.</p><p>This upgrade is ignored in 8.3.23 version compatibility mode.</p></td><td>If the <span class="term">Find() </span>table method could not find the search string and the list of search columns had only a <span class="term">LineNumber </span>column, the search was executed in all table columns.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.24" class="tag_60"><td><a name="40d18310-2146-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br></td><td>New feature: when you fill a spreadsheet document, formatted strings in cells with the <span class="interface">Template </span>fill type are supported.<p>When you replace a parameter name with an actual value, the formatting of the resulting text is determined by the first character of the parameter name, and pictures and links inside the parameter name are deleted. Other operations with templates do not change.</p></td><td>When you filled a spreadsheet document, formatted strings in cells with the <span class="interface">Template </span>fill type were not supported.</td><td>Expanded support for formatted strings in a spreadsheet document.</td></tr><tr title="Версия 8.3.24" class="tag_70"><td><a name="09ec6248-629b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>Now you can specify the automatic bitness option of the client application to be started in the settings of the dialog box of client application startup and infobase parameters on Windows.<p>If a 32-bit application is running for the infobase, the distribution package of the 32-bit application will be downloaded upon automatic client application update.</p></td><td>Previously, when a client application was automatically updated, an application whose bitness matched the used operating system bitness was downloaded. The bitness of the running client application was ignored during the update.</td><td>Simplified automatic client application update when a 32-bit client application is used on 64-bit Windows (for example, because the client application uses add-ins that exist only in the 32-bit version).</td></tr><tr title="Версия 8.3.24" class="tag_20"><td><a name="8abe27b1-6c0c-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>To copy breakpoint settings to the clipboard, press <span class="interface">Ctrl+Alt+K</span>.<p>In previous platform versions, pressing <span class="interface">Ctrl+Alt+C</span> opened the call stack window.</p></td><td>Pressing <span class="interface">Ctrl+Alt+C</span> copied breakpoint settings to the clipboard.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.24" class="tag_32"><td><a name="1fd09043-74ae-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Now you can export keys associated with the Google Play and Huawei AppGallery application stores in the mobile application builder. The feature is implemented as a dialog box that you can call from the dialog box for editing provider parameters and from the dialog box for editing a mobile application group.<p>The following information is exported:</p><ul><li>Application's private signature key (for Google Play, specify the encryption key from the developer console of the application store).</li><li>Private key and the application signature certificate (for both stores).</li><li>Certificate of the application upload key (for both stores).</li></ul></td><td>Previously, you could only export keys for the Google Play store in a format that was no longer supported by the store.</td><td>You can continue using the Google Play store as the store changed the encryption procedure of the signature key.<p>You can upload AAB files to the Huawei AppGallery application store.</p></td></tr><tr title="Версия 8.3.24" class="tag_12"><td><a name="4464e024-7a4c-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>Mobile 1C:Enterprise version 8.3.24 is now supported in the mobile application builder. Now you can use the builder to build Android-based mobile applications that use Huawei mobile services.</td><td>These features were not provided.</td><td>Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.</td></tr><tr title="Версия 8.3.24" class="tag_4"><td><a name="8691c45a-7d4b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New features for the external user website and the chat on the website:<ul><li>Continue your video call on another device.</li><li>Automatic reconnection in a video call when the connection is lost or deteriorated.</li></ul><p>Improved the video call interface.</p></td><td>These features were not provided.</td><td>Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.</td></tr><tr title="Версия 8.3.24" class="tag_19 tag_29"><td><a name="5272981f-b135-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Postgres Pro DBMS version 11.22.1 of the following products:<ul><li>Postgres Pro 1C</li><li>Postgres Pro Standard</li><li>Postgres Pro Enterprise.</li></ul><p>DBMS version bitness: x86-64.</p><p>The products are supported in 1C:Enterprise version 8.3.17 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.24" class="tag_19 tag_29"><td><a name="7c2b74cd-b135-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Postgres Pro DBMS version 12.17.1 of the following products:<ul><li>Postgres Pro 1C</li><li>Postgres Pro Standard</li><li>Postgres Pro Enterprise.</li></ul><p>DBMS version bitness: x86-64.</p><p>The products are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.24" class="tag_19 tag_29"><td><a name="a294e533-b135-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Postgres Pro DBMS version 13.13.1 of the following products:<ul><li>Postgres Pro 1C</li><li>Postgres Pro Standard</li><li>Postgres Pro Enterprise</li><li>Postgres Pro Enterprise certified.</li></ul><p>DBMS version bitness: x86-64.</p><p>The products are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.24" class="tag_19 tag_29"><td><a name="c5d760d3-b135-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Postgres Pro DBMS version 14.10.1 of the following products:<ul><li>Postgres Pro 1C</li><li>Postgres Pro Standard</li><li>Postgres Pro Enterprise</li><li>Postgres Pro Enterprise certified.</li></ul><p>DBMS version bitness: x86-64.</p><p>The products are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.24" class="tag_19 tag_29"><td><a name="da3b9955-b135-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Postgres Pro DBMS version 15.5.1 of the following products:<ul><li>Postgres Pro 1C</li><li>Postgres Pro Standard</li><li>Postgres Pro Enterprise.</li></ul><p>DBMS version bitness: x86-64.</p><p>The products are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.24" class="tag_25"><td><a name="30ee847b-b138-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The time required to open the data composition schema is reduced if there are many predefined items in the chart of calculation types.</td><td>Previously, opening the data composition schema took a long time if there were many predefined items in the chart of calculation types.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.24" class="tag_15"><td><a name="8482ce63-6e51-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>New feature: the WebKit2 library is used to manage HTML objects in Linux client applications. The WebKit2 library is not included in the platform. Instead, a library included in the used operating system is used. The evince library is used to preview HTML document fields. If the libraries are not installed, they will be installed from the repositories of the used operating system during the 1C:Enterprise installation.<p>The WebKit1 library is no longer used and is not included in 1C:Enterprise.</p></td><td>Previously, the WebKit1 library included in the 1C:Enterprise distribution package was used to manage HTML objects in Linux client applications.</td><td>A more modern library is used to manage HTML objects.</td></tr><tr title="Версия 8.3.24" class="tag_71 tag_72"><td><a name="28ff1dfa-e128-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 71); return false;">Analytics system</a>.<br><a href="#" onclick="onTagClick(this, 72); return false;">Analytics - sources</a>.<br></td><td>Now you can manage the report execution location when building the report, similar to the 1C:Enterprise <span class="term">R</span><span class="term">equest</span> object. You can set up the following parameters: <span class="interface">Database copy usage</span>, <span class="interface">Data relevance</span>, and <span class="interface">Relevance time</span>.</td><td>This feature was not provided.</td><td>Advanced management of report execution location in 1C:Analytics client application.</td></tr><tr title="Версия 8.3.24" class="tag_38"><td><a name="bf3f1446-e131-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Now you can access the configuration extension management form in Designer of the base version of 1C:Enterprise (<span class="interface">Main menu - Configuration - Configuration extensions</span>). This form contains interactive extension administration functions. Extensions that can be applied to the base configuration must be signed with the same key as the base configuration. The extension editing functions remain unavailable. You can view the applied extension.</td><td>This feature was not provided.<p>Previously, you could apply and disable extensions only using Designer batch mode.</p></td><td>Advanced administration features of base 1C:Enterprise version.</td></tr><tr title="Версия 8.3.24" class="tag_11"><td><a name="ed0393e4-e137-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>New global context method: <span class="term">CreateAddInObjectAsync()</span>. It allows asynchronous creation of add-in objects.</td><td>This feature was not provided.<p>Previously, you could create add-in objects on the client only using a synchronous constructor. This could lead to errors when using the add-in.</p></td><td>Reduced probability of error if an add-in method is called immediately after creating this add-in object. Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.24" class="tag_73"><td><a name="375773ea-e13d-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>While restructuring the infobase, eliminated deletion of trailing space characters (the Mark, spacing combining character category of the Unicode standard) if the attribute type was not changed upon restructuring. When converting a fixed-length string to a variable-length string, spaces to the right up to the first character other than a space are removed upon restructuring.</td><td>Previously, when restructuring the infobase,trailing space characters (the Mark, spacing combining character category of the Unicode standard) were cut off. When converting a fixed-length string to a variable-length string, not only trailing spaces, but also trailing space characters were removed upon restructuring.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.24" class="tag_30 tag_31 tag_29"><td><a name="4c408f58-f1b7-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following mobile operating systems are supported:<ul><li>for Android: version 14,</li><li>for iOS: versions 15 - 17.</li></ul></td><td>Previously, the following mobile operating systems were supported:<ul><li>for Android: versions 5 - 13,</li><li>for iOS: versions 9 - 14.</li></ul></td><td>Extended list of supported mobile operating systems.</td></tr><tr title="Версия 8.3.24" class="tag_29 tag_15"><td><a name="6704e1b5-fafb-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The following Linux distribution packages are supported:<ul><li>ALT SP 10,</li><li>Debian 12.</li></ul></td><td>The distribution packages were not supported.</td><td>Extended list of supported mobile operating systems.</td></tr><tr title="Версия 8.3.24" class="tag_29 tag_15"><td><a name="a2720743-fafb-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The following Linux distribution packages are no longer supported:<ul><li>Mint 19,</li><li>Ubuntu 18.04 LTS,</li><li>ALT Education 9,</li><li>ALT Workstation 9,</li><li>ALT Workstation K9,</li><li>ALT Server 9.</li></ul></td><td>Previously, 1C:Enterprise supported the following Linux distribution packages:<ul><li>Mint 19,</li><li>Ubuntu 18.04 LTS,</li><li>ALT Education 9,</li><li>ALT Workstation 9,</li><li>ALT Workstation K9,</li><li>ALT Server 9.</li></ul></td><td>Outdated Linux distribution packages are no longer supported.</td></tr><tr title="Версия 8.3.24" class="tag_74"><td><a name="61bc59f1-fb16-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br></td><td>New service addresses to activate the software license using the file. The platform uses new service addresses. Previous service versions are planned to be disabled.<p>The service address has the following format: <span class="interface">https://portal.1c.ru/support/license/license-from-file?lang=LL</span> or <span class="interface">https://portal.1c.eu/support/license/license-from-file?lang=LL</span> (depending on the current settings and the system version), where LL is a two-letter localization language code of the running 1C:Enterprise instance.</p></td><td>Previously, to activate the software license using a file, a service located at <span class="interface">https://users.v8.1c.ru/lc</span> was used.</td><td>A more modern service is used to activate the license using a file.</td></tr><tr title="Версия 8.3.24" class="tag_37"><td><a name="1821ee9e-0d24-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Now you can specify a timeout with 0.01 second accuracy for the <span class="term">HTTPConnection</span>, <span class="term">FTPConnection</span>, and <span class="term">WSProxy </span>objects.</td><td>Previously, a timeout specified as a fractional number was rounded up to the nearest integer number of seconds for the <span class="term">HTTPConnection</span>, <span class="term">FTPConnection</span>, and <span class="term">WSProxy </span>objects.</td><td>You can specify operation timeouts more accurately for Internet services.</td></tr><tr title="Версия 8.3.24" class="tag_8"><td><a name="3d8b5d23-74b0-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>Now you can generate an attached digital signature of the file.<p>1C:Enterprise supports multiple document signatures. The check is performed not only for the first signature, but for all digital signatures of the file.</p><p>You can add and delete certificates to the store of root certificates and intermediate certificate authority certificates.</p><p>When adding an archived timestamp, the <span class="term">ats-hash-index-v3 </span>attribute is added.</p><p>New property for the cryptography manager: <span class="term">IncludeDataInSignature</span>. New methods for the cryptography manager: <span class="term">CheckForDataInSignature()</span>, <span class="term">CheckForDataInSignatureAsync()</span>, <span class="term">GetDataFromSignature()</span>, and <span class="term">GetDataFromSignatureAsync()</span>. Now you can use an attached digital signature in the <span class="term">VerifySignature()</span> and <span class="term">VerifySignatureAsync()</span> methods. New property: <span class="term">CryptoSignature.Data</span>.</p></td><td>Previously, 1C:Enterprise supported only detached digital file signature.<p>When checking a digital signature, only the first digital signature was checked.</p><p>You could not add and delete certificates to the store of root certificates and intermediate certificate authority certificates.</p><p>When adding an archived timestamp, the <span class="term">ats-hash-index </span>attribute was not added.</p></td><td>Advanced cryptography features.</td></tr><tr title="Версия 8.3.24" class="tag_19 tag_29"><td><a name="24772266-2344-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Tantor SE 1C DBMS version 15.6.1.<p>Supported processors: ARM64 and x86-64.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Tantor SE DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.24" class="tag_44"><td><a name="55bce132-e140-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 44); return false;">Infobase verification and repair</a>.<br></td><td><b>This feature is canceled.</b><p>Now, when verifying and repairing an infobase, you can detect and delete empty tables of initialized predefined data in the <span class="interface">Check logical infobase integrity </span>mode.</p></td><td>This feature was not provided.</td><td>Minimized the number of non-informative errors when using a separated infobase.</td></tr><tr title="Версия 8.3.24" class="tag_19"><td><a name="579bedfd-6b82-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Upgrade: improved <span class="term">IN() </span>query operator performance when using the PostgreSQL DBMS (and inherited DBMS) if 1C:Enterprise generates the query.</td><td>When using the PostgreSQL DBMS (and inherited DBMS), queries with the <span class="term">IN() </span>operator generated by 1C:Enterprise took more time.</td><td>Improved performance of queries generated by 1C:Enterprise when using PostgreSQL DBMS (and inherited DBMS) if the queries use the list of values for a table filter (the <span class="term">IN() </span>query language operator).</td></tr><tr title="Версия 8.3.24" class="tag_31"><td><a name="be54616b-8000-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>If it is necessary to change the user password in mobile client versions that do not support password change, a correct message describing the current situation is displayed. The message also contains the actions that the user needs to perform.</td><td>In mobile client versions that did not support changing the user password, the message about the need to change the user password was unclear and did not describe the situation.</td><td>The mobile client behavior is more user-friendly.</td></tr><tr title="Версия 8.3.24" class="tag_24"><td><a name="6a507355-8007-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 24); return false;">Infobase users</a>.<br></td><td>The email sent to the user by the standard password recovery service clearly indicates that the password for signing in to the 1C:Enterprise application is being restored.</td><td>Previously, the email sent to the user by the standard password recovery service did not clearly indicate that the password for signing in to the 1C:Enterprise application is being restored.</td><td>When reading the email, the user understands what password they restore.</td></tr><tr title="Версия 8.3.24" class="tag_18 tag_29"><td><a name="e0ff0679-a037-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>macOS version 15 is supported.</td><td>Previously, 1C:Enterprise did not support macOS versions 15.</td><td>Extended list of supported operating systems.</td></tr><tr title="Версия 8.3.24" class="tag_15 tag_29"><td><a name="5742cac6-b2e9-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following Linux distribution packages are now supported:<ul><li>For the x86 and x86-64 architectures:</li><ul><li>Astra Linux Special Edition 1.8 (with generic kernel only)</li><li>Mint 22</li><li>Simply Linux 10</li><li>Ubuntu 24.04 LTS</li><li>RED OS</li></ul><li>For the ARM64 architecture:</li><ul><li>Astra Linux Special Edition 1.8 (with generic kernel only)</li><li>Simply Linux 10</li><li>Ubuntu 24.04 LTS</li></ul></ul></td><td>The distribution packages were not supported.</td><td>Extended list of supported Linux distribution packages.</td></tr><tr title="Версия 8.3.24" class="tag_22 tag_29"><td><a name="f7ec969a-b2ea-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The list of Linux distribution packages that support Data Accelerator has been changed. The following distribution package versions are supported:<ul><li>Astra Linux Common Edition 2.12</li><li>Astra Linux Special Edition 1.6 - 1.8 (only generic kernel)</li><li>CentOS 7</li><li>Debian 10 - 12</li><li>Mint 20 - 22</li><li>Oracle Linux 7 - 9</li><li>Red Hat Enterprise Linux 7 - 9</li><li>Simply Linux 10</li><li>Ubuntu 20.04 LTS</li><li>Ubuntu 22.04 LTS</li><li>Ubuntu 24.04 LTS</li><li>ALT 8 SP</li><li>ALT Education 10</li><li>ALT Workstation 10</li><li>ALT Workstation K 10</li><li>ALT Server 10</li><li>ALT 10 SP</li><li>RED OS 7.3 MUROM</li><li>RED OS 8</li></ul></td><td>Previously, the following set of Linux distribution packages was supported for Data Accelerator:<ul><li>CentOS 6 and later</li><li>Red Hat Enterprise Linux 7 or later</li><li>Fedora 20 or later</li><li>Debian GNU/Linux 8 or later</li><li>Ubuntu 14.04 or later</li></ul></td><td>Updated the list of supported Linux distribution packages.</td></tr><tr title="Версия 8.3.24" class="tag_75"><td><a name="8b043d41-1c56-11f0-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 75); return false;">Distributed infobases</a>.<br></td><td>New feature: information about configuration objects that change the infobase structure without compatibility mode or changing the configuration format version is now recorded in the data exchange message of the distributed infobase. This information will allow the receiving party to determine whether the exchange message can be imported to the infobase without issues or not. If it is impossible, the message will be rejected, and you will need to update the platform to import the message.
The 1C:Enterprise platform that does not support this change will not be able to import such data exchange message. The message will also not be imported if the platform does not support configuration objects whose information is recorded in the exchange message.</td><td>This feature was not provided. As a result, any exchange message could be imported using any platform, and, when updating the database, changes could occur leading to the destruction of the infobase in the receiving node of the distributed infobase.</td><td>Improved reliability of a distributed infobase as the platform does not allow importing exchange messages that can destroy the infobase.</td></tr></table><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9cfe5bad-7d2f-11ed-963f-0050569f678a">Transition from the previous version to the version 8.3.24</a></h2><ul><li title="Версия 8.3.24" class="tag_0"><a name="9cfe5bae-7d2f-11ed-963f-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.24.
</li><li title="Версия 8.3.24" class="tag_0"><a name="9cfe5baf-7d2f-11ed-963f-0050569f678a"></a>Some features that are added in version 8.3.24 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.24" class="tag_0"><a name="80f33c1d-9349-11ed-963f-0050569f678a"></a>For the full-text search to improve the search result relevance, clear the full-text search index and recreate it on platform version 8.3.24.</li><li title="Версия 8.3.24" class="tag_0"><a name="b74e30e1-0443-11ee-963f-0050569f678a"></a>To use the geofence functionality in the mobile client version 8.3.24:<ul><li>Save the infobase configuration using version 8.3.24. You can set the required configuration compatibility mode.</li><li>Enable the geofence functionality if it is disabled (<span class="interface">Designer - Configuration property - Used mobile application</span> <span class="interface">functionality</span>).</li><li>Specify a text of the <span class="interface">Notification position</span> permission in the same dialog box.</li><li>Save the database configuration.</li><li>Export the mobile client configuration.</li><li>Build a new mobile application version with the new configuration version.</li><li>Update the mobile application on client devices.</li></ul><p>
</p></li></ul><p><a href="#9cfe5ba1-7d2f-11ed-963f-0050569f678a"><small>Table of contents</small></a></p><h1><a name="801127d0-e1af-11ec-aa69-0050569f678a">Version 8.3.23</a></h1><p title="Версия 8.3.23" class="tag_0"><a name="801127df-e1af-11ec-aa69-0050569f678a"></a>Version 8.3.23 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.23" class="tag_0"><a name="07a8fe64-f257-11ee-963f-0050569f678a"></a>The standalone server graduated out of beta.</p><hr></hr><ul><li><a href="#801127d1-e1af-11ec-aa69-0050569f678a">New functionality and changes</a></li><li><a href="#801127d2-e1af-11ec-aa69-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#801127d3-e1af-11ec-aa69-0050569f678a">Optimization</a></li><li><a href="#801127d4-e1af-11ec-aa69-0050569f678a">Changes that affect system behavior</a></li><li><a href="#801127d5-e1af-11ec-aa69-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#801127d6-e1af-11ec-aa69-0050569f678a">Renamed objects</a></li><li><a href="#801127d7-e1af-11ec-aa69-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#801127d9-e1af-11ec-aa69-0050569f678a">Library updates
</a></li><li><a href="#801127da-e1af-11ec-aa69-0050569f678a">Demo configuration changes</a></li><li><a href="#801127db-e1af-11ec-aa69-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#801127dc-e1af-11ec-aa69-0050569f678a">Transition from the previous version to the version 8.3.23</a></li></ul><h2><a name="801127d1-e1af-11ec-aa69-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.23" class="compat tag_2 tag_1"><td><a name="eef76a48-e337-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>New value for the <span class="interface">Compatibility mode </span>configuration property: <span class="interface">Version 8.3.22</span>.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.21 was available.
</td><td>You can run configurations developed in versions 8.3.22 and earlier in version 8.3.23 without changing the configuration and data structures. This way, you can migrate to version 8.3.23 without changing the configuration, then make required changes, and disable compatibility mode. You can also use version 8.3.22 after migration to version 8.3.23. You can do it both before you disable compatibility mode and after you enable it again.
</td></tr><tr title="Версия 8.3.23" class="tag_20"><td><a name="2786f50c-e57b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New 1C:Enterprise license type: for developers. This license type has the following features:<ul><li>It allows using the client application and the server cluster.</li><li>It is exclusively a software license.</li><li>It can be attached only to computer parameters.</li><li>If several licenses of this type are activated for one profile at the same time, they still have the same restriction parameters as one license.</li><li>It is time-restricted.</li><li>It does not limit quantitative characteristics of the configuration and the database.</li><li>To get this license, you need to register on the <a href="https://developer.1c.ru/" target="_blank">Read more</a>. developer portal.</li></ul><p>Detailed developer license features and restrictions are described in the respective documentation.</p><p>New properties for the <span class="term">LicenseAcquisitionRequest </span>object: <span class="term">AccountName </span>and <span class="term">AccountPassword</span>. New methods for the license acquisition manager: <span class="term">GetDeveloperLicenseUsageAvailability() </span>and <span class="term">GetDeveloperLicenseAgreement().</span></p></td><td>This feature was not provided.<p>The training version was used for practice.</p><p>The developer package or any other main distribution package were required for development.</p></td><td>1C:Enterprise version with full functionality can be used free of charge for training and development.</td></tr><tr title="Версия 8.3.23" class="tag_19 tag_10 tag_12"><td><a name="05ca5b4c-e586-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>You can now manage database tablespaces in client/server infobase mode. You can manage tablespaces for indexes and data. Separation of tables by namespaces is unique for each infobase and is not preserved when you export an infobase. Tablespace management is not supported in file infobases and Data Accelerator.<p>New standard function available in server infobases starting from <span class="interface">Version 8.3.7</span> compatibility mode: <span class="interface">Database tablespace management</span>.</p><p>New global context property: <span class="term">DatabaseTablespaces</span>.</p><p>New parameter for the <span class="term">IBCheck</span><span class="term">AndRepair </span>command-line option of Designer batch mode: <span class="term">RefreshTableLocation</span>.</p><p>New columns for the value table returned by the <span class="term">GetDBStorageStructureInfo()</span> method: <span class="term">DataStorageTablespace </span>and <span class="term">IndexStorageTablespace</span>.</p><p>New configuration property: <span class="interface">Tablespace usage mode</span>.</p><p>Database tablespace management is supported for CORP licenses.</p></td><td>This feature was not provided.</td><td>Advanced infobase administration features in client/server mode. Now you can assign infobase tables to various disk drives based on table load profiles.</td></tr><tr title="Версия 8.3.23" class="tag_69 tag_57"><td><a name="7068118c-e587-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 57); return false;">JSON support</a>.<br></td><td>New global context methods: <span class="term">WriteJSONValue()</span> and <span class="term">ReadJSONValue()</span>. The methods are available in any context. They serialize and deserialize a certain data type set to a JSON string and back to 1C:Enterprise language objects.</td><td>This feature was not provided.<p>The new methods could be implemented using existing JSON tools. However, this generally required a server call.</p></td><td>Simplified operations with JSON format, especially in web client and on mobile devices.</td></tr><tr title="Версия 8.3.23" class="tag_4"><td><a name="4df6106c-e597-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can exchange files with Telegram and VK if the collaboration system is integrated with them. Video file exchange with VK is not supported.<p>To store exchanged files, you can configure your own storage on the collaboration server.</p></td><td>This feature was not provided.<p>
</p></td><td>Advanced features for integration with instant messaging systems.</td></tr><tr title="Версия 8.3.23" class="tag_47 tag_10"><td><a name="ca1061ac-e59c-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can convert a server infobase into an infobase maintained by another DBMS without exporting it to a dt file and importing to a new DBMS. Conversion from file infobases is not supported.<p>New command for the "<span class="term">infobase</span>" command of the <span class="interface">ibcmd </span>utility: <span class="term">replicate</span>.</p></td><td>This feature was not provided.<p>The only way to change an active DBMS was infobase export to a dt file with its further import from this file to a new DBMS.</p><p>
</p></td><td>Simplified server infobase migration between various database management systems.</td></tr><tr title="Версия 8.3.23" class="tag_69"><td><a name="deca9b0c-e59d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>ICU regular expressions can be used in 1C:Enterprise language. Operations with regular expressions are available only on 1C:Enterprise server.<p>New global context methods: <span class="term">StrFindByRegularExpression()</span>, <span class="term">StrReplaceByRegularExpression()</span>, <span class="term">StrLikeByRegularExpression()</span>, and</p><p><span class="term"> StrFindAllByRegularExpression()</span>.</p></td><td>This feature was not provided.</td><td>Advanced search in strings using 1C:Enterprise language.</td></tr><tr title="Версия 8.3.23" class="tag_4"><td><a name="f30ca7d4-e646-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can integrate the collaboration system with the WhatsApp instant messaging system.<p>New property: <span class="term">CollaborationSystemIntegration.EnabledMessageEdit</span></p><p>New methods for the collaboration system manager: <span class="term">GetAnswerAvailabilityEndTime()</span>, <span class="term">GetAnswerAvailabilityEndTimeAsync()</span>, <span class="term">GetMessageTemplates()</span>, <span class="term">GetMessageTemplatesAsync()</span>, <span class="term">GetMessageTemplate()</span>, <span class="term">GetMessageTemplateAsync()</span>, <span class="term">SetMessageTemplatePresentations()</span>, and <span class="term">SetMessageTemplatePresentationsAsync()</span>.</p><p>New properties for the <span class="term">CollaborationSystemMessage </span>object: <span class="term">MessageTemplate </span>and <span class="term">MessageTemplatePlaceholderValues</span>.</p><p>New application module event: <span class="term">CollaborationSystemMessageTemplateChoiceProcessing</span>.</p></td><td>This feature was not provided.</td><td>Advanced features for collaboration system integration with instant messaging systems.</td></tr><tr title="Версия 8.3.23" class="tag_4"><td><a name="d297ff60-e669-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The standard data processor of collaboration system management displays information on parameters of the collaboration system where the infobase is registered and the subscriber email address.<p>New methods for the collaboration system manager: <span class="term">ServerAddress()</span>, <span class="term">ServerVersion()</span>, <span class="term">SubscriberEmail()</span>, and <span class="term">CurrentUserIsSubscriberAdministrator()</span>.</p><p>
</p><p>
</p></td><td>This feature was not provided.</td><td>Access to information about the collaboration system to which the current infobase is connected.</td></tr><tr title="Версия 8.3.23" class="tag_38"><td><a name="06278840-e66b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>You can create your own scheduled jobs in a configuration extension.</td><td>This feature was not provided.</td><td>Advanced configuration extension features.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="ae205260-e676-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Microsoft OLE DB Driver for SQL Server can be used in client/server infobase mode to ensure Microsoft SQL Server DBMS operation.</td><td>Microsoft OLE DB Driver for SQL Server was not supported in client/server infobase mode to ensure Microsoft SQL Server DBMS operation. Only Microsoft SQL Server Native Client was supported.</td><td>Extended list of supported access tools for Microsoft SQL Server DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_47"><td><a name="0d82ad25-e8bb-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>New standalone server features:<ul><li>Establish direct TCP connection to the infobase in managed applications.</li><li>Use Designer.</li><li>Use a standalone server as a test manager.</li><li>Debug applications using a built-in debug server.</li></ul></td><td>These features were not provided.<p>Application debugging was supported only when the debug server was deployed separately from the standalone server.</p></td><td>Advanced standalone server features.</td></tr><tr title="Версия 8.3.23" class="tag_47"><td><a name="284884c5-e8bd-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>You can enable and disable standalone server features in the new "<span class="term">features</span>" section of the configuration file. You can also use the following <span class="interface">ibsrv </span>utility command-line options:<ul><li><span class="term">--enable-extended-designer-features</span>, <span class="term">--disable-extended-designer-features</span>. Enables or disables advanced configuration features in the standalone server.</li><li><span class="term">--enable-http-gate</span>, <span class="term">--disable-http-gate</span>. Enables or disables infobase access over HTTP.</li><li><span class="term">--enable-ssh-gate</span>, <span class="term">--disable-ssh-gate</span>. Enables or disables the SSH gateway of the standalone server in agent mode.</li><li><span class="term">--enable-direct-gate</span>, <span class="term">--disable-direct-gate</span>. Enables or disables infobase access over TCP.</li></ul></td><td>These features were not provided.<p>All standalone server features were always available.</p></td><td>Advanced standalone server management features. You can now disable unused standalone server features.</td></tr><tr title="Версия 8.3.23" class="tag_47"><td><a name="dfda422e-ebe2-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>New standalone server features:<ul><li><span class="term">mobile-app export</span> mode. Save the mobile application configuration. Available only after advanced configuration features are enabled.</li><li><span class="term">mobile-client</span> mode:</li><ul><li><span class="term">export</span>. Save the mobile client configuration. Available only after advanced configuration features are enabled.</li><li><span class="term">sign</span>. Digitally sign the configuration.</li></ul><li><span class="term">config </span>mode. Shortened version of the <span class="term">infobase config</span> command.</li><li><span class="term">extension </span>mode. Shortened version of the <span class="term">infobase config</span> <span class="term">extension</span> command.</li><li><span class="term">infobase config</span> <span class="term">export</span>. Export an external data processor, report or extension to an XML file.</li><li><span class="term">infobase config import</span>. Import an external data processor, report, or extension from an XML file.</li></ul></td><td>These features were not provided.</td><td>Advanced standalone server features.<p>
</p></td></tr><tr title="Версия 8.3.23" class="tag_47"><td><a name="0c71c3ae-ebe1-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>New commands for the SSH gateway of the standalone server:<ul><li><span class="term">config </span><span class="term">mobile-app-write-file</span>. Save the mobile application configuration.</li><li><span class="term">config </span><span class="term">mobile-client-write-file</span>. Save the mobile client configuration.</li><li><span class="term">config sign-cfg</span>. Digitally sign the configuration.</li><li><span class="term">config </span><span class="term">mobile-client-digi-sign</span>. Digitally sign the mobile client configuration.</li></ul><p>
</p></td><td>These features were not provided.</td><td>Advanced standalone server features.</td></tr><tr title="Версия 8.3.23" class="tag_4"><td><a name="de47b64b-ee24-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can embed the collaboration system chat into third-party websites. New feature: API that allows the website to manage the chat.<p>New integration type: collaboration system web chat.</p><p>New events for the bot module: <span class="term">OnCreateCollaborationSystemConversation</span>, <span class="term">OnAddToCollaborationSystemConversation</span>, and <span class="term">OnDeleteFromCollaborationSystemConversation</span>.</p><p>New properties: <span class="term">CollaborationSystemGenerateCommandParameters.User</span>, <span class="term">CollaborationSystemUser.Alias,</span> <span class="term">CollaborationSystemIntegration</span>.<span class="term">VideoconferencesAvailable</span>, <span class="term">CollaborationSystemStandardCommand.ShowUserInfo</span>, and <span class="term">CollaborationSystemCommandSource.User</span>.</p><p>New method for the <span class="term">Color </span>and <span class="term">Font </span>types: <span class="term">GetAbsolute().</span></p><p>New feature that allows the website to interact with the web chat: Collaboration System WebChat API.</p><p>
</p></td><td>This feature was not provided.</td><td>Advanced collaboration system features.</td></tr><tr title="Версия 8.3.23" class="tag_17"><td><a name="937cc328-f2f9-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>The technological log can output the list of session data modification operations with their contexts to the <span class="term">Context </span>property of the <span class="term">CALL </span>events for the <span class="term">seanceParametersCommit </span>and <span class="term">finishSeance </span>cluster manager methods (<span class="interface">rmngr</span>).<p>This feature is managed by the <span class="term">&lt;sessiondatacontext&gt;</span> item of the <span class="interface">logcfg.xml </span>configuration file of the technological log.</p><p>Since this feature slows down the system, enable it only when you investigate issues related to the size of session data storage of a server cluster.</p></td><td>This feature was not provided.</td><td>Simplified investigation of issues related to the size of session data storage of a server cluster.</td></tr><tr title="Версия 8.3.23" class="tag_9"><td><a name="80a935b9-f910-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 9); return false;">Speech recognition</a>.<br></td><td>Implemented speech recognition in 1C:Enterprise platform. You can use it both in stream mode and from Ogg files. Speech recognition can be applied locally (on a user computer without Internet connection) or via 1C cloud service.<p>New global context property: <span class="term">SpeechProcessing</span>.</p><p>New standard data processor: <span class="interface">Manage speech recognition</span>.</p><p>New technological log events: <span class="term">&lt;STTAdm&gt;</span> and<span class="term"> &lt;STT&gt;</span>.</p><p>New system enumeration property: <span class="term">ErrorCategory.SpeechProcessingError</span>.</p><p>New command of the client application startup command-line: <span class="term">/DisableLocalSpeechToText</span>.</p><p>New 1C:Enterprise server cluster services: <span class="interface">Speech recognition service</span> and <span class="interface">Speech recognition model management service</span>.</p><p>New production server feature: change location of the directory with speech recognition models using the <span class="interface">Speech recognition model directory</span> property of the cluster console production server.</p><p>New parameter for the<span class="interface"> conf.cfg </span>file: <span class="term">SpeechToTextModelLocation</span>.</p><p>Speech recognition state is now displayed in the client application interface.</p><p>Speech recognition is not supported:</p><ul><li>In the web client in Mozilla Firefox, Safari, Google Chrome, and Chromium-based web browsers version 66 and earlier.</li><li>In the web client that is accessible over HTTP and whose publishing host is not <span class="interface">localhost</span>.</li><li>On the standalone server.</li><li>In the training 1C:Enterprise version.</li><li>On Microsoft Windows XP or Microsoft Windows Server 200</li><li>In local mode if the used file infobase is running on:</li><ul><li>macOS.</li><li>ARM processor.</li></ul><li>If the infobase is created in version 8.1 compatibility mode.</li></ul></td><td>This feature was not provided.</td><td>Available speech recognition in applications based on 1C:Enterprise. Specifically, voice control of the application or text input by voice dialing.</td></tr><tr title="Версия 8.3.23" class="tag_13"><td><a name="143f5f66-73ac-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 13); return false;">Binary data storage</a>.<br></td><td>New feature: binary data storage. Use it to store binary data in the computer file system of 1C:Enterprise server cluster instead of an infobase. The storage does not affect the way data reading and writing operations are defined by developers: the application considers that such operations are performed from applied object attributes.<p>The storage is supported only in client/server mode. The binary data storage is not supported on a standalone server and in a file infobase. You can manage the storage with the API developed in 1C:Enterprise language.</p><p>New global context property: <span class="term">BinaryDataStorage</span>. New 1C:Enterprise server cluster service: <span class="interface">Binary data storage service</span>. New standard data processor: <span class="interface">Binary data storage management</span>. New technological log event: <span class="term">&lt;STORE&gt;</span>.</p><p>Now you can check the binary data storage integrity:</p><ul><li>New item in the <span class="interface">Verify and repair </span>dialog box: <span class="interface">Binary data storage integrity check</span>.</li><li>New parameter for the<span class="term"> /IBCheckAndRepair </span>command-line option of Designer batch mode: <span class="term">-BinaryDataStorageIntegrity</span>.</li></ul><p>The feature requires a CORP license.</p><p>The feature is currently in beta status. To use the binary data storage, you need a testing license. Without it, the feature is unavailable.</p></td><td>This feature was not provided.</td><td>New feature: if an infobase contains a large quantity of binary data, you can manage the database size and performance of binary data operations using the binary data storage.</td></tr></table><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127d2-e1af-11ec-aa69-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.23" class="tag_14"><td><a name="27ed8e80-e679-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The following user settings are automatically saved in the client application every 20 minutes:<ul><li>Application window position and size </li><li>Table column width settings </li><li>Position of separators</li></ul></td><td>User settings were saved only during regular client application shutdown.</td><td>Reduced risk of losing configured settings in the client application.</td></tr><tr title="Версия 8.3.23" class="tag_4"><td><a name="d5fed3a3-ed5e-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can switch the current video call to another device or another running application. If screen sharing is enabled at the moment of switching, it is disabled.</td><td>This feature was not provided.</td><td>Advanced features of collaboration system video calls.</td></tr><tr title="Версия 8.3.23" class="tag_4 tag_31"><td><a name="d83a04a3-ed77-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>In case of network issues, the collaboration system attempts to restore connection during the call. The system attempts to restore connection until the client application is closed and the problematic video call is finished.</td><td>In case of network issues, the collaboration system did not attempt to restore connection.</td><td>Enhanced video call quality in case of poor communication channel quality.</td></tr><tr title="Версия 8.3.23" class="tag_4"><td><a name="fdea4c23-ed7f-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Video call image quality now adapts to the current communication channel quality. Image quality can increase or decrease in direct correlation with the communication channel quality.</td><td>In the collaboration system, video call image quality could only decrease if communication channel quality decreased. If communication channel quality increased, image quality was not restored.</td><td>More flexible adaptation of video call image quality in relation to communication channel quality.</td></tr></table><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127d3-e1af-11ec-aa69-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.23" class="tag_38"><td><a name="4e8dfec0-e67a-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>When you start thin and web clients after updating one or several configuration extensions, the number of server requests and amount of transferred data is reduced.</td><td>When you started thin and web clients after updating one or several configuration extensions, numerous requests were executed and a large amount of data was transferred.</td><td>Faster start of thin and web clients after updating one or several extensions.</td></tr><tr title="Версия 8.3.23" class="tag_7"><td><a name="25083429-e715-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Initial database copy filling takes less time.</td><td>Initial database copy filling took more time.</td><td>Improved performance of initial database copy filling.</td></tr><tr title="Версия 8.3.23" class="tag_6"><td><a name="537e3f38-ecab-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Client application blackout is reduced or eliminated upon restart of the working process serving this client application.</td><td>Upon restart of the working process serving the client application, this client application could be unavailable for a long time.</td><td>Reduced or eliminated client application blackout upon restart of the working process serving this client application.</td></tr><tr title="Версия 8.3.23" class="tag_4"><td><a name="85d43da2-0e77-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Connection established over PPP between video call participants is faster now.<p>Improved noise reduction when both video call participants are talking at the same time.</p><p>Improved screen sharing quality.</p></td><td>Connection established over PPP (time from receiving a call to conversation start) could take a very long time.<p>When both video call participants were talking at the same time, noise reduction quality was not good enough.</p><p>Screen sharing quality was not good enough.</p></td><td>Improved video stream performance in the collaboration system in the thick and thin client applications.</td></tr><tr title="Версия 8.3.23" class="tag_22"><td><a name="b573e2ec-3376-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>A sharp increase in RAM consumption by Data accelerator during some user queries is eliminated.</td><td>A sharp increase in RAM consumption by Data accelerator was observed during some user queries.</td><td>Reduced RAM consumption by Data accelerator in some cases.</td></tr><tr title="Версия 8.3.23" class="tag_22"><td><a name="0ca9ac52-3377-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>Execution of queries with ordering to some tables takes less time.</td><td>Execution of queries with ordering to some tables took more time.</td><td>Improved performance of queries to some tables in Data accelerator.</td></tr><tr title="Версия 8.3.23" class="tag_22"><td><a name="8fca18be-3377-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>In Data accelerator, stored text fields use less memory and their processing takes less time.</td><td>In Data accelerator, stored text fields used more memory and their processing took more time.</td><td>Faster operations with text fields in Data accelerator.</td></tr><tr title="Версия 8.3.23" class="tag_22"><td><a name="02e9d958-3378-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>Operations with indexes set up in the configuration have been optimized in Data accelerator.</td><td>Operations with indexes set up in the configuration were not optimized in Data accelerator.</td><td>Improved performance of queries that use tables for which indexes are set up in the configuration.</td></tr><tr title="Версия 8.3.23" class="tag_22"><td><a name="35c57b8a-3379-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>At Data accelerator startup on Linux, the system checks that the "<span class="term">transparent hugepage</span>" operating system core parameter is appropriately set for Data accelerator operation. This parameter must be set to "<span class="term">madwise</span>" or "<span class="term">never</span>".<p>If this parameter is set up incorrectly, Data accelerator is not started and respective diagnostic information is saved to the technological log.</p></td><td>The value of the "<span class="term">transparent </span>hugepage" operating system core parameter was not checked at Data accelerator startup on Linux.</td><td>Operating system settings check for optimal Data accelerator operation on Linux.</td></tr><tr title="Версия 8.3.23" class="tag_22"><td><a name="6d18df46-3379-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>Some Data accelerator queries have been optimized.</td><td>Execution of some Data accelerator queries took more time.</td><td>Improved Data accelerator performance.</td></tr><tr title="Версия 8.3.23" class="tag_5"><td><a name="a78cd522-2bba-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 5); return false;">Data Accelerator</a>.<br></td><td>Improved Data Accelerator stability in case of restrictions or insufficient memory during query execution. The improvement was achieved by changing query optimization algorithms, which might slightly slow down query execution in some cases.</td><td>Previously, Data Accelerator could be unstable in case of restrictions or insufficient memory during query execution and aggressive query optimization.</td><td>Improved Data Accelerator stability in case of restrictions or insufficient memory during query execution. The improvement was achieved by changing query optimization algorithms, which might slightly slow down query execution in some cases.</td></tr></table><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127d4-e1af-11ec-aa69-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.23" class="tag_10"><td><a name="b87b31c8-e339-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>User action logging is deprecated.<p>The /<span class="term">LogUI </span>option of the client application startup command line is deprecated.</p></td><td>User action logging was supported in the client application.</td><td>Outdated tools are no longer supported.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="52931aec-e598-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Infobase verification and repair in client/server mode is always performed on the server.<p>Infobase verification and repair takes less time.</p></td><td>Infobase verification and repair in client/server mode was performed on the client in Designer.<p>Infobase verification and repair took more time.</p></td><td>Faster infobase verification and repair in client/server mode.</td></tr><tr title="Версия 8.3.23" class="tag_38"><td><a name="ea0e30c0-e677-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The query wizard opened in the configuration extension supports operations configuration objects not included in the extension. If objects not included in the extension are used in a query, you are prompted to add all the missing configuration objects to the extension when the wizard is closed.<p>In the query wizard dialog box, you can manage the view of tables and fields in the extended configuration.</p></td><td>This feature was not provided.<p>The query wizard opened from the configuration extension allowed using only tables and fields of native and adopted extension objects.</p></td><td>Advanced configuration extension features.</td></tr><tr title="Версия 8.3.23" class="tag_59"><td><a name="45d6df2f-e70a-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>You can save settings of the client application window. New client application form property available in the form editor: <span class="interface">Save window settings</span>.<p>New command: <span class="interface">Restore size</span>. To call this command, press <span class="interface">Alt+Shift+R</span>. This command restores not only window position and size, but also sets the position of separators and column size of all form tables to default values.</p><p>The "<span class="interface">Restore window position</span>" command is no longer available. Behavior of the "<span class="interface">Restore sizes</span>" command depends on how the form is opened.</p><p>
</p></td><td>This feature was not provided. Form settings were always saved regardless of whether the form developer needed it.</td><td>You can save form settings.<p>The command to restore window position and size also restores the position of separators and the size of form table columns.</p></td></tr><tr title="Версия 8.3.23" class="tag_8"><td><a name="99c22209-e718-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>On Windows, the size of a file to be decrypted is no longer limited to 100 MB.</td><td>On Windows, the size of a file to be decrypted was limited to 100 MB.</td><td>Removed size restrictions for a file to be decrypted on Windows.</td></tr><tr title="Версия 8.3.23" class="tag_14"><td><a name="3d65ed89-e72b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>In client applications and in Designer on macOS, <span class="interface">Option </span>and <span class="interface">Cmd </span>keys are displayed in keyboard shortcuts instead of <span class="interface">Alt </span>and <span class="interface">Ctrl</span>.</td><td>In client applications and in Designer on macOS, keyboard specifics of Apple computers were not considered in displayed keyboard shortcuts.</td><td>Keyboard shortcut representation is adjusted to macOS standards.</td></tr><tr title="Версия 8.3.23" class="tag_20 tag_14"><td><a name="7e2e7809-e726-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>New keyboard shortcuts for Designer on macOS:<ul><li><span class="interface">Cmd+M</span>. Open a tooltip.</li><li><span class="interface">Cmd+Shift+M</span>. Open a tooltip on method parameters.</li><li><span class="interface">Option+F11</span>. Go to the method in the debugger.</li><li><span class="interface">Shift+F12</span>. Go to the method definition.</li><li><span class="interface">Cmd+Option+Shift+F5</span>. Start the application without debug mode.</li></ul><p>New keyboard shortcuts for any client application on macOS:</p><ul><li><span class="interface">Cmd+J</span>. Select from the text template list.</li><li><span class="interface">Cmd+Q</span>. Close the application.</li><li>All the added shortcuts are implemented in addition to the already existing keyboard shortcuts for the specified functions.</li></ul></td><td>These keyboard shortcuts were unavailable in client applications and Designer on macOS.</td><td>Adjusted keyboard shortcuts for operations on macOS.</td></tr><tr title="Версия 8.3.23" class="tag_6"><td><a name="4ed164f4-e733-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When the server cluster monitoring system successfully receives data during a server call, it considers such working process functional.</td><td>The server cluster monitoring system used only special cluster monitoring system calls to make sure the working process is functional. In some cases, this could lead to erroneous restarts of working processes due to heavy load on the server cluster.</td><td>Reduced risk of unreasonable restarts of working processes by the server cluster monitoring system.</td></tr><tr title="Версия 8.3.23" class="tag_14"><td><a name="ec9f876b-ebb9-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>If a cluster service call error occurs on the server when connecting the client application to a server cluster or during a server call, the user will see a dialog box with information about the error and option to reconnect or attempt another server call (automatically as well).</td><td>If a cluster service call error occurred on the server when connecting the client application to a server cluster or during a server call, the user was prompted to close or restart the client application.</td><td>Reduced number of situations when the client application is restarted or closed. </td></tr><tr title="Версия 8.3.23" class="compat tag_76 tag_1"><td><a name="35f9bc98-ecb2-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 76); return false;">Storing settings</a>.<br></td><td>For the standard settings storage, restrictions on the length of username and settings key are removed. The object key length is still restricted and cannot exceed 256 characters.<p>The dataset obtained by the <span class="term">Select()</span> method of the standard settings storage manager will be ordered by:</p><ul><li>Hash function value of the username (ascending).</li><li>Object key (in alphanumeric order, ascending).</li><li>Hash function value of the settings key (ascending).</li><li>The <span class="term">Version </span>field (ascending).</li></ul><p>This change is not implemented in version 8.3.22 compatibility mode.</p></td><td>The following restrictions on property length were set for the standard settings storage:<ul><li>Username could no exceed 64 characters.</li><li>Settings key could no exceed 128 characters.</li></ul><p>The dataset obtained by the <span class="term">Select()</span> method of the standard settings storage manager was sorted in ascending order by the following fields:</p><ul><li>Username </li><li>Object key </li><li>Settings key</li></ul></td><td>Advanced standard settings storage features.</td></tr><tr title="Версия 8.3.23" class="tag_21"><td><a name="578d0c7d-ed47-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>If you enter a search query of 3 or less characters into the global search string, this query is sent to the full-text search as is.<p>Restrictions on the number of returned full-text search results are removed.</p></td><td>If you entered a search query of 3 or less characters into the global search string, this query was sent to the full-text search with an asterisk after the entered characters.<p>If a full-text search returned more than 1 million results, an error occurred without displaying the search results.</p></td><td>You can get the result of a full-text search in situations that previously caused errors.</td></tr><tr title="Версия 8.3.23" class="tag_38 tag_20"><td><a name="3ac75d8a-ed82-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>When you check the extension module syntax In Designer, in methods annotated as <span class="term">ChangeAndValidate</span>, the "<span class="interface">Variable is not defined</span>" errors are ignored in all method areas except for <span class="term">#Insert ... </span><span class="term">#EndInsert</span>.<p>
</p></td><td>When you checked the extension module syntax in Designer, in methods annotated as <span class="term">ChangeAndValidate</span>, the "<span class="interface">Variable is not defined</span>" errors occurred when the method used an attribute not added to the extension. However, it was not required to actually add the attribute.</td><td>In case of targeted changes of configuration methods using the <span class="term">ChangeAndValidate </span>annotation, fewer extended configuration objects must be adopted into the extension.</td></tr><tr title="Версия 8.3.23" class="compat tag_26 tag_1"><td><a name="975aa068-ee0e-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>If vertical text alignment for a spreadsheet document cell is set to "<span class="term">Center</span>" or "<span class="term">Bottom</span>", but the text in it does not fit in the cell vertically, the text will be displayed as if vertical text alignment were set to "<span class="term">Top</span>". In this case, the text is displayed starting from the top cell border. If the text still does not fit in the cell completely, the excess text will be truncated.<p>If a spreadsheet document is exported to any format other than MXL (HTML, Microsoft OpenXML, OpenOffice, and so on), alignment will remain the same and the exported document might differ from the original.</p><p>This change is not implemented in version 8.3.22 compatibility mode.</p></td><td>If vertical text alignment for a spreadsheet document cell was set to "<span class="term">Center</span>" or "<span class="term">Bottom</span>", but the text in it did not fit in the cell vertically, the text was placed and truncated in the following way:<ul><li>If alignment was set to "<span class="term">Center</span>", the text was vertically aligned to the cell center and the text parts that did not fit in the cell were truncated from its beginning and from its ending.</li><li>If alignment was set to "<span class="term">Bottom</span>", the text was vertically aligned to the cell bottom and the text part that did not fit in the cell was truncated from its beginning.</li></ul><p>
</p></td><td>Eliminated unexpected system behavior. If the text does not fit in the cell, the text beginning will be always visible regardless of selected vertical text alignment.<p>
</p></td></tr><tr title="Версия 8.3.23" class="tag_31 tag_28"><td><a name="86bd45a8-11a1-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>For client application form fields, you can specify the field content to be taken into account by the operating system autofill tool. The feature is implemented in mobile and web clients. In web client, only input fields of the currently open form can be automatically filled. The field content of other open forms remains unchanged.<p>New form field extension property for the input field: <span class="term">AutofillHint</span>.</p></td><td>This feature was not provided.</td><td>Simplified auto filling of fields that have standard meanings.<p>
</p></td></tr><tr title="Версия 8.3.23" class="compat tag_25 tag_43 tag_1"><td><a name="7e0848bc-6b2a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>When restoring settings, the <span class="term">DataCompositionSettingsComposer.Restore()</span> method now clears (or disables) filters in custom settings that use unavailable fields (on the left of the filter).<p>This change is not implemented in version 8.3.22 compatibility mode.</p></td><td>When restoring settings, the <span class="term">DataCompositionSettingsComposer.Restore() </span>method did not check the availability of fields used in on the left of the filter.</td><td>In reports or dynamic lists, custom filters by fields unavailable in the report or dynamic list are disabled or deleted. This change is also applied to filters by fields disabled by functional options.</td></tr><tr title="Версия 8.3.23" class="tag_25"><td><a name="b65ab6c5-6fc2-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The way the list of available DCS fields is displayed in a form table field has been optimized.</td><td>The way the list of available DCS fields was displayed in a form table field was not optimal.</td><td>Delay-free navigation in the list of available DCS fields (especially when the list contains thousands of items).</td></tr><tr title="Версия 8.3.23" class="tag_27"><td><a name="925c8da6-7146-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is 2.16.</td><td>The format version of configuration dump to XML files was 2.15.</td><td>Configuration dump to XML files supports new platform features.</td></tr><tr title="Версия 8.3.23" class="compat tag_25 tag_1"><td><a name="37852bf7-762a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When fields with multiple characteristics are filtered, the data composition system filters the field that contains a multiple characteristic, but does not filter the values of such characteristic.<p>This change is not implemented in version 8.3.22 compatibility mode.</p></td><td>When fields with multiple characteristics were filtered, the data composition system filtered the field that contained a multiple characteristic and the values of such characteristic.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127d5-e1af-11ec-aa69-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.23" class="tag_10"><td><a name="99baf377-e7d6-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can set up preliminary downloading and installation of the client application distribution package on user computers. Such downloading will be performed before the actual application update on the server.<p>New configuration file: <span class="interface">ClientUpdate.cfg</span>.</p></td><td>This feature was not provided.<p>Client application update could not be scheduled.</p></td><td>After 1C:Enterprise update on the server, the user does not have to wait until the new client application version is downloded and installed to start working, since it is done preliminary.</td></tr><tr title="Версия 8.3.23" class="tag_59"><td><a name="c1a91438-ec79-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>Collection view for the input field displaying the form attribute of the <span class="term">ValueList </span>or <span class="term">FormDataCollection </span>type has been changed. Each collection element displayed in the input field has its own presentation, image, and the deletion button. If the input field displays a collection with a single type, you can add values to the collection directly from the input field including multiple choice. The selection button does not perform any actions. The view button activates the collection editing form.<p>Value list view in a table cell of the client application form is changed in the same way.</p><p>New properties for the input field of the client application form: <span class="term">MultipleValuesBackColor</span>, <span class="term">MultipleValuesTextColor</span>, <span class="term">MultipleValuesFont</span>, <span class="term">MultipleValueDataPath</span>, <span class="term">MultipleValuePresentationDataPath</span>, <span class="term">MultipleValuePictureDataPath</span>, <span class="term">MultipleValuesPicture</span>, <span class="term">AllowInputEmptyMultipleValues</span>, <span class="term">AllowMultipleValuesDuplicates</span>, <span class="term">ShowCheckBoxesInDropListWhenInputMultipleValues</span>, <span class="term">MultipleValuesHyperlink</span>, <span class="term">MultipleValuePictureShape</span>, and <span class="term">MultipleValuePictureSize</span>.</p><p>New methods for input field extension for the client application form: <span class="term">GetSelectedMultipleValues()</span> and <span class="term">SetSelectedMultipleValues()</span>.</p><p>New events for the input field of the client application form: <span class="term">CommandGenerateProcessing</span>, <span class="term">MultipleValuesAdd</span>, <span class="term">MultipleValuesDelete</span>, <span class="term">MultipleValueOpening</span>, and <span class="term">MultipleValueURLProcessing</span>.</p><p>New system enumerations: <span class="term">InputFieldMultipleValuePictureShape </span>and <span class="term">InputFieldMultipleValuePictureSize</span>.</p><p>The changed view is implemented in the <span class="interface">Taxi</span> and <span class="interface">Version 8.2</span> interfaces.</p><p>
</p></td><td>The input field displayed the form attribute of the <span class="term">ValueList </span>or <span class="term">FormDataCollection </span>type as a list of semicolon-separated value presentations. To change the list, you had to open a separate form.</td><td>Improved view of values of the <span class="term">ValueList </span>and <span class="term">FormDataCollection </span>types. This will allow creating more compact and user-friendly interfaces.</td></tr><tr title="Версия 8.3.23" class="tag_63"><td><a name="5ed7ed18-eca9-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Changed Gantt chart appearance in thin and web clients. Text for points, values, and intervals of the chart can be displayed in several rows. You can display text on chart intervals.<p>You can select chart values using the keyboard and mouse. You can select chart intervals using the mouse. Interval time limits are displayed in a tooltip. When you drag an interval, interval time limits are displayed in the tooltip.</p><p>New property for the <span class="term">GanttChart </span>object: <span class="term">IntervalTextRepresentation</span>. New method for the <span class="term">GanttChart</span><span class="term"> </span>object: <span class="term">FindIntervalByID().</span></p><p>New property for the <span class="term">GanttChartPlotArea </span>object: <span class="term">TextPlacement</span>.</p><p>New properties for the <span class="term">GanttChartInterval </span>object: <span class="term">TextColor</span>, <span class="term">ID</span>.</p><p>New properties for form field extension of the Gantt chart: <span class="term">CurrentValue</span>, <span class="term">SelectedValues</span>, <span class="term">ValueSelectionMode</span>, <span class="term">CurrentInterval</span>, <span class="term">SelectedIntervals</span>, <span class="term">IntervalSelectionMode</span>, <span class="term">VerticalLines</span>, and <span class="term">HorizontalLines</span>.</p><p>New events for form field extension of the Gantt chart: <span class="term">OnActivateValue</span>, <span class="term">OnActivateInterval</span>, <span class="term">BeforeExpand</span>, <span class="term">BeforeCollapse</span>.</p></td><td>The Gantt chart had a different appearance. Users could not select values and intervals.</td><td>The Gantt chart is now more user-friendly. Advanced user and chart interaction features.</td></tr><tr title="Версия 8.3.23" class="compat tag_56 tag_1"><td><a name="a31d2902-0e7a-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>New types for the XDTO namespace (<a href="http://v8.1c.ru/8.1/data/enterprise" target="_blank">http://v8.1c.ru/8.1/data/enterprise</a>):<ul><li><span class="term">AnyDBRef</span>. Main type of references to database objects (any reference types, except for enumerations).</li><li><span class="term">AnyMDEnum</span>. Main type of references to configuration enumerations (any values of enumerations created in the configuration).</li><li><span class="term">AnyIBRef</span>. Type corresponding to the <span class="term">AnyRef </span>type.</li></ul><p>When you generate a native XDTO package, we recommend that you use one of the implemented types depending on the type of saved value. If you use a global XDTO factory, the new types will be used automatically.</p><p>This change is not implemented in 8.3.22 version compatibility mode.</p></td><td>The XDTO namespace (<a href="http://v8.1c.ru/8.1/data/enterprise" target="_blank">http://v8.1c.ru/8.1/data/enterprise</a>) contained only the <span class="term">AnyRef </span>type. It did not allow you to correctly display the <span class="term">AnyRef </span>type value. When you used a global XDTO factory, the <span class="term">AnyRef </span>type was used for the <span class="term">AnyRef </span>type attribute.</td><td>Eliminated unexpected system behavior.<p>With the <span class="term">AnylBRef </span>type, you can correctly save and restore the value of the <span class="term">AnyRef </span>type attribute.</p></td></tr><tr title="Версия 8.3.23" class="compat tag_59 tag_1"><td><a name="d9296088-119c-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>The following item properties of the client application form are now supported on the server:<ul><li>Form field extension for the input field: <span class="term">AutoShowClearButton</span>, <span class="term">AutoShowOpenButton</span>, <span class="term">AutoCorrectionOnTextInput</span>, <span class="term">SpellCheckingOnTextInput</span>, <span class="term">AutoCapitalizationOnTextInput</span>, <span class="term">SpecialTextInputMode</span>, <span class="term">OnScreenKeyboardReturnKeyText</span>, and <span class="term">HeightControlVariant</span>.</li><li>Form table extension for the input field: <span class="term">RefreshRequest</span>.</li></ul><p>An attempt to access the <span class="term">AssociatedTable </span>property throws an exception for the following client application form items: form group extension for a normal group, form group extension for pages, and form command.</p><p>This change is not implemented in 8.3.22 version compatibility mode.
</p></td><td>No actions or errors occurred when the server accessed the following item properties of the client application form:<ul><li>Form field extension for the input field: <span class="term">AutoShowClearButton</span>, <span class="term">AutoShowOpenButton</span>, <span class="term">AutoCorrectionOnTextInput</span>, <span class="term">SpellCheckingOnTextInput</span>, <span class="term">AutoCapitalizationOnTextInput</span>, <span class="term">SpecialTextInputMode</span>, <span class="term">OnScreenKeyboardReturnKeyText</span>, and <span class="term">HeightControlVariant</span>.</li><li>Form table extension for the input field: <span class="term">RefreshRequest</span>.</li><li>Form group extension for a normal group: <span class="term">AssociatedTable</span>.</li><li>Form group extension for pages: <span class="term">AssociatedTable</span>.</li><li>Form command: <span class="term">AssociatedTable</span>.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.23" class="compat tag_25 tag_1"><td><a name="556845c8-119e-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New restriction for programmatic or interactive editing of the DCS settings structure: not more than 30 nesting levels.<p>In case of interactive or programmatic import of a report, report option, or data composition schema from a file, only the settings located above the 60 nesting level are imported. The remaining settings are ignored.</p><p>This change is not implemented in version 8.3.22 compatibility mode.</p><p>
</p></td><td>There were not any restrictions in terms of nesting levels of items for the DCS settings structure in case of programmatic or interactive operations or import from files. That could result in an abnormal termination of the client application.</td><td>Reduced probability of situations where the number of DCS settings is dramatically increased due to their editing (for example, as a result of dragging some part of settings).<p>Developers and users cannot interactively or programmatically set up a report option where the limit of 30 nesting levels is exceeded for settings structure items, filter items, or grouping fields.</p><p>If the user opens reports or imports report options/data composition settings, all the setting items located below the 60 nesting level are lost and the user gets a respective notification.</p></td></tr><tr title="Версия 8.3.23" class="compat tag_59 tag_1"><td><a name="04eae16e-79f5-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>If the <span class="term">Accessibility </span>property in the client application form (in thin, thick, or web client) is set to <span class="term">False</span>, the buttons related to form commands become unavailable in the form.<p>This change is not implemented in version 8.3.22 compatibility mode.</p></td><td>If the <span class="term">Accessibility </span>property in the client application form (in thin, thick, or web client) was set to <span class="term">False</span>, the buttons related to form commands remained available in the form.<p>This change is not implemented in version 8.3.22 compatibility mode.</p></td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127d6-e1af-11ec-aa69-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.23" class="tag_0"><td><a name="88473c98-ecaa-11ec-aa69-0050569f678a"></a>New names of properties and objects related to the planner field. Former names are supported for compatibility purposes.<p>
</p></td><td><ul><li><span class="term">PlannerCommandGenerateParameters</span>.</li><li><span class="term">PlannerCommandDescription</span>.</li><li><span class="term">PlannerCommandSource</span>.</li><li><span class="term">PlannerStandardCommand</span>.</li></ul><p>
</p></td><td><ul><li><span class="term">PlannerFieldCommandGenerateParameters</span>.</li><li><span class="term">PlannerFieldCommandDescription</span>.</li><li><span class="term">PlannerFieldCommandSource</span>.</li><li><span class="term">PlannerFieldStandardCommand</span>.</li></ul></td></tr><tr title="Версия 8.3.23" class="tag_0"><td><a name="e7e2bca4-463c-11ed-963f-0050569f678a"></a>English method names of the error handling manager. The old method names are supported for compatibility purposes.</td><td><ul><li><span class="term">GetCategoryForUser()</span>.</li><li><span class="term">GetMessageForUser()</span>.</li><li><span class="term">GetDescriptonForUser()</span>.</li><li><span class="term">GetBriefDescription()</span>.</li><li><span class="term">GetDetailDescription()</span>.</li></ul><p>
</p>
</td><td><ul><li><span class="term">ErrorCategoryForUser()</span>.</li><li><span class="term">ErrorMessageForUser()</span>.</li><li><span class="term">ErrorDescriptionForUser()</span>.</li><li><span class="term">BriefErrorDescription()</span>.</li><li><span class="term">DetailErrorDescription()</span>.</li></ul></td></tr></table><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127d7-e1af-11ec-aa69-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.23" class="compat tag_30 tag_31 tag_1"><td><a name="7cd91be0-e678-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>On mobile devices, the <span class="term">SystemInfo.PlatformType </span>property contains the relevant value. New values for the <span class="term">PlatformType </span>system enumeration. They describe supported mobile operating systems.<p>This change is not implemented in 8.3.22 version compatibility mode.</p></td><td>On mobile devices, the <span class="term">SystemInfo.PlatformType</span> property was set to <span class="term">Undefined</span>.</td><td>Simplified type and bitness identification of the used mobile version of 1C:Enterprise.</td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31 tag_48"><td><a name="be82c24b-ee39-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Mobile 1C:Enterprise version now supports NFC tags. This feature is provided on Android version 4.4 or later and iOS version 13.0 or later. You can read and write data in NDEF format, change the tag state to "read-only", and start the application upon mobile device contact with an NFC tag. The application is started using the deep linking tool.<p>New global context property: <span class="term">NFCTools</span>. New objects: <span class="term">TextNDEFRecord</span>, <span class="term">URINDEFRecord</span>, <span class="term">MediaRecordNDEF</span>, <span class="term">ExternalTypeNDEFRecord</span>, <span class="term">EmptyNDEFRecord</span>, <span class="term">UnknownNDEFRecord</span>, <span class="term">NDEFMessage</span>, and <span class="term">NDEFTag</span>.</p><p>
</p></td><td>This feature was not provided.</td><td>Support of NFC tags on mobile devices except for payment features.</td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31 tag_48"><td><a name="4300bb59-f08f-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Users can scale pictures in the preview window, which opens when executing the <span class="term">MultimediaTools</span><span class="term">.MakePhoto()</span> method.<p>Scaling is available on Android and performed in a standard way.</p></td><td>This feature was not provided.</td><td>The user can view a taken photo in more detail and retake it if necessary.</td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31"><td><a name="9c453019-f09e-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile version on Android can transfer data to a third-party application and get its operation result. You can configure the search for an application to be started using the <span class="term">MobileDeviceApplicationRun </span>object.<p>New properties for the <span class="term">MobileDeviceApplicationRun </span>object: <span class="term">ClipData </span>and <span class="term">Categories</span>.</p><p>New methods for the <span class="term">MobileDeviceApplicationRun </span>object: <span class="term">RunAsync()</span>, <span class="term">RunWithoutWaiting()</span>, and <span class="term">SetApplicationChoiceParameters()</span>.</p><p>The <span class="term">MobileDeviceApplicationRun.Category</span> property is deprecated.</p><p>The <span class="term">MobileDeviceApplicationRun.Run()</span> method is deprecated.</p></td><td>For the mobile version on Android, features of data transfer to a third-party application were more limited. Users could not get the operation result of a third-party application.</td><td>In versions on Android, advanced features for operations with external mobile applications.</td></tr><tr title="Версия 8.3.23" class="tag_31"><td><a name="9a8af9e2-f143-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New feature for the mobile client with standalone mode: automatic exchange with the main infobase. The exchange starts every 15 minutes and the interval cannot be changed.<p>New parameter for the <span class="term">AfterExchangeDataWithMainServer </span>event handler: <span class="term">ExchangeDate</span>.</p></td><td>This feature was not provided.</td><td>Improved data synchronization between the mobile device and the main infobase.</td></tr><tr title="Версия 8.3.23" class="tag_31 tag_4"><td><a name="9464c1e5-f78d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Video calls can be switched to or from mobile devices.<p>
</p></td><td>This feature was not provided.</td><td>Users can switch devices and join interrupted video calls again if they cannot continue a conversation on their initial device. </td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31"><td><a name="2307ca25-f79b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The date and time choice form for mobile devices has been revised.</td><td>The date and time choice form was different.</td><td>More user-friendly date and time choice form for mobile devices.</td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31"><td><a name="222ea780-3366-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Mobile 1C:Enterprise version no longer supports iOS 8.0.<p>The minimum supported iOS version is 9.0.</p><p>
</p></td><td>Mobile 1C:Enterprise version supported iOS 8.0.<p>
</p></td><td>An outdated iOS version is no longer supported.<p>
</p></td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31"><td><a name="395009c2-336b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New feature in mobile 1C:Enterprise version: document scanning (with result normalization) using the built-in mobile device camera. Scanning can be performed automatically or manually. Users can scan one or several pages and change page order in the scanned document.<p>New methods for the <span class="term">MultimediaTools </span>object: </p><ul><li><span class="term">DocumentScanningSupported()</span></li><li><span class="term">ShowDocumentScanning()</span></li><li><span class="term">ScanDocumentsAsync()</span></li><li><span class="term">CloseDocumentScanning()</span></li></ul><p>New mobile application functionality: <span class="term">DocumentScanning</span>.</p><p>Document scanning is not supported on Windows.</p></td><td>This feature was not provided.<p>Documents could be scanned only as photos, without image quality and placement normalization.</p></td><td>Document scanning using the mobile device camera with scanning results close to the ones of stationary scanners.<p>
</p></td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31 tag_48"><td><a name="be0c8a6e-3375-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Extended filter features for operations with contacts and calendars.<p>The following filter fields can be specified for the filters used in the <span class="term">ContactManager.FindContacts()</span> and <span class="term">CalendarsManager.FindCalendars()</span> methods: <span class="term">Account</span>, <span class="term">AccountID</span>, and <span class="term">AccountSource</span>.</p><p>When using the <span class="term">ContactManager.FindContacts(</span><span class="term">)</span>, <span class="term">CalendarsManager.FindCalendars()</span>, and<span class="term"> CalendarsManager.FindEvents()</span> methods, the root values of the passed filter are combined in case of searching with the AND operator.</p><p>For better performance of operations with contacts and calendars, filter is always applied by the account currently used in the application.</p><p>
</p></td><td>Filtering by account (or its parameters) was not supported for operations with contacts and calendars.</td><td>Extended filter features for operations with contacts and calendars.</td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31"><td><a name="7672f250-4639-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>HEIC images can be imported in the mobile 1C:Enterprise version running on Android 9 or later and on iOS 11 or later. After such import, HEIC images are converted into JPEG and stored in this format.<p>
</p></td><td>This feature was not provided.</td><td>Extended list of image formats that can be imported by mobile applications based on 1C:Enterprise platform.</td></tr></table><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127d9-e1af-11ec-aa69-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.23" class="tag_0"><a name="3b6c04a7-8ea1-11ee-963f-0050569f678a"></a>The libtiff library is updated to version 4.6.</li></ul><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127da-e1af-11ec-aa69-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.23" class="tag_0"><a name="fca76edc-82c4-11ed-963f-0050569f678a"></a>New example of how to use multiple value choice in the input field:<ul><li><span class="interface">Recipients </span>input field in the <span class="interface">Outgoing emails </span>catalog item form.</li><li>Multiple characteristic types in the <span class="interface">Goods </span>catalog form.</li><li>Quick choice is enabled for the <span class="interface">Characteristic </span><span class="interface">values </span>catalog. When you enter multiple characteristics, you can select their values from this catalog by selecting the check boxes in the drop-down list.</li></ul><p>New guide section: <span class="interface">Multiple input field values</span>.</p></li><li title="Версия 8.3.23" class="tag_0"><a name="720e6240-82c5-11ed-963f-0050569f678a"></a>New examples of how to use regular expressions:<ul><li>Check whether the email address is specified correctly in the Counterparties catalog upon saving.</li><li>Check whether the email address matches the template in the <span class="interface">Recipients </span>field of the Outgoing emails catalog.</li></ul><p>New guide section: <span class="interface">Regular expressions</span>.</p></li><li title="Версия 8.3.23" class="tag_0"><a name="5a1d7961-eb16-11ed-963f-0050569f678a"></a>Added an example of how to use NFC tags in the demo configuration for the mobile version:<ul><li>Implemented a command for saving NFC tags in an item form of the product catalog.</li><li>Implemented a command for scanning NFC tags to add a product to an order in the product selection form.</li></ul></li><li title="Версия 8.3.23" class="tag_0"><a name="f7948d65-eb1e-11ed-963f-0050569f678a"></a>Added an example of how to scan documents in an item form of the counterparty catalog.<p>
</p></li><li title="Версия 8.3.23" class="tag_0"><a name="13931bff-eb21-11ed-963f-0050569f678a"></a>Added examples of how to use the following features to objects designed for emails:<ul><li>Specify a form field property that indicates how to autofill the field on mobile devices (the <span class="interface">Email message sender name </span>field in the email settings form, only in the mobile client application).</li><li>Set up multiple value selection (in an outgoing email form, an item of the <span class="interface">Ad</span><span class="interface">dress</span> form).</li></ul></li></ul><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127db-e1af-11ec-aa69-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.23" class="tag_59"><td><a name="d77095c4-86b0-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>New property for a form field that displays a form attribute of the <span class="term">ValueList</span> or <span class="term">FormDataCollection</span> type: <span class="term">MultipleValuesExtendedEdit</span>. If the property is set to <span class="term">False</span>, the input field has the same features as in previous versions, except for displaying the collection content.<p>New properties for the input field that displays multiple values: <span class="term">TypeRestriction</span>, <span class="term">ChoiceParameters</span>, <span class="term">ChoiceParameterLinks</span>, <span class="term">TypeLink</span>.</p><p>New parameter for the choice form: <span class="term">ChoiceByAdding</span>. New parameter for the <span class="term">NotifyChoice()</span> method: <span class="term">ChoiceByAdding</span>. New parameter for the <span class="term">StartChoice </span>and <span class="term">ChoiceProcessing </span>event handlers of the form field extension for the input field: <span class="term">ChoiceByAdding</span>. These parameters will allow you to identify the mode of the form field that initiated adding of values.</p><p>If the selection using checkboxes is allowed for the input field that displays multiple values and the field data contains several values, the opened choice list will contain all the selected values with selected checkboxes.</p></td><td>This feature was not provided.<p>You were unable to change multiple value presentation in the input field without using the multiple value edit mode.</p><p>In events and methods for selecting values in the input field, you were unable to specify the multiple value mode for the field.</p></td><td>When using multiple values in the input field, you can now specify the field mode. You can also implement the previous behavior where the new behavior is not required.</td></tr><tr title="Версия 8.3.23" class="tag_30 tag_31 tag_48"><td><a name="4597ea5d-9675-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Now you need less time and effort to ensure that a document in the mobile device viewfinder is suitable enough for scanning (the document frame lights up green).<p>The algorithm for calculating the scanned document quality has been changed so that you can get a more evenly distributed value.</p><p>You will get a warning if the page you are trying to scan is already scanned.</p></td><td>Previously, you spent more time to ensure that the system accepts the quality of the document for scanning.<p>The algorithm for calculating the scanned document quality used to return values that were unevenly distributed within the valid value range.</p><p>You did not get any warning if you tried to scan an already scanned page.</p></td><td>Improved document scanning in 1C:Enterprise mobile version.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="190c20e0-b101-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The<span class="term"> GetDBStorageStructureInfo()</span> method returns a description of internal tables linked to the speech recognition tool.</td><td>The <span class="term">GetDBStorageStructureInfo() </span>method did not return tables linked to the speech recognition tool.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="b2d59736-b101-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The <span class="term">GetDBStorageStructureInfo() </span>method returns a description of internal tables linked to the collaboration system.</td><td>The<span class="term"> GetDBStorageStructureInfo() </span>method did not return tables linked to the collaboration system.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="dbcc00c5-cfa0-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now the <span class="term">GetDBStorageStructureInfo() </span>method returns a description of service tables related to the tool of database tablespace management.</td><td>Previously the <span class="term">GetDBStorageStructureInfo() </span>method did not return tables related to the tool of database tablespace management.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="465f7dce-c3e6-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now the <span class="term">GetDBStorageStructureInfo() </span>method returns a description of service tables related to collaboration system bots.</td><td>Previously the <span class="term">GetDBStorageStructureInfo() </span>method did not return tables related to collaboration system bots.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="b111986b-cfbb-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now the <span class="term">GetDBStorageStructureInfo() </span>method returns a description of service tables related to settings storage.</td><td>Previously the <span class="term">GetDBStorageStructureInfo() </span>method did not return tables related to settings storage.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.23" class="tag_31"><td><a name="a0962a97-b66f-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New features during automatic data synchronization by a mobile client with standalone mode:<ul><li>The device cannot switch to sleep mode during generation and initial import of standalone mode data, as well as during the first data exchange after configuration startup.</li><li>You can now click the status window at the bottom of the screen to see the exchange process status.</li></ul></td><td>The mobile device could go into sleep mode during the initial infobase filling with data. This caused situations when the application was running and the data in it was incomplete, inconsistent, or missing.<p>Displayed exchange process information was less user-friendly.</p></td><td>Improved automatic data synchronization for a mobile client in standalone mode.</td></tr><tr title="Версия 8.3.23" class="tag_32"><td><a name="a0150a8e-eb09-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile 1C:Enterprise version 8.3.23 is now supported in the mobile application builder.</td><td>Mobile 1C:Enterprise version 8.3.23 was not supported in the mobile application builder.</td><td>Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.</td></tr><tr title="Версия 8.3.23" class="tag_29 tag_19"><td><a name="93e94473-eb4a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 11.19.1</li><li>Postgres Pro Standard 11.19.1</li><li>Postgres Pro Enterprise 11.19.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.17 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 11.19.1</li><li>Postgres Pro Standard 11.19.1</li><li>Postgres Pro Enterprise 11.19.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_29 tag_19"><td><a name="093f5cde-eb4b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 12.14.1,</li><li>Postgres Pro Standard 12.14.1,</li><li>Postgres Pro Enterprise 12.14.1.</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 12.14.1,</li><li>Postgres Pro Standard 12.14.1,</li><li>Postgres Pro Enterprise 12.14.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_29 tag_19"><td><a name="2ab3fe2c-eb4b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 13.10.1</li><li>Postgres Pro Standard 13.10.1</li><li>Postgres Pro Enterprise 13.10.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 13.10.1</li><li>Postgres Pro Standard 13.10.1</li><li>Postgres Pro Enterprise 13.10.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_29 tag_19"><td><a name="485d6ce2-eb4b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 14.7.1</li><li>Postgres Pro Standard 14.7.1</li><li>Postgres Pro Enterprise 14.7.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 14.7.1</li><li>Postgres Pro Standard 14.7.1</li><li>Postgres Pro Enterprise 14.7.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_29 tag_19"><td><a name="621cb713-eb4b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 15.2.1</li><li>Postgres Pro Standard 15.2.1</li><li>Postgres Pro Enterprise 15.2.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 15.2.1</li><li>Postgres Pro Standard 15.2.1</li><li>Postgres Pro Enterprise 15.2.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_74 tag_10"><td><a name="c98af53f-044d-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented the legal access verification in a server infobase: now the system verifies whether you have legal rights to use the application at 1C:Enterprise level. To pass the verification, you need to configure the licensing client.<p>For more information on the licensing client settings, see the documentation.</p><p>For a separated infobase, the licensing client is configured only once. You do not need to set it up for each data area.</p></td><td>Previously the system verified whether you had legal rights to use the application at 1C:Enterprise level only when running in file mode or using the MINI server.</td><td>Now the system verifies whether you have legal rights to use the application in all infobase modes.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="23678976-1741-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can close active sessions in the infobase when updating the infobase configuration via the command-line. The process is similar to the interactive behavior of Designer. The list of situations when you can close sessions has not changed and is provided in the documentation.<p>New commands and parameters:</p><ul><li>New parameter for the<span class="term"> /UpdateDBCfg </span>command to run Designer in batch mode: <span class="term">SessionTerminate</span>.</li><li>New parameter for Designer running in the Agent mode and for the SSH gateway of the standalone server: <span class="term">--session-teminate</span> for the <span class="term">config update-db-cfg </span>command.</li><li>New possible values for the session-terminate parameter of the<span class="term"> infobase config apply </span>command of the standalone server administration utility (<span class="interface">ibcmd</span>). New default value for the<span class="term"> --session-terminate </span>parameter: <span class="term">disable</span>.</li><li>If you update the database configuration after the extension is updated, you can use the <span class="term">--session-terminate </span>parameter in the<span class="term"> infobase config apply </span>command.</li></ul></td><td>Previously you were unable to close active sessions in the infobase similarly to the interactive operation in Designer when you updated the infobase configuration via the command-line (Designer, agent, or the SSH gateway of the standalone server).</td><td>Unified behavior of different infobase configuration update options.</td></tr><tr title="Версия 8.3.23" class="tag_33"><td><a name="aad64ffa-19a2-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>In the help section of Designer and client application, you can find information on keyboard shortcuts for Mac computers.</td><td>Information on keyboard shortcuts for Mac computers was not provided in the help section of Designer and client application.</td><td>More informative help section.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="1813175e-19a3-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New mode for the administration console utility. In this mode, you can verify and repair only the tables of infobase data history. New startup command-line option for the <span class="interface">1cv8a</span> utility: <span class="term">--data-history-integrity</span>.</td><td>This feature was not provided.</td><td>Advanced features of the administration console utility.</td></tr><tr title="Версия 8.3.23" class="tag_20"><td><a name="c8c2e402-4188-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Now it takes less time to start the thin client from Designer in the client/server infobase.</td><td>Thin client startup from Designer in the client/server infobase was time-consuming.</td><td>Faster thin client startup from Designer in the client/server infobase.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="5185a27c-418f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 11.20.1 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li></ul><p>DBMS version bitness: x86-64.</p><p>The products are supported in 1C:Enterprise version 8.3.17 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="9e1a7f28-418f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 12.15.1 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="b1ed7afc-418f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 13.11.1 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise (version 13.11.2).</li><li>Postgres Pro Enterprise certified.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="dc8607c1-418f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 14.8.1 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li><li>Postgres Pro Enterprise certified.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="efcc923a-418f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 15.3.1 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li><li>Postgres Pro Enterprise certified.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_32"><td><a name="44880420-5eb1-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Changed the process of building iOS mobile applications. Now you can publish built applications in the AppStore.<p>To publish an application, rebuild it using the mobile application version 8.3.23.80 or later on the builder that comes with the mobile version used.</p></td><td>Mobile applications built by an earlier version of the mobile application builder failed validation in the AppStore and could not be published.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="13b176ff-76f6-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 11.21.2 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li></ul><p>DBMS version bitness: x86-64.</p><p>The products are supported in 1C:Enterprise version 8.3.17 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="2adb0b95-76f6-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 12.16.2 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="4133267b-76f6-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 13.12.2 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li><li>Postgres Pro Enterprise certified.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="4e64f0b1-76f6-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 14.9.2 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li><li>Postgres Pro Enterprise certified.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19"><td><a name="5d1f7f11-76f6-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS version 15.4.2 of the following products:<ul><li>Postgres Pro 1C.</li><li>Postgres Pro Standard.</li><li>Postgres Pro Enterprise.</li><li>Postgres Pro Enterprise certified.</li></ul><p>DBMS version bitness: x86-64.
The products are supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</p></td><td>This Postgres Pro DBMS version was not supported by 1C:Enterprise.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_22"><td><a name="c3027939-7718-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>If a memory shortage error is generated in Data accelerator during query execution, the copy of the Data accelerator database is disabled for 60 seconds. After the 60-second pause, Data accelerator queries are resumed. If memory shortage errors occur for 3 times sequentially (with an interval of 60 seconds), the copy of the Data accelerator database is completely disabled until the forced update.</td><td>Previously, the copy of the Data accelerator database was disabled before the forced update after the first memory shortage error.</td><td>1C:Enterprise attempts to maintain the performance of the copy of the Data accelerator database to perform simpler queries than the one that caused the error. When the load is reduced, operations with complex queries, which previously caused memory shortage errors, might be resumed.</td></tr><tr title="Версия 8.3.23" class="tag_19 tag_29"><td><a name="24b84098-9984-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Tantor SE 1C DBMS.<p>Supported versions: 14.8 and 15.4.</p><p>Supported processors: ARM64 and x86-64.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously, 1C:Enterprise did not support Tantor SE DBMS.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19 tag_29"><td><a name="0eaf7e9f-ca53-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Pangolin DBMS version 5.3.2.<p>Supported processors: x86-64.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously, 1C:Enterprise did not support Pangolin DBMS.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_19 tag_29"><td><a name="b18ec024-e123-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports Jatoba DBMS version 4.8.2-1117.<p>Supported processors: x86-64.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>Previously, 1C:Enterprise did not support Jatoba DBMS.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.23" class="tag_18 tag_29"><td><a name="e9c05acd-e13d-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The system now supports macOS versions 11, 12, 13, and 14.</td><td>Previously, 1C:Enterprise did not support macOS versions 11.4 and later.</td><td>Extended list of supported operating systems.</td></tr><tr title="Версия 8.3.23" class="tag_33"><td><a name="730c9a86-e789-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>The description of the OpenID authentication request when the OpenID server uses the second authentication factor check is now refined in the documentation.</td><td>Previously, the OpenID authentication request when the OpenID server uses the second authentication factor check was incorrectly described in the documentation.</td><td>Fixed error in the documentation.</td></tr><tr title="Версия 8.3.23" class="tag_10"><td><a name="ee79eefe-eda4-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New feature: intermediate certificates of the Federal Tax Service of the Russian Federation generated using the GOST R 34.11-2012 algorithms are added to the <span class="interface">cacert.pem</span> and <span class="interface">cacertnx.pem</span> files.</td><td>This feature was not provided.</td><td>The number of certificate check errors when accessing the websites of the Federal Tax Service of the Russian Federation is reduced.</td></tr><tr title="Версия 8.3.23" class="tag_20"><td><a name="2631fe24-fafe-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Now you can activate a developer license if you are registered on the 1C:Developer Network portal <a href="https://1c-dn.com/" target="_blank">Read more</a>..<p>If your localization language is Armenian, Azerbaijani, Georgian, Latvian, Kazakh, Russian, or Turkmen, the 1C for Developers portal (<a href="https://1c.ru/news/info.jsp?id=30506" target="_blank">read more</a>) will be used. For all other localization languages, you will be able to choose between these portals. The choice of the portal does not depend on the <span class="term">ExternalResourcesMode</span> parameter of the <span class="interface">conf.cfg</span> configuration file.</p><p>New parameter for the <span class="term">GetDeveloperLicenseAgreement()</span> method of the license acquisition manager: <span class="term">DeveloperPortal</span>. New property: <span class="term">LicenseAcquisitionRequest.DeveloperPortal</span>.</p></td><td>Previously, you were able to activate the developer license if you were registered only on the 1C for Developers portal (<a href="https://1c.ru/news/info.jsp?id=30506" target="_blank">read more</a>).</td><td>Users who cannot register on the 1C for Developers portal (<a href="https://1c.ru/news/info.jsp?id=30506" target="_blank">read more</a>) can get a developer license.</td></tr></table><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="801127dc-e1af-11ec-aa69-0050569f678a">Transition from the previous version to the version 8.3.23</a></h2><ul><li title="Версия 8.3.23" class="tag_0"><a name="801127dd-e1af-11ec-aa69-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.23.
</li><li title="Версия 8.3.23" class="tag_0"><a name="801127de-e1af-11ec-aa69-0050569f678a"></a>Some features that are added in version 8.3.23 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li></ul><p><a href="#801127d0-e1af-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h1><a name="717b9b8d-67e4-11ec-aa69-0050569f678a">Version 8.3.22</a></h1><p title="Версия 8.3.22" class="tag_0"><a name="717b9b9c-67e4-11ec-aa69-0050569f678a"></a>Version 8.3.22 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#717b9b8e-67e4-11ec-aa69-0050569f678a">New functionality and changes</a></li><li><a href="#717b9b8f-67e4-11ec-aa69-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#717b9b90-67e4-11ec-aa69-0050569f678a">Optimization</a></li><li><a href="#717b9b91-67e4-11ec-aa69-0050569f678a">Changes that affect system behavior</a></li><li><a href="#717b9b92-67e4-11ec-aa69-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#717b9b93-67e4-11ec-aa69-0050569f678a">Renamed objects</a></li><li><a href="#717b9b94-67e4-11ec-aa69-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#717b9b97-67e4-11ec-aa69-0050569f678a">Demo configuration changes</a></li><li><a href="#717b9b98-67e4-11ec-aa69-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#717b9b99-67e4-11ec-aa69-0050569f678a">Transition from the previous version to the version 8.3.22</a></li></ul><h2><a name="717b9b8e-67e4-11ec-aa69-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.22" class="compat tag_2 tag_1"><td><a name="bc987634-6870-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.21</span><span class="interface"> </span>is now implemented.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.20
was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.21 or earlier can now run on version 8.3.22 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.21 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.21 after the migration to version 8.3.22, even if you disable the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.22" class="tag_21"><td><a name="1fcfdd9e-7519-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>New version (2) of the full-text data search engine. This engine can use special algorithms for selecting root base and the list of stop words. Some search query features of the current full-text search version are not supported in the new version. New design for displaying full-text search results. Changes in the operation of the full-text search manager methods in the new full-text search version:<ul><li>The following methods are not used: <span class="term">GetCompositeWordsSeparationMode()</span> /<span class="term">SetCompositeWordsSeparationMode().</span></li><li>The <span class="term">UpdateIndex()</span> method starts indexing and immediately returns control. To manage indexing completion, use the <span class="term">IndexTrue()</span> method.</li><li>The <span class="term">IndexUpdateComplete() </span>method does not consider that full-text search indexes must be merged.</li></ul><p>New methods for the full-text search manager: <span class="term">GetFullTextSearchVersion()</span> /<span class="term">InstallFullTextSearchVersion().</span></p><p>New server cluster services:</p><ul><li>Full-text search service v2.</li><li>Full-text search coordination service v2.</li></ul><p>New technological log event: <span class="term">&lt;FTS&gt;</span></p><p>New command line parameter for the <span class="interface">ibsrv</span> utility:<span class="term"> --ftext2-data</span></p><p>The new full-text search version requires server cluster computers to have Java version 8 or later.</p><p>The standard data processor of full-text search management is revised.</p><p>The new full-text search version is supported for infobases in client/server mode. For a standalone server, it is also supported for infobases in file mode. In other modes, the new full-text search version is not supported.</p></td><td>1C:Enterprise contained only one full-text search engine option.</td><td>The new full-text search engine will:<ul><li>Improve the quality of search results.</li><li>Improve full-text search performance in large infobases.</li><li>Add new information from the infobase to an index more efficiently.</li><li>Prevent the following error: <span class="interface">Maximum number of words to search exceeded</span>.</li><li>Reduce the disk space occupied by the full-text search index.</li><li>Notify the user of multiple search results by displaying a warning instead of an error. Search results will be displayed anyway.</li></ul></td></tr><tr title="Версия 8.3.22" class="tag_36"><td><a name="98cb4127-7796-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>New feature: create random passwords that are easier to remember but still secure. New object: <span class="term">RandomPasswordGenerator</span>.<p>New feature: generate random passwords in the infobase user editing form and password recovery form.</p><p>New buttons to view the password value are implemented in the infobase user editing form, password input field, and password confirmation field. If you click <span class="interface">Generate password</span>, a new password will be displayed in clear text in the <span class="interface">Password</span> field.</p></td><td>This feature was not provided.<p>
</p></td><td>Simplified creation of unique passwords to use in various application subsystems and set authorization passwords for infobase users.</td></tr><tr title="Версия 8.3.22" class="tag_8"><td><a name="de784c1b-779a-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>New feature: cryptography is fully supported in client applications on macOS. The system supports CryptoPro cryptography tools (for macOS).</td><td>Cryptography support on macOS was limited.<p>
</p></td><td>New feature: cryptography is fully supported in client applications on macOS.</td></tr><tr title="Версия 8.3.22" class="tag_38"><td><a name="31eb9b27-785b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: change numeration properties for documents, business processes, tasks, and number generators.<p>New feature: create native number generators in extensions. New feature: set native and adopted number generators for native and adopted extension documents.</p><p>New feature: change code length for catalogs, tasks, exchange plans, charts of characteristic types, charts of accounts, and calculation charts.</p><p>New feature: change description length for catalogs, exchange plans, charts of characteristic types, charts of accounts, and calculation charts.</p></td><td>These features were not provided.<p>
</p></td><td>Advanced configuration extension features.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_36"><td><a name="0bdf1631-7861-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>New property: <span class="term">SystemInfo.ApplicationOption</span>. The property is used to identify special distribution options of 1C:Enterprise platform.</td><td>This feature was not provided.</td><td>New feature: define a special distribution option of 1C:Enterprise platform.</td></tr><tr title="Версия 8.3.22" class="tag_34"><td><a name="1cd8e58d-7866-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 34); return false;">PDF document operations</a>.<br></td><td>New method: <span class="term">PDFDocument.Show(). </span>Use this method to open a form to view a PDF document from 1C:Enterprise language.</td><td>To view a PDF document, you could either open the view form interactively or create your own form.<p>
</p></td><td>The <span class="term">PDFDocument</span> object allows you to open a form to view a document like other similar 1C:Enterprise language objects.</td></tr><tr title="Версия 8.3.22" class="tag_75 tag_38"><td><a name="8d819ddb-78fd-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 75); return false;">Distributed infobases</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: receive information about changes located in the data exchange package to be processed:<ul><li>Configuration</li><li>Configuration extensions</li><li>Configuration extensions that change data</li></ul><p>New methods for the exchange plan manager: <span class="term">ReadChangesDescription()</span> and <span class="term">ReadConfigurationAndConfigurationExtensionsChanges()</span><span class="term">.</span></p></td><td>This feature was not provided.<p>You could only receive information about the main configuration being different from the database configuration at the moment.</p></td><td>Improved troubleshooting for implementing automatic data exchange in systems that use a distributed infobase.</td></tr><tr title="Версия 8.3.22" class="tag_14 tag_10 tag_39"><td><a name="c10c1ea8-7903-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>New feature for OpenID Connect or USIA authentication: specify various values to identify infobase users (matching keys). These values are specified for each infobase user and linked to the authentication provider used in a certain case. Matching keys can have an arbitrary ID and value.<p>New property for the <span class="term">InfobaseUser</span> object: <span class="term">UsersMatchingKeys</span>. You can access this property only from 1C:Enterprise language.</p><p>New value for the <span class="term">authenticationUserPropertyName</span> field of the provider parameter details in the <span class="interface">default.vrd</span> file: <span class="term">matchingKey</span>. This value allows you to specify that a user is determined via a matching key upon authentication.</p><p>More detailed messages about errors that occur upon OpenID Connect or USIA authentication.</p></td><td>Upon OpenID Connect or USIA authentication, you could use a limited list of fields to determine an infobase user.<p>Messages about authentication errors were unclear and did not provide information on reasons of authentication issues.</p></td><td>Improved user matching upon OpenID Connect or USIA authentication. Improved troubleshooting of authentication issues.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_25"><td><a name="b490dae1-7905-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New feature: specify an appearance template to be used in all application reports by default. New feature: specify this template for the whole infobase or for a certain user. You can specify a system data appearance template or a data appearance template created as a common configuration template.<p>New configuration property: <span class="interface">Main report appearance template</span>. New global context property: <span class="term">ReportsAppearance</span>.</p></td><td>This feature was not provided.<p>You could specify an appearance template only for single reports in the application.</p></td><td>Improved report appearance features. You can apply the same appearance to all configuration reports, including those that will be added later and by other technicians.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_4 tag_10"><td><a name="fa3eb4a4-790d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New feature: create a collaboration system data export and restore data from a backup.<p>New feature: transfer data between different collaboration system server instances.</p><p>New methods for the collaboration system manager: <span class="term">GetDataExportsAsync()</span>, <span class="term">GetDataExports()</span>, <span class="term">GetDataExportAsync()</span>, <span class="term">GetDataExport()</span>, <span class="term">BeginCreateDataExportAsync()</span>, <span class="term">BeginCreateDataExport()</span>, <span class="term">GetDataExportAddressAsync()</span>, <span class="term">GetDataExportAddress()</span>, <span class="term">LoadDataExportAsync()</span>, <span class="term">LoadDataExport()</span>, <span class="term">RegisterDataExportAsync()</span>, <span class="term">RegisterDataExport()</span>, <span class="term">BeginRestoreFromDataExportAsync()</span>, <span class="term">BeginRestoreFromDataExport()</span>, <span class="term">DeleteDataExportAsync()</span>, <span class="term">DeleteDataExport()</span>, <span class="term">SetDataExportDescriptionAsync()</span>, <span class="term">SetDataExportDescription()</span>.</p><p>New feature for the standard <span class="interface">Collaboration system management</span> data processor: operate with data export and import.</p><p>The file format of the collaboration system data export is not documented.</p><p>The collaboration system can store a limited number of export files at the same time: not more than 5 copies. You can change this parameter using the collaboration server configuration tools.</p></td><td>These features were not provided.<p>You could not export collaboration system data and transfer data between different collaboration system server instances.</p></td><td>New features: Data transfer from one collaboration server (including a cloud server) to another one.<p>Export of all collaboration system data as one file.</p></td></tr><tr title="Версия 8.3.22" class="tag_34"><td><a name="55a3a44a-792f-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 34); return false;">PDF document operations</a>.<br></td><td>New feature: convert a PDF document so that the color scheme is converted into grayscale.<p>New commands in forms for operating with PDF documents allow you to execute this conversion. New methods for the <span class="term">PDFDocument</span> object: <span class="term">ConvertToGrayScaleAsync()</span>, <span class="term">ConvertToGrayScale()</span>.</p></td><td>This feature was not provided.<p>
</p></td><td>Advanced PDF document features.</td></tr><tr title="Версия 8.3.22" class="tag_34"><td><a name="957b5fdc-792f-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 34); return false;">PDF document operations</a>.<br></td><td>New property for the PDF document form field extension: <span class="term">UsedFileName</span>. You can use this property to specify a file name that will be used if a user decides to save a document displayed by the form field.<p>
</p></td><td>This feature was not provided.</td><td>Advanced PDF document features.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_69"><td><a name="8fdd22db-79e0-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>New property for attribute columns of the client application form of the <span class="term">ValueTable</span> and <span class="term">ValueTree</span> types: <span class="interface">Fill check</span> (<span class="term">FillChecking</span>). The check is executed by the client application form. The check is executed similarly to tabular sections of catalogs, documents, and so on.</td><td>You could execute the fill check for the client application form attributes of the <span class="term">ValueTable</span> or <span class="term">ValueTree</span> type only for the availability of at least one row. The fill check for attribute columns was not supported.</td><td>Improved automatic fill check for the client application form attributes of the <span class="term">ValueTable</span> or <span class="term">ValueTree</span> type.</td></tr><tr title="Версия 8.3.22" class="tag_38"><td><a name="18af0376-79f7-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: change localizable properties of configuration objects in the extension. You can change the following configuration objects: note, presentation and editing formats, tooltips, presentations of objects, records, and lists.<p>New feature: modify adopted common templates and configuration object templates.</p></td><td>You could not change localizable properties of objects and templates, except for spreadsheet documents.<p>
</p></td><td>Advanced configuration extension features.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_38"><td><a name="42056ccb-79f9-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New optional parameter for the <span class="term">ConfigurationExtensions.Create() </span>method: <span class="term">Data</span>. This method allows you to create an object of the <span class="term">ConfigurationExtension</span> type from the <span class="term">BinaryData</span> type value. For such <span class="term">ConfigurationExtension</span> object, the Data parameter is not required in the <span class="term">Write() </span>method.<p>New method: <span class="term">ConfigurationExtensions.ConfigurationExtensionsChanged(</span><span class="term">)</span>. It indicates that either the extension composition is changed or one of the existing extensions is updated after the current session is started.</p></td><td>You could not receive extension parameters without saving the extension to the database.<p>You could analyze whether the extension composition was changed or an extension was updated after the current session is started. You could do it by analyzing the hashes of session and infobase extensions.
</p></td><td>Advanced extension administration features.</td></tr><tr title="Версия 8.3.22" class="tag_45 tag_25"><td><a name="6162555e-7a85-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New feature in queries and data composition system: receive an infobase object reference UUID.<p>New function in query language and expression language of the Data composition system: <span class="term">UUID()</span>.</p></td><td>This feature was not provided.</td><td>New feature in queries and data composition system: receive an infobase object reference UUID.</td></tr><tr title="Версия 8.3.22" class="tag_10 tag_6"><td><a name="83c90252-7a90-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New feature: use the external session management service for file infobases. You can use the external session management service for a file infobase only with a PROF-level license.<p>New parameters for the <span class="interface">conf.cfg</span> configuration file: <span class="term">ExternalSessionManagementRequired</span> and <span class="term">ExternalSessionManagementConnectionString</span>.</p><p>New parameters for the <span class="term">synchronize()</span> method of the external session management web service: <span class="term">SessionNumber</span> and <span class="term">ClientIPAddress</span>. New properties for the <span class="term">Sessions</span> object: <span class="term">SessionNumber</span> and <span class="term">ClientIPAddress</span>. The new features are available only if the value of the <span class="term">wsver </span>parameter is 4.</p></td><td>This feature was not provided.<p>External session management was available only for infobases in client/server mode.</p></td><td>You can centrally manage the number of concurrently used licenses for different applications without modifying the applications themselves.</td></tr><tr title="Версия 8.3.22" class="compat tag_26 tag_1"><td><a name="9fbe0e2b-7a95-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Automatic column width calculation when displaying the report result in a spreadsheet document is executed as follows:<ul><li>Column width for the first 100 displayed rows is calculated accurately.</li><li>Column width for rows starting from 101 is not calculated automatically.</li></ul><p>This change is not implemented in 8.3.21 compatibility mode.</p><p>If you double-click the column separator, the column width is calculated according to the <span class="interface">Location</span> property. </p></td><td>Automatic column width calculation when displaying the report result in a spreadsheet document was executed as follows:<ul><li>For columns of the first displayed row, the width was calculated "accurately".</li><li>For the next 99 displayed rows, the width was calculated "approximately".</li><li>For rows starting from 101, the width was not calculated automatically.</li></ul><p>
</p></td><td>More accurate column width calculation in reports.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_26"><td><a name="ea95172a-7cf5-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>New spreadsheet document feature: set indents of the content from the borders of a cell/cell area. <p>New properties for the <span class="term">SpreadsheetDocumentCellsArea</span>, <span class="term">SpreadsheetDocumentDrawing</span>, <span class="term">DataCompositionAppearance</span>, <span class="term">DataCompositionAreaTemplateTableCellAppearance</span> objects: <span class="term">LeftIndent</span>, <span class="term">RightIndent</span>, <span class="term">TopIndent</span>, <span class="term">BottomIndent</span>. For the data composition system settings, these properties are available only for report settings.</p><p>Export to the following formats considers indents availability: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 or later, Microsoft Word 2007 or later), or ODS (OpenDocument).</p><p>
</p></td><td>This feature was not provided.</td><td>Improved report appearance features.
</td></tr><tr title="Версия 8.3.22" class="tag_26"><td><a name="d5930874-7cfd-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>New feature: get the row format of a spreadsheet document cell area.<p>New property: <span class="term">SpreadsheetDocumentCellsArea.RowsFormat</span>.</p><p>New <span class="term">RowsFormat</span> parameter for the <span class="term">Area() </span>and <span class="term">GetArea() </span>methods of the <span class="term">SpreadsheetDocument</span> object.</p></td><td>This feature was not provided.<p>
</p></td><td>Using 1C:Enterprise language, you can determine which row format is set for the selected cell area.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_19"><td><a name="625ce93f-e198-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Information that describes the data exchange table for mobile client with standalone mode is included in the data (the <span class="term">Purpose</span> field) returned by the <span class="term">GetDBStorageStructureInfo()</span> global context method.</td><td>This feature was not provided.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="ce71a639-f918-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following versions of PostgreSQL DBMS are supported now: 10.19, 11.14.<p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise version 8.3.14 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="15ee8a30-c244-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following versions of PostgreSQL DBMS are supported now: 10.20 and 11.15.<p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise version 8.3.14 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="57f69579-f917-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following versions of PostgreSQL DBMS are supported now: 10.21, 11.16.<p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise version 8.3.14 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="1d597a79-f919-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following versions of PostgreSQL DBMS are supported now: 12.9, 13.5, 14.1.<p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="12a2e514-e641-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following versions of PostgreSQL DBMS are supported now: 12.10, 13.6, and 14.2.<p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="82fa2e39-f917-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following versions of PostgreSQL DBMS are supported now: 12.11, 13.7, 14.3.<p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr></table><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b8f-67e4-11ec-aa69-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.22" class="tag_77"><td><a name="46f3898d-784a-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>On macOS, you can now print using internal operating system interfaces.<p>On macOS and Linux, the <span class="interface">Printer</span> button is hidden from all report forms.</p></td><td>On macOS, printing was performed by the platform tools.<p>On macOS and Linux, print forms contained the <span class="interface">Printer</span> button but clicking it had no effect as these operating systems do not allow opening a separate window with printer property settings.</p></td><td>Printing using familiar print tools is now available on iOS.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="44b8c210-785e-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: noncontext conversation search by a conversation title and full names of participants. To search, you can enter only several space-separated words. All the entered words must be found.</td><td>Only search by a conversation title was available.</td><td>Simplified noncontext conversation search when only a conversation participant (or participants) is known.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="9ebc1384-7ab3-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>
<p>Simplified monitor selection for screen sharing. You can select a monitor if several monitors are connected to the computer. The change is implemented only for thin and thick client applications.</p></td><td>Monitor selection for screen sharing was less clear and required more actions.</td><td>Simplified monitor selection for screen sharing.</td></tr><tr title="Версия 8.3.22" class="tag_26"><td><a name="1ec045e8-7ab4-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Extended area beyond which you can drag a spreadsheet document area.</td><td>The area beyond which you could drag a spreadsheet document area was smaller.</td><td>You can drag a spreadsheet document area more conveniently.</td></tr><tr title="Версия 8.3.22" class="tag_53 tag_28"><td><a name="5e8d3dc0-7aba-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>If you need to take a screenshot when generating an error report in Mozilla Firefox, you need to use a web browser extension for 1C:Enterprise.<p>If you do not have the web browser extension, you will see a warning that will prompt you to install the extension and specify the reason why it is required (taking a screenshot is time-consuming).</p></td><td>Taking a screenshot when generating an error report in Mozilla Firefox could take a long time.<p>
</p></td><td>If you need to attach a screenshot when generating an error report in web client, taking a screenshot will take less time. The change is applied only to web client in Mozilla Firefox.</td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="3bf56db2-7abf-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Improved user interface of the collaboration system and video call window.<p>New keyboard shortcut for the <span class="interface">Mark as read</span> command in the message list: <span class="interface">Ctrl + M</span>.</p><p>
</p></td><td>The user interface of the collaboration system and video call window was less convenient.</td><td>Improved user interface of the collaboration system and video call window.</td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="23926fd9-7d1c-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New features for the website that manages operations for external collaboration system users:<ul><li>Quote when responding to a message using a special command.</li><li>Mark a conversation as read using a special command. Configure the reading mark in the user settings.</li><li>View an image without downloading the image file to the local drive.</li><li>Select hardware to use during video calls in a special dialog box.</li><li>Edit the profile picture of the current user.</li><li>Copy attachments using the context menu.</li><li>Start video conferences in a more convenient window.</li></ul></td><td>These features were not provided.</td><td>Improved website that manages operations for external collaboration system users.</td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="2a3a1227-bb29-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Updated appearance of the video conference form and its buttons (expand to full view, and so on) in the collaboration system. Changed animation upon connecting a new user, reconnecting a user, and starting screen sharing.</td><td>The appearance of form buttons and animation in the video conference form of the collaboration system was different.</td><td>Improved video conference appearance.</td></tr><tr title="Версия 8.3.22" class="tag_31 tag_4"><td><a name="4c183377-f390-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Enhanced image quality during video calls if they are executed in mobile client using a video server.<p>Image quality is adjusted to the current processor load and video size on the mobile device screen.</p></td><td>Image quality during video calls did not depend on the processor load and video size on the mobile device screen.</td><td>Enhanced image quality during video calls in mobile client on mobile devices.<p>
</p></td></tr></table><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b90-67e4-11ec-aa69-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.22" class="tag_19"><td><a name="750902aa-72cc-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Receiving results of a query with multiple nested tables is improved.</td><td>Receiving results of a query with multiple nested tables was time-consuming.</td><td>Receiving results of a query with multiple nested tables takes less time.</td></tr><tr title="Версия 8.3.22" class="tag_19"><td><a name="813e85bd-72de-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Improved use of the <span class="term">IN(&lt;value list&gt;) </span>query language operator when using PostgreSQL DBMS. Execution of data access restriction queries takes less time.<p>It is recommended that you analyze query conditions and, if PostgreSQL DBMS is used, substitute the <span class="term">Var1=Var2 OR Var1=Var3 </span>expression for the <span class="term">Var1 IN (Var2, Var3)</span> expression.</p></td><td>Execution of queries with the <span class="term">IN(&lt;value list&gt;) </span>query language operator when using PostgreSQL DBMS took more time.</td><td>Improved performance of the <span class="term">IN(&lt;value list&gt;) </span>query language operator when using PostgreSQL DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_78"><td><a name="63e7e073-7471-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>File transfer operations between the client and the server take significantly less time.<p>The size of a file to be placed in the temporary storage is no longer restricted.</p></td><td>Transferring files between the client and the server took more time.<p>The size of a file to be placed in the temporary storage could not exceed 4 GB (in serialized form).</p></td><td>Improved file management characteristics in 1C:Enterprise.</td></tr><tr title="Версия 8.3.22" class="tag_38 tag_6"><td><a name="ee728234-7474-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Reduced RAM consumption by server cluster working processes when using extensions in a shared infobase.</td><td>When using extensions in a shared infobase, server cluster working processes consumed more RAM.</td><td>Reduced RAM consumption by server cluster working processes when using extensions in a shared infobase.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_6"><td><a name="28005059-7477-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved efficiency of session data repository operations.<p>
</p></td><td>Operations with the session data repository were not efficient.</td><td>No loss of server cluster performance if the server cluster stores large amounts of data in the session data repository.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_20"><td><a name="63056c50-7478-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Faster configuration export to a CF file.</td><td>Configuration export to a CF file took more time.</td><td>Faster configuration export to a CF file.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_20"><td><a name="249aafc3-7479-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Configuration comparison takes less time.<p>Application configuration update takes less time. Reduced RAM consumption in 32-bit Designer upon configuration update.</p></td><td>The operations of configuration comparison and update took more time.<p>32-bit Designer consumed more RAM upon configuration update.</p></td><td>Configuration comparison and update take less time.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_21"><td><a name="13bdb38e-7865-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Execution of full-text search query with the <span class="term">AND</span> operator takes less time. Full-text search index must be rebuilt to achieve better performance.</td><td>Execution of full-text search queries with the <span class="term">AND</span> operator was more time-consuming.<p>
</p></td><td>Improved performance of full-text search queries with the <span class="term">AND</span> operator.</td></tr><tr title="Версия 8.3.22" class="tag_21"><td><a name="0f00a206-792d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Improved full-text search reliability:<ul><li>The occurrence of large index files with high fragmentation is prevented.</li><li>Merging indexes in large infobases takes less time.</li></ul><p>
</p></td><td>Creation of large index files could lead to file system errors.</td><td>Improved full-text search engine reliability.</td></tr><tr title="Версия 8.3.22" class="tag_20"><td><a name="773b2e3b-792e-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Reduced RAM consumption when opening the <span class="interface">All roles</span> form in Designer.<p>
</p></td><td>When opening the <span class="interface">All roles</span> form in Designer, RAM consumption was high.<p>
</p></td><td>Reduced RAM consumption when opening the <span class="interface">All roles </span>form in Designer.</td></tr><tr title="Версия 8.3.22" class="tag_10"><td><a name="dc093679-7a84-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Improved receipt of the user authentication lock list. Time required to receive the lock list no longer depends on the number of infobase users.</td><td>Time required to receive the user authentication lock list depended on the number of infobase users.</td><td>Improved performance of the <span class="interface">Administration – Authentication locks</span> commands in Designer and of the <span class="term">AuthenticationLock.GetLocks() </span>1C:Enterprise language method.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_21"><td><a name="f359a370-7a85-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>
<p>If file errors related to index files occur when indexing full-text search data, the full-text search index remains correct.</p></td><td>If file errors related to index files occurred when indexing full-text search data, the full-text search index could no longer be used.</td><td>Improved full-text search stability upon data indexing.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_38 tag_6"><td><a name="aebff4ad-7a89-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Reduced RAM consumption by a server cluster working process if the working process serves a distributed infobase with distributed extensions that affect the user interface.</td><td>RAM consumption by a server cluster working process was excessive if the working process served a distributed infobase with distributed extensions that affect the user interface.</td><td>Reduced RAM consumption by a server cluster that serves distributed infobases with extensions that affect the user interface.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_79"><td><a name="5773271d-bbd4-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>Accessing properties of the<span class="term"> PictureLib </span>object (as well as accessing the same property sequentially) takes less time.</td><td>Accessing properties of the <span class="term">PictureLib</span> object took more time.</td><td>Improved performance of operations with 1C:Enterprise picture library. In particular, now it takes less time to open the <span class="interface">Functions for technician</span> form in configurations with large volumes of metadata.</td></tr></table><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b91-67e4-11ec-aa69-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.22" class="tag_19"><td><a name="e3b9347f-72e1-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>1C:Enterprise sets the row-level lock granularity for Microsoft SQL Server 2008 or later. Lock escalation is prevented. RAM consumption by Microsoft SQL Server might increase.</td><td>1C:Enterprise set the page-level lock granularity for Microsoft SQL Server.</td><td>Locks when different users operate with different database objects that occur on the same DBMS index page are prevented.</td></tr><tr title="Версия 8.3.22" class="tag_39"><td><a name="77f3bdb0-72e3-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>The event log cannot be converted to SQLite format.<p>This event log format will no longer be supported in later 1C:Enterprise versions.</p><p>It is recommended that you convert the event log to sequential format.</p></td><td>1C:Enterprise supported the ability to convert the registration log into the SQLite format</td><td>1C:Enterprise is prepared to stop supporting the SQLite format of the event log.</td></tr><tr title="Версия 8.3.22" class="tag_65 tag_14"><td><a name="eae4c660-7374-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>If the connection is lost when calling a web service, a catchable exception is thrown.<p>If the client application runs over HTTP, loss of connection opens a standard error dialog box that allows you to retry the uncompleted action.</p></td><td>If the connection was lost when calling a web service, the application froze.<p>When the client application ran over HTTP, loss of connection caused the application to hang.
</p></td><td>Improved client application responsiveness when running over HTTP and using web services in case of unstable network connection.</td></tr><tr title="Версия 8.3.22" class="tag_6"><td><a name="fd63bd50-746e-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Revised procedure of server cluster monitoring. Improved stability of the cluster and connected users. Performance indicators are also estimated for working processes running on the same working server. Monitoring does not stop even when one of the working processes freezes. When the number of main servers increases, the load on working processes does not increase.<p>New properties of the <span class="term">&lt;ATTN&gt;</span> and <span class="term">&lt;CLSTR&gt;</span> events.</p></td><td>Performance indicators were not estimated for working processes running on the same working server. Cluster monitoring stopped when one of the working processes froze. When the number of main servers increased, the load on working processes also increased.<p>
</p></td><td>Improved stability of the server cluster and users served by it.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_36"><td><a name="7bbd555b-7794-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>For the <span class="term">RandomNumberGenerator</span> object, the random number generator is used in accordance with standard NIST SP 800-90A (Hash_DRBG algorithm). A number sequence after creating two different random number generator objects using the same beginning number will be different.</td><td>For the <span class="term">RandomNumberGenerator</span> object, the Mersenne twister algorithm was applied.</td><td>Improved random number generator.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_38"><td><a name="87d8d2b8-7910-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New additional checks for the <span class="interface">"Extension applicability test"</span> command in Designer:<ul><li>Check whether a method specified in the annotation exists.</li><li>Check whether the number of method parameters and the number of value transfer modifiers match in the method of the main configuration and extension.</li></ul><p>These checks are executed for methods that are not event handlers.</p></td><td>This feature was not provided.</td><td>Simplified correction of issues that occur when an extended method no longer exists in the main configuration or the number of parameters or parameter transfer modifiers changed.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_14"><td><a name="37df7de2-7a84-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>In thin client, if a server call is not completed within 400 msec, the mouse cursor changes to "busy". The upgrade is ignored in thick client.</td><td>In thin and thick client applications, the mouse cursor changed to "busy" when starting a server call.</td><td>The mouse cursor change displays a long server call but the cursor does not blink upon numerous short server calls.<p>
</p></td></tr><tr title="Версия 8.3.22" class="compat tag_59 tag_1"><td><a name="857e4490-7aa1-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>If a font is generated from another font and the size of the new font is specified, the base font size and scale are not used to determine the new font characteristics.<p>This change is not implemented in 8.3.21 compatibility mode.</p><p>A text for which 0 font size is set is always displayed by 13 pt font size in all client applications and on the server.</p></td><td>If a font was generated from another font and the size of the new font was specified, the base font size and scale were used to determine the new font characteristics.<p>A text for which 0 font size was set was displayed differently in different client applications.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="compat tag_25 tag_1"><td><a name="a1adcb0e-7db6-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If one available data composition filter field is generated from several fields, its <span class="term">LinkByType</span> and <span class="term">ChoiceForm</span> properties are filled in. They are filled in only if these properties of all the fields used for the generation contain the same values. The new data composition filter field is generated by merging fields in a query or by receiving several fields using dot syntax for different reference types. Besides, the <span class="term">ChoiceParameters</span> and <span class="term">ChoiceParametersLinks</span> properties of the available field are filled in so that the resulting links and parameters receive only links and parameters that exist in all the fields included in the available field and have matching property values.<p>This change is not implemented in 8.3.21 compatibility mode.</p></td><td>If one available data composition filter field is generated from several fields, its <span class="term">LinkByType</span>, <span class="term">ChoiceForm, ChoiceParameters</span>, and <span class="term">ChoiceParametersLinks</span> properties were filled in from the first field with the filled value of the respective property. The new data composition filter field is generated by merging fields in a query or by receiving several fields using dot syntax for different reference types.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_11 tag_28"><td><a name="5ba1d124-a13b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>New feature: add-ins running in a web browser under Linux support operations in Russian even if the OS does not have the Russian localization.<p>To ensure that add-ins support this feature, they must be rebuilt with new adapter libraries.</p></td><td>Add-ins running in a web browser under Linux caused errors when the OS did not have the Russian localization.</td><td>You can use add-ins, file system and cryptography extensions in web client running under Linux that does not have the Russian localization.</td></tr><tr title="Версия 8.3.22" class="tag_27"><td><a name="4861a376-a383-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is 2.15.</td><td>The format version of configuration dump to XML files was 2.14.</td><td>Configuration dump to XML files supports new platform features.</td></tr><tr title="Версия 8.3.22" class="tag_27"><td><a name="bd0b41a6-a399-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>In XDTO package describing data types of the current configuration, the minimum value is set to 0 for all attributes that belong either to a group or an item of the hierarchical chart of characteristic types.</td><td>In XDTO package describing data types of the current configuration, the minimum value was set to 1 for all attributes that belonged either to a group or an item of the hierarchical chart of characteristic types.</td><td>Eliminated unexpected system behavior.<p>Upon XDTO serialization of objects of the hierarchical chart of characteristic types, attributes that belong either to a group or an item are displayed correctly.</p></td></tr><tr title="Версия 8.3.22" class="compat tag_26 tag_25 tag_1"><td><a name="bf658146-a39c-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New feature: when exporting a spreadsheet document to various formats, you can manage the quality of pictures that are placed in the spreadsheet document.<p>New spreadsheet document property: <span class="term">SavedPicturesDensity</span>. New parameter for the list of data composition output parameters (the <span class="term">DataCompositionOutputParameterValues </span>type): <span class="term">SavedPicturesDensity</span>. New object: <span class="term">DataCompositionAreaDocumentTemplate</span>. The first template placed in the data composition template for a spreadsheet document is the <span class="term">DataCompositionTemplateAreaTemplateDefinition </span>object. This template is placed in the body of the data composition template.</p><p>When exporting a spreadsheet document in Office OpenXML (<span class="interface">*.docx</span>) format, pictures are saved in DrawingML format.</p><p>If the <span class="term">SavedPicturesDensity </span>parameter is not set for the data composition system, the composer of the data composition template sets this parameter to <span class="term">High</span>. In 8.3.21 compatibility mode, the composer sets the parameter to <span class="term">Original</span>.</p><p>If you know that a report or a spreadsheet document contains pictures that should be used in the original quality (for example, they will be saved to files and edited), set the <span class="term">SavedPicturesDensity </span>property to <span class="term">Original</span>.</p><p>This change is not implemented in 8.3.21 compatibility mode.</p></td><td>This feature was not provided. Pictures were saved in the initial format.<p>When exporting a spreadsheet document in Office OpenXML (<span class="interface">*.docx</span>) format, pictures were saved in VML format.</p></td><td>You can control the size of the file that resulted from a spreadsheet document export to another format.</td></tr><tr title="Версия 8.3.22" class="tag_38"><td><a name="8eee4ea8-b402-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Reduced RAM consumption if an extension contains numerous roles and adopted objects.<p>Faster session startup if an extension contains numerous roles and adopted objects.</p><p>Reduced number of similar messages about access restrictions upon extension of roles.
</p></td><td>RAM consumption by the application was greater if a configuration extension contained numerous roles and adopted objects. <p>Session startup took more time if an extension contained numerous roles and adopted objects.</p><p>When an extension was applied, numerous similar messages about access restrictions upon extension of roles were generated.</p></td><td>RAM consumption by the application was greater if a configuration extension contained numerous roles and adopted objects. <p>Session startup took more time if an extension contained numerous roles and adopted objects.</p><p>When an extension was applied, numerous similar messages about access restrictions upon extension of roles were generated.</p></td></tr><tr title="Версия 8.3.22" class="compat tag_60 tag_1"><td><a name="adcbd633-bb08-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br></td><td>When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the <span class="term">Picture</span> objects now behave as follows:<ul><li>If the <span class="term">PictureSize</span> property value is not <span class="term">Tile</span>, an original picture is saved to the resulting document. If a pattern is specified for a cell, pattern picture is also saved.</li><li>If the <span class="term">PictureSize</span> property is set to <span class="term">Tile</span>, a picture is redrawn into the resulting document and the background color of a Microsoft Excel document picture becomes the same as the one of the source document picture.</li></ul><p>As a result of these changes, pictures in a spreadsheet document become less distorted when scaling a Microsoft Excel document.</p><p>This change is not implemented in version 8.3.21 compatibility mode.</p></td><td>When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the <span class="term">Picture</span> objects behaved as follows:<ul><li>When the<span class="term"> PictureSize</span> property value was not <span class="term">Stretch</span>, a picture was redrawn into the resulting document.</li><li>When the <span class="term">PictureSize</span> property value was set to <span class="term">Stretch</span>, a picture was redrawn to the resulting document if a background color or pattern was not set. Otherwise, an original picture was saved.</li></ul><p> </p></td><td>The result of saving a spreadsheet document in Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats meets expectations of users to a greater extent.</td></tr><tr title="Версия 8.3.22" class="tag_34"><td><a name="fdbc04a7-bb08-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 34); return false;">PDF document operations</a>.<br></td><td>If a PDF document contains pictures in JPEG 2000 format, they are displayed when you view this document using 1C:Enterprise platform tools.</td><td>If a PDF document contained pictures in JPEG 2000 format, they were not displayed when viewing this document using 1C:Enterprise platform tools.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_30 tag_31"><td><a name="78267eac-bb27-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Updated user notification behavior in the mobile version of 1C:Enterprise:<ul><li>To close a notification, you need to click it.</li><li>If a notification allows performing an action, the right part of the notification displays a picture.</li><li>When displaying a notification, the application attempts to place it so that it does not overlap (or overlaps as little as possible) form controls that a user might use. In any case, the application attempts to display a notification in the lower third of the screen on a mobile device.</li></ul></td><td>User notification behavior in the mobile version of 1C:Enterprise had the following distinctive features:<ul><li>To close a notification, you had to swipe it.</li><li>If a notification allowed performing an action, you could perform it by clicking the notification. If a notification contained no action, clicking the notification navigated you back to the opened form.</li><li>A notification had a fixed location on the screen.</li></ul></td><td>Now the user notification behavior in the platform is highly similar to the notification behavior in the mobile operating system. Notifications are now more convenient to use.</td></tr><tr title="Версия 8.3.22" class="tag_25"><td><a name="dfce0609-c627-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a report parameter contains a value of the <span class="term">ValueList</span> type, then value presentation settings specified by the user are used when generating the parameter presentation:<ul><li>Presentation of each list value is generated considering conditional appearance and available values.</li><li>Empty values are displayed by the <span class="interface">&lt;Empty value&gt;</span> string.</li><li>Value presentations are separated by a semicolon ";".</li></ul><p>
</p><p>
</p></td><td>Value presentation settings specified by the user were not used to generate the presentation of a report parameter with a value of the<span class="term"> ValueList</span> type.</td><td>Presentation of a report parameter that contains a value list is generated similarly to other report parameters.</td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="509c9129-c62e-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Enhanced image quality during video calls from external users of the collaboration system.</td><td>Image quality during video calls from external users of the collaboration system was insufficient.</td><td>Enhanced image quality during video calls. Reduced load on slow client computers.</td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="277b289a-e0bc-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The <span class="term">CollaborationSystemUser.InfoBaseUserID </span>property can be written now.<p>To change the <span class="term">InfoBaseUserID</span> and <span class="term">MatchingKey</span> properties of the <span class="term">CollaborationSystemUser</span> object, the user must have the <span class="term">DataAdministration</span> access rights.</p></td><td>The <span class="term">CollaborationSystemUser.InfoBaseUserID</span> property could not be written.<p>To change the <span class="term">CollaborationSystemUser.MatchingKey</span> property, the user did not require any special access rights.</p></td><td>Loss-free data transfer between different collaboration system servers.</td></tr></table><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b92-67e4-11ec-aa69-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.22" class="tag_80"><td><a name="fb38c405-737d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 80); return false;">External reports and data processors</a>.<br></td><td>New parameter for the <span class="term">Connect()</span> method of the external data processor manager: <span class="term">LanguageCode</span>. You can use this parameter to specify the current language for an external data processor to be connected.</td><td>This feature was not provided.<p>When connecting an external data processor, the current language of the authenticated user was used. The language code is returned by the <span class="term">CurrentLanguage()</span> global context method.</p></td><td>Open external data processors in the required localization language.</td></tr><tr title="Версия 8.3.22" class="tag_22 tag_74 tag_6"><td><a name="cc0353dd-78f2-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New feature: start several Data Accelerator instances within one server cluster. New feature: control the possibility of creation of several Data Accelerator instances using permissive and prohibitive functionality assignment rules.<p>PROF-level license allows you to use only one Data Accelerator instance in one server cluster. CORP-level license allows you to use an unlimited number of Data Accelerator instances in one server cluster.</p></td><td>Within one 1C:Enterprise server cluster.</td><td>Load balance among several Data Accelerator instances. Improved performance of queries that use Data Accelerator.</td></tr><tr title="Версия 8.3.22" class="tag_59 tag_10"><td><a name="9cde7d23-79dc-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When saving form settings for another user (not the current one), new settings are applied in less than 20 seconds after saving. Form settings are settings that are located in the system settings storage and have a suffix of the /<span class="term">FormSettings</span> settings key.<p>
</p><p>
</p></td><td>Form settings copied to another user were applied only after disconnecting from the infobase if this form had already been opened in a session by the user to which the settings were copied.</td><td>Simplified copying of form settings to other infobase users.</td></tr><tr title="Версия 8.3.22" class="compat tag_69 tag_1"><td><a name="e6cb5b7d-79dd-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>If you specify an error processing method when creating the <span class="term">NotifyDescription() </span>object, this method receives management only when an error occurs within an asynchronous call where the created <span class="term">NotifyDescription</span> object is passed.<p>This change is not implemented in 8.3.21 compatibility mode.</p></td><td>If you specified an error processing method when creating the <span class="term">NotifyDescription()</span> object, this method received management in two cases. First case: an error occurred during an asynchronous call. Second case: an error occurred when executing a method that was called after an asynchronous call had been completed.<p>
</p></td><td>Eliminated unexpected system behavior.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="5ae27b22-79de-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The <span class="term">CollaborationSystemInfobaseRegistrationData</span> object is now available in thin and web clients.</td><td>The <span class="term">CollaborationSystemInfobaseRegistrationData</span> object was available only in thick client and on the server. When passing a value of this type from the server to the thin client, the value was available as a value of the <span class="term">BinaryData</span> type on the client side.<p>
</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="compat tag_25 tag_1"><td><a name="d29df64f-79e9-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If the <span class="interface">"Text"</span> appearance parameter (specified in appearance of the data set field of the data composition schema) is used in report templates of the data composition system, the parameter value is displayed in a report.<p>This change is not implemented in 8.3.21 compatibility mode.</p><p>It is recommended that you analyze the <span class="interface">"Text"</span> appearance parameter use. If the data set field settings contain filled parameters that are not supposed to be displayed, clear their check boxes.</p></td><td>The <span class="interface">"Text"</span> appearance parameter (specified in appearance of the data set field of the data composition schema) was not used when displaying a report if a field with the same parameter was used in report templates of the data composition system.<p>
</p></td><td>Eliminated unexpected system behavior.<p>
</p></td></tr><tr title="Версия 8.3.22" class="compat tag_25 tag_1"><td><a name="d7d1652a-79ea-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The <span class="interface">"Mark negatives"</span> appearance parameter (specified in appearance of the data set field of the data composition schema) is used in report templates of data composition system and dynamic list templates. The <span class="term">NegativeTextColor</span> style color is used in a report template cell of data composition system and the dynamic list if the field to be displayed contains a negative value. In data composition template in cell appearance, an expression of the data composition system template is created for the <span class="term">TextColor </span>appearance parameter.<p>This change is not implemented in 8.3.21 compatibility mode.</p></td><td>The <span class="interface">"Mark negatives"</span> appearance parameter (specified in appearance of the data set field of the data composition schema) was used in report templates of data composition system and dynamic list templates. The <span class="term">NegativeTextColor</span> style color was used in a report template cell and in the dynamic list of data composition system only if the cell contained a text where the first significant character was "-". The <span class="term">MarkNegatives</span> parameter was created in the data composition template in the data composition appearance.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_63"><td><a name="367100f6-79ec-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The <span class="term">"Update"</span> chart property is considered obsolete for Managed application mode. In web client, the property does not affect the chart behavior.</td><td>In thin client, the<span class="term"> "Update" </span>chart property did not affect chart generation. In web client, the property operated correctly.</td><td>The difference in chart behavior in web and thin clients is eliminated.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_65 tag_81 tag_10"><td><a name="8991ac92-7aa2-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Improved performance of calling a web service method by optimizing the selection of a session suitable for call execution. There is no limit on session pool size. All web service calls are executed at once.<p>In the <span class="interface">default.vrd</span> file, the <span class="term">poolSize</span> and <span class="term">poolTimeout</span> attributes are deleted for items describing web services, HTTP services, and standard OData Interface.</p></td><td>When calling a web service, there was a limit on pool size of sessions that executed calls.<p>
</p></td><td>Improved performance of web service calls.</td></tr><tr title="Версия 8.3.22" class="compat tag_10 tag_1"><td><a name="8d8fd2d0-bb06-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>According to the <span class="term">SetUserPasswordMinLength() </span>method, a user password cannot contain less than 0 and more than 99 characters. If the restriction is violated, an exception is thrown. This change is not implemented in version 8.3.21 compatibility mode.<p>If the infobase checks user password complexity, the lower limit for password length is the maximum value of 7 and the specified minimum password length.</p><p>If the specified <span class="interface">"Minimum user password length"</span> infobase parameter exceeds 99, value 99 is used. This change is not implemented in version 8.3.21 compatibility mode.</p><p>If you clear the <span class="interface">"Password complexity check"</span> check box in the dialog box to set up infobase parameters, the <span class="interface">"Minimum user password length"</span> parameter value is not changed.</p></td><td>The <span class="term">SetUserPasswordMinLength()</span> method did not impose restrictions on the minimum user password length.<p>When receiving a value of the <span class="interface">"Minimum user password length"</span> infobase parameter, the platform did not control the received value.</p><p>When you cleared the <span class="interface">"Password complexity check"</span> check box in the dialog box to set up infobase parameters, the <span class="interface">"Minimum user password length"</span> parameter was set to 0.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_10"><td><a name="5a5e369a-bb07-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The default value for the <span class="term">IgnoreServerCertificatesChainRevocationSoftFail</span> parameter of the <span class="interface">conf.cfg</span> file is<span class="term"> True</span>.</td><td>The default value for the <span class="term">IgnoreServerCertificatesChainRevocationSoftFail</span> parameter of the <span class="interface">conf.cfg</span> file was <span class="term">False</span>.</td><td>Now you can establish HTTPS connection (without additional system settings) if one or several servers with certificate revocation lists are unavailable.</td></tr><tr title="Версия 8.3.22" class="tag_28 tag_29"><td><a name="3a1cb1e0-c0a0-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following web browsers are no longer supported:<ul><li>Microsoft Edge version 18 or earlier.</li><li>Microsoft Internet Explorer 10.</li></ul></td><td>The following web browsers were supported in web client:<ul><li>Microsoft Edge version 18 or earlier.</li><li>Microsoft Internet Explorer 10.</li></ul></td><td>Obsolete web browsers are no longer supported.</td></tr><tr title="Версия 8.3.22" class="tag_28 tag_29 tag_20"><td><a name="3d84cde0-c0af-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Microsoft Edge version 19 or later running Linux, macOS, and Windows is supported.<p>Video calls in Microsoft Edge version 64 or later are supported.</p><p>Progressive web applications in Yandex Browser and Microsoft Edge version 73 or later are supported.</p><p>New feature: debugging for web client in Yandex Browser and Microsoft Edge.</p></td><td>These features were not provided.</td><td>Extended list of supported web browsers.<p>New system features that you can use in web client.</p></td></tr><tr title="Версия 8.3.22" class="tag_21"><td><a name="b89dd4ad-e0c3-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>New parameter for the <span class="interface">conf.cfg</span> configuration file: <span class="term">FtsJavaOpts</span>. You can use it to configure settings of Java Virtual Machine used by full-text search version 2.</td><td>This feature was not provided.</td><td>You can set up Java Virtual Machine used by full-text search version 2.</td></tr><tr title="Версия 8.3.22" class="tag_80"><td><a name="ab7f94f7-e7cf-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 80); return false;">External reports and data processors</a>.<br></td><td>New parameter for the <span class="term">Attach() </span>method of the external report manager: <span class="term">LanguageCode</span>. Use this parameter to specify a language to be used as the current one in the attached external report.</td><td>This feature was not provided.<p>The current language of authenticated user was used when attaching an external report. The code of this language was returned by the <span class="term">CurrentLanguage()</span> global context method.</p></td><td>You can now open external reports in a required localization language.</td></tr><tr title="Версия 8.3.22" class="tag_56"><td><a name="c559efe8-119f-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>When you import the XSD schema to the XDTO package, for properties whose items are included in the <span class="term">choice </span>content model in the XSD schema description, values defined for these items in the XSD schema are specified as minimum values.</td><td>When you imported the XSD schema to the XDTO package, the minimum value was always set to 0 for properties whose items were included in the <span class="term">choice </span>content model in the XSD schema description.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b93-67e4-11ec-aa69-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.22" class="tag_0"><td><a name="32671be8-7529-11ec-aa69-0050569f678a"></a>English name for the <span class="term">SystemOfLinearEquationsCalculation.SolveSystemOfLinearEquations()</span> method.<p>
</p></td><td><ul><li><span class="term">SolveSystemOfLinearEquations</span>.</li></ul></td><td><ul><li><span class="term">SolveSystemsOfLinearEquations</span>.</li></ul><p>
</p></td></tr><tr title="Версия 8.3.22" class="compat tag_0 tag_1"><td><a name="a52d2492-7798-11ec-aa69-0050569f678a"></a>English name of the following appearance parameters of the data composition system:<ul><li><span class="term">MaximumHeight</span></li><li><span class="term">MaximumWidth</span></li><li><span class="term">MinimumHeight</span></li><li><span class="term">MinimumWidth</span></li></ul><p>To ensure compatibility, both new and former names will be used for parameter search from 1C:Enterprise language and import from XML.</p><p>In 8.3.21 (or later) compatibility mode, the former parameter names will be used for the English version of 1C:Enterprise language when exporting to XML.</p><p>
</p></td><td>
<ul><li><span class="term">MaximumHeight</span></li><li><span class="term">MaximumWidth</span></li><li><span class="term">MinimumHeight</span></li><li><span class="term">MinimumWidth</span></li></ul><p>
</p><p>
</p></td><td><ul><li><span class="term">MaxHeight</span></li><li><span class="term">MaxWidth</span></li><li><span class="term">MinHeight</span></li><li><span class="term">MinWidth</span></li></ul></td></tr><tr title="Версия 8.3.22" class="tag_0"><td><a name="b9af013a-792d-11ec-aa69-0050569f678a"></a>English name of the <span class="term">NotifyDescription</span> property of the client application form.</td><td><ul><li><span class="term">NotifyDescription</span>.</li></ul><p>
</p></td><td><ul><li><span class="term">CallbackDescription</span>.</li></ul><p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_0"><td><a name="f16d6bc5-792d-11ec-aa69-0050569f678a"></a>English name of the <span class="term">ExecuteNotifyProcessing</span> global context method.</td><td><ul><li><span class="term">ExecuteNotifyProcessing</span>.</li></ul><p>
</p></td><td><ul><li><span class="term">RunCallback</span>.</li></ul><p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_0"><td><a name="3350d6b3-792e-11ec-aa69-0050569f678a"></a>English name of the <span class="term">OnCloseNotifyDescription</span> property of the client application form.</td><td><ul><li><span class="term">OnCloseNotifyDescription</span>.</li></ul><p>
</p></td><td><ul><li><span class="term">CallbackDescriptionOnClose</span>.</li></ul></td></tr><tr title="Версия 8.3.22" class="tag_0"><td><a name="4e0c9292-e0c3-11ec-aa69-0050569f678a"></a>New parameter of the <span class="interface">conf.cfg</span> file that allows you to set up Java Virtual Machine to use the optimized restructuring feature.</td><td><ul><li><span class="term">JavaOpts</span></li></ul><p>
</p></td><td><ul><li><span class="term">RestructJavaOpts</span></li></ul></td></tr></table><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b94-67e4-11ec-aa69-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.22" class="tag_31"><td><a name="1eec3ba2-7d19-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New feature for mobile client in the standalone mode: automatically synchronize data with the main server. When editing standalone configuration data, you can specify that an object takes part in automatic exchange. Also, you can specify whether object changes need to be registered for automatic exchange purposes. New dialog box to configure automatic exchange with a standalone configuration.<p>New event handlers for the exchange plan object module: <span class="term">OnAutoCreateNewNode()</span>, <span class="term">BeforeCreateInitialImage()</span>, <span class="term">BeforeSendDataToSubordinate()</span>, <span class="term">BeforeSendDataToMaster()</span>.</p><p>New standard attribute for the exchange plan: <span class="term">ExchangeDate</span>.</p><p>New global context property: <span class="term">DataExchangeWithMainServer</span>.</p><p>New application module event handler: <span class="term">AfterDataExchangeWithMainServer()</span>.</p></td><td>This feature was not provided. Synchronization could be executed only in 1C:Enterprise language.</td><td>Simplified exchange between mobile client in the standalone mode and the main server.</td></tr><tr title="Версия 8.3.22" class="tag_26"><td><a name="8729b9b2-a39d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>New feature in the mobile platform: view a spreadsheet document using the <span class="term">SpreadsheetDocument.Show()</span> method or interactive opening.</td><td>This feature was not provided.<p>
</p></td><td>View external spreadsheet documents in mobile platform applications.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_31"><td><a name="8abd394e-a43b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New feature for mobile client in the standalone mode: switch a collaboration system call to background mode. If you switch a call to background mode, the video stream will no longer be transmitted from your mobile device. On iOS, this feature is available starting from version 10. On Android, this feature is available on all supported versions.<p>New feature for mobile client: share your own screen and view the screen of another device using the collaboration system video stream. The screen is demonstrated even when the application is not active. On iOS, this feature is available starting from version 12. On Android, this feature is available on all supported versions.</p><p>New functionality for the list of used mobile device functionalities: <span class="interface">Video conference</span>.</p></td><td>Participation in a video call stopped after collapsing the mobile client application, switching to another application, or locking the device.<p>The screen demonstration used another protocol.</p><p>
</p></td><td>You can continue a call after switching the mobile application to background mode. New feature: you can share not only the mobile application screen but also the device screen. Improved performance when sharing the device screen.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_31"><td><a name="f0aa1664-cc89-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>If a report form is used in mobile client in standalone mode when connection with the main server is lost, then:<ul><li>A spreadsheet document field is not locked in the report form. Report form settings and commands become unavailable.</li><li>Commands for saving and printing a report become available.</li><li>Report decryption is not supported in this mode.</li><li>When opening a standalone report form, the current report form is not closed. If you select the <span class="interface">Open online</span> command, the offline report form is closed.</li><li>If the report is generated in background on the server, the report form displays the result after connection is restored. If generation is not completed, the report form waits for generation to be completed.</li></ul></td><td>When a report form was used in mobile client in standalone mode and connection with the main server was lost:<ul><li>The entire report form became unavailable for editing.</li><li>When opening the offline report form, the online report form was closed.</li></ul><p>
</p><p>
</p><p>
</p></td><td>More user-friendly report behavior in mobile client after switching to standalone mode.</td></tr></table><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b97-67e4-11ec-aa69-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.22" class="tag_0"><a name="8328295a-f919-11ec-aa69-0050569f678a"></a>In the mobile demo configuration, data exchange between the main infobase and standalone infobases is implemented using a built-in platform functionality.</li><li title="Версия 8.3.22" class="tag_0"><a name="e44e4759-f919-11ec-aa69-0050569f678a"></a>In the mobile demo configuration, the <span class="interface">"Order analysis" report</span> is replaced with a regular one.</li><li title="Версия 8.3.22" class="tag_0"><a name="50031efc-f93a-11ec-aa69-0050569f678a"></a>In the demo configuration, the <span class="interface">"Stock balance in warehouses"</span> report form is selected programmatically depending on the used client.<p>
</p></li><li title="Версия 8.3.22" class="tag_0"><a name="a317bc9c-f93a-11ec-aa69-0050569f678a"></a>The <span class="interface">"Order analysis"</span> report can be used in standalone mode to analyze local data.<p>
</p></li></ul><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b98-67e4-11ec-aa69-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.22" class="tag_30 tag_31 tag_48"><td><a name="74838c77-f787-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Calls and text messages can be processed in the mobile application built for Android. To apply this feature, rebuild your mobile application using the mobile version 8.3.22 and configuration exported by Designer version 8.3.22.<p>If necessary, specify hint texts for the required mobile application functionality.</p></td><td>Calls and text messages in the mobile application built for Android could not be processed even when the mobile application functionality to be used was specified correctly.</td><td>Eliminated unexpected system behavior.<p>
</p></td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="8bfdd450-1265-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following version of PostgreSQL DBMS is supported now:14.4.
DBMS version bitness: x86-64.
The version is supported in 1C:Enterprise version 8.3.18 or later.
Supported operating systems are defined by a DBMS vendor.</td><td>This PostgreSQL DBMS version was not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_73"><td><a name="55f80c57-3331-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>The <span class="term">MergeCfg</span> command in Designer batch mode is executed faster. The new command execution time matches the execution time of respective interactive operation.</td><td>Execution of the <span class="term">MergeCfg</span> command in Designer batch mode took more time.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_56"><td><a name="2737715d-3333-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>New method for the <span class="term">XDTODataObject</span> and <span class="term">XDTODataValue</span> objects: <span class="term">Factory()</span>. The method returns an object of the <span class="term">XDTOFactory</span> type that was used to create an object or value in use.<p>When operating with XDTO objects (and saving them to XML), use one factory instance for all used objects.</p></td><td>This feature was not provided.</td><td>If required, you can get an <span class="term">XDTOFactory</span> object that was used to create an XDTO object or value.</td></tr><tr title="Версия 8.3.22" class="tag_29"><td><a name="c95957ad-3334-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>1C:Enterprise platform now supports the 64-bit architecture of ARM processors including Baikal processors.<p>1C:Enterprise for ARM processors does not support:</p><ul><li> Windows operation for ARM processors.</li><li>HASP dongles (only software licensing is supported).</li><li>Processors Apple M1 and later.</li><li>Elbrus processors.</li><li>Automatic update of client applications for thin client distribution packages intended for ARM processors.</li><li>Operations in the following DBMS:</li></ul><p>New system enumeration value: <span class="term">PlatformType.Linux_ARM_64</span>.</p><p>(<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>)add-in development technology has been changed.</p><p>CORP license is required for 1C:Enterprise operation on ARM processors.</p></td><td>1C:Enterprise could not operate in systems running on ARM processors.</td><td>Extended list of devices supported by 1C:Enterprise.</td></tr><tr title="Версия 8.3.22" class="tag_11 tag_28"><td><a name="1fce5edf-3337-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Extensions for file operations and cryptography are now supported in Yandex.Browser, Chromium-gost, and Microsoft Edge.<p>Documentation on (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>) add-in development technology has been changed.</p><p>Extension manifests and add-in adapters are installed in the following directories (registry keys):</p><ul><li>Linux:</li></ul><p><span class="interface">~/.config/yandex-browser/NativeMessagingHosts</span>
<span class="interface">~/.config/chromium-gost/NativeMessagingHosts</span>
<span class="interface">~/.config/chromium/NativeMessagingHosts</span>
<span class="interface">~/.config/microsoft-edge/NativeMessagingHosts</span></p><ul><li>macOS:</li></ul><p><span class="interface">/Library/Application Support/Chromium/NativeMessagingHosts</span></p><ul><li>Windows (information on file location is recorded):</li></ul><p><span class="interface">HKEY_CURRENT_USER\SOFTWARE\Chromium\NativeMessagingHosts</span>
<span class="interface">HKEY_CURRENT_USER\SOFTWARE\Microsoft\Edge\NativeMessagingHosts</span></p></td><td>Extensions for file operations and cryptography were not supported for web client in Yandex.Browser, Chromium-gost, and Microsoft Edge.<p>Extension manifests and add-in adapters were installed in the following directories (registry keys):</p><ul><li>Linux:</li></ul><p><span class="interface">~/.config/google-chrome/NativeMessagingHosts</span>
<span class="interface">~/.mozilla/native-messaging-hosts</span></p><ul><li>macOS:</li></ul><p><span class="interface">/Library/Application Support/Mozilla/NativeMessagingHosts</span>
<span class="interface">/Library/Google/Chrome/NativeMessagingHosts</span></p><ul><li>Windows (information on file location is recorded):</li></ul><p><span class="interface">HKEY_CURRENT_USER\SOFTWARE\Google/Chrome\NativeMessagingHosts</span>
<span class="interface">HKEY_CURRENT_USER\SOFTWARE\Mozilla\NativeMessagingHosts</span></p></td><td>Extended web client features in Yandex.Browser, Chromium-gost, and Microsoft Edge.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="ae81a98b-3348-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 10.21</li><li>Postgres Pro Standard 10.21.1</li><li>Postgres Pro Enterprise 10.21.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.16 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 10.21</li><li>Postgres Pro Standard 10.21.1</li><li>Postgres Pro Enterprise 10.21.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="e35bdd73-3348-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 11.16</li><li>Postgres Pro Standard 11.16.2</li><li>Postgres Pro Enterprise 11.16.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.16 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 11.16</li><li>Postgres Pro Standard 11.16.2</li><li>Postgres Pro Enterprise 11.16.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="0af5fed9-3349-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 12.11</li><li>Postgres Pro Standard 12.11.2</li><li>Postgres Pro Enterprise 12.11.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 12.11</li><li>Postgres Pro Standard 12.11.2</li><li>Postgres Pro Enterprise 12.11.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="2560b76b-3349-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 13.7</li><li>Postgres Pro Standard 13.7.2</li><li>Postgres Pro Enterprise 13.7.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 13.7</li><li>Postgres Pro Standard 13.7.2</li><li>Postgres Pro Enterprise 13.7.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="496d8895-3349-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 14.4</li><li>Postgres Pro Standard 14.4.1</li><li>Postgres Pro Enterprise 14.4.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 14.4</li><li>Postgres Pro Standard 14.4.1</li><li>Postgres Pro Enterprise 14.4.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_4"><td><a name="b179060e-334b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The storage scheme of separator values has been changed for some collaboration system objects in a distributed infobase.<p>After migration to version 8.3.22, collaboration system bots will be activated after one of the following events:</p><ul><li>Connection to a client application infobase.</li><li>Call to the collaboration system from a server cluster.</li></ul></td><td>The storage scheme of separator values for some collaboration system objects was different.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_30 tag_31 tag_48"><td><a name="562dce62-3364-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>
<p>You can interactively manage the camera backlight in the mobile application interface used for barcode scanning after calling the <span class="term">MultimediaTools.ShowBarcodeScanning()</span> method. The backlight control button depends on whether the device has backlight and light sensor features. Backlight state is preserved between sessions.</p></td><td>This feature was not provided.<p>Camera backlight could be enabled only automatically. That did not allow users to enable it on devices without a light sensor.</p></td><td>Simplified barcode scanning by built-in tools in case of insufficient lighting on devices with supported camera backlight, but without a light sensor.
</td></tr><tr title="Версия 8.3.22" class="tag_6"><td><a name="a0283604-4638-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Performance of administration operations via the administration server (<span class="interface">ras</span>) has been improved.<p>The frequency and duration of periods when administration server connections might conflict with exclusive infobase access have been reduced.
</p></td><td>Administration operations via the administration server (<span class="interface">ras</span>) took more time.<p>Connection to a server cluster established by the administration server (<span class="interface">ras</span>) could result in more conflicts with exclusive infobase access.</p></td><td>Improved performance of server cluster administration operations via the administration server (<span class="interface">ras</span>).</td></tr><tr title="Версия 8.3.22" class="tag_47"><td><a name="384f267f-4a00-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>New commands for the SSH gateway of the standalone server:<ul><li><span class="term">config </span><span class="term">dump-external-data-processor-or-report-to-files</span>. Dump an external report or data processor to XML files.</li><li><span class="term">config </span><span class="term">load-external-data-processor-or-report-to-files</span>. Load an external report or data processor from XML files.
New parameter for <span class="term">infobase config export </span>commands to specify the location of an external data processor or configuration: <span class="term">--file</span>.
New parameter for <span class="term">infobase config import </span>commands to specify the location of an external data processor or configuration: <span class="term">--out</span>.</li></ul><p>
</p></td><td>These features were not provided.</td><td>Extended standalone server features related to external reports and data processors.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="d58ff094-6f08-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 10.22.1</li><li>Postgres Pro Standard 10.22.1</li><li>Postgres Pro Enterprise 10.22.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.16 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 10.22.1</li><li>Postgres Pro Standard 10.22.1</li><li>Postgres Pro Enterprise 10.22.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="00262ddc-6f09-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 11.17.1</li><li>Postgres Pro Standard 11.17.1</li><li>Postgres Pro Enterprise 11.17.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.16 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 11.17.1</li><li>Postgres Pro Standard 11.17.1</li><li>Postgres Pro Enterprise 11.17.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="292ee436-6f09-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 12.12.1</li><li>Postgres Pro Standard 12.12.1</li><li>Postgres Pro Enterprise 12.12.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 12.12.1</li><li>Postgres Pro Standard 12.12.1</li><li>Postgres Pro Enterprise 12.12.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="4afba6bc-6f09-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 13.8.1</li><li>Postgres Pro Standard 13.8.1</li><li>Postgres Pro Enterprise 13.8.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 13.8.1</li><li>Postgres Pro Standard 13.8.1</li><li>Postgres Pro Enterprise 13.8.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="5ef72266-6f09-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 14.5.1</li><li>Postgres Pro Standard 14.5.1</li><li>Postgres Pro Enterprise 14.5.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 14.5.1</li><li>Postgres Pro Standard 14.5.1</li><li>Postgres Pro Enterprise 14.5.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_15"><td><a name="2fde9685-6fb4-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>New supported Linux distribution packages:<ul><li>Debian 11</li><li>Mint 21</li><li>Oracle Linux 9</li><li>RHEL 9</li><li>Ubuntu 22.04 LTS</li></ul></td><td>The distribution packages were not supported.<p>
</p></td><td>Extended list of supported Linux distribution packages.</td></tr><tr title="Версия 8.3.22" class="tag_15 tag_29"><td><a name="5d330bbb-6fb4-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following distribution packages for Linux operating system are no longer supported: <ul><li>Debian 9</li></ul></td><td>1C:Enterprise supported the following distribution packages for Linux operating system: <ul><li>Debian 9</li></ul></td><td>Outdated Linux distribution packages are no longer supported.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_30 tag_31"><td><a name="09fe9545-6fd5-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Mobile applications built using the mobile 1C:Enterprise version 8.3.22.40 will meet Google Play store requirements related to uploading of new applications with in-app purchases.<p>For a mobile application to be uploaded to Google Play store, it must be built using the mobile 1C:Enterprise version 8.3.22.40 or later.</p></td><td>Starting from November 1, 2022, you will not be able to upload mobile applications with in-app purchases to Google Play store if such applications are built using mobile 1C:Enterprise versions earlier than 8.3.22.40.</td><td>The mobile 1C:Enterprise version meets Google Play store requirements.</td></tr><tr title="Версия 8.3.22" class="tag_31 tag_30"><td><a name="81b0b92f-7165-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>The list of root certificates has been extended.</td><td>Fewer root certificates were supported.</td><td>Extended list of supported root certificates.</td></tr><tr title="Версия 8.3.22" class="tag_47"><td><a name="5721cbce-82c0-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>Standalone server shutdown is improved.</td><td>Previously, standalone server shutdown took more time.</td><td>Accelerated standalone server restart after infobase configuration update.</td></tr><tr title="Версия 8.3.22" class="tag_30 tag_31 tag_48"><td><a name="305d4a6e-59e9-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Statistics library versions for the mobile platform and mobile client have been updated.</td><td>The mobile platform and mobile client contained outdated versions of statistics libraries.</td><td>Updated statistics library versions that meet Google Play store requirements.</td></tr><tr title="Версия 8.3.22" class="tag_29"><td><a name="ed25d242-86b7-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Now 1C:Enterprise platform supports Elbrus-8S processors.<ul><li>1C:Enterprise for Elbrus processors does not support:</li></ul><p>Windows.</p><ul><li>HASP dongles (only software licensing is supported).</li><li>Thin client distribution packages assembled for Elbrus processors in automatic update tools of client applications.</li><li>DBMS:</li><ul><li>IBM Db2.</li><li>Microsoft SQL Server.</li><li>Oracle</li><li>Data accelerator.</li></ul><li>Local speech recognition.</li></ul><p>Implemented a new system enumeration value: <span class="term">PlatformType.Linux_E2K</span>.</p><p>Changed the development technology for URL1 add-ins.</p><p>To use 1C:Enterprise for Elbrus processors, you need to acquire a CORP license.</p></td><td>Previously, 1C:Enterprise did not support systems running on Elbrus processors.</td><td>Extended list of devices supported by 1C:Enterprise.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="9d97e3fe-b0e1-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft SQL Server 2022 is now supported.</td><td>Microsoft SQL Server 2022 was not supported.</td><td>New Microsoft SQL Server version is now supported.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="0065cd4b-b1b5-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 10.23.1</li><li>Postgres Pro Standard 10.23.1</li><li>Postgres Pro Enterprise 10.23.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.16 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 10.23.1</li><li>Postgres Pro Standard 10.23.1</li><li>Postgres Pro Enterprise 10.23.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="1dc7defb-b1b5-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 11.18.1</li><li>Postgres Pro Standard 11.18.1</li><li>Postgres Pro Enterprise 11.18.2</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.16 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 11.18.1</li><li>Postgres Pro Standard 11.18.1</li><li>Postgres Pro Enterprise 11.18.2</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="822d1135-b1b5-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 12.13.1,</li><li>Postgres Pro Standard 12.13.1,</li><li>Postgres Pro Enterprise 12.13.2.</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 12.13.1,</li><li>Postgres Pro Standard 12.13.1,</li><li>Postgres Pro Enterprise 12.13.2.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="989a988d-b1b5-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 13.9.1</li><li>Postgres Pro Standard 13.9.1</li><li>Postgres Pro Enterprise 13.9.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 13.9.1</li><li>Postgres Pro Standard 13.9.1</li><li>Postgres Pro Enterprise 13.9.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="c217f2a9-b1b5-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 14.6.1</li><li>Postgres Pro Standard 14.6.1</li><li>Postgres Pro Enterprise 14.6.1</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 14.6.1</li><li>Postgres Pro Standard 14.6.1</li><li>Postgres Pro Enterprise 14.6.1</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19"><td><a name="d4f829c5-b1b5-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 15.1.1</li><li>Postgres Pro Standard 15.1.1</li><li>Postgres Pro Enterprise 15.1.1</li><li>DBMS version bitness: x86-64.</li></ul><p>The versions are supported in 1C:Enterprise 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 15.1.1</li><li>Postgres Pro Standard 15.1.1</li><li>Postgres Pro Enterprise 15.1.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="9ea1c834-c3cb-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 10.22.<p>Supported processors: x86, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.14 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="ad14ed18-c3cb-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 11.17.<p>Supported processors: x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.14 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="d2337d48-c3cb-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 12.12.<p>Supported processors: x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="fa01fd1a-c3cb-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 13.8.<p>Supported processors: x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="0af575f8-c3cc-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 14.5.<p>Supported processors: x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="8a71d282-c3c7-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 10.23.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.14 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="9fe0a5e4-c3c7-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 11.18.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.14 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="b4616efe-c3c7-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 12.13.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="aadf8dc6-c3ca-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 13.9.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="c3813cd8-c3ca-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 14.6.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="cff6f9d0-c3ca-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 15.1.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="6c8dfe8e-c3c6-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 11.19.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.14 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="9295d642-c3c6-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 12.14.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="a905befc-c3c6-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 13.10.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="d7a051a4-c3c6-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 14.7.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_19 tag_29"><td><a name="e5e89da4-c3c6-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following PostgreSQL DBMS version is supported now: 15.2.<p>Supported processors: ARM64, E2k, x86-64.</p><p>The version is supported in 1C:Enterprise version 8.3.18 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p></td><td>These PostgreSQL DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_37"><td><a name="192da875-cf8c-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>When the <span class="term">HTTPConnection</span>, <span class="term">WSDefinitions</span>, <span class="term">WSProxy</span>, and <span class="term">WSReferences </span>object are used on Linux and macOS, you can now use Kerberos authentication. This feature is implemented in the thick client and on the server.</td><td>When the <span class="term">HTTPConnection</span>, <span class="term">WSDefinitions</span>, <span class="term">WSProxy</span>, and <span class="term">WSReferences </span>object were used on Linux and macOS, you could not use Kerberos authentication. This authentication type was supported only on Windows.</td><td>When the <span class="term">HTTPConnection</span>, <span class="term">WSDefinitions</span>, <span class="term">WSProxy</span>, and <span class="term">WSReferences </span>object are used on Linux and macOS, you can use Kerberos authentication.</td></tr><tr title="Версия 8.3.22" class="tag_21"><td><a name="ee22d539-cf8d-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Accelerated full-text search. Decreased the load on the processor upon searching.</td><td>Full-text search took more time to find a result and significantly loaded the processor.</td><td>Accelerated full-text search.</td></tr><tr title="Версия 8.3.22" class="tag_78"><td><a name="686158b8-91ac-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>In thick client, the <span class="term">BeginPutFile()</span>, <span class="term">BeginPuttingFiles()</span>, <span class="term">BeginPutFileToServer()</span>, <span class="term">BeginPutFilesToServer()</span>, <span class="term">PutFileToServerAsync()</span>, and <span class="term">PutFilesToServerAsync()</span> methods are executed on the main thread, but remain asynchronous. As a result, when these methods are executed, the user interface update is locked, but method programming interface keeps running.</td><td>Executing the <span class="term">BeginPutFile()</span>, <span class="term">BeginPuttingFiles()</span>, <span class="term">BeginPutFileToServer()</span>, <span class="term">BeginPutFilesToServer()</span>, <span class="term">PutFileToServerAsync()</span>, and <span class="term">PutFilesToServerAsync()</span> methods in thick client could cause unexpected application shutdown.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_10 tag_70 tag_15"><td><a name="5dcf9d64-de05-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Now you can install 1C:Enterprise on Linux using RPM and DEB packages. The packages contain all the system components. To install or remove the application, use the package manager of the used operating system.<p>New parameters for the <span class="interface">conf.cfg </span>file: <span class="term">PublishDistributiveLocationLinuxDeb64</span>, <span class="term">PublishDistributiveLocationLinuxDeb32</span>, <span class="term">PublishDistributiveLocationLinuxRpm64</span>, and <span class="term">PublishDistributiveLocationLinuxRpm32</span>.</p><p>New attributes for the point item of the <span class="interface">default.vrd</span> file: <span class="term">pubdstlindeb32</span>, <span class="term">pubdstlindeb64</span>, <span class="term">pubdstlinrpm32</span>, and <span class="term">pubdstlinrpm64</span>.</p><p>New parameters for the <span class="term">pubdst </span>parameter of the <span class="term">http </span>section of the standalone server configuration file: <span class="term">lindeb64</span>, <span class="term">lindeb32</span>, <span class="term">linrpm64</span>, and <span class="term">linrpm32</span>.</p><p>Installation using the RUN file (the installer) will be supported and available along with the package files.</p><p>
</p></td><td>Previously 1C:Enterprise applications were distributed as RUN packages.</td><td>Advanced options to install 1C:Enterprise components on Linux.</td></tr><tr title="Версия 8.3.22" class="tag_20"><td><a name="e91275e4-df4d-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Now you can enable debugging over HTTP if the 1C:Enterprise server cluster is configured to start automatically on Linux. To enable the debugging protocol, use the <span class="term">SRV1CV8_DEBUG </span>parameter of the server cluster configuration file.</td><td>Previously if the 1C:Enterprise server cluster on Linux was configured to start automatically upon the operating system startup, the HTTP debugging protocol was not supported. Only the TCP debugging protocol was supported.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.22" class="tag_29 tag_19 tag_65"><td><a name="5237d67b-eb4a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>The following versions of Postgres Pro DBMS are supported now:<ul><li>Postgres Pro 1C 11.18.1</li><li>Postgres Pro Standard 11.18.1</li><li>Postgres Pro Enterprise 11.18.2</li></ul><p>DBMS version bitness: x86-64.</p><p>The versions are supported in 1C:Enterprise 8.3.16 or later.</p><p>Supported operating systems are defined by a DBMS vendor.</p><p>
</p></td><td>The following versions of Postgres Pro DBMS were not supported:<ul><li>Postgres Pro 1C 11.18.1</li><li>Postgres Pro Standard 11.18.1</li><li>Postgres Pro Enterprise 11.18.2.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.22" class="tag_82"><td><a name="6661e371-3341-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Improved features when operating with accounting registers:<ul><li>The query that is executed when filter by extra dimensions is applied in the <span class="term">Filter </span>parameter of virtual tables of the accounting register and in case of unspecified<span class="term"> ExtDimensionTypes</span> parameter has been optimized.</li><li>The query that is executed when filters by date range including period adjustment are applied in virtual tables has been optimized.</li></ul></td><td>Some queries to accounting registers were not optimal.</td><td>Faster data acquisition from accounting registers.</td></tr><tr title="Версия 8.3.22" class="tag_75"><td><a name="5e49c69b-3342-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 75); return false;">Distributed infobases</a>.<br></td><td>When operating with a distributed infobase, objects are exported to the file of changes in the following order:<ul><li>Constants</li><li>Charts of characteristic types</li><li>Charts of accounts</li><li>Charts of calculation types</li><li>Catalogs</li><li>Other reference objects of the infobase (without defined sequence)</li><li>Register record sets (without defined sequence)</li><li>Calculation register records</li><li>Sequence data</li></ul></td><td>When operating with a distributed infobase, the export order to the file of changes was undefined.</td><td>Decreased number of inconsistent infobase states during exchange (before its completion) due to defined exchange order.</td></tr><tr title="Версия 8.3.22" class="tag_44"><td><a name="0ddb68e3-3346-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 44); return false;">Infobase verification and repair</a>.<br></td><td>During infobase verification and repair, logical and referential integrity check of an infobase can be performed for specific object types (constants, catalogs, documents, and so on). Regardless of selected object types, some checks are still performed for all object types. <p>New parameter values for the <span class="term">-LogIntegrity</span> and <span class="term">-LogAndRefsIntegrity</span> parameters of the <span class="term">/IBCheckAndRepair</span> command:</p><ul><li><span class="term">Constants</span></li><li><span class="term">Catalogs</span></li><li><span class="term">Documents</span></li><li><span class="term">DocumentJournals</span></li><li><span class="term">ChartsOfCharacteristicTypes</span></li><li><span class="term">ExchangePlans</span></li><li><span class="term">ChartsOfAccounts</span></li><li><span class="term">ChartsOfCalculationTypes</span></li><li><span class="term">InformationRegisters</span></li><li><span class="term">AccumulationRegisters</span></li><li><span class="term">AccountingRegisters</span></li><li><span class="term">CalculationRegisters</span></li><li><span class="term">BusinessProcesses</span></li><li><span class="term">Tasks</span></li><li><span class="term">Other</span></li></ul></td><td>This feature was not provided.</td><td>Logical and referential integrity check of an infobase can be performed more precisely by required object types.</td></tr><tr title="Версия 8.3.22" class="tag_11"><td><a name="031e10b0-2147-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>When you attach and install an add-in using the <span class="term">AttachAddIn()</span>, <span class="term">InstallAddIn()</span>, or <span class="term">AttachAddInAsync()</span> methods, the add-in file is cached as earlier. At the same time, for add-ins that are attached from infobase data, data changes are tracked. The check is performed when the add-in is attached but no more than once per second. If the data is changed since the last add-in attachment, add-in cache is cleared for this add-in. Next time the add-in is attached, it is extracted from the data again. For metadata objects without a record version, cache is cleared when you access the data but no more than once per second.</td><td>Previously, when you attached and installed an add-in using the <span class="term">AttachAddIn()</span>, <span class="term">InstallAddIn()</span>, or <span class="term">AttachAddInAsync()</span> methods, the add-in file was cached in a temporary directory on the server to improve the performance when reusing the add-in. However, if the add-in was obtained from the infobase, you could not understand that the add-in version in the cache had become different from the add-in version in the infobase until you restarted the client application.</td><td>Improved add-in management.</td></tr><tr title="Версия 8.3.22" class="tag_6 tag_29 tag_15"><td><a name="0c308d15-2bbc-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Now the server cluster on Linux always requires a server license in the same way as the server cluster on Windows.</td><td>Previously, the server cluster on Linux allowed running up to 12 client sessions without a server license if the server cluster consisted of one production server with one working process.</td><td>Now you cannot use the server cluster on Linux without a license. Unexpected system shutdown due to the lack of a 1C:Enterprise server cluster license is eliminated.</td></tr><tr title="Версия 8.3.22" class="tag_77 tag_83"><td><a name="ec2dbffa-417f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br><a href="#" onclick="onTagClick(this, 83); return false;">HTML support</a>.<br></td><td>Now you can save print settings for an HTML document field to the system settings storage in thin and thick client applications. The settings are saved when you change them in the Print options dialog box for an HTML document field and are read before you open the Print options dialog box, as well as when you print/preview an HTML document field.</td><td>This feature was not provided.
An HTML document field was always printed with the default settings.</td><td>Now it is more convenient to print data from an HTML document field as the previously specified settings will be used and you will not have to specify them again every time.</td></tr><tr title="Версия 8.3.22" class="tag_14"><td><a name="a85bacdb-5c5f-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>New parameters that define traffic compression modes between the client and the server cluster for the<span class="term"> /TComp </span>command-line option of the thin client: <span class="term">lz4 </span>and <span class="term">zstd</span>. The default value is <span class="term">zstd</span>.</td><td>The default traffic compression parameter was <span class="term">-SDC</span>.</td><td>Now you can more flexibly manage traffic compression between the client application and the 1C:Enterprise server cluster.<p>In <span class="term">-zstd </span>compression mode, the amount of traffic transmitted between the client and the 1C:Enterprise server cluster is reduced.</p></td></tr><tr title="Версия 8.3.22" class="tag_19"><td><a name="001f4d48-aec0-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports PostgreSQL DBMS version 16 (x86-64).</td><td>This PostgreSQL DBMS version was not supported.</td><td>Reduced number of certificate check errors when accessing Russian websites.</td></tr><tr title="Версия 8.3.22" class="tag_10"><td><a name="15d87531-ca55-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now the root certificates of the Ministry of Digital Development, Communications and Mass Communications of the Russian Federation generated using the GOST R 34.11-2012 algorithms are added to the <span class="interface">cacert.pem</span> and <span class="interface">cacertnx.pem</span> files.</td><td>This feature was not provided.</td><td>Reduced number of certificate check errors when accessing Russian websites.</td></tr><tr title="Версия 8.3.22" class="tag_84"><td><a name="00ff6c8a-ed9b-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Localized client application interface for Portuguese (Brazil), (<span class="interface">pt_BR</span>).</td><td>This feature was not provided.</td><td>Users who speak the Brazilian dialect of Portuguese can use 1C:Enterprise.</td></tr><tr title="Версия 8.3.22" class="tag_70"><td><a name="a0b65ffd-2195-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>New feature: when you install a client application, when updating over HTTP or from a self-extracting application installer (created by the <span class="interface">1CEClientSetupMake </span>utility) running on Windows 8.1 and earlier, the system warns that it is impossible to verify the installer signature and that the installation is running on an outdated version, and allows you to cancel the installation.<p>When you install a client application (when updating over HTTP) running on Windows 8.1 and earlier, you can also disable signature verification of a new version of the client application installer. The checkbox is stored in the <span class="term">DisableInstallerVerification </span>parameter of the <span class="interface">1cestart.cfg </span>configuration file.</p></td><td>Previously, when you installed a client application, when updating over HTTP or from a self-extracting application installer (created by the <span class="interface">1CEClientSetupMake </span>utility) running on Windows 8.1 and earlier, you could not install the client application as it was impossible to verify the digital signature of the installer.</td><td>Simplified diagnostics of the situation that occurs when trying to install current versions of a client application running on outdated Windows-based operating systems (version 8.1 and earlier).</td></tr><tr title="Версия 8.3.22" class="tag_19"><td><a name="ae5b0113-ce68-11ef-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports PostgreSQL DBMS version 17 (x86-64).</td><td>This PostgreSQL DBMS version was not supported.</td><td>Extended list of supported PostgreSQL DBMS versions.</td></tr></table><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717b9b99-67e4-11ec-aa69-0050569f678a">Transition from the previous version to the version 8.3.22</a></h2><ul><li title="Версия 8.3.22" class="tag_0"><a name="717b9b9a-67e4-11ec-aa69-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.22.
</li><li title="Версия 8.3.22" class="tag_0"><a name="717b9b9b-67e4-11ec-aa69-0050569f678a"></a>Some features that are added in version 8.3.22 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.22" class="tag_0"><a name="d72df498-334b-11ed-963f-0050569f678a"></a>After migration to version 8.3.22, collaboration system bots will be activated after one of the following events:<ul><li>Connection to a client application infobase.</li><li>Call to the collaboration system from a server cluster.</li></ul></li></ul><p><a href="#717b9b8d-67e4-11ec-aa69-0050569f678a"><small>Table of contents</small></a></p><h1><a name="bb572410-f9ba-11eb-8371-0050569f678a">Version 8.3.21</a></h1><p title="Версия 8.3.21" class="tag_0"><a name="bb57241f-f9ba-11eb-8371-0050569f678a"></a>Version 8.3.21 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#bb572411-f9ba-11eb-8371-0050569f678a">New functionality and changes</a></li><li><a href="#bb572412-f9ba-11eb-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#bb572413-f9ba-11eb-8371-0050569f678a">Optimization</a></li><li><a href="#bb572414-f9ba-11eb-8371-0050569f678a">Changes that affect system behavior</a></li><li><a href="#bb572415-f9ba-11eb-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#bb572416-f9ba-11eb-8371-0050569f678a">Renamed objects</a></li><li><a href="#bb572417-f9ba-11eb-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#bb572419-f9ba-11eb-8371-0050569f678a">Library updates
</a></li><li><a href="#bb57241a-f9ba-11eb-8371-0050569f678a">Demo configuration changes</a></li><li><a href="#bb57241b-f9ba-11eb-8371-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#bb57241c-f9ba-11eb-8371-0050569f678a">Transition from the previous version to the version 8.3.21</a></li></ul><h2><a name="bb572411-f9ba-11eb-8371-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.21" class="compat tag_2 tag_1"><td><a name="93813440-f9bd-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.20 </span>is now implemented.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.19 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.20 or earlier can now run on version 8.3.21 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.21 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.20 after the migration to version 8.3.21, even if you disable the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.21" class="tag_43"><td><a name="db8f6f2a-fe96-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>You can now get a URL to an object or a record of the current dynamic list row without having to open the object/record form.<p>New form table extension property for the dynamic list: <span class="term">AllowGetCurrentRowURL</span>. New event handlers for the form table extension for a dynamic list: <span class="term">URLListGetProcessing</span> and <span class="term">URLGetProcessing</span>.</p><p>The dialog box for getting a form URL is upgraded considering this feature.</p><p>The dialog box for getting a URL on the home page displays all the URL options received from all forms on the home page.</p></td><td>Getting a URL to an object or a record of the current dynamic list row without having to open the object/record form was unavailable.<p>On the home page, getting a URL of any home page form from one dialog box was unavailable.</p></td><td>Improved and simplified interface for getting a URL in a dynamic list or on the home page.</td></tr><tr title="Версия 8.3.21" class="tag_27 tag_47 tag_20"><td><a name="0412dd23-ff40-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>You can now export the application to the zip. archive of XML files. New feature: multi-threaded application export on the server cluster side.<p>The <span class="interface">Dump configuration to files</span> command in Designer allows you to set the export method (on the server/on the client), the number of simultaneous export threads, and the need to archive the export file.</p><p>To enable this feature, a special parameter is implemented for the following import tools:</p><ul><li>Command line to start 1C:Designer. New parameter for the <span class="term">/DumpConfigToFiles</span> command: <span class="term">-Server</span>, <span class="term">-Archive</span>, -<span class="term">JobsCount</span>.</li><li>1C:Designer in the agent mode. New parameters for the <span class="term">config dump-config-to-files</span> command: <span class="term">--archive</span>, <span class="term">--server</span>, <span class="term">--threads</span>.</li><li>Standalone server management utility (<span class="interface">ibcmd</span>). New parameters for the <span class="term">infobase config export </span>commands: <span class="term">--archive</span>, <span class="term">--server</span>, <span class="term">--threads</span>.</li></ul></td><td>This feature was not provided.</td><td>Improved performance of the application export to XML files. Now you can export files to another computer in a ZIP archive.</td></tr><tr title="Версия 8.3.21" class="tag_64"><td><a name="ba1d76ea-ff46-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New pictures in the picture library:<ul><li><span class="term">RotateClockwise</span></li><li><span class="term">RotateCounterclockwise</span></li></ul></td><td>The listed pictures were not available in the picture library.</td><td>The picture library is upgraded.</td></tr><tr title="Версия 8.3.21" class="tag_85"><td><a name="9ef68ee2-ff46-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 85); return false;">Processing PDF documents</a>.<br></td><td>You can now view and print PDF documents using 1C:Enterprise platform tools. You can view and verify digital signatures in documents. Encrypted documents are now supported. Current restrictions are listed in the documentation.<p>New object: <span class="term">PDFDocument</span>. New field form kind for the client application: <span class="term">PDFDocumentField</span>.</p><p>New global context methods: <span class="term">PasswordProtectedDocument</span>() and <span class="term">PasswordProtectedDocumentAsync</span>().</p><p>New methods for the <span class="term">PDFAttachmentCollection </span>object: <span class="term">Clear() </span>and <span class="term">Delete()</span>.</p><p>New properties for the <span class="term">PDFDocumentFileType</span> system enumeration: <span class="term">PDF</span>, <span class="term">PDF_A_1</span>, <span class="term">PDF_A_2</span>, and <span class="term">PDF_A_3</span>.</p><p>New properties for the <span class="term">ErrorCategory </span>system enumeration: <span class="term">IncorrectPassword </span>and <span class="term">SignatureCheckError</span>.</p></td><td>This feature was not provided.<p>Only PDF document generation was available.</p></td><td>Advanced PDF document features.<p>
</p></td></tr><tr title="Версия 8.3.21" class="tag_37"><td><a name="0e458bde-001d-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>New feature for the <span class="term">HTTPConnection </span>object: use client certificates supporting GOST algorithms. CryptoPRO CSP is now supported on Linux and macOS.<p>New parameter for the <span class="interface">conf.cfg</span> configuration file: <span class="term">CryptoAPILibraryLocation</span>.</p><p>New objects: <span class="term">LinuxClientCertificate</span>, <span class="term">OSCertificateSelectMode</span>, and <span class="term">OSClientCertificate</span>.</p><p>The <span class="term">OpenSSLSecureConnection</span> object constructor can take the <span class="term">OSClientCertificate</span> object as the value of its <span class="term">ClientCertificate</span> parameter.</p><p>
</p><p>
</p></td><td>Client certificates supporting GOST algorithms were not supported.</td><td>Extended list of certificate kinds used for the <span class="term">HTTPConnection </span>object operations.</td></tr><tr title="Версия 8.3.21" class="tag_59"><td><a name="5f2ddaca-00d7-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>New feature: display the Gantt chart with a table that contains additional data for the chart values.<p>New feature: expand the form table for the Gantt chart.</p><p>New property for the <span class="term">GanttChart </span>object: <span class="term">DataColumns</span>. New method for the <span class="term">GanttChart </span>object: <span class="term">FindValueByID()</span>.</p><p>New property to expand the form field for the Gantt chart: <span class="term">TablePosition</span>.</p><p>New properties for the <span class="term">GanttChartValue </span>object: <span class="term">ID </span>and <span class="term">Data</span>.</p><p>New properties for the <span class="term">GanttChartPlotArea </span>object: <span class="term">ShowPointsText </span>and <span class="term">ShowData</span>.
New property for the <span class="term">FormField </span>object <span class="term">Table</span>.</p></td><td>This feature was not provided. The Gantt chart could only display the point names created for the chart series.<p>
</p></td><td>Advanced Gantt chart features.</td></tr><tr title="Версия 8.3.21" class="tag_7"><td><a name="17f9d20a-00e7-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>New feature to update a database copy when using standard replication. This feature applies specialized DBMS tools of the main database. The new feature is used only for Microsoft SQL Server DBMS that records changes.<p>New methods for the <span class="term">DatabaseCopiesManager</span> object: <span class="term">GetStandardReplicationVersion()</span> and <span class="term">InstallStandardReplicationVersion</span>().</p></td><td>This feature was not provided.</td><td>Improved performance of database copy update when using the new database copy update tool.</td></tr><tr title="Версия 8.3.21" class="tag_37"><td><a name="d732050f-00ee-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>New feature: use the JWT token (URL44 standard) for authorization in online services of 1C:Enterprise platform. You can also create and verify a JSON Web Signature (JWS).<p>New object: <span class="term">AccessToken</span>.</p><p>New method for the <span class="term">HTTPRequest </span>object: <span class="term">AddAccessToken()</span>. New property for the <span class="term">InfoBaseUser</span> object: <span class="term">AccessTokenAuthentication</span>.</p><p>New item for the <span class="interface">defaul.vrd </span>file: <span class="term">&lt;accessTokenAuthentication&gt;</span>.</p><p>New startup command line commands for thin and web clients: <span class="term">/AccessToken</span>.</p></td><td>This feature was not provided.</td><td>Advanced access token features and improved security when using online services.</td></tr><tr title="Версия 8.3.21" class="tag_53"><td><a name="f567788b-03fe-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>In the dialog box that appears in case of infobase connection errors, you can now view information that will help you understand why a certain error occurred and who you need to contact in case of such error.<p>New object: <span class="term">StartupErrorProcessingSettings</span>. New methods for the <span class="term">ErrorProcessingManager </span>object: <span class="term">SetStartupErrorProcessingSettings()</span> and <span class="term">GetStartupErrorProcessingSettings()</span>.</p><p>New parameters for the infobase connection parameters described in the <span class="interface">*.v8i </span>file: <span class="term">StartupErrorHelpURL </span>and <span class="term">StartupErrorHelpText</span>.</p></td><td>This feature was not provided.<p>A link to supporting information could be placed only in the dialog box for entering the username and password.</p></td><td>Connection errors of the client application to the infobase are now more comprehensible to users.</td></tr><tr title="Версия 8.3.21" class="tag_86"><td><a name="8881fff3-0416-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>When selecting a subsystem, you can now execute only one command of this subsystem.<p>New property for the <span class="term">Subsystem</span> metadata object: <span class="term">UseOneCommand</span>.</p></td><td>This feature was not provided.</td><td>Simplified application usage with only one subsystem command available to a user.</td></tr><tr title="Версия 8.3.21" class="tag_28 tag_37"><td><a name="a52afffa-04a4-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>You can now take advantage of HTTP requests in web client. Provided features are limited by web browser capabilities.<p>The following objects are available in the web client: <span class="term">HTTPConnection</span>, <span class="term">HTTPRequest</span>, <span class="term">HTTPResponse</span>, and <span class="term">OpenSSLSecureConnection</span>. Synchronous object methods are not supported in web client.</p></td><td>This feature was not provided.</td><td>Advanced web client features for Internet resources.</td></tr><tr title="Версия 8.3.21" class="tag_37"><td><a name="d5347cf7-04a5-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>New feature in client applications (thin, mobile, thick, and web clients): asynchronous HTTP requests.<p>New methods for the <span class="term">HTTPConnection</span> object: <span class="term">CallHTTPMethodAsync()</span>, <span class="term">WriteAsync()</span>, <span class="term">ChangeAsync()</span>, <span class="term">PostAsync()</span>, <span class="term">GetAsync()</span>, <span class="term">GetHeadersAsync()</span>, and <span class="term">DeleteAsync()</span>.</p><p>The <span class="term">CallHTTPMethod()</span>, <span class="term">Write()</span>, <span class="term">Change()</span>, <span class="term">Post()</span>, <span class="term">Get()</span>, <span class="term">GetHeaders()</span>, and <span class="term">Delete()</span> methods of the <span class="term">HTTPConnection </span>object are considered obsolete for client applications and supported for compatibility reasons. Specified methods are available only on the server application side.</p></td><td>1C:Enterprise did not support asynchronous HTTP request execution. Only request execution timeout could be specified.</td><td>Asynchronous data exchange with various Internet resources.<p>
</p></td></tr><tr title="Версия 8.3.21" class="tag_38 tag_58"><td><a name="3a073d45-04ba-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>New feature: include your own extension objects in adopted common attributes being separators.<p>New feature: install extensions that extend data simultaneously for the whole infobase as well as for a specific data area.</p></td><td>Including your own extension objects in adopted common attributes being separators was not supported.<p>An extension that extends data could be installed in a specific data area or for the whole infobase. Simultaneous installation of such extensions was not supported.</p></td><td>The configuration extension now provides more features.</td></tr><tr title="Версия 8.3.21" class="tag_23 tag_43 tag_25"><td><a name="2124ddf3-0585-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When setting up application object characteristics, you can now specify that a characteristic can contain more than one value. This feature is implemented in the data composition system and dynamic list.<p>New properties for the <span class="term">CharacteristicsDescription</span> object: <span class="term">MultipleValuesUseField</span> and <span class="term">MultipleValuesKeyField</span>. <span class="term">MultipleValuesOrderField</span>.</p><p>If multiple characteristics are specified in the infobase, data can be duplicated as a result of data composition when migrating to previous platform versions. It is not recommended that you use previous versions of 1C:Enterprise after specifying multiple characteristic values.</p></td><td>More than one value could not be specified in object characteristics.</td><td>Support of multiple values in required characteristics. For example, WiFi frequency bands, materials used for goods, and so on.</td></tr></table><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb572412-f9ba-11eb-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.21" class="tag_4"><td><a name="d28cdebd-0185-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can now create a new conversation during a video call in the collaboration system. The current video call participants are added to the conversation participants.<p>In the video call window, there is a submenu for the <span class="interface">Go to conversation</span> button containing the following commands: <span class="interface">Go to conversation</span> and <span class="interface">New video call conversation</span>.</p></td><td>Participants could go to a conversation during a video call only if a video call was started from a conversation. If a video call was started from the collaboration system menu, to exchange text messages on the discussed topic, a user had to manually create a new conversation and add all video call participants to it.</td><td>Fast creation of a text chat (and access to it) during a video call.</td></tr><tr title="Версия 8.3.21" class="tag_53"><td><a name="f2e22cf2-03fc-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>New feature: view <span class="interface">About</span> window in the dialog box that generates an error report.</td><td>This feature was not provided.</td><td>Access to error environment details (application and platform version, connection mode, user, infobase name, and so on) when generating an error report.</td></tr><tr title="Версия 8.3.21" class="tag_53 tag_28"><td><a name="400e61b8-0406-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>If a web client connects to an infobase using the HTTPS protocol, this infobase was accessed from this computer before, and the web browser supports the service-worker technology, a special page will be displayed in case of a connection error (similar to the exit page). This page will display connection error information and various supporting information. The page will be functionally identical to the connection error form in thin client, but its implementation will depend on web application specifics.</td><td>This feature was not provided.</td><td>The same view of the infobase connection error via HTTPS and errors in web applications.</td></tr><tr title="Версия 8.3.21" class="tag_4"><td><a name="8418b9ef-04da-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>When working via a video server, the image quality in a video call in the speaker view mode has been improved.<p>When working via a video server, the load on the client computer is reduced when all subscribers in a group video call are displayed in the gallery view mode.</p></td><td>When working via a video server, the image quality in a video call in the speaker view mode was insufficient.<p>When working via a video server, the load on the client computer was significant when all subscribers in a group video call were displayed in the gallery view mode.</p></td><td>Improved video call quality via a video server.</td></tr></table><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb572413-f9ba-11eb-8371-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.21" class="tag_59"><td><a name="4d76b6d7-00d3-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>Optimized transfer of tables from the server to the client in the client application form. If some table rows are changed on the server, only the rows with changed columns are transferred to the client. Only the lines previously transferred to the client side are modified. The transfer is carried out in portions of 35 rows (or less). If more than 105 rows are changed on the server (3 portions of 35 rows), then after transferring three portions of 35 rows each, all table rows are transferred to the client. If a form is opened, no more than 35 rows are trensferred to the client.</td><td>When a form was opened, only the displayed table part was transferred to the client. In case of any change of the table on the server, the entire table was transferred to the client. With a large table, this could take a long time and even cause run-time errors.</td><td>Improved performance of the client application form when a small number of rows are changed in a large table on the server (in one call).</td></tr><tr title="Версия 8.3.21" class="tag_6"><td><a name="aa8fd9ba-00d4-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved working process cache: frequently used objects are stored for longer periods and rarely used objects are deleted sooner. Reduced memory consumption by the working process, improved operation stability, and reduced probability of restarting cluster working processes when the memory threshold is exceeded.</td><td>The working process cache of server clusters had a different operation procedure. This could lead to increased RAM consumption by the working process.</td><td>Reduced memory consumption by the working process, improved operation stability, and reduced probability of restarting cluster working processes when the memory threshold is exceeded.</td></tr><tr title="Версия 8.3.21" class="tag_36"><td><a name="f81467e4-0410-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>Improved setting of values in the <span class="term">ValueTable</span> object if the column where a value is specified participates in the index created for the value table. The following operations take less time now (not limited to this list):<ul><li>Setting a value to a column.</li><li>Copying a value table.</li></ul></td><td>Setting a value to the <span class="term">ValueTable</span> type object column that participated in the index was very time-consuming.</td><td>Improved performance when changing values in the <span class="term">ValueTable</span> type object columns that participate in the indexes created for the value table.</td></tr><tr title="Версия 8.3.21" class="tag_21"><td><a name="d0b150db-0415-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>
<p>Improved full-text search by the beginning of a word. The improvement is manifested when performing a full-text search from 1C:Enterprise language with a search string of the "sear*" kind or when using the global search field.</p></td><td>Full-text search by the beginning of a word took more time.</td><td>Improved performance of full-text data search.</td></tr><tr title="Версия 8.3.21" class="tag_87"><td><a name="88444d5f-0418-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 87); return false;">Metadata objects</a>.<br></td><td>Improved performance of the application that contains numerous metadata objects, including improved:<ul><li>The <span class="term">Value(EnumerationID)</span> query language expression.</li><li>Operations of a user with numerous roles.</li></ul></td><td>Performance of the application that contains numerous metadata objects was insufficient.</td><td>Improved performance of applications with numerous metadata objects.</td></tr><tr title="Версия 8.3.21" class="tag_26"><td><a name="00202968-2a98-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In thin client, the display of a spreadsheet document that contains a large number of merged cells and columns is improved.</td><td>In thin client, the display of a spreadsheet document that contains a large number of merged cells and columns took longer.</td><td>Improved display of spreadsheet documents with a complex structure.</td></tr><tr title="Версия 8.3.21" class="tag_20"><td><a name="0bfb02b1-32fd-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>When trying to view a large collection in the <span class="interface">Expression</span> dialog box, the collection is received by Designer (for display) in portions. As a result, you do not have to spend a lot of time to view the collection.</td><td>When trying to view a large collection in the <span class="interface">Expression</span> dialog box, the entire collection was received by Designer (for display). This caused significant delays and could lead to disconnection from the debug item.</td><td>Viewing large collections in the <span class="interface">Expression</span> dialog box is more convenient for developers.</td></tr><tr title="Версия 8.3.21" class="tag_21"><td><a name="a3f068e3-4203-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Preparing full-text search results for users takes less time now.<p>In full-text search results, the first exact match of the search word (if there is one) is always highlighted. If there is no exact match, the first found form of the search word is highlighted.</p></td><td>Preparing full-text search results for users took longer.<p>In full-text search results, the first found form of the search word was always highlighted.</p></td><td>Displaying search results to users takes less time.<p>Search text in search results is highlighted more correctly.</p></td></tr></table><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb572414-f9ba-11eb-8371-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.21" class="tag_28 tag_59"><td><a name="1fc92448-f9cd-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>In web client, the indent between a picture and a page title text as well as the indent from page edges depend on the font size of all <span class="term">Page </span>items of the current form.</td><td>In web client, the indent between a picture and a page title text as well as the indent from page edges depended on the font size of a <span class="term">Page </span>item.</td><td>The web client behavior is now identical to the thin client behavior.</td></tr><tr title="Версия 8.3.21" class="tag_45"><td><a name="018c9576-fe89-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>When working in the thick client, the <span class="term">QueryWizard</span> object constructor can be called with an empty query text. In this case, the default constructor is called.</td><td>When working in the thick client, the <span class="term">QueryWizard</span> object constructor threw an exception if the constructor parameter value was an empty string.</td><td>Unified behavior of the <span class="term">QueryWizard</span> object constructor in different client applications.</td></tr><tr title="Версия 8.3.21" class="tag_53"><td><a name="62b3370c-ff62-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>Extended features when working with errors for application developers. New features: define exception codes for your own exceptions; throw an exception based on another exception. The presentation of errors generated from the application code has been changed.<p>New parameters for the <span class="term">Raise </span>operator: <span class="term">Category</span>, <span class="term">Code</span>, <span class="term">AdditionalInformation</span>, and <span class="term">Cause</span>. When specifying more than one parameter, the operator can be written only in the functional form (with parameters enclosed in parentheses).</p><p>New system enumeration property: <span class="term">ErrorCategory.ConfigurationError</span>.</p><p>New properties for the <span class="term">ErrorInfo </span>object: <span class="term">Code </span>and <span class="term">AdditionalInformation</span>.</p><p>New parameters for the <span class="term">getInfo </span>query of the error registration service: <span class="term">errorCategories</span>, <span class="term">clientID</span>, and <span class="term">reportID</span>. New error report properties: <span class="term">id </span>(contains the <span class="term">reportID </span>value from the <span class="term">getInfo </span>query) and <span class="term">dump.reasonForNoDump </span>(contains the reason why a report does not contain a crash dump).</p><p>New properties for the <span class="term">ErrorProcessingSettings </span>object: <span class="term">SendReportAtServer</span>, <span class="term">SendCrashReportAtServer</span>, <span class="term">SendCrashReportToPlatformErrorRegistrationService</span>, <span class="term">IncludeUserNameInReportAtServer</span>, <span class="term">IncludeInfobaseInformationInReportAtServer</span>, <span class="term">IncludeDetailErrorDescriptionInReportAtServer</span>.</p></td><td>These features were not provided.</td><td>Extended features for error operations. You can now create codes for application errors. Extended API features of the error registration service.</td></tr><tr title="Версия 8.3.21" class="compat tag_88 tag_1"><td><a name="96802afd-0028-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 88); return false;">1C:Enterprise language</a>.<br></td><td>The <span class="term">Undefined</span> value can now be used as a key for the objects of the <span class="term">Map</span> and <span class="term">FixedMap</span> types. This feature was already available in the web client.<p>This change is not implemented in 8.3.20 version compatibility mode.</p></td><td>The <span class="term">Undefined</span> value could be used as a key for the objects of the <span class="term">Map</span> and <span class="term">FixedMap</span> types only in the web client.</td><td>Possible use of the <span class="term">Undefined</span> value as a key for the objects of the <span class="term">Map</span> and <span class="term">FixedMap</span> types.</td></tr><tr title="Версия 8.3.21" class="tag_56"><td><a name="d8cd5a1d-00e9-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>For the <span class="term">WriteXML()</span> and <span class="term">XDTOSerializer.WriteXML()</span> global context methods, you can now pass a metadata object of the following types as the <span class="term">Value</span> parameter: a catalog, a document, a chart of characteristic types, a chart of accounts, a chart of calculation types, an information, accumulation, or accounting register, a constant, a business process and task. All metadata object data available to the user that writes data will be written.</td><td>This feature was not provided. Export of all configuration object data to XML was unavailable. Data had to be sorted and each data item had to be exported separately.</td><td>Improved performance of data export from the application.</td></tr><tr title="Версия 8.3.21" class="tag_89"><td><a name="c1dd2d2a-00ed-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 89); return false;">URLs</a>.<br></td><td>New feature: get a URL with its presentation. New radio button in the dialog box for getting a URL: <span class="interface">Copy name</span>. The dialog box to follow a link, the global search, and the collaboration system consider that the clipboard may contain a URL with a presentation.</td><td>This feature was not provided.</td><td>Simplified simultaneous receiving of a URL and a presentation of the object to which this URL refers.</td></tr><tr title="Версия 8.3.21" class="tag_36"><td><a name="4bb5510e-00f2-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>New feature: generate UUIDs of versions 1, 3, 4, and 5. New parameters for the <span class="term">UUID</span> object constructor for creating IDs of the required version.<p>New system enumeration: <span class="term">UUIDVersion</span>.</p></td><td>This feature was not provided. Only version 4 IDs could be generated by 1C:Enterprise platform.</td><td>Now application developers can generate a UUID version required to complete a specific task.</td></tr><tr title="Версия 8.3.21" class="tag_37"><td><a name="3c3f054f-00f6-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>If the <span class="term">HTMLDocumentField</span> form item in thin and thick clients displays a URL that requires an SSL certificate, and this certificate contains any errors (for example, it is invalid), a page with error details will be displayed, and you will be offered to continue working with the URL or close it.</td><td>If the <span class="term">HTMLDocumentField</span> form item in thin and thick clients displays a URL that requires an SSL certificate, and this certificate contains any errors (for example, it is invalid), an error message will be displayed in the field and further operations with the required URL will be unavailable.</td><td>Improved troubleshooting of problems with URLs displayed in the client application. Access to resource operations in cases where such operations are not recommended, but the user is confident in their actions.</td></tr><tr title="Версия 8.3.21" class="tag_7 tag_90"><td><a name="08ce8a22-040e-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br><a href="#" onclick="onTagClick(this, 90); return false;">Data Composition System</a>.<br></td><td>If during the execution of a data query to a copy, an error occurs related to the copy used in the query, the copy is no longer used in all existing or new sessions until the copy is updated or the server cluster is restarted.<p>If an error is caused by a copy during the execution of the report created in the Data Composition System that contains several data sets or a hierarchical data set, the data access error will be displayed to the user. In other cases, as well as if a report/query does not require using only a database copy, an error is not displayed to the user, and the query is automatically re-executed in the main database or in one of the available database copies (except for the copy with an error).</p></td><td>This feature was not provided.<p>The copy in which an error occurred had to be manually disabled. After restarting the cluster or updating the copy, it had to be included in the used copies again.</p></td><td>When working with database copies, the damaged copy is disabled automatically without user intervention. If a query can be generated without the damaged copy of the database, the user will not notice the copy failure. The user will receive an error message only if a data query cannot be completed without the data of the database copy, all copies are marked as damaged, and queries to them are not executed.</td></tr><tr title="Версия 8.3.21" class="tag_21"><td><a name="0c684204-0413-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Full-text search correctly processes situations with numerous iterations of full-text search index update (hundreds of thousands iterations) and numerous indexed items.<p>To enable this feature, the user must create an index in compatibility mode with <span class="interface">version 8.3.14 </span>or later (including the "<span class="interface">Do not use</span>" value).</p><p>
</p></td><td>Full-text search index could be incorrect in case of numerous iterations of full-text search index update (hundreds of thousands iterations) and numerous indexed items in the infobase.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="tag_26"><td><a name="373333e1-04e2-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When converting a spreadsheet document to compact mode used on mobile devices, the <span class="term">AutoIndent</span> property is used to align text in cells.</td><td>When converting a spreadsheet document to compact mode used on mobile devices, only the <span class="term">Indent</span> property was used to align text in cells.</td><td>Improved spreadsheet documents view on mobile devices.</td></tr><tr title="Версия 8.3.21" class="tag_91"><td><a name="4e1fa0bc-0572-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 91); return false;">Collaboration System</a>.<br></td><td>
<p>If screen sharing is enabled during a video call in thin or web clients, the video call window switches to the compact display mode. New feature: minimize the compact video call window to the heading size.</p></td><td>If screen sharing was enabled during a video call in thin or web clients, the video call window disappeared from the screen. The users that shared the screen could not tell whether they had listeners or not.<p>
</p></td><td>Improved screen sharing during a video call.<p>
</p></td></tr><tr title="Версия 8.3.21" class="compat tag_26 tag_1"><td><a name="b732d02b-2a9d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the <span class="interface">Sheet</span><span class="interface">1 </span>name is set in the resulting document for the Microsoft Excel sheet. In version 8.3.20 compatibility mode, this behavior is not changed.<p>When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the document sheet panel is not hidden.</p></td><td>When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the <span class="interface">TDSheet </span>name was set in the resulting document for the Microsoft Excel sheet.<p>When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the document sheet panel was hidden.</p><p>
</p></td><td>Eliminated performance issues when trying to open a document with a hidden sheet panel in Microsoft Excel. The naming of sheets in the resulting Microsoft Excel document is more understandable and predictable now.</td></tr><tr title="Версия 8.3.21" class="tag_4"><td><a name="fd1ffcbf-2bf6-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can now enable support for specific types of audio devices (multichannel microphones and audio systems) in the Collaboration System. This feature is enabled separately in the settings dialog box for video and sound in the Collaboration System settings. The user can use this feature in case of problems with capturing or playing audio on their computer.</td><td>Some users had sound problems when making video calls.</td><td>Extended list of supported audio devices in thin client.</td></tr><tr title="Версия 8.3.21" class="compat tag_25 tag_1"><td><a name="5a7534be-36ee-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When displaying list templates of the data composition system in the lower-right cell of the template, the cell is no longer vertically merged with an empty cell in the row below.<p>This change is not implemented in 8.3.20 compatibility mode.</p></td><td>When displaying list templates of the data composition system in the lower-right cell of the template, the cell was vertically merged with an empty cell in the row below.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="compat tag_92 tag_1"><td><a name="0ce1a234-4d02-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 92); return false;">Dynamic list</a>.<br></td><td>If a dynamic list contains a visible field whose type consists of a string of unlimited length and any other type (except for <span class="term">NULL</span> and <span class="term">Undefined</span>):<ul><li>You can use the search string in this dynamic list.</li><li>Such field will not be in the list of available filter fields.</li></ul><p>In version 8.3.20 compatibility mode, the behavior has not changed.</p></td><td>If a dynamic list contained a visible field whose type consisted of a string of unlimited length and any other type (except for <span class="term">NULL</span> and <span class="term">Undefined</span>):<ul><li>You could not use the search string in this dynamic list (an error was generated).</li><li>If such field was in the list of available filter fields, any attempt to apply filter by this field resulted in an error.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="tag_11"><td><a name="50568ce2-4d04-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>New method for the program and add-in interface: <span class="term">SetUserInterfaceLanguageCode()</span>. It is used to transfer an interface localization language of the client application to the add-in. The <span class="term">SetLocale()</span> method is considered deprecated. The technology for creating add-ins has been changed (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>).<p>It is recommended that you use the new method of getting the interface localization code for the current add-in.</p></td><td>The <span class="term">SetLocale() </span>method was used to transfer an interface localization language of the client application to the add-in. This method worked differently in different client applications and with different interface localization languages.</td><td>Unified method of transferring information about a client application localization language to the add-in.</td></tr><tr title="Версия 8.3.21" class="compat tag_64 tag_60 tag_1"><td><a name="bf8c2cf8-5bf9-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br></td><td>If the print scale of a spreadsheet document is set to <span class="interface">"Fit page width"</span> in the print parameters, and the page width is not enough to fit the whole document, then when exporting a spreadsheet document to Microsoft Word format, the document is scaled similarly to the scaling applied by 1C:Enterprise when printing a spreadsheet document: the column width, the row height, and the font size are changed.<p>In version 8.3.20 compatibility mode, the behavior has not changed.</p></td><td>If the print scale of a spreadsheet document was set to <span class="interface">"Fit page width"</span> in the print parameters, and the page width was not enough to fit the document, then when the spreadsheet document was exported to Microsoft Word format, the document was not changed in the way 1C:Enterprise system would change this spreadsheet document when printing.</td><td>If the print scale is set to <span class="interface">"Fit page width"</span> for a spreadsheet document, the printed document and the document exported to Microsoft Word format will be almost identical.</td></tr><tr title="Версия 8.3.21" class="tag_27"><td><a name="80be7232-67b5-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is 2.14.</td><td>The format version of configuration dump to XML files was 2.13.</td><td>Configuration dump to XML files supports new platform features.</td></tr></table><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb572415-f9ba-11eb-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.21" class="compat tag_59 tag_1"><td><a name="b43369f6-0029-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>When trying to change the form attributes or dynamic list settings from 1C:Enterprise language, adding an attribute/column with a duplicate name will result in an exception.<p>This change is not implemented in 8.3.20 version compatibility mode.</p></td><td>When trying to change the form attributes or dynamic list settings from 1C:Enterprise language, adding an attribute/column with a duplicate name did not cause adding errors. Access to such attribute from 1C:Enterprise language was impossible.</td><td>Eliminated unexpected system behavior.<p>
</p></td></tr><tr title="Версия 8.3.21" class="tag_15 tag_10 tag_6"><td><a name="a0aba891-00f4-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When using a 1C:Enterprise server cluster running on Linux, the SystemV subsystem for initialization and management of services will no longer be used. The systemd subsystem (similar to the previously mentioned one in terms of purpose) is used instead.<p>The distribution package includes a systemd-scenario for starting a server cluster and an administration server (<span class="interface">ras</span>) and their configuration files.</p><p>The SystemV-scenario for starting a server cluster (and its configuration file) was deleted from 1C:Enterprise distribution package.</p><p>After migration to a new version, you need to reconfigure the functionality to automatically start a server cluster.</p></td><td>
<p>When using a 1C:Enterprise server cluster running on Linux, the SystemV subsystem for initialization and management of services was used.</p></td><td>Improved startup and configuring of 1C:Enterprise service instances for system administrators working on Linux including (if required) multiple startups of different instances.</td></tr><tr title="Версия 8.3.21" class="tag_11"><td><a name="596f707e-01b5-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>New feature: import add-ins in a separate process separated from 1C:Enterprise platform processes. In this case, abnormal add-in termination will not result in the abnormal platform termination, but the add-in reattachment will be required.<p>The add-in creation technology has been changed. An add-in can now provide the platform with information about available add-in operation modes and current URL1 mode.</p><p>New parameter for the <span class="term">AttachAddIn</span>() method (and all asynchronous analogs): <span class="term">AddInAttachmentType</span>. New method: <span class="term">CheckAddInAtachment</span>().</p><p>New event: <span class="term">AddInDetachmentProcessing</span>. It is called upon abnormal termination of the add-in operating process.</p><p>It is recommended that you develop add-ins that support the isolated operation mode. When using add-ins on the client side, it is recommended that you provide a reload code in case of abnormal add-in termination. </p><p>When developing configurations in the compatibility mode with version 8.3.20 or earlier, isolated add-in import is recommended if the add-in can run in a separate process.</p></td><td>This feature was not provided.<p>Add-ins were imported only to the address space of 1C:Enterprise platform process that used this add-in. Abnormal add-in termination resulted in the abnormal termination of 1C:Enterprise process.</p></td><td>Improved stability of add-ins.</td></tr><tr title="Версия 8.3.21" class="tag_10"><td><a name="83296150-01be-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>If OS updates were automatically installed before the platform was installed, or the updated files were used by other applications, after installing the platform you will see a warning stating that a computer restart might be required.</td><td>
<p>If OS updates were automatically installed before the platform was installed, or the updated files were used by other applications, after installing the platform the computer was restarted without a warning. That could lead to data loss of the user who installed 1C:Enterprise.</p></td><td>Improved installer behavior for cases when a computer restart is required to complete the installation.</td></tr><tr title="Версия 8.3.21" class="tag_14"><td><a name="1ba5f5bb-03fc-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>When connecting to the infobase via HTTP using thin or web clients, the <span class="term">/UC</span> command can be specified in the startup command line if the session start is locked with an unlock code.</td><td>When connecting to the infobase via HTTP using thin or web clients, the <span class="term">/UC</span> command in the startup command line was ignored.</td><td>Possible connection to the infobase via HTTP for the user knowing the unlock code even if the session start is locked.</td></tr><tr title="Версия 8.3.21" class="compat tag_53 tag_1"><td><a name="c6d8c3ce-0400-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>If the technician mode is enabled in the user session, the interpretation of the <span class="term">Auto</span> value of the <span class="term">ErrorProcessingSettings</span><span class="term">.MessageDisplayVariant</span> property is changed:<ul><li>If the technician mode is enabled, <span class="term">Auto</span> is interpreted as <span class="term">BriefErrorDescription</span>.</li><li>If the technician mode is disabled, <span class="term">Auto</span> is interpreted as <span class="term">ErrorMessageForUser</span>.</li></ul><p>This change is not implemented in 8.3.20 compatibility mode.</p></td><td>The <span class="term">Auto </span>value of the <span class="term">ErrorProcessingSettings.MessageDisplayVariant</span> property was always interpreted as <span class="term">ErrorMessageForUser</span>.</td><td>Simplified troubleshooting and problem solving due to errors being displayed in a more technical form for developers and technicians.</td></tr><tr title="Версия 8.3.21" class="compat tag_38 tag_1"><td><a name="7378bfa4-040f-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: create your own predefined items for adopted objects of the following types: catalogs, charts of characteristic types, charts of accounts, and charts of calculation types. Predefined items can be adopted or native.<p>This change is not implemented in 8.3.20 compatibility mode.</p></td><td>This feature was not provided.</td><td>The configuration extension now provides more features.<p>
</p></td></tr><tr title="Версия 8.3.21" class="compat tag_19 tag_1"><td><a name="9f804afa-04de-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>For PostgreSQL, Oracle Database, and IBM DB2 DBMS, a query language expression containing a multiple <span class="term">B</span> operator with a subquery is translated to the DBMS language using the <span class="term">EXISTS()</span> operator. After the change, the multiple <span class="term">B</span> operator with a subquery always returns a <span class="term">Boolean</span> type value. This change is not implemented in 8.3.20 compatibility mode.<p>It is recommended that you check the use of queries that contain the multiple <span class="term">B</span> operator with a subquery in applications.</p><p>
</p></td><td>For PostgreSQL, Oracle Database, and IBM DB2 DBMS, a query language expression containing a multiple <span class="term">B</span> operator with a subquery was translated to the DBMS language using the <span class="term">multivalue IN</span> operator. The <span class="term">EXISTS()</span> operator was used in Microsoft SQL Server DBMS and the file mode of the infobase. Because of that, the query language expression could return different values in different DBMS.</td><td>Unified behavior of the multiple <span class="term">B</span> operator with a subquery for all supported DBMS.<p>
</p></td></tr><tr title="Версия 8.3.21" class="compat tag_25 tag_1"><td><a name="ca533988-2a91-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The Data Composition System does not display records from other periods in the report if the following grouping is specified: field-period - field not being a period - field-period.<p>In version 8.3.20 compatibility mode, this behavior is not changed.</p></td><td>The Data Composition System displayed records from other periods in the report if the following grouping is specified: field-period - field not being a period - field-period.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="compat tag_25 tag_1"><td><a name="9a93f65f-2a97-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When generating a data composition template, if some optional connection of a data set query is considered used (in the data composition settings, a field from the tables of this connection is used), connections with tables whose fields are used in this connection are also considered used.<p>In version 8.3.20 compatibility mode, this behavior is not changed.</p></td><td>When generating a data composition template, if some optional data set query connection is considered used (in the data composition settings, a field from the tables of this connection is used), connections with tables whose fields were used in this connection were not considered used.</td><td>The behavior of the data composition template generator is now more predictable.</td></tr><tr title="Версия 8.3.21" class="tag_21"><td><a name="7121ce10-2a9c-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>If a full-text search query contains the * character surrounded by quotation marks, for example, <span class="interface">"table*"</span>, the expression is interpreted as a search for the * character, not as a metacharacter.</td><td>If a full-text search query contained the * character, such expression was always interpreted as a metacharacter, no matter how the search string was formatted.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="tag_92"><td><a name="cd145943-51dc-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 92); return false;">Dynamic list</a>.<br></td><td>The dynamic list key fields are added to the end of the list of order fields in the data composition system settings obtained by calling the form table extension method for the <span class="term">GetPerformingDataCompositionSettings() </span>dynamic list if these fields are specified in the <span class="interface">Key fields</span> property of the dynamic list. As a result, data sorting performed according to such settings will always be stable.<p>It is recommended that you analyze all places where the <span class="term">GetPerformingDataCompositionSettings()</span> method is used for dynamic lists with any key and make sure that the resulting settings are not imported to the dynamic list settings. The resulting settings can be used only with the data composition schema obtained by calling the <span class="term">GetPerformingDataCompositionScheme()</span> method of the form table extension for the same dynamic list.</p></td><td>Dynamic list key fields were not added to the end of the list of order fields in the data composition system settings obtained by calling the form table extension method for the <span class="term">GetPerformingDataCompositionSettings() </span>dynamic list. As a result, data sorting performed according to such settings could be unstable.</td><td>Consistently stable sorting of data obtained using the executable data composition schema and the executable data composition settings of the dynamic list.</td></tr></table><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb572416-f9ba-11eb-8371-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.21" class="tag_0"><td><a name="81075902-ff64-11eb-8371-0050569f678a"></a>Properties of the <span class="term">ErrorProcessingSettings</span> object. The former names are supported for compatibility purposes.</td><td><ul><li><span class="term">IncludeUserNameInReport,</span></li><li><span class="term">IncludeSystemInfoInReport,</span></li><li><span class="term">IncludeDetailErrorDescriptionInReport,</span></li><li><span class="term">IncludeInfobaseInformationInReport,</span></li><li><span class="term">IncludeWindowsPictureInReport,</span></li><li><span class="term">SendCrashReport,</span></li><li><span class="term">SendCrashReportToPlatformErrorRegistrationService,</span></li><li><span class="term">SendReport.</span></li></ul></td><td>
<ul><li><span class="term">IncludeUserNameInReportAtClient,</span></li><li><span class="term">IncludeSystemInfoInReportAtClient,</span></li><li><span class="term">IncludeDetailErrorDescriptionInReportAtClient,</span></li><li><span class="term">IncludeInfobaseInformationInReportAtClient,</span></li><li><span class="term">IncludeWindowsPictureInReportAtClient,</span></li><li><span class="term">SendCrashReportAtClient,</span></li><li><span class="term">SendCrashReportToPlatformErrorRegistrationServiceAtClient,</span></li><li><span class="term">SendReportAtClient.</span></li></ul><p>
</p><p>
</p></td></tr><tr title="Версия 8.3.21" class="tag_0"><td><a name="3d52b909-24e2-11ec-aa69-0050569f678a"></a>New property used to specify the error registration service address of the <span class="term">ErrorProcessingSettings</span> object.</td><td><ul><li><span class="term">ErrorRegistrationServiceURL</span></li></ul></td><td><ul><li><span class="term">ErrorProcessingServiceURL</span></li></ul></td></tr><tr title="Версия 8.3.21" class="tag_0"><td><a name="aba1c666-8006-11ec-aa69-0050569f678a"></a>Russian picture names of the picture library. Former names are considered obsolete and unsupported for compatibility.<p>
</p></td><td><ul><li><span class="term">AppearanceCharExclamationMark</span></li><li><span class="term">AppearanceExclamationMark</span></li></ul><p>The names contain Latin letter "c".</p></td><td><ul><li><span class="term">AppearanceCharExclamationMark</span></li><li><span class="term">AppearanceExclamationMark</span></li></ul><p>The names contain Russian letter "c".</p> </td></tr></table><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb572417-f9ba-11eb-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.21" class="tag_30 tag_31 tag_41"><td><a name="e20de6f7-0418-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>The mobile version of 1C: Enterprise now supports ZIP archive operations.</td><td>This feature was not provided.</td><td>Supported ZIP archive operations in the mobile version of 1C:Enterprise.</td></tr><tr title="Версия 8.3.21" class="compat tag_30 tag_31 tag_92 tag_25 tag_1"><td><a name="6063b618-04d9-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 92); return false;">Dynamic list</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the mobile version of 1C:Enterprise, custom report settings are saved when generating a report. The <span class="term">UserSettingsModified</span> report form extension property is set to <span class="term">False</span> when generating the report result. This change is not implemented in 8.3.20 compatibility mode.<p>In the mobile version of 1C:Enterprise, a report option is saved after closing the report option editing form by clicking <span class="interface">Finish editing</span>. This change is not implemented in 8.3.20 compatibility mode.</p><p>Custom dynamic list settings are saved after dynamic list records are successfully imported.</p></td><td>In the mobile version of 1C:Enterprise, custom report settings were saved when closing a report form. The <span class="term">UserSettingsModified</span> report form extension property was set to <span class="term">False</span> when closing the form.<p>In the mobile version of 1C:Enterprise, a report option was saved only when the <span class="interface">Save option</span> command was manually called.</p></td><td>More logical and understandable operations with report and dynamic list settings.</td></tr></table><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb572419-f9ba-11eb-8371-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.21" class="tag_0"><a name="9b0834ce-1969-11ee-963f-0050569f678a"></a>The ImageMagick library is updated to version 7.1.11-11.</li></ul><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb57241a-f9ba-11eb-8371-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.21" class="tag_0"><a name="8ecc5f50-7d0a-11ec-aa69-0050569f678a"></a>You can find an example of using the Gantt chart with a data table in the demo configuration for operating with charts (<a href="https://its.1c.ru/db/metod8dev#content:5952:hdoc" target="_blank">Read more</a>.). </li><li title="Версия 8.3.21" class="tag_0"><a name="2be9c574-7d0e-11ec-aa69-0050569f678a"></a>View operations with multiple characteristics in the <span class="interface">Price list </span>report.<p>
</p></li><li title="Версия 8.3.21" class="tag_0"><a name="5ba44e24-7d11-11ec-aa69-0050569f678a"></a>New feature: highlight order status in the list of orders.<p>You can find an example of filling in the <span class="term">GoodsConsumption</span> document based on the <span class="term">Order</span> document.</p></li></ul><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb57241b-f9ba-11eb-8371-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.21" class="tag_31"><td><a name="67224557-7d17-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Startup of the mobile client with the connected collaboration system takes less time.</td><td>Startup of the mobile client with the connected collaboration system took more time.</td><td>Startup of the mobile client with the connected collaboration system takes less time.<p>
</p></td></tr><tr title="Версия 8.3.21" class="tag_20"><td><a name="a1778b70-a123-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New feature: prohibit exporting references to deleted configuration objects to XML files.<p>New radio button in the dialog box for dumping configuration to files: <span class="interface">Do not export references to non-existent objects</span>.</p><p>New parameter for the /<span class="term">DumpConfigToFiles</span> command: <span class="term">-ignoreUnresolvedReferences</span>.</p><p>New parameter for the config dump-config-to-files Designer agent command: <span class="term">--ignore-unresolved-refs</span>.</p><p>New parameter for the (<span class="interface">ibcmd</span>) config export management utility of the standalone server:<span class="term"> --</span><span class="term">ignore-unresolved-refs</span>.</p></td><td>This feature was not provided.<p>
</p></td><td>You can deny export of references to previously deleted objects that remained in forms, command interface, and so on to XML configuration files.</td></tr><tr title="Версия 8.3.21" class="tag_4 tag_28"><td><a name="a8cd6029-a12a-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>If a collaboration system user makes a video call in web client using Mozilla Firefox, video stream quality always remains high. Video stream quality does not depend on how this user is displayed for their counterparty.</td><td>If a collaboration system user made a video call in web client using Mozilla Firefox, the web client tried to manage video stream quality, but the attempts failed.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="tag_43"><td><a name="821eb3ea-a456-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>You cannot receive a URL of the current row for an information register subordinate to the recorder. An item with the <span class="term">WriteCurrentListRow</span> key is not passed to the list of URLs. This list is passed to the <span class="term">ProcessURLsReceiving</span> event handler for this information register.</td><td>You could receive a URL of the current row for an information register subordinate to the recorder. <p>
</p></td><td>Eliminated unexpected system behavior as the record form is missing for an information register subordinate to the recorder.</td></tr><tr title="Версия 8.3.21" class="compat tag_25 tag_31 tag_1"><td><a name="35800a82-e184-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>User report settings are saved:<ul><li>When the settings form is closed (in thin, thick, mobile, and web clients).</li><li>Upon calling the standard report generation command.</li><li>After 10 seconds since the latest change in user settings.</li></ul><p>This change is not implemented in version 8.3.20 compatibility mode.
</p></td><td>User report settings were saved only upon calling the standard report generation command.</td><td>Eliminated unexpected system behavior.<p>Reduced risk of losing configured settings due to automatic saving.</p><p>
</p><p>
</p><p>
</p><p>
</p></td></tr><tr title="Версия 8.3.21" class="tag_75"><td><a name="357e14d8-ed4b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 75); return false;">Distributed infobases</a>.<br></td><td>Licensing client data must be entered in each node of a distributed infobase.</td><td>Licensing client data had to be entered only in the main node of a distributed infobase.<p>
</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="tag_30 tag_31 tag_10"><td><a name="129138d7-f391-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The <span class="interface">cacertnx.pem </span>file that contains root CA certificates is included in the mobile version of 1C:Enterprise.<p>When establishing a secure connection, certificate revocation is checked in the following order: certificates from the <span class="interface">cacertnx.pem</span> file, configuration certificates, application certificates, and mobile OS certificates.</p></td><td>This feature was not provided.</td><td>Advanced features for certificate revocation check.</td></tr><tr title="Версия 8.3.21" class="tag_19 tag_82"><td><a name="f0f5bed9-3330-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Accounting register indexes have been changed when running in PostgreSQL, Oracle Database, and Data accelerator.<p>Indexes change in case of accounting register restructuring including verification and restoration operations.</p></td><td>Accounting register indexes when running in PostgreSQL, Oracle Database, and Data accelerator were different.<p>
</p></td><td>Data acquisition from accounting registers is faster now.</td></tr><tr title="Версия 8.3.21" class="tag_31 tag_29 tag_32"><td><a name="afffe693-ee45-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Android 12 is supported now. Android 4.1 is no longer supported. The minimum supported Android version is 4.4.<p>(<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>) add-in development technology has been changed.</p><p>The mobile application that will be published in Google Play Store and uses the <span class="interface">"Installing applications"</span> functionality must meet the app store requirements effective on July 11, 2022. To meet the requirements, use mobile version 8.3.21.41 or later.</p></td><td>Android version 4.1 was supported.</td><td>The latest Android version is supported.<p> The mobile version of 1C:Enterprise no longer supports devices for which Google stopped releasing security updates.</p></td></tr><tr title="Версия 8.3.21" class="tag_93 tag_10"><td><a name="1fd1e870-4638-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>If you call the <span class="term">EraseInfoBaseData()</span> method and exclusive mode is disabled, the system attempts to enable it. If the attempt is not successful, the method throws an exception. <p>The <span class="term">EraseInfoBaseData()</span> method deletes data in extension object tables, but does not delete extensions installed in the infobase.</p></td><td>In file infobases, the <span class="term">EraseInfoBaseData() </span>method could be successfully executed with disabled exclusive mode.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="tag_34"><td><a name="90c77f50-6b36-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 34); return false;">PDF document operations</a>.<br></td><td>New parameters for the <span class="term">Write()</span> and <span class="term">WriteAsync()</span> methods: FileType.<p>New feature: when saving a PDF document interactively, select a PDF subset for it.</p></td><td>This feature was not provided.</td><td>Saving PDF files in required format (including PDF/A archival formats).</td></tr><tr title="Версия 8.3.21" class="tag_30 tag_31"><td><a name="42e5ba59-762f-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>If the scale is increased on a mobile device on iOS, the interface of the mobile 1C:Enterprise version is also increased in scale.</td><td>This feature was not provided.</td><td>Improved user interface view on mobile devices on iOS.</td></tr><tr title="Версия 8.3.21" class="tag_56"><td><a name="d5c5a61e-82bf-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>If XSL transformation using the <span class="term">XSLTransform</span> object results in an HTML file, the attribute value is URL-encoded for the <span class="term">href</span>, <span class="term">action</span>, and <span class="term">src </span>attributes of various elements, and for the <span class="term">name </span>attribute of the a element. You cannot use the following characters in URL encoding: <span class="interface">@/:=?;#%&amp;,+\</span>.</td><td>If XSL transformation using the <span class="term">XSLTransform</span> object resulted in an HTML file, no values were URL-encoded.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.21" class="tag_56"><td><a name="c43c40d6-c405-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>New feature for the <span class="term">ReadXML() </span>global context method: partial reading. You can read only data specified in an XML file without changing the data in the infobase object. Such reading is enabled if an XML element that describes a 1C:Enterprise object contains the optional <span class="term">dataPart </span>attribute set to <span class="term">True</span>.<p>1C:Enterprise does not allow creating an XML file to perform partial reading.</p><p>Partial reading is implemented for the following configuration objects: catalogs, documents, tasks, business processes, exchange plans, charts of accounts, charts of calculation types, charts of characteristic types, and accumulation, information, calculation, and accounting registers.</p></td><td>Previously the <span class="term">ReadXML() </span>method did not allow partial reading of a configuration object from an XML file.</td><td>Advanced exchange with third-party systems using XML files.</td></tr><tr title="Версия 8.3.21" class="tag_37"><td><a name="a574ee89-ce1d-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Secure connection is used when calling the <span class="term">InternetMail.Logon()</span> method. If the application uses mail servers that do not require server certificate verification, specify these servers in the <span class="interface">conf.cfg</span> configuration file. Now you can do it using the new <span class="term">IgnoreInternetMailServerCertificateVerificationList </span>parameter of the configuration file.</td><td>Unsecure connection was used when calling the <span class="term">InternetMail.Logon()</span> method.</td><td>Enhanced security for using objects related to remote access to various external services.</td></tr><tr title="Версия 8.3.21" class="tag_11"><td><a name="4a2dd2c9-8ea5-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>New feature: if the user, on whose behalf the application trying to attach an add-in (the <span class="term">AttachAddIn()</span> method) in isolation is running, does not have enough rights to create a separate process, the add-in will be attached in non-isolated mode.</td><td>Previously, if the user, on whose behalf the application trying to attach an add-in (the <span class="term">AttachAddIn()</span> method) in isolation was running, did not have enough rights to create a separate process, the add-in was not attached, and it was impossible to use it.</td><td>Now you can use an add-in regardless of whether you have the rights to start a separate process, on whose behalf the application that attaches the add-in is running.</td></tr></table><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bb57241c-f9ba-11eb-8371-0050569f678a">Transition from the previous version to the version 8.3.21</a></h2><ul><li title="Версия 8.3.21" class="tag_0"><a name="bb57241d-f9ba-11eb-8371-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.21.
</li><li title="Версия 8.3.21" class="tag_0"><a name="bb57241e-f9ba-11eb-8371-0050569f678a"></a>Some features that are added in version 8.3.21 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.21" class="tag_0"><a name="2e7256fc-00f5-11ec-8371-0050569f678a"></a>When using a server cluster on Linux, re-configure the requirement to automatically start the cluster at the start of the operating system or the requirement to run different cluster versions at the same time. You need to do this because the systemd subsystem for initialization and management of services is now used to manage the server cluster auto start (instead of the System V subsystem with a similar purpose).<p>
</p></li><li title="Версия 8.3.21" class="tag_0"><a name="43369d62-0413-11ec-8371-0050569f678a"></a>For full-text search to correctly process situations with numerous iterations of full-text search index update (hundreds of thousands iterations) and numerous indexed items, the user must create an index in compatibility mode with <span class="interface">version 8.3.14</span> or later (including the "<span class="interface">Do not use</span>" value).</li></ul><p><a href="#bb572410-f9ba-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h1><a name="4ec18ac3-6c4d-11eb-8371-0050569f678a">Version 8.3.20</a></h1><p title="Версия 8.3.20" class="tag_0"><a name="4ec18ad1-6c4d-11eb-8371-0050569f678a"></a>Version 8.3.20 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#4ec18ac4-6c4d-11eb-8371-0050569f678a">New functionality and changes</a></li><li><a href="#4ec18ac5-6c4d-11eb-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#4ec18ac6-6c4d-11eb-8371-0050569f678a">Optimization</a></li><li><a href="#4ec18ac7-6c4d-11eb-8371-0050569f678a">Changes that affect system behavior</a></li><li><a href="#4ec18ac8-6c4d-11eb-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#4ec18ac9-6c4d-11eb-8371-0050569f678a">Renamed objects</a></li><li><a href="#4ec18aca-6c4d-11eb-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#54c00802-b23f-11eb-8371-0050569f678a">System "1C:Analytics"</a></li><li><a href="#4ec18acb-6c4d-11eb-8371-0050569f678a">Library updates
</a></li><li><a href="#4ec18acc-6c4d-11eb-8371-0050569f678a">Demo configuration changes</a></li><li><a href="#4ec18acd-6c4d-11eb-8371-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#4ec18ace-6c4d-11eb-8371-0050569f678a">Transition from the previous version to the version 8.3.20</a></li></ul><h2><a name="4ec18ac4-6c4d-11eb-8371-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.20" class="compat tag_2 tag_1"><td><a name="bc8f7492-6c64-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.19</span> is now implemented.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.18 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.19 or earlier can now run on version 8.3.20 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.20 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.19 after the migration to version 8.3.20, even if you disable the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.20" class="tag_38 tag_46"><td><a name="ba4a2573-6d35-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br></td><td>You can now adopt integration services and create native integration services in an extension.</td><td>This feature was not provided.</td><td>The configuration extension now provides more features.</td></tr><tr title="Версия 8.3.20" class="tag_74"><td><a name="bec5d89d-704b-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br></td><td>You can now activate a ssoftware license from 1C:Enterprise language. New global context property: <span class="term">LicensesAcquisition</span>.</td><td>This feature was not provided.</td><td>You can now activate software licenses when it is not possible to start Designer.</td></tr><tr title="Версия 8.3.20" class="tag_39"><td><a name="4975c386-704c-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>You can now control the period of event log data separation and reduce the event log from 1C:Enterprise language.<p>New methods: <span class="term">GetEventLogDataStorageSeparationPeriod()</span>, <span class="term">SetEventLogDataStorageSeparationPeriod()</span>, <span class="term">GetEventLogPeriod()</span>, and <span class="term">ReduceEventLog()</span>.</p><p>You can use the <span class="term">Range</span> type to manage locks and the event log.</p></td><td>This feature was not provided. It was possible to control the period of event log data separation and reduce the event log only in interactive mode from Designer.
</td><td>You can now implement all functions of managing the event log using 1C:Enterprise language.
</td></tr><tr title="Версия 8.3.20" class="tag_94"><td><a name="c3a98114-7052-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 94); return false;">Regional settings</a>.<br></td><td>You can now work with regional infobase settings from 1C:Enterprise language.<p>New global context methods: <span class="term">GetRegionalInfobaseSettings()</span>, <span class="term">SetRegionalInforbaseSettings()</span>, and <span class="term">GetRegionalSessionSettings()</span>.</p></td><td>This feature was not provided.<p>Using 1C:Enterprise language, it was possible to obtain the current locale code and the infobase locale code.</p></td><td>It is now possible to work with regional infobase settings using 1C:Enterprise language.</td></tr><tr title="Версия 8.3.20" class="tag_45"><td><a name="b19561b3-7056-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>New query language functions: <span class="term">String()</span>, <span class="term">StringLength()</span>, <span class="term">TrimL()</span>, <span class="term">TrimR()</span>, <span class="term">TrimAll()</span>, <span class="term">Left()</span>, <span class="term">Right()</span>, <span class="term">StrFind()</span>, <span class="term">StrReplace()</span>, <span class="term">Upper()</span>, <span class="term">Lower()</span>, <span class="term">Sin()</span>, <span class="term">Cos()</span>, <span class="term">Tan()</span>, <span class="term">ASin()</span>, <span class="term">ACos()</span>, <span class="term">ATan()</span>, <span class="term">Exp()</span>, <span class="term">Log()</span>, <span class="term">Log10()</span>, <span class="term">Pow()</span>, <span class="term">Sqrt()</span>, <span class="term">Round()</span>, <span class="term">Int()</span>, and <span class="term">StoredDataSize()</span>.<p>If a query uses the above functions, this query will not be sent to Data Accelerator.</p></td><td>These features were not provided.</td><td>Advanced query language features.</td></tr><tr title="Версия 8.3.20" class="compat tag_25 tag_1"><td><a name="edbeadc5-7056-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New functions in the expression language of the Data Composition System: <span class="term">TrimL()</span>, <span class="term">TrimR()</span>, <span class="term">TrimAll()</span>, <span class="term">Left()</span>, <span class="term">Right()</span>, <span class="term">StrFind()</span>, <span class="term">StrReplace()</span>, <span class="term">Upper()</span>, <span class="term">Lower()</span>, and <span class="term">NStr()</span>.<p>If a filter of the Data Composition System is applied to a calculated field that contains the following functions: <span class="term">Sin()</span>, <span class="term">Cos()</span>, <span class="term">Tan()</span>, <span class="term">ASin()</span>, <span class="term">ACos()</span>, <span class="term">ATan()</span>, <span class="term">Exp()</span>, <span class="term">Log()</span>, <span class="term">Log10()</span>, <span class="term">Pow()</span>, <span class="term">Sqrt()</span>, <span class="term">Round()</span>, <span class="term">Int()</span>, or <span class="term">StringLength()</span>, this field will be processed using a query (if possible).</p><p>This change is not implemented in 8.3.19 compatibility mode.</p></td><td>These features were not provided.<p>If a filter of the Data Composition System was applied to a calculated field that contained the following functions: <span class="term">Sin()</span>, <span class="term">Cos()</span>, <span class="term">Tan()</span>, <span class="term">ASin()</span>, <span class="term">ACos()</span>, <span class="term">ATan()</span>, <span class="term">Exp()</span>, <span class="term">Log()</span>, <span class="term">Log10()</span>, <span class="term">Pow()</span>, <span class="term">Sqrt()</span>, <span class="term">Round()</span>, <span class="term">Int()</span>, or <span class="term">StringLength(),</span> this field was calculated during data composition.
</p></td><td>Advanced Data Composition System features.</td></tr><tr title="Версия 8.3.20" class="tag_4"><td><a name="83b5659d-7103-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>External (in relation to the information system) users can now participate in conversations of the iCollaboration System (conversationss and video calls). External users participate in conversations using the website <a href="https://dialog.online" target="_blank">https://dialog.online</a>. External users can only communicate with those users who participate in the conversation to which the external user is invited. To access conversations, an external user must send an invitation.<p>New properties for the <span class="term">CollaborationSystemUser </span>object: <span class="term">External </span>and <span class="term">EmailForAuthentication</span>.</p><p>New methods for the Collaboration System manager: <span class="term">ExternalAccessSupported()</span>, <span class="term">GetExternalAccessURL()</span>, and <span class="term">SendExternalAccessURL()</span>.</p><p>New object: <span class="term">CollaborationSystemUsersFilter</span>. New parameter for the <span class="term">GetUsers()</span> method of the Collaboration System manager: <span class="term">Filter</span>.</p><p>New event handler for the managed application module: <span class="term">CollaborationSystemExternalUserInvitationProcessing</span>.</p><p>Changed the user interface of the Collaboration System.</p></td><td>This feature was not provided.</td><td>Expanded collaboration system capabilities.</td></tr><tr title="Версия 8.3.20" class="tag_19"><td><a name="ec3145a3-72be-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of PostgreSQL version 13 (x86-64). is implemented.</td><td>This PostgreSQL version was not supported.</td><td>Extended list of supported PostgreSQL versions.</td></tr><tr title="Версия 8.3.20" class="tag_4"><td><a name="a12e345d-76a5-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>In the Collaboration System, integration with an arbitrary system is now possible. One-way integration is implemented. The Collaboration System can only receive messages of a certain format. REST interface is used for interaction.<p>New property: <span class="term">CollaborationSystemIntegration.ConnectionPointURL</span>.</p><p>The <span class="term">CollaborationSystemConversation.Integration</span> property becomes writable.</p><p>HTML formatting is limited in message texts.</p></td><td>This feature was not provided.<p>A limited list of external systems was available for integration.</p></td><td>Expanded collaboration system capabilities.</td></tr><tr title="Версия 8.3.20" class="compat tag_38 tag_95 tag_1"><td><a name="6278d2fb-76a8-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>You can now create predefined items in native catalogs of configuration extensions. This change is not implemented in version 8.3.19 compatibility mode (for configuration and configuration extension).
</td><td>Native catalogs of configuration extensions did not support creation of predefined configuration items.</td><td>The configuration extension now provides more features.</td></tr><tr title="Версия 8.3.20" class="compat tag_96 tag_1"><td><a name="d6746b14-7753-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>You can now control the display of form groups of the <span class="term">Page </span>type:<ul><li>The value of the <span class="term">TitleFont </span>property of the form group of the <span class="term">Page </span>type sets the font of the page title. This property for the form group of the <span class="term">Pages </span>type controls the font of the title of all pages in the group (for which the font is not explicitly specified).</li><li>The value of the <span class="term">TitleTextColor </span>property of the form group of the <span class="term">Page </span>type sets the color of the page title text. This property for the form group of the <span class="term">Pages </span>type controls the color of the title text of all pages in the group (for which the title text color is not explicitly specified).
</li></ul><p>This change is not implemented in 8.3.19 compatibility mode.
</p></td><td>These features were not provided.<p>The <span class="term">TitleFont </span>and <span class="term">TitleTextColor </span>properties were not used to style form groups of the <span class="term">Page </span>type.</p></td><td>Improved client application interface.</td></tr><tr title="Версия 8.3.20" class="tag_43"><td><a name="f5174cb8-7757-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>A dynamic list now supports the <span class="interface">Presentation expression</span> property for data set fields and calculated fields. This presentation is only used in a dynamic list table, and is not used for a field that appears outside of a dynamic list.<p>The property value can be set interactively or by using the <span class="term">PresentationExpression </span>property of the <span class="term">DataCompositionSchemaDataSetField </span>and <span class="term">DataCompositionSchemaCalculatedField </span>objects.
</p></td><td>This feature was not provided.</td><td>New formatting options for dynamic lists.</td></tr><tr title="Версия 8.3.20" class="tag_56"><td><a name="f22cafe3-921e-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>New global context property: <span class="term">XMLStringProcessing</span>. Use this property to call the <span class="term">FindDisallowedXMLCharacters()</span> method. The global context method of the same name is deprecated.<p>New global context method to remove invalid XML characters from a string: <span class="term">XMLStringProcessing.RemoveDisallowedXMLCharacters</span>().</p></td><td>It was only possible to find the occurrence of an invalid XML character in a string using the <span class="term">FindDisallowedXMLCharacters</span><span class="term">() </span>global context method.</td><td>Clearing text with XML-like markup from invalid characters is now more convenient.</td></tr><tr title="Версия 8.3.20" class="tag_36"><td><a name="2cfbc7d4-9615-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>You can now get the type of the client application that started a given session. You can now determine that a given client application can work with a standalone mobile client server.<p>New methods for the <span class="term">ClientApplication </span>object: <span class="term">ClientApplicationType()</span> and <span class="term">ClientUsingStandaloneServer()</span>.</p></td><td>This feature was not provided.</td><td>It is now easier to determine the client application used.</td></tr><tr title="Версия 8.3.20" class="tag_64"><td><a name="bd01742f-b6dc-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>The picture library includes the following new pictures:<ul><li><span class="term">MessageHistory</span></li><li><span class="term">ExternalUser</span></li><li><span class="term">ShowPassword</span></li><li><span class="term">HidePassword</span></li></ul></td><td>he listed pictures were not available in the picture library.</td><td>The picture library is upgraded.</td></tr><tr title="Версия 8.3.20" class="tag_29"><td><a name="d05be023-d503-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Astra Linux Special Edition 1.7 and PostgreSQL DBMS 11.10 are now supported from this OS.</td><td>Astra Linux Special Edition 1.7 and PostgreSQL DBMS 11.10 were not supported from this OS.</td><td>Astra Linux Special Edition 1.7 and PostgreSQL DBMS 11.10 are now supported from this OS.</td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18ac5-6c4d-11eb-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.20" class="tag_4"><td><a name="2cd28cdd-7697-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The video call ends automatically and the video call window closes when only the current user remains in the participant list.<p>The default video call window displays all video conference participants without activating the speaking user.</p><p>On screen sharing, the video from the local camera is displayed on the bottom right of the video call window.</p></td><td>The video call window remained open after the video call ended.<p>In the video call window, the speaking participant was activated by default, and the rest were displayed in the column to the right of the speaker.</p><p>On screen sharing, the video from the local camera was not displayed anywhere.</p></td><td>Video calls in the Collaboration System are now more user-friendly.</td></tr><tr title="Версия 8.3.20" class="tag_4"><td><a name="97879f40-769b-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The Collaboration System now has the following options to control the read status for messages:<ul><li>When viewed. The message is marked as read a few seconds after the user opens the message.</li><li>Manually. The message is marked as read once the <span class="interface">Read </span>hyperlink is clicked in the message list.</li><li>On reply or manually. The message is marked as read when replying to the message or clicking the <span class="interface">Read </span>hyperlink.</li></ul><p>
</p><p>The conversation context menu and the <span class="interface">More actions </span>menu now have the <span class="interface">Mark as read </span>command, which is available for conversations that have unread messages.</p></td><td>These features were not provided.<p>Messages were always marked as read a few seconds after being viewed. It was impossible to control this.</p></td><td>It is now easier to manage the read status of messages. The user can configure the control mode for this feature.</td></tr><tr title="Версия 8.3.20" class="tag_10"><td><a name="e19423d7-7752-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented standard data processors that allow you to edit infobase parameters (<span class="interface">Infobase parameters</span>) and the user list (<span class="interface">Users</span>).</td><td>The platform did not allow these operations to be performed in the client application. These tools could be implemented in the application.</td><td>Advanced features of system administration from the client application.</td></tr><tr title="Версия 8.3.20" class="tag_4"><td><a name="99cb0b11-776c-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The Collaboration System menu now contains the <span class="interface">Message history </span>command. This command opens a form that allows you to view messages for the selected date. This form also displays all conversations the user participated in on the selected day.</td><td>This feature was not provided.<p>A single list of all messages for the day was not available.</p></td><td>Improved operations with Collaboration System messages.</td></tr><tr title="Версия 8.3.20" class="tag_30 tag_31"><td><a name="4493cad4-9617-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>On mobile devices, the appearance and behavior of the following system forms has been changed:<ul><li>Report settings save form</li><li>Report option save form</li><li>Dynamic list settings choice form</li><li>Dynamic list settings save form</li><li>Report settings choice form</li><li>Report option choice form</li><li>Form parameter choice form</li><li>Form parameter save form</li><li>Report form</li><li>Report settings form</li><li>Dynamic list settings form</li><li>Settings edit form</li><li>Report option edit form</li><li>Conditional appearance item form</li></ul><p>
We recommend that you check the display of the specified forms in used mobile applications on the new mobile version.</p></td><td>The specified forms looked different in the mobile application.</td><td>Improved interface of some forms on mobile devices.</td></tr><tr title="Версия 8.3.20" class="tag_28 tag_78"><td><a name="d142af13-b221-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>When using the File System extension in Google Chrome and Mozilla Firefox, receiving files over HTTPS is now faster.</td><td>When using the File System extension in Google Chrome and Mozilla Firefox, receiving files over HTTPS took longer.</td><td>When using the File System extension in Google Chrome and Mozilla Firefox, receiving files over HTTPS is now faster.</td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18ac6-6c4d-11eb-8371-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.20" class="tag_6"><td><a name="fe9947e2-6d31-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved performance of the server cluster when working on high load. Optimized use of RAM on Windows.</td><td>RAM was used less effectively on Windows.</td><td>Slightly increased system speed and optimized use of RAM on Windows.</td></tr><tr title="Версия 8.3.20" class="tag_6"><td><a name="f38cbcc6-70ed-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved server cluster stability. Reduced the number of issues that lead to abnormal termination of the server cluster.</td><td>A large number of issues that occurred during cluster operation led to abnormal termination of the server cluster.</td><td>Improved server cluster stability in problematic situations.</td></tr><tr title="Версия 8.3.20" class="tag_45"><td><a name="946eb729-710b-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Optimized the <span class="term">LIKE </span>operator of the query language for a file infobase.</td><td>In a file infobase, the <span class="term">LIKE </span>operator of the query language required more time.</td><td>Improved performance of the <span class="term">LIKE </span>operator in a file infobase.</td></tr><tr title="Версия 8.3.20" class="tag_97"><td><a name="9db55b89-72b6-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 97); return false;">Data access restrictions</a>.<br></td><td>Improved performance of a query that uses the <span class="term">SELECT FIRST</span>, <span class="term">ALLOWED</span>, and <span class="term">ORDER BY</span> statements and a data access restriction at a time. For optimization purposes, a statement that does not depend on the data in the protected table is extracted from the data access restriction query, if possible. The result of this query is placed in a temporary table (but no more than 6 temporary tables), and this temporary table is then used in the original query. The exact behavior implementation depends on the DBMS used.</td><td>A query that used the <span class="term">SELECT FIRST</span>, <span class="term">ALLOWED</span>, and <span class="term">ORDER BY</span> statements and a data access restriction at a time could be executed in a suboptimal way due to the fact that the DBMS could not select an adequate query plan.</td><td>Improved performance of some queries executed on systems with restricted data access.</td></tr><tr title="Версия 8.3.20" class="tag_6"><td><a name="a6efc6b4-72bb-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Fixed identified memory leaks in a working process when sessions served by this working process fail or migrate to another working process.</td><td>There were memory leaks in a working process when sessions serviced by that working process failed or migrated to another working process.</td><td>Improved control over resource usage by the cluster working process.</td></tr><tr title="Версия 8.3.20" class="tag_6 tag_58 tag_38"><td><a name="4a75c98a-72bc-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Reduced RAM consumption by a working process when working with a separated infobase with a large number of separated configuration extensions.</td><td>A working process used more RAM when working with a separated infobase with a large number of separated configuration extensions.</td><td>Reduced RAM consumption by the server cluster in the separated mode.</td></tr><tr title="Версия 8.3.20" class="tag_38 tag_93"><td><a name="a19f1265-72bd-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br></td><td>Optimized infobase restructuring if the infobase contains configuration extensions.</td><td>Restructuring an infobase if it contained configuration extensions took longer.</td><td>Restructuring an infobase if it contains configuration extensions is now faster.</td></tr><tr title="Версия 8.3.20" class="tag_98"><td><a name="338ab291-7695-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 98); return false;">Standalone serverDumping configurations to files/Restoring configurations from files</a>.<br></td><td>Significantly reduced the time to fully load the configuration from XML files when using a standalone server.</td><td>It took a significantly longer time for a standalone server to perform a full configuration load from XML files.</td><td>Improved configuration load from XML files when the standalone server is used.</td></tr><tr title="Версия 8.3.20" class="tag_23"><td><a name="13b51e4a-7756-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Improved generation of a list of characteristics for a flexible type when settings of characteristics of different types (out of the flexible type) differ only in the filter value for the characteristic type.</td><td>Generation of a list of characteristics for a flexible type when settings of characteristics of different types (out of the flexible type) differed only in the filter value for the characteristic type took more time and could slow down various platform mechanisms.</td><td>Improved list of characteristics.</td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18ac7-6c4d-11eb-8371-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.20" class="compat tag_38 tag_1"><td><a name="9528e919-7110-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>You can now extend types of the following adopted objects:<ul><li>Common attribute type if the common attribute is not a separator.</li><li>Type of the "Type of chart of characteristic types" attribute.</li><li>Defined type.</li></ul><p>
</p><p>You can now create native defined types (if the extension compatibility mode is strictly older than version 8.3.19).</p><p>In native objects of the configuration extension, you can now use types of the types <span class="term">AnyRef</span>, <span class="term">CatalogRef</span>, and so on, and defined types.</p><p>References of the type <span class="term">AnyRef</span>, <span class="term">CatalogRef</span>, and so on include references to objects brought in by configuration extensions. The <span class="term">AllRefsType()</span> method includes types from extensions in the return value.</p><p>This change is not implemented in 8.3.19 compatibility mode.</p></td><td>These features were not provided.</td><td>Advanced configuration extension features.</td></tr><tr title="Версия 8.3.20" class="tag_31 tag_20"><td><a name="e66aded6-72ab-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>You can now debug a standalone server for a standalone mobile client. You can now attach three debug items in a single debug session. New debug item: <span class="interface">Standalone server (standalone mobile client)</span>. You can now use performance analyzer to analyze the runtime of all three components of the standalone mobile client.<p>Optimized Debugger.</p></td><td>This feature was not provided.<p>A single debug session could attach up to two debug items at a time.</p></td><td>Simplified debugging of applications that run in an standalone mobile client.</td></tr><tr title="Версия 8.3.20" class="compat tag_16 tag_97 tag_1"><td><a name="75109362-773f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br><a href="#" onclick="onTagClick(this, 97); return false;">Data access restrictions</a>.<br></td><td>Information registers can now use dimensions and separators that include a register in expressions for restricting read and edit access to data.<p>Specifying different access restrictions for individual fields only applies when receiving data from information registers using queries and dynamic lists. When using 1C:Enterprise language objects, it is assumed that all fields are accessed and access is allowed only if it is allowed to all fields (restrictions are imposed on all fields combined with "AND"). When writing a record set, only edit restrictions are applied.</p><p>This change is not implemented in 8.3.19 compatibility mode.</p></td><td>For information registers, in data access restriction expressions, it was not possible to specify dimensions and separators that included a register. For read access to dimensions and separator fields, no data access restrictions were applied.</td><td>Expanded restrictions of access to information register data.</td></tr><tr title="Версия 8.3.20" class="compat tag_38 tag_1"><td><a name="8277e9a2-7767-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>On compilation errors of adopted extension modules, the following behavior is implemented:<ul><li>A notification to the notification center is generated.</li><li>Information about a compilation error is generated (available using the <span class="interface">Information for technical support </span>dialog box).</li><li>The action (that required compilation of the adopted module) is performed without the extension in which the error occurred.</li></ul><p>
If the application is started in debug mode or in version 8.3.19 compatibility mode, this change is not implemented.</p></td><td>On compilation errors of adopted extension modules, the following behavior was observed:<ul><li>A module compilation error was generated.</li><li>The action (that required compilation of the adopted module) was aborted.</li></ul></td><td>The configuration keeps functioning as much as possible in case of extension issues.</td></tr><tr title="Версия 8.3.20" class="tag_27"><td><a name="6e8284ce-77f9-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is now 2.13.</td><td>The format version of configuration dump to XML files was 2.12.</td><td>The configuration dump to XML files now supports new platform features.</td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18ac8-6c4d-11eb-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.20" class="tag_10"><td><a name="d47b3c0d-6c6f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>1C:Enterprise server distribution package for Linux and Windows now includes Java (Liberica JRE).<p>The utilities for installing 1C:Enterprise server have been changed for these operating systems.</p></td><td>Java was not included in 1C:Enterprise server distribution package. To use some features of 1C:Enterprise, the user had to download and install Java on their own.</td><td>Simplified use of 1C:Enterprise components that require Java system, for example, the v2 restructuring mechanism, the licensing utility, and so on.</td></tr><tr title="Версия 8.3.20" class="tag_10"><td><a name="9b5df894-6c70-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The licensing utility is no longer included in 1C:Enterprise distribution package. You can download the licensing utility via 1C:Application update of 1C:ITS Portal (<a href="https://releases.1c.ru/project/EnterpriseLicenseTools" target="_blank">read more</a>).</td><td>The licensing utility was part of 1C:Enterprise distribution package.</td><td>Simplified access to the licensing utility.</td></tr><tr title="Версия 8.3.20" class="tag_38 tag_10"><td><a name="696b5bdc-6d2f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>To specify the name of the file to be signed, use the following parameters:<ul><li><span class="term">/SignCfg</span> command - <span class="term">-SignedFile</span> parameter.</li><li>Agent mode commands <span class="term">config sign-cfg</span> - <span class="term">--signed-file</span> parameter. The <span class="term">--result-file</span> parameter is no longer used.</li></ul><p>
</p><p>To specify the configuration type, use the following parameters:</p><ul><li><span class="term">/SignCfg</span> command - <span class="term">-ConfigurationType</span> parameter. The <span class="term">-Type</span> parameter is no longer used.</li><li>Agent mode commands <span class="term">config sign-cfg</span> - <span class="term">--configuration-type </span>parameter. The <span class="term">--type</span> parameter is no longer used.</li></ul></td><td>To specify the name of the file to be signed, the following parameters were used:<ul><li><span class="term">/SignCfg</span> command - the first positional parameter of the command.</li><li>Agent mode commands <span class="term">config sign-cfg</span> - <span class="term">--result-file</span> parameter.</li></ul><p>
To specify the configuration type, the following parameters were recommended:</p><ul><li><span class="term">/SignCfg</span> command - <span class="term">-Type</span> parameter.</li><li>Agent mode commands <span class="term">config sign-cfg</span> - <span class="term">--type</span> parameter.</li></ul></td><td>The parameters of the <span class="term">/SignCfg</span> command in batch mode and <span class="term">config sign-cfg</span> in Designer agent responsible for specifying file names and configuration types have been unified with similar parameters of other commands.
</td></tr><tr title="Версия 8.3.20" class="tag_10 tag_70 tag_15"><td><a name="6dd447c2-6d3b-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Implemented an application for installing 1C:Enterprise components on Linux. The installer is available in three versions: full, thin client, and training version. The installer works both in graphics mode and batch mode (without a window interface).<p>Package files .deb and .rpm are no longer used to deliver system distribution packages for Linux.</p><p>Implemented an uninstaller.</p><p>New parameters for the <span class="interface">conf.cfg</span> file: <span class="term">PublishDistributiveLocationLinux64 </span>and <span class="term">PublishDistributiveLocationLinux32</span>. The following parameters of this file are no longer supported: <span class="term">PublishDistributiveLocationLinuxDeb64</span>, <span class="term">PublishDistributiveLocationLinuxDeb32</span>, <span class="term">PublishDistributiveLocationLinuxRpm64</span>, and <span class="term">PublishDistributiveLocationLinuxRpm32</span>.</p><p>New attributes for the point element of the default.vrd file: <span class="term">pubdstlin64 </span>and <span class="term">pubdstlin32</span>. The following attributes of this element are no longer supportred: <span class="term">pubdstlindeb32</span>, <span class="term">pubdstlindeb64</span>, <span class="term">pubdstlinrpm32</span>, and <span class="term">pubdstlinrpm64</span>.</p><p>New parameters for the <span class="term">pubdst </span>parameter of the <span class="term">http </span>section of the standalone server configuration file: <span class="term">lin64 </span>and <span class="term">lin32</span>.
</p></td><td>1C:Enterprise applications were delivered in the form of .deb and .rpm packages that could be installed only from the command line.</td><td>Simplified installation of 1C:Enterprise components on Linux.</td></tr><tr title="Версия 8.3.20" class="tag_29 tag_15"><td><a name="3b90355e-72b9-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The following Linux distribution packages are no longer supported:<ul><li>Astra Linux Common Edition 1.11</li><li>Astra Linux Special Edition 1.4 and 1.5</li><li>ALT Linux 7.0 SPT</li></ul></td><td>1C:Enterprise supported the following Linux distribution packages:<ul><li>Astra Linux Common Edition 1.11</li><li>Astra Linux Special Edition 1.4 and 1.5</li><li>ALT Linux 7.0 SPT
</li></ul></td><td>Outdated Linux distribution packages are no longer supported.</td></tr><tr title="Версия 8.3.20" class="tag_29 tag_15"><td><a name="be00b242-72b9-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>1C:Enterprise distribution package for Linux now includes the WebKit1 library version 2.4.11.</td><td>The WebKit1 library was not included in 1C:Enterprise distribution package for Linux.</td><td>1C:Enterprise deployed under Linux no longer depends on the <span class="interface">webkitgtk-3.0.0</span> library.</td></tr><tr title="Версия 8.3.20" class="tag_4"><td><a name="b23c2237-72be-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can now set the user on whose behalf the session will connect to the Collaboration System. This feature is supported only for sessions that run on behalf of the "default user" (a background job started by a scheduled job).<p>New method: <span class="term">CollaborationSystemManager.SetCurrentUser()</span>.</p></td><td>This feature was not provided.<p>A background job that was started by a scheduled job could not connect to the Collaboration System without explicitly specifying the user on whose behalf the scheduled job should be executed.</p></td><td>Simplified connection to the Collaboration System from background jobs that are started using scheduled jobs.</td></tr><tr title="Версия 8.3.20" class="tag_40"><td><a name="c51d078a-76a7-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 40); return false;">Settings storage</a>.<br></td><td>When crawling the list of standard storage settings using the <span class="term">StandardSettingsStorageSelection.Next()</span> method, no attempt is made to deserialize the stored settings. Deserialization is performed only when an attempt is made to access the object that stores the settings (<span class="term">StandardSettingsStorageSelection.Settings</span>). In this case, an exception might be thrown.</td><td>When crawling the list of standard storage settings using the <span class="term">StandardSettingsStorageSelection.Next()</span> method, an attempt was made to deserialize the stored settings. If an incorrect setting object was placed in the storage, an exception was thrown when crawling the settings list.<p>After reaching the selection end, all object properties contain values ​​matching the last selection item. If the selection is empty or the <span class="term">StandardSettingsStorageSelection.Next() </span>method has not been called yet, the selection contains the following values:</p><ul><li>The following properties contain an empty string: <span class="term">ObjectKey</span>, <span class="term">SettingsKey</span>, <span class="term">User</span>, and <span class="term">Presentation</span>.</li><li>The following properties contain the <span class="term">Undefined </span>value: <span class="term">ChangeDate </span>and <span class="term">Settings</span>.</li></ul></td><td>Crawling the list of standard settings is more logical now. When crawling the list, the possibility of an exception caused by incorrect settings is excluded.</td></tr><tr title="Версия 8.3.20" class="tag_14 tag_10"><td><a name="d49b119e-7749-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>OpenID Connect protocol now supports authentication with Authorization Code Flow.<p>New field for the OpenID provider description section of the <span class="interface">default.vrd </span>file (the <span class="term">&lt;providers&gt;</span> element): <span class="term">client_secret</span>.</p><p>We recommend that you switch all production systems to Authorization Code Flow. We do not recommend that you use Implicit Code Flow (the current protocol implementation) for security reasons.
</p></td><td>For OpenID Connect protocol, only authentication with Implicit Code Flow was supported.</td><td>It is now possible to use a more secure version of OpenID Connect protocol.</td></tr><tr title="Версия 8.3.20" class="tag_53"><td><a name="feb0a20f-7756-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>Errors that occur when converting a spreadsheet document to external formats can now be detected. New system enumeration value: <span class="term">ErrorCategory.DocumentConversionError</span>.<p>When analyzing error categories, an application developer should note that the list of categories may expand in new system versions. They should also note that an error can change the belonging to a particular category.</p></td><td>Errors that occurred when converting a spreadsheet document to external formats did not come into a separate category.</td><td>Extended list of error categories.</td></tr><tr title="Версия 8.3.20" class="compat tag_25 tag_1"><td><a name="63556201-7765-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If the data composition schema uses filter with the comparison types <span class="interface">Contains</span>,<span class="interface"> Begins with</span>, <span class="interface">Like</span>, <span class="interface">Does not contain</span>, <span class="interface">Does not begin with</span>, or <span class="interface">Not like </span>for a query field that contains a join where this field is a string type in one part of the join and is not a string type in a different part of the join, a knowingly false condition will be added to the query in the part of the join where the field is a non-string type.<p>We recommend that you analyze data composition schema filters in order to correct such conditions.</p><p>This change is not implemented in 8.3.19 compatibility mode.</p></td><td>If the data composition schema used filter with the comparison types <span class="interface">Contains</span>,<span class="interface"> Begins with</span>, <span class="interface">Like</span>, <span class="interface">Does not contain</span>, <span class="interface">Does not begin with</span>, or <span class="interface">Not like </span>for a query field that contained a join where this field was a string type in one part of the join and was not a string type in a different part of the join, there were no conditions in a query in the part of the join where the field was a non-string type.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.20" class="tag_47"><td><a name="c89daa98-7744-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>All commands that use the infobase (regardless of the execution method) are performed within the full infobase session with checking rights of a user performing the action and registering actions in the event log.<p>Commands related to the server as a whole (for example, commands to receive a list of sessions or terminate a call) do not require to create a session. However, they must be executed on behalf of an infobase user with administrative rights.</p></td><td>The execution of administration interface commands did not require to create a session, check rights of a user performing an administrative action, and register performed actions in the infobase event log.</td><td>Improved standalone server management security.</td></tr><tr title="Версия 8.3.20" class="tag_47"><td><a name="4bab2593-7a93-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>All administration interface commands of a standalone server (except for commands for initializing a server configuration, creating an infobase, and restoring infobase integrity) can be managed by a running instance of a standalone server. To identify the managed server, you can use the ID of the standalone server process (on a local computer, access is performed using IPC technology) or the remote computer address (access is performed using the ssh protocol). For the <span class="interface">ibcmd </span>utility, the <span class="term">--pid</span>, <span class="term">-p</span>, <span class="term">--remote</span>, and <span class="term">-r</span> parameters are implemented to control the way of connecting to a standalone server for command execution.<p>New <span class="interface">ibsrv </span>utility commands for the <span class="interface">ibcmd </span>utility: <span class="term">--config</span>, <span class="term">-c</span>, <span class="term">--system</span>, <span class="term">--dbms</span>, <span class="term">--db-server</span>, <span class="term">--db-name</span>, <span class="term">--db-user</span>, <span class="term">--db-pwd</span>, <span class="term">--request-db-pwd</span>, <span class="term">-W</span>, <span class="term">--db-path</span>, <span class="term">--data</span>, <span class="term">-d</span>, <span class="term">--lock</span>, <span class="term">--temp</span>, <span class="term">-t</span>, <span class="term">--session-data</span>, <span class="term">--log-data</span>, <span class="term">--ftext-data</span>, and <span class="term">--openid-data</span>.</p></td><td>It was not possible to manage a running instance of a standalone server. Standalone server management on a remote computer was not supported. The <span class="interface">ibcmd </span>utility (in standalone server settings) could only change the configuration file content.</td><td>There are two modes available for managing a standalone server:<ul><li>Without a running server instance. In this case, the configuration file of the standalone server is generated.</li><li>With a running server instance. In this case, you must explicitly specify the managed server instance (on the current or remote computer) using the appropriate command-line options.</li></ul></td></tr><tr title="Версия 8.3.20" class="tag_47"><td><a name="93a2dd29-7a95-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>You can now describe several HTTP gateways that serve calls to the infobase. The <span class="term">gates </span>section is implemented in the standalone server configuration file. The infobase of the client application and Internet services is accessed using the <span class="term">gates|http</span> section.<p>For a standalone server, the administration interface can now be accessed via SSH. The standalone server commands are the same as the commands of Designer in agent mode and are listed in the documentation. The <span class="term">gates|ssh </span>section is implemented in the standalone server configuration file.</p></td><td>The standalone server configuration file supported setting up only one HTTP gateway that provided access to the infobase.<p>SSH access to the standalone server was not provided.</p></td><td>Advanced standalone server administration features.</td></tr><tr title="Версия 8.3.20" class="tag_47"><td><a name="ad7e3607-7a99-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>New administration interface commands for a standalone server:<ul><li><span class="term">session</span>. Operations with a list of sessions.</li><li><span class="term">lock</span>. Operations with locks.</li><li><span class="term">infobase config extension</span>. Operations with an extension.</li><li><span class="term">infobase config data-separation list</span>. Getting a list of names of common attributes of the application.</li><li><span class="term">infobase config support disable</span>. Disables the configuration support.</li><li><span class="term">infobase config repair</span>. Verifies and repairs the infobase.</li></ul><p>
</p><p>For the <span class="term">infobase config save </span>command:</p><ul><li>Implemented the<span class="term"> --db </span>parameter that indicates an operation with the database configuration.</li><li>Removed the<span class="term"> --stage</span> parameter that indicates an operation with the main configuration.</li><li>By default, the command is executed with the main configuration.</li></ul><p>
</p><p>For the<span class="term"> infobase config apply</span> command:</p><ul><li>Implemented the <span class="term">--dynamic </span>parameter that allows you to dynamically update the infobase configuration.</li><li>Implemented the <span class="term">--session-terminate </span>parameter that sets the behavior if there are sessions that block the setting of the exclusive mode of access to the infobase.</li></ul><p>
For the <span class="term">infobase config export </span>command, implemented the<span class="term"> --force</span> parameter that allows you to force a full dump using the<span class="term"> --sync </span>parameter if it turns out that files of the configuration located on the hard drive are in the format that differs from the format of the current dump.</p></td><td>These features were not provided.</td><td>Expanded the administrative interface of the standalone server.</td></tr><tr title="Версия 8.3.20" class="compat tag_63 tag_1"><td><a name="8f31e021-921d-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The following properties of the GanttChart, Dendrogram, and PivotChart objects are no longer available in 1C:Enterprise language: <span class="term">SplineMode</span>, <span class="term">SplineStrain</span>, <span class="term">SemiTransparencyMode</span>, <span class="term">SemiTransparencyPercent</span>, <span class="term">FunnelNeckHeight</span>, <span class="term">FunnelNeckWidth</span>, <span class="term">FunnelSpace</span>, <span class="term">ValuesBySeriesConnection</span>, <span class="term">ValuesBySeriesConnectionLines</span>, <span class="term">ValuesBySeriesConnectionColor</span>, <span class="term">SeriesOrderInLegend</span>, <span class="term">ValuesAxis</span>, <span class="term">PointsAxis</span>, <span class="term">SecondaryValuesAxis</span>, <span class="term">PointsAxisValuesSource</span>, <span class="term">PointsAxisSeries</span>, <span class="term">BubbleSizeValueSource</span>, <span class="term">BubbleSizeCommonSeries</span>, <span class="term">BubbleSizing</span>, <span class="term">BubbleChartNegativeValuesShowMode</span>, <span class="term">DefaultBubbleSize</span>, <span class="term">MinBubbleSize</span>, <span class="term">MaxBubbleSize</span>, <span class="term">PointsConnection</span>, <span class="term">BarChartPointsOrder</span>, <span class="term">GradientPaletteMaxColors</span>, <span class="term">GradientPaletteStartColor</span>, <span class="term">GradientPaletteEndColor</span>, <span class="term">ValuesReferenceLines</span>, <span class="term">ValuesReferenceBands</span>, <span class="term">PointsReferenceLines</span>, <span class="term">PointsReferenceBands</span>, <span class="term">ColorPaletteDescription</span>, <span class="term">ReferenceBandsColorPaletteDescription</span>, <span class="term">NonNumericValuesUse</span>, <span class="term">PointsConnectionOnMissedValues</span>, <span class="term">DonutChartInnerRadius</span>, <span class="term">ValueTooltipRepresentation</span>, <span class="term">ValuesToolTipFillType</span>, <span class="term">SelectionModeShowPopUpInformationalLineOfPoints</span>, <span class="term">ShowPopuUpInformationalLineOfValues</span>, and <span class="term">ValuesEditMode</span>.<p>The following properties of the <span class="term">GanttChartPlotArea</span>, <span class="term">DendrogramPlotArea</span>, and <span class="term">PivotChartPlotArea</span> objects are no longer available in 1C:Enterprise language: <span class="term">PointsScale</span>, <span class="term">ValuesScale</span>, <span class="term">AdditionalValuesScale</span>, and <span class="term">SeriesScale</span>.</p><p>This change is not implemented in 8.3.19 compatibility mode.</p></td><td>The specified properties were available in 1C:Enterprise language but had no effect.
</td><td>Excluded access to undocumented properties of chart objects.</td></tr><tr title="Версия 8.3.20" class="tag_10 tag_70 tag_15"><td><a name="8b7500e3-9d25-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Changed format of installation packages for Linux client applications used on updating client applications via the <span class="interface">distr</span> directory. The file names for client application distribution packages follow the form <span class="interface">win-mac-clients-distr-ver</span>.<span class="interface">arch</span>.<span class="interface">run</span> and <span class="interface">all-clients-distr-ver</span>.<span class="interface">arch</span>.<span class="interface">run</span>, where <span class="interface">ver</span> is the full version number and <span class="interface">arch</span> is the processor architecture for which the distribution package is intended. The .deb and .rpm packages are no longer supported.<p>You can now install client application distribution packages and other 1C:Enterprise components at the same time.</p></td><td>Installation packages for client application distribution packages were available in .deb and .rpm package formats. It was not possible to install a client application distribution package and other 1C:Enterprise components at the same time.</td><td>Simplified installation of 1C:Enterprise components on Linux. The installation of client application distribution packages is unified with other operating systems as much as possible.</td></tr><tr title="Версия 8.3.20" class="compat tag_26 tag_1"><td><a name="a97f5d13-9dbf-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When exporting a spreadsheet document to Microsoft Excel format, extended line spacing is used to calculate the height of document lines with multiline text (including text with automatic line wrapping).<p>We recommend that you check that spreadsheet documents saved in Microsoft Excel format are correct and, if necessary, make changes to the algorithm for generating these documents.</p><p>This change is not implemented in 8.3.19 compatibility mode.</p></td><td>When exporting a spreadsheet document to Microsoft Excel format, the line spacing equal to that in the spreadsheet document was used to calculate the height of document lines with multiline text. However, the line spacing in a spreadsheet document and Microsoft Excel is different, which led to a violation of the document display.</td><td>The Microsoft Excel document obtained as a result of spreadsheet document export is now more correct.</td></tr><tr title="Версия 8.3.20" class="compat tag_99 tag_1"><td><a name="7342e433-c784-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 99); return false;">Window-based interface</a>.<br></td><td>In <span class="interface">Taxi </span>interface using thin client or web client:<ul><li>If the home page is active, the <span class="term">ActiveWindow()</span> method returns an object of the <span class="term">ClientApplicationForm </span>type, in which:</li><ul><li>Property <span class="term">HomePage </span>is set to <span class="term">True</span>.</li><li>Property <span class="term">Content </span>contains home page forms.
</li></ul><li>For the form located on the <span class="term">Home </span>page, the Window property contains an object of the <span class="term">ClientApplicationForm </span>type, in which:</li><p>For the active home page, the <span class="term">Window </span>home page form property and the <span class="term">ActiveWindow()</span> method return the same object.
</p></ul><p>This change is not implemented in 8.3.19 compatibility mode.</p></td><td>In <span class="interface">Taxi </span>interface using thin client or web client:<ul><li>If the home page is active, the <span class="term">ActiveWindow()</span> method returned:</li><li>If the home page is active, the <span class="term">Window </span>property of the home page form returned:</li></ul><p>
</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.20" class="tag_47 tag_29"><td><a name="6ae8f12b-325b-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The standalone server does not support 32-bit Windows operating systems.</td><td>The standalone server supported 32-bit Windows operating systems.</td><td>32-bit Windows operating systems are no longer supported by the standalone server.</td></tr><tr title="Версия 8.3.20" class="tag_47 tag_29"><td><a name="56a866c9-c610-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Standalone server is no longer supported on 64-bit Windows Server 2003 and Windows XP.</td><td>Standalone server was supported on 64-bit Windows Server 2003 and Windows XP.</td><td>Standalone server is no longer supported on obsolete Windows operating systems.</td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18ac9-6c4d-11eb-8371-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.20" class="tag_0"><td><a name="1755370c-710b-11eb-8371-0050569f678a"></a>The method for checking the availability of video conferences of the Collaboration System. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">VideoConferencesAvailable</span><span class="term">().</span></li></ul></td><td><ul><li><span class="term">VideoConferencesSupported().</span></li></ul></td></tr><tr title="Версия 8.3.20" class="tag_0"><td><a name="430cbef9-72bf-11eb-8371-0050569f678a"></a>Presentation of the <span class="term">DataCompositionSchema.NestedDataCompositionSchemas </span>property. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">NestedDataCompositionSchema</span>.</li></ul></td><td><ul><li><span class="term">NestedDataCompositionSchemas</span>.</li></ul></td></tr><tr title="Версия 8.3.20" class="tag_0"><td><a name="92efd099-a26f-11eb-8371-0050569f678a"></a>Description option of the <span class="term">MobileClientSign</span> property for the <span class="term">Configuration</span> metadata object. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">MobileClientSign</span></li></ul></td><td><ul><li><span class="term">MobileClientSignature</span></li></ul></td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18aca-6c4d-11eb-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.20" class="tag_30"><td><a name="a583433a-776e-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>The mobile platform now supports automated testing. For automated testing to work, the test manager infobase with which the mobile application will interact must be available in the network.<p>For the <span class="term">/TESTCLIENT </span>command of the mobile application command line, the <span class="term">-TURL </span>parameter is implemented to specify the publication URL of the test manager.</p></td><td>Automated testing was not available on the mobile platform.</td><td>Now you can use the mobile platform for automated testing of applications.</td></tr><tr title="Версия 8.3.20" class="tag_31"><td><a name="4e185f16-7772-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>When a new session starts, the server cluster automatically closes the previous session associated with this mobile client application if this session exists.<p>If the mobile client connects to the server cluster version 8.3.19 or later, or the infobase list is displayed, the mobile client application explicitly sends a request to close the previous session if that session was not closed.</p><p>New event handlers in the application module: <span class="term">OnClientApplicationWakeup</span> and <span class="term">OnClientApplicationHibernation</span>.</p></td><td>When the application was minimized or the device fell asleep, the mobile client did not notify the server cluster of this. As a result, the session did not hibernate. It was also impossible to determine the application recovery after falling asleep.</td><td>Reduced license consumption for standard mobile client application usage patterns when the application is not closed but minimized.<p>It is now possible to detect when the mobile application falls asleep and wakes up.
</p></td></tr><tr title="Версия 8.3.20" class="tag_20"><td><a name="8d1db6ec-960d-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Implemented the <span class="interface">Mobile application build service</span> standard data processor that provides access to the service for building mobile applications that can run Android and iOS. The service functions only if you have Internet access. To use the service, registration on the website for <a href="https://developer.1c.ru/" target="_blank">Read more</a>.developers is required.</td><td>This feature was not provided.</td><td>The service should simplify and facilitate the build of mobile applications running Android and iOS.</td></tr><tr title="Версия 8.3.20" class="tag_31 tag_30"><td><a name="395b5f4e-9616-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>New value for the <span class="term">UsualGroupBehavior</span> and <span class="term">FormPagesRepresentation</span> system enumerations: <span class="term">Auto</span>. When the value is set to <span class="term">Auto</span>, the display of form items on a mobile device is handled in a special way.</td><td>This feature was not provided.<p>It was impossible to set the system behavior so that the system would automatically change the behavior of the group and form pages on a mobile device.</p></td><td>Simplified development of some form types for mobile devices.</td></tr><tr title="Версия 8.3.20" class="tag_31"><td><a name="f22dc975-ba2e-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile client now supports a specialized server application deployed on the collaboration server. When such an application is deployed on the collaboration server, the stability of video calls and the number of simultaneous video conference participants increase. The mobile client supports all acceptable methods of making video calls.</td><td>The mobile client made video calls in p2p mode. That is, the mobile client exchanged video streams with computers of all video call participants.</td><td>Improved stability of video calls from the mobile client. Improved display of video call participants.</td></tr><tr title="Версия 8.3.20" class="tag_86 tag_31"><td><a name="1cce6115-c790-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The <span class="term">LocationInCommandBar </span>property of the form button is now supported in mobile client. This property is similar to the one from the personal computer platform, with the following exceptions:<ul><li>The <span class="term">Auto </span>value in the personal computer platform is <span class="term">InCommandBarAndInAdditionalSubmenu</span>. The <span class="term">Auto </span>value in the mobile client is <span class="term">InCommandBar</span>.</li><li>If the <span class="term">InCommandBar </span>display mode is selected for a command bar button, but the button does not fit the command bar, the <span class="term">InAdditionalSubmenu </span>display mode will be selected.</li></ul></td><td>The <span class="term">LocationInCommandBar </span>property of the form button in mobile client was supported with limitations: the <span class="term">OnlyInAllActions </span>property was only emulated.</td><td>Now you can manage the same way button display in the command bar of mobile client and client applications for personal computers.</td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="54c00802-b23f-11eb-8371-0050569f678a">System "1C:Analytics"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.20" class="tag_100"><td><a name="ce16174d-b23f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>Implemented mode for viewing charts and dashboards. In this mode, the edit functions that are not required for analyzing information (layout of dashboard elements, adding new elements) are disabled. The mode is enabled automatically for "foreign" charts and dashboards.</td><td>This feature was not provided. Users interacted with all system objects in edit mode.</td><td>Working with dashboard data is now more convenient.</td></tr><tr title="Версия 8.3.20" class="tag_101"><td><a name="059b8f66-b240-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>Updated the selection panel.</td><td>The selection panel had a different appearance.</td><td>Improved chart selection panel appearance.</td></tr><tr title="Версия 8.3.20" class="tag_102"><td><a name="4d3be94b-b240-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 102); return false;">Analytics - desktop</a>.<br></td><td>You can now transfer links to your folders to other users.</td><td>This feature was not provided.</td><td>Users can share sets of charts and dashboards.</td></tr><tr title="Версия 8.3.20" class="tag_100"><td><a name="d99d1096-b240-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>You can now configure the link transition when clicking anywhere on an element of any dashboard.</td><td>This feature was not provided.</td><td>Implemented more interactive features for dashboards.</td></tr><tr title="Версия 8.3.20" class="tag_100"><td><a name="ce5c046b-b241-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>You can now set the text style and specify links when editing text elements of the dashboard.</td><td>This feature was not provided.</td><td>Upgraded customization of text elements of dashboards.</td></tr><tr title="Версия 8.3.20" class="tag_101"><td><a name="3fff1780-b242-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>In <span class="interface">Pivot table</span> charts, you can now pin rows and columns.</td><td>This feature was not provided.</td><td>The pivot table display customization is now more flexible.</td></tr><tr title="Версия 8.3.20" class="tag_100"><td><a name="a07bef3c-b243-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>You can now scale charts by rolling the mouse wheel while pressing the Ctrl key. Rolling the mouse wheel without pressing the Ctrl key does not scale the chart.</td><td>Charts were scaled by rolling the mouse wheel, without using the keyboard. This use was unexpected and interfered with the dashboard scrolling.</td><td>The scaling of charts is now more expected and does not interfere with the dashboard scrolling.</td></tr><tr title="Версия 8.3.20" class="tag_101"><td><a name="fb65452f-b243-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>New chart type: stacked lines.</td><td>This feature was not provided.</td><td>Extended list of used chart types.</td></tr><tr title="Версия 8.3.20" class="tag_103"><td><a name="1bea7b6f-b246-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 103); return false;">Analytics - other</a>.<br></td><td>System objects (charts, dashboards, and folders) are automatically deleted from the database if there are no users who use these objects on their desktop.</td><td>This feature was not provided.<p>Unused objects were not deleted from the database.</p></td><td>Optimized use of 1C:Analytics database.</td></tr><tr title="Версия 8.3.20" class="tag_101"><td><a name="760bdce6-b246-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>Upgraded indicator chart customization and appearance.</td><td>The indicator appearance was determined automatically. The customization options were limited.</td><td>Improved indicator appearance. Now users have more customization options for this type of chart.</td></tr><tr title="Версия 8.3.20" class="tag_101"><td><a name="8ae984b2-b246-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>Two different facts on axes can now be displayed for a bubble char.</td><td>This feature was not provided. Only the following combinations were available: fact-dimension and dimension-dimension.</td><td>Expanded visualization features for a bubble chart.</td></tr><tr title="Версия 8.3.20" class="tag_103"><td><a name="a7e2e5b6-b246-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 103); return false;">Analytics - other</a>.<br></td><td>New feature for 1C:Analytics: a notification center that stores the latest system messages for viewing.</td><td>This feature was not provided.<p>After the error notification disappeared, it could not be viewed anywhere.</p></td><td>Reporting system issues is now easier.</td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18acb-6c4d-11eb-8371-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.20" class="tag_0"><a name="eb490cd5-6c64-11eb-8371-0050569f678a"></a>The libetpan library is updated to version 1.9.4.</li><li title="Версия 8.3.20" class="tag_0"><a name="17492ec9-6c65-11eb-8371-0050569f678a"></a>The boost library is updated to version 1.74.</li><li title="Версия 8.3.20" class="tag_0"><a name="52d2fdf2-6c65-11eb-8371-0050569f678a"></a>The OpenSSL library is updated to version 1.1.1k.</li><li title="Версия 8.3.20" class="tag_0"><a name="62b9813c-6c65-11eb-8371-0050569f678a"></a>The libssh library is updated to version 0.9.4.<p>
</p></li><li title="Версия 8.3.20" class="tag_0"><a name="0044eb71-ed83-11ec-aa69-0050569f678a"></a>The <span class="interface">libpq</span> library is updated to version 14.2-3.1C.</li></ul><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18acc-6c4d-11eb-8371-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.20" class="tag_0"><a name="c59cbe21-ca9d-11eb-8371-0050569f678a"></a>New commands in the counterparty form: <span class="interface">Invite To Conversations</span>, <span class="interface">Open Conversation</span>, <span class="interface">V</span>i<span class="interface">deo</span><span class="interface"> Call</span>. Use the commands to work with the collaboration system external users.</li><li title="Версия 8.3.20" class="tag_0"><a name="fee35e12-ca9e-11eb-8371-0050569f678a"></a>New feature demonstrating the possibility of the planner item border linking in the <span class="interface">Calendar </span>form of the <span class="interface">Meetings </span>catalog. When the display of appointments of all users is enabled, a user can drag a calendar event only if the event initially belonged to the user.</li><li title="Версия 8.3.20" class="tag_0"><a name="52fbdb8e-ca9f-11eb-8371-0050569f678a"></a>New section <span class="interface">Additional resources </span>in the <span class="interface">Guide</span>. It contains hyperlinks used to:<ul><li>Switch to demo configurations.</li><li>Download demo configurations.</li></ul></li><li title="Версия 8.3.20" class="tag_0"><a name="0929069f-2bfe-11ec-aa69-0050569f678a"></a>In the mobile demo application, working with secure data storage is switched to asynchronous calls using promises.</li><li title="Версия 8.3.20" class="tag_0"><a name="4432194c-2bfe-11ec-aa69-0050569f678a"></a>New feature: code of the <span class="term">OnClientApplicationWakeup() </span>handler, which is triggered in mobile client in the standalone mode to perform data exchange with the main server after the client application wakeup.</li></ul><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18acd-6c4d-11eb-8371-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.20" class="tag_47 tag_27"><td><a name="10fe54cb-def5-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>Optimized several infobase operations executed using the administration utility (<span class="interface">ibcmd</span>) by connecting to a working instance of a standalone server. The optimized operations include but are not limited to: export of configurations to XML files, partial import of configurations from XML files. database configuration update;</td><td>It took longer time to execute some infobase operations executed using the administration utility (<span class="interface">ibcmd</span>) by connecting to a working instance of the standalone server.</td><td>Accelerated execution of some operations of the infobase managed by the standalone server.</td></tr><tr title="Версия 8.3.20" class="tag_47 tag_20"><td><a name="c5afff9d-def6-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>You can now start 1C:Enterprise Development Tools for the interactive launcher. If 1C:Enterprise Development Tools are not installed yet, you will be prompted to install the product. You can manage the button visibility by a check box in the interactive launcher dialog box.<p>For an infobase that uses connection via HTTP(s) protocol, you can now specify the development control address in the connection settings. To use this feature for an infobase located on a web server, click <span class="interface">More</span>.</p></td><td>This feature was not provided.<p>The interactive launcher did not support 1C:Enterprise Development Tools.</p></td><td>Extended interactive launcher features. Improved integration of 1C:Enterprise Development Tools with other 1C:Enterprise application components.</td></tr><tr title="Версия 8.3.20" class="tag_47"><td><a name="a5bfd4e1-defc-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>Now you can find information on a debugger in the administration interface of a standalone server via SSH protocol (<span class="term">infobase-tools debug-info</span>). The parameter set returned by the command now includes the <span class="term">infobase-name</span> optional parameter. It contains the name of the infobase to be debugged.</td><td>This feature was not provided.</td><td>Simplified connection of 1C:Enterprise Development Tools debugger to the infobase managed by a standalone server.</td></tr><tr title="Версия 8.3.20" class="tag_20 tag_47 tag_27"><td><a name="8496ca2f-df00-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>You can now disable configuration integrity check upon importing a configuration from XML files. This check can be useful if a previously exported configuration is imported.<p>To enable this feature, a special parameter is implemented for the following import tools:</p><ul><li>Command line to start 1C:Designer. New<span class="term"> -NoCheck </span>parameter for the<span class="term"> /LoadConfigFromFiles </span>command.</li><li>1C:Designer in the agent mode. New <span class="term">--no-check </span>parameter for the config <span class="term">load-config-from-files </span>command.</li><li>Standalone server management utility (<span class="interface">ibcmd</span>). New <span class="term">--no-check</span> parameter for the <span class="term">infobase config import </span>command.</li></ul></td><td>This feature was not provided.</td><td>Accelerated configuration import from XML files for some scenarios.</td></tr><tr title="Версия 8.3.20" class="tag_28"><td><a name="43e40c3d-df01-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>You can now automatically open a standard function form when starting the web client. Opening standard data processor forms using 1C:Enterprise language or client application user interface (following a link) is not supported.</td><td>This feature was not provided.</td><td>Opening standard functions form is now available from 1C:Enterprise Development Tools.</td></tr><tr title="Версия 8.3.20" class="tag_14"><td><a name="bb5a92dd-df07-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>You can now disable opening home page forms upon opening the client application. New <span class="term">DisableHomePageForms </span>command for the startup command line of thin client and web client.</td><td>This feature was not provided.</td><td>Accelerated opening of the client application.</td></tr><tr title="Версия 8.3.20" class="tag_20 tag_47 tag_27"><td><a name="0459b8fb-df09-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>When importing the configuration from XML files, you can now import data from a ZIP archive containing configuration XML files. The archive structure must match the import directory structure.<p>The <span class="interface">Import configuration from files </span>command in 1C:Designer allows you to select not only a directory but also a ZIP archive file.</p><p>To use this feature, a special parameter is now available for the following import tools:</p><ul><li>Command line to start 1C:Designer. New <span class="term">-Archive </span>parameter for <span class="term">/LoadConfigFromFiles </span>command.</li><li>1C:Designer in the agent mode. New <span class="term">--archive </span>parameter for config <span class="term">load-config-from-files </span>command.</li><li>Standalone server management utility (<span class="interface">ibcmd</span>). New<span class="term"> -archive </span>parameter for <span class="term">infobase config import </span>command. For commands <span class="term">infobase config import </span>and<span class="term"> infobase config import all-extensions</span>, a directory or a ZIP archive can be specified in the unnamed parameter. The <span class="term">--import </span>parameter for the <span class="term">infobase create </span>command can contain a directory path or a ZIP archive name.</li></ul></td><td>This feature was not provided.</td><td>Accelerated import of configuration files, especially if files to be imported are transferred via communication channels before import.</td></tr><tr title="Версия 8.3.20" class="tag_47"><td><a name="bf221365-df09-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>The standalone server generates standard text messages into the standard output stream (<span class="term">stdout</span>) in the following cases:<ul><li>After the standalone server is ready and after the internal state update is completed: <span class="interface">1C:Enterprise 8.3 (x86-64) (&lt; version number&gt;) Stand-alone Server ready</span>.</li><li>After the infobase configuration update (during the internal state update): <span class="interface">1C:Enterprise 8.3 (x86-64) (&lt; version number&gt;) Stand-alone Server refreshing</span>.</li></ul></td><td>This feature was not provided.</td><td>Now it is easier to get a standalone server status when some management commands are executed.</td></tr><tr title="Версия 8.3.20" class="tag_20 tag_47"><td><a name="73ed6937-df0a-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>Now you can get metadata generation ID of the infobase configuration. This ID changes every time the configuration is changed in any way.<p>To use this feature, commands are now available for the following import tools:</p><ul><li>Command line to start 1C:Designer. New <span class="term">/GetConfigGenerationID </span>command.</li><li>1C:Designer in the agent mode. New <span class="term">config generation-id </span>command.</li><li>Standalone server management utility (<span class="interface">ibcmd</span>). New <span class="term">infobase</span> <span class="term">config generation-id </span>command.</li></ul></td><td>This feature was not provided.</td><td>Now you can check whether the infobase configuration was changed since the latest check.</td></tr><tr title="Версия 8.3.20" class="tag_20 tag_27"><td><a name="2c8fe097-df0b-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>Configuration support rules settings are ignored for full configuration import from XML files. The current configuration is completely replaced including support information.</td><td>Full configuration import from XML files was impossible if support rules were set. For full configuration import from XML files, configuration support had to be disabled.</td><td>The behavior of full import from XML files is now identical to the configuration import from a CF file.</td></tr><tr title="Версия 8.3.20" class="tag_20"><td><a name="af7167fb-df0c-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Modified format of JSON messages used in 1C:Designer in the agent mode. More than two response options can be specified in messages of the <span class="term">questions </span>type.</td><td>Only two response options could be specified for JSON messages of the <span class="term">questions </span>type in 1C:Designer in the agent mode.</td><td>Extended features of the format of JSON messages used for interaction with 1C:Designer in the agent mode.</td></tr><tr title="Версия 8.3.20" class="tag_27 tag_20"><td><a name="d381dfe3-df0e-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The standalone server no longer supports a linear format for configuration import from XML files. Only a hierarchical format is used for configuration import from XML files.</td><td>The standalone server supported configuration import from XML files in linear and hierarchical formats.</td><td>The standalone server no longer supports the obsolete export format.</td></tr><tr title="Версия 8.3.20" class="compat tag_40 tag_1"><td><a name="a9f51bab-f45f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 40); return false;">Settings storage</a>.<br></td><td>A recoverable error in 1C:Enterprise language occurs when accessing properties of the <span class="term">StandardSettingsStorageSelection </span>object if dataset is finished or it is empty.<p>We recommend that you analyze the <span class="term">StandardSettingsStorageSelection </span>object usages for possible errors that occur if dataset is finished or it is empty.</p><p>This change is not implemented in 8.3.19 compatibility mode.</p></td><td>An attempt to access properties of the <span class="term">StandardSettingsStorageSelection </span>object showed different behavior in different cases:<ul><li>If dataset was finished, the latest read data was left in the object properties.</li><li>If dataset was empty, the <span class="term">Undefined </span>values were in the object properties.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.20" class="tag_45"><td><a name="13613c8d-f460-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Accelerated execution of the query that uses fields in temporary tables received from other temporary tables with high nesting.</td><td>Execution of the query that used fields in temporary tables received from other temporary tables with high nesting took more time.</td><td>Improved query execution in some scenarios.</td></tr><tr title="Версия 8.3.20" class="tag_28 tag_56"><td><a name="a9d4143d-f460-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>The <span class="term">XMLStringProcessing </span>global context property is now available in web client.</td><td>The <span class="term">XMLStringProcessing </span>global context property was not available in web client.</td><td>Web client now supports methods of search and deletion of invalid XML characters in arbitrary strings.</td></tr><tr title="Версия 8.3.20" class="tag_77"><td><a name="946c044d-f462-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>If the printer used for printing by 1C:Enterprise platform is available, this information will be cached. If the same printer is used for printing within 60 seconds, its availability state is received from the cache.</td><td>When using the same printer multiple times consecutively, the printer availability for each print attempt was defined by the actual state of the printer.</td><td>Accelerated printing when the same printer is used to print several documents consecutively.</td></tr><tr title="Версия 8.3.20" class="tag_19"><td><a name="db0afca3-f4fe-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>When using PostgreSQL DBMS, the result of <span class="term">MIN() </span>and <span class="term">MAX() </span>query language functions for a <span class="term">Boolean </span>type field does not depend on the order of <span class="term">Boolean </span>and <span class="term">NULL </span>type values in a dataset.</td><td>When using PostgreSQL DBMS, the result of <span class="term">MIN() </span>and <span class="term">MAX() </span>query language functions for a <span class="term">Boolean </span>type field depended on the order of <span class="term">Boolean </span>and <span class="term">NULL </span>type values in a dataset.</td><td>Eliminated unexpected system behavior. Query language functions <span class="term">MIN() </span>and <span class="term">MAX() </span>now work in the same manner in all supported DBMS.</td></tr><tr title="Версия 8.3.20" class="tag_4"><td><a name="7dfe55c5-f503-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can re-register an infobase in the collaboration system without explicitly specifying an email after disconnecting the infobase from the collaboration system. The email address specified during initial registration will be used for re-registration. All objects created in the collaboration system will be available after re-registration. If an infobase was never connected to the collaboration system, re-registration without email address specification will be impossible.<p>Property <span class="term">CollaborationSystemInfobaseRegistrationParameters.EmailAddress </span>is not required.</p><p>Now you can take advantage of re-registration for the <span class="interface">Collaboration system management </span>data processor.</p></td><td>Infobase re-registration in the collaboration system was possible only with email address specification.</td><td>Now you can re-register an infobase in the collaboration system if the infobase was previously disconnected from the collaboration system and the email address used for initial registration was forgotten.</td></tr><tr title="Версия 8.3.20" class="tag_84"><td><a name="c3072a1f-f507-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Now you can use Turkmenian (<span class="term">tk </span>code) in the following cases:<ul><li>To specify in regional infobase settings dialog box.</li><li>To specify it as the session localization code (<span class="term">/VL</span> startup command-line option).</li><li>To view the calendar in Turkmenian.</li></ul></td><td>These features were not provided.</td><td>Limited support of Turkmenian is now available in 1C:Enterprise platform.</td></tr><tr title="Версия 8.3.20" class="tag_25 tag_30 tag_31"><td><a name="d844ed8d-f528-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>In the tables that contain data composition system settings in mobile client and the mobile platform application, the following commands are available only in the context menu of the corresponding table row: <span class="interface">User-defined settings item properties, Set presentation, Use as field value, Set title, Expand, Group, Group conditions, Group fields,</span> and<span class="interface"> Ungroup</span>. The update is applied to report settings forms, dynamic list settings, and report option editing.</td><td>In the tables that contained data composition system settings in mobile client and in the mobile platform application, the following commands were available in the context menu of the corresponding table row and in the <span class="interface">More </span>menu: <span class="interface">User-defined settings item properties, Set presentation, Use as field value, Set title, Expand, Group, Group conditions, Group fields</span>, and <span class="interface">Ungroup</span>. A command from the <span class="interface">More </span>menu had no effect.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.20" class="tag_91"><td><a name="73a66f2f-056b-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 91); return false;">Collaboration System</a>.<br></td><td>The <span class="interface">Mark as read</span> setting status (in the setup dialog box of the Collaboration System) is saved on the collaboration system server. If there is no such setting on the collaboration system server, an attempt is made to read the setting from the local storage.</td><td>The <span class="interface">Mark as read</span> setting status (in the setup dialog box of the Collaboration System) was saved to a local storage of a user computer.</td><td>The same <span class="interface">Mark as read</span> setting value (in the setup dialog box of the Collaboration System) for any device used by a user.</td></tr><tr title="Версия 8.3.20" class="tag_45 tag_14"><td><a name="473f9460-274a-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>New commands in Query Wizard that runs in thin client: "search" and "cancel search" for all wizard form lists. The commands are available from the context menu or the <span class="interface">More </span>menu.</td><td>In Query Wizard that runs in thin client, the "search" and "cancel search" commands were not available in the wizard form lists. The commands were available only via hotkeys, which was not clear to users.</td><td>More user-friendly search in Query Wizard in thin client.</td></tr><tr title="Версия 8.3.20" class="tag_30 tag_31"><td><a name="c7e51551-2bfa-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The file selection dialog box for the mobile application running on Android or iOS is updated. The dialog box has become more convenient and faster. You can now create a file directly from the file selection dialog box. The user can now switch the dialog box to the multiple selection mode (if this mode is available).<p>You can now set up the sections that will be available when selecting a file. New property: <span class="term">FileSelectionDialogBox.Sections</span>.</p><p>New feature: filter files by MIME type. New property: <span class="term">FileSelectionDialogBox.EncType</span>.</p></td><td>The file selection dialog box for the mobile application running on Android and iOS was less convenient and slower.</td><td>Improved operation of the file selection dialog box in the mobile application running on Android and iOS.</td></tr><tr title="Версия 8.3.20" class="tag_32"><td><a name="cb05b370-2bfe-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>The mobile application build service now supports the mobile version 8.3.19 of 1C:Enterprise.</td><td>The mobile application build service did not support the mobile version 8.3.19 of 1C:Enterprise.</td><td>Extended list of supported mobile versions of 1C:Enterprise in the mobile application build service</td></tr><tr title="Версия 8.3.20" class="tag_15 tag_29"><td><a name="b2330901-0bd6-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following distribution packages for Linux operating system are supported now:<ul><li>Debian 10</li><li>Mint 20</li><li>Oracle Linux 7</li><li>Oracle Linux 8</li><li>RHEL 8</li><li>Ubuntu 20.04 LTS</li><li>ALT Education 10</li><li>ALT Workstation 10</li><li>ALT Workstation K 10</li><li>ALT Server 10 (only 64-bit version)</li><li>RED OS 7.3 (only 64-bit version).</li></ul></td><td>The distribution packages were not supported.</td><td>Extended list of supported Linux distribution packages.</td></tr><tr title="Версия 8.3.20" class="tag_15 tag_29"><td><a name="37c83801-0bd7-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following distribution packages for Linux operating system are no longer supported: <ul><li>Centos 6</li><li>Debian 8</li><li>RHEL 6</li><li>Ubuntu 14.04 LTS</li><li>Ubuntu 16.04 LTS</li><li>ALT Education 8</li><li>ALT Workstation 8</li><li>ALT Workstation K 8</li><li>ALT Server 8.</li></ul></td><td>1C:Enterprise supported the following distribution packages for Linux operating system: <ul><li>Centos 6</li><li>Debian 8</li><li>RHEL 6</li><li>Ubuntu 14.04 LTS</li><li>Ubuntu 16.04 LTS</li><li>ALT Education 8</li><li>ALT Workstation 8</li><li>ALT Workstation K 8</li><li>ALT Server 8.</li></ul></td><td>Outdated Linux distribution packages are no longer supported.</td></tr><tr title="Версия 8.3.20" class="tag_29"><td><a name="b386d78f-51a3-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft Windows 11 operating system is supported.</td><td>Microsoft Windows 11 operating system was not supported.</td><td>Extended list of supported operating systems.</td></tr><tr title="Версия 8.3.20" class="tag_46"><td><a name="a159dbe3-0025-11ec-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br></td><td>New integration service feature: sending messages with a significant data amount (hundreds of megabytes).<p>The <span class="term">IntegrationServiceMessage.GetBodyAsStream()</span> method returns the stream for which position change is always unavailable. The reading and writing availability depends on the message for which the method is called.</p><p>The <span class="term">IntegrationServiceMessage.ExpirationDate</span> property is read only. The property value can be set only when creating a message. New parameter for the <span class="term">IntegrationServiceManager.CreateMessage</span> method: <span class="term">ExpirationDate</span>.</p><p>New property: <span class="term">IntegrationServiceMessage.BodySize</span>.</p></td><td>An attempt to send messages with a significant data amount could lead to various side effects and impossibility to use the integration service.<p>The stream that was returned by the <span class="term">IntegrationServiceMessage.GetBodyAsStream()</span> method was always available for writing and reading.</p><p>The <span class="term">IntegrationServiceMessage.ExpirationDate</span> property was writable.</p></td><td>
<p>Improved integration service stability when working with messages of significant size.</p></td></tr><tr title="Версия 8.3.20" class="tag_30 tag_31"><td><a name="4b2da778-51e9-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>If the user does not agree to receive data, the promise execution result obtained by using the <span class="term">GetDataAsynс() </span>method of the secure storage manager will be <span class="term">Undefined</span>.<p>
</p></td><td>The promise execution result obtained by using the <span class="term">GetDataAsync() </span>method of the secure storage manager did not reveal what happened during the method execution: a runtime error or the user did not agree to receive data.<p>
</p></td><td>Now it's possible to distinguish a runtime error and a situation when the user did not agree to receive data when using the <span class="term">GetDataAsync()</span> method of the secure storage manager.<p>
</p></td></tr><tr title="Версия 8.3.20" class="tag_29"><td><a name="7239926a-5bdc-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft Windows Server 2022 operating system is supported.</td><td>Microsoft Windows Server 2022 operating system was not supported.</td><td>Extended list of supported operating systems.</td></tr><tr title="Версия 8.3.20" class="tag_71"><td><a name="66072f3b-85c1-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 71); return false;">Analytics system</a>.<br></td><td>In the main menu of the administration console of the 1C: Analytics system, the ability to gain access to the description of the system programming interface has been implemented.<p>The ability to change the server settings of the 1C:Analytics system using the built-in language object<span class="term"> AnalyticsSystemServerConnection</span></p></td><td>The built-in language of the 1C:Enterprise system made it possible to read and write the parameters of the 1C:Analytics system server, but did not allow changing these parameters, because they were not documented.</td><td>Implemented the ability to change the server settings of the 1C: Analytics system using the built-in language object<span class="term"> AnalyticsSystemServerConnection</span></td></tr><tr title="Версия 8.3.20" class="tag_47"><td><a name="c7e0db21-a111-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>When using a standalone server, the server license is required in the following cases:<ul><li>When running the <span class="interface">ibcmd</span> utility in client/server mode.</li><li>When connecting to a standalone server in client/server mode over SSH.</li></ul><p>When a file infobase is used and the <span class="interface">ibcmd</span> utility performs operations with the infobase without connecting to a standalone server, the server license is not required.</p><p>
</p></td><td>When using a standalone server, the server license was required when running the <span class="interface">ibcmd </span>utility and the standalone server over SSH. The license was not required only when using a file infobase with less than 3 concurrent sessions.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.20" class="tag_30 tag_31"><td><a name="09507996-a11f-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New feature in the mobile application build service: build a developer platform.</td><td>This feature was not provided.</td><td>Advanced features of the mobile application build service.<p>
</p></td></tr><tr title="Версия 8.3.20" class="tag_8 tag_28"><td><a name="226a5634-b3ef-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Improved signature standard CAdES is now supported in the cryptography manager. CAdES defines the standard of a digital signature that remains valid for a long period of time.<p>New property for the <span class="term">CryptoManager</span> object: <span class="term">TimestampsServersAddresses</span>. New parameter for the <span class="term">Sign(), SignAsync(), </span>and <span class="term">BeginSigning(</span>) methods of the <span class="term">CryptoManager</span> object: <span class="term">CryptoSignatureType</span>. New parameter for the <span class="term">VerifySignature</span>(), <span class="term">VerifySignatureAsync(), </span>and <span class="term">BeginVerifyingSignature() </span>methods of the <span class="term">CryptoManager</span> object: <span class="term">CheckAdditionalAttributes</span>.</p><p>New methods for the <span class="term">CryptoManager</span> object: <span class="term">ImproveSignature(), ImproveSignatureAsync(), BeginImprovingSignature(), AddArchiveTimestamp(), AddArchiveTimestampAsync(), BeginAddingArchiveTimestamp().</span></p><p>New methods for the <span class="term">CryptoCertificateStore</span> object: <span class="term">RefreshCertificatesRevocationLists(), RefreshCertificatesRevocationListsAsync(), BeginRefreshingCertificatesRevocationLists(), CheckTimestamp(), CheckTimestampAsync(), </span><span class="term">BeginCheckingTimestamp(), GetCryptoSignaturesContainer(), GetCryptoSignaturesContainerAsync(), BeginGettingCryptoSignaturesContainer().</span></p><p>Improved digital signatures are not supported in the cryptography extension in Safari. Improved digital signatures might be unavailable in the latest versions of Internet Explorer on Windows 10. In this case, it is recommended that you use Mozilla Firefox, Google Chrome or previous versions of Internet Explorer instead.</p></td><td>This feature was not provided.</td><td>Advanced cryptography features in 1C:Enterprise.</td></tr><tr title="Версия 8.3.20" class="tag_28 tag_11"><td><a name="dbf0a700-c08d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>For web client on Linux, file system extensions, cryptography extensions, and add-in adapters now use GTK-3 library.</td><td>For web client on Linux, file system extensions, cryptography extensions, and add-in adapters required GTK-3 library.</td><td>To use add-ins, file system extensions, and cryptography extensions in web client on Linux, GTK-3 library must be available on the computer.</td></tr><tr title="Версия 8.3.20" class="tag_10"><td><a name="7cad04a3-cc8d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New <span class="interface">cacertnx.pem</span> file that is used in thin client, thick client, and server cluster to check certificate revocation. Root certificates of trusted certification authorities are added to the <span class="interface">cacert.pem</span> and <span class="interface">cacertnx.pem</span> files.<p>Now you can update the <span class="interface">cacertnx.pem </span>file when installing thin client or full distribution package (using an MSI file).
Certificate revocation check in 1C:Enterprise is performed as follows:</p><ul><li>In compatibility mode with <span class="interface">version 8.3.8</span> or later, the check is performed using the <span class="interface">cacertnx.pem </span>file and then using the current operating system.</li><li>In compatibility mode with <span class="interface">version 8.3.7</span> or earlier, the check is performed using the <span class="interface">cacert.pem </span>file only.</li></ul><p>
</p></td><td>These features were not provided.</td><td>Advanced features for certificate revocation check.</td></tr><tr title="Версия 8.3.20" class="tag_10"><td><a name="446f10ac-e180-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Hash algorithms implemented according to GOST are now supported upon USIA authentication.</td><td>Hash algorithms implemented according to GOST were not supported upon USIA authentication.<p>
</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.20" class="tag_32"><td><a name="4496ef68-11a0-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile 1C:Enterprise version 8.3.20 is now supported in the mobile application builder.</td><td>Mobile 1C:Enterprise version 8.3.20 was not supported in the mobile application builder.</td><td>Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.</td></tr><tr title="Версия 8.3.20" class="tag_32"><td><a name="f90ccce8-119f-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile 1C:Enterprise version 8.3.22 is now supported in the mobile application builder.</td><td>Mobile 1C:Enterprise version 8.3.22 was not supported in the mobile application builder.</td><td>Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.</td></tr><tr title="Версия 8.3.20" class="tag_56"><td><a name="ac6a968b-332f-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>If an error occurs during XML operations, the error message contains the error cause, which is specified in the library used by 1C:Enterprise for XML operations.</td><td>If an error occurred during XML operations, the error message did not contain the error cause specified in the library used by 1C:Enterprise for XML operations.</td><td>Eliminated unexpected system behavior.<p>Simplified troubleshooting of some issues that might occur during XML operations.</p></td></tr><tr title="Версия 8.3.20" class="tag_19 tag_6"><td><a name="c8cc8471-3a38-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>
<p>New feature: secure connection between the server cluster and PostgreSQL DBMS over SSL protocol.</p></td><td>This feature was not provided.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.20" class="tag_47 tag_27"><td><a name="e2853c78-3b2b-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>Loading a configuration from XML files in Designer and on the standalone server requires less RAM.<p>Loading a configuration from XML files in Designer and on the standalone server takes less time.</p></td><td>Designer and the standalone server used more RAM when loading a configuration from XML files.<p>Loading a configuration from XML files in Designer and on the standalone server took more time.</p><p>
</p></td><td>Reduced RAM consumption and better performance when loading a configuration from XML files in Designer and on the standalone server.</td></tr><tr title="Версия 8.3.20" class="tag_10"><td><a name="3f7780cb-7165-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The list of supported root certificates has been extended.</td><td>Fewer root certificates were supported.</td><td>Extended list of supported root certificates.</td></tr><tr title="Версия 8.3.20" class="tag_6"><td><a name="f711d1cd-b68a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Now 1C:Enterprise in client/server mode contains indexes for tables related to infobase users if you use IBM Db2, Oracle Database, or PostgreSQL.<p>Once the platform is updated, connect a user to the infobase to restore the indexes before the system starts connecting other users.</p><p>
</p></td><td>Previously, 1C:Enterprise in client/server mode did not contain indexes for tables related to infobase users if you used IBM Db2, Oracle Database, or PostgreSQL. So, it took more time to find a user by name and connect a large number of new users to the infobase.
</td><td>Eliminated unexpected system behavior.
</td></tr><tr title="Версия 8.3.20" class="tag_81"><td><a name="70a3a963-cf8a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>Now the web server extension consumes less RAM on Windows.</td><td>Previously the web server extension consumed more RAM on Windows.</td><td>Reduced RAM consumption by the web server extension on Windows.</td></tr></table><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="4ec18ace-6c4d-11eb-8371-0050569f678a">Transition from the previous version to the version 8.3.20</a></h2><ul><li title="Версия 8.3.20" class="tag_0"><a name="4ec18acf-6c4d-11eb-8371-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.20.
</li><li title="Версия 8.3.20" class="tag_0"><a name="4ec18ad0-6c4d-11eb-8371-0050569f678a"></a>Some features that are added in version 8.3.20 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.20" class="tag_0"><a name="508b4937-0020-11ec-8371-0050569f678a"></a>Until the first non-dynamic update of the database configuration, there will be no dynamic update of the database configuration.<p>To perform a dynamic update of the database configuration, it is recommended that you restructure the infobase after migration to a new version. You can perform this operation by testing and repairing the infobase with the <span class="interface">Restructure infobase tables</span> mode enabled, or by making changes in the configuration that lead to the infobase restructuring.</p></li><li title="Версия 8.3.20" class="tag_0"><a name="b9b59a6d-b68c-11ed-963f-0050569f678a"></a>In client/server mode with IBM Db2, Oracle Database, or PostgreSQL, connect a user to the infobase once the platform is updated. You need to do it before the system starts connecting other users to restore indexes for tables related to infobase users.</li></ul><p><a href="#4ec18ac3-6c4d-11eb-8371-0050569f678a"><small>Table of contents</small></a></p><h1><a name="cacd4ced-ca96-11ea-8371-0050569f678a">Version 8.3.19</a></h1><p title="Версия 8.3.19" class="tag_0"><a name="cacd4cfb-ca96-11ea-8371-0050569f678a"></a>Version 8.3.19 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#cacd4cee-ca96-11ea-8371-0050569f678a">New functionality and changes</a></li><li><a href="#cacd4cef-ca96-11ea-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#cacd4cf0-ca96-11ea-8371-0050569f678a">Optimization</a></li><li><a href="#cacd4cf1-ca96-11ea-8371-0050569f678a">Changes that affect system behavior</a></li><li><a href="#cacd4cf2-ca96-11ea-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#cacd4cf4-ca96-11ea-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#bf3e2557-385e-11eb-8371-0050569f678a">
</a></li><li><a href="#cacd4cf6-ca96-11ea-8371-0050569f678a">Demo configuration changes</a></li><li><a href="#cacd4cf7-ca96-11ea-8371-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#cacd4cf8-ca96-11ea-8371-0050569f678a">Transition from the previous version to the version 8.3.19</a></li></ul><h2><a name="cacd4cee-ca96-11ea-8371-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.19" class="compat tag_2 tag_1"><td><a name="f75035c0-ca96-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.18</span> is now implemented.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.17 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.18 or earlier can now run on version 8.3.19 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.19 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.18 after the migration to version 8.3.19, even if you disable the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.19" class="tag_33"><td><a name="31b5366f-cb20-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>New feature: objects available on a standalone mobile server can be selected for the Syntax Assistant.<p>New availability mode for the Syntax Assistant: <span class="interface">Standalone mobile server</span>. This availability mode describes objects and methods available on the 1C:Enterprise server running on a mobile device in standalone mode of the mobile client.
</p></td><td>In the Syntax Assistant, it was not possible to select objects available on a mobile device on the server side of the mobile client running in standalone mode.</td><td>New features of the 1C:Enterprise mobile version are considered in the Syntax Assistant.</td></tr><tr title="Версия 8.3.19" class="tag_66"><td><a name="15ef41bd-ccb1-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 66); return false;">Navigation links</a>.<br></td><td>Now you can specify additional parameters in URLs. The composition of parameters depends on the URL kind. Now you can do the following:<ul><li>Pass additional parameters for the form to open.</li><li>Get a URL to a report option.</li><li>Get a URL to full report settings.</li><li>Get a URL to a dynamic list with settings.</li><li>Get a URL to the current dynamic list row with settings.</li><li>Get a URL to a command and pass parameters to it.</li></ul><p>In the get URL dialog box (if necessary), you can choose which URL to get at a specific place in the client application interface.</p><p>New methods for the client application form extension for a report: <span class="term">GetReportURL()</span>, <span class="term">GetCurrentReportOptionURL()</span>, and <span class="term">GetCurrentReportSettingsURL()</span>.</p><p>New method for the client application form extension for a data processor: <span class="term">GetDataProcessorURL()</span>.</p><p>New methods for the client application form extension for a dynamic list: <span class="term">GetListURL()</span> and <span class="term">GetCurrentListSettingsURL()</span>. New client application form parameter for a dynamic list: <span class="term">TableDisplay</span>.</p><p>New method for the client application form extension for an object, a document, a catalog, a business process, a task, a chart of characteristic types, and an object of an external data source table: <span class="term">GetObjectURL()</span>.</p><p>New method for the client application form extension for an information register record and a record of an external data source table: <span class="term">GetRecordURL()</span>.</p><p>New feature: all the listed URL options can be received for the <span class="term">GetURL()</span> global context method. </p><p>New handlers for the client application form: <span class="term">GetURLsListProcessing</span> and <span class="term">GetURLProcessing</span>.</p><p>New configuration property: <span class="term">URLsExternalDataStorage</span>.</p><p>Changed format of the XML configuration export.
</p></td><td>These features were not provided.</td><td>Advanced navigation links features.</td></tr><tr title="Версия 8.3.19" class="tag_59"><td><a name="7f5ebe4d-d0a4-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>For form field extensions for an HTML document, a formatted document, a geographical schema, and the planner, implemented the <span class="term">BeforePrint </span>event that occurs before an object is printed interactively.<p>For form field extensions for an HTML document and a formatted document, implemented the <span class="term">BeforeWrite </span>event that occurs before an object is written interactively.</p><p>For form field extensions for an HTML document and a formatted document, implemented the <span class="term">AfterWrite </span>event that occurs after an object is saved interactively.</p><p>The <span class="interface">Save </span>command of the client application form called for a spreadsheet document does the following:</p><ul><li>If a file name is not specified or a spreadsheet document is not in edit mode, the dialog box to specify a name of a file to be saved is generated.</li><li>If a file name is specified and a spreadsheet document is in edit mode, saving is performed without displaying the dialog box to specify a file name.</li></ul><p>Once a spreadsheet document is saved, an operation completion notification appears.</p><p>For all form item kinds that support saving (except a spreadsheet document), the value that matches the executing action is passed to the <span class="term">Copy </span>parameter of the <span class="term">BeforeWrite </span>event handler:</p><ul><li><span class="term">True </span>if the <span class="interface">Save as</span> command is selected.</li><li><span class="term">False </span>if the <span class="interface">Save </span>command is selected. </li></ul><p>For a spreadsheet document or a report, the behavior is not changed when you select the <span class="interface">Save </span>command.
</p></td><td>For all form item kinds that supported saving, the system behavior was the same when the <span class="interface">Save </span>and <span class="interface">Save as </span>commands were specified: the dialog box to select a file to be saved was generated.<p>For all form item kinds that supported saving (except a spreadsheet document), the <span class="term">True </span>value was always passed to the <span class="term">Copy </span>parameter of the <span class="term">BeforeWrite </span>event handler. For a spreadsheet document, when the <span class="interface">Save </span>command was selected for a spreadsheet document or a report, the <span class="term">False </span>value was passed to the <span class="term">BeforeWrite </span>handler in the <span class="term">Copy </span>parameter.
</p></td><td>Implemented the <span class="term">BeforePrint</span>, <span class="term">BeforeWrite</span>, and <span class="term">AfterWrite </span>event handlers for all client application form items that support saving and printing.</td></tr><tr title="Версия 8.3.19" class="tag_14"><td><a name="4e9c8aed-d0ca-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Changed icons of all 1C:Enterprise executable files and icons associated with different file extensions related to 1C:Enterprise.</td><td>Icons of executable and generated files of 1C:Enterprise were different.</td><td>Icons follow the same style.</td></tr><tr title="Версия 8.3.19" class="tag_79"><td><a name="be42fbc5-d1a8-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>SMIL animation of SVG images is now supported. SMIL animation is not supported in Microsoft Internet Explorer and Microsoft Edge up to version 18 inclusive. In web browsers that do not support SMIL animation, a static picture will be displayed.<p>New feature: in a set of picture variants, you can specify a web browser the variant element is intended for. When a picture is output in a web browser, an attempt is made to define a variant for the used web browser first.</p><p>We recommend that you use SVG images with SMIL animation to create animated pictures in the application. Such pictures take up little space and do not require large resources for their display.</p></td><td>This feature was not provided.</td><td>Animated SVG images can now be displayed. Animation is displayed in both ordinary client applications and the web client (except Microsoft Internet Explorer and Microsoft Edge up to version 18).</td></tr><tr title="Версия 8.3.19" class="compat tag_43 tag_1"><td><a name="4bfd186e-d650-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The following features similar to the features provided in the data composition system are available for a dynamic list:<ul><li>Setting up query fields (a title, a type, appearance, a use restriction, and other).</li><li>Operations with calculated fields.</li><li>Using parameters in user settings.</li><li>Setting up parameter properties (a title, a type, and other).</li><li>In fields of the <span class="term">Date </span>type, you can now use parent fields (beginning of day, month, and other) in sorting and grouping.</li></ul><p>Changed the dynamic list settings editor.</p><p>New properties for a dynamic list: <span class="term">Fields</span>, <span class="term">FieldsToCalculate</span>, and <span class="term">DataParameters</span>. Changed the configuration XML dump format.</p><p>The following dynamic list methods are deprecated: <span class="term">SetRestrictionsForUseInGroup()</span>, <span class="term">SetRestrictionsForUseInFilter()</span>, <span class="term">SetRestrictionsForUseInOrder()</span>, <span class="term">GetRestrictionsForUseInGroup()</span>, <span class="term">GetRestrictionsForUseInFilter()</span>, and <span class="term">GetRestrictionsForUseInOrder()</span>. We recommend that you use the <span class="term">UseRestriction </span>dynamic list properties and the <span class="term">AttributesUseRestriction </span>dynamic list fields.</p><p>This change is not implemented in version 8.3.18 compatibility mode.
</p></td><td>These features were not provided.</td><td>Simplified setup of dynamic list fields. In particular, you can now specify localized presentations of query fields displayed in a dynamic list.</td></tr><tr title="Версия 8.3.19" class="tag_25 tag_43"><td><a name="05e022e3-d725-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>When you set up configuration object characteristics, you can now specify which configuration object field contains a characteristic name. Changing the characteristic presentation will not result in the loss of settings field of the data composition system or a dynamic list.<p>New property: <span class="term">CharacteristicsDetails.DataPathField</span>.</p><p>The value that returns the <span class="term">Presentation </span>virtual field is used as a characteristic presentation. A new field remains blank for existing characteristics.</p><p>If you change a field that contains a characteristic name in the characteristic description, we recommend that you provide a mechanism that converts data composition settings by replacing the old characteristic name with a new one.</p><p>Changed format of the XML configuration export.</p></td><td>The presentation of this characteristic was used as a characteristic name. Changing the characteristic presentation resulted in the loss of characteristics of data composition system settings and dynamic list settings.</td><td>Simplified creation of localized characteristic presentations in applications.</td></tr></table><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cacd4cef-ca96-11ea-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.19" class="tag_4"><td><a name="dca11535-d011-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The client application on Windows uses the Video Tools module that matches the operating system bitness for video calls.</td><td>The client application on Windows used the Video Tools module that matched the client application bitness for video calls.</td><td>On a video call, computer resources are used more efficiently.</td></tr><tr title="Версия 8.3.19" class="tag_14 tag_28"><td><a name="1aaa2ec4-d6f8-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Now the <span class="interface">Taxi </span>interface supports right-to-left languages (in thin and thick client applications). This mode is supported in the entire client application interface automatically.<p>The need to change the interface is determined by the interface language or the configuration language. Now client applications support Arabic numbers and dates.</p><p>When calculating placement of form items and other interface elements, Almarai font is used by default.</p><p>If a right-to-left language is set as the current configuration language in Designer, then the form preview in the form editor will also be performed in the relevant format.</p><p>Support of right-to-left languages has been implemented starting with version 8.3.7 compatibility mode.</p><p>The web client now supports right-to-left languages for the planner and charts.</p></td><td>Right-to-left languages were supported in the web client only.</td><td>1C:Enterprise is now available in right-to-left languages (using thin and thick client applications).</td></tr><tr title="Версия 8.3.19" class="tag_26 tag_64"><td><a name="e86eace6-0711-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>If the length of the text within a cell exceeds 3276 characters in a spreadsheet document being saved in the Microsoft Excel format (Microsoft Excel 97 or Microsoft Office OpenXML), saving is terminated and an error message appears.</td><td>When saving a spreadsheet document in the Microsoft Excel format (Microsoft Excel 97 or Microsoft Office OpenXML), the length of the text within a cell was not checked. This could result in a document that Microsoft Excel could not open.</td><td>Saving in the Microsoft Excel format is more correct now.</td></tr></table><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cacd4cf0-ca96-11ea-8371-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.19" class="tag_45"><td><a name="1880533e-cb56-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Improved query execution including when data access restrictions are used.<p>Improved performance of the <span class="term">StrContains()</span> function of the data access restriction expression.</p></td><td>Query execution (including queries that used data access restrictions) took more time.</td><td>Improved query performance.</td></tr><tr title="Версия 8.3.19" class="tag_6"><td><a name="f4280ce2-cb59-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>In a client/server infobase, loading from the .dt file is now faster as several background jobs are used for loading. To speed up significantly, we recommend that the server cluster and the DBMS are on the same computer or that the server cluster and the DBMS are interconnected with a high-bandwidth channel (1 GB/s or higher).<p>For the <span class="term">/RestoreIB</span> command of the Designer batch mode, implemented the <span class="term">JobsCount</span> parameter that allows you to manage the number of used background jobs.</p></td><td>In a client/server infobase, loading from the .dt file was performed sequentially.</td><td>Upgrade: information is restored from the .dt file faster in a client/server infobase.</td></tr><tr title="Версия 8.3.19" class="tag_36"><td><a name="87a75530-cb5c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>When solving systems of linear equations, reduced the time spent on obtaining a solution and the use of RAM.</td><td>Solving systems of linear equations took more time and required more RAM.</td><td>Improved solving systems of linear equations.</td></tr><tr title="Версия 8.3.19" class="tag_6"><td><a name="9236c77c-ccc5-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved generation of a session list.<p>New service: <span class="interface">Service for retrieving a list of server cluster sessions</span>.</p></td><td>Retrieving a session list took more time and could cause the system to hang on bulk retrieving the session list when load on the server cluster was heavy.</td><td>A possibility of system hanging on bulk retrieving a session list under heavy load is excluded. Reduced time of a single operation for retrieving a session list on a cluster with multiple servers. The time spent on simultaneous bulk retrieval of session lists is significantly reduced.</td></tr><tr title="Версия 8.3.19" class="tag_19"><td><a name="511dc419-d011-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>If you press the <span class="interface">Write </span>button several times in the object edit form (with the object unchanged), object tabular sections are not written to the DBMS upon each object record.</td><td>If you pressed the <span class="interface">Write </span>button several times in the object edit form, object tabular sections were written to the DBMS upon each object record.</td><td>Decreased DBMS load in some cases.</td></tr><tr title="Версия 8.3.19" class="tag_19 tag_45"><td><a name="d3fa8f10-d019-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In a file infobase, executing a query that receives data with ordering and filtering by the field for which the index is built is faster now even if the <span class="term">IN </span>operator that receives a large amount of data is used to impose a condition.
</td><td>In a file infobase, executing a query that received data with ordering and filtering by the field for which the index was built was not optimal if the <span class="term">IN </span>operator that received a large amount of data was used to impose a condition.</td><td>Improved file infobase performance.</td></tr><tr title="Версия 8.3.19" class="tag_82"><td><a name="6e584449-d0a7-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Optimized the query used by 1C:Enterprise to access virtual tables of balance and turnovers of the accounting register.</td><td>The query used by 1C:Enterprise to access virtual tables of balance and turnovers of the accounting register was not optimal.</td><td>Improved performance of queries to the virtual table of balance and turnovers of the accounting register.</td></tr><tr title="Версия 8.3.19" class="tag_64"><td><a name="134f7f82-d0a9-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Improved performance of the <span class="term">GetStringDeclension()</span> and <span class="term">GetStringDeclensionByNumber()</span> upon consecutive calls. For example, to get several case forms of the same phrase at once.</td><td>Several consecutive calls to the <span class="term">GetStringDeclension()</span> and <span class="term">GetStringDeclensionByNumber()</span> methods took more time.</td><td>Getting several case forms of the same phrase at once using the <span class="term">GetStringDeclension()</span> and <span class="term">GetStringDeclensionByNumber()</span> methods is faster now.</td></tr><tr title="Версия 8.3.19" class="tag_51"><td><a name="1f1b77b8-d17a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>Reduced the number of network calls when the <span class="term">FindObject()</span>, <span class="term">FindObjects()</span>, and <span class="term">GetObject()</span> methods of automated testing are running. This improves the overall automated testing performance.</td><td>When the <span class="term">FindObject()</span>, <span class="term">FindObjects()</span>, and <span class="term">GetObject()</span> methods of automated testing were running, a large number of network calls were made, which caused poor automated testing performance.</td><td>Improved automated testing performance, especially when the web client is used.</td></tr><tr title="Версия 8.3.19" class="tag_64"><td><a name="88b16963-f432-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Bulk retrieval of presentations of reference objects is now faster if only data passed to the handler is used to generate the presentation. This is reached by caching the presentations.<p>If data that is not passed to the presentation generation handler is used to get the presentation, when the presentation changes in the object, the presentation will change in the handler only in 20 seconds.</p></td><td>Bulk generation of presentations of reference objects took more time as values used to get the presentation were cached and the presentation itself was calculated every time the presentation was required.</td><td>Receiving presentations of reference objects and related operations are faster now. For example, ordering a value table by a reference column will speed up.</td></tr></table><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cacd4cf1-ca96-11ea-8371-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.19" class="tag_7 tag_45 tag_25"><td><a name="2339b0d0-ccc4-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Now you can control where a specific query or data composition will be executed: use only copies, only the main database, or mostly copies to execute a query, or select automatically. Thus, it became possible not to load the main database with a query that was created to be executed on a copy.<p>New properties for the <span class="term">Query </span>and <span class="term">DataCompositionOutputParametersValues </span>objects: <span class="term">DatabasesCopiesUse </span>and <span class="term">UsedDatabaseCopies</span>.</p></td><td>The platform automatically selected where the query would be executed. If it was not possible to execute a query on a copy, the main database was used to execute the query.</td><td>It is now possible not to execute queries or reports on the main database that can affect the database performance and that were intended to be executed on a copy only.</td></tr><tr title="Версия 8.3.19" class="tag_25"><td><a name="31b4b689-cff3-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Once the report is generated, the server part of the data composition system notifies the client application initiated the report generation of report generation completion using the Collaboration System. This mechanism works in conjunction with the existing mechanism for determining whether report generation is completed (periodic polling of the system background job).</td><td>To determine whether report generation was completed, periodic polling of the system backgroud job generating the report was used. Each failed completion check increases the time interval after which the next check will be done.</td><td>If there is the Collaboration System, a user will know right away when long report generation is completed.<p>If the Collaboration System is not connected to the infobase or is temporarily not functioning, the existing mechanism will be used.</p></td></tr><tr title="Версия 8.3.19" class="tag_43"><td><a name="5ee9688a-d001-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>For the header of the table column displaying a dynamic list with an order setting item that cannot be disabled by a user:<ul><li>In the web client: clicking the header changes the sorting order.</li><li>In thin and thick client applications: the column header always displays the sorting direction.</li></ul><p>As a result, the behavior of thin, thick, and web clients is the same when a user left-clicks the header of the dynamic list column whose ordering settings include an item that cannot be controlled by the user.</p></td><td>For the header of the table column displaying a dynamic list with an order setting item that could not be disabled by a user:<ul><li>In the web client: clicking the header did not change the sorting order.</li><li>In thin and thick client applications: the sorting direction was displayed in the column header only if there were user ordering settings for that column.</li></ul><p>The behavior of thin, thick, and web clients was not uniform when a user left-clicked the header of the dynamic list column whose settings included an item that could not be controlled by the user.</p></td><td>Unified behavior of thin, thick, and web clients when a user left-clicks the header of the dynamic list column whose ordering settings include an item that cannot be controlled by the user.</td></tr><tr title="Версия 8.3.19" class="compat tag_64 tag_1"><td><a name="49d5205e-d010-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>The behavior of the <span class="term">GetStringDeclensionsByNumber()</span> method changes when generating a number:<ul><li>For an ordinal:</li><ul><li>For a cardinal: an error of invalid parameter specification is generated.
</li><p>This change is not implemented in version 8.3.18 compatibility mode.</p></ul></ul></td><td>When generating a numeral with an ending using the <span class="term">GetStringDeclensionByNumber()</span> method, two-letter endings were always returned for ordinal and cardinal numbers.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.19" class="tag_7"><td><a name="34945eff-d014-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Now you can add objects included in separators to a database copy. On initial filling, the entire table is transferred. On change transfer, only the area that matches the separators of the current (transferred) transaction is transferred.<p>To create a database copy (using the <span class="term">DatabaseCopyManager.Write()</span> method) and update copy data (using the <span class="term">DatabaseCopyManager.Update()</span> method), the <span class="term">DataAdministration</span> access right is required.</p></td><td>It was possible to add only tables that were not part of separators or a table with conditionally disabled separators to a copy.</td><td>Now you can add separated application objects to a database copy.</td></tr><tr title="Версия 8.3.19" class="tag_14"><td><a name="9dc048c2-d0ab-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Now each infobase user can manage OpenIDConnect authentication. New property: <span class="term">InfobaseUser.OpenIDConnectAuthentication</span>.<p>Now you can end an authentication session according to the OpenID Connect standard. New property in OpenID Connect provider description–<span class="term">default.vrd</span> file, <span class="term">&lt;providers&gt;</span> item: endSessionEndpoint.</p></td><td>This feature was not provided.</td><td>Improved OpenID Connect support.</td></tr><tr title="Версия 8.3.19" class="tag_74"><td><a name="c218ee2e-d0c7-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br></td><td>Expanded the set of information displayed by the licensing utility (the <span class="interface">ring license info</span> command):<ul><li>Added information about the license type and the license binding type in the section with license information.</li><li>New section with machine-readable information: <span class="interface">TechnicalInfo</span>. Data in this section is always displayed in English.</li></ul></td><td>The output of the <span class="interface">ring license info</span> command did not contain information about the license type and the license binding type, and did not contain a section with machine-readable information about the license.</td><td>Expanded the set of activated license information that can be obtained. Simplified obtaining information about licenses using various automation tools.</td></tr><tr title="Версия 8.3.19" class="compat tag_63 tag_25 tag_1"><td><a name="d1305cb7-d0d9-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Upgrade: a chart in a data composition system report better adjusts to the width of the screen showing the report.<p>This change is not implemented in version 8.3.18 compatibility mode.</p></td><td>A chart in a data composition system report did not adjust well to the width of the screen showing the report.</td><td>Improved appearance of charts on low-resolution screens.</td></tr><tr title="Версия 8.3.19" class="compat tag_45 tag_1"><td><a name="9cc628dd-f42d-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If a query that generates a temporary table based on a value table retrieves a field separated by dot from another expression, a query language error is generated on executing such a query.<p>We recommend that you analyze texts of queries to generate temporary tables to eliminate the modifiable behavior.</p><p>This change is not implemented in 8.3.18 compatibility mode.</p></td><td>If a query that generated a temporary table based on a value table retrieved a field separated by dot from another expression, a runtime error was generated when executing this query in client/server mode and an incorrect value was placed in the temporary table value when executing this query in file mode.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.19" class="tag_26"><td><a name="833cb2fd-f42e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>This feature is canceled.<p>When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the Picture objects now behave as follows:</p><ul><li>If the <span class="term">PictureSize</span> property value is not <span class="term">Tile</span>, an original picture is saved to the resulting document. If a pattern is specified for a cell, the pattern picture is also saved.</li><li>If the <span class="term">PictureSize</span> property is set to <span class="term">Tile</span>, a picture is redrawn into the resulting document and the background color of a Microsoft Excel document picture becomes the same as the one of the source document picture.</li></ul><p>As a result of these changes, pictures in a spreadsheet document become less distorted when scaling a Microsoft Excel document.</p></td><td>When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the <span class="term">Picture</span> objects behaved as follows:<ul><li>When the <span class="term">PictureSize</span> property value was not <span class="term">Stretch</span>, a picture was redrawn into the resulting document.</li><li>When the <span class="term">PictureSize</span> property value was set to <span class="term">Stretch</span>, a picture was redrawn to the resulting document if a background color or pattern was not set. Otherwise, an original picture was saved.</li></ul></td><td>The result of saving a spreadsheet document in Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats meets expectations of users to a greater extent.</td></tr><tr title="Версия 8.3.19" class="compat tag_25 tag_104 tag_1"><td><a name="5735ba2a-f434-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>When calculating the availability of child fields used in data composition expressions, a check whether the field is not disabled using a functional option is performed for both the field itself and all parent fields of this field.<p>This change is not implemented in version 8.3.18 compatibility mode.</p></td><td>When calculating the availability of child fields used in data composition expressions, a check whether the field was not disabled using a functional option was performed only for the field itself. Parent fields were not checked.</td><td>Upgrade: the availability of fields associated with functional options is checked in the same way in both the query language and the data composition system.</td></tr><tr title="Версия 8.3.19" class="tag_105"><td><a name="9ea70e7c-32f6-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>For the <span class="term">RecordChanges()</span> and <span class="term">DeleteChangeRecords()</span> methods, it is now possible to register and unregister changes for an arbitrary set of data objects that are passed as an array in the <span class="term">Data </span>parameter of these methods.<p>The action for all objects in the passed array will be performed within a single transaction with the minimum number of queries used.</p></td><td>For the <span class="term">RecordChanges()</span> and <span class="term">DeleteChangeRecords()</span> methods, it was not possible to specify an array of objects to perform an action.</td><td>Executing the <span class="term">RecordChanges()</span> and <span class="term">DeleteChangeRecords()</span> methods is now faster when these methods must be applied to a large number of data objects.</td></tr></table><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cacd4cf2-ca96-11ea-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.19" class="tag_14 tag_70 tag_10"><td><a name="d6020d2f-cb5b-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can update a client application using the web server when Microsoft Internet Information Services configured by default is used as a web server. Implemented support of the MIME type <span class="interface">application/x-zip-compressed</span> used by the web server for .zip files by default.
</td><td>To update a client application using the web server when Microsoft Internet Information Services was used as a web server, you had to manually override the MIME type that the web server used to pass .zip files.</td><td>Administration of the Microsoft Internet Information Services web server is more convenient when a client application update is configured via the web server.</td></tr><tr title="Версия 8.3.19" class="tag_10"><td><a name="62be01d5-cce6-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When exclusive mode is set, you can now specify a human-understandable description of the reason why exclusive mode is set (what the session is doing) and terminate the session that set the exclusive access.<p>New parameter for the <span class="term">SetExclusiveMode()</span> method: <span class="term">Parameters</span>. New global context method: <span class="term">GetExclusiveModeParameters()</span>. New access right: <span class="term">ExclusiveModeCompletionOnStartSession</span>.</p><p>The message text about the reason for the inability to start a new session can be a formatted string or an HTML string generated from a formatted string.</p></td><td>When attempting to log into the infobase where exclusive mode was set, it was impossible to terminate such a session (even if it was possible to terminate the session according to the logic of the actions being performed) and it was not clear what was being done at that moment.</td><td>When exclusive mode is set, you can now specify a user-understandable text that explains why exclusive mode is set. A user can terminate the session that set exclusive access if the user rights and the logic of the actions performed allow such termination.</td></tr><tr title="Версия 8.3.19" class="compat tag_95 tag_1"><td><a name="783df70a-cdba-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>Calling the <span class="term">PredefinedValue()</span> method when a non-existent enumeration value is specified as a parameter value generates an exception. <p>This change is not implemented in version 8.3.18 compatibility mode.</p></td><td>Calling the <span class="term">PredefinedValue()</span> method when a non-existent enumeration value was specified as a parameter value returned an empty value.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.19" class="tag_10"><td><a name="1446dc49-d0dd-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The name of the distribution package of 1C:Enterprise server cluster for x86-64 architecture looks as follows: 1C:Enterprise 8 (x86-64) Server.
</td><td>The name of the distribution package of 1C:Enterprise server cluster for x86-64 architecture looked as follows: 1C:Enterprise 8 (x86-64).</td><td>Now software names follow a single style for all software distribution packages for Windows.</td></tr><tr title="Версия 8.3.19" class="compat tag_26 tag_25 tag_1"><td><a name="59837e33-d181-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Now you can scale a picture so that the picture height matches the size of the font used in the item that displays the picture.<p>New system enumeration property: <span class="term">PictureSize.ByFontSize</span>.</p><p>If a picture in a report cell is specified using the <span class="term">Picture </span>conditional appearance parameter of the data composition system, the <span class="term">PictureSize </span>parameter value equals the <span class="term">ByFontSize </span>value (if the <span class="term">PictureSize </span>parameter is not specified in conditional appearance). This change is not implemented in version 8.3.18 compatibility mode.</p><p>We recommend that you use the <span class="term">ByFontSize </span>picture display mode in a spreadsheet document when a picture in a cell is a marker. When using this picture display mode, the picture height does not affect the automatically calculated height of the spreadsheet document row and does not depend on the number of text rows displayed in the cell.</p></td><td>If a picture in a report cell was specified using the <span class="term">Picture </span>conditional appearance parameter of the data composition system, the default value was not set for the <span class="term">PictureSize </span>parameter and this parameter was not used (except if this parameter was specified explicitly).</td><td>Improved display of pictures in a spreadsheet document in cases where it is necessary to use a picture in the text so that the picture size automatically adjusts to the height of the font used.</td></tr><tr title="Версия 8.3.19" class="tag_6 tag_10"><td><a name="06e7b2db-d269-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can use partial Kerberos delegation for OS authentication if the server cluster is running Windows, the web server and the client application are each on their own computer, and this computer is different from the computer where the server cluster is running.<p>For server cluster administration tools, a service principal name (SPN) can now be specified:</p><ul><li>In the cluster administration console, the working server properties, implemented the property <span class="interface">1C:Enterprise server principal name (SPN)</span>.</li><li>The <span class="term">AdministrationWorkServer.ServerServiceName </span>object property.</li><li>The <span class="term">IWorkingServerInfo.ServicePrincipalName </span>object property for administration tools using COM connection.</li><li>The <span class="term">getServicePrincipalName()</span> and <span class="term">setServicePrincipalName()</span> methods of the <span class="term">IWorkingServerInfo </span>interface for Java-based administration tools.</li><li>The <span class="term">service-principal-name</span> parameter for the <span class="term">rac server insert </span>and <span class="term">rac server update</span> commands.</li></ul></td><td>This feature was not provided.<p>OS authentication could only be performed with full Kerberos delegation if the server cluster was running Windows, the web server and the client application were each on their own computer, and that computer was different from the computer where the server cluster was running.</p></td><td>Now you can use OS authentication when accessed via the web server, without lowering the overall system security.</td></tr><tr title="Версия 8.3.19" class="tag_64"><td><a name="3e46cfd3-d64e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Now you can automatically switch a report to compact mode (if necessary), regardless of how the report is generated: using the platform or the 1C:Enterprise language.<p>New property of the client application form extension for a report: <span class="term">ViewModeUseOnSetResult</span>. The property works together with the <span class="term">ResultViewMode </span>property of the client application form extension for a report.</p><p>Changed format of the XML configuration export.</p></td><td>If a report was generated using the 1C:Enterprise language, it was required to switch the report to compact mode (if necessary) manually.</td><td>For a developer, simplified report display on a form if the report is generated using the 1C:Enterprise language and it is necessary to consider that the report can be displayed on mobile devices.</td></tr><tr title="Версия 8.3.19" class="tag_6"><td><a name="76db076a-f433-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The value of the <span class="interface">Temporarily allowed amount of process memory</span> property of the working cluster server is used to restart working processes from memory and manage large call termination. You can use this property with a PROF license.</td><td>When working with PROF licenses, a value equal to 80% of the RAM of the computer where the server was running was used to restart cluster working processes and terminate large server calls. It was not allowed to change the <span class="interface">Temporarily allowed amount of process memory </span>property of the working cluster server with PROF licenses.</td><td>Administration of systems with PROF licenses is more convenient.</td></tr><tr title="Версия 8.3.19" class="tag_26"><td><a name="b58679da-12a8-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Now you set the report display mode for reports using the 1C:Enterprise language.<p>New methods for the client application form extension for a report form: <span class="term">GetResultViewMode()</span>, <span class="term">GetCurrentResultViewMode()</span>, and <span class="term">SetResultViewMode()</span>.</p><p>Changed the approach to storing information about the result display mode in the system settings storage. Information about the report display mode is stored in the system report storage when the display mode value to be set differs from the value specified in the configuration. In this case, the <span class="term">Auto </span>value interpretation is ignored for various client types.</p><p>The <span class="term">ResultViewMode </span>property of the client application form extension for a report form is deprecated.</p></td><td>It was not possible to change the report result view mode using the 1C:Enterprise language.<p>The value that the current client application took into account was stored in the system storage (the <span class="term">Auto </span>value interpretation was not ignored).</p></td><td>Now you can manage report display using the 1C:Enterprise language.</td></tr></table><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cacd4cf4-ca96-11ea-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.19" class="tag_31 tag_51"><td><a name="2bdca401-0ec0-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>Now you can use the mobile client as a test client. The mobile client in standalone mode can be a test client only during connection with the main server.<p>Now you can record user actions on a mobile device and playback a test written earlier in the 1C:Enterprise language.</p><p>New commands for the command-line to start the mobile client: <span class="term">/UILOGRECORDER</span> and <span class="term">/TESTCLIENT</span>.</p><p>The developer mobile client is always started with the option to record user actions (with the <span class="term">/UILOGRECORDER</span> command).</p><p>If the mobile client is started with the <span class="term">/UILOGRECORDER</span> command, the <span class="interface">Record user actions</span> item appears in the <span class="interface">Mobile client tools</span> menu.
</p></td><td>This feature was not provided.</td><td>Now you can use the mobile client for automated testing of applications.</td></tr><tr title="Версия 8.3.19" class="tag_53"><td><a name="2c81d95b-12b0-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>New values for the <span class="term">ErrorsCategories </span>system enumeration:<ul><li><span class="term">NoPermissionToUseFunctionality </span>that describes errors that occur because the mobile application does not have permissions to use some features correctly.</li><li><span class="term">MultimediaToolsError </span>that describes errors that occur while using a mobile device camera or microphone.</li></ul></td><td>These error categories were missing in the <span class="term">ErrorsCategories </span>system enumeration.
</td><td>Improved mobile application error categorization.</td></tr><tr title="Версия 8.3.19" class="tag_48"><td><a name="6dfc7a52-12da-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Now you can manage audio recording in the background. If this functionality is enabled, audio recording will continue when the application is minimized and the device screen is turned off.<p>New system enumeration value: <span class="term">MobileApplicationFunctionality.AudioRecordingInBackground</span>.</p></td><td>Background audio recording was not available. Audio information could be recorded only if the application was active.</td><td>Improved audio information operations in the mobile application.</td></tr><tr title="Версия 8.3.19" class="tag_31"><td><a name="a7f8a384-406d-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Upgraged the video call interface in the mobile client.<p>In the mobile client, you can now view the screen of another device and share your own screen. The viewing screen cannot control the mobile device whose screen is being shared.</p></td><td>The video call interface in the mobile client was different.<p>The mobile client did not support screen viewing and sharing.</p></td><td>Improved interaction system video calls in the mobile client.</td></tr></table><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="bf3e2557-385e-11eb-8371-0050569f678a">
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.19" class="tag_101"><td><a name="1a0fad6c-385f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>In a graph, the x-axis will show the time dimension by default.</td><td>The x-axis now showed the first added dimension.</td><td>The expected result is obtained more often without additional actions.</td></tr><tr title="Версия 8.3.19" class="tag_100"><td><a name="e5d8e4c0-385f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>The left dashboard panel shows folders, just like the desktop.</td><td>The left dashboard panel showed all charts, excluding folders.</td><td>It is now easier to navigate through charts on the dashboard.</td></tr><tr title="Версия 8.3.19" class="tag_100"><td><a name="ff76f129-385f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>Decreased spacing between dashboard items.</td><td>Spacing between the dashboard items was larger.</td><td>The dashboard now contains more information.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="0dbf4329-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>In table mode, you can now customize how totals will be placed: at the beginning or at the end of dimension values.</td><td>In table mode, totals were always displayed at the beginning of a dimension.</td><td>Improved appearance settings for table totals.</td></tr><tr title="Версия 8.3.19" class="tag_106"><td><a name="1df6b599-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 106); return false;">Analytics - expression language</a>.<br></td><td>Implemented the <span class="term">FORMAT()</span> function to format values in a chart.</td><td>The value was displayed in the default format.</td><td>You can now customize the required option to display values.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="2cb3ab8c-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>When the chart type is switched, the chart retains roles of fields that are close in meaning.</td><td>When the chart type was switched, field roles were set to default values.</td><td>Switching the chart type requires fewer steps to achieve the desired chart appearance.</td></tr><tr title="Версия 8.3.19" class="tag_72"><td><a name="3ed7dd09-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 72); return false;">Analytics - sources</a>.<br></td><td>When creating additional sources based on virtual tables, it is now possible to transfer parameters from report settings to a query.</td><td>It was not possible to define virtual table parameters in additional sources.</td><td>Additional sources based on virtual tables are now more efficient.</td></tr><tr title="Версия 8.3.19" class="tag_106"><td><a name="509f3871-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 106); return false;">Analytics - expression language</a>.<br></td><td>Implemented the <span class="term">PREVDATE() </span>and <span class="term">VALUEFOR()</span> functions to build comparative graphs for different time slices or other dimensions. <p>Using these functions will allow you to compare similar indicators obtained for different periods of time or other analytical dimensions in the table.</p></td><td>For output to the table, it was not possible to use similar indicators obtained for different periods of time or other analytical dimensions.</td><td>You can now obtain the same indicators for different periods of time to build better charts.</td></tr><tr title="Версия 8.3.19" class="tag_106"><td><a name="a159ffef-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 106); return false;">Analytics - expression language</a>.<br></td><td>Implemented the <span class="term">TOP()</span> function that allows you to limit the number of values displayed in a report and combine the remaining values into a single total value. The setting is available from the dimension context menu.</td><td>This feature was not provided.</td><td>You can now build more descriptive charts.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="b32ae0e3-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>The chart editor now supports search for available fields in nested source structures (in nested references to catalog items and documents).</td><td>The search only worked for the top level of the hierarchy.</td><td>It is now easier to search for fields to be analyzed.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="c47d9858-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>The hierarchy can now be expanded by date similar to the directory hierarchy using the field hierarchy menu in a chart.
</td><td>Periods in charts had to be refined manually.</td><td>It it now easier to manage dates in charts.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="d562d003-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>You can now customize the legend location in the chart.
</td><td>The position of the legend was fixed.</td><td>The chart appearance settings are now more flexible.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="eef032b7-3860-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>Implemented tooltips and notes in the filter by date editor for universal formulas ("Current year", "Last year", and other).</td><td>This feature was not provided.</td><td>Help information is now available in the filter by date editor.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="02c0ddd0-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>The chart background now considers the currently enabled application theme.</td><td>The chart background was light regardless of the theme.</td><td>The chart background now matches the theme used.
</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="143e6e3b-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>A tooltip can now be displayed for a field value if it does not fit within one cell in the table.</td><td>This feature was not provided.<p>Field values were clipped to cell borders.
</p></td><td>You can now see the full value in a table cell for any length of the text presentation of the value.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="2260aa0b-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>The full date value can now be displayed in a chart using the context menu.</td><td>The full date could only be displayed by editing the formula.</td><td>It is now easier to manage dates.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="33f1458e-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>You can now smoothly adjust the size of the panel with data source fields.</td><td>The panel size was not customizable.</td><td>You can now use screen space more efficiently.</td></tr><tr title="Версия 8.3.19" class="tag_100"><td><a name="503a7ff4-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>When switching from the dashboard to the chart level, common dashboard filters can now be displayed and quickly enabled/disabled.</td><td>There were no common filters on the dashboard.</td><td>The user can quickly assess the filter impact on the dashboard data.</td></tr><tr title="Версия 8.3.19" class="tag_103"><td><a name="5fcdb2b5-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 103); return false;">Analytics - other</a>.<br></td><td>Implemented the command to open the web client of 1C:Enterprise infobase with which 1C:Analytics works.</td><td>It was not possible to quickly call the web client for the used 1C:Enterprise infobase.</td><td>It is now easier to use the infobase.</td></tr><tr title="Версия 8.3.19" class="tag_102"><td><a name="74f2c41b-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 102); return false;">Analytics - desktop</a>.<br></td><td>You can now batch copy/move objects on the desktop.
</td><td>Objects on the desktop could only be copied and moved one at a time.</td><td>The desktop is now more user-friendly.</td></tr><tr title="Версия 8.3.19" class="tag_102"><td><a name="87253dea-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 102); return false;">Analytics - desktop</a>.<br></td><td>The path to objects can now be displayed upon desktop search.</td><td>Upon search, it was not clear where the object came from.</td><td>Desktop search is now more informative.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="978c4c16-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>Chart data is stored in the cache of 1C:Analytics for 24 hours.</td><td>Chart data was stored in the cache of 1C:Analytics until the web browser tab was reloaded.</td><td>The result is now more predictable.</td></tr><tr title="Версия 8.3.19" class="tag_100"><td><a name="a56e4275-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>You can now copy dashboard widgets.</td><td>Dashboard widgets could not be copied. It was only possible to create a new widget that had to be configured manually.</td><td>Simplified dashboard setup.
</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="b567d0d7-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>You can now set the display range of values on graph axes.</td><td>The display range of values on graph axes was adjusted automatically based on the displayed data.</td><td>Chart appearance customization is upgraded.</td></tr><tr title="Версия 8.3.19" class="tag_72"><td><a name="ca692d70-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 72); return false;">Analytics - sources</a>.<br></td><td>When using virtual tables of balance and turnovers, balance by periods when there were no turnovers for dimension values can now be supplemented. The balance in the supplemented periods is equal to the balance of the last actual period preceding the supplemented period.</td><td>When using virtual tables of balance and turnovers, balance by periods were not displayed (there could be gaps in the data) if there were no turnovers for dimension values during these periods.</td><td>Data display is correct.</td></tr><tr title="Версия 8.3.19" class="tag_106"><td><a name="ddd83fae-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 106); return false;">Analytics - expression language</a>.<br></td><td>New date functions: <span class="term">DATEDIFF()</span>, <span class="term">BEGINOFPERIOD()</span>, and <span class="term">ENDOFPERIOD()</span>.</td><td>This feature was not provided.</td><td>Extended the list of date functions.</td></tr><tr title="Версия 8.3.19" class="tag_100"><td><a name="ead34f8a-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 100); return false;">Analytics - dashboards</a>.<br></td><td>Implemented filter templates for Boolean and Date fields on the dashboard.</td><td>Filters of the specified types could only be set by a formula.</td><td>Simplified filter creation.</td></tr><tr title="Версия 8.3.19" class="tag_72"><td><a name="facf3f4f-3861-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 72); return false;">Analytics - sources</a>.<br></td><td>Improved appearance of the dialog box that is displayed when updating sources of 1C:Analytics. The dialog box now displays more detailed information and does not block the system.</td><td>The dialog box that was displayed when updating sources of 1C:Analytics showed less information and blocked the system.</td><td>Improved appearance and behavior of 1C:Analytics when updating sources.</td></tr><tr title="Версия 8.3.19" class="tag_106"><td><a name="0c40e8cb-3862-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 106); return false;">Analytics - expression language</a>.<br></td><td>Implemented the <span class="term">ADD()</span> function to change date and time values.</td><td>This feature was not provided.</td><td>Extended the list of date functions.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="1b408592-3862-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>Pressing <span class="interface">ESC </span>closes the field edit window only if the window field values are not changed.</td><td>Pressing <span class="interface">ESC </span>closed the field edit window regardless of whether the data in the window fields was changed or not, which could lead to data loss.</td><td>The system is now more predictable and user-friendly.</td></tr><tr title="Версия 8.3.19" class="tag_106"><td><a name="2d39de19-3862-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 106); return false;">Analytics - expression language</a>.<br></td><td>Improved context hint when editing expression code.</td><td>The context hint did not work well when editing expression code.</td><td>The expression editor is now more user-friendly.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="3cf0c5a7-3862-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>Improved chart labels.</td><td>When there were a lot of labels, they covered each other and the chart looked bad.</td><td>Improved appearance of charts.</td></tr><tr title="Версия 8.3.19" class="tag_101"><td><a name="4d82acc9-3862-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 101); return false;">Analytics - charts</a>.<br></td><td>Improved grouping performance.</td><td>Grouping performance was non-optimal.</td><td>Improved data retrieval.</td></tr></table><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cacd4cf6-ca96-11ea-8371-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.19" class="tag_0"><a name="a6526e31-388d-11eb-8371-0050569f678a"></a>Implemented configurations to demonstrate the following features:<ul><li>An infobase serving as a service for registering errors that occur during application operation.</li><li>You can now contact application technical support using the Collaboration System.</li></ul><p>You can find the demo configurations on the ITS disk <a href="https://its.1c.ru/db/metod8dev#content:5981:hdoc" target="_blank">Read more</a>..</p></li><li title="Версия 8.3.19" class="tag_0"><a name="9f5bce5f-5408-11eb-8371-0050569f678a"></a>The <span class="interface">Order </span>document form now has an option to get a URL with the current row of the <span class="interface">Goods </span>tabular section.</li><li title="Версия 8.3.19" class="tag_0"><a name="370ded4d-5409-11eb-8371-0050569f678a"></a>Additional information (about the counterparty debt) can now be displayed in global search results (see the global search help).</li><li title="Версия 8.3.19" class="tag_0"><a name="77c80240-5409-11eb-8371-0050569f678a"></a>For additional characteristics of configuration objects, the <span class="interface">Data path field</span> field is specified.<p>
</p></li><li title="Версия 8.3.19" class="tag_0"><a name="e76bdcea-9219-11eb-8371-0050569f678a"></a>The counterparty form now includes the <span class="interface">Create voice note</span> command, which demonstrates recording an audio file using the asynchronous method and recording this file. Information about this feature is included in the guide.<p>The list of used mobile application features now includes the following:</p><ul><li><span class="interface">Geolocation in the background.</span></li><li><span class="interface">Audio playback and vibration in the background.</span></li><li><span class="interface">Audio recording in the background.</span></li></ul></li></ul><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cacd4cf7-ca96-11ea-8371-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.19" class="tag_27"><td><a name="eab58525-5410-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of configuration dump to XML files is now 2.12.</td><td>The format version of configuration dump to XML files was 2.11.</td><td>The configuration dump to XML files now supports new platform features.</td></tr><tr title="Версия 8.3.19" class="tag_64"><td><a name="9c69bbc7-6136-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New picture was added to the picture library: <span class="term">StartVideoConference</span></td><td>The listed picture was not available in the picture library.</td><td>The picture library is upgraded.</td></tr><tr title="Версия 8.3.19" class="tag_21"><td><a name="12308736-6155-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Full-text search is now faster when the search is started from 1C:Enterprise language (including global search mechanisms) and filter by metadata is set (the <span class="term">FullTextSearchList.DataArea</span> property).<p>It will be faster if the full-text search index is built in version 8.3.7 and later compatibility mode.</p></td><td>When filter by metadata was set, full-text search was slow.</td><td>When filter by metadata is set, full-text search is faster.</td></tr><tr title="Версия 8.3.19" class="compat tag_25 tag_1"><td><a name="7794775a-6c4f-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When conditional appearance is used in the Data Composition System, a conditional appearance element with the <span class="interface">In overall usage </span>area set is used to style templates of the overall resources horizontally and vertically in the table.<p>This change is not implemented in 8.3.18 compatibility mode.</p></td><td>A conditional appearance element with the <span class="interface">In overall usage </span>area set was not used to conditionally style templates of the overall resources horizontally and vertically in the table.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.19" class="tag_79 tag_30 tag_31"><td><a name="d6ebc945-6c61-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The <span class="term">PictureToProcess </span>object is now available in 1C:Enterprise mobile version. The following object methods are not implemented: <span class="term">SelectKeyArea()</span>, <span class="term">SetColorDepth()</span>, and <span class="term">SetDensity()</span>. The features of other object properties and methods in this case can be found in Syntax Assistant.<p>For the <span class="term">Picture </span>object, the <span class="term">Width()</span>, <span class="term">Height()</span>, and <span class="term">FileSize()</span> methods are now available in the mobile version. The <span class="term">ColorDepth()</span>, <span class="term">GrayScale()</span>, <span class="term">HorizontalDensity()</span>, and <span class="term">VerticalDensity()</span> methods always return <span class="term">Undefined </span>in the mobile version.</p></td><td>In 1C:Enterprise mobile version, the <span class="term">PictureToProcess </span>object and all methods of the <span class="term">Picture </span>object were unavailable.</td><td>You can now implement some custom scenarios on mobile devices. For example, display thumbnails on the form (for more efficient use of mobile device resources).</td></tr><tr title="Версия 8.3.19" class="tag_4"><td><a name="a78014cf-7a8b-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can now exchange a video stream only with the server upon group video calls. To do this, a special server application must be configured on the interaction server.</td><td>Group video calls were made in p2p mode. That is, the client application exchanged video streams with computers of all video call participants.</td><td>The load on the client computer upon a group video call and a large number of video call participants can now be reduced. Improved Collaboration System performance if a user has an asymmetric communication channel.</td></tr><tr title="Версия 8.3.19" class="tag_32 tag_30 tag_31"><td><a name="2202d8a3-91fa-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The distribution package of 1C:Enterprise mobile version contains requirements for the versions of the utilities used to build a mobile application.</td><td>The requirements for the utilities used to build a mobile application were not included in the mobile version distribution package. It was impossible for users to understand which utility versions to install to build a mobile application.</td><td>It is now possible to understand which versions of the utilities used to build a mobile application to install on the builder computer. If the versions do not match, troubleshooting is more understandable.</td></tr><tr title="Версия 8.3.19" class="tag_74 tag_71"><td><a name="2f2edfca-93b2-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br><a href="#" onclick="onTagClick(this, 71); return false;">Analytics system</a>.<br></td><td>You can now start a single 1C:Analytics client without a 1C:Analytics client license if no more than 5 client application sessions are connected to the infobase.</td><td>Starting 1C:Analytics client without its own license was not available.</td><td>The application developer can use 1C:Analytics for development purposes without the need to obtain a 1C:Analytics client license.</td></tr><tr title="Версия 8.3.19" class="tag_78"><td><a name="9e6d96e5-93b6-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>Updated distribution package of <a href="https://v8.1c.ru/static/1s-predpriyatie-rabota-s-faylami/" target="_blank">Read more</a>. file manager. The distribution package comes with an interface in all languages supported by 1C:Enterprise.</td><td>The distribution package of the file manager was available in two versions: only in Russian and in all languages supported by 1C:Enterprise.</td><td>Simplified file manager operations. Users no longer need to choose which distribution package they need.</td></tr><tr title="Версия 8.3.19" class="tag_46"><td><a name="ba67abef-93ba-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br></td><td>You can now specify that receiving an integration service message will be processed outside a transaction.<p>New property of the <span class="term">IntegrationServiceChannel </span>configuration object: <span class="term">InTransaction</span>.</p></td><td>Receiving an integration service message was always processed within a transaction.</td><td>You can now implement more flexible algorithms for integration service channels.</td></tr><tr title="Версия 8.3.19" class="tag_4"><td><a name="e9bc9815-9604-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Optimized screen sharing module for thin, thick, and web clients. The new screen sharing module requires the Collaboration System server version 10 or later. To use the new screen sharing module in the web client, Google Chrome version 64 or later is required (in addition to the Collaboration System server version).<p>The optimized version of the screen sharing module allows you to select a monitor to share (if there are multiple monitors), is faster, and loads the CPU of the computer used for sharing less.</p><p>The previous screen sharing module is used if the subscriber cannot use the new module version in the video call.</p></td><td>The previous screen sharing module did not allow you to select a monitor to share, had lower performance, and loaded the CPU of the computer used for sharing more heavily.</td><td>Improved computer screen sharing when using Collaboration System.</td></tr><tr title="Версия 8.3.19" class="tag_7"><td><a name="21b8ce3f-9dd1-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Optimized execution of queries in a database copy when a large number of transactions are performed in the main database and data is transferred to the copy not very often.<p>To enable optimization, restructure the infobase (by updating the configuration or on testing and patching).</p></td><td>Queries executed in a database copy were not optimized.</td><td>Improved performance of queries that can be executed on a database copy.</td></tr><tr title="Версия 8.3.19" class="tag_26"><td><a name="b50d611d-ba37-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Improved spreadsheet document switch to compact mode used on mobile devices.</td><td>Switching a spreadsheet document to compact mode was not optimal.</td><td>Improved spreadsheet documents view on mobile devices.</td></tr><tr title="Версия 8.3.19" class="tag_32"><td><a name="79c821cf-f463-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile Application Builder no longer supports the following features:<ul><li>Build mobile applications using Apache Ant.</li><li>Build mobile applications using Android SDK 25 and earlier.</li><li>Build mobile applications managed by Windows 8.1.</li></ul><p>
If you need to use these features, use Mobile Application Builder 8.3.18 or earlier.</p></td><td>Mobile Application Builder supported:<ul><li>Build mobile applications using Apache Ant.</li><li>Build mobile applications using Android SDK 25 and earlier.</li><li>Build mobile applications managed by Windows 8.1.</li></ul></td><td>Mobile Application Builder no longer supports obsolete technologies and mobile operating systems.</td></tr><tr title="Версия 8.3.19" class="tag_30 tag_31 tag_32"><td><a name="9da5b632-f465-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Starting from mobile version 8.3.19.52, you can build mobile applications for Android in the application bundle format (aab-file).<p>Changed files in the mobile distribution package.</p><p>With Mobile Application Builder, you can build applications in any format depending on the mobile version used to build the mobile application.</p><p>With Mobile Application Builder, you can upload any built application option to the application store (but not both at the same time). Before importing version 8.3.19.52 or later to Mobile Application Builder, update the builder to the distribution package version.
</p></td><td>1C:Enterprise mobile version (including Mobile Application Builder) did not support building application bundles (aab files).</td><td>You can now build mobile applications and upload them to Google Play store.</td></tr><tr title="Версия 8.3.19" class="tag_84"><td><a name="54b988f1-2745-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Localized client application interface for Turkmenian (<span class="interface">tk</span>).</td><td>This feature was not provided.</td><td>1C:Enterprise is now available to Turkmenian-speaking users.</td></tr><tr title="Версия 8.3.19" class="tag_30 tag_31 tag_48"><td><a name="50c34e72-325e-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Improved recognition of DataMatrix codes using mobile device cameras:<ul><li>New feature: recognition of a light-colored code on a dark background.</li><li>New feature: recognition of round pixels in the code.</li><li>Improved recognition of complex codes: on crumpled paper, with reflections, and so on.</li></ul><p>The following changes are implemented when recognizing barcodes using mobile device cameras: </p><ul><li>Automatic setting of 1.5x magnification for easy scanning of small barcodes.</li><li>Reduced frame rate for recognition.</li><li>Reduced timeout between consecutive scans to 1.3 seconds.</li></ul></td><td>DataMatrix code recognition did not work in some common situations.<p>Scanning small barcodes with mobile device cameras was inconvenient. The pause between consecutive scans was 2 seconds.</p></td><td>Improved use of mobile device cameras to scan DataMatrix codes and other barcodes.</td></tr><tr title="Версия 8.3.19" class="tag_7"><td><a name="b5fad3f3-32ff-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Improved performance of initial filling of a database copy.</td><td>Initial filling of a database copy took more time.</td><td>Improved performance of initial filling of a database copy.</td></tr><tr title="Версия 8.3.19" class="compat tag_26 tag_1"><td><a name="3aace5f7-a131-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The <span class="interface">Save</span> command in spreadsheet documents works as follows:<ul><li>If the file name is not specified or the the spreadsheet document is in the "Read only" mode, a dialog box for selecting a file to save is displayed.</li><li>If the file name is specified and the spreadsheet document is in the editing mode, it is saved without displaying a dialog box for selecting a file.</li></ul><p>This change is not implemented in 8.3.18 compatibility mode.</p></td><td>The <span class="interface">Save</span> command in spreadsheet documents was performed in the same way as the <span class="interface">Save as</span> command.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cacd4cf8-ca96-11ea-8371-0050569f678a">Transition from the previous version to the version 8.3.19</a></h2><ul><li title="Версия 8.3.19" class="tag_0"><a name="cacd4cf9-ca96-11ea-8371-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.19.
</li><li title="Версия 8.3.19" class="tag_0"><a name="cacd4cfa-ca96-11ea-8371-0050569f678a"></a>Some features that are added in version 8.3.19 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li></ul><p><a href="#cacd4ced-ca96-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h1><a name="cfd09ff9-5899-11ea-8371-0050569f678a">Version 8.3.18</a></h1><p title="Версия 8.3.18" class="tag_0"><a name="cfd0a007-5899-11ea-8371-0050569f678a"></a>Version 8.3.18 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#cfd09ffa-5899-11ea-8371-0050569f678a">New functionality and changes</a></li><li><a href="#cfd09ffb-5899-11ea-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#cfd09ffc-5899-11ea-8371-0050569f678a">Optimization</a></li><li><a href="#cfd09ffd-5899-11ea-8371-0050569f678a">Changes that affect system behavior</a></li><li><a href="#cfd09ffe-5899-11ea-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#cfd09fff-5899-11ea-8371-0050569f678a">Renamed objects</a></li><li><a href="#cfd0a000-5899-11ea-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#cfd0a001-5899-11ea-8371-0050569f678a">Library updates
</a></li><li><a href="#cfd0a002-5899-11ea-8371-0050569f678a">Demo configuration changes</a></li><li><a href="#cfd0a003-5899-11ea-8371-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#cfd0a004-5899-11ea-8371-0050569f678a">Transition from the previous version to the version 8.3.18</a></li></ul><h2><a name="cfd09ffa-5899-11ea-8371-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.18" class="compat tag_2 tag_1"><td><a name="b84522ad-5c8d-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.17</span> is now implemented.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.16 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.17 or earlier can now run on version 8.3.18 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.18 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.17 after the migration to version 8.3.18, even if you disable the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.18" class="tag_28"><td><a name="e3c4fe7d-5df0-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Support for the progressive web application (Progressive Web Apps, PWA) is implemented for the web client. A progressive web application is supported for Google Chrome version 73 and later, and if the web client is published using HTTPS protocol.<p>The <span class="interface">Display </span>as a standalone application command is implemented in the <span class="interface">Tools and Settings</span> menu.</p><p>The <span class="term">ProgressiveWebApplication </span>global context property is implemented.</p><p>The <span class="term">ProgressiveWebApplicationName</span> web client start option is implemented.</p><p>The <span class="term">progressiveWebApplication </span>element is implemented for <span class="interface">default.vrd</span> file.</p></td><td>This feature was not provided.</td><td>Sending the web client application launch icon to the desktop is now available. The web client (in progressive web application mode) is started in a separate window, and not in a web browser window.</td></tr><tr title="Версия 8.3.18" class="tag_69"><td><a name="d0a6ee38-5df3-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Updated asynchronous calls processing. Implemented the option to describe the method as an asynchronous, nonblocking analogue of a usual method. Asynchronous methods always return a <span class="term">Future </span>object. The result of the asynchronous method is returned through this object.<p>Implemented <span class="term">Asynch </span>modifier used to describe the method. Implemented <span class="term">Future</span>, <span class="term">AddInAsynchCallResult </span>methods. Implemented <span class="term">Wait </span>operator.</p><p>The <span class="term">&lt;MethodName&gt;Asynch</span>, <span class="term">Get&lt;PropertyName&gt;Asynch </span>and <span class="term">Set&lt;PropertyName&gt;Asynch </span>methods should be used to work with add-ins. These methods are added automatically by the platform; no add-in modification is required.</p><p>For global context methods and 1C:Enterprise language objects starting with <span class="term">Show </span>and <span class="term">Start</span>, analogues with the <span class="term">Asynch </span>name suffix are implemented.</p></td><td>This feature was not provided.<p>Using asynchronous methods required using special notification handlers.</p></td><td>Using asynchronous methods was improved.
</td></tr><tr title="Версия 8.3.18" class="tag_37 tag_28"><td><a name="204fbb98-5dfd-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Now you can get information about MAC addresses of network adapters of the current computer in client applications (thin, thick, and web client).<p>New object: <span class="term">NetworkAdapterInformation</span>. New global context methods: <span class="term">GetNetworkAdaptersInformation()</span>, <span class="term">BeginGettingNetworkAdaptersInformation()</span>, and <span class="term">GetNetworkAdaptersInformationAsync()</span>.</p><p>For the web client, install the extension to get information about the computer. New methods: <span class="term">BeginInstallingComputerInformationExtension()</span> and <span class="term">BeginAttachingComputerInformationExtension()</span>.</p></td><td>This feature was not provided.</td><td>You can get MAC address of the client computer if it is required for interaction with external systems.</td></tr><tr title="Версия 8.3.18" class="tag_84"><td><a name="c8ddcb13-5dfe-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Chinese language (zh, zh_CN) support is implemented for <span class="term">NumberInWords()</span> method.</td><td>This feature was not provided.</td><td>Simplified the presentation of information for Chinese-speaking users.</td></tr><tr title="Версия 8.3.18" class="tag_19 tag_29"><td><a name="07c2bf85-5e05-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>PostgreSQL DBMS 12 (x86-64) is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.18" class="tag_19"><td><a name="f72f193a-9906-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 12.2 is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.18" class="tag_36"><td><a name="75f0d454-5e1e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The <span class="term">DataHashing</span> object can calculate the <span class="term">SHA512</span> hash function.</td><td>This feature was not provided.</td><td>The list of supported hash functions is extended.</td></tr><tr title="Версия 8.3.18" class="tag_59"><td><a name="f0d68b49-62d8-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>Implemented the feature to specify a formatted string as the value of the <span class="term">Text </span>property for the following planner items: <span class="term">PlannerItem</span>, <span class="term">PlannerDimension</span>, <span class="term">PlannerDimensionItem</span>, <span class="term">PlannerBackgroundIntervalLabel</span>, <span class="term">TimeScaleItemLabel</span>. We have implemented the <span class="term">NewItemsTextType </span>property for the <span class="term">Planner </span>type form attribute, which allows to specify which text can be entered in new user-created planner items.<p>Implemented the feature to set actions for the planner item. Implemented the <span class="term">PlannerItem</span>.<span class="term">Actions </span>property. You can specify various appearance properties (accessibility, picture, presentation, alignment, etc.) for each action. Implemented the feature to configure various system reactions to the selection of actions or clicking the hyperlinks in the planner items.</p><p>The following events are implemented for planner field: <span class="term">OnURLClick</span>, <span class="term">OnPlannerActionClick</span>.</p><p>Implemented the feature to create planner items that are not user-editable. Implemented the <span class="term">PlannerItem</span>.<span class="term">EditingPermissionMode </span>property.</p><p>Implemented the feature to change the border color for planner background interval. Implemented the <span class="term">PlannerBackgroundInterval</span><span class="term">.BorderColor</span> property.</p><p>Implemented the feature to set the border for planner, planner background interval and planner item. Implemented the <span class="term">Border </span>property for <span class="term">Planner</span>, <span class="term">PlannerBackgroundInterval, PlannerItem</span> objects.</p><p>The <span class="term">Text </span>parameter of <span class="term">BeforeCreate </span>event of the planner extension for form field may have the values of <span class="term">Text </span>and <span class="term">FormattedString </span>type.</p><p>The <span class="term">Text </span>parameter of <span class="term">Add()</span> method in <span class="term">PlannerDimensionCollection</span>, <span class="term">PlannerDimensionItemsCollection </span>and <span class="term">PlannerBackgroundIntervalLabelsCollection </span>objects may have the values of <span class="term">Text </span>and <span class="term">FormattedString </span>type.</p><p>The <span class="term">Text </span>parameter of <span class="term">Insert</span><span class="term">()</span> method in <span class="term">PlannerDimensionCollection</span>, <span class="term">PlannerDimensionItemsCollection </span>and <span class="term">PlannerBackgroundIntervalLabelsCollection </span>objects may have the values of <span class="term">Text </span>and <span class="term">FormattedString </span>type.</p><p>For system enumeration </p><p><span class="term">PlannerCommandSource </span>the following new values are implemented: <span class="term">URL </span>and <span class="term">Action</span>.</p><p>For system enumeration <span class="term">PlannerCommandGenerationParameters </span>the <span class="term">URL</span>, <span class="term">Action</span>, <span class="term">Dimension </span>values are implemented.</p><p>For system enumeration <span class="term">StandardPlannerCommand </span>the <span class="term">GotoURL</span>, <span class="term">CopyURL</span>, <span class="term">ExecuteAction </span>values are implemented.
</p></td><td>These features were not provided.</td><td>New planner use features. Implementing a more friendly user interface using a planner is now possible.</td></tr><tr title="Версия 8.3.18" class="tag_54"><td><a name="fe8bfccb-62cd-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 54); return false;">Global search</a>.<br></td><td>Implemented the feature to set custom actions to the global search results. The set actions are displayed next to the global search result and are available for execution directly from the list of global search results.<p>Implemented the <span class="term">GlobalSearchResultItem.Actions </span>property. Implemented the <span class="term">OnGlobalSearchResultActionSelect </span>application module event handler.</p></td><td>These features were not provided.</td><td>Enhanced global search results formatting options.</td></tr><tr title="Версия 8.3.18" class="tag_38 tag_10"><td><a name="f9ada78e-6373-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented the feature to use configuration extensions for the <span class="term">/MergeCfg</span> Designer start command line command. The <span class="interface">.cfe</span> file may be used as command option. The <span class="term">-Extension</span> option is implemented for this command to specify the extension, which the command will be executed for.</td><td>The <span class="term">/MergeCfg</span> command did not allow to use the extensions.</td><td>Using extensions in automated scenarios in development, testing and maintenance of applications is now possible.</td></tr><tr title="Версия 8.3.18" class="tag_38"><td><a name="582ff491-6383-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Implemented the feature to expand the adopted objects attribute types, except for:<ul><li>common attribute types;</li><li>attributes with external data source types;</li><li>attributes having a definable type;</li><li><span class="term">Type </span>attribute of the chart of characteristic types.</li></ul><p>
Selecting actions for individual types when comparing and combining the extensions was implemented.</p></td><td>This feature was not provided.</td><td>New extension features.</td></tr></table><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd09ffb-5899-11ea-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.18" class="tag_4"><td><a name="46e7e709-6dca-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented the feature to hide all important notifications with one click in 1C:Enterprise - Startup and Notifications application. This feature appears if three (or more) notifications appear.<p>The button for clearing notifications in the notification center of the client application has <span class="interface">Clear </span>label now.</p></td><td>Hiding all important notifications with one click in 1C:Enterprise - Startup and Notifications application was not available.<p>The button for clearing notifications In the notification center of the client application was called <span class="interface">Clear </span><span class="interface">notifications</span>.</p></td><td>Improved using the notifications. A large number of notifications can be hidden in one action.</td></tr><tr title="Версия 8.3.18" class="tag_4"><td><a name="45762ac8-6dcf-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented highlighting of new messages in an open conversation.<p>Implemented an application title representation in the incoming video call title.</p><p>Implemented a feature to insert pictures using <span class="interface">Shift+Ins </span>hot-key.</p><p>When scrolling the list of messages up with the mouse wheel, the new messages are loaded automatically.</p><p>When sending a message, the read flag for this conversation is set.</p><p>Implemented caching of attachment files when they are received or opened (in the thin client) or received (in the web client).</p><p>Implemented the feature to quote messages. Implemented the <span class="interface">Quote </span>command in the selected text context menu. The "&gt;" character in the first position of the message line is the quotation flag.</p><p>Implemented the feature to copy a message with attachments.</p><p>For a client application running in Linux or Windows, the number of unread messages in the notification center is displayed as a number on the application icon in the taskbar and on the icon of the open notification list command.</p></td><td>These features were not provided.</td><td>Improved user operations in the collaboration system.</td></tr><tr title="Версия 8.3.18" class="tag_28 tag_11"><td><a name="e3015c60-9c10-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>64-bit add-ins are now supported by the web client in 64-bit Google Chrome and Mozilla Firefox web browsers running Windows.
</td><td>In 64-bit Google Chrome and Mozilla Firefox web browsers running Windows, the web client used 32-bit add-ins.</td><td>Improved support of 64-bit Google Chrome and Mozilla Firefox web browsers.</td></tr></table><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd09ffc-5899-11ea-8371-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.18" class="tag_47"><td><a name="ed77d2c8-5e08-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>Faster .DT file import to the infobase when using the standalone server management utility (<span class="interface">ibcmd</span>).</td><td>Importing a DT file to the infobase of a standalone server (using <span class="interface">ibcmd </span>utility) took longer.</td><td>Faster DT file import to the infobase of the standalone server.</td></tr><tr title="Версия 8.3.18" class="tag_12"><td><a name="7e32e4c5-5eae-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>Faster opening of the standard function main form for event log browsing.</td><td>Opening the standard function main form for event log browsing took longer.</td><td>Improved event log browsing.</td></tr><tr title="Версия 8.3.18" class="tag_6"><td><a name="ad23e70f-5eb5-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The time to obtain a client license by the session is significantly reduced in the following cases:<ul><li>Mass user operations start.</li><li>Restarting cluster managers after a software or hardware failure.</li></ul></td><td>Obtaining licenses took a lot of time and significantly slowed down the sessions starting in case of mass starting (or restarting) of the client sessions.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_64 tag_6"><td><a name="5e8ae84d-5eef-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved performance of the <span class="term">GetStringDeclensions()</span> and <span class="term">GetStringDeclensionsByNumber()</span> methods if the declension feature was used by several users at the same time when using client/server mode of the infobase.</td><td>If the <span class="term">GetStringDeclensions()</span> and <span class="term">GetStringDeclensionsByNumber()</span> methods are used by several users at the same time in the client/server mode of the infobase, execution of the methods took longer.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_97"><td><a name="d58b178b-5eef-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 97); return false;">Data access restrictions</a>.<br></td><td>Improved performance of <span class="term">StrContains()</span> function used in data access restriction templates.
</td><td>Performance of <span class="term">StrContains()</span> function used in data access restriction templates, was insufficient.</td><td>Improved performance of <span class="term">StrContains()</span> function used in data access restriction templates. </td></tr><tr title="Версия 8.3.18" class="tag_19"><td><a name="a8deedfe-5ef1-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>When using queries from the platform to Microsoft SQL Server DBMS, their plans are cached in the same viewpoint of properties as when executing these queries from SQL Server Management Studio with default settings. This does not result in generation of a different query plan when the query is executed again in SQL Server Management Studio, which simplifies the analysis of the query operation.
</td><td>When using the same query in Microsoft SQL Server DBMS directly from the platform and from SQL Server Management Studio, different query plans could be generated.</td><td>Simplified analysis of query plans that are used in Microsoft SQL Server DBMS.</td></tr><tr title="Версия 8.3.18" class="tag_7"><td><a name="73ddc39e-6dad-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Optimized the process of transferring completed transactions to the database copy.</td><td>The process of transferring completed transactions to the database copy took longer.</td><td>Faster transfer of data to the database copy.</td></tr><tr title="Версия 8.3.18" class="tag_25 tag_43"><td><a name="bb8cf86a-6db1-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Faster opening of report and dynamic list settings, as well as generation of data composition templates, if child fields of fields for which a large number of characteristics are defined are used in the data composition settings.</td><td>If the data composition settings involve child fields of fields for which a large number of characteristics are defined, opening report and dynamic list settings, as well as generating data composition templates took a lot of time.</td><td>Faster opening of dynamic list and report settings forms.</td></tr><tr title="Версия 8.3.18" class="tag_97"><td><a name="2638e077-6dd3-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 97); return false;">Data access restrictions</a>.<br></td><td>In data access restriction queries, a feature to replace subqueries that do not depend on the protected table with the result of their operation is implemented. Replacing one subquery for each protected table is supported. The result of calculating such subqueries is cached in the working process RAM.</td><td>Queries for data access restrictions were not subjected to additional processing and were always performed in their original form.</td><td>Improved performance of data access restriction queries. As a result of the change, the DBMS can plan a more efficient query.</td></tr><tr title="Версия 8.3.18" class="tag_60 tag_85"><td><a name="f8cd2b24-7972-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br><a href="#" onclick="onTagClick(this, 85); return false;">Processing PDF documents</a>.<br></td><td>Improved spreadsheet document export to PDF performance.</td><td>Exporting a spreadsheet document to PDF required more time.</td><td>Improved performance of spreadsheet document export to PDF format. Possible reduced size of the resulting PDF document if the original spreadsheet document contains cells with changed text orientation.</td></tr><tr title="Версия 8.3.18" class="tag_20"><td><a name="8b9d3179-894a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Faster standalone configuration generation.
</td><td>Standalone configuration generation took more time.</td><td>Faster standalone configuration generation.</td></tr><tr title="Версия 8.3.18" class="tag_26"><td><a name="f8abf824-894f-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Improved performance of spreadsheet documents with numerous merged cells in a great number of rows.</td><td>Operations with a spreadsheet document with numerous merged cells in a great number of rows took more time.</td><td>Improved performance of spreadsheet documents.</td></tr></table><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd09ffd-5899-11ea-8371-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.18" class="tag_47"><td><a name="954489a4-5d39-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>A partial import and export of configurations from files has been implemented for the standalone server management utility (<span class="interface">ibcmd</span>).<p>The following items are implemented for the <span class="term">config export </span>command:</p><ul><li>The <span class="term">--sync</span> option allows to synchronize the configuration and the export directory.</li><li>The <span class="term">objects </span>command allows to export only those configuration objects that are specified in the file, which is the command option.</li><li>The <span class="term">info </span>command allows to get information about the infobase used by the standalone server.</li><li>The <span class="term">status </span>command allows to get the differences between the configuration and the export directory.</li><li>The <span class="term">base </span>command allows to export changes to the infobase configuration relative to the directory with previously exported files.</li><li>The <span class="term">all-extensions</span> command allows to export all the infobase extensions to files.
</li></ul><p>The following commands are implemented for the <span class="term">config import</span> command:</p><ul><li>The <span class="term">files </span>command imports data from files that are listed as a command option.</li><li>The <span class="term">all-extensions</span> command allows to import all the extensions that are in the specified directory from the files.</li></ul></td><td>The standalone server management utility (<span class="interface">ibcmd</span>) allowed only complete configuration import and export from/to files.</td><td>Expanded standalone server capabilities.</td></tr><tr title="Версия 8.3.18" class="compat tag_37 tag_1"><td><a name="b496c224-5d3c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Implemented the feature to receive and set a custom text type for an email message when using <span class="term">InternetMail </span>feature.<p>Implemented <span class="term">CustomText </span>value for the <span class="term">MailTextType </span>enumeration. Implemented <span class="term">CustomTextType </span>property for the <span class="term">InternetMailText</span> object, which contains the actual text type from the email <span class="term">Content-Type</span> property. If the platform cannot define the mail message type, the <span class="term">InternetMailText.TextType</span> property is set to <span class="term">MailTextType.CustomText</span>.</p><p>The <span class="term">TextType </span>parameter of the <span class="term">InternetMailTexts.Add()</span> method may have a <span class="term">String</span> type value.</p><p>When generating the mail text that will be actually sent to the mail server, the <span class="term">charset </span>parameter with the encoding specified in the <span class="term">InternetMailTexts.Encoding</span> property will be added to (or replaced in) the <span class="term">Content-Type</span> header.</p><p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>When using Internet mail, receiving the actual type of mail message was not available. If the platform could not define the mail message type, the <span class="term">InternetMailText.TextType</span> property was set to <span class="term">MailTextType.SimpleText</span>.<p>When generating the text of the mail to be actually sent to the mail server, the <span class="term">charset </span>parameter in the <span class="term">Content-Type</span> header was not generated.</p></td><td>Improved working with emails such as meeting invitations that are sent from electronic calendars when using Internet mail.</td></tr><tr title="Версия 8.3.18" class="tag_4"><td><a name="e1f09504-5d3e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented a feature of creating a robot (bot) that runs on the 1C:Enterprise server (does not require a running instance of the client application) for the collaboration system.<p>Implemented the <span class="term">CollaborationSystemBot </span>object. The <span class="term">ProcessBots()</span>, <span class="term">NewBot()</span>, <span class="term">GetBot()</span>, <span class="term">GetBots()</span> methods were implemented for collaboration system manager.</p><p>Implemented system background jobs for bot operations.</p><p>Implemented the bot using features in the collaboration system management system data processor.</p></td><td>Implementing a robot (bot) required constantly running client application. Distinguished entity to describe bots was absent.</td><td>Simplified the robots (bots) creation in the collaboration system. A working robot does not require a running client application.</td></tr><tr title="Версия 8.3.18" class="tag_6"><td><a name="5bb281ab-5e08-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New feature: parallel recalculation of register totals is available upon infobase restructuring, testing, and repair. System background jobs are used for recalculation. ID of such a background job is <span class="term">SystemBackgroundJob.RecalcTotals</span>. Implemented the <span class="interface">Number of totals recalculation </span>job parameter for the<span class="interface"> </span><span class="interface">Infobase parameters</span><span class="interface"> </span>dialog box. There are 4 recalculation background jobs by default.<p>New global context methods: <span class="term">GetTotalsRecalculationJobsCount()</span> and <span class="term">SetTotalsRecalculationJobsCount()</span>.</p></td><td>Register totals were recalculated sequentially upon infobase restructuring, testing, and repair for all required infobase registers.</td><td>New feature: totals are recalculated faster upon infobase restructuring, testing, and repair.</td></tr><tr title="Версия 8.3.18" class="tag_83"><td><a name="0ac86530-5e0b-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 83); return false;">HTML support</a>.<br></td><td>Availability of the <span class="term">HTMLDocumentShell.TemplateLanguageCode</span> property in the Syntax Assistant was removed for the thick client.</td><td>The <span class="term">HTMLDocumentShell.TemplateLanguageCode</span> property in the Syntax Assistant was available for the thick client.</td><td>Fixed bug in the Syntax Assistant.</td></tr><tr title="Версия 8.3.18" class="tag_60 tag_85"><td><a name="afe4ea6d-5e0b-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br><a href="#" onclick="onTagClick(this, 85); return false;">Processing PDF documents</a>.<br></td><td>When saving a spreadsheet document to PDF, the JPEG pictures are saved in a compressed format. The picture format does not change.</td><td>When saving a spreadsheet document to PDF, the pictures were saved without using JPEG compression algorithms.</td><td>Reduced size of PDF documents if the original spreadsheet document contains JPEG images.</td></tr><tr title="Версия 8.3.18" class="tag_38"><td><a name="209e677a-5e1e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Implemented a feature to continue full-fledged using of the configuration, if the extensions that perform data extension were not attached for some reason when starting the configuration.<p>In this case, the default values for the corresponding types will be written in the extended attributes.
</p></td><td>If not all extensions that perform data extension are attached on session start, the application could read the extended configuration data of successfully attached extensions without errors. At the same time, an attempt to write an object, which data is supplemented by a disabled extension, was not available.
</td><td>An application that uses an extension, which performs data extension, remains fully functional (except for non-attached extensions), if not all extensions that perform data extension are attached.</td></tr><tr title="Версия 8.3.18" class="tag_36"><td><a name="02bf529a-5eb5-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The Russian letter "ё" is now supported by the <span class="term">GetStringDeclensions()</span> and <span class="term">GetStringDeclensionsByNumber()</span> methods.</td><td>The <span class="term">GetStringDeclensions()</span> and <span class="term">GetStringDeclensionsByNumber()</span> methods replaced "ё" with "е" and performed resulting string declension after that.</td><td>The Russian letter "ё" is no longer replaced with "е" when using <span class="term">GetStringDeclensions()</span> and <span class="term">GetStringDeclensionsByNumber()</span> methods.</td></tr><tr title="Версия 8.3.18" class="tag_69"><td><a name="d4aee643-5eb7-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The <span class="term">Number()</span> function allows to convert exponential number representations to numbers only if the absolute value of that number order does not exceed 1,000. In the web client, the <span class="term">Number()</span> function does not support conversion from the exponential number representation.</td><td>The <span class="term">Number()</span> function allowed exponential number representations to be converted to numbers without limiting the order value. This could cause a very large memory consumption and a very large amount of time spent on arithmetic operations with these values.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_11"><td><a name="489c016b-5ec2-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>The name of the temporary file, which the add-in is saved to before attachment, includes the name of the original add-in file. Thus, the full name of the add-in file consists of a prefix (assigned by the platform according to the standard algorithm for generating the temporary file name) and a suffix (which includes the name and extension of the original add-in file obtained from the add-in manifest).</td><td>The name of the temporary file, which the add-in is saved to before attachment, consisted only of an arbitrary temporary file name (with the <span class="interface">.tmp</span> extension) which was generated by 1C:Enterprise.</td><td>Simplified diagnostics of faults caused by problems in attached add-ins. Various event logs will clearly show the name of the add-in, in which the error occurred.</td></tr><tr title="Версия 8.3.18" class="tag_23"><td><a name="1ebc5f34-5ecd-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>If the main form attribute is <span class="term">ConstantsSet </span>and there are no constants in the set when the form is opened (due to access right restrictions or displayed type restrictions), methods of reading data and writing data to an infobase are not called for the constant set upon opening or closing the form.</td><td>If the main form attribute was <span class="term">ConstantsSet</span> and there were no constants in the set when the form was opened (due to access right restrictions or displayed type restrictions), unavailable infobase constants were filled in with defaults for their types.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_59"><td><a name="9e9be4b7-62bc-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>Changed the behavior of some buttons in the objects and record sets forms:<ul><li>The <span class="interface">Delete</span>, <span class="interface">Reread </span>buttons are not available in the new object or the information register record forms and external data source table.</li><li>The <span class="interface">Mark for deletion </span>button is not available in the new object form.</li><li>The <span class="interface">Activate </span>button is not available in the new job form.</li><li>When clicking <span class="interface">Copy</span>, <span class="interface">Mark for deletion</span>, you will be offered to save the object and then perform an action or refuse an action in the new object, new information register record forms, or the external data source table record.</li></ul></td><td>The <span class="interface">Delete</span><span class="interface">, </span><span class="interface">Reread</span>, <span class="interface">Mark for deletion</span>, <span class="interface">Activate </span>and <span class="interface">Copy </span>commands were always available in the new object, information register records forms or external data source records.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_36 tag_1"><td><a name="12ab5e4b-637c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>If the <span class="term">ConvertibleSplitterOfLines </span>property is not set for <span class="term">DataReader</span> object or is set to <span class="term">Chars.CR+Chars.LF</span>, and the text file being read contains consecutive <span class="term">Chars.CR </span>characters between the combinations of<span class="term"> Chars.CR+Chars.LF</span>, the <span class="term">ReadChars() </span>method will be executed as follows:<ul><li>Each pair of <span class="term">Chars.CR+Chars.LF</span> will be replaced with <span class="term">Chars.LF</span>.</li><li>All other characters are returned as is.</li></ul><p>
This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>If the <span class="term">ConvertibleSplitterOfLines </span>property was not set for <span class="term">DataReader </span>object or was set to <span class="term">Chars.CR+Chars.LF</span>, and the text file being read contained consecutive <span class="term">Chars.CR</span> characters between the combinations of <span class="term">Chars.CR+Chars.LF</span>, the <span class="term">ReadChars() </span>method could violate the sequence of characters (including permutation of characters, deletion and addition of <span class="term">Chars.CR </span>or <span class="term">Chars.LF</span>).
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_63 tag_1"><td><a name="04755f90-6384-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Improved the Gantt chart representation.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>The Gantt chart looked different.</td><td>Merging of connection lines is excluded, the number of connection lines of complex shape is reduced, the appearance of the chart items is improved on the Gantt chart.</td></tr><tr title="Версия 8.3.18" class="tag_73"><td><a name="46ea015e-6387-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>When using the optimized infobase restructuring feature, the actual restructuring will be performed if:<ul><li>The following changes to the configuration objects were made:</li><li>The tables of restructured objects do contain data that must be changed during the update process. If there is no such data, no action is taken and the restructuring is considered completed.</li></ul></td><td>The optimized infobase restructuring feature always performed database tables restructuring if the following changes were made to the configuration objects:<ul><li>A type was removed from a composite type.</li><li>A recorder was removed from the information register, accumulation register or accounting register.</li><li>A value was removed from enumeration.</li></ul></td><td>In some cases, significant improvement of the optimized infobase restructuring feature performance can be reached.</td></tr><tr title="Версия 8.3.18" class="tag_64"><td><a name="14f51e13-6da1-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>If the parameter of the <span class="term">GetStringDeclensions()</span> or <span class="term">GetStringDeclensionsByNumber()</span> methods contains unequal number of opening and closing brackets or quotes, the platform will automatically fix this issue and decline the correct phrase. The resulting number of brackets or quotes will match the number of brackets or quotes in the parameter.</td><td>If the parameter of the <span class="term">GetStringDeclensions()</span> or <span class="term">GetStringDeclensionsByNumber()</span> methods contained unequal number of opening and closing brackets or quotes, the platform threw an exception.</td><td>The <span class="term">GetStringDeclensions()</span> and <span class="term">GetStringDeclensionsByNumber()</span> methods behavior became more logical.</td></tr><tr title="Версия 8.3.18" class="tag_21"><td><a name="ce9f1c44-6da8-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>If a full-text search is used to search by the beginning of a line, all the results are highlighted in the search results representation, regardless of the number of results.</td><td>If a full-text search was used to search by the beginning of a line, and a large number of words were found that satisfied the search query as a result of the search, the found words may not be highlighted in the search results.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_45 tag_1"><td><a name="c9a99f12-6db6-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Query Wizard generates missing aliases of query fields using the same scheme as the query execution functionality.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>Query Wizard could generate missing aliases of query fields using a scheme different from the scheme used upon query execution.</td><td>Now automatic generation of aliases of query fields (in different platform tools) is consistent.</td></tr><tr title="Версия 8.3.18" class="tag_4"><td><a name="6234bd07-6dd0-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented the standard collaboration system commands, which allow to copy the attachment and quote the message. Implemented the <span class="term">CopyAttachment </span>and <span class="term">QuoteMessage </span>values for <span class="term">CollaborationSystemStandardCommand </span>system enumeration.<p>Implemented the default constructor for <span class="term">CollaborationSystemUserIDCollection </span>object.</p><p>Implemented the <span class="term">VideoconferencesAreAvailable()</span>, <span class="term">GetMaximumVideoconferenceParticipantsNumber()</span> and <span class="term">StartVideoconference()</span> methods for <span class="term">CollaborationSystemManager </span>object.</p></td><td>These features were not provided.</td><td>Expanded the collaboration system usage capabilities.</td></tr><tr title="Версия 8.3.18" class="tag_11 tag_28"><td><a name="a4640498-892b-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>An attempt to use a non-existent add-in method or property in web client generates an error that can be caught in the <span class="term">Try–Except </span>clause. The method or property is not called at all.<p>The behavior in thick, thin, and web client applications is now the the same.</p></td><td>An attempt to use a non-existent add-in method or property in web client initiated a call from the web client. If a method or a property was missing, an error occurred only in the error handler specified in notification details. The error could not be caught in the <span class="term">Try–Except </span>clause.</td><td>Web client behavior is now identical to thin and thick client behavior.</td></tr><tr title="Версия 8.3.18" class="tag_30 tag_31"><td><a name="ca31ecfd-8939-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Implemented the <span class="term">HomePageSettings</span> and <span class="term">HomePageForms</span> objects on the mobile application server and the standalone mobile server.</td><td>The <span class="term">HomePageSettings</span> and <span class="term">HomePageForms</span> were not available on the mobile application server and the standalone mobile server.</td><td>Now you can customize the application home page on your mobile device.</td></tr><tr title="Версия 8.3.18" class="tag_59"><td><a name="ee00de7d-894e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>In thick client and Designer, improved display of a table box whose header or footer contains numerous columns grouped into a composite multiline column using the <span class="term">Position</span> of table box column property.
</td><td>In thick client and Designer, a table box whose header or footer contained numerous columns grouped into a composite multiline column using the <span class="term">Posit</span>i<span class="term">on</span> of table box column property, was displayed with delay.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_25 tag_1"><td><a name="69228ef1-9f33-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The DCS template generator calculates the width (in cells) of each resource template displayed in a DCS table column as the maximum width of all templates displayed in this DCS table column (both generated and predefined templates). If predefined templates are specified for group and resource templates, the number of recourses specified for them in the data composition settings is not considered for such groups.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>The DCS template generator calculated the width (in cells) of each resource template displayed in a DCS table column based on all resources displayed in this template (in the data composition settings) and predefined templates. If the estimated template width was bigger than the predefined template width for a resource template specified for a table row/column intersection, the width of a template to create was equal to the estimated width.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_25 tag_1"><td><a name="f76e6b27-9f37-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When the Data Composition System groups by a calculated field, a presentation expression of this field (if specified) is used in this group and its nested groups when this field is displayed in the data composition result.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>When the Data Composition System grouped by a calculated field, a calculated field presentation was displayed in detailed records only.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_59"><td><a name="e0fa2f46-9f53-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>For a table that displays the value tree with one column, implemented the following algorithm for calculating the column width depending on the width of the text in rows of the tree being displayed:<ul><li>For table cells with disabled automatic calculation of the cell height, the table cell width is calculated based on the width of the text displayed in cells.</li><li>For table cells with enabled automatic calculation of the cell height, the table cell width is calculated based on the width specified in column properties upon configuration development. If there is less than half of the table width for text display in the visible table area, the text area width becomes equal to the table width, provided that this width is bigger than the width of the selected area.</li><li>The actual table column width is calculated as the maximum width of all cells displayed in the visible table area. </li></ul><p>For a table whose cell (not a complete row) is selected upon row selection, horizontal scrolling is done when you move between table rows or activate a row so that the text is fully displayed in the visible table area. If a text does not fit in the visible area, the text area is aligned to the left edge of the table.</p></td><td>For a table that displayed the value tree with one column, the column width and position of the text in a column did not depend on the text displayed in the tree.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_38"><td><a name="373be98a-a961-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>When the <span class="term">ChangeAndValidate </span>annotation is used in configuration extensions, the applicability check does not consider changes where empty strings and strings formed only with space and tab characters are added or deleted.</td><td>When the <span class="term">ChangeAndValidate </span>annotation was used in configuration extensions, the applicability check considered changes where empty strings and strings formed only with space and tab characters were added or deleted.</td><td>Decreased the amount of false positives of the extension applicability check.
</td></tr><tr title="Версия 8.3.18" class="tag_60 tag_30 tag_31"><td><a name="c7f37cc2-afa8-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Improved spreadsheet document conversion to compact mode (on a mobile device):<ul><li>Now you can move spreadsheet document cells that are under horizontal cell merge.</li><li>Implemented automatic highlighting for moved cells. A single spreadsheet document column is displayed in a single color. Highlighting does not apply when the text color is explicitly specified for a spreadsheet document cell.</li><li>Highlighting also does not apply when cells are not moved upon spreadsheet document conversion to compact mode.</li><li>Now dividing lines of a spreadsheet document are lighter.
</li></ul></td><td>The algorithm for spreadsheet document conversion to compact mode was different. The resulting spreadsheet document was not well suited for a mobile device.</td><td>Improved spreadsheet document display on a mobile device (compact spreadsheet document mode).</td></tr></table><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd09ffe-5899-11ea-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.18" class="compat tag_38 tag_1"><td><a name="02ae481d-5e0a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Calling extended form methods from an extension using the <span class="term">Execute()</span> method is no longer supported. Only the methods that are available through the <span class="term">ThisObject </span>property can be called.<p>It is recommended to analyze the extensions and refactor them, if necessary.</p><p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>Calling extended form methods from an extension using the <span class="term">Execute()</span> method was supported. </td><td>A form extension can only use the documented interface for using an extended form. A “documented interface" refers to methods declared in a form module using the <span class="term">Export </span>keyword.</td></tr><tr title="Версия 8.3.18" class="tag_10"><td><a name="a92fdc30-5e0a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The service message output file, which is specified in the <span class="term">/Out </span>command-line option of the client applications and Designer start, is generated in UTF-8.</td><td>The service message output file, which was specified in the <span class="term">/Out </span>command-line option of the client applications and Designer start, was generated in the operating system encoding.</td><td>The service message output file is always generated in the same encoding, regardless of the operating system encoding.</td></tr><tr title="Версия 8.3.18" class="tag_15 tag_29 tag_47"><td><a name="68943998-5e21-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>When using Linux, the feature was implemented to simultaneously install several versions of 1C:Enterprise, including those that differ only in the last (fourth) digit of the number.<p>Implemented automatic selection of the started client application version.</p><p>Changed starting of the server cluster and the location of the <span class="interface">srv1cv83 </span>and <span class="interface">srv1cv83</span>.conf files.</p><p>Implemented the feature to automatically update the client application over the network and from the web server. Implemented the feature to specify the location of client application distribution packages in the web client publishing dialog (in the Linux version of Designer).</p><p>The <span class="term">PublishDistributiveLocationLinuxDEB64</span>, <span class="term">PublishDistributiveLocationLinuxDEB32</span>, <span class="term">PublishDistributiveLocationLinuxRPM64</span>, <span class="term">PublishDistributiveLocationLinuxRPM32 </span>parameters are implemented for <span class="interface">conf.cfg</span> file. Implemented the <span class="term">pubdstlindeb64</span>, <span class="term">pubdstlindeb32</span>, <span class="term">pubdstlinrpm64</span>, <span class="term">pubdstlinrpm32 </span>attributes for the <span class="term">&lt;point&gt;</span> item of<span class="interface"> default.vrd</span> file.</p><p>Implemented the <span class="term">lindeb64</span>, <span class="term">lindeb32</span>, <span class="term">linrpm64</span>, <span class="term">linrpm32 </span>properties for the <span class="term">pubdst </span>parameter of the standalone server configuration file.</p></td><td>These features were not provided.</td><td>Using several versions of 1C:Enterprise simultaneously is now available when using Linux.</td></tr><tr title="Версия 8.3.18" class="tag_64"><td><a name="90929f95-5ec6-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>The Parameters parameter of <span class="term">StringWithNumber()</span> method was renamed to <span class="term">NumberFormatString</span>. A number format string similar to the <span class="term">Format()</span> method can be passed to this parameter.<p>The <span class="term">StringWithNumber()</span> method generates a number representation considering the current session or the passed format string locale.</p></td><td>The <span class="term">StringWithNumber()</span> method always generated a number representation considering the locale code passed as the method parameter and did not consider the current session locale.
</td><td>Eliminated unexpected system behavior.<p>The result of the <span class="term">StringWithNumber()</span> method now matches the current session locale.</p></td></tr><tr title="Версия 8.3.18" class="compat tag_23 tag_1"><td><a name="d1e6ae34-5ed5-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>The following changes have been implemented for document journals:<ul><li>The rows of the document journal table corresponding to documents, for which there is no <span class="term">Read </span>right, cannot be retrieved using the query language (dynamic list, data composition system).</li><li>The rows of the document journal table corresponding to documents, for which there is no <span class="term">View </span>right, cannot be retrieved using the data composition system when interactive rights check is enabled, for example, in a dynamic list and by default in reports.</li><li>A column of the document journal is available if at least one attribute included in this column is available.</li><li>The interactive properties of the <span class="interface">Password </span><span class="interface">mode</span>, <span class="interface">Format</span>, <span class="interface">Hint</span>, <span class="interface">Highlight </span><span class="interface">negative </span>and <span class="interface">Multiline </span><span class="interface">mode </span>document journal columns in the data composition system are received from the corresponding properties of the document attributes included in the journal column.</li><li>The data composition system uses the <span class="interface">Quick Select </span>property for fields with types of references to object tables of external data sources.
</li></ul><p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>The following behavior of document journals was observed:<ul><li>The rows of the document journal table corresponding to documents, for which there was no <span class="term">Read </span>right, could be retrieved using the query language, if there were <span class="term">Read </span>rights for the log table.</li><li>The rows of the document journal table corresponding to documents, for which there was no <span class="term">View </span>right, could not be retrieved using the data composition system when interactive rights check was enabled, for example, in a dynamic list and by default in reports.</li><li>A column of the document journal was available if all the attributes included in this column were available.</li><li>The interactive properties of the <span class="interface">Password mode</span>, <span class="interface">Format</span>, <span class="interface">Hint</span>,<span class="interface"> Highlight negative </span>and <span class="interface">Multiline mode </span>document journal columns in the data composition system were not received from the corresponding properties of the document attributes included in the journal column.</li><li>The data composition system did not use the <span class="interface">Quick Select </span>property for fields with types of references to object tables of external data sources.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_4 tag_1"><td><a name="bc423edb-62d6-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Reviewed the feature for working with actions in the collaboration system messages.<p>The <span class="term">CollaborationSystemMessageActionsCollection </span>type was implemented to generate the list of actions. The <span class="term">CollaborationSystemMessageActionsCollection </span>becomes a value type for the <span class="term">CollaborationSystemMessage.Actions</span> property. This change is not implemented in 8.3.17 version compatibility mode.</p><p>Implemented the <span class="term">OnCollaborationSystemActionSelect </span>event handler for application module.</p><p>The <span class="term">AttachMessageActionHandler()</span> and <span class="term">DetachMessageActionHandler()</span> are collaboration system manager methods considered obsolete and are not recommended for use.</p><p>It is necessary to change the algorithms for working with actions in the collaboration system messages in applications.</p></td><td>A list of values was used to specify the list of actions of the collaboration system. Setting the collaboration system message action handlers required using the <span class="term">AttachMessageActionHandler()</span> and <span class="term">DetachMessageActionHandler()</span> collaboration system manager methods.</td><td>Procedure of using actions is unified with the other platform features.</td></tr><tr title="Версия 8.3.18" class="compat tag_25 tag_1"><td><a name="fa0b7e3c-6da2-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If the data composition schema query contains union, and a filtering field is available for applying filter only (and is not available for selection) in several union parts, then the filter is applied only to the union parts where this field is available for filtering.<p>It is recommended to review data composition schemas that contain queries with unions.</p><p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>When applying a filter to a data set query containing a union, the filter was applied to all the union sections if at least one section a filtering field available for filter.</td><td>The result of applying filter in the data composition schema has become more predictable.</td></tr><tr title="Версия 8.3.18" class="compat tag_21 tag_1"><td><a name="99bddff3-6dae-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>When setting the value of the <span class="term">FullTextSearchList.SearchArea </span>property, an exception is thrown if the array being set contains an item that is not a metadata object.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>When setting the value of the <span class="term">FullTextSearchList.SearchArea </span>property, the validation of the value being set was not performed, however, when an attempt was made to get the search result (<span class="term">FullTextSearchList.First Part()</span> method), an exception was thrown with incomprehensible text.</td><td>Validation of parameters is aligned with standard practices. The error message now corresponds the detected error.</td></tr><tr title="Версия 8.3.18" class="compat tag_63 tag_1"><td><a name="91aa1dba-6daf-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The <span class="term">Data</span><span class="term">Source </span>chart property is not available in the thin client and web client. When attempting to set the value of this property using 1C:Enterprise language, an error is generated.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>The attempt to set the <span class="term">DataSource </span>chart property depended on the client application:<ul><li>An error was generated in the web client.</li><li>The setting worked in the thin client and the data was displayed in a chart until the first server call. The link of the chart to the data was lost after the first server call.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_63 tag_1"><td><a name="01c8d094-6db0-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Interactive chart editing with a set data source is not supported.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>For a chart with a set data source, the following behavior was observed when attempting to edit interactively:<ul><li>Chart values were edited.</li><li>The values in the data source did not change.</li><li>When changing values in the data source, all the changes made manually were lost and the chart displayed data from the data source.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_59 tag_1"><td><a name="74cd7a8e-6dc7-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>Window settings for thin client, web client, mobile client and mobile platform are stored with different settings keys suffixes. When changing the configuration compatibility mode, the following actions are performed:<ul><li>When setting the <span class="interface">Do not use </span>compatibility mode:</li><li>When setting the<span class="interface"> Version 8.3.17 </span>compatibility mode:</li><p>
</p><p>New settings keys are given in the documentation.
If the configuration uses direct operation with the window settings, it is recommended to analyze the program code that interacts with the settings and make appropriate changes to it.</p></ul><p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>These features were not provided.<p>Settings were stored separately for the web client (one setting) and all other client applications (another setting).</p></td><td>The client application window settings for different types of client applications are stored separately and do not mix with each other. Implementing software operations with the window settings of a single type of client application is simplified.</td></tr><tr title="Версия 8.3.18" class="compat tag_25 tag_1"><td><a name="cf8c8535-8897-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If condition <span class="interface">Contains</span>, <span class="interface">Does not contain</span>, <span class="interface">Like</span>, <span class="interface">Not like</span>, <span class="interface">Begins with</span>, or <span class="interface">Does not begin with </span>is specified for data composition filter set at the data set level and the condition string contains a single double quote ("""), Data Composition System escapes such characters automatically upon data composition template generation.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>If condition <span class="interface">Contains</span>,<span class="interface"> Does not contain</span>, <span class="interface">Like</span>, <span class="interface">Not like</span>, <span class="interface">Begins</span> <span class="interface">with</span>, or <span class="interface">Does</span> <span class="interface">not</span> <span class="interface">begin</span> <span class="interface">with</span> was specified for data composition filter set at the data set level and the condition string contained a single double quote ("""), Data Composition System did not escape such characters upon data composition template generation. Executing such data composition might have caused an error.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_16 tag_1"><td><a name="f3dbd814-98f4-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>Only register records with the <span class="term">Activity </span>property set to <span class="term">True </span>are included in the result of a query to a virtual table of the <span class="term">SliceLast </span>information register.<p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>All register records were included in the result of a query to a virtual table of the <span class="term">SliceLast </span>information register, regardless of the <span class="term">Activity </span>property value.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="compat tag_107 tag_54 tag_92 tag_21 tag_1"><td><a name="f7f28bfb-9f57-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 107); return false;">Input by string</a>.<br><a href="#" onclick="onTagClick(this, 54); return false;">Global search</a>.<br><a href="#" onclick="onTagClick(this, 92); return false;">Dynamic list</a>.<br><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Implemented the search query complexity limitation. The overall search query length must not exceed 1000 characters and 32 words. The limitations are implemented for the following mechanisms:<ul><li>Input by string.</li><li>Global search.</li><li>Dynamic list search string.</li><li>Full-text search.</li></ul><p>
In the parameter structure of the <span class="term">GetChoiceData()</span> method, the <span class="term">LimitSearchString </span>parameter that provides search without analyzing a search query is expected.</p><p>Implemented the <span class="term">FullTextSearchList.LimitSearchString </span>property. If this property is set to <span class="term">False</span>, full-text search does not analyze a search query.</p><p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>There was no search query complexity limitation, except for the search string of a dynamic list where the search string was not to exceed 1000 characters and 20 words.</td><td>Complexity of a search query to built-in search tools is limited to avoid high server load and unexpected shutdown due to a complex search query.</td></tr><tr title="Версия 8.3.18" class="tag_11"><td><a name="12c1b060-a96a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>Examples from add-in development technology are switched to build with CMake.<p>Static libraries for creating adapters for web browsers running Windows are built with Microsoft Visual Studio 2017 compiler that supports Windows XP.</p><p>Developers who develop circulation add-ins must develop an add-in for all operating systems from the list of system requirements <a href="http://v8.1c.ru/requirements/" target="_blank">Read more</a>.. Web client adapters for Windows must be built with Microsoft Visual Studio 2017 compiler that supports Windows XP. </p><p>Developers whose add-ins are developed for a specific deployment case can use the compiler they used for supported operating system versions. Still, use Microsoft Visual Studio 2017 compiler that supports Windows XP to build web client adapters for Windows.</p><p>Changes were made to development technology for add-ins (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>).</p></td><td>Examples from add-in development technology were built with Microsoft Visual Studio 2013.</td><td>A more modern set of tools is used to build demo add-ins.</td></tr><tr title="Версия 8.3.18" class="compat tag_59 tag_1"><td><a name="0fc804ef-a979-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>A line that does not fit to width in decorations, label fields, or field headers is broken by a word separator closest to the form item edge.<p>Upon disabling the compatibility mode, we recommend that you check that forms with texts that do not fit to width in decorations, label fields, or field headers are displayed correctly.</p><p>This change is not implemented in 8.3.17 version compatibility mode.</p></td><td>A line that did not fit to width in decorations, label fields, or field headers could be broken by a word separator that was not closest to the form item edge.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd09fff-5899-11ea-8371-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.18" class="tag_0"><td><a name="8a770ac2-5e04-11ea-8371-0050569f678a"></a>System event log event names.</td><td><ul><li><span class="term">_$InfoBase$_.InfoBaseAdmParamsUpdate</span>;</li><li><span class="term">_$InfoBase$_.InfoBaseAdmParamsUpdateError</span>;</li><li><span class="term">_$InfoBase$_.TARInfo</span>;</li><li><span class="term">_$InfoBase$_.TARMess</span>;</li><li><span class="term">_$InfoBase$_.TARImportant</span>;</li><li><span class="term">_$InfoBase$_.SecondFactorAuthTemplateNew</span>;</li><li><span class="term">_$InfoBase$_.SecondFactorAuthTemplateUpdate</span>;</li><li><span class="term">_$InfoBase$_.SecondFactorAuthTemplateDelete</span>.</li></ul></td><td><ul><li><span class="term">_$InfoBase$_.ParametersUpdate</span>;</li><li><span class="term">_$InfoBase$_.ParametersUpdateError</span>;</li><li><span class="term">_$InfoBase$_.VerifyAndRepairInfo</span>;</li><li><span class="term">_$InfoBase$_.VerifyAndRepairMessage</span>;</li><li><span class="term">_$InfoBase$_.VerifyAndRepairImportant</span>;</li><li><span class="term">_$InfoBase$_.SecondAuthenticationFactorTemplateNew</span>;</li><li><span class="term">_$InfoBase$_.SecondAuthenticationFactorTemplateUpdate</span>;</li><li><span class="term">_$InfoBase$_.SecondAuthenticationFactorTemplateDelete</span>.</li></ul></td></tr><tr title="Версия 8.3.18" class="tag_0"><td><a name="19e43a5b-893d-11ea-8371-0050569f678a"></a>Designer description for a name of a property with roles that will limit mobile user capabilities.<p>
</p></td><td><ul><li><span class="interface">Limiting roles of a standalone configuration.</span></li></ul></td><td><ul><li><span class="interface">Limiting roles of a standalone mobile application.</span></li></ul></td></tr><tr title="Версия 8.3.18" class="tag_0"><td><a name="3f398879-894c-11ea-8371-0050569f678a"></a>Check box of the configuration check dialog box that enables configuration check in the standalone mode.
</td><td><ul><li><span class="interface">Mobile client (standalone mode).</span></li></ul></td><td><ul><li><span class="interface">Mobile client (standalone mode) and standalone mobile server.</span></li></ul></td></tr><tr title="Версия 8.3.18" class="tag_0"><td><a name="835b6ecc-c02c-11ea-8371-0050569f678a"></a>Changed the <span class="term">File.Exist()</span> and <span class="term">FileDialog.CheckFileExist</span> methods names.<p>The former names are supported for compatibility purposes.</p></td><td><ul><li><span class="term">File.Exist()</span>.</li><li><span class="term">FileDialog.CheckFileExist</span>.</li></ul></td><td><ul><li><span class="term">File.Exists()</span>.</li><li><span class="term">FileDialog.CheckFileExistence</span>.</li></ul></td></tr><tr title="Версия 8.3.18" class="tag_0"><td><a name="7c4d9fad-30bb-11eb-8371-0050569f678a"></a><span class="term">CopyFile()</span> method description option.</td><td><ul><li><span class="term">FileCopy().</span></li></ul></td><td><span class="term">CopyFile()</span>.</td></tr><tr title="Версия 8.3.18" class="tag_0"><td><a name="54d0b8bd-4070-11eb-8371-0050569f678a"></a>The name of the method for verifying that a purchase has been made. The former name is supported for compatibility purposes.<p>
</p></td><td><ul><li><span class="term">Purchased()</span>.</li></ul></td><td><ul><li><span class="term">CheckPurchase()</span>.</li></ul></td></tr><tr title="Версия 8.3.18" class="tag_0"><td><a name="f2c67557-6c4c-11eb-8371-0050569f678a"></a>The names of the files with the Linux installation packages that contain the client application distribution packages.</td><td><ul><li><span class="interface">win-mac-clients-distr-A.B.C-D.i386.rpm</span></li><li><span class="interface">win-mac-clients-distr-A.B.C-D.x86_64.rpm</span></li><li><span class="interface">win-mac-clients-distr_A.B.C-D_amd64.deb</span></li><li><span class="interface">win-mac-clients-distr_A.B.C-D_i386.deb</span></li></ul><p>
In this list, <span class="interface">A.B.C-D</span> is the full version number of 1C:Enterprise.</p></td><td><ul><li><span class="interface">win-mac-clients-A.B.C.D-distr-A.B.C-D.i386.rpm</span></li><li><span class="interface">win-mac-clients-A.B.C.D-distr-A.B.C-D.x86_64.rpm</span></li><li><span class="interface">win-mac-clients-A.B.C.D-distr_A.B.C-D_amd64.deb</span></li><li><span class="interface">win-mac-clients-A.B.C.D-distr_A.B.C-D_i386.deb</span></li></ul><p>
</p>In this list,<span class="interface"> A.B.C.D </span>and <span class="interface">A.B.C-D</span> are the full version number of 1C:Enterprise</td></tr><tr title="Версия 8.3.18" class="tag_0"><td><a name="335af80f-f508-11eb-8371-0050569f678a"></a>The global context property that allows accessing data of the link used to start the application. The previous property name is supported for compatibility.</td><td><ul><li><span class="term">StartupURL</span>.</li></ul></td><td><ul><li><span class="term">StartupURLNavigationData</span>.</li></ul></td></tr></table><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd0a000-5899-11ea-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.18" class="tag_30 tag_31"><td><a name="ccf54163-6e72-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Implemented the feature to control the automatic image rotation when using the <span class="term">MultimediaTools.MakePhoto()</span> method. To do this, the <span class="term">AutoRotate</span> option is implemented in this method.</td><td>When using the <span class="term">MultimediaTools.MakePhoto()</span> method, the mobile version always rotated the resulting image if the orientation of the phone at the time of taking the photo did not match the orientation of the resulting photo.</td><td>Improving the performance of taking photos by disabling the resulting photo turning is now possible.</td></tr><tr title="Версия 8.3.18" class="tag_59"><td><a name="c2798bf7-7404-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>Implemented the grouping of fields in a system form, which is generated for editing a form table row (not associated with a dynamic list), if such grouping is implemented in the table settings. Only the first level of grouping is displayed. Other grouping levels are not displayed. They are placed in the parent group of the first level instead.</td><td>All the table row fields were displayed in a list without grouping in a system form, which was generated for editing a form table row (not associated with a dynamic list).
</td><td>Improved automatically generated form for editing a form table row.</td></tr><tr title="Версия 8.3.18" class="tag_20"><td><a name="bd460ced-894c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Now you can set up module check in the standalone mode of a mobile client in <span class="interface">Service – Parameters – Modules – Check</span>. Implemented the <span class="interface">Mobile client (standalone mode) and a standalone mobile server</span> check box.
</td><td>This feature was not provided.</td><td>Simplified real-time check of modules to be run in the standalone mode of a mobile client.</td></tr><tr title="Версия 8.3.18" class="tag_108 tag_30 tag_31"><td><a name="f5ec967c-95be-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 108); return false;">Printing tools</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Now the mobile application supports printers that are supported by the used mobile operating system.<p>You can switch between printing through the operating system and printing using the platform tools (printers that support PCL3 and ZPL languages) in infobase settings on your mobile device (in <span class="interface">Service and settings - Settings</span>) or in Mobile Application Builder (the <span class="interface">Print mode </span>application settings property).</p></td><td>1C:Enterprise mobile platform supported only printers supporting PCL3 and ZPL languages.</td><td>Extended list of printers supported by 1C:Enterprise mobile platform.</td></tr><tr title="Версия 8.3.18" class="tag_30 tag_31"><td><a name="8260b711-afbc-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Updated permission management for a mobile application built using Mobile Application Builder. Implemented the functionality mechanism that combines a mobile application permission and a text displayed to a user upon request for a permission. Included the mobile version functionality module in the mobile application.<p>If the functionality is disabled, the matching module will not be included in the build and an attempt to use this functionality will generate a runtime exception (on a mobile device).</p><p>Settings of mobile application functionalities can be accessed using the configuration property <span class="interface">Used mobile application functionality</span>.</p><p>Before you build a configuration to be dumped using version 8.3.18, we recommend that you check that the required functionality is specified correctly for the configuration.</p></td><td>The mechanism of mobile application permission management was different. It did not affect the total size of an application to build. A disabled permission might not affect performance of a built application.</td><td>Now it is easier to manage the used mobile application functionality. When a developer specifies a functionality, they must also specify the text to be displayed to a user upon request for a permission and make this functionality available for use.</td></tr></table><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd0a001-5899-11ea-8371-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.18" class="tag_0"><a name="879c5d68-0ec3-11eb-8371-0050569f678a"></a>The libjpeg library is updated to version 9d.</li></ul><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd0a002-5899-11ea-8371-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.18" class="tag_0"><a name="8e8f0055-c02b-11ea-8371-0050569f678a"></a>The home page of the demo configuration was revised.</li><li title="Версия 8.3.18" class="tag_0"><a name="805ea021-f368-11ea-8371-0050569f678a"></a>In the <span class="term">Users </span>catalog, implemented an example of how to create a video call or a chat with the selected user from the user edit form.</li><li title="Версия 8.3.18" class="tag_0"><a name="c164e174-f368-11ea-8371-0050569f678a"></a>Implemented an example of how to use global search for operations with counterparties. Now you can create a new sales order for the counterparty using global search.</li><li title="Версия 8.3.18" class="tag_0"><a name="aba91a72-f369-11ea-8371-0050569f678a"></a>Implemented the <span class="term">OfficeManager </span>bot to demonstrate how mechanisms work. The bot allows you to get prices and available stock for the specified goods, the state of mutual settlements with a counterparty, and the list of last three unclosed orders.<p>The <span class="term">Assistant </span>conversations features are moved to the <span class="term">OfficeManager </span>bot.</p></li><li title="Версия 8.3.18" class="tag_0"><a name="ebc87542-f369-11ea-8371-0050569f678a"></a>The calendar form demonstrates how you can use new features of the <span class="term">Planner </span>object. Changed the calendar description text in the configuration guide.</li><li title="Версия 8.3.18" class="tag_0"><a name="15bb8a54-f40d-11ea-8371-0050569f678a"></a>The user settings form was revised. New feature: you can install a progressive web application (if the demo configuration runs in the web client) and enable notifications even when the application is closed.</li><li title="Версия 8.3.18" class="tag_0"><a name="35f3af4f-f40d-11ea-8371-0050569f678a"></a>The configuration guide includes new sections about a progressive web application and <span class="interface">1C:Enterprise Notifications and startup</span>.</li></ul><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd0a003-5899-11ea-8371-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.18" class="tag_45 tag_58"><td><a name="e1c36923-d625-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>In infobase file mode, execution of a query where an inner join between object data and its tabular section is being created is faster now. The upgrade is valid if an object used in a query is part of a common attribute that is a separator.</td><td>In infobase file mode, it took more time to execute a query where an inner join between object data and its tabular section was being created for an object included into the separator.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_20"><td><a name="91e31b0c-d627-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Now you can press<span class="interface"> Ctrl+Alt+E</span> to abort long-running operations on Windows. You can still press <span class="interface">Ctrl+Break </span>for this purpose. Both shortcuts can be used at the same time.</td><td>To abort long-running operations, you could press <span class="interface">Ctrl+Break </span>on Windows.</td><td>Now you can abort long-running operations on devices without the <span class="interface">Break </span>key.</td></tr><tr title="Версия 8.3.18" class="tag_63"><td><a name="80444e4e-d630-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>A chart tooltip is no longer covered by a formatted document field or the planner field. A chart tooltip is displayed without semitransparency if a thin or thick client application runs Linux or macOS.</td><td>A chart tooltip could be covered by a formatted document field or the planner field. It was impossible to view some tooltip information.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_38"><td><a name="a9059519-d63c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: you can change data of a configuration object whose attribute types are changed by an inactive extension.<p>When reading objects with attribute types modified by disabled configuration extensions, values stored in a database will be converted to configuration types, ignoring inactive extensions.</p><p>On recording, only changed attributes will be updated.</p><p>Information about disabled extensions is added to an error report. Changed the format of the <span class="interface">report.json</span> file to which collected error information is placed automatically.</p><p>We recommend that you use this mode as emergency mode when you need to update an application infobase if there are extensions that are incompatible with a new configuration version.</p></td><td>It was not possible to change data of a configuration object whose attribute types were changed by an inactive extension.</td><td>Simplified configuration update if an extension that modifies attribute types of an extended configuration becomes inactive once the extended configuration is updated.</td></tr><tr title="Версия 8.3.18" class="tag_30 tag_31 tag_32"><td><a name="5b90fb16-dc87-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Now you can open the mobile application by clicking an URL. You can set up schemas and links the mobile application reacts to in Designer or Mobile Application Builder. Now the configuration supports navigation to the application when clicking an URL.<p>New configuration property: <span class="term">MobileApplicationURLs</span>. New handler in the application module: <span class="term">URLNavigationProcessing()</span>. New global context method: <span class="term">GetExternalURL()</span>.</p></td><td>This feature was not provided. The mobile application could not be called from another application, for example, when a hyperlink was placed in email.</td><td>Added new features for 1C:Enterprise mobile version. Now you can register specific URLs. When you click them in another application, the mobile application opens automatically.</td></tr><tr title="Версия 8.3.18" class="tag_29"><td><a name="813b4fc4-f341-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>1C:Enterprise now supports Microsoft Windows Server 2019 (x86-64).</td><td>1C:Enterprise did not support Microsoft Windows Server 2019 (x86-64).</td><td>The list of supported operating systems is extended.</td></tr><tr title="Версия 8.3.18" class="tag_59"><td><a name="3bf29fca-f424-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>In the client application form, you can now handle the following events of the form field extension for the planner field:<ul><li>Selecting an empty planner area to create a planner item.</li><li>Selecting planner items.</li><li>Dragging or changing borders of one or more planner items.</li><li>Copying one or more planner items.</li></ul><p>Implemented the event handler of the form field extension of the client application for the <span class="term">CheckDraggingInside </span>planner field.</p><p>For the event handler of the form field extension of the client application for the <span class="term">BeforeCreate </span>planner field, the following parameters become return parameters: <span class="term">Start</span>, <span class="term">End</span>, <span class="term">DimensionsValues</span>, and <span class="term">Text</span>.</p></td><td>Dragging items within the planner field and changing the size of planner field items were not available.</td><td>New features for interactive editing of the planner field.</td></tr><tr title="Версия 8.3.18" class="compat tag_53 tag_1"><td><a name="ed6dcf8b-f429-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>Implemented a new error category: a database copy error. Errors that occur while using database copies fall into this category.<p>Implemented value of the <span class="term">ErrorCategory.DatabaseCopyError </span>system enumeration.</p><p>This change is not implemented in 8.3.17 compatibility mode.</p><p>
</p></td><td>Errors that occurred while using database copies fell into the category of external data source errors.</td><td>Improved error categorization.</td></tr><tr title="Версия 8.3.18" class="tag_26 tag_28"><td><a name="7ec19b55-f42a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Improved update of a spreadsheet document displayed in the web client with scale greater than 100% when editing text in cells. Once you finish editing text in a cell, the server is no longer called if the entered text fits the cell.</td><td>Once you finished editing text in a cell of a spreadsheet document displayed in the web client with scale greater than 100%, the server was called if the entered text fitted the cell.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_37"><td><a name="a8b3292d-06d2-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>New property: <span class="term">NetworkAdapterInformation.IPAddress</span>. The property contains a network adapter IP address that describes the <span class="term">NetworkAdapterInformation</span> object.</td><td>This feature was not provided.</td><td>Expanded the network adapter information provided by 1C:Enterprise.</td></tr><tr title="Версия 8.3.18" class="tag_21 tag_53"><td><a name="110072c9-12cd-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>An attempt to search by a word for which a lot of matches are found generates an error. Reduced the full-text search index size for very large infobases.<p>New system enumeration value: <span class="term">ErrorsCategories.FullTextSearchError</span>.</p><p>We recommend that you clear the full-text search index and build it again if the full-text search index size exceeds 50 Gb.</p><p>When the previous platform version with the full-text search index built by platform version 8.3.19 is started, the index will be cleared and built again.</p></td><td>An attempt to search by a word for which a lot of matches were found could lead to unpredictable results.</td><td>Improved stability and fault tolerance of full-text search.</td></tr><tr title="Версия 8.3.18" class="tag_29 tag_19"><td><a name="81e98f69-12d7-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):<ul><li>Postgres Pro 1C 12.4.1,</li><li>Postgres Pro Standard 12.4.1,</li><li>Postgres Pro Enterprise 12.4.1.</li></ul></td><td>The following Postgres Pro DBMS versions were not supported:<ul><li>Postgres Pro 1C 12.4.1,</li><li>Postgres Pro Standard 12.4.1,</li><li>Postgres Pro Enterprise 12.4.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.18" class="tag_32"><td><a name="8d95fbac-28e1-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>The version of Mobile Application Builder now matches the number of the 1C:Enterprise mobile version the builder is supplied with. Thus, Mobile Application Builder that comes with the mobile version 8.3.18 has the version number 8.3.18.*. The fourth digit of the builder version number indicates the builder build number and has nothing to do with the fourth digit of the number of the mobile version of 1C:Enterprise.
</td><td>Mobile Application Builder had the numbering that did not match the number of the mobile version of 1C:Enterprise.</td><td>The numbering of Mobile Application Builder is now more transparent and associated with its mobile version of 1C:Enterprise.</td></tr><tr title="Версия 8.3.18" class="tag_32"><td><a name="7a8a256d-28e2-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile Application Builder does not support mobile versions of 1C:Enterprise whose number (first three digits) is greater than the builder version number (first three digits). Mobile Application Builder 8.3.18 will not load the mobile version 8.3.19 and later.<p>The builder still allows you to upload the previous mobile versions of 1C:Enterprise (8.3.17 and later).</p><p>In Mobile Application Builder, you can now block loading of configurations whose format is not supported by the current builder version.</p></td><td>Mobile Application Builder did not have any restrictions on loading mobile configurations and mobile versions of 1C:Enterprise. This could lead to hard-to-diagnose issues when configurations or mobile versions not supported by the builder were uploaded to the builder.</td><td>Mobile Application Builder no longer supports loading of objects that it does not support.
</td></tr><tr title="Версия 8.3.18" class="tag_15 tag_29"><td><a name="99dd0709-28e3-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following Linux distributions are now supported:<ul><li>ALT Education 9.</li><li>ALT Workstation 9.</li><li>ALT Workstation K 9.</li><li>ALT Server 9.</li></ul><p>The following Linux distributions are no longer supported:</p><ul><li>ALT Linux 6.0 SPT.</li><li>ALT Workstation 7.</li><li>ALT Server 7.
</li></ul></td><td>The following Linux distributions were supported:<ul><li>ALT Linux 6.0 SPT.</li><li>ALT Workstation 7.</li><li>ALT Server 7.</li></ul></td><td>The list of supported Linux distributions is brought up-to-date.</td></tr><tr title="Версия 8.3.18" class="tag_21"><td><a name="763b151f-32f0-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Changed the algorithm to perform the standard type of the <span class="term">Data </span>global search. As a result, the search returns a more relevant result in less time.<p>For the algorithm description, see the documentation.</p></td><td>When performing the standard type of the <span class="term">Data </span>global search, the result might not match the search string well.
</td><td>Improved relevance and performance of the standard type of the <span class="term">Data </span>global search.</td></tr><tr title="Версия 8.3.18" class="tag_74"><td><a name="a0e4e62e-33bd-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br></td><td>For system distribution packages designed for Windows XP, HASP Device Driver version 7.63 is now included.<p>The outdated <span class="interface">haspds_windows.dll </span>and <span class="interface">hdinst_windows.dll </span>files are removed from the distribution package.
</p></td><td>For system distribution packages designed for Windows XP, HASP Device Driver version 7.92 that did not run on this operating system was included.</td><td>Windows XP users can install HASP Device Driver directly from the current 1C:Enterprise distribution package.</td></tr><tr title="Версия 8.3.18" class="tag_69"><td><a name="1c2b5c80-4063-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Improved performance of the <span class="term">Insert()</span> and <span class="term">Get()</span> methods of the <span class="term">Map </span>object for cases when a reference to an infobase object is used as a map key.</td><td>The <span class="term">Insert()</span> and <span class="term">Get()</span> methods of the <span class="term">Map </span>object showed poor performance when a reference to an infobase object was used as a map key.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_48"><td><a name="0a44eb6a-4070-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Upgraged the in-app purchases mechanism. The purchases mechanism is based on the Google Play Billing 3 library.<p>New parameters for the <span class="term">InAppPurchases.UpdatePurchaseInformation()</span> method: <span class="term">PurchaseType </span>and <span class="term">AutoConfirmation</span>. New parameter for the <span class="term">InAppPurchases.BeginPurchasing()</span> and <span class="term">InAppPurchases.PurchaseAsync()</span> methods: <span class="term">AutoConfirmation</span>.</p><p>New methods for the <span class="term">InAppPurchasesManager </span>object: <span class="term">PurchasesConfirmationSupported()</span>, <span class="term">CheckConfirmation()</span>, and <span class="term">ConfirmPurchase()</span>.</p><p>To build a mobile application that supports the new in-app purchases mechanism, use Mobile Application Builder version 8.3.18 or later.</p><p>We recommend that you refactor the application to switch to the new in-app purchases interface.</p><p>The old purchases mechanism is only supported in version 8.2.17 and earlier compatibility mode.</p></td><td>The in-app purchases mechanism was based on Google Play through Android Interface Definition Languages.</td><td>Upgrade: the mobile application monetization mechanism is now supported, which will be required when publishing in Google Play, starting in August 2021.</td></tr><tr title="Версия 8.3.18" class="tag_46"><td><a name="3d63cc2b-4446-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br></td><td>You can now get the state of connection to an external integration service. You can now receive and delete messages that are in the integration service channel.<p>New methods for the manager of the external integration service channel: <span class="term">GetState()</span>, <span class="term">SelectMessages()</span>, and <span class="term">DeleteMessages()</span>.</p></td><td>These features were not provided.<p>The message when sent could only be out of date. If an error occurred while sending a message, this message blocked the channel.</p></td><td>New operations with messages in the channel of the external integration service.</td></tr><tr title="Версия 8.3.18" class="tag_32 tag_30 tag_31"><td><a name="1ef456df-5412-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>In Mobile Application Builder, you can now build mobile applications for iOS if the build uses a Mac based on the Apple M1 processor and uses macOS Big Sur.</td><td>Mobile Application Builder did not support running a build of mobile applications for iOS when the build used a Mac based on the Apple M1 processor and used macOS Big Sur.</td><td>Mobile Application Builder now supports modern Apple computers and operating systems.</td></tr><tr title="Версия 8.3.18" class="tag_14 tag_70 tag_10"><td><a name="4610986d-6c4c-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>On Linux, it is now possible to update the distribution package without additional configuration of the <span class="interface">default.vrd</span> file (via the <span class="interface">distr </span>directory of a specific version directory).<p>For Linux and Windows, installation package files that contain all client applications are implemented.</p></td><td>Updating the distribution package without additional configuration of the <span class="interface">default.vrd</span> file (via the distr directory of a specific version directory) was supported only by client applications for macOS and Windows.</td><td>It is now easier to configure distribution of client application distribution packages when updating the 1C:Enterprise version on servers running Linux.</td></tr><tr title="Версия 8.3.18" class="tag_28"><td><a name="877d092a-7761-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The web client now supports URLs:<ul><li>Global context event handler <span class="term">URLNavigationProcessing</span>.</li><li>Global context method <span class="term">GetExternalURL()</span>.</li><li>Global context property <span class="term">StartupURL</span>. This property contains the URL that started the client application.
</li></ul></td><td>These features were not available in the web client.</td><td>Web client URL features are now in line with the rest of the client applications.</td></tr><tr title="Версия 8.3.18" class="tag_32"><td><a name="0596601a-93b0-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>It is now easier to load configurations into Mobile Application Builder. The builder automatically determines which group to place the configuration to be loaded in.<p>You can now view properties of the used configuration directly from the built mobile application card.</p><p>For a configuration loaded into the builder, it is now possible to get a list of applications that include this configuration.</p></td><td>To load a new mobile configuration version, it was necessary to manually determine which group to load the configuration into, which was not very easy with a large list of used configurations.<p>Mobile Application Builder did not provide an easy way to get a list of applications that used any configuration. It also did not allow you to quickly view the configuration properties in the built mobile application card.</p></td><td>Managing mobile configurations in Mobile Application Builder is now more convenient.</td></tr><tr title="Версия 8.3.18" class="tag_31"><td><a name="ad0e186f-b230-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile client signature on the server is verified in accordance with the parameter value in the infobase settings. The parameter in the infobase settings is called <span class="interface">Mobile client signature verification</span>.<p>New global context methods to access the parameter value: <span class="term">GetMobileClientSignatureVerificationMethod()</span>/<span class="term">SetMobileClientSignatureVerificationMethod()</span>.</p></td><td>The mobile client signature on the server was always verified, regardless of the parameter value in the infobase settings. The parameter in the infobase settings was called <span class="interface">Mobile client signature verification on database configuration update</span>.</td><td>You can now disable useless troubleshooting if the application is not used with the mobile client and the mobile client does not require configuration signature verification.</td></tr><tr title="Версия 8.3.18" class="tag_29 tag_30 tag_31"><td><a name="56966c24-ba31-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Mobile applications built using mobile version 8.3.18.71 will meet the requirements of Google Play for new applications. The target SDK version is 30.<p>To upload a mobile application to Google Play, build a mobile application using mobile version 8.3.18.71 or later.
</p></td><td>Mobile applications built using mobile versions that are older than 8.3.18.71 could not be uploaded to Google Play after August 1, 2021.</td><td>1C:Enterprise mobile version meets the requirements of Google Play.</td></tr><tr title="Версия 8.3.18" class="tag_30 tag_31"><td><a name="4d2992e7-ba33-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New mobile version functionality: <span class="interface">Access to all data</span>. If a configuration has this functionality enabled, an Android mobile application that includes this configuration will have permission to access an arbitrary place (within the global restrictions of the operating system) in the file system of a mobile device.</td><td>Access to an arbitrary place in the file system of an Android device did not require any permission to be specified.</td><td>Improved compliance with the requirements set by Google for Android mobile applications.</td></tr><tr title="Версия 8.3.18" class="tag_70 tag_10 tag_15"><td><a name="0a4a9e77-c778-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>If 1C:Enterprise server is updated to version 8.3.20 or later and the client application update is set up via the server (any method), thin client 8.3.18 and 8.3.19 managed by Linux can be updated to version 8.3.20. To update the application, you can use not only distribution packages in <span class="interface">.deb </span>and<span class="interface"> .rpm </span>formats but also in <span class="interface">.run </span>format (implemented in version 8.3.20).</td><td>The client application managed by Linux could be updated only using distribution packages in<span class="interface"> .deb </span>and <span class="interface">.rpm </span>formats. After update to version 8.3.20, the client application could not be automatically updated to the current version.</td><td>Migration to version 8.3.20 is now as easy as migration to previous versions despite the changed file format of the distribution package.</td></tr><tr title="Версия 8.3.18" class="tag_18 tag_29"><td><a name="625d66d5-d329-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>macOS Big Sur (version 11) is now supported.<p>Under macOS Big Sur the <span class="term">SystemInformation.Processor </span>property always contains the <span class="interface">x86_64 </span>value.</p></td><td>1C:Enterprise application did not work under macOS Big Sur (version 11).</td><td>Extended list of supported macOS versions.</td></tr><tr title="Версия 8.3.18" class="tag_71"><td><a name="7288d758-f52c-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 71); return false;">Analytics system</a>.<br></td><td>To execute data queries, the analytics system uses a session pool similar to a pool processing HTTP service queries.<p>New session type: Analytics system query.</p><p>To set up the pool, use the <span class="term">analytics </span>element of the <span class="interface">default.vrd </span>file. 1C:Designer infobase publication interface does not support editing pool settings.</p></td><td>To execute data queries, the analytics system used background jobs.</td><td>Accelerated the analytics system queries to infobase data due to faster session initialization.</td></tr><tr title="Версия 8.3.18" class="tag_85"><td><a name="aa483260-fff1-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 85); return false;">Processing PDF documents</a>.<br></td><td>You can now convert a PDF document to grayscale. <p>New methods for the <span class="term">PDFWriter</span> object: <span class="term">ConvertToGrayScale()</span> and <span class="term">ConvertToGrayScaleAsync()</span>.</p></td><td>This feature was not provided.</td><td>Advanced PDF document features.</td></tr><tr title="Версия 8.3.18" class="tag_7"><td><a name="5a8efd9e-2742-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Improved performance of queries executed in a database copy.</td><td>Execution of queries in a database copy took more time.</td><td>Improved performance of queries executed in a database copy.</td></tr><tr title="Версия 8.3.18" class="tag_25 tag_62"><td><a name="3c4843b3-51e6-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>Fields of external data sources of the non-reference type received using dot syntax from another field become available in the source of available data composition settings. That means that such fields can be used in the data composition settings.</td><td>Fields of external data sources of the non-reference type received using dot syntax from another field were not available in the source of available data composition settings. That meant that such fields could not be used in the data composition settings.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.18" class="tag_19"><td><a name="c243e664-575c-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL version 10.18 (x86-64) is supported.</td><td>This version of PostgreSQL was not supported.</td><td>Extended list of supported PostgreSQL versions.</td></tr><tr title="Версия 8.3.18" class="tag_19"><td><a name="ec71551a-575c-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL version 11.13 (x86-64) is supported.</td><td>This version of PostgreSQL was not supported.</td><td>Extended list of supported PostgreSQL versions.</td></tr><tr title="Версия 8.3.18" class="tag_19"><td><a name="f6ff1229-575c-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL version 12.8 (x86-64) is supported.</td><td>This version of PostgreSQL was not supported.</td><td>Extended list of supported PostgreSQL versions.</td></tr><tr title="Версия 8.3.18" class="tag_19"><td><a name="00b8f47f-575d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL version 13.4 (x86-64) is supported.</td><td>This version of PostgreSQL was not supported.</td><td>Extended list of supported PostgreSQL versions.</td></tr><tr title="Версия 8.3.18" class="tag_19"><td><a name="0d08962b-575d-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL version 14.0 (x86-64) is supported.</td><td>This version of PostgreSQL was not supported.</td><td>Extended list of supported PostgreSQL versions.</td></tr><tr title="Версия 8.3.18" class="tag_71 tag_12"><td><a name="ebbde287-7d00-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 71); return false;">Analytics system</a>.<br><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>
<p>New features for the standard <span class="interface">"Analytics system management"</span> data processor:</p><ul><li>Support of virtual table parameters in queries to additional sources.</li><li>Operations with additional data sources.</li></ul><p>
</p></td><td>The standard <span class="interface">"Analytics system management</span>" data processor did not support virtual table parameters in queries to additional sources. For the list of additional sources, only additional source registration was available in the data processor.</td><td>The standard processor features are compliant with 1C:Enterprise features.<p>
</p></td></tr><tr title="Версия 8.3.18" class="tag_29"><td><a name="e561b61e-7d03-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Minimum system requirements are specified for platform components:<ul><li>CD reader is excluded from the list of system requirements.</li><li>Installation requires from 350 MB to 1 GB of disk space (depending on the application to be installed).</li><li>Chromium-gost - version 64 or later.</li><li>Google Chrome - version 64 or later.</li></ul><p>The user can now read in the documentation about recommended hardware to select an optimal hardware configuration.</p></td><td>Minimum system requirements for platform components were as follows:<ul><li>CD reader support was required.</li><li>Installation required from 250 MB to 800 MB of disk space (depending on the application to be installed).</li><li>Chromium-gost - version 49 or later.</li><li>Google Chrome - version 49 or later.</li></ul></td><td>Specified some system requirements.<p>
</p></td></tr><tr title="Версия 8.3.18" class="tag_29 tag_19"><td><a name="19cbf889-7d0a-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS of the following versions (only for x86-64):<ul><li>Postgres Pro 1C 12.9.1</li><li>Postgres Pro 1C 13.5.1</li><li>Postgres Pro 1C 14.1.1</li><li>Postgres Pro Standard 12.9.1</li><li>Postgres Pro Standard 13.5.1</li><li>Postgres Pro Standard 14.1.1</li><li>Postgres Pro Enterprise 12.9.1</li><li>Postgres Pro Enterprise 13.5.1</li><li>Postgres Pro Enterprise 14.1.1</li></ul></td><td>These DBMS versions were not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.18" class="tag_19 tag_29"><td><a name="9bbc7400-82c2-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>PostgreSQL 15 is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>Extended list of supported PostgreSQL DBMS versions.</td></tr><tr title="Версия 8.3.18" class="tag_37"><td><a name="3ebd7631-fbce-11ee-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>1C:Enterprise now supports the TLS 1.3 protocol. When using the TLS 1.3 protocol, client certificates are not supported.<p>New parameters for the <span class="interface">conf.cfg </span>configuration file: <span class="term">ForceTLS1_1</span> and <span class="term">ForceTLS1_2</span>. These parameters allow you to specify the maximum version of the used TLS protocol.</p><p>New commands for the client application startup command line: <span class="term">/HttpsForceTLS1_1</span> and <span class="term">/HttpsForceTLS1_2</span>. These commands allow you to specify the maximum used version of the TLS protocol when accessing the web server over HTTPS.</p></td><td>Previously, 1C:Enterprise did not support the TLS 1.3 protocol.</td><td>Increased security of the connection established by the client application when running over the Internet.</td></tr></table><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="cfd0a004-5899-11ea-8371-0050569f678a">Transition from the previous version to the version 8.3.18</a></h2><ul><li title="Версия 8.3.18" class="tag_0"><a name="cfd0a005-5899-11ea-8371-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.18.
</li><li title="Версия 8.3.18" class="tag_0"><a name="cfd0a006-5899-11ea-8371-0050569f678a"></a>Some features that are added in version 8.3.18 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.18" class="tag_0"><a name="01ee1836-12d3-11eb-8371-0050569f678a"></a>We recommend that you clear the full-text search index and build it again if the full-text search index size exceeds 50 Gb.</li></ul><p><a href="#cfd09ff9-5899-11ea-8371-0050569f678a"><small>Table of contents</small></a></p><h1><a name="9f36892b-eb6c-11e9-8371-0050569f678a">Version 8.3.17</a></h1><p title="Версия 8.3.17" class="tag_0"><a name="9f368939-eb6c-11e9-8371-0050569f678a"></a>Version 8.3.17 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.17" class="tag_0"><a name="0f292fb0-73fd-11ea-8371-0050569f678a"></a>Thick client and Designer for macOS are out of beta.</p><p title="Версия 8.3.17" class="tag_0"><a name="120765df-8ea1-11ea-8371-0050569f678a"></a>Data Accelerator and database copy features now require a CORP license.<p>The feature testing license now does not provide access to the Data Accelerator and database copy features.</p></p><p title="Версия 8.3.17" class="tag_0"><a name="3954c610-8eaa-11ea-8371-0050569f678a"></a>Added a beta testing server license for 1C:Analytics. It provides access to the 1C:Analytics, Data Accelerator, and database copy features.</p><p title="Версия 8.3.17" class="tag_0"><a name="ead875c6-9865-11eb-8371-0050569f678a"></a>New feature: license to start 1C:Analytics client. The number of concurrent sessions of 1C:Analytics client are determined by the license value. The license to start 1C:Analytics client can be PROF or CORP.<p>The license to start 1C:Analytics client is installed on a computer with 1C:Enterprise server cluster and allows you to:</p><ul><li>Start 1C:Analytics client sessions.</li><li>Start Data Accelerator.</li><li>Use the database copy mechanism with Data Accelerator.</li></ul></p><hr></hr><ul><li><a href="#9f36892c-eb6c-11e9-8371-0050569f678a">New functionality and changes</a></li><li><a href="#9f36892d-eb6c-11e9-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#9f36892e-eb6c-11e9-8371-0050569f678a">Optimization</a></li><li><a href="#9f36892f-eb6c-11e9-8371-0050569f678a">Changes that affect system behavior</a></li><li><a href="#9f368930-eb6c-11e9-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#9f368931-eb6c-11e9-8371-0050569f678a">Renamed objects</a></li><li><a href="#9f368932-eb6c-11e9-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#9f368933-eb6c-11e9-8371-0050569f678a">Library updates
</a></li><li><a href="#9f368934-eb6c-11e9-8371-0050569f678a">Demo configuration changes</a></li><li><a href="#9f368935-eb6c-11e9-8371-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#9f368936-eb6c-11e9-8371-0050569f678a">Transition from the previous version to the version 8.3.17</a></li></ul><h2><a name="9f36892c-eb6c-11e9-8371-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.17" class="compat tag_2 tag_1"><td><a name="2e4674b7-eb6d-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.16</span> is now implemented.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.15 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.16 or earlier can now run on version 8.3.17 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.17 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.16 after the migration to version 8.3.17, even if you disable the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.17" class="compat tag_64 tag_1"><td><a name="014f0732-f0c8-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New pictures were added to the picture library:<ul><li><span class="term">Zoom</span>.</li><li><span class="term">Parameters</span>.</li><li><span class="term">Information</span>.</li><li><span class="term">FunctionMenuCommand</span>.</li><li><span class="term">Favorites</span>.</li><li><span class="term">Settings</span>.</li><li><span class="term">Message</span>.</li><li><span class="term">GroupConversation</span>.</li><li><span class="term">CollaborationSystemUser</span>.</li><li><span class="term">SearchForData</span>..</li><li><span class="term">GotoExternalNavigationLink</span>.</li><li><span class="term">Calendar</span>. <span class="term">CalendarInputField</span> picture is used in version 8.3.16 compatibility mode.</li><li><span class="term">Calculator</span>. <span class="term">CalculatorInputField</span> picture is used in version 8.3.16 compatibility mode.</li><li><span class="term">Help</span>. <span class="term">FormHelp</span> picture is used in version 8.3.16 compatibility mode.</li><li><span class="term">CollaborationSystemIntegrationUser</span>,</li><li><span class="term">OpenFromMainServer</span>,</li><li><span class="term">OpenFromStandaloneServer</span>.</li></ul><p><span class="term">Conversations</span> image was updated.</p></td><td>The listed pictures were not available in the picture library.</td><td>The picture library is upgraded.</td></tr><tr title="Версия 8.3.17" class="tag_53"><td><a name="27f2dc70-f0cf-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>The following features related to the application running error processing were implemented:<ul><li>Processing of all non-trapped errors that occur during the application running before displaying errors to the user.</li><li><span class="term">ErrorDisplayProcessing</span> application module handler was implemented.</li><li>Declarative configuring of error message texts is now available.</li><li>You can now generate and send error reports to technical support team (inter alia in default mode). <span class="term">ErrorReport</span> object was implemented.</li><li>An 'error category' concept is supported, which enables you to group errors. <span class="term">ErrorInfo.IsErrorOfCategory()</span> method is available.</li><li>The standard window to display errors was modified.</li></ul><p><span class="term">ErrorProcessing</span> global context property was implemented.
<span class="interface">Error Processing Settings Management</span> standard function is now available, which allows you to configure error texts.
<span class="term">BriefErrorDescription()</span>, <span class="term">DetailErrorDescription()</span>, and <span class="term">ShowErrorInfo()</span> global context methods are deprecated. It is recommended to use the similar methods of the <span class="term">ErrorProcessing</span> object.
When running Linux, the <span class="interface">libunwind</span> library is used to get the application stack when an error occurs.</p></td><td>These features were not provided.
Local processing of recoverable errors was available only.</td><td>You can now make error texts easier to understand by end users.
Error processing in 1C:Enterprise language was improved.</td></tr><tr title="Версия 8.3.17" class="compat tag_6 tag_14 tag_1"><td><a name="0411e90c-f0e7-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>When in the client/server mode, you can by default delete temporary files created using <span class="term">GetTemporaryFileName() </span>method on the side of the PC(s) running the server cluster in the following scenarios:<ul><li>20 minutes after the end of a session when a temporary file is created.</li><li>20 minutes after the end of a server call when a temporary file was created. This feature is not available in the 8.3.16 and earlier compatibility mode.</li></ul><p>Temporary files are deleted as soon as you start 1C:Enterprise processes (client applications, server cluster processes) without delaying the start.</p></td><td>Temporary files were only deleted when the 1C:Enterprise processes were started. The system startup speed depended on the number of temporary files to be deleted.</td><td>1C:Enterprise processes performance is improved, if there is a large number of temporary files generated by 1C:Enterprise itself.<p>The risk of running out of space on the hard drivers where the temporary file directories are located is mitigated during prolonged operation without restarting and inaccurate application handling of the temporary files being created.</p><p>The number of simultaneously existing temporary files with names that were obtained using <span class="term">GetTemporaryFileName()</span> method was reduced.</p></td></tr><tr title="Версия 8.3.17" class="tag_4"><td><a name="6f3d7e1c-f57c-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Integration with external (with respect to the collaboration system) instant messaging systems was implemented for the collaboration system. Interaction with the following systems is now supported: Telegram, VKontakte.<p><span class="term">CollaborationSystemIntegration</span> object is supported. <span class="term">CreateIntegration()</span>, <span class="term">GetIntegration()</span>, <span class="term">GetIntegrations()</span>, <span class="term">GetExternalSystemTypes()</span> and <span class="term">GetExternalSystemDescription()</span> methods were implemented for <span class="term">CollaborationSystemManager </span>object.</p><p><span class="term">CollaborationSystemUser</span>.<span class="term">ExternalSystemType</span>, <span class="term">CollaborationSystemUser</span>.<span class="term">ExternalSystemUserID</span>, <span class="term">CollaborationSystemConversion</span>.<span class="term">Integration </span>and <span class="term">CollaborationSystemConversationFilter</span>.<span class="term">Integration </span>properties were implemented.</p></td><td>This feature was not provided.</td><td>Expanded collaboration system capabilities.</td></tr><tr title="Версия 8.3.17" class="tag_38"><td><a name="9c304521-f583-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>You can now borrow event subscriptions and create your own subscriptions in the extension.</td><td>This feature was not provided.</td><td>Extended configuration extension options.</td></tr><tr title="Версия 8.3.17" class="tag_14 tag_64 tag_29"><td><a name="6c919e93-f585-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>You can save a spreadsheet document in Microsoft Excel 97 format in a client application running macOS. In Linux, to save in Microsoft Excel 97, use <span class="interface">libgsf-v8</span> library included in 1C:Enterprise platform distribution package. Thus, <span class="interface">libgsf-1</span> and <span class="interface">libglib-2.0</span> libraries are no longer required.<p>You cannot save a spreadsheet document in Microsoft Excel 95 format in Linux and macOS.</p></td><td>You could save a spreadsheet document in Microsoft Excel 97 format in Linux only.<p>Nominally, you were able to save a spreadsheet document in Microsoft Excel 95 format in Linux and macOS. However, in practice this feature was unavailable.</p></td><td>Users of client applications running macOS can now save spreadsheet documents in Microsoft Excel 97 format.</td></tr><tr title="Версия 8.3.17" class="tag_20"><td><a name="f6527e41-f58f-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>A technical specialist mode is implemented for a managed client application. The following features are available in this mode for managed forms:<ul><li>You are able to retrieve the full form name displayed in this window using <span class="interface">Information for Technical Specialist </span>command in the form header context menu and form menu.</li><li>You can open the current configuration object in Designer using <span class="interface">Open in Designer </span>command in the form header context menu and form menu. This feature is only available, if the client application is running in debug mode.</li></ul></td><td>This feature was not provided.<p>It was difficult to determine which form is currently used in the client application.</p></td><td>Technical specialists operations as part of application development or deployment process were made easier.</td></tr><tr title="Версия 8.3.17" class="tag_36"><td><a name="6485437a-fb18-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>You now can identify IP-address of a PC, where an infobase user session was started. IP-address cannot be determined in every instance and in every mode of operation.<p><span class="term">ClientIPAddress </span>property was implemented for <span class="term">AdministrationSession</span> and <span class="term">InfobaseSession</span> objects.</p><p>Now, IP-address of a client application can be displayed in the cluster console and standard server management processor.</p><p><span class="term">ISessionInfo.getClientIPAddress() </span>property is now available in the administration server interface in Java language.</p><p><span class="term">Client-ip </span>field is now available in the command-line utility (<span class="interface">rac</span>) of a server cluster. It displays values returned by<span class="term"> session info </span>command..</p><p><span class="term">SessionNumber</span> and <span class="term">ClientIPAddress</span> parameters are now available for the onStartSession() method of external session management Web-service. New features are only available, if <span class="term">wsver</span> is assigned 3.</p></td><td>This feature was not provided.</td><td>You now can identify IP-address of a PC, where an infobase user session was started.</td></tr><tr title="Версия 8.3.17" class="tag_71"><td><a name="33487d51-11c7-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 71); return false;">Analytics system</a>.<br></td><td>1C:Enterprise is now integrated with 1C:Analytics (analytics system).<p>In the publishing settings on the Web server, you can enable analytics system publication.</p><p>In the <span class="interface">Service and Settings </span>menu, <span class="interface">Analytics System </span>command is now supported, thus allowing you to open a tab with analytics system in the web browser for the current user.</p><p><span class="interface">Standard Analytics System Management </span>function is supported to integrate it with the infobase.</p><p>So far as global context is concerned, <span class="term">AnalyticsSystem</span> property is available. <span class="term">AnalyticsSystemClient</span> access rights are supported.</p><p>1C:Analytics is not included in distribution package. Information on this functionality is published separately.
</p></td><td>This feature was not provided.</td><td>1C:Enterprise is now integrated with 1C:Analytics (analytics system).</td></tr><tr title="Версия 8.3.17" class="tag_25"><td><a name="19110485-11e0-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>You can pass temporary tables manager to data composition system. In the data composition system, you can use tables that do not exist in the infobase similarly with temporary tables in the query language.<p>The <span class="term">TempTablesManager </span>parameter is now available for the <span class="term">DataCompositionProcessor.Initialize() </span>method.</p></td><td>This feature was not provided. You were able to use temporary tables in the data composition system only as part of a batch query.</td><td>Now, you can use pre-defined temporary tables, when a query is executed by the data composition processor.</td></tr><tr title="Версия 8.3.17" class="compat tag_26 tag_63 tag_1"><td><a name="0342853f-1504-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Now, you can manage the way an image selection box is displayed in a spreadsheet document in a client application form.
To expand the form field boundaries, <span class="term">DrawingsSelectionView </span>property is supported for spreadsheet fields.<p>This upgrade is ignored in 8.3.13 version compatibility mode.
</p></td><td>This feature was not provided.<p>When you selected a chart in a spreadsheet document available in the client application form, the said chart was always highlighted.</p></td><td>Now, it is much more easier to use charts in a spreadsheet document available in the form.</td></tr><tr title="Версия 8.3.17" class="tag_64 tag_109"><td><a name="3aa949da-1678-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 109); return false;">Сlient application form</a>.<br></td><td>Nested dimension items can be created and text in background bands displayed in the Planner.<p>The <span class="term">PlannerDimensionItem</span> object now supports <span class="term">Items</span>, <span class="term">Parent</span>, and <span class="term">ShowItemsAreaOnlyForSubordinateItems</span> properties.</p><p>The <span class="term">PlannerDimensionItemsCollection.Find() </span>method now supports <span class="term">IncludeSubordinates</span> parameter.</p><p>To expand the form field, planner filed supports the following:</p><ul><li><span class="term">CollapseDimensionItem()</span>, <span class="term">ExpandDimensionItem()</span>, and <span class="term">DimensionItemExpanded()</span> methods.</li><li><span class="term">BeforeExpa</span><span class="term">ndDimensionItem</span> and <span class="term">BeforeCollapseDimensionItem</span> events.</li></ul><p>
Text parameter is available for <span class="term">Add()</span> and <span class="term">Insert()</span> methods (<span class="term">PlannerDimensionCollection</span> and <span class="term">PlannerDimensionItemCollection</span> objects). When you use this parameter, it is recommended to specify its value to avoid server calls getting presentations.</p></td><td>These features were not provided.</td><td>Now, you can implement a group of planner dimension items similarly to a group of spreadsheet or hierarchical catalog lines.</td></tr><tr title="Версия 8.3.17" class="tag_19 tag_29"><td><a name="28638596-2569-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following Oracle Database DBMS versions are supported now:<ul><li>12.2</li><li>18c</li><li>19c</li></ul></td><td>These Oracle Database DBMS versions were not supported.</td><td>Extended list of supported Oracle Database DBMS versions.</td></tr><tr title="Версия 8.3.17" class="tag_46"><td><a name="d573542d-223f-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br></td><td>Integration service creating feature was implemented. Integration services allow to coordinate with the "External integration service" product.
The <span class="term">IntegrationServices</span> property of 1C:Enterprise language was implemented.
Managing integration services was implemented in standard functions.
"External Integration Service" is not included in distribution package. Information on this functionality is published separately.
To use integration services, a license to test dedicated functionality is required. The integration services will not be available without a license to test the dedicated functionality.
</td><td>This feature was not provided.
</td><td>Interaction with "External Integration Service” was implemented.</td></tr><tr title="Версия 8.3.17" class="tag_28"><td><a name="338643f9-2237-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Language support with spelling from right to left is implemented for the web client. This mode is supported automatically in the entire client application interface, with the exception of the following form elements: planner, chart, Gantt chart, dendrogram, graphical schema field and graphical schema field. The requirement to change the interface is determined by the interface language or configuration language. The web client now supports Arabic formats for numbers and dates.<p>When calculating the arrangement of form elements and other interface items, the default font is Almarai.</p><p>The web client supports using specialized Arabic characters for writing arithmetic expressions. In such cases, the expressions are calculated correctly.</p></td><td>The web client did not support using of languages with right-to-left spelling.</td><td>It has become possible to use 1C: Enterprise (using a web client) in countries where the national language uses right-to-left spelling.</td></tr></table><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f36892d-eb6c-11e9-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.17" class="tag_28 tag_78"><td><a name="4d0815fa-fbdf-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>As soon as you open an external report or data processor file on a web client (without a file system extension installed), there is no need to reopen the selected file after positive feedback to security warning.<p>In a file opening dialog box on a web client, now you can select a filter to search files you need to open (if it is defined, when you open a dialog box).</p></td><td>As soon as you opened an external report or data processor file on a web client (without a file system extension installed), you needed to reopen the selected file after positive feedback to security warning.<p>In a file opening dialog box on a web client, there was no option to define a filter to search files.</p></td><td>Now, you can open an external report or data processor on a web-client (without a file system extension installed) in a easier and user-friendly way.<p>Moreover, it's much more easier to open other files on a web client now.</p></td></tr><tr title="Версия 8.3.17" class="tag_64"><td><a name="3fd67256-fbe4-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Some platform images (including part of image library) now have different appearance (they were redrawn) and are now implemented in SVG format.<p>In the <span class="interface">Taxi </span>interface windows appearance was modified. They are now generated by <span class="term">ShowUserNotification()</span> and <span class="term">State()</span> global context methods.</p></td><td>Some platform images (including part of image library) had different appearance, and they were implemented in PNG format.<p>Appearance of windows generated in Taxi interface using <span class="term">ShowUserNotification()</span> and <span class="term">State()</span> global context methods was different.</p></td><td>Visual perception of 1C:Enterprise interface was improved.</td></tr><tr title="Версия 8.3.17" class="tag_53"><td><a name="9e857468-fbe4-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>As soon as you open a dialog box with information for technical support team, the entire text available in the input field is selected by default.</td><td>When you opened a dialog box with information for technical support team, text available in the input field was not selected.</td><td>Now, you can copy information for technical support team (if necessary) easier and without delay.</td></tr><tr title="Версия 8.3.17" class="tag_54 tag_14 tag_28"><td><a name="684e5b63-10f9-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 54); return false;">Global search</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The following global search commands are available:<ul><li><span class="interface">Help</span>: you can open Help section in the client application for the current context.</li><li><span class="interface">Help</span> Content: you can open content of client application help section.</li></ul><p>
<span class="interface">Search Everywhere </span>context menu command is available, only if a pointer is set on a word or you selected a text block. If no text block is selected, and a pointer is on a word, search is made using the said word or URL (whenever a pointer is placed on URL).</p><p>In <span class="interface">Search Everywhere </span>command presentation in the menu a text block is added which will be searched, whenever you use this command.</p><p>Whenever you use Safari browser on a web client, click the right mouse button in the input field, formated or text document to select the entire word with a pointer placed thereon (without further analysis of that word).</p><p>Whenever you use a thin, thick or web client (other than Mozilla Firefox and Safari browsers), click the right mouse button in the input field to place a pointer in a position where the button was clicked.</p></td><td><span class="interface">Search Everywhere </span>context menu command was available, only if there was a selected text block in the current form element. Search was made by the text block so selected.<p>No text block so searched was added to <span class="interface">Search Everywhere </span>command presentation in the menu.</p></td><td>Global search usage was improved.</td></tr><tr title="Версия 8.3.17" class="tag_28 tag_26"><td><a name="224c6624-10ff-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The display of a spreadsheet document containing patterns in cells was optimized when using a web client in case of a slow connection. When saving a spreadsheet document containing patterns in cells in HTML format, the size of resulting HTML document was reduced.
</td><td>Displaying a spreadsheet document containing patterns in cells took longer when using a web client in case of a slow connection.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_21 tag_12"><td><a name="7a980ad0-1104-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>So far as standard full-text search management function is concerned, you can check the current full-text search index for accuracy.<p>Before you clear the current full-text search index, a warning is displayed notifying that you can abandon this procedure.
</p></td><td>So far as standard full-text search management function was concerned, the current full-text search index was unavailable for accuracy verification.<p>The current full-text search index was cleared with a prior warning on an unconditional basis.</p></td><td>Capabilities supported by the standard full-text search management function were expanded.<p>Now, it is more difficult to clear full-text search index.</p></td></tr><tr title="Версия 8.3.17" class="tag_28"><td><a name="bd1be69c-14e8-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The browser extension installation process was simplified (for Google Chrome and Mozilla Firefox browsers). The said extension is required to use file system, cryptography and add-in extensions. As soon as you install an extension for Google Chrome web browser, there is no need to restart your web client any more.</td><td>The browser extension installation process was complicated (for Google Chrome and Mozilla Firefox browsers). The said extension was required to use file system, cryptography and add-in extensions. As soon as you installed an extension for Google Chrome web browser, you needed to restart your web client.</td><td>Now, the web browser extension installation process is much more easier and user-friendly.</td></tr><tr title="Версия 8.3.17" class="tag_4"><td><a name="8fb20a40-15d0-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The collaboration system interface was modified as follows:<ul><li>Now, you can change the size of the message input field in the context conversation.</li><li>User pictures can be displayed in the dialog box where you can create conversations and users added to non-context conversations.</li><li>Any user participating in a non-context conversation can be deleted by any other user.</li><li>Message recipients can be defined for a non-context conversation.</li><li>So far as a non-context conversation is concerned, a list of recipients is generated similarly to that applicable to context conversation (including but not limited to, by way of calling all data processors). <span class="interface">No Notification </span>option is unavailable in the user list.</li><li>So far as messages sent to several users are concerned, you can press either <span class="interface">Reply </span>or <span class="interface">Reply All </span>button (displayed as icons).</li><li>Moreover, you can reply to your own message. As such, a list of notified users specifies those defined for the original message.</li><li>If so far as a non-context message is concerned the current user is unavailable in the list of users, no notice is sent thereto whenever the said message is received.</li><li>You can view attachments in the messages you create.</li></ul></td><td>Previously, the collaboration system interface was different.</td><td>Now, it is much more easier to use the collaboration system.</td></tr><tr title="Версия 8.3.17" class="tag_12"><td><a name="bcc192d0-2238-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>The button for accepting changes is always available, and not only after changing the parameters in the dialog box for configuring full-text search parameters of full-text search standard processing management. The button itself is called <span class="interface">OK</span>.</td><td>The button for accepting the changes was only available after changing any parameter in the dialog box for configuring full-text search parameters of full-text search standard processing management. The button itself was called <span class="interface">Set</span>.</td><td>The interface of the parameter setting dialog box has been brought to the standard accepted in the platform.</td></tr></table><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f36892e-eb6c-11e9-8371-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.17" class="tag_109"><td><a name="e09ad7ce-f0c3-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 109); return false;">Сlient application form</a>.<br></td><td>Removal of rows from tables displayed in the client application form was optimized.</td><td>Previously, removal of rows from tables displayed in the client application form took more time.</td><td>Client application operation when rows are removed from the form table was improved.</td></tr><tr title="Версия 8.3.17" class="tag_39"><td><a name="62486f79-f581-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>You can index event log files. Indexing is performed in the background. Indexes are stored in .<span class="interface">lgx</span> files in <span class="interface">1Cv8Log</span> directory. Algorithms for sequential reading of event log files were optimized.<p>No additional settings are required to enable indexing. Due to indexing, filtering of event log entries by indexed fields was significantly accelerated.</p><p>When another infobase event log file is opened in Designer, indexing of this file is performed in the background and the index file is deleted after the work with the event log being viewed is finished.</p><p><span class="interface">Separate Log Storage by Periods </span>is set to <span class="interface">Week</span> for a new infobase. It is recommended to set separation for existing infobases, so that the size of a single log file is max 100 MB.</p><p>Event logs created in the 1C:Enterprise of version 8.0 and 8.1 are no longer supported.</p></td><td>This feature was not provided.<p>No event log files indexing was performed. Filtering of entries in event log files took a very long time, so far as large event log files were concerned.</p></td><td>Operations with event logs were accelerated.</td></tr><tr title="Версия 8.3.17" class="tag_110 tag_6"><td><a name="1ba6e7b9-f582-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When using the client/server mode, starting of the first session is accelerated to access the infobase, the configuration of which contains a large number of roles.
</td><td>When using the client/server mode, starting of the first session to access the infobase, the configuration of which contained a large number of roles, took more time.</td><td>The time for server cluster inaccessibility for users during the working processes restart is reduced, and the start time of the first session for each infobase in working process is also decreased.
</td></tr><tr title="Версия 8.3.17" class="tag_6"><td><a name="55a59ddd-f586-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When using the client/server mode, starting of the first session to access the infobase is accelerated. Acceleration is especially noticeable for configurations containing a large amount of metadata.</td><td>When using the client/server mode, starting of the first session to access the infobase took more time.</td><td>The time for server cluster inaccessibility for users during the working processes restart is reduced, and the start time of the first session for each infobase in working process is also decreased.</td></tr><tr title="Версия 8.3.17" class="tag_36"><td><a name="89935b03-f587-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>Accelerated solution of some systems of linear algebraic equations is enabled.<p><span class="term">AllowGraphReduction </span>parameter is implemented for <span class="term">SolvingLinearEquationSystems</span>.<span class="term">SolveLinearEquationSystems()</span> method, which allows to control the calculation algorithm. <span class="term">SolvingLinearEquationSystems</span>.<span class="term">GetGraphDepth()</span> method is implemented to allow making the decision on <span class="term">AllowGraphReduction </span>parameter value.</p></td><td>1C:Enterprise showed insufficient search speed for solutions of some linear algebraic equations systems.</td><td>A finer customization of behavior of a tool designed to solve linear algebraic equations systems was implemented.</td></tr><tr title="Версия 8.3.17" class="tag_45"><td><a name="53c57f64-fbea-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Comparison of composite type with non-composite type was improved, provided that the latter can be <span class="term">NULL </span>and a query includes temporary tables.<p>The following operations were optimized:</p><ul><li><span class="term">A = B</span> comparison, where <span class="term">A</span> is composite type and <span class="term">B </span>is simple type which can be <span class="term">NULL</span>.</li><li><span class="term">ISNULL </span><span class="term">(A,B) = C</span> comparison, where <span class="term">A</span> is simple type and can be <span class="term">NULL</span>, while<span class="term"> C</span> is composite type.</li><li>Comparison of <span class="term">Expression</span><span class="term">1 IN</span><span class="term"> (SELECT ...)</span> and <span class="term">Expression</span><span class="term">1 IN</span><span class="term"> (List of Values), </span>where <span class="term">Expression</span><span class="term">1 </span>is a field with references to two or more tables. However, you need to procure that a subquery selection list or list of values has references to various tables and no <span class="term">Undefined </span>values are available therein.</li></ul><p>Optimization is feasible, whenever it has no impact on the query results. Optimization can contribute to query plan improvement and reduction of time required to compile a query.</p></td><td>Comparison of composite type with non-composite type, whenever the latter can be <span class="term">NULL </span>and query had temporary tables, resulted in generation of complex queries which eventually can trigger runtime errors and generate non-optimal query plans.</td><td>In some scenarios, query performance was improved.</td></tr><tr title="Версия 8.3.17" class="tag_45 tag_19 tag_6"><td><a name="f0fae804-fbed-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>If comparison with an empty link returned as a parameter is made in a query, DBMS receives a query, where a parameter is replaced with a constant. Optimization is feasible, if a server cluster supports such DBMS as IBM DB2, Microsoft SQL Server or Oracle Database.</td><td>If comparison with an empty link returned as a parameter was made in a query, no replacement of a parameter with a constant was effected. </td><td>DBMS can select a more efficient query execution plan, whenever comparison with empty links returned as parameters is made in a query.</td></tr><tr title="Версия 8.3.17" class="tag_19"><td><a name="72b0bd76-11b9-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>So far as use of infobase in file mode is concerned, execution of a query with several B conditions which use indexes was largely improved.<p>However, in some scenarios insignificantly decelerated execution of such queries is possible.</p></td><td>So far as use of infobase in file mode is concerned, execution of a query with several B conditions which used indexes was non-optimal.</td><td>Execution of some queries in infobase file mode was accelerated.</td></tr></table><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f36892f-eb6c-11e9-8371-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.17" class="tag_25"><td><a name="ce5676de-f0c6-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When reading report, dynamic lists and conditional appearance settings, missing style elements do not cause an error, but are replaced with default values of the corresponding type.</td><td>When reading report, dynamic lists and conditional appearance settings, missing style elements caused an error and no application of such settings was possible.</td><td>If a style element is used as the appearance parameter value in any report, dynamic list, form conditional appearance settings, the entire settings object will not be lost and the remaining settings will be applied if this element is unavailable for reading as a result of deleting/renaming or applying settings on the previous platform version. Appearance options containing invalid values will also be applied, but using default values.</td></tr><tr title="Версия 8.3.17" class="tag_28"><td><a name="522f26ca-f0e7-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Web client reliability is improved.</td><td>Web client operation was characterized by lower reliability.</td><td>Web client reliability is improved.</td></tr><tr title="Версия 8.3.17" class="tag_20"><td><a name="e7873e43-f585-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>If halt on error during debugging is enabled, the error text is displayed both in the dialog box and in the message window. This also allows you to go to exception from the message window.
</td><td>This feature was not provided.<p>An error message was only displayed in a dialog box with error details.</p></td><td>It is now much more easier to use debugger when halt on error is enabled.</td></tr><tr title="Версия 8.3.17" class="tag_20"><td><a name="e1eba073-f595-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The following control features were implemented when a report on the configuration repository versions is generated:<ul><li>Managing a date range used to generate a report.</li><li>Including and excluding tagged versions from the report.</li><li>Displaying comments in the report starting with (//).</li><li>Specifying a configuration version to display related repository changes.</li><li>Managing a repository report format.</li></ul><p><span class="term">DateBegin</span>, <span class="term">DateEnd</span>, <span class="term">DoNotIncludeVersionsWithLabel</span>, <span class="term">IncludeOnlyVersionsWithLabel</span>, <span class="term">IncludeCommentLineWithDoubleSlash</span>, <span class="term">ConfigurationVersion</span> and <span class="term">ReportFormat</span> parameters were implemented for <span class="term">ConfigurationRepositoryReport</span> Designer batch run command.</p></td><td>These features were not provided.</td><td>A list of features designed to manage repository reports in Designer batch run mode was expanded.</td></tr><tr title="Версия 8.3.17" class="tag_4 tag_15"><td><a name="b8753991-f596-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>After installing <span class="interface">1C:Enterprise - Notifications and Startup </span>application (in Linux), a shortcut is created on the desktop to launch this application. The shortcut refers to the <span class="interface">Finance </span>subcategory of the <span class="interface">Office </span>category.</td><td><span class="interface">In</span> Linux, you were able to start <span class="interface">1C:Enterprise - Notifications and </span><span class="interface">Startup</span> application from <span class="interface">~/bin/1cecla</span> directory only.</td><td>Now, it became easier for Linux users to find and run <span class="interface">1C:Enterprise - Notifications and Startup</span> application.</td></tr><tr title="Версия 8.3.17" class="tag_28 tag_78"><td><a name="2310e3ac-fbcc-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>Whenever you use <span class="term">BeginPutFileToServer()</span> and <span class="term">BeginPutFilesToServer()</span> methods on the web client (without a file system extension), <span class="term">PutFilesDialogParameters</span> is used, and in the file opening dialog box you can now select one of the filters defined when you created <span class="term">PutFilesDialogParameters</span> object.<p>When you create <span class="term">PutFilesDialogParameters</span> object, you can now define filter by default to be used when a file selection dialog box is opened.</p></td><td>Whenever you used <span class="term">BeginPutFileToServer()</span> and <span class="term">BeginPutFilesToServer()</span> methods on the web client (without a file system extension), <span class="term">PutFilesDialogParameters</span> was used, and in the file opening dialog box you were unable to select a filter in the file opening dialog box.</td><td>If there is now file system extension on the web client, it's easier to select files for further processing by application.</td></tr><tr title="Версия 8.3.17" class="tag_8"><td><a name="9ec44524-fbe2-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>Values of properties starting from <span class="term">OID </span>prefix which are based on <span class="term">Subject</span> and <span class="term">Publisher</span> properties of <span class="term">CryptoCertificate</span> have the maximum length of 2,048 bytes.</td><td>Values of properties starting from <span class="term">OID</span> prefix which were based on <span class="term">Subject</span> and <span class="term">Publisher</span> properties of <span class="term">CryptoCertificate</span> object had the maximum length of 128 bytes.</td><td>Eliminated unexpected system behavior .<p>
</p></td></tr><tr title="Версия 8.3.17" class="tag_54"><td><a name="dd3b33c0-10fc-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 54); return false;">Global search</a>.<br></td><td><span class="term">GlobalSearchResultItem</span> object cannot be created on the basis of the following standard global search kinds: <span class="term">GlobalStandardCommands</span> and <span class="term">FunctionsForTechnical</span><span class="term">Specialist</span>.</td><td>You were able to create <span class="term">GlobalSearchResultItem</span> object on the basis of the following standard global search kinds: <span class="term">GlobalStandardCommands</span> and <span class="term">FunctionsforTechnicalSpecialist</span>, so that eventually incorrect data upon global search result processing was returned.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_43"><td><a name="6663c9b5-10fe-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>If the dynamic list settings form contains changed settings, then when attempting to close this form, the user will be warned about the changed settings and will be prompted to save the changed settings.<p>The <span class="term">UserSettingsModified </span>and <span class="term">SettingsModified </span>properties are implemented to expand the client application form for the settings composer. The standard processing of the settings composer form analyzes the flag of settings modification and prompts to save the settings, if necessary.</p></td><td>If the dynamic list settings form contains changed settings, when attempting to close this form, the form was closed without any warnings.</td><td>Likelihood of losing work results by changing dynamic list settings was reduced.</td></tr><tr title="Версия 8.3.17" class="compat tag_56 tag_1"><td><a name="a777b9ce-1102-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>When exporting an XDTO package to an XML schema, the default value (or fixed value) for properties with an "Element" presentation option is exported in the same way as it is for properties with an "Attribute" presentation option.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>When exporting an XDTO package to an XML schema, the default value (or fixed value) for properties with an "Element" presentation option was not exported.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_26"><td><a name="4a8948d4-111d-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Whenever you convert a spreadsheet document into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format, cells which contain tab characters or text starting with whitespace can now be created easier.</td><td>Whenever you converted a spreadsheet document into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format, cells which contained tab characters or text starting with whitespace were created in a way, when the resulting document was visually different from the original one.</td><td>Now you have less visual differences between the original spreadsheet document displayed in 1C:Enterprise and that created by way of conversion thereof into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format.</td></tr><tr title="Версия 8.3.17" class="compat tag_45 tag_1"><td><a name="49f1c30c-11bf-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If the temporary table is generated based on the table of values, a runtime error will be generated if a column with an unspecified type is present in the table of values and this column is included in the temporary table. An error will also occur if a non-typed column is involved in any expression (for example, <span class="term">SELECT </span>or <span class="term">ISNULL</span>).<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>If a temporary table is formed based on a table of values where a column with an unspecified type is present and this column is included in a temporary table, no runtime errors were generated, but the query result could be incorrect.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_4 tag_28"><td><a name="e7e6364a-14ea-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Screen translation in the collaboration system running on a web client:<p>
</p><ul><li>Google Chrome browser:</li></ul><p>
</p><ul><li>Mozilla Firefox browser:</li><p>
</p></ul></td><td>Screen translation in the collaboration system running on a web client:<ul><li>Google Chrome browser:</li><li>Mozilla Firefox browser:</li></ul></td><td>The screen translation tool is improved, so far as the collaboration system runs on the web client.</td></tr><tr title="Версия 8.3.17" class="compat tag_10 tag_1"><td><a name="22b5e05e-14ed-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>In<span class="interface"> Version 8.3.10 </span>and later compatibility mode, <span class="term">GetDataBaseStorageStructure()</span> function returns a table of values where the <span class="term">Indexes </span>column contains short index names. At the same time, the names of indexes are displayed identically for any DBMS.</td><td>In the <span class="term">Indexes </span>column of the table of values returned by the <span class="term">GetDataBaseStorageStructure()</span> method, long index names were indicated and the index names differed in different DBMSs.</td><td>The names of indexes in the database schema are refined.</td></tr><tr title="Версия 8.3.17" class="tag_38"><td><a name="10f30227-14f6-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Tooltips for the check box, which controls the behavior of the object property in the extension, have become more clear and better describing the essence of the check box status.</td><td>Tooltips for the check box, which controls the behavior of the object property in the extension were poorly describing the check box status.</td><td>Improved tooltips for the check box describing the behavior of an object property in the extension.</td></tr></table><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f368930-eb6c-11e9-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.17" class="compat tag_109 tag_1"><td><a name="64bfb748-f0c0-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 109); return false;">Сlient application form</a>.<br></td><td>If no table is displayed in the form or there are no rows in the table or a row which is unavailable in the table is transferred to <span class="term">FormTable </span>object method:<ul><li>Use of <span class="term">FormTable.RowData()</span>, <span class="term">TableForm.CheckRow()</span> and <span class="term">FormTable.Unfolded()</span> results in <span class="term">Undefined</span> value.</li><li>Whenever you call <span class="term">FormTable.Unfold() </span>and <span class="term">FormTable.Fold() </span>methods, an exception is generated.</li></ul><p>If no table is displayed in the form or no rows are available in the table, as soon as you call <span class="term">FormTable.ChangeRow() </span>and <span class="term">FormTable.CopyRow() </span>methods an exception is generated.</p><p>If no table is displayed in the form, whenever you call <span class="term">FormTable.AddRow()</span>, <span class="term">FormTable</span>.<span class="term">FinishRowEditing</span><span class="term">()</span> and <span class="term">FormTable</span>.<span class="term">Update</span><span class="term">()</span> methods an exception is generated.</p><p>In 8.3.13 version compatibility mode behavior remained unchanged.</p></td><td>So far as thin and thick client applications are concerned:<ul><li>If no table is displayed in the form:</li><li>If now rows are available in the table or a row is transferred which is unavailable therein:</li><p> </p></ul><p>Web client:
</p><ul><li>If no table is displayed in the form:</li><li>If no rows are available in the table or a row is transferred which is unavailable therein:</li><li>If no rows are available in a table, as soon as <span class="term">FormTable.EditRow()</span> and <span class="term">FormTable.CopyRow() </span>methods are called, the said call is ignored.</li></ul><p>
</p></td><td>Now, the system operates in a similar way both on the thin and thick client. Unexpected system behavior was eliminated.</td></tr><tr title="Версия 8.3.17" class="tag_14"><td><a name="d93dba39-1103-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>To describe OpenID Connect provider in <span class="interface">default.vrd </span>file, you can specify the fields to compare users of 1C:Enterprise and OpenID Connect provider infobases.</td><td>This feature was not provided.<p>Users were always compared by e-mail and infobase user name.</p></td><td>Now, you can use OpenID Connect with a great number of providers, for instance, Microsoft Azure.</td></tr><tr title="Версия 8.3.17" class="compat tag_25 tag_1"><td><a name="8d099732-14e5-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a data composition system expression in query language contains curly brackets, whenever this query is processed, the said characters cannot be deleted.<p>If there is no "}" character at the end of a data composition system expression in query language before that query is transmitted, an error is displayed.</p><p>In 8.3.16 version compatibility mode behavior remained unchanged.</p></td><td>If a data composition system expression in query language contained curly brackets, whenever this query was processed, the said characters were deleted from the query.<p>If there was no "}" character at the end of a data composition system expression in query language before that query was transmitted, no error was displayed.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="compat tag_19 tag_45 tag_1"><td><a name="0d2006e9-11bb-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>When using the file or client-server version (when using the Microsoft SQL Server DBMS), the query language operator <span class="term">IN</span>, which meets all of the following criteria, always returns a <span class="term">Boolean </span>value:<ul><li>Operator <span class="term">IN </span>contains a subquery.</li><li>Operator <span class="term">IN </span>subquery contains <span class="term">FIRST </span>or <span class="term">ORDER BY </span>operations.</li><li>The left side of <span class="term">IN </span>operator and the subquery contain values of different types or the <span class="term">AnyReference </span>type.
</li></ul><p>It is recommended to analyze these queries and refactor them, if necessary.</p><p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>When using the file or client-server version (when using the Microsoft SQL Server DBMS), the query language operator <span class="term">IN</span>, which meets all of the following criteria, returned a <span class="term">Boolean </span>or <span class="term">NULL </span>value:<ul><li>Operator <span class="term">IN </span>contains a subquery.</li><li>Operator <span class="term">IN </span>subquery contains <span class="term">FIRST </span>or <span class="term">ORDER BY </span>operations.</li><li>The left side of <span class="term">IN </span>operator and the subquery contain values of different types or the <span class="term">AnyReference </span>type.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="compat tag_25 tag_1"><td><a name="daafe832-166d-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a query with merges is available in the data composition system query, whenever you use <span class="term">DataCompositionProcessor</span>.<span class="term">Initialize() </span>method with <span class="term">RestrictGettingFieldsByRefByViewRight </span>set to <span class="term">True</span>, <span class="term">View </span>rights are applicable to all merging parts.<p>In 8.3.16 version compatibility mode behavior remained unchanged.</p></td><td>If a query with merges was available in the data composition system query, whenever you used <span class="term">DataCompositionProcessor.Initialize()</span> method with <span class="term">RestrictGettingFieldsByRefByViewRight </span>set to <span class="term">True</span>, <span class="term">View </span>rights were applicable to the initial merging part only.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_10"><td><a name="979d198a-b106-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now it takes less time to connect to the infobase upon mass connections.
When you start the server cluster, the working process caches the <span class="term">PublishDistributiveLocation*</span> parameter values. If you change the <span class="term">PublishDistributiveLocation*</span> parameters in the <span class="interface">conf.cfg </span>file, 1C:Enterprise will apply the new directory values in 10 seconds after you save the cong.cfg file.</td><td>Previously, the system read the <span class="term">PublishDistributiveLocation*</span> parameters from the <span class="interface">conf.cfg </span>file when it required the parameter values. It could result in significant delays upon mass connections to the infobase.</td><td>Now it takes less time to connect to the infobase upon mass connections.</td></tr></table><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f368931-eb6c-11e9-8371-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.17" class="compat tag_0 tag_1"><td><a name="a35b9a8a-f0c8-11e9-8371-0050569f678a"></a>Some picture library items were renamed. Old names are saved for compatibility purposes, but they can refer to other pictures.</td><td><ul><li><span class="term">Calendar</span>.</li><li><span class="term">Calculator.</span></li><li><span class="term">Magnifier</span>.</li><li><span class="term">SelectType</span>.</li><li><span class="term">Select</span>.</li><li><span class="term">Clear</span>.</li><li><span class="term">Help</span>.</li></ul></td><td><ul><li><span class="term">InputFieldCalendar</span>.</li><li><span class="term">InputFieldCalculator</span>.</li><li><span class="term">InputFieldOpen</span>.</li><li><span class="term">InputFieldSelectType</span>.</li><li><span class="term">InputFieldSelect</span>.</li><li><span class="term">InputFieldClear</span>.</li><li><span class="term">FormHelp</span>.</li></ul></td></tr><tr title="Версия 8.3.17" class="tag_0"><td><a name="d722a69e-f0e4-11e9-8371-0050569f678a"></a>Cluster service that stores dynamic information about cluster composition and status.</td><td><ul><li><span class="interface">Cluster lock service.</span></li></ul></td><td><ul><li><span class="interface">Cluster</span> <span class="interface">status</span> <span class="interface">service</span>.</li></ul></td></tr><tr title="Версия 8.3.17" class="tag_0"><td><a name="ceae2cbf-f591-11e9-8371-0050569f678a"></a>Availability of 'all functions' phrase in the headers of Designer and client application configuration settings.</td><td><ul><li><span class="interface">Show All Functions Command </span>parameter in Designer starting setup dialog box.</li><li><span class="interface">All functions </span>main menu item and header of the form that opens at the same time.</li><li><span class="interface">All Functions </span>global search keyword.</li><li>Global search result display - <span class="interface">All Functions</span>.</li></ul></td><td><ul><li><span class="interface">Technical Specialist mode </span>parameter in Designer start setup dialog box.</li><li><span class="interface">Functions for Technical Specialist </span>main menu item and a similar header of the form that opens at the same time.</li><li><span class="interface">Functions for Technical Specialist </span>global search keyword.</li><li>Global search result display -<span class="interface"> Functions for Technical Specialist</span>.
</li></ul></td></tr><tr title="Версия 8.3.17" class="tag_0"><td><a name="23460cd3-f593-11e9-8371-0050569f678a"></a>Names containing 'all functions' phrase. Old names are used for compatibility.</td><td><ul><li><span class="term">AllFunctionsMode</span> access rights.</li><li><span class="term">StandardGlobalSearchAppearance</span>.<span class="term">AllFunctions </span>system enumeration value.</li><li>Command line parameter to start <span class="term">DisplayAllFunctions</span> client application.</li></ul></td><td><ul><li><span class="term">TechicalSpecialistMode</span> access rights.</li><li><span class="term">StandardGlobalSearchAppearance</span>.<span class="term">FunctionsForTechnicalSpecialist</span> system enumeration value.</li><li>Command line parameter to start <span class="term">TechnicalSpecialistMode</span> client application.</li></ul></td></tr></table><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f368932-eb6c-11e9-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.17" class="tag_31"><td><a name="9906b238-1509-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Images in SVG format can be displayed in the mobile client. No filters and effects are supported when you use images of this format.<p><span class="term">ImageFormat</span>.<span class="term">SVG</span> system enumeration property was implemented.</p></td><td>This feature was not provided.</td><td>1C:Enterprise mobile client now supports display of images in SVG format.</td></tr><tr title="Версия 8.3.17" class="tag_11 tag_30 tag_31"><td><a name="7998d5a4-150f-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>So far as add-ins are concerned which are supported by mobile devices running iOS, you can connect dynamic system libraries to add-ins.<p>The add-in technology documentation is updated. (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>)</p></td><td>This feature was not provided.<p>So far as add-ins running iOS were concerned, you were able to specify required subsystem components only.</p></td><td>Functionality to develop add-ins running iOS was added.</td></tr><tr title="Версия 8.3.17" class="tag_31"><td><a name="2779720c-1511-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Dynamic add-in setting is no longer supported by mobile client application build (including mobile clients which can run in a standalone mode) running Android. <span class="term">DynamicAddInInstallationSupported</span><span class="term">()</span> method always returns <span class="term">False</span> value on a mobile device (except mobile versions for developers)</td><td>Whenever you were running Android, you were able to use dynamic add-in setting for mobile application application build (including mobile clients capable of running in a standalone mode).</td><td>Due to update of security policy by Google, always make sure that add-ins available on a mobile client are included in a mobile application build.</td></tr><tr title="Версия 8.3.17" class="tag_111"><td><a name="fcd0546c-1511-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 111); return false;">Formatted documents</a>.<br></td><td>External appearance of a tool bar for formatted and HTML-documents in a mobile version of 1C:Enterprise was changed. Functionality offered by a tool bar remained unchanged.<p>The formatting tool bar was made similar for mobile phones and tablets.</p></td><td>Previously, external appearance of a tool bar for formatted and HTML-documents in a mobile version of 1C:Enterprise was different. The formatting tool bar was dissimilar for mobile phones and tablets.</td><td>The formatting tool bar for formatted and HTML-documents became easier and more user-friendly.</td></tr><tr title="Версия 8.3.17" class="tag_30 tag_31"><td><a name="0a7b68e2-1513-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Application usage statistics services can now be connected to the mobile application being built. The following statistics services are supported:<ul><li>FirebaseAnalytics (Android and iOS).</li><li>AppMetrica (Android, iOS and Windows).</li><li>Appsee (Android and iOS).</li></ul><p>
<span class="term">ApplicationUsageStatistics</span> global context property was implemented.</p></td><td>This feature was not provided.</td><td>Now, you can integrate mobile applications for a mobile version of 1C:Enterprise with various mobile application statistics services.</td></tr><tr title="Версия 8.3.17" class="tag_30 tag_31"><td><a name="7f5c31b0-15be-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>User interface was enhanced (photos, audio and video recording). Now, you can review the result of action you performed and (if deemed necessary) repeat it.</td><td>User interface was different (photos, audio and video recording). You were unable to preview and hear the results of your actions. Moreover, you were unable to repeat any of the actions.</td><td>Now, it is much more easier to use tools supported by a mobile version to record audios and videos and make photos in a convenient way.</td></tr><tr title="Версия 8.3.17" class="tag_30 tag_20"><td><a name="5c4dc041-224b-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>It has become possible to connect to the web server where the configuration of the mobile application is published using the HTTPS protocol in the developer's mobile platform. Opening the dialog box for configuring an HTTPS connection has been implemented in the infobase adding dialog box.</td><td>This feature was not provided.</td><td>Connecting a developer's mobile platform to a web server can be more secure (using the HTTPS protocol).</td></tr></table><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f368933-eb6c-11e9-8371-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.17" class="tag_0"><a name="75c02249-eb6d-11e9-8371-0050569f678a"></a>OpenSSL library is updated to version 1.1.0k.</li><li title="Версия 8.3.17" class="tag_0"><a name="109287b7-93a2-11eb-8371-0050569f678a"></a>The libtiff library is updated to version 4.2.0.</li></ul><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f368934-eb6c-11e9-8371-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.17" class="tag_0"><a name="708bd01a-475a-11ea-8371-0050569f678a"></a>In the demo configuration an example of error display handler is implemented and an example of declarative configuration of error message text templates is given.
The handler is implemented in the application module. For more details see the configuration guide.</li><li title="Версия 8.3.17" class="tag_0"><a name="48e5ded9-7982-11ea-8371-0050569f678a"></a>Setting global search description from the configuration code in mobile client is now available.<p>
</p></li><li title="Версия 8.3.17" class="tag_0"><a name="0dadfca4-7983-11ea-8371-0050569f678a"></a>The <span class="term">ShowUserNotification()</span> method is used to inform the user when synchronization completes.</li><li title="Версия 8.3.17" class="tag_0"><a name="e99fa54a-7983-11ea-8371-0050569f678a"></a>Updated guide appearance. The guide list of sections is implemented as a drop-down list.</li></ul><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f368935-eb6c-11e9-8371-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.17" class="tag_53"><td><a name="a24ab6e7-376a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>The HTTP error registration service <a href="https://pult.1c.com/pult/platform/errors" target="_blank">https://pult.1c.com/pult/platform/errors</a> can be called when the application abnormally terminates.
To stop reports sending, disable abnormal terminations report sending in the <span class="term">ErrorProcessing</span> object.
</td><td>No services were used when the application terminated abnormally.</td><td>When the application terminates abnormally, the information about the error is sent to 1C Company automatically.
</td></tr><tr title="Версия 8.3.17" class="tag_53"><td><a name="a237bef6-3772-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>The standard texts of error messages are changed. The standard dialog box for sending an error report is changed.
To motivate the user to send a report on a specific error to the error registration service, it is recommended to return an appropriate message from the error registration service. This message will be displayed on the error form.</td><td>The standard texts of the error messages were different. The dialog box of sending the error report was different.</td><td>Error representation has been improved.</td></tr><tr title="Версия 8.3.17" class="tag_16"><td><a name="1375ba5d-3773-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>When recording an information register record set, the insignificant chars to the right of the last significant chart are deleted in string type dimensions.</td><td>When recording an information register record set, the insignificant chars to the right of the last significant chart were not deleted in string type dimensions.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="compat tag_112 tag_1"><td><a name="051de2d8-3781-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 112); return false;">A client application form</a>.<br></td><td>If after the form table display update all displayed rows have become invisible, then the <span class="term">InitialListView</span> form table property is used to define the first displayed row.
If the current table row have become invisible, the nearest (by key) row of the list becomes the current one. A new display list is formed based on the new current row.
It is recommended to review the previous list behavior in the application.
This change is not implemented in version 8.3.16 compatibility mode.</td><td>If after the form table display update all displayed rows had become invisible, the list display always started from the beginning.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="compat tag_25 tag_1"><td><a name="224c4ded-3788-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If the filter with the <span class="interface">Filled</span> or <span class="interface">Is not filled</span> comparison type for the filed which is set as the aggregate function in the query is specified in the settings of the data composition system, then such condition in the resulting query is placed to the <span class="term">HAVING</span> query section.
This change is not implemented in version 8.3.16 compatibility mode.</td><td>If the filter with the <span class="interface">Filled</span> or <span class="interface">Is not filled</span> comparison type for the filed which was set as the aggregate function in the query was specified in the settings of the data composition system, then such condition in the resulting query was placed to the <span class="term">WHERE</span> query section.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_10"><td><a name="ed2e93aa-4759-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td><span class="term">InfobaseSession.ClientIPAddress</span> property contains IP-address for another sessions only if the user has the <span class="term">Administration</span> right. Otherwise, this property contains an empty string.</td><td><span class="term">InfobaseSession.ClientIPAddress</span> property always contained IP-address for another sessions.</td><td>Increased security of the infobase sessions list.</td></tr><tr title="Версия 8.3.17" class="tag_53"><td><a name="49c3697e-4d81-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>For the <span class="term">ErrorCategory</span> system enumeration, the <span class="term">FullTextSearchError</span>, <span class="term">ExternalDataSourceError</span>, and <span class="term">NavigationLinkError</span> values are implemented.<p>Help is disabled in the error form and error report form, because there may be no connection with the server when these forms are displayed.</p><p>Changed the format of the report.json file, which contains automatically collected error information. Changes are stated in the documentation as well.</p><p>When adding screenshots in the error report, screenshots of all application windows will be added (even if the application is not active).</p><p>For the <span class="term">ErrorProcessingSettings</span> object, the <span class="term">IncludeScreenshotsInReport</span>, <span class="term">IncludeDetailedErrorTextInReport</span>, <span class="term">IncludeInfobaseInformationInReport</span>, and <span class="term">AdditionalReportInfo</span> properties are implemented.</p><p>The appearance of the error report form has been improved.</p><p>The request file format has been modified for the getInfo method of the error registration web service. It will allow to return localized message texts to the user and specify the dump format for transferring in service (available only when running Windows).</p></td><td>These features were not provided.</td><td>The mechanism of runtime errors processing has been improved.</td></tr><tr title="Версия 8.3.17" class="tag_84 tag_28"><td><a name="35c379d9-524c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Localized web client application interface for Arabic (<span class="interface">ar</span>).</td><td>This feature was not provided.</td><td>1C:Enterprise web client is now available for Arabic-speaking users.</td></tr><tr title="Версия 8.3.17" class="tag_45"><td><a name="a7048702-62b4-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Optimized execution of queries using the <span class="term">IN</span> operator with a list of values containing the <span class="term">UNDEFINED</span> value.</td><td>Executing queries using the <span class="term">IN</span> operator with a list of values containing the <span class="term">UNDEFINED</span> value was not optimal.</td><td>Optimization results in faster query execution, if after the field used in the expression <span class="term">Field IN (Undefined)</span> there are still fields in the index that are used in the filter.</td></tr><tr title="Версия 8.3.17" class="tag_19 tag_29"><td><a name="068e98b6-6829-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft SQL Server 2019 DBMS is now supported.</td><td>Microsoft SQL Server 2019 DBMS was not supported.</td><td>New Microsoft SQL Server version is now supported.</td></tr><tr title="Версия 8.3.17" class="tag_14 tag_28 tag_53"><td><a name="bb645f34-682f-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>If an unrecoverable error occurs, the option to automatically terminate the client application without displaying a dialog that requires a user reaction is implemented. The <span class="term">/</span><span class="term">DisableUnrecoverableErrorMessage </span>client application start line command has been implemented.</td><td>This feature was not provided.<p>When an unrecoverable error occurred, a dialog was generated that required a mandatory user reaction.</p></td><td>Simplified the system use in modes when the client application does not require a presence of user (for example, in automatic testing mode).</td></tr><tr title="Версия 8.3.17" class="tag_26 tag_64"><td><a name="842e7838-6d97-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Implemented the feature to save the text writing direction in a spreadsheet document for exporting and printing. This feature is available for thin client, thick client, and web client. The text direction is saved when exporting to all appropriate formats.<p>Text direction is supported for the 1C:Enterprise spreadsheet document and for imported spreadsheet documents of XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) formats.</p><p>Added the <span class="term">TextDirection </span>spreadsheet document property. This property allows to specify the text direction in a spreadsheet document explicitly: left-to-right or right-to-left.</p><p>If a cell has automatic horizontal alignment, the numbers are always right-aligned, and other values are aligned according to the interface text direction.</p></td><td>A spreadsheet document was exported and printed with left-to-right text direction. The export and print mode did not depend on the operating system used.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_4"><td><a name="f8975fad-73fe-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>You can now perform a video call in thick or thin client in remote desktop window.</td><td>There was no option to perform a video call in thick or thin client remote desktop window.</td><td>Video calls in thin and thick client are more accessible now.</td></tr><tr title="Версия 8.3.17" class="tag_30 tag_31"><td><a name="4a142872-797c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>1C:Enterprise mobile version now supports the hardware or external keyboard in the client application form fields that display values of <span class="term">Number </span>and <span class="term">Date </span>types.<p><span class="interface">Tab </span>and <span class="interface">Shift+Tab </span>shortcuts can now be used to navigate through the form fields. The arrow keys of hardware or external keyboard, joystick, or other cursor control mechanism can now be used to navigate through the form fields.</p><p>The keyboard shortcuts configured by the developer are now supported for the form items. The standard keyboard shortcuts used in the PC version are not supported.</p><p>Implemented the <span class="interface">Esc </span>and <span class="interface">Enter </span>keys support on a hardware or external keyboard.</p></td><td>This feature was not provided.</td><td>Improved data input on mobile devices through a hardware or external keyboard.</td></tr><tr title="Версия 8.3.17" class="tag_42"><td><a name="6f0d00f4-98f4-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br></td><td>When the maximum period of calculated totals of the accumulation register is set, it is not possible to add register records of this register.</td><td>When the maximum period of calculated totals of the accumulation register was set, it was possible to add register records of this register. When the maximum period of calculated totals was changed and register records were added at the same time, register totals could be incorrect.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_71"><td><a name="071edf9b-9f2a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 71); return false;">Analytics system</a>.<br></td><td>For the analytics system manager, implemented the <span class="term">GetConnections</span><span class="term">()</span> method that returns the <span class="term">AnalyticsSystemServerConnection </span>object. Implemented the <span class="term">AnalyticsSystemSchema </span>object.<p>Implemented the options to manage additional sources for the standard data processor of analytics management.</p><p>The <span class="term">RefreshInterface()</span> global context method changes visibility of the <span class="interface">Analytics </span>item in the <span class="interface">Service and settings </span>menu (depending on the current analytics system settings).</p></td><td>These features were not provided.</td><td>Extended API of interaction with the analytics system.</td></tr><tr title="Версия 8.3.17" class="tag_71 tag_4"><td><a name="7c58677a-9f2a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 71); return false;">Analytics system</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>If an infobase supports the collaboration system, the analytics system provides the ability to open information on a reference type object in all client applications of this user at once.</td><td>This feature was not provided.</td><td>Improved the analytics system interface.</td></tr><tr title="Версия 8.3.17" class="tag_21 tag_58"><td><a name="a256b4bc-9f36-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>Reduced use of RAM upon indexing information register records.<p>Faster indexing for separated infobases.</p><p>Changed the format of temporary full-text search files. Now the format changes automatically upon index update. Upon migration to the previous platform version, the index will be cleared.</p></td><td>Indexing information register records required more RAM.<p>Building a full-text search index for a separated infobase took more time.</p></td><td>Improved building of a full-text search index.</td></tr><tr title="Версия 8.3.17" class="tag_59 tag_30 tag_31"><td><a name="b9d08fa9-a97a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>If an input field is used to enter a value of the <span class="term">Number </span>type and the <span class="term">SpecialTextInputMode </span>property is set to <span class="term">Digits</span>, a calculator that contains only digits, a comma, the last character delete button, <span class="interface">OK</span>, and <span class="interface">Cancel </span>is used for input.</td><td>If an input field was used to enter a value of the <span class="term">Number </span>type and the <span class="term">SpecialTextInputMode </span>property was set to <span class="term">Digits</span>, a standard calculator with excessive features was used for input.</td><td>Simplified number input in mobile applications.</td></tr><tr title="Версия 8.3.17" class="tag_51"><td><a name="37a3bf5f-b6df-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>Improved performance of the following methods of the <span class="term">TestedApplication</span> object and objects of client application windows: <span class="term">FindObject()</span>, <span class="term">FindObjects()</span>, and <span class="term">GetObject()</span>.</td><td>Execution of the following methods of the <span class="term">TestedApplication </span>object and objects of client application windows took more time: <span class="term">FindObject()</span>, <span class="term">FindObjects()</span>, and <span class="term">GetObject()</span>.</td><td>Improved performance of the automated testing feature for the client application.</td></tr><tr title="Версия 8.3.17" class="tag_32"><td><a name="575a7589-b6e1-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>The mobile application builder can now upload new 1C:Enterprise mobile versions automatically. This feature is supported by the client/server mode of the mobile application builder only.<p>The mobile application builder in the file mode has the following options (and settings) disabled:</p><ul><li>Clearing the obsolete data from the infobase.</li><li>Clearing the obsolete data from the builder cache.</li></ul></td><td>The mobile application builder could upload the new 1C:Enterprise mobile version interactively only.<p>Clearing the obsolete data from the infobase and from the builder cache were available in the file infobase mode. This could potentially cause unexpected system behavior due to the scheduled job feature specifics in the file infobase mode. </p></td><td>Uploading new 1C:Enterprise mobile versions in the mobile application builder is now faster and more convenient.</td></tr><tr title="Версия 8.3.17" class="tag_44"><td><a name="890cd681-b6e3-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 44); return false;">Infobase verification and repair</a>.<br></td><td>Infobase verification and repair feature now includes an option to check the logical integrity of the configuration extension. Some repair options are also available for the extensions.<p>Added the new parameter for the <span class="term">/IBCheckAndRepair</span> command of the Designer batch mode <span class="term">- ConfigurationExtensionsLogIntegrity</span>. This parameter launches the logical integrity check of the configuration extension.</p></td><td>Infobase verification and repair feature had no option to check and repair configuration extensions errors. Some errors might cause the entire infobase to be unavailable.
</td><td>Improved the reliability of infobases containing extensions.</td></tr><tr title="Версия 8.3.17" class="tag_27"><td><a name="6d3fa648-c027-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The format version of the configuration export to XML is now 2.11.</td><td>The format version of the configuration export to XML was 2.10.</td><td>The configuration export to XML now supports new platform features.</td></tr><tr title="Версия 8.3.17" class="tag_53"><td><a name="7f3f68f0-c04a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>The network errors info feature was completely reviewed. Improved the error messages text, that now contain information about the error and its possible causes.<p>If there was a network connection error while requesting the 1C:Enterprise server cluster and there is an option to retry the request after the connection was restored, the prompt to retry the request will be replaced by the message that the network connection was restored.</p><p>The error dialog box does not provide the option to send an error report, if there is no network connection.</p><p>Application developers should rework the application code using the following recommendations:</p><ul><li>Use a single idle handler to execute user actions, such as procedure delayed execution or displaying the current row data.</li><li>Use a repeated idle handler to execute automatic actions without user interaction, such as status updates.</li><li>We recommend to change the error display mode for configurations that use the version 8.3.16 and earlier compatibility mode to <span class="interface">User message errors</span>. Use the standard function of error processing settings management for that.</li></ul></td><td>The error messages were harder to understand and more annoying.<p>An option to send the error report was available even if there was no network connection (thus the report could not be sent).</p></td><td>The network errors dialog boxes are now less annoying.</td></tr><tr title="Версия 8.3.17" class="tag_14"><td><a name="992ef030-cb1e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>For all client applications the login button in the authentication dialog box is now called <span class="interface">Log in</span>.<p>There is now an option to show the password. Implemented the button to show/hide the password.</p><p>Improved the authentication form display of OpenID Connect on mobile devices.</p></td><td>For all client applications the login button in the authentication dialog box was called Ok.<p>There was no option to show the password.</p></td><td>The authentication dialog box is now more convenient.</td></tr><tr title="Версия 8.3.17" class="tag_0"><td><a name="c37b91ef-cfe6-11ea-8371-0050569f678a"></a></td><td>Improved performance of initial population of database copy table if this table is included in multiple transactions.</td><td>The performance of initial population of database copy table if this table was included in multiple transactions was not optimal.</td><td>Improved performance of initial population of database copy table if this table is included in multiple transactions.</td></tr><tr title="Версия 8.3.17" class="tag_29 tag_30 tag_31"><td><a name="ad973583-dc94-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Mobile applications built using mobile version 8.3.17.67 will meet the requirements of Google Play for new applications. The target SDK version is 29.<p>To upload a mobile application to Google Play, build a mobile application using mobile version 8.3.17.67 or later.
</p></td><td>Mobile applications built using mobile versions that are older than 8.3.17.67 could not be uploaded to Google Play after August 3, 2020.</td><td>1C:Enterprise mobile version meets the requirements of Google Play.</td></tr><tr title="Версия 8.3.17" class="tag_48 tag_30 tag_31"><td><a name="45bcaf45-dc97-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>For mobile version tools responsible for audio recording on a mobile device, the following features are now available:<ul><li>Managing audio recording parameters: result format, mono or stereo recording, audio stream characteristics, and other. New object: <span class="term">AudioRecordingParameters</span>.</li><li>New parameters for the <span class="term">MultimediaTools</span>.<span class="term">MakeAudioRecording()</span>: <span class="term">AudioRecordingParameters</span>, <span class="term">StartRecordingAtOnce</span>, and <span class="term">DisplayListeningWindow</span>. The parameters allow you to manage audio recording when you use the mobile application.</li><li>New feature: background audio recording can be managed using device microphones. New methods for the <span class="term">MultimediaTools </span>global context property: <span class="term">EnableAudioRecording()</span> and <span class="term">DisableAudioRecording()</span>.</li></ul></td><td>Audio recording parameters could not be configured on a mobile device. Background audio recording was not supported on a mobile device.</td><td>New features for audio recording on a mobile device.</td></tr><tr title="Версия 8.3.17" class="tag_46"><td><a name="f73ea803-f65f-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 46); return false;">Integration service</a>.<br></td><td>Improved sending and receiving of integration service messages.</td><td>When using integration services, sending and receiving of messages were not sufficient enough.</td><td>Improved sending and receiving of integration service messages.</td></tr><tr title="Версия 8.3.17" class="tag_48 tag_30 tag_31 tag_32"><td><a name="af37bea3-0ebb-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>AppSee is removed from the list of supported statistics services.</td><td>1C:Enterprise mobile version supported AppSee.</td><td>1C:Enterprise mobile version does not support AppSee.</td></tr><tr title="Версия 8.3.17" class="tag_48"><td><a name="ac5e78f0-12dc-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The <span class="term">EnableAudioRecording() </span>and <span class="term">MakeAudioRecording()</span> methods prevent the mobile device from idling to sleep to prevent audio recording from stopping.<p>The audio recording stop handler passed to the <span class="term">EnableAudioRecording()</span> method is called to not lock the user interface.</p><p>The default value for the <span class="term">ButtonLocation </span>parameter of the <span class="term">EnableAudioRecording()</span> method is <span class="term">Undefined</span>.</p><p>Improved the audio recording interface.</p></td><td>The <span class="term">EnableAudioRecording()</span> and <span class="term">MakeAudioRecording()</span> methods did not prevent the mobile device from idling to sleep. As a result, audio recording could stop.<p>The audio recording stop handler passed to the <span class="term">EnableAudioRecording()</span> method was called in such a way that a long server call from this handler could lock the user interface.</p><p>The default value for the <span class="term">ButtonLocation</span> parameter of the <span class="term">EnableAudioRecording()</span> method was the value where the platform automatically selected the location of the button to stop recording.</p></td><td>Improved the audio recording interface (both user interface and API) in the mobile application.</td></tr><tr title="Версия 8.3.17" class="tag_31"><td><a name="e646eff8-12de-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile client tries to close the session in the server cluster correctly in case of unexpected shutdown. Abnormal termination can occur, in particular, when the mobile operating system removes the mobile client application from RAM when the device enters sleep.</td><td>The mobile client did not try to close the session in the server cluster correctly in case of unexpected shutdown.
</td><td>Reduced the number of hung mobile client sessions. This reduces the amount of occupied licenses and locks from inactive devices.</td></tr><tr title="Версия 8.3.17" class="tag_29"><td><a name="3d711f30-32e1-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Updated system requirements for the client application:<ul><li>Minimum system requirements:</li><li>Recommended system requirements:</li></ul></td><td>The system requirements for the client application were as follows:<ul><li>Minimum system requirements:</li><li>Recommended system requirements:</li></ul></td><td>Updated system requirements for client applications (including Designer).</td></tr><tr title="Версия 8.3.17" class="tag_48 tag_30 tag_31"><td><a name="529598fd-32e5-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>For a mobile application running Android 10 or later to use geolocation in the background, set the <span class="interface">Background location</span><span class="interface"> </span>permission in Designer, export the configuration, and rebuild the mobile application using Mobile Application Builder.</td><td>A mobile application running Android version 10 or later was unable to use geolocation in the background.</td><td>The limitations of Android 10 and later are taken into account.</td></tr><tr title="Версия 8.3.17" class="tag_31"><td><a name="b8b3a63a-32fb-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Upgrade: checking the connectivity to the selected infobase in the mobile client is revised. A mobile client signature is verified not only on the mobile client but also on the server. The mobile client can connect to the infobase if the mobile client configuration and the server configuration match at least 80%.<p>Changed setup for generating an infobase configuration signature.</p><p>Errors that occur while checking the mobile client connectivity to the selected infobase are now more user-understandable.</p></td><td>Mobile client connectivity to the infobase was tested only on the mobile client.<p>The requirement to match mobile client configurations and main infobase configurations was more stringent.</p></td><td>The mobile client can connect to the infobase in more cases. The need to update the mobile client is now less acute. The previously published mobile client can work with the infobase in case of minor modifications to the infobase configuration.</td></tr><tr title="Версия 8.3.17" class="tag_30 tag_31"><td><a name="c84a45e9-3300-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>To restore the ability of the mobile application to access files on a mobile device, do the following:<ul><li>Install SDK Platform for API 29 in Android Studio used by Mobile Application Builder.</li><li>Upload the mobile version 8.3.17.80 or later to Mobile Application Builder.</li><li>Build a mobile application with a new mobile version.</li><li>Republish the mobile application on Google Play.</li></ul><p>
The target Android version is set back to 10.0 (API 29).</p></td><td>The target Android version was 11 (API 30). As a result of changing the target Android version, the mobile application lost access to files on the mobile device.</td><td>Restored access to files on a mobile device.</td></tr><tr title="Версия 8.3.17" class="tag_32"><td><a name="0fb198c4-4072-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile Application Builder now supports Xcode 12.</td><td>Mobile Application Builder did not support building using Xcode 12.</td><td>Mobile Application Builder now supports the latest Xcode version.</td></tr><tr title="Версия 8.3.17" class="tag_29 tag_30 tag_31"><td><a name="46f86e90-4073-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile version now supports Android 11 and iOS 14.</td><td>The mobile version did not support Android 11 and iOS 14.</td><td>The mobile version of 1C:Enterprise now supports the latest mobile operating systems.</td></tr><tr title="Версия 8.3.17" class="tag_74"><td><a name="04975e07-4062-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br></td><td>In file mode, it is checked whether there is a feature testing license.<p>In partictular, using integration services in a file infobase requires a feature testing license.</p><p>In client/server mode, the upgrade is ignored.</p></td><td>The feature testing license check depended on the infobase mode:<ul><li>In client/server mode, the check was performed.</li><li>In file mode, the check was not performed.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_79"><td><a name="830e95f4-6c41-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>When receiving an SVG image from a temporary storage, an infobase or via a direct link, sections with JavaScript are removed from the image.</td><td>When receiving an SVG image from a temporary storage, an infobase or via a direct link, sections with JavaScript were not removed from the image.</td><td>Reduced the possibility of destructive actions using JavaScript embedded in an SVG image.</td></tr><tr title="Версия 8.3.17" class="tag_20 tag_31"><td><a name="d1ae448f-6d1e-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile client configuration that was signed in version 8.3.16 (and the signature was not changed in version 8.3.17 and later) is accepted by the mobile client in version 8.3.17 and later.<p>We do not recommend that you change the configuration signature in version 8.3.16 if the configuration is executed on version 8.3.17.</p></td><td>The mobile client configuration that was signed in version 8.3.16 (and the signature was not changed in version 8.3.17 and later) was not accepted by the mobile client in version 8.3.17 and later. Platform version 8.3.17 and later considered such a configuration to be unsigned.</td><td>As a result, after updating the platform on the server cluster computer up to version 8.3.17, mobile clients running iOS will remain in operation.</td></tr><tr title="Версия 8.3.17" class="tag_14"><td><a name="0d6b6b06-8328-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>When using 1C:Enterprise authentication or accessing infobase with thin or web client using HTTP protocol, user password is passed using SHA-256 hash algorythm and AES-256 CBC encoding algorythm..</td><td>Thin and web clients passed the user password not encrypted when using 1C:Enterprise authentication or accessing infobase with thin or web client using HTTP protocol.</td><td>Thin and web cliients now use safer authentication when accessing infobase using HTTP protocol.</td></tr><tr title="Версия 8.3.17" class="tag_48"><td><a name="8ff50152-92f3-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>PUSH notifications that are sent from the mobile platform for PC through APNS service now use HTTP/2 protocol, port 443.</td><td>PUSH notifications that were sent from the mobile platform for PC through APNS service used obsolete binary protocol.</td><td>PUSH notifications can now be sent through APNS.service again.</td></tr><tr title="Версия 8.3.17" class="tag_39 tag_6"><td><a name="c9d34903-93ac-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Limited the number of event log indexing streams. New technological log event: <span class="term">&lt;EVENTLOG&gt;</span>.</td><td>Event log indexing could produce heavy system load, especially with a large number of infobases.</td><td>Reduced the system load caused by event log indexing when the server cluster hosts a large number of infobases.</td></tr><tr title="Версия 8.3.17" class="tag_28 tag_29"><td><a name="f9724b4b-93ae-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The web client is now supported in the following web browsers:<ul><li>Google Chrome 49 and later running Linux.</li><li>chromium-gost version 49 and later running Linux, macOS, or Windows.</li></ul></td><td>The web client was not supported in the following web browsers:<ul><li>Google Chrome of any version running Linux.</li><li>chromium-gost of any version.</li></ul></td><td>Extended the list of web browsers to run the web client.</td></tr><tr title="Версия 8.3.17" class="tag_39"><td><a name="4bcbae51-9cfd-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>In a file infobase, the event log indexing and the use of an already built index are disabled.</td><td>In a file infobase, the event log was indexed and an already built index was used in the event log.</td><td>Decreased infrastructure load, especially for a shared file infobase. Improved client application stability.</td></tr><tr title="Версия 8.3.17" class="tag_6"><td><a name="8e2c208c-b224-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Eliminated the slowdown in user operations when there is insufficient RAM on computers running cluster working processes. The RAM consumption by cluster working processes might increase.</td><td>When there is insufficient RAM on computers running cluster working processes, there was a significant performance decrease.</td><td>Eliminated the slowdown in user operations when there is insufficient RAM on computers running cluster working processes.</td></tr><tr title="Версия 8.3.17" class="tag_56"><td><a name="448eebf3-ba14-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>Reading a large <span class="term">CDATA </span>section for an XML document with UTF-8 encoding is now faster.</td><td>Reading a large <span class="term">CDATA </span>section for an XML document with UTF-8 encoding was slow.</td><td>Improved XML document performance in some cases.</td></tr><tr title="Версия 8.3.17" class="tag_15 tag_6 tag_10"><td><a name="2d2a491b-da69-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented operating system authentication via Kerberos protocol for 1C:Enterprise client applications managed by Linux.</td><td>This feature was not provided.</td><td>Linux users in a Windows domain network can now use operating system authentication to access infobases that are managed by a Windows server cluster.</td></tr><tr title="Версия 8.3.17" class="tag_47"><td><a name="e3756ee4-f426-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>New feature: authentication in the infobase is required to perform operations with it via the standalone server administration utility (<span class="interface">ibcmd</span>). It is required for the following commands:<ul><li>Dump infobase to a DT file (<span class="interface">infobase dump</span>).</li><li>Restore infobase from a DT file (<span class="interface">infobase restore</span>).</li><li>Clear infobase (<span class="interface">infobase clear</span>).</li><li>Load configuration (<span class="interface">infobase config load</span>).</li><li>Save configuration (<span class="interface">infobase config save</span>).</li><li>Check infobase (<span class="interface">infobase config check</span>).</li><li>Update database configuration (<span class="interface">infobase config apply</span>).</li><li>Reset to database configuration (<span class="interface">infobase config reset</span>).</li><li>Export configuration to XML files (<span class="interface">infobase config export</span>).</li><li>Import configuration from XML files (<span class="interface">infobase config import</span>).</li><li>If the standalone server administration utility (<span class="interface">ibcmd</span>) requires to specify a password to connect to the infobase and it is not specified in the utility parameters, you are prompted to enter a password in the console.</li><li>New command line parameters for the standalone server administration utility (<span class="interface">ibcmd</span>): <span class="interface">--user</span> and <span class="interface">--password</span>.</li></ul></td><td>Authentication was not required to perform operations with an infobase via the standalone server administration utility (<span class="interface">ibcmd</span>). If connection to DBMS administration utility required a password and it was not specified, the administration utility did not prompt you to enter it.</td><td>Operations with the infobase via the standalone server administration utility (<span class="interface">ibcmd</span>) are more secure.</td></tr><tr title="Версия 8.3.17" class="tag_28 tag_29"><td><a name="61950c99-c074-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Yandex Browser version 22 or later is now supported on Linux, macOS, and Windows.</td><td>This feature was not provided.</td><td>Extended list of supported web browsers.</td></tr><tr title="Версия 8.3.17" class="tag_59"><td><a name="e313498a-1187-11ed-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>If visibility is disabled for a form table in the client application, calls of the following methods of this table are ignored: <span class="term">Expand()</span>, <span class="term">Collapse()</span>, <span class="term">AddRow()</span>, <span class="term">ChangeRow()</span>, <span class="term">CopyRow()</span>, <span class="term">EndEditRow()</span>, and <span class="term">Refresh()</span>. This update is applied to tables whose visibility was disabled by the user, tables in a collapsed group, and so on.<p>
</p><p>
</p></td><td>If visibility was disabled for a form table in the client application, calls of the following methods of this table raised an exception: <span class="term">Expand()</span>, <span class="term">Collapse()</span>, <span class="term">AddRow()</span>, <span class="term">ChangeRow()</span>, <span class="term">CopyRow()</span>, <span class="term">EndEditRow()</span>, and <span class="term">Refresh()</span>. This behavior was relevant for tables whose visibility was disabled by the user, tables in a collapsed group, and so on.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.17" class="tag_20"><td><a name="83a668e0-e675-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>You can control remote debugging and debugging features for separated infobases. To do it, you can specify users who can debug the configuration (broken down by infobases). To connect to the debugger, specify username and password.<p>New command for the command line of <span class="interface">ragent</span> and <span class="interface">dbgs</span> utilities: <span class="term">debugServerUsers</span>. For more information about the user description file format, see the documentation.</p><p>In the dialog box of Designer parameters, on the <span class="interface">Debug</span> tab, the <span class="interface">Password</span> input field is removed.</p><p>New event log events: <span class="interface">Debugging. Debug item attachment</span>, <span class="interface">Debugging. Debug item detachment</span>, and <span class="interface">Debugging. Expression calculation</span>.</p></td><td>This feature was not provided.<p>You could specify one password to debug any database served by a cluster.</p></td><td>Advanced development features for applications running in separated infobases.<p>
</p></td></tr><tr title="Версия 8.3.17" class="tag_28 tag_29"><td><a name="076fb90f-3b0a-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>In web client, the minimum supported Google Chrome version is 88.<p>Clipboard operations can be performed in web client without the file system extension in Google Chrome. However, web client must be available over HTTPS or published on a local computer. If these conditions are not met, clipboard operations are unavailable.</p></td><td>In web client, the minimum supported Google Chrome version was 49.<p>The file system extension had to be installed in Google Chrome to perform clipboard operations in web client.</p></td><td>Ended support for legacy Google Chrome versions.</td></tr><tr title="Версия 8.3.17" class="tag_10"><td><a name="76cf59ce-4629-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New user password features:<ul><li>Set the minimum password complexity with specification of required password characters and password complexity.</li><li>Set the minimum and maximum password validity period.</li><li>Prohibit usage of previously used passwords.</li><li>Group user password rules into password profiles.</li><li>Assign password profiles to users.</li><li>Check whether a password corresponds to the current password policies without saving a user (actual or dummy one) to the infobase.</li><li>Change user passwords with enabled password change prohibition if you have administrative rights.</li></ul><p>New global-context methods: <span class="term">SetUsersPasswordsMinValidityPeriod()</span>, <span class="term">GetUsersPasswordsMinValidityPeriod()</span>, <span class="term">SetUsersPasswordsMaxValidityPeriod()</span>, <span class="term">GetUsersPasswordsMaxValidityPeriod()</span>, <span class="term">SetUsersPasswordsRepetitionRestrictionAmongRecent()</span>, <span class="term">GetUsersPasswordsRepetitionRestrictionAmongRecent()</span>, <span class="term">SetPeriodOfWarningAboutUsersPasswordsExpiration()</span>, and <span class="term">GetPeriodOfWarningAboutUsersPasswordsExpiration().</span></p><p>New global-context property: <span class="term">UsersPasswordsPolicies</span>.</p><p>New property: <span class="term">AuthenticationSecondFactorSettingsTemplates</span>.<span class="term">UsersPasswordsPolicies</span>.</p><p>New properties for the <span class="term">InfobaseUser </span>object: <span class="term">PasswordsPolicyName</span>, <span class="term">PasswordSettingDate</span>, and <span class="term">WrittenPasswordSettingDate</span>.</p></td><td>These features were not provided.<p>Some of the features could be implemented in 1C:Enterprise language, which allowed bypassing of requirements.</p></td><td>Improved user password features, which resulted in overall better system security.</td></tr><tr title="Версия 8.3.17" class="tag_74"><td><a name="fbd2ba7e-717c-11ed-963f-0050569f678a"></a><a href="#" onclick="onTagClick(this, 74); return false;">Licensing system</a>.<br></td><td>The license owner address is hidden from the <span class="interface">About... </span>dialog box when the list of active (or activated) licenses is displayed. For licenses displayed in the <span class="interface">Infobase</span> and <span class="interface">Configuration</span> sections, addresses are not hidden for the rows obtained by previous 1C:Enterprise versions.</td><td>The license owner address was displayed in license information in the <span class="interface">About... </span>dialog box.</td><td>The license owner address is no longer displayed in license information in the <span class="interface">About... </span>dialog box.<p>
</p></td></tr></table><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="9f368936-eb6c-11e9-8371-0050569f678a">Transition from the previous version to the version 8.3.17</a></h2><ul><li title="Версия 8.3.17" class="tag_0"><a name="9f368937-eb6c-11e9-8371-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.17.
</li><li title="Версия 8.3.17" class="tag_0"><a name="9f368938-eb6c-11e9-8371-0050569f678a"></a>Some features that are added in version 8.3.17 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.17" class="tag_0"><a name="33299ba0-438e-11eb-8371-0050569f678a"></a>Dynamic configuration updates will not be available until infobase tables are restructured. You can restructure the infobase tables either verifying and repairing an infobase with the <span class="interface">Restructure infobase tables </span>mode enabled, or by making changes in the configuration that lead to the infobase restructuring.<p>
</p></li></ul><p><a href="#9f36892b-eb6c-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h1><a name="2c7299b4-8dd0-11e9-8371-0050569f678a">Version 8.3.16</a></h1><p title="Версия 8.3.16" class="tag_0"><a name="2c7299c2-8dd0-11e9-8371-0050569f678a"></a>Version 8.3.16 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#2c7299b5-8dd0-11e9-8371-0050569f678a">New functionality and changes</a></li><li><a href="#2c7299b6-8dd0-11e9-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#2c7299b7-8dd0-11e9-8371-0050569f678a">Optimization</a></li><li><a href="#2c7299b8-8dd0-11e9-8371-0050569f678a">Changes that affect system behavior</a></li><li><a href="#2c7299b9-8dd0-11e9-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#2c7299ba-8dd0-11e9-8371-0050569f678a">Renamed objects</a></li><li><a href="#2c7299bb-8dd0-11e9-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#2c7299bc-8dd0-11e9-8371-0050569f678a">Library updates
</a></li><li><a href="#2c7299bd-8dd0-11e9-8371-0050569f678a">Demo configuration changes</a></li><li><a href="#2c7299be-8dd0-11e9-8371-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#2c7299bf-8dd0-11e9-8371-0050569f678a">Transition from the previous version to the version 8.3.16</a></li></ul><h2><a name="2c7299b5-8dd0-11e9-8371-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.16" class="compat tag_2 tag_1"><td><a name="a10bb560-8dd0-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.15</span> is now implemented.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.14 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.15 or earlier can now run on version 8.3.16 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.16 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.15 after the migration to version 8.3.16, even if you disable the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.16" class="tag_29"><td><a name="efb53861-90e5-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Implemented Programming Training Version running on Linux and macOS.</td><td>Programming Training Version ran on Windows only.</td><td>Programming Training Version runs on all supported operating systems.</td></tr><tr title="Версия 8.3.16" class="tag_29 tag_18"><td><a name="1272a9e1-90e7-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br></td><td>OS X family (version 10.11 or under) is no longer supported. Client application runs on macOS only (version 10.12 or above).</td><td>Client application could run on OS X (version 10.8 or above).</td><td>Outdated operating systems are no longer supported.</td></tr><tr title="Версия 8.3.16" class="tag_6 tag_10"><td><a name="d5baafdf-8deb-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>In client/server mode, you can now limit the number of logon attempts with an incorrect password.<p>The following parameters are implemented for the infobase: maximum number of failed authentication attempts before a user is blocked; a time interval during which a user who made a threshold number of authentication attempts cannot attempt authentication again; username suffixes that should be used if it is necessary to authenticate as a blocked user.</p><p>New global context property: <span class="term">AuthenticationLock</span>.</p><p>New form to view authentication locks in Designer (<span class="interface">Administration </span>– <span class="interface">Authentication locks</span>). This command is available only to a user with administrative rights.</p><p>Implemented the following event log events:</p><ul><li><span class="interface">Users. Authentication lock </span>(<span class="term">_$User$_.AuthenticationLock</span>).</li><li><span class="interface">Users. Authentication unlock </span>(<span class="term">_$User$_.AuthenticationUnlock</span>).</li><li><span class="interface">Users. Authentication unlock error </span>(<span class="term">_$User$_.AuthenticationUnlockError</span>).</li></ul><p>
New data of event log events:</p><ul><li><span class="interface">Infobase. Infobase parameters change.</span></li><li><span class="interface">Session</span>. <span class="interface">Authentication.</span></li><li><span class="interface">Access</span>. <span class="interface">Access </span>(only for a Z version)</li><li><span class="interface">Access</span>. <span class="interface">Access </span><span class="interface">denied</span>.</li></ul><p>
In the display form of the list of active users of Designer, you can now view a column with characteristics of user data separation.</p></td><td>This feature was not provided.<p>The platform did not prevent someone from guessing the password by going through the options.</p></td><td>Reduced the likelihood of guessing the infobase user password by going through the options.</td></tr><tr title="Версия 8.3.16" class="tag_45"><td><a name="755bd556-926e-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>New feature: the query language now supports grouping sets.<p>Upgrade: the query language now supports keywords <span class="term">GROUPING SETS</span> for sentence <span class="term">GROUP BY</span>.</p><p>New query language function that allows you to determine whether a function parameter can be grouped: <span class="term">GroupedBy()</span>.</p></td><td>This feature was not provided.</td><td>Upgrade: grouping by several field sets is faster because grouping is performed per table scan.</td></tr><tr title="Версия 8.3.16" class="tag_63 tag_25"><td><a name="88c5edf6-9274-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When using charts, you can now save a map between an object (displayed by different charts) and its color.<p>For charts displayed on the form, 1C:Enterprise code is required for this. For the data composition system, this feature is available using settings.</p><p>A map between an object and its color is saved to the settings system storage.</p><p>Implemented the <span class="term">Chart.FillSeriesColors()</span> method.</p><p>For objects </p><p><span class="term">DataCompositionOutputParametersValues</span>, </p><p><span class="term">DataCompositionGroupOutputParametersValues</span>, <span class="term">DataCompositionChartOutputParametersValues</span>, and</p><p><span class="term">DataCompositionAreaChartAppearance</span>, implemented properties <span class="term">ChartType</span>.<span class="term">ColorsSaving </span>and <span class="term">ChartType</span>.<span class="term">ColorsSavingKey</span>. New property: <span class="term">ProcessorOfDataCompositionResultOutputToSpreadsheetDocument</span>.<span class="term">AppearanceForValues</span>. New property: <span class="term">DataCompositionAreaChartGroupTemplate</span>.<span class="term">Presentation</span>.</p></td><td>This feature was not provided.<p>The same object could be displayed by charts with a different color, resulting in bad report readability.</p></td><td>The same object can be displayed by charts with the same color that helps make charts look better and more informative.<p>
</p></td></tr><tr title="Версия 8.3.16" class="compat tag_4 tag_1"><td><a name="11984e84-929c-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>When using the collaboration system, you can now share your PC screen on a video call.<p>In the web client, screen sharing is available only in Google Chrome and Mozilla Firefox. In the web client, Google Chrome supports sharing of the current web browser tab.</p></td><td>This feature was not provided.</td><td>Expanded the collaboration system capabilities.</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="4fe52b84-929d-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>On setting the <span class="term">CollaborationSystemMessage.Text </span>property of the <span class="term">FormattedString </span>type from 1C:Enterprise code, appearance is saved (except pictures to be deleted). This message is displayed by the system considering its formatting. A message with appearance cannot be created interactively.<p>Smileys set by emoticons (Unicode characters) are now supported.</p></td><td>This feature was not provided.</td><td>New operations with collaboration system messages.</td></tr><tr title="Версия 8.3.16" class="tag_10 tag_6"><td><a name="535709c4-92a0-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>You can now get a server cluster version using program administration interfaces. Getting a server cluster version is only available if a server cluster is running 1C:Enterprise version 8.3.11 or above.<p>Implemented <span class="term">ServerAdministration</span>.<span class="term">GetVersion</span><span class="term">()</span> method.</p><p>Implemented the<span class="interface"> </span><span class="interface">agent version</span><span class="interface"> </span>command of the rac utility.</p></td><td>This feature was not provided.</td><td>On program administration of the server cluster, you can now determine which features can or cannot be used depending on 1C:Enterprise version the server cluster is running on.</td></tr><tr title="Версия 8.3.16" class="tag_60 tag_113 tag_85"><td><a name="24125cc4-92a3-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br><a href="#" onclick="onTagClick(this, 113); return false;">Formatted document</a>.<br><a href="#" onclick="onTagClick(this, 85); return false;">Processing PDF documents</a>.<br></td><td>On saving a PDF document, the OpenType font is now available if it is used in appearance of the document to be saved.</td><td>This feature was not provided. On saving to the PDF format, only TrueType fonts were embedded.</td><td>Improved compatibility of PDF documents generated by 1C:Enterprise with different PDF document display devices.</td></tr><tr title="Версия 8.3.16" class="compat tag_63 tag_1"><td><a name="d25ac9e4-92a6-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>You can now interactively change values displayed by charts of the following kinds: a line, a step, and an area (including summarized and normalized series). This feature is not provided in 8.3.15 compatibility mode.<p>Implemented the <span class="term">ValuesEditMode </span>property for <span class="term">Chart </span>and <span class="term">ChartSeries </span>objects. New property: <span class="term">ChartValue</span>.<span class="term">EditMode</span>. New event for the chart form field extension: <span class="term">OnEditValue</span>.</p><p>The form field extension event for the <span class="term">OnChangeAreaContent </span>spreadsheet document will be called upon interactive editing of a chart and a Gantt chart inserted into the spreadsheet document. The <span class="term">AdditionalParameters </span>parameter is implemented in the handler.</p><p>This change is not implemented in 8.3.15 compatibility mode. </p></td><td>This feature was not provided.<p>The form field extension event for the <span class="term">OnChangeAreaContent </span>spreadsheet document was not called upon interactive editing of a Gantt chart inserted into the spreadsheet document.</p></td><td>Improved chart interactivity.</td></tr><tr title="Версия 8.3.16" class="tag_28"><td><a name="87afe9c4-92ab-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>You can now embed the web client in third-party sites and ensure the web client interacts with these sites.<p>New global context property: <span class="term">ExternalSiteWindow</span>. Implemented the <span class="term">ClientApplicationMainWindowMode</span>.<span class="term">EmbeddedWorkplace </span>system enumeration value.</p><p>Implemented the <span class="term">MainWindowMode </span>command-line command for the client application and web client.</p><p>Implemented the following access rights, which allow you to start the client application in a main window mode: <span class="term">StandardMainWindowMode</span>, <span class="term">MainWindowModeWorkplace</span>, <span class="term">MainWindowModeEmbeddedWorkplace</span>, <span class="term">MainWindowModeFullScreenWorkplace</span>, and <span class="term">MainWindowModeKiosk</span>.</p><p>Implemented Embedded WebClient API, which allows a site to interact with the web client.</p></td><td>This feature was not provided.<p>It was impossible to embed the web client in a third-party site.</p></td><td>Advanced web client features.</td></tr><tr title="Версия 8.3.16" class="tag_60 tag_85"><td><a name="849d84a4-92af-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br><a href="#" onclick="onTagClick(this, 85); return false;">Processing PDF documents</a>.<br></td><td>New feature: you can save a spreadsheet document to PDF/A-2 and PDF/A-3 (versions of the PDF/A format used for long-term storage).<p>New values for the <span class="term">SpreadsheetDocumentFileType </span>system enumeration:<span class="term"> </span><span class="term">PDF</span><span class="term">_A_2</span> and <span class="term">PDF_A_3</span>.</p><p>Implemented two syntax options for the <span class="term">SpreadsheetDocument</span>.<span class="term">Write</span><span class="term">()</span> method. Implemented the Attachments parameter for the <span class="term">SpreadsheetDocument</span>.<span class="term">BeginWriting</span><span class="term">()</span> method.</p><p>New objects: <span class="term">ReadPDF </span>and <span class="term">WritePDF</span>.</p></td><td>It was possible to save a spreadsheet document to PDF/A-1 only.</td><td>Expanded spreadsheet document export features.</td></tr><tr title="Версия 8.3.16" class="tag_114"><td><a name="ee0567a4-92af-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 114); return false;">Charts of characteristic types</a>.<br></td><td>Implemented the <span class="term">FullDescription()</span> method for <span class="term">ChartOfCharacteristicTypesRef </span>and <span class="term">ChartOfCharacteristicTypesObject </span>objects.</td><td>This feature was not provided.</td><td>Unified behavior of the chart of characteristic types and the catalog for getting an item presentation based on hierarchy.</td></tr><tr title="Версия 8.3.16" class="tag_26"><td><a name="1fe416c4-92b2-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>New feature: you can write a spreadsheet document (using the <span class="term">SpreadsheetDocument.Write()</span> method in an option for writing to a stream) to a stream as XLSX.</td><td>It was not possible to write a spreadsheet document (using the <span class="term">SpreadsheetDocument.Write()</span> method in an option for writing to a stream) to a stream as XLSX.</td><td>Expanded features of spreadsheet document export to streams.</td></tr><tr title="Версия 8.3.16" class="tag_38"><td><a name="acb9f184-92b4-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>You can now create the following objects in a сonfiguration extension:<ul><li>Constants</li><li>Functional options and functional option parameters</li><li>Filter criteria.</li></ul><p>
You can now extend the following:</p><ul><li>Adopted functional options (using own and adopted objects)</li><li>Adopted filter criteria using attributes of own extension objects.</li></ul></td><td>These features were not provided.</td><td> Extended configuration extension options.</td></tr><tr title="Версия 8.3.16" class="tag_115"><td><a name="822699e4-92b5-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>New feature: you can generate a planner context menu from 1C:Enterprise code and specify an action called upon clicking (depending on the click area).<p>New events for the form field extension for the planner field: <span class="term">GenerateCommandsProcessing</span>, </p><p><span class="term">DimensionItemClick</span>, </p><p><span class="term">TimeScaleItemClick</span>, </p><p>and <span class="term">WrappedTimeScaleHeaderClick</span>.</p><p>New properties for the form field extension for the planner field: <span class="term">TimeScaleItemHyperlink</span>, <span class="term">DimensionItemHyperlink</span>, and </p><p><span class="term">WrappedTimeScaleHeaderHyperlink</span>.</p></td><td>These features were not provided.</td><td>New planner features.</td></tr><tr title="Версия 8.3.16" class="compat tag_115 tag_1"><td><a name="1f7847d6-9340-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>New feature: you can use a search string for a form table that displays a value table, a value tree, or a value list. <p>Search history is stored in the system settings storage with the following key: <span class="interface">Common/TableSearchHistory/&lt;Form name&gt;.&lt;Table name&gt;.</span></p><p>This change is not implemented in 8.3.15 compatibility mode.</p><p>New feature: you can use the <span class="interface">Find by current value</span> command in all form tables ignoring сonfiguration compatibility mode.</p></td><td>The search string was available only for form tables that displayed a dynamic list. In other tables, search was done using the standard dialog box, which performed positioning.<p>Search by current value was not available.</p></td><td>Improved search in tables of managed forms, including a pictorial view of searching in the table.</td></tr><tr title="Версия 8.3.16" class="tag_25 tag_79"><td><a name="466f7177-967c-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>New feature: you can use pictures for conditional appearance of reports in the data composition system. New property: <span class="term">DataCompositionAppearance</span>.Picture.<p>New pictures in the picture library: <span class="term">AppearanceGreenUpTriangle</span>, <span class="term">AppearanceYellowHyphen</span>, <span class="term">AppearanceRedDownTriangle</span>, <span class="term">AppearanceGreenUpArrow</span>, <span class="term">AppearanceGreenUpInclineArrow</span>, <span class="term">AppearanceYellowUpInclineArrow</span>, <span class="term">AppearanceYellowRightArrow</span>, <span class="term">AppearanceYellowDownInclineArrow</span>, <span class="term">AppearanceRedDownArrow</span>, <span class="term">AppearanceRedDownInclineArrow</span>, <span class="term">AppearanceGrayUpArrow</span>, <span class="term">AppearanceGrayUpInclineArrow</span>, <span class="term">AppearanceGrayRightArrow</span>, <span class="term">AppearanceGrayDownInclineArrow</span>, <span class="term">AppearanceGrayDownArrow</span>, <span class="term">AppearanceGreenCircle</span>, <span class="term">AppearanceYellowCircle</span>, <span class="term">AppearanceRedCircle</span>, <span class="term">AppearanceBlackCircle</span>, <span class="term">AppearanceCharCheckBox</span>, <span class="term">AppearanceCharExclamationMark</span>, <span class="term">AppearanceCharCross</span>, <span class="term">AppearanceCheckBox</span>, <span class="term">AppearanceExclamationMark</span>, <span class="term">AppearanceCross</span>, <span class="term">AppearanceGreenFlag</span>, <span class="term">AppearanceYellowFlag</span>, <span class="term">AppearanceRedFlag</span>, <span class="term">AppearanceFullStar</span>, <span class="term">AppearanceHalfFullStar</span>, <span class="term">AppearanceEmptyStar</span>, <span class="term">AppearanceFilledCircle</span>, <span class="term">AppearanceThreeQuartersFilledCircle</span>, <span class="term">AppearanceTwoQuartersFilledCircle</span>, <span class="term">AppearanceOneQuarterFilledCircle</span>, <span class="term">AppearanceEmptyCircle</span>, <span class="term">AppearanceFourFilledBoxes</span>, <span class="term">AppearanceThreeFilledBoxes</span>, <span class="term">AppearanceTwoFilledBoxes</span>, <span class="term">AppearanceOneFilledBox</span>, and <span class="term">AppearanceEmptyBoxes</span>.</p><p>In conditional appearance, you can use only the above pictures from the picture library.</p><p>If the сonfiguration already has pictures with the same names, a picture from the сonfiguration is added to the collection and a warning is generated upon сonfiguration update.</p></td><td>This feature was not provided. Conditional appearance of the data composition system did not allow you to use pictures for conditional appearance of reports.</td><td>Specifying pictures in conditional appearance of reports built using the data composition system is now easier.</td></tr><tr title="Версия 8.3.16" class="compat tag_79 tag_1"><td><a name="4303d7f7-967d-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>For common pictures, you can now specify that a common picture is used:<ul><li>To select a picture in a cell, an image, or a header/footer of a spreadsheet document in 1C:Enterprise mode. New property: <span class="term">CommonPicture.ChoiceAvailability</span>.</li><li>To select to use reports of the data composition system in conditional appearance. New property: <span class="term">CommonPicture.AppearanceAvailability</span>.</li></ul><p>Property <span class="term">CommonPicture.ChoiceAvailability</span> is ignored in 8.3.15 compatibility mode. Property CommonPicture.AppearanceAvailability is ignored in 8.3.15 compatibility mode.</p></td><td>This feature was not provided.</td><td>New feature: you can specify which common pictures can be used when working with a spreadsheet document in 1C:Enterprise mode and conditional appearance. As a result, there are less pictures a user can select from in these situations.</td></tr><tr title="Версия 8.3.16" class="tag_56"><td><a name="05776f37-968e-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>New feature: the platform supports XSD schemas containing types, in which attributes are defined via references to global attributes, but overriding such properties as <span class="term">default </span>or <span class="term">fixed </span>ones.</td><td>Upon trying to use in the platform XSD schemas containing types, in which attributes were defined via references to global attributes, but overriding such properties as <span class="term">default </span>or <span class="term">fixed </span>ones, errors occurred when checking the XDTO model, and such schemas were not available.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="compat tag_63 tag_25 tag_1"><td><a name="4c6aa0e2-9813-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>You can now build combo charts and display a secondary value scale for the following chart types: <ul><li><span class="term">Column</span></li><li><span class="term">Bar</span></li><li><span class="term">NormalizedColumn</span></li><li><span class="term">NormalizedBar</span></li><li><span class="term">StackedColumn</span></li><li><span class="term">StackedBar</span></li><li><span class="term">Line</span></li><li><span class="term">Step</span></li><li><span class="term">StackedLine</span></li><li><span class="term">Area</span></li><li><span class="term">StackedArea</span></li><li><span class="term">NormalizedArea</span></li><li><span class="term">Column3D</span></li><li><span class="term">StackedColumn3D</span></li><li><span class="term">NormalizedColumn3D</span></li><li><span class="term">Bar3D</span></li><li><span class="term">StackedBar3D</span></li><li><span class="term">NormalizedBar3D</span></li></ul><p> </p><p>Implemented animation upon chart value change.</p><p>Implemented the <span class="term">SecondaryValuesAxis </span>property for <span class="term">ChartPlotArea </span>and <span class="term">Chart </span>objects. New property: <span class="term">ChartScale</span>.<span class="term">Display</span>. New properties for the <span class="term">ChartSeries </span>object: <span class="term">GraphicalPresentationType</span>, <span class="term">AccumulationType</span>, <span class="term">AccumulationGroup</span>, <span class="term">UsedValuesAxis</span>, <span class="term">ValuesFormatInLabels</span>, <span class="term">PercentageFormatInLabels</span>, and <span class="term">FormatInDataTable</span>.</p><p>The <span class="term">ChartSeries</span>.<span class="term">Indicator </span>property is deprecated and supported for compatibility purposes. Use the <span class="term">ChartSeries</span>.<span class="term">GraphicalPresentationType </span>property instead.</p><p>The <span class="term">Chart</span><span class="term">.</span><span class="term">ChartType </span>property value is <span class="term">Column </span>by default.</p><p>The <span class="term">Chart</span>.<span class="term">Outline </span>property value is <span class="term">False </span>by default.</p><p>New properties for objects <span class="term">DataCompositionAreaChartGroupAppearance </span>and <span class="term">DataCompositionAppearance</span>: <span class="term">GraphicalPresentationTypeInChart</span>, <span class="term">AccumulationTypeInChart</span>, and <span class="term">UsedValuesAxisInChart</span>. New property: <span class="term">DataCompositionAreaChartGroupAppearance</span>.<span class="term">AccumulationGroupInChart</span>. For objects </p><p><span class="term">DataCompositionOutputParametersValues</span>,</p><p><span class="term">DataCompositionGroupOutputParametersValues</span>, <span class="term">DataCompositionChartOutputParametersValues</span>, and</p><p><span class="term">DataCompositionAreaChartAppearance</span>, implemented parameters <span class="term">ChartType</span>.<span class="term">SecondaryValuesScale</span> and <span class="term">ChartType</span>.<span class="term">SecondaryValuesAxis</span>.</p><p>The <span class="term">ChartType</span>.<span class="term">IndicatorInChart</span> parameter is deprecated and supported for compatibility purposes. Use the <span class="term">ChartType</span>.<span class="term">GraphicalPresentationTypeInChart</span> parameter instead.</p><p>New parameters for the <span class="term">DataCompositionAreaChartGroupAppearance</span> object: <span class="term">ValuesFormatInChartLabels</span> and <span class="term">FormatInChartDataTable</span>.</p><p>This change is not implemented in 8.3.15 compatibility mode.
</p></td><td>It was impossible to build combo charts and display a secondary value scale.<p>The <span class="term">Chart</span>.<span class="term">ChartType</span> property value is <span class="term">Column3D</span> by default.</p><p>The <span class="term">Chart</span>.<span class="term">Outline</span> property value is <span class="term">True</span> by default.</p></td><td>New chart features.</td></tr><tr title="Версия 8.3.16" class="tag_6"><td><a name="e6be6f3b-9d70-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>You can now start backup working processes. A backup working process is started in advance and server cluster overhead is synchronized for it. This feature allows you to reduce the time spent on switching the client application to a new working process in case of unexpected termination of the working process serving this client application.<p>A flag indicating whether backup is required is set for the infobase. The number of backup working processes is calculated from the <span class="interface">Number of infobases per process</span> working server property.</p><p>New properties: <span class="term">AdministrationInfobase</span>.<span class="term">WorkingProcessesBackup </span>and <span class="term">AdministrationWorkingProcess</span>.<span class="term">Backup</span>. </p><p>The following Java-based methods are implemented in the administration server interface: <span class="term">IWorkingProcessInfo</span>.<span class="term">isReserve</span><span class="term">()</span>, <span class="term">IInfobaseInfo</span>.<span class="term">getReserveWorkingProcesses</span><span class="term">()</span>, and <span class="term">IInfobaseInfo</span>.<span class="term">setReserveWorkingProcesses</span><span class="term">()</span>.</p><p>The following items are implemented for the cluster service command-line utility (<span class="interface">rac</span>):</p><ul><li><span class="term">Reserve-working-process</span> parameter for <span class="term">infobase insert </span>and <span class="term">infobase update </span>commands.</li><li><span class="term">Reserve-working-processes</span> field for the <span class="term">infobase info</span> command result.</li><li><span class="term">Reserve</span> field for the <span class="term">process info</span> command result.</li></ul></td><td>This feature was not provided.<p>A new working process was started only after the current working process was terminated, which could lead to significant time delays upon client application reconnection. From the user's point of view, it looked like the client application interface froze at the time of connection to a new working process.</p></td><td>Reduced time delays resulting from switching the client application to a new working process. Improved application reactivity.
</td></tr></table><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299b6-8dd0-11e9-8371-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.16" class="tag_115"><td><a name="fd399416-927a-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the client application form table that displays the value tree (including the <span class="interface">All functions</span><span class="interface"> </span>dialog box), search using the search string is done considering a parent and by words.<p>In the history form, record date and time are no longer involved in search.</p></td><td>In the client application form table that displays the value tree, search was done ignoring a parent and by substring.<p>In the history form, record date and time were involved in search.</p></td><td>Improved search in client application form tables that display trees (including in the <span class="interface">All functions</span> dialog box).</td></tr><tr title="Версия 8.3.16" class="tag_28 tag_78"><td><a name="1a5ecad6-927e-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>Upgrade: security check of access to the file system and clipboard when accessing the web client in Google Chrome and Mozilla Firefox (including web browser extensions and file system extensions) is updated.<p>Once the web browser extension and the file system extension are updated, if it is required to get access to the file system, a user will have to confirm that they trust the site (where the web client is published) to use the file system on their local computer. After that, there are no question until this permission is revoked (using settings of the web browser extension). If the user refuses to trust it, the old mechanism for getting permissions is used (a separate request per action).</p><p>Clipboard operations are allowed accordingly.</p><p>Permissions are stored broken down by site addresses where web clients are published.</p></td><td>In the web client, a separate question was displayed to a user upon each file operation, which was not user-friendly.</td><td>Simplified file operations in the web client regarding the user permission on operations with the file system and clipboard.</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="7d59ac64-929a-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: the user history now displays whether this user participates in a context conversation regarding an object associated with a form in the history.<p>Optimized user history opening.</p></td><td>The user history did not display whether this user participated in a context conversation regarding an object associated with a form.</td><td>In the history, it is now easier for a user to find object forms, in the context conversation of which this user was a message recipient.</td></tr></table><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299b7-8dd0-11e9-8371-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.16" class="tag_14 tag_6"><td><a name="1f3670c4-92ac-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved performance of 1C:Enterprise platform running on Windows 8 or above when the client application and the server cluster are on the same computer.</td><td>Performance of 1C:Enterprise platform running on Windows 8 or above when the client application and the server cluster were on the same computer was less optimal. Interprocess interactions took more time.</td><td>Improved performance of 1C:Enterprise running on Windows 8 or above.</td></tr><tr title="Версия 8.3.16" class="tag_26"><td><a name="40e80864-92b0-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Reduced amount of RAM used by a spreadsheet document that contains many text cells.</td><td>A spreadsheet document with many text cells needed more space in RAM.</td><td>A spreadsheet document now uses smaller amount of RAM.</td></tr><tr title="Версия 8.3.16" class="tag_6"><td><a name="d7e5a124-92b3-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved performance of the server cluster when working with a large amount of session data. Managed form opening, a context server call, and temporary storage operations take less time now.<p>New technological log event: <span class="term">&lt;SDGC&gt;.</span></p></td><td>The server cluster spent more time on handling a large amount of session data. Managed form opening, a context server call, and temporary storage operations took more time.</td><td>Improved server cluster performance.</td></tr><tr title="Версия 8.3.16" class="tag_42"><td><a name="18d71d97-9685-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br></td><td>Improved performance of a virtual table of accumulation register balance.</td><td>When using a virtual table of accumulation register balance, more time was spent on getting the query result.</td><td>Improved performance of a virtual table of accumulation register balance.
</td></tr><tr title="Версия 8.3.16" class="compat tag_45 tag_1"><td><a name="3a7bacd7-9686-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Optimized execution of query in client/server infobase mode, that includes the query language operator <span class="term">IN </span>with a list of values, if the left section of <span class="term">IN </span>operator contains a reference type field that includes several main tables, and the list of values contains references to different tables (from the list of composite type values) but not the <span class="term">Undefined </span>value.<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>The query in client/server infobase mode, that includes the query language operator <span class="term">IN </span>with a list of values, if the left section of <span class="term">IN </span>operator contains a reference type field that includes several main tables, and the list of values contains references to different tables (from the list of composite type values) but not the <span class="term">Undefined </span>value, took more time to execute.</td><td>Optimized execution of queries containing <span class="term">IN </span>operator with composite type fields.</td></tr><tr title="Версия 8.3.16" class="tag_37"><td><a name="44fe6f17-bd0a-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Optimized retrieving of email message headers using the <span class="term">InternetMailMessage.GetHeaderField()</span> method.</td><td>Retrieving email message headers using the <span class="term">InternetMailMessage.GetHeaderField()</span> method took a considerable amount of time.
</td><td>Optimized email message headers retrieving.</td></tr></table><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299b8-8dd0-11e9-8371-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.16" class="tag_64"><td><a name="6805f01f-8de8-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Upgrade: client applications (except the web client) running on macOS, Linux, and Windows are switched to graphics based on the Cairo library.</td><td>Client applications (except the web client) running on macOS, Linux, and Windows used their own graphics based on different technologies and libraries in each operating system.</td><td>Unified and optimized user interface display in supported operating systems.</td></tr><tr title="Версия 8.3.16" class="tag_81"><td><a name="1da3b91f-8dea-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>In the dialog box for publishing the сonfiguration on a web server, labels now comply with the current client applications of the platform.</td><td>In the dialog box for publishing the сonfiguration on a web server, labels did not consider the mobile client.</td><td>The dialog box for publishing the сonfiguration on a web server considers the mobile client.</td></tr><tr title="Версия 8.3.16" class="compat tag_21 tag_1"><td><a name="7223d6e4-92a9-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>New feature: full-text search by hashtag became available (strings of the #Word format, from the # character to the first space).<p>To apply fuzzy search (both in interactive mode and search from 1C:Enterprise code using the <span class="term">FullTextSearchManager </span>object), use the ~ character.</p><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>Search by hashtag was not supported but it was possible to find a hashtag value (the word after the # character) in the usual way or by double quoting a hashtag to search for.<p>The # character was used for fuzzy search.
</p></td><td>You can now hashtag objects involved in full-text search. As a result, it became possible to simply find several different types of objects grouped by hasgtag only.</td></tr><tr title="Версия 8.3.16" class="tag_110"><td><a name="154693e4-92ae-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br></td><td>If the access rights do not allow saving a spreadsheet document, a text document, a graphic chart, a geographical diagram, a package of displayed documents or an HTML document to the file, but after creating these objects, privileged mode was enabled, then the file can be saved.</td><td>If access rights did not allow saving a spreadsheet document, a text document, a graphic chart, a geographic diagram, a package of displayed documents or an HTML document to a file, then enabling privileged mode was ignored and the the files could not be saved.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="compat tag_107 tag_1"><td><a name="6281e236-9344-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 107); return false;">Input by string</a>.<br></td><td>When using input by string for a managed application, all searched words are highlighted in search results if full-text search is not used for input by string or full-text search failed with an error.<p>If full-text search in data is used for input by string, the <span class="interface">The method of searching for the specified string during the input by string</span> setting is ignored upon successful application of full-text search, the searched text is always split into words, and search is based on the beginning of the words.</p><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>When using input by string for a managed application, if full-text search was not used for input by string or full-text search failed with an error, two consecutive occurrences of the same string were not highlighted and only the first occurrence of the searched word was highlighted in the first half of results (when searching for one word).</td><td>Improved search result highlighting for input by string.</td></tr><tr title="Версия 8.3.16" class="tag_64"><td><a name="b0081177-967f-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>With the Windows operating system, stability and responsiveness of the client application are improved when working with unavailable printers.</td><td>With the Windows operating system, there were some issues when working with unavailable printers, such as unexpected shutdown of the client application and a significant slowdown upon client application start.</td><td>With the Windows operating system, stability and responsiveness of the client application are improved when working with unavailable printers.</td></tr><tr title="Версия 8.3.16" class="tag_6"><td><a name="4939f3d7-9690-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td><b>This change is rolled back.</b><p>New feature: parallel recalculation of register totals is available upon infobase restructuring, testing, and repair. System background jobs are used for recalculation. ID of such a background job is <span class="term">SystemBackgroundJob.RecalcTotals</span>. Implemented the <span class="interface">Number of totals recalculation </span>job parameter for the<span class="interface"> </span><span class="interface">Infobase parameters</span><span class="interface"> </span>dialog box. There are 4 recalculation background jobs by default.</p><p>New global context methods: <span class="term">GetTotalsRecalculationJobsCount()</span> and <span class="term">SetTotalsRecalculationJobsCount()</span>.</p></td><td>Register totals were recalculated sequentially upon infobase restructuring, testing, and repair for all required infobase registers.</td><td>New feature: totals are recalculated faster upon infobase restructuring, testing, and repair.</td></tr><tr title="Версия 8.3.16" class="tag_51"><td><a name="8a164862-982f-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>You can now use form item additions in automated testing. Implemented the <span class="term">FormItemAdditionToTest </span>object.<p>For the <span class="term">FormTableToTest </span>object, the result returned by <span class="term">GetSubobjects()</span>, <span class="term">GetObject()</span>, <span class="term">FindObjects()</span>, and <span class="term">FindObject() </span>methods can include objects of the <span class="term">FormItemAdditionToTest </span>type.</p><p>For the <span class="term">FormTableToTest</span>.<span class="term">NavigateLevelDown()</span> method, implemented the <span class="term">RowDetails </span>parameter that allows you to specify presentation of a child group to go to.</p><p>For the <span class="term">FormTableToTest</span>.<span class="term">NavigateLevelUp()</span> method, implemented the <span class="term">RowDetails </span>parameter that allows you to specify presentation of a parent group to go to.</p><p>For the <span class="term">FormTableToTest</span>.<span class="term">Expanded()</span> method, implemented the <span class="term">RowDetails </span>parameter that allows you to specify presentation of a row of a table, for which it is necessary to check whether this row is collapsed or expanded.</p><p>For the <span class="term">FormTableToTest</span>.<span class="term">CanExpand()</span> method, implemented the <span class="term">RowDetails </span>parameter that allows you to specify presentation of a table row, for which the expanding feature is being checked.</p><p>Implemented the <span class="term">FormFieldToTest</span>.<span class="term">GetStateDisplay()</span> function that returns the current state of a spreadsheet document field.</p><p>Implemented the <span class="term">ApplicationToTest</span>.<span class="term">WaitForState</span><span class="term">()</span> function intended for waiting within the specified time.</p><p>Implemented the <span class="term">FormGroupToTest</span>.<span class="term">CurrentOpened()</span> function that returns a group status: collapsed or expanded.</p><p>Implemented the <span class="term">FormButtonToTest</span>.<span class="term">CurrentCheckBox</span><span class="term">()</span> function that indicates whether the button is pressed or displays the check box.</p><p>A reference to the function that will return the notification processing result to the platform can be passed to the <span class="term">ExecuteNotificationProcessing()</span> method now.
</p></td><td>These features were not provided.</td><td>Extended automated testing capabilities. New features of the Taxi interface are considered in the functionality.</td></tr><tr title="Версия 8.3.16" class="tag_115 tag_38"><td><a name="ee9b39a2-9832-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The adopted form editor now displays changed and unchanged adopted form items with different colors.<p>The form editor command that allows you to display only changed adopted and own form items in the form item tree is now available.</p><p>The extension object property panel now displays properties of a сonfiguration object changed in the extension in relation to the extendable сonfiguration with another color.</p><p>The extension object property panel now has a command that shows only properties that were changed in relation to the extendable сonfiguration.</p></td><td>In the adopted form editor, it was impossible to hide unchanged adopted items in the form item tree. Form items were not distinguished by color.<p>In the property panel, it was not possible to quickly distinguish between changed and unchanged properties of an adopted configuration object.</p></td><td>New feature: easier editing of adopted сonfiguration objects.</td></tr><tr title="Версия 8.3.16" class="compat tag_43 tag_1"><td><a name="51031f77-bd07-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The dynamic list does not support fields with different expressions for selection and filtering as key fields.<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>It was possible to use fields with different expressions for selection and filtering as the key fields of the dynamic list. In this case, the dynamic list operation could cause various hard-to-diagnose errors.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_26"><td><a name="bf03aab7-bd09-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When opening a spreadsheet document in Microsoft Office OpenXML (<span class="interface">*.xlsx</span>) or Microsoft Excel (<span class="interface">*.xls</span>) format in 1C:Enterprise, conditional formatting is only imported for the area of the source document that contains data. Conditional formatting import now has reduced RAM consumption.<p>When viewing a spreadsheet document obtained after import, there may be situations when the formatting of the resulting document differs from the source document (design of the document area that does not contain data).</p></td><td>When opening a spreadsheet document in Microsoft Office OpenXML (<span class="interface">*.xlsx</span>) or Microsoft Excel (<span class="interface">*.xls</span>) format in 1C:Enterprise, conditional formatting was not imported for the whole document. In this case, a session could abnormally terminate due to lack of RAM.</td><td>Improved 1C:Enterprise stability when importing spreadsheet documents in Microsoft Office OpenXML (<span class="interface">*.xlsx</span>) or Microsoft Excel (<span class="interface">*.xls</span>) format, when conditional formatting is set for the whole sheet, and not just for a meaningful area.</td></tr><tr title="Версия 8.3.16" class="compat tag_25 tag_1"><td><a name="0c9de310-bda5-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The type of data composition system field that results from using the query language aggregate functions <span class="term">SUM()</span> and <span class="term">AVERAGE()</span> will be an unlimited length number.<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>The type of data composition system field that resulted from using the query language aggregate functions <span class="term">SUM() </span>and <span class="term">AVERAGE()</span> was the type of field, which was used as parameter for these aggregate functions.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_19"><td><a name="868fd6f0-bdb0-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The data (<span class="term">Purpose </span>field) returned by the <span class="term">GetDBStorageStructureInfo</span><span class="term">()</span> global context method contains information that describes the tables that are created using the database copy functionality.</td><td>The data returned by the <span class="term">GetDBStorageStructureInfo()</span> global context method did not contain information that described the tables that are created using the database copy functionality. The <span class="term">Main </span>value was specified as the table purpose for all the tables after using the database copy functionality.</td><td>Eliminated unexpected system behavior.
</td></tr><tr title="Версия 8.3.16" class="compat tag_26 tag_1"><td><a name="dbd47a50-bdb8-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When displaying a spreadsheet document containing pictures in cells or pictures of the <span class="term">Picture </span>type:<ul><li>The <span class="term">AutoSizeIgnoreScale </span>value of the <span class="term">PictureSize </span>property of the spreadsheet document area or the spreadsheet document image is interpreted as the <span class="term">AutoSize </span>value.</li><li>The <span class="term">RealSizeIgnoreScale </span>value of the <span class="term">PictureSize </span>property of the spreadsheet document region or the spreadsheet document image is interpreted as the <span class="term">ActualSize </span>value.</li></ul><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>When displaying a spreadsheet document containing pictures in cells or pictures of the <span class="term">Picture </span>type, the system behaved as follows:<ul><li>A picture in a cell for which the <span class="term">PictureSize </span>property was set to <span class="term">AutoSizeIgnoreScale </span>or <span class="term">RealSizeIgnoreScale </span>was not displayed.</li><li>The height of the line, where there is a cell with a picture, for which the <span class="term">PictureSize </span>property is set to <span class="term">AutoSizeIgnoreScale</span>, was calculated based on the actual picture height. </li><li>In the <span class="interface">Taxi </span>interface, for a spreadsheet document picture of the <span class="term">Picture </span>type, for which the <span class="term">PictureSize </span>property is set to <span class="term">AutoSizeIgnoreScale </span>or <span class="term">RealSizeIgnoreScale</span>, the picture was displayed with a smaller size than it should.</li></ul></td><td>Corrected spreadsheet document pictures display.</td></tr><tr title="Версия 8.3.16" class="compat tag_59 tag_1"><td><a name="f02e3cd0-bdbc-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>The addon menu of the <span class="interface">Search management</span> form item contains only the appropriate commands, that is: search by current value, advanced search, search history, cancel search).<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>The addon menu of the <span class="interface">Search management</span> form item contained all the commands of the linked form table (similar to autofilling the table command bar). Visibility was turned off for "excess" commands.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_21 tag_6"><td><a name="6c651a9d-bdd1-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When the <span class="term">UpdateIndex()</span> method of the full-text search manager is called in the client/server infobase mode, preparatory actions are performed using the system background job (its parameters are similar to the system indexing background job). This background job runs on the same working server as the full-text search service. When you click the <span class="interface">Refresh Index</span> button of the<span class="interface"> Full-text search management </span>standard function, the system behavior will be the same.<p>If a single task is configured in the full-text search settings, it will be performed in a separate background job.</p></td><td>When the <span class="term">UpdateIndex()</span> method of the full-text search manager was called in the client/server infobase mode, preparatory actions were performed at the same computer the method was called from. <p>If a single indexing task was configured in the full-text search settings, it was performed in a common server execution thread.</p></td><td>Improved reliability and speed of full-text search indexing. All the indexing actions are performed on the working server, assigned for running the full-text search service.</td></tr></table><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299b9-8dd0-11e9-8371-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.16" class="tag_45"><td><a name="4827467f-8de5-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Upon query execution in the infobase file mode, if a number cannot be represented with the required accuracy, an exception is thrown.</td><td>Upon query execution in the infobase file mode, if a number cannot be represented with the required accuracy, a number where all digits are 9s is put in the query result.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_10"><td><a name="3779443f-8de6-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented Java 9 or later support for the administration server interaction interface from Java.</td><td>The administration server interaction interface from Java did not support Java version 9 or later. Only Java version 1.8 was supported.</td><td>Implemented support for modern Java versions.</td></tr><tr title="Версия 8.3.16" class="tag_116"><td><a name="cd17d15f-8de6-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>When running commands, the licensing utility sends unattended statistical information to 1C:Remote service by default. You can now deactivate this action when running one command using the <span class="term">--</span><span class="term">send-statistics</span> parameter.</td><td>The licensing utility did not interact with 1C:Remote service.</td><td>New feature: you can accumulate statistical information about the licensing utility activity.</td></tr><tr title="Версия 8.3.16" class="tag_104"><td><a name="adce9f7f-8de8-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>If a functional option is stored in a catalog, the functional option value is recalculated once a catalog item is deleted.</td><td>If a functional option was stored in a catalog, the functional option value was not recalculated once a catalog item was deleted and the code could get the old value of the functional option.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_28 tag_29"><td><a name="15df8341-90e3-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>When running on macOS, Google Chrome and Mozilla Firefox can now be used to work in the web client.</td><td>When running on macOS, only Safari could be used to work in the web client.</td><td>The list of supported web browsers for macOS is expanded.</td></tr><tr title="Версия 8.3.16" class="tag_28 tag_29"><td><a name="b8105361-90e3-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Ended support of Google Chrome versions 48 and earlier. The web client is supported in Google Chrome versions 49 and later.</td><td>Google Chrome versions 48 and earlier were supported.</td><td>Ended support for legacy Google Chrome versions.</td></tr><tr title="Версия 8.3.16" class="tag_28"><td><a name="a4dd9d01-90e5-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>On macOS, Google Chrome and Mozilla Firefox now support the file system extension and the add-in extension.<p>Implemented the add-in adapter library for Google Chrome and Mozilla Firefox running on macOS. Changes were made to development technology for add-ins (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>).</p></td><td>On macOS, Google Chrome and Mozilla Firefox did not support the file system extension and the add-in extension.</td><td>Advanced file operations on macOS using the web client.</td></tr><tr title="Версия 8.3.16" class="tag_78"><td><a name="d9a3a936-9286-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>The following methods are deprecated and supported for compatibility purposes (in all clent applications):<ul><li><span class="term">InstallFileSystemExtension()</span></li><li><span class="term">AttachFileSystemExtension()</span></li><li><span class="term">InstallCryptoExtension()</span></li><li><span class="term">AttachCryptoExtension()</span></li><li><span class="term">InstallAddIn()</span>.</li></ul><p>Use asynchronous equivalents of these methods instead.</p></td><td>The following methods could be used to create applied applications:<ul><li><span class="term">InstallFileSystemExtension()</span></li><li><span class="term">AttachFileSystemExtension()</span></li><li><span class="term">InstallCryptoExtension()</span></li><li><span class="term">AttachCryptoExtension()</span></li><li><span class="term">InstallAddIn()</span>.</li></ul></td><td>Deprecated methods are no longer supported.</td></tr><tr title="Версия 8.3.16" class="tag_78"><td><a name="753a4324-92b6-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>Once the <span class="term">BeginPutFilesToServer</span><span class="term">()</span> method or the <span class="term">BeginPutFileToServer()</span> method is called, there is no need to wait for the method completion to call these methods again.</td><td>Once the <span class="term">BeginPutFilesToServer()</span> method or the <span class="term">BeginPutFileToServer()</span> method was called, it was necessary to wait for completion of a previously executed call to call the methods again. A recall attempt led to an error in the thin client or waiting for completion of the previous call in the web client.</td><td>You can now import several files (or file groups) at the same time.</td></tr><tr title="Версия 8.3.16" class="compat tag_7 tag_1"><td><a name="47a53ff6-934b-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>You can now choose сonfiguration object properties to be passed to a database copy upon enabled standard replication. You can specify the following objects:<ul><li>For reference objects: attributes, tabular sections, and tabular section attributes.</li><li>For registers: resources and attributes.</li></ul><p>Other attributes (standard attributes, register changes, and common attributes included in separators) are always passed.</p><p>A query accessing attributes that are outside of the copy is executed on the main database.</p><p>If a database copy created in version 8.3.16 with restrictions on a composition of objects to copy is used, this copy will be considered deprecated when trying to use it on previous versions and refilled with data upon synchronization.</p><p>New properties for the <span class="term">DatabaseCopyManager </span>object: <span class="term">TabularSectionsUsage</span>, <span class="term">ValueStoragesUsage</span>, <span class="term">UnlimitedLengthStringsUsage</span>, and <span class="term">OtherFieldsUsage</span>.</p><p>The following properties of the DatabaseCopyManager object became writable: <span class="term">DBMSType</span>, <span class="term">DatabaseServer</span>, and <span class="term">Database</span>.</p><p>Parameters of the <span class="term">DatabaseCopyManager.Add()</span> method became optional.</p><p>New properties for the <span class="term">DatabaseCopyContentItem </span>object: <span class="term">Fields</span>, <span class="term">TabularSectionsUsage</span>, <span class="term">ValueStoragesUsage</span>, <span class="term">UnlimitedLengthStringsUsage</span>, and <span class="term">OtherFieldsUsage</span>.</p><p>The <span class="term">DatabaseCopyContentItem.Metadata </span>property became writable. The <span class="term">Item </span>parameter of<span class="term"> Insert() </span>and <span class="term">Add()</span> methods of the <span class="term">DatabaseCopyContent </span>object is mandatory. This change is not implemented in 8.3.15 compatibility mode.</p><p>The database copy management standard data processor is changed.
</p></td><td>All data of the selected сonfiguration objects was transferred to a database copy upon standard replication usage. It was not possuble to manage properties of data to transfer.<p>The following properties of the <span class="term">DatabaseCopyManager </span>object were read-only: <span class="term">DBMSType</span>, <span class="term">DatabaseServer</span>, and <span class="term">Database</span>.</p><p>Parameters of the <span class="term">DatabaseCopyManager.Add()</span> method were mandatory.</p><p>The <span class="term">DatabaseCopyContentItem.Metadata </span>property was read-only. The <span class="term">Item</span> parameter of <span class="term">Insert()</span> and <span class="term">Add()</span> methods of the <span class="term">DatabaseCopyContent </span>object was optional.</p></td><td>When generating data for a database copy, you can now set up content and volume of data stored in the database copy more precisely.</td></tr><tr title="Версия 8.3.16" class="compat tag_80 tag_1"><td><a name="43e7bf56-9369-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 80); return false;">External reports and data processors</a>.<br></td><td>The user will only be checked for having the <span class="term">View </span>right for the data processor/report used when calling <span class="term">GetForm()</span> method of the <span class="term">DataProcessorManager </span>and <span class="term">ReportManager </span>objects. The <span class="term">Use </span>right is no longer checked in this case.<p>There are no checks for access rights when calling the <span class="term">GetForm()</span> method of the <span class="term">DataProcessorManager </span>and <span class="term">ReportManager </span>objects.</p><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>When calling the <span class="term">GetForm</span><span class="term">()</span> method of the <span class="term">DataProcessorManager </span>and <span class="term">ReportManager </span>objects an exception was thrown if the user did not have the <span class="term">Use </span>right for the appropriate data processor or report.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="compat tag_25 tag_1"><td><a name="a97b4c56-936a-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Upgrade: you can apply conditional appearance to header areas of resource and totals fields. Conditional appearance can be managed both from 1C:Enterprise code and the selection form of the conditional appearance application area.<p>Implemented the following properties for the <span class="term">DataCompositionConditionalAppearanceItem </span>object: <span class="term">UseInResourcesFieldsHeader</span>, <span class="term">UseInOverallHeader</span>, and <span class="term">UseInOverallResourcesFieldsHeader</span>. These properties are not available in 8.3.15 compatibility mode.</p><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>It was impossible to apply conditional appearance to headers of resource and totals fields.</td><td>Advanced conditional appearance features for reports built using the data composition system.</td></tr><tr title="Версия 8.3.16" class="compat tag_43 tag_1"><td><a name="f659d376-936a-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>On getting data, the dynamic list checks whether all filter fields are present in available filter fields. When the first field unavailable for filter is found, an error is generated.<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>On getting data, the dynamic list did not check whether all filter fields were present in available filter fields.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="compat tag_117 tag_1"><td><a name="c92d5d75-965b-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>In infobase file mode, unique indexes are created the same way they are created in client/server mode of the infobase.<p>To force generation of indexes, change the compatibility mode and test and repair the infobase with the <span class="interface">Restructure infobase tables</span> check box selected..</p><p>When the compatibility mode is disabled, while writing data, index keys will be checked for uniqueness for indexes that were rebuilt upon testing and repair.</p><p>Upon testing and repair (in any compatibility mode), index key uniqueness is not checked.</p><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>In infobase file mode, non-unique indexes of infobase tables were created even when unique indexes were created in other supported DBMSs in the same case.<p>While writing data, 1C:Enterprise did not check index keys for uniqueness, which could cause problems with infobase migration from file mode to client/server mode.</p></td><td>Unified behavior of 1C:Enterprise in both file and client/server modes for operations with unique indexes. Reduced the number of issues that occur when migrating an infobase from file mode to client/server mode.</td></tr><tr title="Версия 8.3.16" class="compat tag_43 tag_1"><td><a name="a4398377-968d-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>When you press <span class="interface">Enter </span>(or double-click a row) in a row of a table linked to a dynamic list or when you call the <span class="term">ChangeRow</span>() form table method, a form table extension will open a form linked to this row whether or not there is the <span class="interface">Change </span>command in the table commands.<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>When you pressed <span class="interface">Enter </span>(or double-click a row) in a row of a table linked to a dynamic list or when you called the ChangeRow() form table method, a form table extension will open a form linked to this row:<ul><li>In version from 8.3.11 to 8.3.15 compatibility mode – only if the <span class="interface">Change </span>command is available in the table.</li><li>In version 8.3.10 compatibility mode – whether or not there is the <span class="interface">Change </span>command in table commands.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="compat tag_16 tag_1"><td><a name="55f87f82-97fd-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>If a record set of an independent information register is written to the infobase without replacement, records will be checked for uniqueness in data import mode (the <span class="term">DataExchange.Import</span> property is <span class="term">True</span>).<p>Refined the text of the error that occurs when data is not unique.</p><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>If a record set of an independent information register was written to the infobase without replacement, records were not checked for uniqueness in data import mode (the <span class="term">DataExchange</span>.<span class="term">Import </span>property was <span class="term">True</span>). This behavior could result in data inconsistency.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="compat tag_19 tag_1"><td><a name="15013e42-9811-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The behavior of the <span class="term">IN </span>query language operator with the subquery became the same when using any DBMS.<p>The results of such queries using IBM DB2, PostgreSQL, or Oracle Database might change. It is recommended that you analyze usage locations of the <span class="term">IN </span>operator with the subquery and rewrite these queries if necessary.</p><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>The behavior of the <span class="term">IN </span>query language operator with the subquery depended on the DBMS the query was executed on.</td><td>The result of the <span class="term">IN </span>query language operator with the subquery does not depend on the used DBMS anymore.<p>When using PostgreSQL, reduced the time spent on executing queries that contain the <span class="term">IN </span>operator with the subquery.</p></td></tr><tr title="Версия 8.3.16" class="tag_45"><td><a name="ec30cda2-981a-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Upon addition or subtraction in the query language, if the left operand of the operation could not be <span class="term">NULL </span>but the right operand could be <span class="term">NULL</span>, it is assumed that the operation result can be <span class="term">NULL</span>.</td><td>Upon addition or subtraction in the query language, if the left operand of the operation could not be <span class="term">NULL </span>but the right operand could be <span class="term">NULL</span>, it was assumed that the operation result could not be <span class="term">NULL</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_6"><td><a name="2e1e7ab1-98c4-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>In client/server mode, you can now specify roles to apply in a session for a security profile when switching to privileged mode. When privileged mode is enabled, roles specified in the security profile will be used in a session. When privileged mode is disabled, they will return to roles specified by a user. If full access to privileged mode is set in the security profile, a set of roles does not change when privileged mode is enabled.<p>Implemented the <span class="interface">Privileged mode roles</span> property for the security profile. </p><p>New properties for the <span class="term">AdministrationSecurityProfile </span>object: <span class="term">PrivilegedModeRoles </span>and <span class="term">FullPrivilegedMode</span>. New properties for the <span class="term">ISecurityProfile </span>object: <span class="term">PrivilegedModeRoles </span>and <span class="term">FullPrivilegedMode</span>.</p><p>The following Java-based properties are implemented in the administration server interface for the <span class="term">ISecurityProfile </span>object: <span class="term">PrivilegedModeRoles </span>and <span class="term">FullPrivilegedMode</span>.</p><p>The following parameters of the <span class="term">profile </span>command are implemented for the cluster service command-line utility (rac): <span class="term">privileged-mode-roles </span>and <span class="term">full–privileged-mode</span>.</p><p>Properties <span class="term">AdministrationSecurityProfile.PrivilegedModeAllowed </span>and <span class="term">ISecurityProfile.PrivilegedModeInSafeModeAllowed </span>(server cluster administration COM interface and Java-based administration server interface) are deprecated and supported for compatibility purposes only.</p></td><td>This feature was not provided.<p>It was impossible to explicitly specify a list of roles that would be applied in a session when switching to privileged mode.</p></td><td>Expanded features of security profiles in client/server mode.</td></tr></table><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299ba-8dd0-11e9-8371-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.16" class="tag_0"><td><a name="06b84e44-92b8-11e9-8371-0050569f678a"></a>Changed presentation of the following chart properties in the property palette:<ul><li><span class="term">SmoothingMode</span></li><li><span class="term">SmoothingTension</span></li><li><span class="term">Text</span></li><li><span class="term">AutoSeriesSeparation</span></li><li><span class="term">DonutChartInnerRadius</span></li><li><span class="term">MaxSeriesCount</span></li><li><span class="term">MaxSeriesPercentage</span></li><li><span class="term">AutoSeriesText</span></li><li><span class="term">AutoPointText</span>.</li></ul></td><td><ul><li><span class="interface">Smoothing mode. Continuous histogram smoothing mode.</span></li><li><span class="interface">Smoothing tension. Tension of a smooth curved line in points of continuous histograms (0–100).</span></li><li><span class="interface">Text. A series text to be displayed in the chart.</span></li><li><span class="interface">Automatic sector separation. Separation mode of pie chart sectors.</span></li><li><span class="interface">Inner radius.</span></li><li><span class="interface">Count. Maximum series to display.</span></li><li><span class="interface">Size. Percentage of the absolute maximum values for series to display.</span></li><li><span class="interface">Automatic series text. Generating the default text for new series.</span></li><li><span class="interface">Automatic point text. Generating the default text for new points.</span></li></ul></td><td><ul><li><span class="interface">Smoothing mode. Series line smoothing mode.</span></li><li><span class="interface">Smoothing tension. Tension of a smooth curved line of series (0–100).</span></li><li><span class="interface">Text. A series text to be displayed in the chart.</span></li><li><span class="interface">Automatic series separation. Automatic separation mode for series of pie and doughnut charts.</span></li><li><span class="interface">Inner radius. Inner radius of a doughnut chart in percent of the outer radius.</span></li><li><span class="interface">Maximum series – count. Maximum series to display.</span></li><li><span class="interface">Maximum series – percentage. Percentage of the absolute maximum values for series to display.</span></li><li><span class="interface">Automatic series text. Generating the default text for new series.</span></li><li><span class="interface">Automatic point text. Generating the default text for new points.</span></li></ul></td></tr><tr title="Версия 8.3.16" class="tag_0"><td><a name="5427da7d-bdd2-11e9-8371-0050569f678a"></a>Name of system full-text search indexing background job.</td><td><ul><li><span class="term">BackgroundJob.FullTextSearchIndexAdditionalUpdate</span>.</li></ul></td><td><ul><li><span class="term">BackgroundJob.FullTextSearchIndexUpdate</span>.</li></ul></td></tr><tr title="Версия 8.3.16" class="tag_0"><td><a name="9ee88be8-e9bf-11e9-8371-0050569f678a"></a>Infobase setting in a mobile client with an offline operation mode, which enables working with unstable Internet connection.</td><td><ul><li><span class="interface">Bad connection.</span></li></ul></td><td><ul><li><span class="interface">Expect bad connection.</span></li></ul></td></tr><tr title="Версия 8.3.16" class="tag_0"><td><a name="44b430b4-10f4-11ea-8371-0050569f678a"></a>Methods and events of a client application form.</td><td><ul><li><span class="term">FillWhenReopen()</span> method.</li><li><span class="term">BeforeReopen()</span> event handler.</li><li><span class="term">OnReopen()</span> event handler.</li></ul></td><td><ul><li><span class="term">FillWhenReopenFromOtherServer()</span> method.</li><li><span class="term">BeforeReopenFromOtherServer() </span>event handler.</li><li><span class="term">OnReopenFromOtherServer()</span> event handler.</li></ul></td></tr><tr title="Версия 8.3.16" class="tag_0"><td><a name="2fd6a0ec-10f5-11ea-8371-0050569f678a"></a><span class="term">DatabaseCopyManager </span>object property.</td><td><ul><li><span class="term">ValueStoragesUs</span><span class="term">e</span>.</li></ul></td><td><ul><li><span class="term">ValuesStoragesUsage</span>.</li></ul></td></tr><tr title="Версия 8.3.16" class="tag_0"><td><a name="380ed1ec-10f6-11ea-8371-0050569f678a"></a>Properties of objects used to manage charts.</td><td><ul><li><span class="term">DataCompositionResultSpreadsheetDocumentOutputProcessor.AppearanceForValues </span>property.</li></ul></td><td><ul><li><span class="term">DataCompositionResultSpreadsheetDocumentOutputProcessor.Value</span><span class="term">Appearance </span>property.</li></ul></td></tr><tr title="Версия 8.3.16" class="tag_0"><td><a name="72522132-10f6-11ea-8371-0050569f678a"></a>Image library icon.</td><td><ul><li><span class="term">AppearanceBoxesFour</span><span class="term">Filled.</span></li></ul></td><td><ul><li><span class="term">AppearanceBoxesFilled</span>.</li></ul></td></tr><tr title="Версия 8.3.16" class="tag_0"><td><a name="162f23fb-10f7-11ea-8371-0050569f678a"></a><span class="term">PDFAttachmentRelationshipType </span>system enumeration value.</td><td><ul><li><span class="term">NotSpecified</span>.</li></ul></td><td><ul><li><span class="term">Unspecified</span>.</li></ul></td></tr><tr title="Версия 8.3.16" class="tag_0"><td><a name="5f82a06d-10f7-11ea-8371-0050569f678a"></a><span class="term">PDFModificationAccessPermissions </span>system enumeration value.</td><td><ul><li><span class="term">FillAndSign</span>.</li><li><span class="term">FillSignAndAnnotate</span>.</li></ul></td><td><ul><li><span class="term">FillingSigning</span>.</li><li><span class="term">FillingSigningAnnotation</span></li></ul></td></tr></table><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299bb-8dd0-11e9-8371-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.16" class="tag_31"><td><a name="33352d71-98cc-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile client now supports authentication using OpenID Connect protocol. Authentication uses a system web browser of a mobile device.<p>Authentication using OpenID Connect is supported for iOS 9.0 or higher devices and Android devices that have Google Chrome installed.
</p></td><td>This feature was not provided.</td><td>The mobile client now supports authentication that was available in thin client and web client.</td></tr><tr title="Версия 8.3.16" class="tag_31"><td><a name="c7bfc8fb-9d74-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>A сonfiguration synonym is not checked for matches when you start the mobile client. The mobile client will be started if a сonfiguration name has not changed since mobile application build and a сonfiguration signature matches its digest.</td><td>Once a сonfiguration synonym changed, it was impossible to use this configuration with the mobile client application that was built with another synonym (for example, which did not have a synonym in any language).</td><td>You do not now need to rebuild a mobile application of the mobile client when only a сonfiguration synonym changes.</td></tr><tr title="Версия 8.3.16" class="tag_31 tag_32"><td><a name="62e3a947-be72-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Implemented a mobile client with the operating offline feature. This client application allows you to use it both online (as a mobile client) and offline (as a standalone mobile application). Implemented option to switch from online to offline mode and back.<p>Implemented an offline configuration feature that will be available on the mobile device in offline mode. Offline configuration is a subset of the main configuration. The offline configuration may include all metadata that exists in the platform for a PC. Configuration objects may not be a part of an offline configuration. Configuration extensions cannot be included in an offline configuration.</p><p>Implemented the <span class="term">MainServer </span>global context property. Implemented the <span class="term">MainServerAvailable()</span> global context method. Implemented the <span class="term">OnMainServerAvailabilityChange()</span> client application module event. The following is implemented for the <span class="term">ClientApplicationForm </span>object:</p><ul><li><span class="term">ReopenFromAnotherServer()</span> and <span class="term">FillWhenReopen()</span> methods.</li><li><span class="term">OnMainServerAvailabilityChange</span>, <span class="term">BeforeReopening</span>, and <span class="term">OnReopening </span>events.</li></ul><p>Implemented the <span class="term">BehaviorWhenMainServerIsUnavailable </span>property for the input field, button, decoration, and table form elements.</p><p>Implemented the <span class="term">OfflineConfigurationContents</span>, <span class="term">OfflineConfigurationRestrictionRoles </span>properties for the Configuration object. Implemented the <span class="term">BehaviorWhenMainServerIsUnavailable </span>property for the common command and common form.</p><p>Implemented the form preview in the mobile client mode in offline mode for the client application form editor. Implemented the display of elements and attributes that are not available offline on a mobile device in the client application form editor.</p><p>Implemented the feature to perform configuration verification in the offline mobile client mode.</p><p>Implemented the feature to specify in which mode the mobile client will be started in Designer settings.</p><p>Implemented new debugging items for the debugger.</p><p>The mobile application builder allows building a mobile client application with the offline mode feature.
</p></td><td>This feature was not provided.<p>It was possible to create either a standalone mobile application or a mobile client that worked online.</p></td><td>Expanded the options to build mobile applications using 1C:Enterprise.</td></tr><tr title="Версия 8.3.16" class="tag_30 tag_31 tag_32 tag_48"><td><a name="72cd0387-be93-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Implemented the feature to automatically manage mobile application data backup using the mobile operating system. Implemented the <span class="interface">Backup using OS</span> <span class="interface">tools </span>mobile application permission. The backup is performed as follows:<ul><li>Android - Google Drive service or manually using Android Debug Bridge.</li><li>iOS - Apple iCloud service.</li><li>Windows - Microsoft OneDrive service.</li></ul><p>The mobile application builder uses this permission to correctly configure the mobile application being built.
</p></td><td>This feature was not provided.</td><td>Automatic mobile application data backup (without user interaction) is now possible.
</td></tr><tr title="Версия 8.3.16" class="tag_30 tag_31 tag_32 tag_48"><td><a name="1fa30738-c260-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Implemented the mobile application permission, which allows you to manage the third-party applications installation. This feature is supported by the mobile application builder when building applications for Android.<p>Implemented <span class="term">ApplicationInstallation </span>permission.</p></td><td>This feature was not provided.<p>The third-party applications installation has always been permitted.</p></td><td>If the third-party applications installation is not required for the application, you can reduce the total number of permissions that the mobile application requires when running on Android.</td></tr></table><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299bc-8dd0-11e9-8371-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.16" class="tag_0"><a name="eb460389-8890-11ea-8371-0050569f678a"></a>The OpenSSL library is updated to version 1.1.1d.</li><li title="Версия 8.3.16" class="tag_0"><a name="01c3e6bb-0ec4-11eb-8371-0050569f678a"></a>Libraries included in the WebKit library are updated.</li><li title="Версия 8.3.16" class="tag_0"><a name="5724e395-0ec4-11eb-8371-0050569f678a"></a>Changes were made to the libicu library to remediate vulnerabilities.</li><li title="Версия 8.3.16" class="tag_0"><a name="62a576f4-0ec4-11eb-8371-0050569f678a"></a>Changes were made to the cairo library to remediate vulnerabilities.</li><li title="Версия 8.3.16" class="tag_0"><a name="6e374a6d-32d3-11eb-8371-0050569f678a"></a>The ImageMagick library is updated to version 7.0.10-24. As a result, converting images using the <span class="term">PictureToProcess </span>object may take a little longer.</li></ul><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299bd-8dd0-11e9-8371-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.16" class="tag_0"><a name="5253b9b9-e43f-11e9-8371-0050569f678a"></a>Example of formatted string usage in collaboration system message is implemented in the uncompleted order wizard.<p>Information that the message text is displayed as a formatted string has been added to the Guide. </p></li><li title="Версия 8.3.16" class="tag_0"><a name="17f6dae1-e443-11e9-8371-0050569f678a"></a>A search bar is enabled for all client application form tables.</li><li title="Версия 8.3.16" class="tag_0"><a name="e5653cbb-e44a-11e9-8371-0050569f678a"></a>The Guide (<span class="interface">Charts </span>section) demonstrates how to embed a web client in the <span class="term">iframe </span>web page.</li><li title="Версия 8.3.16" class="tag_0"><a name="1bf51363-e44b-11e9-8371-0050569f678a"></a>Simultaneous loading of several files with a shared progress bar is implemented in the stored files list form (the <span class="term">Catalog.StoredFiles.Form.ListForm</span> form).</li><li title="Версия 8.3.16" class="tag_0"><a name="94c01485-e44b-11e9-8371-0050569f678a"></a>New chart features can be seen in the following sections:<ul><li>In the <span class="interface">Sales dynamics</span> report: the <span class="interface">Amount and quantity</span> report option shows two resources on a single chart.</li><li><span class="interface">Editing prices</span> data processor demonstrates interactive changing of chart values.</li><li>The <span class="interface">Sales dynamics</span> report demonstrates how to configure the reference lines and chart intervals in the <span class="interface">Desired sales levels</span> report option.</li></ul></li><li title="Версия 8.3.16" class="tag_0"><a name="1c1502bf-e44e-11e9-8371-0050569f678a"></a>The new scheduler features are demonstrated in the <span class="term">Catalog.Meetings.Form.Calendar</span> form.</li><li title="Версия 8.3.16" class="tag_0"><a name="5bdc460a-1740-11ea-8371-0050569f678a"></a>A standalone part of a demo configuration is implemented. Functionality of a standalone part is almost similar to that of a demo configuration for a mobile platform.</li><li title="Версия 8.3.16" class="tag_0"><a name="7b02844a-1740-11ea-8371-0050569f678a"></a>Notification through FCM service is enabled.</li><li title="Версия 8.3.16" class="tag_0"><a name="9551816a-1742-11ea-8371-0050569f678a"></a>As soon as you link photos to goods and counterparties, you can stamp your photos. For stamp settings, go to <span class="term">MobileDeviceSettings </span>common form.</li><li title="Версия 8.3.16" class="tag_0"><a name="2382f8c3-1745-11ea-8371-0050569f678a"></a>The mobile demo configuration now supports an extra authentication feature to grant access to data (<span class="term">ClientExchange </span>common module and <span class="term">Settings </span>common form).</li><li title="Версия 8.3.16" class="tag_0"><a name="339df2b2-174d-11ea-8371-0050569f678a"></a>A mobile demo configuration supports a file management feature (saved product files).<p>
</p></li><li title="Версия 8.3.16" class="tag_0"><a name="7f95d446-174d-11ea-8371-0050569f678a"></a>A mobile demo configuration supports popup groups (Counterparties.ItemForm catalog form; AddressesAndContacts group).</li><li title="Версия 8.3.16" class="tag_0"><a name="6ac88cfc-4754-11ea-8371-0050569f678a"></a>The following examples are implemented in the demo configuration for working with the charts (<a href="https://its.1c.ru/db/metod8dev#content:5952:hdoc" target="_blank">Read more</a>.):<ul><li>An option to accumulate series in different accumulation groups. The example is implemented in the <span class="interface">Column chart</span> group.</li><li>An option to combine different types of series in a single chart. The example is implemented in the <span class="interface">Combination</span> group.</li><li>An option to operate the additional scale of values. The example is implemented in the <span class="interface">Combination</span> group.</li><li>An option to interactively edit the chart and process the result of editing from the script. The example is implemented in the <span class="interface">Interactive operations</span> group.</li><li>The series color saving mechanism operation, program settings and its implementation in the report. The example is implemented in the <span class="interface">General</span> group.</li></ul></li><li title="Версия 8.3.16" class="tag_0"><a name="b94e65e5-4754-11ea-8371-0050569f678a"></a>In the demo configuration for working with the charts (<a href="https://its.1c.ru/db/metod8dev#content:5952:hdoc" target="_blank">Read more</a>.), a global search by examples is implemented. You can also filter examples by the platform versions. A special dialog box for platform versions filter is implemented. You can call it by clicking the <span class="interface">Settings</span> button in the upper right corner of the home page.</li></ul><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299be-8dd0-11e9-8371-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.16" class="tag_20"><td><a name="9eb6937a-cd65-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>You can now export a configuration which size exceeds 2 GB to a <span class="interface">1Cv8.cf </span>file from Designer. Designer version 8.3.16 and later can only be used to import such configuration.</td><td>When attempting to export a configuration which size exceeds 2 GB to a <span class="interface">1Cv8.cf </span>file, the upload was interrupted with a confusing error message.</td><td>Exporting very large configurations to a <span class="interface">1Cv8.cf</span> file is now available.</td></tr><tr title="Версия 8.3.16" class="compat tag_64 tag_1"><td><a name="7991bf5a-cd67-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td><span class="term">GetStringDeclensions()</span> and <span class="term">GetStringDeclensionsByNumber()</span> methods return a maximum of 10 declension variants of the passed phrase.<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>There was no limit for <span class="term">GetStringDeclensions()</span> <span class="term">and GetStringDeclensionsByNumber()</span> methods of the number of the passed phrase declension variants.</td><td><span class="term">GetStringDeclensions()</span> and <span class="term">GetStringDeclensionsByNumber()</span> methods performance has been improved due to decreasing the number of declension variants.</td></tr><tr title="Версия 8.3.16" class="compat tag_25 tag_43 tag_1"><td><a name="ff2889fa-cd67-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The data composition layout composer adds ordering from the data composition system settings to the top of the ordering list of data composition layout request.<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>The data composition layout composer added ordering from the data composition system settings to the bottom of the ordering list of data composition layout request.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_59 tag_64"><td><a name="6bd6b17a-cd69-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>When automatically calculating the interface element text color, a more contrasting color relative to the element background color is selected.</td><td>When automatically calculating the interface element text color, a less contrasting color relative to the element background color was selected.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_22"><td><a name="1b2635ba-cd6a-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br></td><td>The RAM consumption for storing variable-length fields (variable-length strings and value storage) in the Data Accelerator has been reduced.<p>Execution of some types of queries has been optimized.</p></td><td>Data Accelerator required more RAM to store variable-length fields (variable-length strings and a value storage).<p>Execution of some types of queries was not optimal.</p></td><td>Data Accelerator has been optimized.</td></tr><tr title="Версия 8.3.16" class="tag_85"><td><a name="2f5bbb51-e382-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 85); return false;">Processing PDF documents</a>.<br></td><td>New feature: digital signature in PDF documents. Embedding of a digital signature visual representation into a document is also available.<p>Implemented <span class="term">PDFSignatureDescription </span>object. <span class="term">LinkType </span>and <span class="term">ContentType </span>properties are implemented for <span class="term">PDFAttachment </span>object. <span class="term">ContentType </span>and <span class="term">LinkType </span>parameters are implemented for <span class="term">PDFAttachmentCollection.Add()</span> method.</p><p><span class="term">ReadPDF </span>object is now available in the thin client and in the web client. File system extension is required to use web client. The following methods are implemented for the <span class="term">ReadPDF </span>object: <span class="term">CheckSignatures()</span>, <span class="term">CheckSignature()</span>, <span class="term">GetSignatureDescription()</span>, <span class="term">StartOpening()</span>, <span class="term">StartRetrievingAttachments()</span>, <span class="term">StartSignaturesCheck()</span>, <span class="term">StartSignatureCheck()</span>, <span class="term">StartRetrievingSignatureDesctiption()</span>, <span class="term">StartClosing()</span>.</p><p><span class="term">WritePDF </span>object is now available in the thin client and in the web client. File system extension is required to use web client. <span class="term">WriteSignature()</span>, <span class="term">StartOpening()</span>, <span class="term">StartWritingAttachments()</span>, <span class="term">StartWritingDeletingAttachments()</span>, <span class="term">StartWritingSignature()</span>, <span class="term">StartClosing()</span> methods are implemented for the <span class="term">WritePDF </span>object.</p></td><td>This feature was not provided.<p>Creating a separate digital signature file was available.</p></td><td>Expanded PDF documents management capabilities. The document consistency can now be secured after signing.</td></tr><tr title="Версия 8.3.16" class="compat tag_59 tag_1"><td><a name="0e8fdf0d-e388-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>The <span class="term">OnClose </span>event handler called after the <span class="term">ShutdownSystem (False)</span> method has the <span class="term">Shutdown </span>parameter set to <span class="term">True</span>.<p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>The <span class="term">OnClose </span>event handler called after the <span class="term">ShutdownSystem (False)</span> method had the <span class="term">Shutdown </span>parameter set to <span class="term">True </span>in the web client and <span class="term">False </span>otherwise.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_54"><td><a name="4ddbd715-e38b-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 54); return false;">Global search</a>.<br></td><td>If an error occurred while performing the global search, the search result is placed to the <span class="term">GlobalSearchResultElement </span>object, which has the <span class="term">ErrorDetails </span>object placed to the Value property.<p>When displaying the results, the error will be shown using the <span class="term">SpecialTextColor </span>style color.</p><p>Serialization and XDTO serialization has been implemented for the <span class="term">ErrorDetails </span>object.</p></td><td>Errors that occurred while performing a global search were not displayed to the user.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_7"><td><a name="fba1b081-e430-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>The cases of excessive RAM usage when transferring data to a copy (including the Data Accelerator) have been fixed.</td><td>Cases of excessive RAM usage were possible when transferring data to a copy.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="compat tag_58 tag_1"><td><a name="e3877e8a-e4f9-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>When using two (or more) separators that are used at the same time (i.e., store their value and conditional separation flag in the same configuration objects), the <span class="term">DeleteInfobaseData() </span>method will deem the configuration object to be included in the current area if it is separated by at least one of the separators from the list of separators using the same configuration objects to store their parameters.<p>It is recommended to analyze using the <span class="term">DeleteInfobaseData() </span>method in the separated configurations and refactor this code, if required.</p><p>This change is not implemented in 8.3.15 compatibility mode.</p></td><td>When using two (or more) separators that are used at the same time (i.e., store their value and conditional separation flag in the same configuration objects), the <span class="term">DeleteInfobaseData()</span> method deemed the configuration object to have been included in the current area if it was separated by at least one of the separators from the list of separators using the same configuration objects to store their parameters.</td><td>The approach to determining the data area using the <span class="term">DeleteInfobaseData()</span> method has been changed.</td></tr><tr title="Версия 8.3.16" class="tag_30 tag_31"><td><a name="e1393be0-e4fe-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Improved execution of certain operations (starting, creating an infobase, etc.) in mobile applications built for Android. The size of mobile applications built for Android has slightly increased.</td><td>Execution of certain operations (starting, creating an infobase, etc.) in mobile applications built for Android took more time.</td><td>Optimized 1C:Enterprise mobile version, running on Android.</td></tr><tr title="Версия 8.3.16" class="tag_31"><td><a name="027181ef-e904-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>In an offline mobile client, a form that reopens after changing the availability of the main server is reopened with the same set of form parameters as the original form.<p>The documentation contains the recommendation for generation of the offline mobile client home page.</p><p>The <span class="term">-MobileStandalone</span> parameter has been implemented for the <span class="term">CheckConfig </span>Designer batch run command, which allows to check the configuration for using an offline mode.</p><p>The <span class="term">-RebuildStandaloneCfg</span> parameter is implemented for the <span class="term">IBCheckAndRepair </span>Designer batch mode run command, which allows to regenerate the offline configuration.</p></td><td>In an offline mobile client, a form that reopens after changing the availability of the main server was reopened with the set of parameters that included the original form key parameters only.</td><td>Improved offline mobile client running. </td></tr><tr title="Версия 8.3.16" class="tag_18 tag_15 tag_36"><td><a name="59449810-e9b3-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The <span class="term">UniqueID </span>object creates version 4 universal unique identifiers (a completely random universal unique identifier) when used on PCs running Linux and macOS.</td><td>The <span class="term">UniqueID </span>object created version 1 universal unique identifiers (universal unique identifier dependent on time and network adapter MAC) when used on PCs running Linux and macOS.</td><td>Enabled using the platform’s built-in features if it was required to pass a version 4 universal unique identifier to an external service during integration and the existing universal unique identifier was not suitable for such transfer.</td></tr><tr title="Версия 8.3.16" class="tag_43 tag_21"><td><a name="2dfafeb2-f0ac-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>The " " (space) character is used as a separator only when breaking into words, which is performed at input by string and at search in a dynamic list. The ".", ",","-", "/" and "\" characters are no longer considered as separators and are searched for as regular characters.<p>Not only the lines between every two separators, but also the lines from each separator to the end of the line are added to the full-text search index during indexing.
</p></td><td>The ".", ",","-", "/" and "\" characters were used as a separators when breaking into words, which is performed at input by string and at search in a dynamic list.</td><td>Search as you type and in the dynamic list has become better suited to the user's habits.</td></tr><tr title="Версия 8.3.16" class="tag_31"><td><a name="cdb5137c-15d9-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>It now supports forced use of main server. Use this feature when you start to fill in the infobase of a mobile client with a standalone mode enabled.<p><span class="term">SetPreferableMainServerUse()</span>/<span class="term">GetPreferableMainServerUse()</span> global context methods are implemented.</p></td><td>This feature was not provided.
</td><td>Now, you can avoid access to a local infobase of a mobile client , when you begin to populate this database.</td></tr><tr title="Версия 8.3.16" class="tag_30 tag_31"><td><a name="caab293f-dd5b-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Now you can manage whether a mobile device can enter sleep when the mobile application is running. New global context methods: <span class="term">SetComputerIdlingToSleepProhibition()</span> and <span class="term">GetComputerIdlingToSleepProhibition()</span>.</td><td>This feature was not provided.</td><td>Now you can block mobile device idling to sleep, which can make it easier to use the mobile application in some usage scenarios.</td></tr><tr title="Версия 8.3.16" class="tag_31"><td><a name="947ecdc7-1733-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td><span class="interface">Remember Me</span> check box is available in the mobile client authentication dialog box. If this check box is selected and standard authentication is used (without biometrics), authentication data is saved in the mobile device secure storage.<p>The following commands of the QR-code designed to add an infobase to a mobile client are now supported:</p><ul><li><span class="term">DisableUseBiometrics </span>to hide <span class="interface">Use Biometrics </span>check box.</li><li><span class="term">UseBiometrics </span>to define the state of <span class="interface">Use Metrics </span>check box.</li><li><span class="term">DisableRememberMe</span> to hide<span class="interface"> Remember Me </span>check box.</li><li><span class="term">RememberMe</span> to define the state of <span class="interface">Remember Me </span>check box.
</li></ul><p>The following parameters of the <span class="term">/AddInfoBase </span>command of <span class="interface">e1c:// </span>schema are supported:</p><p>
</p><ul><li><span class="term">DisplayAuthDialog </span>to display an authentication dialog box as soon as you start it for the first time.</li><li><span class="term">DisableUseBiometrics</span> to hide<span class="interface"> Use Biometrics </span>check box.</li><li><span class="term">UseBiometrics</span> to define the state of <span class="interface">Use Metrics </span>check box.</li><li><span class="term">DisableRememberMe</span> to hide <span class="interface">Remember Me</span> check box.</li><li><span class="term">RememberMe</span> to define the state of <span class="interface">Remember Me </span>check box.</li></ul></td><td>These features were not provided.</td><td>Mobile client start settings are now more detailed.</td></tr><tr title="Версия 8.3.16" class="tag_21"><td><a name="1ab5972e-263a-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>During infobase data indexing, if the string does not contain any alphanumeric characters, the full-text search index comprises of substrings from each non-alphanumeric character to the end of the line only if the length of the original string is less than 64 characters.</td><td>During infobase data indexing, if the string did not contain alphanumeric characters, the full-text search index comprised of substrings from each non-alphanumeric character to the end of the line. As a result, data indexing consumed a big amount of RAM.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_31"><td><a name="994ee3e3-36bf-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>When executing a mobile client with the option of standalone mode, the 1C:Enterprise language modules are compiled using the following preprocessor commands:<ul><li><span class="term">MobileClient</span> on client.</li><li><span class="term">MobileStandaloneServer</span> on the standalone server.</li><li><span class="term">Server</span> on the desktop server.</li></ul><p>You can now find out which server is currently used in a client application form and will be called during a server call. The <span class="term">ClientApplicationForm.CurrentFormServer</span> property is implemented. The <span class="term">GetCurrentServer()</span> global context method is implemented.
The <span class="term">StandardProcessing</span> parameter that defines whether the dialog box with the suggestion to reopen the form will appear is implemented for the <span class="term">OnMainServerAvailabilityChange</span> event handler of the client application form.
The <span class="term">MobileClient</span> value, defining the mode of the mobile client session is implemented for the <span class="term">InfobaseSession.ApplicationName</span> property. The <span class="term">ApplicationPresentation()</span> method now supports the <span class="term">MobileClient</span> parameter value.</p></td><td>When executing a mobile client with the option of standalone mode, the 1C:Enterprise language modules were compiled using the following preprocessor commands:<ul><li><span class="term">MobileApplicationClient</span> on client.</li><li><span class="term">MobileApplicationServer</span> on standalone server.</li><li><span class="term">Server</span> on the desktop server.
</li></ul></td><td>Preprocessor commands used to distinguish the client-server interaction methods are now easier to understand when using the mobile client with standalone mode option.
It is now easier to determine which server will be used in the form and called during the next server call from the 1C:Enterprise language.
</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="b3d95a7c-3d1c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>To deploy your own instance of the collaboration system server, you can purchase a specific software <a href="https://1c.ru/news/info.jsp?id=26598" target="_blank">Read more</a>. that doesn't require the CORP license.</td><td>CORP license was required to deploy a collaboration system server instance.</td><td>To deploy an instance of the collaboration system server, you have to fulfill one of the conditions:<ul><li>Purchase CORP license.</li><li>Purchase the 1C:Collaboration server.
</li></ul></td></tr><tr title="Версия 8.3.16" class="tag_84"><td><a name="1405860b-3db1-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Localized client application interface for Armenian (<span class="interface">hy</span>).</td><td>This feature was not provided.
</td><td>1C:Enterprise is now available for Armenian-speaking users.
</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="6219f0c3-4756-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>When displaying a collaboration system message specified by a formatted string, the navigation links from this formatted string are recognized automatically. If a navigation link has an appearance specified (colour, font, etc.), it will not be recognized.
</td><td>When displaying a collaboration system message specified by a formatted string, the navigation links from this formatted string were not recognized automatically
</td><td>Eliminated unexpected system behavior.
</td></tr><tr title="Версия 8.3.16" class="tag_19"><td><a name="9863b9e9-685c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>When using PostgreSQL DBMS in the client-server mode, the infobase restructuring causes the database structure to change. These changes are required to support PostgreSQL 12.<p>The change does not affect the application operation.</p></td><td>The database structure did not support PostgreSQL 12 DBMS.</td><td>The database structure supports PostgreSQL 12 DBMS.</td></tr><tr title="Версия 8.3.16" class="tag_59"><td><a name="356ba679-7965-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td><span class="term">MoveUp </span>and <span class="term">MoveDown </span>commands are now available for the form table linked with data of <span class="term">FormDataCollection </span>or <span class="term">ValueList </span>type with the set row filter.<p><span class="term">MoveUp </span>and <span class="term">MoveDown </span>commands are available for multiple rows selection in tables linked with data of the <span class="term">ValueList </span>type.</p></td><td><span class="term">MoveUp </span>and <span class="term">MoveDown </span>commands were unavailable for the form table linked with data of <span class="term">FormDataCollection </span>or <span class="term">ValueList </span>type with the set row filter.<p><span class="term">MoveUp </span>and <span class="term">MoveDown </span>commands were not supported for multiple rows selection in tables linked with data of the <span class="term">ValueList </span>type.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_29 tag_30 tag_31"><td><a name="c065cf44-7984-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Implemented support for Apple iPhone 11 device family.<p>Implemented support for iOS version 13.</p></td><td>Apple iPhone 11 device family was not supported.<p>iOS version 13 was not supported.</p></td><td>1C:Enterprise supports new operating systems and devices.</td></tr><tr title="Версия 8.3.16" class="tag_37"><td><a name="3cb0b000-8894-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Now the OAuth2 protocol can be used for emails together with the SMTP protocol. The <span class="term">InternetMailProfile.AccessToken </span>property is used for authentication.</td><td>The OAuth2 protocol was used for emails for the IMAP protocol only.</td><td>Now email servers with the OAuth2 authentication protocol are supported if you use SMTP.</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="03156864-8896-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can take advantage of separate settings of notification sounds for messages and video calls in the dialog box of collaboration system settings.<p>Notification settings from previous versions apply to messages. Video call notifications are enabled by default.</p><p>Video call notifications allow playing sound notifications upon:</p><ul><li>An incoming call.</li><li>Ending a call.</li><li>Awaiting for a contact to accept a call.</li></ul></td><td>Separate settings of notification sounds for messages and video calls were not supported in the dialog box of collaboration system settings.</td><td>Users can mute or unmute video call notifications and default notifications separately. This will reduce missed video calls.</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="8cd533ba-95cc-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can click <span class="interface">Add users to video call </span>to add a new user during a video call. The command is now available:<ul><li>In the <span class="interface">Conversations </span>form.</li><li>In the context conversation form.</li><li>In the user parameters dialog box.</li><li>In the video call submenu, in the main window title.</li></ul></td><td>During a video call, you needed to click <span class="interface">Start a video call </span>to add a new user:<ul><li>In the <span class="interface">Conversations </span>form.</li><li>In the context conversation form.</li><li>In the user parameters dialog box.</li><li>In the video call submenu, in the main window title.</li></ul></td><td>Now the name of the command for adding a new user to a video call is more user-friendly.</td></tr><tr title="Версия 8.3.16" class="tag_14"><td><a name="1c31fdd4-98dc-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>When using thick and thin clients running Windows, changed the view of titles of independent windows (main application window, calendar window, calculator window, system dialog boxes, and other):<ul><li>In remote desktop (RDP) mode, the operating system title is not displayed.</li><li>For RemoteApp, the operating system title:</li></ul></td><td>When using thick and thin clients running Windows, independent windows (main application window, calendar window, calculator window, system dialog boxes, and other) were always displayed with the operating system title in remote desktop (RDP) mode or RemoteApp mode.</td><td>Improved appearance of the application. When using client applications in terminal mode, the application appearance is now more user-friendly.</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="f8142274-98e0-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Updated the dialog box of collaboration system settings. Settings specified in the dialog box of collaboration system settings are applied at once without clicking any buttons. Now the button that opens the dialog box is at the top of the <span class="interface">Conversations </span>window.<p>Now the dialog box of collaboration system settings has a button that opens the dialog box of device selection where you can:</p><ul><li>Select a camera you want to use and test it.</li><li>Select a microphone you want to use and check its signal level.</li><li>Select a device you want to use to play audio.</li></ul><p>
Now you can open the dialog box of device settings during a video call.</p><p>In the web client, the dialog box of device settings is displayed in Google Chrome and Mozilla Firefox only if the web client is published using HTTPS protocol (or at <span class="interface">localhost</span>). The publication can access the microphone and camera. In the dialog box of device settings, the list of devices and their names can differ from the list of devices and their names in thin and thick client applications (for the same computer).</p></td><td>The button that opened the dialog box of collaboration system settings was at the bottom of the <span class="interface">Conversations </span>window. Settings specified in the dialog box of collaboration system settings were applied after clicking <span class="interface">OK</span>. Users could not specify the devices used.</td><td>Improved collaboration system settings if there are several computer devices that can be used for calls (audio and video calls).</td></tr><tr title="Версия 8.3.16" class="tag_10 tag_14"><td><a name="d735a994-98ed-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Upgrade: on computers running Windows, users without administrative rights can install the client application ("for user" installation option). The application is installed to <span class="interface">%LOCALAPPDATA%\Programs.</span><p>With this installation option, 1C:Enterprise server cluster cannot be installed as an operating system service.</p><p>You can still install client applications in the "for computer" mode (with administrative rights). The "for user" and "for computer" installation options can coexist. Both lists of installed applications will be used upon client application selection.</p><p>
We recommend that you check configurations for explicitly specified directories that store the system. Use the <span class="term">BinDir() </span>global context method instead of explicitly specifying the path.
</p></td><td>On computers running Windows, the client application could be installed only if users had administrative rights or it required users to enter an administrator password if they did not have such rights.</td><td>Now users without administrative rights can install the client application.</td></tr><tr title="Версия 8.3.16" class="tag_31 tag_4"><td><a name="facc1082-9f28-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>For the mobile client, implemented collaboration system video calls. The mobile device position (in front of the eyes or close to an ear) is considered upon video calls.</td><td>This feature was not provided.</td><td>Now you can use collaboration system video calls in the mobile client.</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="90e6cbe7-a968-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>If the client application is connected to the client application agent, a notification about an incoming video call is shown even if the client application is not running.<p>If a user accepts an incoming call, the client application is launched. A video call to callers starts automatically here.</p></td><td>If the client application was connected to the client application agent, a notification about an incoming video call was not displayed if the client application was not running on a computer.</td><td>Users will receive notifications about incoming video calls when the client application is closed. Previously, such video calls were missed.</td></tr><tr title="Версия 8.3.16" class="tag_70"><td><a name="7b18006d-c01b-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>If Windows XP or Windows Server 2003 have Windows installer v3.1, 1C:Enterprise can be installed only in the per-machine installation context (providing that the user is granted the Administrator rights). If Windows XP or Windows Server 2003 have Windows installer updated to v4.5, 1C:Enterprise can be installed in the per-user installation context (if the user is not granted the Administrator rights).</td><td>If Windows XP or Windows Server 2003 had Windows installer v3.1, 1C:Enterprise couldn't be installed raising the error due to the unsupported installer version.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="c0d7df31-d599-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The header of the client application includes a menu that accommodates all Collaboration System commands. The menu appears only is the infobase in connected to the Collaboration System.<p>Some command items are clickable only if their features are available. For example, the video call button is faded if the user's machine has no camera.</p></td><td>The Collaboration System buttons were scattered over the interface.</td><td>Collaboration System user interface is improved.</td></tr><tr title="Версия 8.3.16" class="tag_79 tag_30 tag_31"><td><a name="3f6aceec-0ec3-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Upgrade: 1C:Enterprise mobile version now supports multipage TIFF files, just like the personal computer platform.</td><td>This feature was not provided.</td><td>Upgrade: 1C:Enterprise mobile version now supports multipage TIFF files.</td></tr><tr title="Версия 8.3.16" class="tag_4"><td><a name="85ed1176-0eca-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Improved application stability when using video calls of the collaboration system in thin and web clients.<p>Changes in the dialog box to set up parameters of the used hardware (the <span class="interface">Conversations... </span>menu - the <span class="interface">Settings </span>menu item - the <span class="interface">Settings </span>button) are applied at once without confirming the change.</p></td><td>Application stability was low when using video calls of the collaboration system in thin and web clients.
</td><td>Improved application stability when using video calls of the collaboration system in thin and web clients.</td></tr><tr title="Версия 8.3.16" class="tag_18 tag_29"><td><a name="e514c372-32df-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Updated system requirements for the client application running macOS. The client application is supported only on macOS 10, starting from version 10.12 and later.</td><td>The system requirements for the client application running macOS were version 10.12 and later.</td><td>Updated system requirements for the client application running macOS.</td></tr><tr title="Версия 8.3.16" class="tag_6"><td><a name="70850ae0-53fc-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When a working process fails, switching the session to a backup working process takes less time.</td><td>When a working process failed, switching the session to a backup working process took more time.</td><td>In the backup cluster, working process emergencies are now less visible to users.</td></tr><tr title="Версия 8.3.16" class="tag_33"><td><a name="a31a82a0-53fc-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>The documentation contains a recommendation for using the HTTPs protocol when working with an infobase engaged in commercial operation.</td><td>The documentation did not contain a recommendation for using the HTTPs protocol when working with an infobase engaged in commercial operation.</td><td>The documentation recommends using safer methods of working over the Internet.</td></tr><tr title="Версия 8.3.16" class="tag_94"><td><a name="96c46d55-5aed-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 94); return false;">Regional settings</a>.<br></td><td>Upgrade: in accordance with the Federal Law of the Russian Federation No. 432-FZ, a new time zone is applied for Volgograd oblast. The update is applied to all 1C:Enterprise system components, except for the web client. The web client sets the time in accordance with the time zone information provided by the operating system and web browser.
</td><td>1C:Enterprise ignored the changes introduced by the Federal Law of the Russian Federation No. 432-FZ.</td><td>New time zone settings are applied due to the legislation change.</td></tr><tr title="Версия 8.3.16" class="tag_85 tag_60"><td><a name="e5cccf77-32ee-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 85); return false;">Processing PDF documents</a>.<br><a href="#" onclick="onTagClick(this, 60); return false;">Spreadsheet document</a>.<br></td><td>For a PDF document, it is now possible to insert an arbitrary image or a spreadsheet document in a specified PDF document area.<p>New object: <span class="term">DetailsOfPDFObjectToDisplay</span>. New methods for the <span class="term">WritePDF </span>object: <span class="term">WriteObjectToDisplay()</span> and <span class="term">WriteObjectToDisplayAsync()</span>.</p></td><td>This feature was not provided.</td><td>Advanced PDF document features.</td></tr><tr title="Версия 8.3.16" class="tag_14 tag_70 tag_28"><td><a name="dde0b42c-b705-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Platform files and extension files for web browsers, and distribution packages used in Windows are signed only with the SHA256 algorithm.<p>With Microsoft Internet Explorer (when running Windows XP, Windows Vista, Windows Server 2003, or Windows Server 2008), enable the option to load and attach unsigned add-ons.</p><p>We recommend that you use Windows 7 and later (including the web client) to work with 1C:Enterprise.</p></td><td>Platform files and extension files for web browsers, and distribution packages used in Windows were signed with SHA1 and SHA256 algorithms.</td><td>The outdated and insecure SHA1 cryptographic hash algorithm is no longer supported.</td></tr><tr title="Версия 8.3.16" class="tag_14 tag_10"><td><a name="6b631e99-c77d-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Now you can choose an installation mode for 1C:Enterprise: for all users or for the current user. This feature is implemented both in the interactive mode and as command-line parameters/configuration file parameters.<p>New <span class="term">InstallForUsers </span>parameter for <span class="interface">1cestart.cfg </span>configuration file. New <span class="term">ALLUSERS </span>command of the startup command line for the<span class="interface"> setup.exe </span>utility.</p></td><td>The client application installation mode was selected only by the current user access rights. Even when a user knew the administrator password, the installation for all users could be started only when the <span class="interface">setup.exe </span>utility was run under an administrator.</td><td>Simplified 1C:Enterprise platform administration. You can select an installation mode for the client application as required by the current administration policies.</td></tr><tr title="Версия 8.3.16" class="tag_29 tag_19"><td><a name="debbc1ba-7d09-11ec-aa69-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The system now supports Postgres Pro DBMS of the following versions (only for x86-64):<ul><li>Postgres Pro 1C 9.6.24.1</li><li>Postgres Pro 1C 10.19.1</li><li>Postgres Pro 1C 11.14.1</li><li>Postgres Pro Standard 9.6.24.1</li><li>Postgres Pro Standard 10.19.1</li><li>Postgres Pro Standard 11.14.1</li><li>Postgres Pro Enterprise 9.6.24.1</li><li>Postgres Pro Enterprise 10.19.1</li><li>Postgres Pro Enterprise 11.14.1</li></ul></td><td>These DBMS versions were not supported.<p>
</p></td><td>Extended list of supported DBMS.</td></tr></table><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2c7299bf-8dd0-11e9-8371-0050569f678a">Transition from the previous version to the version 8.3.16</a></h2><ul><li title="Версия 8.3.16" class="tag_0"><a name="2c7299c0-8dd0-11e9-8371-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.16.
</li><li title="Версия 8.3.16" class="tag_0"><a name="2c7299c1-8dd0-11e9-8371-0050569f678a"></a>Some features that are added in version 8.3.16 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li></ul><p><a href="#2c7299b4-8dd0-11e9-8371-0050569f678a"><small>Table of contents</small></a></p><h1><a name="83bf2cb2-14ce-11e9-a3f7-0050569f678a">Version 8.3.15</a></h1><p title="Версия 8.3.15" class="tag_0"><a name="83bf2cc0-14ce-11e9-a3f7-0050569f678a"></a>Version 8.3.15 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#83bf2cb3-14ce-11e9-a3f7-0050569f678a">New functionality and changes</a></li><li><a href="#83bf2cb4-14ce-11e9-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#83bf2cb5-14ce-11e9-a3f7-0050569f678a">Optimization</a></li><li><a href="#83bf2cb6-14ce-11e9-a3f7-0050569f678a">Changes that affect system behavior</a></li><li><a href="#83bf2cb7-14ce-11e9-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#83bf2cb9-14ce-11e9-a3f7-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#83bf2cba-14ce-11e9-a3f7-0050569f678a">Library updates
</a></li><li><a href="#83bf2cbb-14ce-11e9-a3f7-0050569f678a">Demo configuration changes</a></li><li><a href="#83bf2cbc-14ce-11e9-a3f7-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#83bf2cbd-14ce-11e9-a3f7-0050569f678a">Transition from the previous version to the version 8.3.15</a></li></ul><h2><a name="83bf2cb3-14ce-11e9-a3f7-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.15" class="compat tag_2 tag_1"><td><a name="317fbd6c-1592-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.14</span> is now implemented.</td><td>Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.13 was available.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.14 or earlier can now run on version 8.3.15 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.15 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.14 after the migration to version 8.3.15, even if you disable the compatibility mode (simply enable it again).</td></tr><tr title="Версия 8.3.15" class="tag_69"><td><a name="1077e35d-1806-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>If some errors occur, a stack of calls leading up to the error (not related to nested exceptions) is now displayed in detailed error description.
In 1C:Enterprise Development Tools, call stack navigation is now available.</td><td>If an error message occurred, detailed error description did not include a call stack leading to the line with error (except for nested exceptions).</td><td>Improved diagnostics of application errors.</td></tr><tr title="Версия 8.3.15" class="tag_37 tag_10 tag_39"><td><a name="5f5d857b-18aa-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>Implemented two-factor authentication.
New data for event log events: <span class="term">_$Session$_.Authentication</span>, <span class="term">_$Session$_.AuthenticationError</span>, <span class="term">_$User$_.New</span>, <span class="term">_$User$_.Update</span>.
Implemented the following event log events: <span class="term">_$Session$_.AuthenticationFirstFactor</span>, <span class="term">_$InfoBase$_.SecondFactorAuthTemplateNew</span>, <span class="term">_$InfoBase$_.SecondFactorAuthTemplateUpdate</span>, <span class="term">_$InfoBase$_.SecondFactorAuthTemplateDelete</span></td><td>This feature was not provided.</td><td>Expanded user authentication options. More secure user authentication is available now.</td></tr><tr title="Версия 8.3.15" class="tag_63 tag_25"><td><a name="249f7e94-18cd-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New feature: doughnut and 3D doughnut charts.
New properties for the <span class="term">ChartType </span>system enumeration: <span class="term">Donut </span>and <span class="term">Donut3D</span>.
Implemented the
<span class="term">Chart.</span><span class="term">DonutChartInnerRadius </span>property.
Implemented the <span class="term">ChartType.DonutChartInnerRadius</span> parameter for the following objects: <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroupOutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance</span>. </td><td>This feature was not provided.</td><td>New chart features.</td></tr><tr title="Версия 8.3.15" class="tag_26"><td><a name="307fe01e-18d0-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Now you can specify a formatted string as a spreadsheet document header or footer.
Included the <span class="term">FormattedString </span>type in types of the following properties of the <span class="term">SpreadsheetDocumentHeaderFooter</span> <span class="term"> </span>object: <span class="term">LeftTex</span><span class="term">t</span>, <span class="term">CenterTex</span><span class="term">t</span>, and <span class="term">RightTex</span><span class="term">t</span>.
With an editor of spreadsheet document headers and footers, you can edit a formatted string. When you start editing the relevant field with the header or footer text, the check box of output of the relevant header or footer to the spreadsheet document is selected automatically. Upon exporting a spreadsheet document, formatting of headers and footers is saved in the following formats: PDF (<span class="interface">*.pdf</span>), Microsoft Office OpenXML (<span class="interface">*.xlsx</span> and <span class="interface">*.docx</span>), Microsoft Excel (<span class="interface">*.xls</span>), and Open Document Spreadsheet (<span class="interface">*.ods</span>).
For more information on how to use a formatted string for displaying headers and footers, see 1C:Enterprise documentation</td><td>This feature was not provided.</td><td>Expanded spreadsheet document export features.</td></tr><tr title="Версия 8.3.15" class="tag_26"><td><a name="8859f61c-1969-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>New feature: you can save a spreadsheet document to PDF/A-1 (a format for long-term storage). When you save to PDF/A-1 format, remember the following:<ul><li>Document is written as PDF 1.4.</li><li>Duplex printing is not supported.</li><li>Transparency is not supported.</li></ul><p>Implemented the <span class="term">SpreadsheetDocumentFileType.PDF_A_1</span> system enumeration value.</p></td><td>This feature was not provided.</td><td>Expanded spreadsheet document export features.</td></tr><tr title="Версия 8.3.15" class="tag_18 tag_4"><td><a name="18b93bab-196b-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Client applications running under macOS now support collaboration system video calls.</td><td>This feature was not provided.</td><td>Implemented collaboration system features under macOS.</td></tr><tr title="Версия 8.3.15" class="tag_25"><td><a name="9d44339e-1978-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New feature: you can save changes upon closing a form for the report settings form and the form for editing a report option. User prompt is generated before saving. The upgrade is valid only if the <span class="term">StandardProcessing </span>parameter of the <span class="term">BeforeClose </span>form event handler is set to <span class="term">True</span>.</td><td>This feature was not provided.
Upon closing the form, changes in the form were lost.</td><td>Reduced risk of losing changes made in the report settings form or the report option form in case of incorrect closing of the editing form.</td></tr><tr title="Версия 8.3.15" class="tag_7 tag_16 tag_42 tag_12"><td><a name="19ed3f4e-197a-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>New feature: you can transfer not all register data but data only for a specific period to a copy for information registers and accumulation registers. This feature is available only for a standard replication.
New property: <span class="term">DatabaseCopyContentItem.Filter</span>.
New feature for the <span class="interface">Database copy management </span>standard data processor. You can set filter by a period for information registers and accumulation registers.
New feature: upon defining the query place, you can analyze a period condition in addition to the existing checks.</td><td>This feature was not provided.</td><td>Extended database copy management features. Improved performance of the database copy management feature by reducing data passed to a copy.</td></tr><tr title="Версия 8.3.15" class="tag_117 tag_58"><td><a name="51d3a7bb-1981-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>New feature: you can get the data size that this data occupies in DBMS tables (including a specific data area). Upon calculating the size, the size of data history, extensions, and platform service tables (indexes, etc.) is not considered.
New global context method: <span class="term">GetDataBaseDataSize()</span>.</td><td>This feature was not provided.</td><td>New feature: you can estimate the size of data available in a database area or table.</td></tr><tr title="Версия 8.3.15" class="tag_38"><td><a name="d1af4847-1fbe-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: you can mark a managed extension property so that a mismatch of this property in the extended configuration and in the extension will not block the extension use, but a user will get a message stating that the property value in the extension and the property value in the extended configuration do not match.</td><td>This feature was not provided.</td><td>New feature: informing of changes of some extended configuration properties is available. Changing such properties does not block extension use, but this change must be processed by the extension developer separately.</td></tr><tr title="Версия 8.3.15" class="tag_38 tag_20"><td><a name="5cd51c74-199b-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New feature: you can map extended configuration objects and extensions by IDs. Implemented the feature helping to resolve conflicts upon rename conflicts.
Mapping objects by IDs can be disabled.
New property for the configuration extension:<span class="interface"> Support mapping to extended configuration objects by internal IDs</span>. New property for adopted extension objects:<span class="interface"> Extended configuration object</span>.</td><td>Extended configuration objects and extensions were mapped only by names.</td><td>Simplified diagnostics of renaming an extended configuration object adopted to an extension. Now there is a feature for resolving conflicts upon such rename.</td></tr><tr title="Версия 8.3.15" class="tag_38"><td><a name="1df7b8bb-1fbf-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Upon creating a new extension, the <span class="interface">Compatibility mode</span> extension property is no longer a managed property.</td><td>Upon creating a new extension, the <span class="interface">Compatibility mode</span> extension property was a managed property.</td><td>Simplified development and applicability of extensions.</td></tr><tr title="Версия 8.3.15" class="tag_64"><td><a name="fc7188fb-1fae-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New pictures are added to the picture library: <span class="term">Notify</span>, <span class="term">DontNotify</span>, <span class="term">DontDisturb</span>, and <span class="term">SendMessage</span>.</td><td>The listed pictures were not available in the picture library.</td><td>The picture library is upgraded.</td></tr><tr title="Версия 8.3.15" class="tag_38"><td><a name="96b5c0f8-1fc8-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: you can adapt extended configuration methods. An extended method is fully copied to an extension where changed code is enclosed by preprocessor directives.
During application, it is checked whether the extended method is not changed in relation to the method in the extension.
New annotation: <span class="term">ChangeAndValidate</span>. New preprocessor directives: <span class="term">Delete </span>and <span class="term">Insert</span>.
You can change one method only in one extension. If two extensions that extend the same method using the <span class="term">ChangeAndValidate </span>annotation are found, only one extension will be applied to the infobase.
If a method change in the extended configuration is found, three-way merge using an external application only is available. If an external application for comparing and merging modules is not configured in Designer, merge will be unavailable.</td><td>Making changes to the method with control of module source code consistency was unavailable.</td><td>Simplified extended configuration method extension if a small method change is required.</td></tr><tr title="Версия 8.3.15" class="tag_28"><td><a name="45256fb7-1fcb-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>When you start the web client on mobile devices, there is no message prompting that the used web browser version is not supported. New feature: partial support of the web client on mobile devices. Full support of the web client on mobile devices is not implemented.<p>Fixed problems that occur in the web client on mobile devices in main scenarios.</p></td><td>Web client was supported on iPad tablets only.</td><td>Web client is partially available on mobile devices.</td></tr><tr title="Версия 8.3.15" class="compat tag_36 tag_1"><td><a name="a2fbf1bf-1fcc-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>New feature: upon solving a system of linear equations, you can search for connected components of various types for graphs built based on a system of linear equations.
Implemented the <span class="term">ComponentsGetMethod </span>parameter of the <span class="term">SolvingLinearEquationsSystems.GetConnectedComponents()</span> method. In 8.3.14 version compatibility mode, this parameter value will be <span class="term">StronglyConnectedComponentsWithoutLinkRequirementWithinComponents</span>.</td><td>This feature was not provided.</td><td>Advanced features for solving a system of linear equations.</td></tr><tr title="Версия 8.3.15" class="tag_4"><td><a name="d2652260-2073-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New link to collaboration system messages.<p>Implemented the <span class="term">CollaborationSystemStandardCommand.GetMessageURL</span> system enumeration value.</p></td><td>This feature was not provided.</td><td>Now you can obtain links to specific collaboration system messages.</td></tr><tr title="Версия 8.3.15" class="tag_115"><td><a name="7c6314f6-217a-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>New feature: a flag field of a client application form can be displayed as an off-on switch. New property of the <span class="term">CheckBoxType.Switch</span> system enumeration.
In<span class="interface"> version 8.3.7</span> or earlier compatibility mode and in platform version earlier than 8.3.15, the <span class="term">CheckBoxType </span>property value set to the <span class="term">Switch </span>value is the <span class="term">Auto </span>value.</td><td>This feature was not provided.</td><td>Extended system presentation features.</td></tr><tr title="Версия 8.3.15" class="compat tag_115 tag_1"><td><a name="a0f59d26-22df-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The client application displays a text document, a spreadsheet document, a graphical schema, and a picture in the client application system form. This is available in the following cases:<ul><li>When you create or open a document using the <span class="interface">File </span>menu.</li><li>When you call the <span class="term">Show()</span> method of the relevant 1C:Enterprise language object or the <span class="term">ShowValue()</span> method for the <span class="term">Picture </span>type object.</li><li>When you drag a file from the operating system.</li><li>When you open a collaboration system attachment.</li></ul><p>A form with a displayed spreadsheet document or graphical schema has a command bar making editing of the relevant document easier.
New events for a form field extension for a spreadsheet document, a text document, and a graphical schema: <span class="term">BeforeWrite</span>, <span class="term">AfterWrite </span>and <span class="term">BeforePrint</span>.
This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>The client application displayed a text document, a spreadsheet document, a graphical schema, and a picture in special forms. Such forms did not have command bars.</td><td>Editing platform documents is now more convenient and intuitive. You can now process saving and printing of a text document, a spreadsheet document, and a graphical schema.</td></tr><tr title="Версия 8.3.15" class="compat tag_115 tag_1"><td><a name="6ba3b5f3-22ee-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Implemented the option to manage the command home position in the command bar:
<ul><li>In the <span class="interface">More </span><span class="interface">actions</span> menu only.</li><li>In command bar only.</li><li>Both (a command bar and the <span class="interface">More </span><span class="interface">actions </span>menu).</li><li>Determine automatically.</li></ul><p>New form button property: <span class="term">LocationInCommandBar</span>.
The <span class="term">OnlyInAllActions </span>form button property is deprecated and supported for compatibility purposes only. Implemented automatic filling of the <span class="term">LocationInCommandBar </span>property based on the <span class="term">OnlyInAllActions </span>property.
Now this mode is available for the client application form button when there is no more than one button linked to one command inside the automatically filled group.
New client application button property: <span class="term">CommandUniqueness</span>.
New property for the picture field extension and the <span class="term">Picture </span>kind decoration: <span class="term">Scale</span>. This property is ignored in version 8.3.6 or earlier compatibility mode.</p></td><td>For a client application form command, only an indication that a command was located either in the command bar or in the <span class="interface">More </span><span class="interface">actions </span>menu was available.</td><td>Improved options for creating command interface of the client application form.</td></tr><tr title="Версия 8.3.15" class="tag_64"><td><a name="8cf68907-22f1-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New pictures are added to the picture library: <span class="term">ZoomOut </span>and <span class="term">ZoomIn</span>.</td><td>The listed pictures were not available in the picture library.</td><td>The picture library is upgraded.</td></tr><tr title="Версия 8.3.15" class="tag_115"><td><a name="3a75f3dd-23d5-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The following features are available for the <span class="term">Planner </span>object:<ul><li>Control of planner item representation if there is not enough space in the field: show all items by changing the line height or saving the line height, and show the <span class="interface">More actions </span>menu. Implemented the <span class="term">Planner.Items</span><span class="term">BehaviorOnLackOfSpace </span>property.</li><li>You can set the minimum column height and width of the planner. As a result, instead of constant reduction of planner items, it will be possible to save the minimum item size and add a scroll bar if items do not fit the form field. New properties for the <span class="term">Planner </span>object: <span class="term">ColumnMinWidth</span>, <span class="term">AutoColumnMinWidth</span>, <span class="term">RowMinHeight</span>, and <span class="term">AutoRowMinHeight</span>.</li><li>Freeze a dimension title and a time scale of the planner. Fixed objects will be visible for a user upon scrolling the planner. New properties for the <span class="term">Planner </span>object: <span class="term">FixDimensionsHeader </span>and <span class="term">FixTimeScaleHeader</span>.</li></ul></td><td>These features were not provided.</td><td>New planner features.</td></tr><tr title="Версия 8.3.15" class="tag_4"><td><a name="9f14c73c-2481-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: you can define a list of selecting collaboration system users upon creating a context conversation message, a noncontext conversation message, or a video call. You can now create a form of selecting collaboration system users.
New event for the <span class="term">ClientApplicationForm </span>object and client application module: <span class="term">CollaborationSystemUserAutoComplete</span>.
New event for the <span class="term">ClientApplicationForm </span>object and client application module: <span class="term">CollaborationSystemUserChoiceFormGetProcessing</span>.
New сonfiguration property: <span class="term">DefaultCollaborationSystemUserChoiceForm</span>.
You can now get a context conversation ID in the client application form (on the client application side). Implemented the <span class="term">BeginGettingConversation() </span>method.</td><td>There was no option to override a list of selecting collaboration system users upon selecting a user.
Earlier, you could get a context conversation ID on the server side only.</td><td>New collaboration system operations for selecting users upon creating messages, conversations, and video calls.</td></tr><tr title="Версия 8.3.15" class="tag_96"><td><a name="9505a0d0-2536-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>Updated the <span class="interface">Taxi </span>interface. New appearance includes the following main changes:<ul><li>Main application window (running under Windows) has no title by default.</li><li>Created the main panel containing access to primary tools of the command interface.</li><li>Tools panel commands are reallocated between other interface items. </li><li>The tools panel is no longer available as a separate panel.</li><li>The system command bar is no longer available.</li><li>Changed the main menu components and location.</li><li>Changed the appearance of auxiliary windows and dialog boxes.</li><li>Created a global search bar displayed in the main panel of the main application window. Global search bar is unavailable in the following main window modes: kiosk, workplace, and full-screen workplace. You can set up search behavior using 1C:Enterprise language. Implemented the <span class="term">GlobalSearch </span>global context property. New application module events: <span class="term">OnGlobalSearch </span>and <span class="term">OnGlobalSearchResultChoice</span>.</li><li>New feature: using the search bar, you can open a link, an external resource URL, perform arithmetic operations, and so on.</li><li>New command <span class="interface">Search everywhere</span> in the context menu of some form items (with supported selection). The search is carried out using the search bar.</li><li>New <span class="interface">Get link </span>button in the auxiliary window title.</li></ul><p>Implemented the <span class="term">StrFindAndHighlightByAppearance</span><span class="term">()</span> global context method that allows you to highlight some substrings in the string.</p><p>The <span class="term">ClientApplicationInterfaceContentSettingsItem </span>object cannot be created for the <span class="term">ToolsPanel </span>panel. The tools panel is ignored in the settings of the main application window panels.</p><p>New methods for the <span class="term">ClientApplication </span>object: <span class="term">GetOSTitleRepresentation()</span> and <span class="term">SetOSTitleRepresentation()</span>.</p><p>The <span class="interface">Default search form</span> сonfiguration property is deprecated. We recommend that you use global search feature instead.
</p></td><td>The <span class="interface">Taxi</span> interface had different appearance.</td><td>Improved application navigation, increased usability, and developed the interface in accordance with modern trends in interface creation.</td></tr><tr title="Версия 8.3.15" class="tag_26"><td><a name="c462665b-2543-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Upon editing spreadsheet document headers and footers, automatic calculation of the page field size is available now if the specified header or footer cannot be placed in the current page field sizes. To calculate the size, click <span class="interface">Ok </span>in the headers and footers editing form and page parameter setting form.
New feature: you can get the header or footer size. New feature: you can get the page field size.
New methods for the <span class="term">SpreadsheetDocument </span>object: <span class="term">CalculateHeaderSize</span><span class="term">()</span>, <span class="term">CalculateFooterSize</span><span class="term">()</span>, <span class="term">GetPrinterTopMarginSize()</span>, <span class="term">GetPrinterBottomMarginSize()</span>, <span class="term">GetPrinterLeftMarginSize()</span>, and <span class="term">GetPrinterRightMarginSize()</span>.</td><td>This feature was not provided.
Earlier, you could pick the size of fields, headers, and footers only manually or iteratively.</td><td>New feature: spreadsheet document page fields can be set automatically according to the specified header or footer.</td></tr><tr title="Версия 8.3.15" class="tag_21"><td><a name="b3f10428-254c-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Implemented search by meaningful word parts. In search results, a word is now highlighted if it has a meaningful part.
New feature: you can specify meaningful word parts in user dictionaries of full-text search. New item for a description file of a user dictionary of full-text search: <span class="term">&lt;Roots&gt;</span>.
To enable search by meaningful word parts, rebuild a full-text search index.
It works automatically if the Russian language is selected in regional infobase settings or a user dictionary of full-text search with a list of meaningful word parts is specified for the infobase.
New methods for full-text search manager: <span class="term">GetSeparationOfCompositeWordsMode()</span> and <span class="term">SetSeparationOfCompositeWordsMode()</span>.</td><td>This feature was not provided.</td><td>Improved full-text search usability.</td></tr><tr title="Версия 8.3.15" class="tag_27"><td><a name="ec45372d-254e-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>If you need to dump configuration information (the <span class="term">DumpConfigToFiles </span>command of Designer batch mode) in a file with objects to dump (the <span class="term">listFiles </span>dump command parameter), specify the <span class="term">Configuration </span>ID. There is no need to specify a configuration name.</td><td>If you needed to dump configuration information (the <span class="term">DumpConfigToFiles </span>command of Designer batch mode) in a file with objects to dump (the <span class="term">listFiles </span>dump command parameter), you needed to specify the <span class="term">Configuration </span>ID and a configuration name (dot-separated).</td><td>Simplified configuration dump to XML files.</td></tr><tr title="Версия 8.3.15" class="tag_4"><td><a name="011245c7-4aec-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Now you can block a collaboration system user. A blocked user cannot interact with the collaboration system. Now you can determine a linked infobase user by a collaboration system user.<p>New properties for the <span class="term">CollaborationSystemUser</span> object: <span class="term">IsLocked</span> and <span class="term">InfoBaseUserID</span>. Implemented the <span class="term">GetUsers()</span> method for the collaboration system manager.</p><p>Standard data processor of collaboration system management supports blocking and unblocking of collaboration system users.
</p></td><td>These features were not provided.</td><td>New operations with collaboration system users. Now you can disable a user from the collaboration system, for example, if a user is fired.</td></tr><tr title="Версия 8.3.15" class="tag_64"><td><a name="0539cf01-5164-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New pictures are added to the picture library: <span class="term">ExclamationDialog</span>, <span class="term">QuestionDialog</span>, <span class="term">StopDialog</span>, and <span class="term">InformationDialog</span>.</td><td>The listed pictures were not available in the picture library.</td><td>The picture library is upgraded.</td></tr></table><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cb4-14ce-11e9-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.15" class="compat tag_43 tag_115 tag_1"><td><a name="1752ab79-17eb-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Typing a text in a form table linked to a dynamic list does not lead to an input focus change and search start if the following conditions are met:
<ul><li>Form item addition <span class="interface">Search bar</span> is available in the form.</li><li>For the form table, the <span class="interface">Search upon character input</span> property is set to<span class="interface"> Do not use</span>.</li></ul><p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>Typing a text in a form table linked to a dynamic list led to an input focus change and search start if the following conditions are met:<ul><li>Form item addition <span class="interface">Search bar</span> is available in the form.</li><li>For the form table, the <span class="interface">Search upon character input</span> property is set to<span class="interface"> Do not use</span>.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_12"><td><a name="01163c84-17f1-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>For the <span class="interface">Active users</span> standard function, the list update button is moved to the beginning of the list form command bar.</td><td>For the <span class="interface">Active users</span> standard function, the list update button was located at the end of the list form command bar.</td><td>Unified list update command location in various forms of standard functions.</td></tr><tr title="Версия 8.3.15" class="tag_12 tag_6"><td><a name="51807084-17f3-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New standard function: <span class="interface">Server management</span>. This function is similar to the cluster management console. It requires a server cluster administration server for all servers to be administered. Server operations are carried out using the <span class="term">ServerAdministration </span>object. For a list of functional differences between the standard function and the cluster console, see 1C:Enterprise documentation. The standard function system requirements are the same as the system requirements of the <span class="term">ServerAdministration </span>object.</td><td>This feature was not provided.
Interactive server cluster administration was available from the cluster management console only.</td><td>Interactive server cluster administration is now available not only under Windows. Cluster administration tools are available in the client application using the <span class="interface">All functions</span> dialog box.</td></tr><tr title="Версия 8.3.15" class="tag_12 tag_68"><td><a name="4dc999e5-1996-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>Implemented the standard function that allows you to view data history, set an arbitrary filter, and update data history interactively.</td><td>Viewing data history of a certain data object only was available in the platform. Custom filter setup to view history was unavailable.</td><td>Extended interactive data history operations.</td></tr><tr title="Версия 8.3.15" class="tag_115 tag_96 tag_4"><td><a name="48ad0f3d-2469-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Upon form scaling, the scale is shown on a logarithmic scale. <span class="interface">100%</span> value is in the middle of the scale.
New feature: you can click a middle button to:<ul><li>Close search state items (in a dynamic list).</li><li>Remove recipients from collaboration system context conversations.</li><li>Remove attachments from unsent collaboration system messages.</li></ul></td><td>Upon form scaling, the scale was shown on a linear scale. <span class="interface">100%</span> value was at the beginning of the scale.
You could close search state items (in a dynamic list), remove recipients from context conversations of the collaboration system, and
remove attachments from unsent messages of the collaboration system only using the required object control (X in the right part of the item).</td><td>Improved application interface usability.</td></tr></table><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cb5-14ce-11e9-a3f7-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.15" class="compat tag_45 tag_1"><td><a name="eb3dba64-1592-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>New feature: the query language now has optimized calculations of expressions being virtual table parameters. This optimization is similar to optimization of standard query language expressions.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>The query language did not have optimized calculations of expressions being virtual table parameters.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_15"><td><a name="ac3f23fa-1962-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Optimized use of RAM on Linux.</td><td>RAM was used less effectively on Linux.</td><td>Decreased RAM fragmentation and, as a result, decreased the amount of used RAM on Linux. Slightly improved application performance.<p>
</p></td></tr><tr title="Версия 8.3.15" class="tag_45 tag_6"><td><a name="1e203e36-197b-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Optimized execution of a query containing constant values in the selection list. Constant values from the query body are implemented by query parameters. This reduces the amount of plan recompilation in DBMS and, as a result, improves performance of the same queries if only their constant value is different.
</td><td>This feature was not provided.<p>Constant values were not used by parameters and were used directly in the query body.</p></td><td>Execution time of queries containing constant values is reduced in some cases. In particular, recalculation of register totals can take less time in client/server mode.</td></tr><tr title="Версия 8.3.15" class="tag_52"><td><a name="63fe12d6-197c-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>Improved performance of the managed lock manager upon transaction completion if there are a lot of transactions that locked the key range of one space.</td><td>The managed lock manager spent more time on transaction completion if there were a lot of transactions that locked the key range of one space.</td><td>Parallel operation is improved in case of similar load generated by numerous sessions.</td></tr><tr title="Версия 8.3.15" class="tag_118"><td><a name="911b7c6e-197c-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 118); return false;">Configuration comparison and merging</a>.<br></td><td>Optimized comparison/merge of configurations.</td><td>Comparison and merge of configurations took more time.</td><td>Comparison and merge of configurations is now faster.</td></tr><tr title="Версия 8.3.15" class="compat tag_45 tag_1"><td><a name="2c313f6b-197d-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If the query text contains a condition with two constant expressions and each expression is not a string, the condition will be replaced with an expression result before passing the query to DBMS.<p>
</p><p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>Conditions which consisted of constant expressions were not simplified.</td><td>In some cases, query performance is improved.</td></tr><tr title="Версия 8.3.15" class="tag_49"><td><a name="557d5d9e-197f-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 49); return false;">Binary data</a>.<br></td><td>Buffers used with objects of the <span class="term">FileStream </span>type are reset only if the <span class="term">FileStream.ResetBuffers()</span> method is executed explicitly.</td><td>Buffers used with objects of the <span class="term">FileStream </span>type were reset:<ul><li>Upon executing the<span class="term"> FileStream.ResetBuffers() </span>method explicitly.</li><li>Upon calling the<span class="term"> FileStream.Close() </span>method.</li><li>Upon deleting the <span class="term">FileStream </span>object.</li></ul></td><td>Decreased load on a disk drive upon intensive operations with the <span class="term">FileStream </span>type objects.</td></tr><tr title="Версия 8.3.15" class="tag_25"><td><a name="b57b6a6d-1994-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Improved performance of the <span class="term">Value()</span> function of the data composition system expression language. </td><td>The <span class="term">Value()</span> function of the data composition system expression language worked more slowly.</td><td>Improved performance of the <span class="term">Value()</span> function of the data composition system expression language. </td></tr><tr title="Версия 8.3.15" class="tag_19 tag_45"><td><a name="4704bec9-1995-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Upon query execution, faster creation of a temporary table from a value table passed as a query parameter is available now.</td><td>Upon query execution, creation of a temporary table from a value table passed as a query parameter took longer time.</td><td>Upgrade: faster creation of a temporary table based on a value table using the query language.</td></tr><tr title="Версия 8.3.15" class="tag_70 tag_29"><td><a name="d1de9954-1995-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Removed Microsoft VC++ Runtime Redistributable Package from thin client distribution package (for Windows).</td><td>Microsoft VC++ Runtime Redistributable Package was inside thin client distribution package (for Windows).</td><td>Reduced thin client distribution package for Windows.</td></tr><tr title="Версия 8.3.15" class="tag_29"><td><a name="9af43209-1996-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Removed Microsoft Windows Installer 3.0 Package from platform distribution package (for Windows).</td><td>Microsoft Windows Installer 3.0 Package was inside platform distribution package (for Windows).</td><td>Reduced platform distribution package for Windows.</td></tr><tr title="Версия 8.3.15" class="compat tag_25 tag_1"><td><a name="91446ba2-1faa-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Composer of data composition system template considers to be used only those fields that are used in the conditional appearance item of data composition only when this conditional appearance item is applied at least to one of the displayed fields (also upon applying conditional appearance to all fields). If conditional appearance item is not applied to any field, used fields are considered to be unused and are not added to the resulting query of the data composition template.
Fields, which are not used in conditional appearance, are not added to the data acquisition query.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Composer of data composition system template considered to be used all fields in conditional appearance item even if this conditional appearance item was not applied to any field.
All fields, which were formally used in conditional appearance, were added to the data acquisition query.</td><td>Improved generation of the query of data composition system data acquisition.</td></tr><tr title="Версия 8.3.15" class="compat tag_45 tag_1"><td><a name="325d433c-1fd6-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If a query with merges contains a false condition, the part of the merge with the false condition is not passed to DBMS. False conditions are detected only for <span class="term">Number </span>or enumeration data type.
Upon merge optimization, the platform can, if necessary, add a requirement for obtaining different records to the resulting query.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>This feature was not provided.</td><td>In some cases, query time will be decreased.</td></tr><tr title="Версия 8.3.15" class="tag_6"><td><a name="c28fc712-2177-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved client connection transfer to a new working process upon automatic restart of the working process.</td><td>Client connection transfer to a new working process upon automatic restart of the working process took more time.</td><td>Transfer of existing sessions to a new working process now takes less time. Decreased (or totally eliminated) client application delay upon transfer. Significantly improved client application operation in interactive mode in this case.</td></tr><tr title="Версия 8.3.15" class="compat tag_82 tag_1"><td><a name="37e66288-239f-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Improved performance of virtual tables of the accounting register, updated totals upon writing register records, and recalculated accounting register totals.
Increased stored data volume and slightly increased record set storage time.
To make accounting register performance increase noticeable, disable the compatibility mode. Accounting registers will be restructured. If infobase size exceeds 10 GB, it is recommended that you use optimized tool of database configuration update for restructuring.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Operations with virtual tables of accounting register, update of totals upon writing register records, and recalculation of accounting register totals took more time.</td><td>Data acquisition from accounting registers is faster now.</td></tr><tr title="Версия 8.3.15" class="compat tag_82 tag_45 tag_1"><td><a name="b92cb61a-23a2-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Improved query to accounting register if the query contains a condition of including the recorder in a list generated under a subquery:<span class="term"> Recorder IN (subquery)</span>.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Query to accounting register if the query contains a condition of including the recorder in a list generated under a subquery: <span class="term">Recorder IN (subquery)</span>, poor performance.</td><td>Improved data acquisition from the accounting register in some cases.</td></tr><tr title="Версия 8.3.15" class="tag_45"><td><a name="a52008d1-2541-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If you execute a query in the infobase file mode with data from two tables and these tables are connected with an internal connection and there are indexes of link fields in both tables, then the first iteration is performed for the table with less records.</td><td>Number of records in tables was not analyzed upon executing a query in the infobase file mode with data from two tables and these tables were connected with an internal connection and there were indexes of link fields in both tables.</td><td>In some cases, improved query performance in the infobase file mode.</td></tr><tr title="Версия 8.3.15" class="tag_25"><td><a name="fe14507e-4661-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Improved generation of data composition system template if a data composition schema query contains a lot of unions (400 or more unions).</td><td>Generation of data composition system template took a significant amount of time if a data composition schema query contained a lot of unions (400 or more unions).</td><td>Improved performance of the data composition system if there are a lot of unions in a data composition schema query.</td></tr><tr title="Версия 8.3.15" class="tag_6 tag_19"><td><a name="529b9ed8-4664-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Upgrade for PostgreSQL DBMS: better posting of large documents in the accounting register and improved <span class="term">RecordsWithExtDimensions </span>virtual table.</td><td>Posting of large documents in the accounting register and operations with the <span class="term">RecordsWithExtDimensions </span>virtual table took more time if PostgreSQL DBMS was used.</td><td>Optimized use of the accounting register if PostgreSQL DBMS is used.</td></tr></table><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cb6-14ce-11e9-a3f7-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.15" class="compat tag_25 tag_1"><td><a name="27405f3e-1597-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a type of one of the operands in a data composition system expression is arbitrary, the resulting expression will also have an arbitrary type.<p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>If a value with an arbitrary type was present in a data composition system expression, an arbitrary type was ignored upon calculating the resulting expression time.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_96"><td><a name="23030c93-17e7-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>Edited pictures in the client application interface (and in the picture library) for the spreadsheet document commands used for collapsing and expanding all groups.</td><td>Pictures in the client application interface (and in the picture library) for the spreadsheet document commands used for collapsing and expanding all groups were different.</td><td>Now pictures of the spreadsheet document commands used for collapsing and expanding all groups of the spreadsheet document better correspond to performed actions.</td></tr><tr title="Версия 8.3.15" class="tag_20"><td><a name="7f927573-18a2-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the form editor, the <span class="interface">Action </span>property of the adopted form command contains a name of the method, which is a command handler in the extended configuration. Navigation to the command handler is unavailable.</td><td>In the form editor, the <span class="interface">Action </span>property of the adopted form command contains a name of the method, which is a command handler in the extended configuration. Navigation to the command handler generated an error.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_45 tag_1"><td><a name="4236978c-1fab-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Query language operation <span class="term">CASE </span>will be considered a constant and replaced with a constant if all operation branches contain only constant expressions. Therefore, operation <span class="term">CASE </span>can be used in constant parameters of virtual tables if all branches of operation <span class="term">CASE </span>contain only constant expressions.
If an operand of operation <span class="term">CASE </span>contains <span class="term">NULL </span>in query totals, then the operation result will be a value specified in <span class="term">ELSE </span>or <span class="term">NULL </span>if it is absent.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Query language operation <span class="term">CASE </span>was not replaced with a constant and could not be used in constant parameters of virtual tables. Upon calculating operation <span class="term">CASE </span>in query totals, if the operation operand contained <span class="term">NULL</span>, the operation result was <span class="term">NULL</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_115"><td><a name="0f853fad-23a5-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>New feature: you can change properties of client application form items without calling a server:<ul><li>Decoration:</li><li>Decoration label extension:</li><li>Form group extension for a command bar:</li><li>Form group extension for a page:</li><li>Form group extension for a normal group:</li><li>Button</li><li>Form field extension for picture field:</li></ul></td><td>This feature was not provided. Accessing the specified properties of client application form items required a server call.</td><td>Reduced client/server interaction upon managing a client application form using 1C:Enterprise language.</td></tr><tr title="Версия 8.3.15" class="tag_4"><td><a name="07e29cc3-23ac-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented the following features in the collaboration system interface:<ul><li>Upon editing a message, the cursor is placed at the end of the message text.</li><li>Upon sending a message, trailing spaces are trimmed in the message.</li><li>You can open a collaboration system user profile by clicking the user avatar.</li><li>The unread mark is cleared in a conversation if any of the following actions is carried out:</li><ul><li>Click a link in a message.</li><li>Click a username or a user avatar.</li><li>Click an attachment in a message.</li><li>Click a message action.</li><li>Right-click (open the context menu).</li></ul><li>When the default collaboration system form is first opened, the first conversation is not activated.</li><li>In the thick and thin client applications, you can select a notification in the notification center by clicking a message picture. The upgrade is ignored in the web client.</li></ul><p>Changed the standard user group picture in the drop-down list of user selection.</p></td><td>The collaboration system interface had different behavior:<ul><li>Upon editing a message, the cursor was not placed at the end of the message.</li><li>Upon sending a message, leading and trailing spaces were trimmed.</li><li>A user profile was opened by clicking a username.</li><li>When the default collaboration system form was first opened, the first conversation was activated.
In the thick and thin client applications, you could select a notification in the notification center only by clicking a message text. In the web client, you could select a notification by clicking a message text or a message picture.</li></ul></td><td>Improved collaboration system interface.</td></tr><tr title="Версия 8.3.15" class="compat tag_25 tag_1"><td><a name="dad12601-23af-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Commands <span class="interface">Generate</span>, <span class="interface">Print</span>, <span class="interface">Save</span>, and <span class="interface">Compact mode </span>will be added to the report form command bar (with enabled automatic filling) if a property of the report form<span class="interface"> Report resul</span><span class="interface">t</span> is set. If a property of the report form <span class="interface">Report result </span>is not set, commands <span class="interface">Generate</span>, <span class="interface">Print</span>, <span class="interface">Save</span>, and <span class="interface">Compact mode </span>will not be added to the report form command bar, which is filled in automatically.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Commands <span class="interface">Generate</span>, <span class="interface">Print</span>, <span class="interface">Save</span>, and <span class="interface">Compact </span><span class="interface">mode </span>were always added to the report form command bar with enabled automatic filling.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_63 tag_1"><td><a name="c42d76d5-2463-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>If a format is not set explicitly for number presentations in the chart settings, the default format (considering regional infobase settings) will be applied to the numbers.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>If a format was not specified explicitly for number presentations in the chart settings, no specific formatting was applied to the numbers.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_115 tag_1"><td><a name="2c58e50b-2466-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If an input field is in the list selection mode, you can search for the value as follows:<ul><li>First, presentations are searched by the beginning of the line if the presentation is specified explicitly.</li><li>Then search considering a list value type is carried out:</li><p>
</p><p>This change is not implemented in version 8.3.14 compatibility mode.</p><p>
</p></ul></td><td>If the input field was in the list selection mode, search was carried out by the beginning of the line for all types in the specified presentation or if the presentation was not specified, search was carried out in a string value presentation from the selection list.</td><td>Now search in input fields, which use a selection list, is more predictable and better meets user expectations.</td></tr><tr title="Версия 8.3.15" class="tag_4"><td><a name="b9d8ed07-246c-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: in the collaboration system, you can manage a number of received notifications for context and noncontext conversations. You can disable notifications of a conversation, receive notifications only for the messages to a user, or receive notifications of all messages.
This feature can be set up using both user interface and 1C:Enterprise language.
Implemented methods <span class="term">GetWatchMode()</span> and <span class="term">SetWatchMode()</span> for noncontext conversations. Implemented the <span class="term">User </span>parameter for the <span class="term">GetWatchMode()</span> and <span class="term">SetWatchMode()</span> methods.
Implemented the following methods of the collaboration system manager: <span class="term">SetConversationNotificationRepresentation()</span> and <span class="term">GetConversationNotificationRepresentation().</span></td><td>Previously, you could only disable all notifications in a collaboration system.
The <span class="term">GetWatchMode</span><span class="term">()</span> and <span class="term">SetWatchMode()</span> methods were used for context conversations only.</td><td>Expanded capabilities of the collaboration system interface.</td></tr><tr title="Версия 8.3.15" class="tag_52 tag_4"><td><a name="51f36674-2472-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: now in the client application (thin, thick, and web client), you can unlock object lock set by another user or the same user in another session. An object lock is a lock set interactively upon editing an object in the form or using methods <span class="term">Lock()</span>, <span class="term">LockDataForEdit()</span>, and <span class="term">LockFormDataForEdit()</span>.
Now when you find a lock, you can start a conversation with a lock initiator in collaboration system (if the infobase supports the collaboration system).</td><td>This feature was not provided.</td><td>Simplified operations with infobase data in some cases.</td></tr><tr title="Версия 8.3.15" class="tag_96"><td><a name="5256086e-3c3a-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>Implemented the following features for dialog boxes generated by 1C:Enterprise language methods <span class="term">DoQueryBox()</span>, <span class="term">ShowQueryBox()</span>, <span class="term">DoMessageBox()</span>, and <span class="term">ShowMessageBox()</span> (in all client applications and <span class="interface">Version 8.2</span> and <span class="interface">Taxi</span> interfaces):<ul><li>Updated the dialog boxes.</li><li>If a title is not specified for a dialog box (in the relevant method parameter), this dialog box is opened without a title.</li><li>Upon creating dialog boxes, scaling set for all forms in the <span class="interface">Taxi </span>interface is considered.</li><li>Changed pictures displayed in the relevant dialog boxes in the <span class="interface">Taxi </span>interface.</li></ul></td><td>Dialog boxes generated by 1C:Enterprise language methods <span class="term">DoQueryBox()</span>, <span class="term">ShowQueryBox()</span>, <span class="term">DoMessageBox()</span>, and <span class="term">ShowMessageBox()</span> had different appearance and did not consider form scale in <span class="interface">Taxi</span> interface.</td><td>Improved appearance of dialog boxes generated by 1C:Enterprise language methods <span class="term">DoQueryBox()</span>, <span class="term">ShowQueryBox()</span>, <span class="term">DoMessageBox()</span>, and <span class="term">ShowMessageBox()</span>.</td></tr><tr title="Версия 8.3.15" class="compat tag_26 tag_1"><td><a name="4dc2c3f0-494c-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Text orientation set for a spreadsheet document cell area is considered upon text output if the Windows system font is selected as a font.<p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>If the Windows system font was selected as a font of a spreadsheet document cell area, text orientation set for a spreadsheet document cell area was not considered upon text output.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_25 tag_1"><td><a name="27f74abb-494d-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Now you can apply conditional appearance of a column of a data composition system report table to the entire column if one of the following usage areas is selected for a conditional appearance item: <span class="interface">In group</span>, <span class="interface">In hierarchical group</span>, or <span class="interface">&lt;Everywhere&gt;</span>.<p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>If usage area <span class="interface">In group</span>, <span class="interface">In hierarchical group</span>, or <span class="interface">&lt;Everywhere&gt;</span> was selected for a conditional appearance item upon applying appearance of a column of a data composition system report table, appearance could be specified for a table header and column total only.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_115"><td><a name="6836fc73-4952-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If a client application form contains one of the following items: a spreadsheet document field, a text document field, a graphical schema field, an HTML document field, a formatted document field, a geographical schema field, or a planner field, a submenu containing <span class="interface">Print</span>, <span class="interface">Save</span>, and <span class="interface">Preview </span>commands is generated in the form title. If there is more than one above-listed item in the form, menu commands are available for the current item of the specified type.<p>Preview command is not displayed in the web client.</p></td><td>This feature was not provided.</td><td>Improved form usability.</td></tr><tr title="Версия 8.3.15" class="tag_18"><td><a name="4257aeed-4955-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br></td><td>Add-ins work correctly in thin client (macOS) and Safari. Add-in revisions are not required.</td><td>Add-ins worked incorrectly in Safari but worked correctly in thin client (running under macOS).</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_45 tag_1"><td><a name="80306e14-4956-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>The following query language functions can be used as virtual table parameters that can have constant values only: <span class="term">SUBSTRING()</span>, <span class="term">YEAR()</span>, <span class="term">QUARTER()</span>, <span class="term">MONTH()</span>, <span class="term">DAYOFYEAR()</span>, <span class="term">DAY()</span>, <span class="term">WEEK()</span>, <span class="term">WEEKDAY()</span>, <span class="term">HOUR()</span>, <span class="term">MINUTE()</span>, and <span class="term">SECOND()</span>. You can use them only if all parameters have constant values in the specified functions. In this case, the calculated function value is added as a parameter value.<p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>The following query language functions could not be used as virtual table parameters that can have constant values only: <span class="term">SUBSTRING()</span>, <span class="term">YEAR()</span>, <span class="term">QUARTER()</span>, <span class="term">MONTH()</span>, <span class="term">DAYOFYEAR()</span>, <span class="term">DAY()</span>, <span class="term">WEEK()</span>, <span class="term">WEEKDAY()</span>, <span class="term">HOUR()</span>, <span class="term">MINUTE()</span>, and <span class="term">SECOND()</span>.</td><td>
<p>Now you can use date/time functions as parameters that can take only constant values, and virtual register tables in the query language. This is possible only if functions have constant values as parameters.</p></td></tr><tr title="Версия 8.3.15" class="tag_26"><td><a name="deefd2e5-4964-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Now you can edit (both interactively and using 1C:Enterprise language) page parameters of a spreadsheet document converted into compact mode.<p>For a compact spreadsheet document, you can now call the <span class="term">SetHorizontalStretch()</span> method.</p><p>Upon editing a compact spreadsheet document, both the compact document and the original document are changed.</p></td><td>A compact spreadsheet document did not support setting up page parameters.</td><td>Settings of spreadsheet document parameters for print and view are now more convenient.</td></tr><tr title="Версия 8.3.15" class="compat tag_115 tag_1"><td><a name="272b7649-4966-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In a form or a form group of the <span class="term">Normal </span>or <span class="term">Page </span>type with set horizontal grouping and the <span class="term">ChildItemsHorizontalAlign </span>property set to <span class="term">Left</span>, <span class="term">Center</span>, or <span class="term">Auto </span>(which is the same as <span class="term">Left </span>or <span class="term">Center</span>), all last form items or group items, for which the <span class="term">HorizontalAlignInGroup </span>property value is set to <span class="term">Right </span>up to the item, for which the <span class="term">HorizontalAlignInGroup </span>property value is not equal to <span class="term">Right</span>, are aligned right.<p>In a form or a form group of the <span class="term">Normal </span>or <span class="term">Page </span>type with set horizontal grouping and the <span class="term">ChildItemsVerticalAlign </span>property set to <span class="term">Top</span>, <span class="term">Center</span>, or <span class="term">Auto </span>(which is the same as <span class="term">Top </span>or <span class="term">Center</span>), all last form items or group items, for which the <span class="term">VerticalAlignInGroup </span>property value is set to <span class="term">Bottom </span>up to the item, for which the <span class="term">VerticalAlignInGroup </span>property value is not equal to <span class="term">Bottom</span>, are aligned bottom.</p><p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>In a form or a form group of the <span class="term">Normal </span>or <span class="term">Page </span>type with set horizontal grouping and the <span class="term">ChildItemsHorizontalAlign </span>property set to <span class="term">Left</span>, <span class="term">Center</span>, or <span class="term">Auto </span>(which is the same as <span class="term">Left </span>or <span class="term">Center</span>), only the last item in a form or a group was aligned right.<p>In a form or a form group of the <span class="term">Normal </span>or <span class="term">Page </span>type with set horizontal grouping and the <span class="term">ChildItemsVerticalAlign </span>property set to <span class="term">Top</span>, <span class="term">Center</span>, or <span class="term">Auto </span>(which is the same as <span class="term">Top </span>or <span class="term">Center</span>), only the last item in a form or a group was aligned bottom.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_32"><td><a name="c536574e-4a17-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>New feature: cleanup of the Mobile application builder cache directory. Artifacts saved to the cache directory more than 30 days ago are deleted. Temporary build directories remaining after unexpected build termination or interruption are also deleted.<p>This does not require setup and is fully automatic.</p></td><td>The Mobile application builder cache could increase in size only. The Mobile application builder did not provide cleanup of unused cached artifacts.</td><td>Stopped the uncontrolled growth of the Mobile application builder cache directory. The builder caches only the artifacts used during build for the last 30 days.</td></tr><tr title="Версия 8.3.15" class="tag_21 tag_6"><td><a name="024e4cf0-4ae9-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The full-text search string cannot contain more than 1,000 words. An error occurs upon excess. Functional words and search operators are not considered when counting the number of words.</td><td>The number of words in the full-text search string was not limited. Specifying a very large number of words in the search string could significantly reduce server cluster performance.</td><td>Improved application stability. Reduced risk of affecting the application responsiveness as a whole by specifying a very large full-text search string.</td></tr><tr title="Версия 8.3.15" class="tag_117"><td><a name="6c247d3c-55f9-11e9-84bd-0050569f678a"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>Enhanced database integrity check upon database configuration update. Several database tables can no longer get the same internal number. In this case, an exception is thrown and the database is not updated.</td><td>Upon database configuration update, internal numbers of database tables were not checked for uniqueness. As a result, various unexpected errors could occur when using the information system.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_78"><td><a name="fae0b17c-55fd-11e9-84bd-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>If thin client connects to the infobase via web server using HTTPS protocol, upon using the <span class="term">GetFile()</span>, <span class="term">GetFiles()</span>, <span class="term">BeginGettingFiles()</span>, <span class="term">BeginGetFileFromServer()</span>, and <span class="term">BeginGetFilesFromServer()</span> methods, reauthentication on the web server is no longer required.</td><td>If thin client connected to the infobase via web server using HTTPS protocol, upon using the <span class="term">GetFile()</span>, <span class="term">GetFiles()</span>, <span class="term">BeginGettingFiles()</span>, <span class="term">BeginGetFileFromServer()</span>, and <span class="term">BeginGetFilesFromServer()</span> methods, reauthentication on the web server was required.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cb7-14ce-11e9-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.15" class="compat tag_25 tag_1"><td><a name="33491353-17e8-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Composer of data composition template does not use the presentation expression specified for the calculated field upon generating an expression of group and total records for calculated fields being resources. Thus, the presentation expression for calculated fields being resources will be displayed in the report in detailed records only.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Composer of data composition template used an expression of the calculated field presentation being a resource in detailed, group, and total records.</td><td>Behavior of composer of data composition template is the same for calculated fields, data set fields, and calculated resource fields.</td></tr><tr title="Версия 8.3.15" class="compat tag_45 tag_25 tag_1"><td><a name="c8991313-17e8-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Right joins are not replaced automatically with similar left joins upon processing query text with the query constructor, query scheme, data composition system, and report builder.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Right joins were replaced automatically with similar left joins upon processing query text with the query constructor, data composition system, and report builder. If conversion failed to be performed, the connection was removed from the query.</td><td>Eliminated system behavior which could lead to an incorrect query.</td></tr><tr title="Версия 8.3.15" class="tag_78 tag_28"><td><a name="c08e4302-18b1-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Implemented the <span class="term">BeginGetFileFromServer()</span> and <span class="term">BeginGetFilesFromServer()</span> global context methods. In the interactive mode, methods do not require installing a file system extension on web client. New feature: you can get several files from the server as an archive.
The <span class="term">BeginRequestingUserPermission()</span> method allows you to request user permission for new methods.
The <span class="term">GetFile()</span>, <span class="term">BeginGettingFiles()</span>, and <span class="term">RequestUserPermission()</span> methods are deprecated and supported for compatibility purposes.
It is recommended that you use new methods in the application.</td><td>Current methods of receiving files from the server were not logical. Method of receiving several files from the server (<span class="term">BeginGettingFiles</span><span class="term">()</span>) in the web client required a file system extension.</td><td>Getting files from the server is now more transparent and convenient. Now a file system extension is no longer required to use the web client in the interactive mode.</td></tr><tr title="Версия 8.3.15" class="tag_78 tag_28"><td><a name="450d7ceb-18b4-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Implemented the <span class="term">BeginPutFileToServer()</span> and <span class="term">BeginPutFilesToServer()</span> global context methods. In the interactive mode, the methods do not require installation of a file system extension on web client. New feature: displayed progress of placing a file to the server. New feature: cancel placing a file to the server. New feature: simultaneous transfer of several files from a client computer to the server. Files being transferred are specified using the file search string.<p>The <span class="term">BeginRequestingUserPermission()</span> method allows you to request user permission for new methods.</p><p>The <span class="term">BeginPutFile()</span>, <span class="term">BeginPuttingFiles()</span>, and <span class="term">RequestUserPermission()</span> methods are deprecated and supported for compatibility purposes.</p><p>It is recommended that you use new methods in the application.</p></td><td>Existing methods of transferring files to the server (<span class="term">BeginPutFile()</span>, <span class="term">BeginPuttingFiles()</span>) did not allow to cancel placing files during transfer and display the transfer progress.</td><td>Putting files to the server is now more transparent and convenient. Now a file system extension is no longer required to use the web client in the interactive mode.</td></tr><tr title="Версия 8.3.15" class="compat tag_117 tag_58 tag_69 tag_1"><td><a name="892396f4-1983-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Method <span class="term">FindMarkedForDeletion()</span> will search all available objects of the current data area only if the <span class="term">Undefined </span>value is passed as a value of the first and the second method parameters.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Method <span class="term">FindMarkedForDeletion()</span> searched all available objects of the current data area only if the <span class="term">Undefined </span>value was passed as a value of the first method parameter only.</td><td>Unified set of parameters and behavior of methods with similar actions.</td></tr><tr title="Версия 8.3.15" class="compat tag_45 tag_1"><td><a name="83c9424e-23a1-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Query language behavior changes if: query is a merge of several queries, which are applied to a unified query and each merge query uses the <span class="term">TOP </span>keyword. In this case, each query in the merge turns into a nested query with ordering. If any of the nested query does not have the <span class="term">TOP </span>keyword, subquery is not built by ordering.
It is recommended that you analyze when queries that meet these conditions are used. When the compatibility mode is disabled, performance result of such queries can be different from the performance result of this query in compatibility mode.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>Query language behavior if: query was a merge of several queries, which were applied to a unified query and each merge query used the <span class="term">TOP </span>keyword, depended on the infobase option:
<ul><li>For file mode: first ordering, then selection of top records.</li><li>For client/server mode: first selection of the top ones (for each simple query). Ordering was not executed for simple queries. Ordering was executed only for merge result. Result repeatability was not guaranteed as the top items were selected from the query without ordering.</li></ul></td><td>Implemented similar behavior of a query containing merge, ordering, and the <span class="term">TOP </span>keyword in various infobase mode options.</td></tr><tr title="Версия 8.3.15" class="tag_6"><td><a name="c138a365-23d2-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Upon editing a server cluster resource consumption counter, the counter is reset only if the <span class="interface">Group </span>property is changed.<p>Implemented reset of a resource consumption counter instance:</p><ul><li>The <span class="interface">Delete </span>command is implemented for a resource consumption counter instance.</li><li>The <span class="term">clear </span>command is implemented for the <span class="term">rac </span><span class="term">counter </span>command.</li><li>The <span class="term">IAgentAdminConnection.clearAccumulatedValues()</span> method is implemented for Java interface of server cluster administration.</li><li>The <span class="term">AdministrationResourceConsumptionCounter.ClearAccumulatedValues()</span> method is implemented in 1C:Enterprise language.</li></ul><p>Now you can get a list of resource consumption counter values:</p><ul><li>The <span class="term">accumalated-values</span> command is implemented for the <span class="term">rac counter</span> command.</li><li>The <span class="term">IAgentAdminConnection.getAccumulatedResourceConsumptionCounterValues()</span> method is implemented for Java interface of server cluster administration.</li><li>The <span class="term">AdministrationResourceConsumptionCounter.GetAccumulatedValues()</span> method is implemented in 1C:Enterprise language.</li></ul><p>For a resource consumption counter instance, a field containing measurement time is implemented. To get measurement time:</p><ul><li>The <span class="term">time </span>property is implemented in the <span class="term">rac counter</span> command output.</li><li>The <span class="term">IresourceConsumptionCounterValue.getTime()</span> method is implemented for Java interface of server cluster administration.</li><li>The <span class="term">AdministrationResourceConsumptionCounter.Time</span> property is implemented in 1C:Enterprise language.</li></ul></td><td>Upon editing a server cluster resource consumption counter, the counter was reset if any of its properties were changed.<p>Other features were not provided.</p></td><td>Improved administration of server cluster resource consumption. Simplified setting of counters and resource consumption restrictions. Now you can analyze changes of accumulated data.</td></tr><tr title="Версия 8.3.15" class="compat tag_25 tag_104 tag_1"><td><a name="3ff53639-2477-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>In the data composition system, for the field separated by dot from the temporary table field or nested query, availability check includes checking that the field is not disabled with a functional option.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>In the data composition system, for the field separated by dot from the temporary table field or nested query, availability check did not include checking that the field is not disabled with a functional option. If a temporary table field or a nested query field was available, it was considered that all fields available via "." (dot) would also be available.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_25 tag_114 tag_1"><td><a name="18ea9474-247a-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 114); return false;">Charts of characteristic types</a>.<br></td><td>In the data composition system, a characteristic value type is considered upon getting a characteristic value (for any purpose, for example, sorting or filtering by it). If a value, which does not match the used characteristic value type, is written in the infobase, then <span class="term">NULL </span>will be used instead.
It is recommended that you analyze additional characteristics in the data composition system and make sure that the actual characteristic value type matches the type.
This change is not implemented in version 8.3.14 compatibility mode.</td><td>In the data composition system, a characteristic value type is not considered upon getting a characteristic value (for any purpose, for example, sorting or filtering by it). Even if a value, which does not match the used characteristic value type, is written in the infobase, it will be used.</td><td>Improved performance of the data composition system with additional characteristics (charts of characteristic types) by reducing the number of tables used in queries.</td></tr><tr title="Версия 8.3.15" class="tag_6"><td><a name="83c3fcab-2604-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Changed rules and settings of 1C:Enterprise server cluster monitoring system. Optimized use of server RAM. In particular, both working process parameters and cluster manager parameters are used when determining the amount of used memory.<p>New feature: server cluster setting, which allows you to specify whether a process dump is to be created when critical memory amount is exceeded.</p><p>New feature: working server properties that describe a temporarily allowable amount of process memory, a time interval that describes exceeding time of a temporarily allowable amount of process memory, and a critical memory amount.</p><p>The following settings are removed from the cluster properties:</p><ul><li>Allowed total memory.</li><li>Period of exceeding the memory threshold.</li><li>Threshold of server error variation.</li></ul><p>Settings that describe the amount of working process memory up to which server performance is considered to be sufficient, and the maximum working process memory are removed from the working process properties.</p><p>However, the removed parameters will be saved in the cluster settings and used in a previous version of 1C:Enterprise.</p><p>If you create a new cluster, some parameters will have the following default values:</p><ul><li>Force close corrupted processes – enabled.</li><li>Close corrupted processes in 60 seconds.</li></ul><p>Upon creating a new working server, 256 connections per process will be established by default.</p><p>If the removed parameters are changed in the cluster settings, it is recommended that you review the cluster settings and adjust them if necessary.</p><p>Implemented the following objects:</p><ul><li><span class="term">AdministrationCluster.WriteDumpWhenTerminatingByMemoryLimit</span> property.</li><li><span class="term">TemporaryAllowedProcessesTotalMemory </span>property for <span class="term">CriticalProcessesTotalMemory </span>object, and <span class="term">TemporaryAllowedProcessesTotalMemoryExcessTimeLimit </span>property for the <span class="term">AdministrationWorkServer </span>object.</li><li><span class="term">IClusterInfo.KillByMemoryWithDump </span>property.</li><li><span class="term">CriticalProcessesTotalMemory</span>, <span class="term">TemporaryAllowedProcessesTotalMemory</span>, and <span class="term">TemporaryAllowedProcessesTotalMemoryTimeLimit </span>properties for the <span class="term">IWorkingServerInfo </span>object.</li></ul><p>The following Java-based tools are implemented in the administration server interface:</p><ul><li><span class="term">IsClusterRecyclingKillByMemoryWithDump()</span> and <span class="term">setClusterRecyclingKillByMemoryWithDump()</span> methods of the <span class="term">IClusterInfo </span>interface.</li><li><span class="term">GetCriticalProcessesTotalMemory()</span>, <span class="term">setCriticalProcessesTotalMemory()</span>, <span class="term">getTemporaryAllowedProcessesTotalMemory()</span>, <span class="term">setTemporaryAllowedProcessesTotalMemory()</span>, <span class="term">getTemporaryAllowedProcessesTotalMemoryTimeLimit()</span>, and <span class="term">setTemporaryAllowedProcessesTotalMemoryTimeLimit()</span> methods of the <span class="term">IWorkingServerInfo </span>interface.</li></ul><p>For the cluster service command-line utility (<span class="interface">rac</span>):</p><ul><li>Implemented the <span class="term">kill-by-memory-with-dump</span> field for the <span class="term">cluster info</span> command output.</li><li>Implemented the <span class="term">kill-by-memory-with-dump</span> parameter for the following commands: <span class="term">cluster update</span> and <span class="term">cluster insert</span>.</li><li>Implemented the following command-line parameters for <span class="term">server insert</span> and <span class="term">server update</span> commands: <span class="term">critical-total-memory</span>, <span class="term">temporary-allowed-total-memory</span>, and <span class="term">temporary-allowed-total-memory-time-limit</span>.</li></ul><p>The following properties are deprecated and supported for compatibility and interaction with previous cluster versions:</p><ul><li><span class="term">ProcessMemoryLimit</span>, <span class="term">MaxMemoryTimeLimit</span>, and <span class="term">ProcessErrorCountLimit </span>properties of the <span class="term">AdministrationCluster </span>object.</li><li><span class="term">MaxMemorySize</span>, <span class="term">MaxMemoryTimeLimit</span>, and <span class="term">ErrorsCountThreshold </span>properties of the <span class="term">IClusterInfo </span>object.
</li></ul></td><td>Server cluster monitoring logic was different. Only working process parameters were used when determining the amount of used RAM. Maximum 128 connections per process were offered by default.</td><td>Optimized use of RAM by a server cluster.</td></tr><tr title="Версия 8.3.15" class="tag_6"><td><a name="18920440-260e-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Upgrade: load balancing upon creating a new connection to the server cluster is updated. Upgrade: the algorithm to assess working process performance is updated.</td><td>Load balancing mechanism did not process some situations well enough. In particular, there was non-optimal working process load and load redistribution took a long time.</td><td>New connections will use available resources more evenly. Load redistribution among server clusters will be faster. Improved load balancing upon mass connections and disconnections of users to/from the server cluster.</td></tr><tr title="Версия 8.3.15" class="tag_68"><td><a name="47df4777-2610-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>The version difference form contains information on moved rows in object tabular sections. A row number before and after movement is shown.
After calling the <span class="term">GetVersionDifference()</span> method, the following information will be available for the moved row:<ul><li>Property <span class="term">LineNumberAfterVersionChange </span>is a new row number (after movement).</li><li>Property <span class="term">LineNumberBeforeVersionChange </span>is an old row number (before movement).</li></ul></td><td>In the version difference form, the row number after change was adjusted considering actions performed between the first movement and the second movement, and the row number before change contained the row number in the version after change.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_68"><td><a name="0f6d3df1-2618-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>Upon using data history, now you can perform actions once a data version is written. New object manager module event (for objects that support data history): <span class="term">AfterWriteDataHistoryVersionsProcessing</span>. New property available for objects that support data history: <span class="term">WriteDataHistory.AfterWriteDataHistoryProcessing</span>. Use it to manage the need to call the <span class="term">AfterWriteDataHistoryVersionsProcessing </span>event handler. Objects that require processing after writing data history are stored in a special queue. New method available for deleting objects from this queue: <span class="term">DataHistory.DeleteFromAfterWriteVersionsProcessing()</span>.
New configuration object property: <span class="term">ExecuteAfterWriteDataHistoryVersionProcessing</span>.
Now you can update data history once an object is written. History will be updated by a background job once an object write transaction is complete. New property: <span class="term">WriteDataHistory.UpdateHistoryImmediatelyAfterWrite</span>.
New configuration object property: <span class="term">UpdateDataHistoryImmediatelyAfterWrite</span>.
New data history manager method: <span class="term">ExecuteAfterWriteVersionsProcessing()</span>.
Now you can add new fields and tabular sections to a data history record. Tabular sections can be added only to those objects where metadata has tabular sections. New property: <span class="term">WriteDataHistory.AdditionalData</span>. The <span class="term">GetMetadata()</span> method (by a data version) of the data history manager returns information considering added properties and tabular sections. New methods for the <span class="term">WriteDataHistory </span>object: <span class="term">AddAdditionalData()</span> and <span class="term">AddAdditionalDataFieldPresentation()</span>.
Now you can cancel a data history record. New property: <span class="term">WriteDataHistoryParameters.Cancel</span>.
Implemented the <span class="term">WriteDataHistory.VersionComment</span> property for a version comment record.
The following methods of objects that support data history are deprecated and supported for compatibility purposes only: <span class="term">SetDataHistoryVersionComment()</span> and <span class="term">GetDataHistoryVersionComment()</span>.
New parameters available for the <span class="term">UpdateHistory()</span> method (in all syntax options) of the data history manager: <span class="term">ExecuteAfterWriteVersionsProcessing </span>and <span class="term">AutoDeleteFromAfterWriteVersionsProcessing</span>.
Implemented manager module for constants.
New system background jobs for processing after recording versions and for updating data history after recording.</td><td>These features were not provided.</td><td>Extended data history features.</td></tr><tr title="Версия 8.3.15" class="compat tag_45 tag_25 tag_1"><td><a name="c1b85aa2-464b-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If the LIKE operation is used in the query language (also upon calculating a function in the TOTALS sentence) or the data composition system expression language in the infobase file mode, a special character specified inside the brackets using the ESCAPE keyword, works correctly.<p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>If the LIKE operation was used in the query language (also upon calculating a function in the TOTALS sentence) or the data composition system expression language in the infobase file mode, a special character specified using the ESCAPE keyword did not function inside the brackets.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_119"><td><a name="63c5cd8b-4661-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 119); return false;">File infobase Queries</a>.<br></td><td>In the file infobase, an addition operation and a subtraction operation of the query language are changed. Upon calculating length and precision of an operation type, preference is given to length rather than precision if the total length of 38 characters is exceeded.<p>Therefore, if two numeric fields, the first of which has 20 characters and 0 precision and the second of which has 30 characters and 20 precision, are added together or subtracted, the resulting length will be 38 and the precision will be 18. If the second field contains a number with the last precision digits, the number will be cut by precision digits.</p><p>Example:</p><ul><li>If you add 1,000,000,000,000,000,000 and 0.00000000000000000001, you get 1,000,000,000,000,000,000.</li><li>If you add 1 and 0.00000000000000000001, you get 1.</li><li>If you subtract 0.99999999999999999999 from 2,000,000,000,000,000,000, you get 1,999,999,999,999,999,999.</li></ul><p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>Upon calculating length and precision of an operation type, preference was given to precision rather than length if the total length of 38 characters was exceeded.<p>Therefore, if two numeric fields, the first of which had 20 characters and 0 precision and the second of which had 30 characters and 20 precision, were added together or subtracted, the resulting length would be 38 and the precision would be 20. Because of that, if the first number contained 20 characters in the integral part, a digit overflow error occurred as a result. This would be expressed by a number containing 9 in all parts.</p><p>Example:</p><ul><li>If you add 1,000,000,000,000,000,000 and 0.00000000000000000001, you get 999,999,999,999,999,999.99999999999999999999.</li><li>If you add 1 and 0.00000000000000000001, you get 1.00000000000000000001.</li><li>If you subtract 0.99999999999999999999 from 2,000,000,000,000,000,000 you get 999,999,999,999,999,999.99999999999999999999.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_4"><td><a name="23322ce0-4953-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: now you can register (and unregister) an infobase in the collaboration system on 1C:Enterprise server.<p>New methods for the collaboration system manager: <span class="term">ExecuteInfoBaseRegistration</span><span class="term">()</span> and <span class="term">CancelInfoBaseRegistration()</span>.</p></td><td>Earlier, you could register and unregister an infobase in the collaboration system on 1C:Enterprise client only.</td><td>Extended administrative actions in the collaboration system.</td></tr><tr title="Версия 8.3.15" class="compat tag_115 tag_25 tag_1"><td><a name="232b1c12-4968-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Upon opening conditional appearance settings (saved in previous platform versions) with disabled compatibility mode, the following conditional appearance parameters of a form or a report will be set to default values:<ul><li>Conditional appearance items of a form (the <span class="term">DataCompositionParameterValue </span>object): <span class="term">Line</span>, <span class="term">Color</span>, and <span class="term">Font</span>.</li><li>Conditional appearance items of a report (the <span class="term">DataCompositionAppearance </span>object collection): <span class="term">Line</span>, <span class="term">Color</span>, <span class="term">Font</span>, <span class="term">VerticalAlign</span>, <span class="term">HorizontalAlign</span>, <span class="term">Placement</span>, <span class="term">TextPositionRelativeToPicture</span>, and <span class="term">PictureSize</span>.</li></ul><p>Changes are applied if values of these conditional appearance parameters are specified as a string and not values of a particular type.</p><p>We recommend that you analyze where the above mentioned conditional appearance parameters are used and eliminate places where the parameters are set as a string.</p><p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>For some form or report conditional appearance parameters (the <span class="term">DataCompositionAppearance </span>object collection), you could specify values (the <span class="term">DataCompositionParameterValue </span>object) not only as values of particular types but also as a string. These parameters were the following:<ul><li>Conditional appearance items of a form: <span class="term">Line</span>, <span class="term">Color</span>, and <span class="term">Font</span>.</li><li>Conditional appearance items of a report: <span class="term">Line</span>, <span class="term">Color</span>, <span class="term">Font</span>, <span class="term">VerticalAlign</span>, <span class="term">HorizontalAlign</span>, <span class="term">Placement</span>, <span class="term">TextPositionRelativeToPicture</span>, and <span class="term">PictureSize</span>.</li></ul><p>You could see the following behavior:</p><ul><li>In conditional appearance of reports and upon reading parameter values from XML, a string was converted to a value matching the parameter type. Parameters were used with the values resulted from the conversion.</li><li>In conditional appearance of dynamic lists, a string was not converted to a value. Default parameter values were used.</li><li>In conditional appearance of forms (in thin client), a string was converted to a value. Parameters were used with the values resulted from the conversion.</li><li>In conditional appearance of forms (in thin client), a string was not converted to a value. Default parameter values were used. In version 8.3.14, an error occurred in that case.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_25 tag_1"><td><a name="bd2a685c-55f1-11e9-84bd-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Upon calculating values of the data composition system fields listed below, the principle is applied: a if value of the resource, from which this field is received, is equal to 0 in the current grouping, the field value is also 0. These fields are the following:<ul><li>% total</li><li>% in grouping</li><li>% in hierarchy group</li><li>% in row or series</li><li>% in column or point</li><li>% in row or series grouping</li><li>% in column or point grouping</li><li>% in row or series group</li><li>% in column or point hierarchy group</li></ul><p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>Upon calculating values of the following data composition system fields:<ul><li>% total</li><li>% in grouping</li><li>% in hierarchy group</li><li>% in row or series</li><li>% in column or point</li><li>% in row or series grouping</li><li>% in column or point grouping</li><li>% in row or series group</li><li>% in column or point hierarchy group</li></ul><p>you could see the following behavior: values were always divided by a parent grouping value or grand total, except for cases when the resource value in the grouping was equal to NULL. As a result, an exception could be thrown due to division by 0.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_63 tag_1"><td><a name="9d59279c-55f2-11e9-84bd-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Upon assigning a new value to the <span class="term">Chart.DataSource</span> property, first, the existing points and series are deleted, and then the new ones are created according to the new data source. After a new value is assigned, the current selection is cleared.<p>We recommend that you remember the current selection before setting new data and restore it if necessary.</p><p>This change is not implemented in version 8.3.14 compatibility mode.</p></td><td>Upon assigning a new value to the <span class="term">Chart.DataSource</span> property, the existing points and series were not deleted and the selection was not cleared.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cb9-14ce-11e9-a3f7-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.15" class="tag_31 tag_20"><td><a name="8f520f98-18ba-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the form editor preview panel, rounded screen corners and displays with a cutout are supported now (for mobile devices on iOS).
iPhone models X/XS/XS Max/XR are added to the list of devices for preview in the form editor.</td><td>This feature was not provided.</td><td>Designing forms for the latest iPhone devices is easier now.</td></tr><tr title="Версия 8.3.15" class="tag_48 tag_31 tag_30"><td><a name="c3faa5cf-1f19-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>Now you can put a stamp on a photo indicating a photo date and time, as well as a custom text.
New object: <span class="term">PhotoStamp</span>.
Implemented the <span class="term">Stamp </span>parameter of the <span class="term">MultimediaTools.MakePhoto()</span> method. </td><td>This feature was not provided.</td><td>Expanded photo management capabilities.</td></tr><tr title="Версия 8.3.15" class="tag_48 tag_30 tag_31"><td><a name="28fff42a-1f1c-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>For mobile applications on Android, the sound is recorded in MPEG4 using AAC codec.
For mobile applications on any mobile operating system, the sound is recorded in stereo, the bitrate is 128 kbps, and the sample rate is 44 kHz.
The <span class="term">MultimediaTools.MakeAudioRecording()</span> method returns the <span class="term">MultimediaData </span>object where the file extension is set to <span class="interface">m4a </span>and the MIME type is set to <span class="interface">audio/mp4</span>.</td><td>The sound quality and the <span class="term">MultimediaTools.MakeAudioRecording()</span> method result depended on the used operating system:
<ul><li>Android: 3gp and mono; the sample rate was 8 kHz. <span class="interface">3gp </span>extension and <span class="interface">audio/3gp</span> MIME type.</li><li>iOS: m4a and stereo; the sample rate was 44 kHz. m4a extension and <span class="interface">audio/mp4</span> MIME type.</li><li>Windows: m4a and mono; the sound quality was selected automatically. <span class="interface">aac </span>extension and <span class="interface">audio/aac</span> MIME type.</li></ul></td><td>Unified audio information recording result on different mobile operating systems.
You can listen to a sound recording made in 1C:Enterprise mobile platform using standard tools of operating systems on personal computers.</td></tr><tr title="Версия 8.3.15" class="tag_120 tag_31"><td><a name="a4d5a3d2-1f1c-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Now you can use the scheduled job dialog on the mobile client. New object available on the mobile client: <span class="term">ScheduledJobDialog</span>. </td><td>Editing a schedule for a scheduled job was not available on mobile client.</td><td>Now you can edit a schedule for a scheduled job on mobile client.</td></tr><tr title="Версия 8.3.15" class="tag_31 tag_32"><td><a name="ca7e6b90-507b-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>In mobile client, you can add an infobase to the list by scanning a QR code. This feature is available if the mobile client application is permitted to add an infobase with a custom address.<p>This feature is also available in mobile version for developers.</p><p>In mobile application builder, you can allow users to add infobases using QR codes.</p><p>In addresses related to schema <span class="term">e1c://</span>, you can use the following commands:</p><ul><li><span class="term">/AddByQRCode</span> to start QR code scanning.</li><li><span class="term">/AddInfoBase</span> to add the infobase to the infobase list of the client application.</li></ul></td><td>This feature was not provided.</td><td>Advanced features for adding infobases to the list in mobile client or mobile platform. Simplified procedure of adding infobases.</td></tr></table><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cba-14ce-11e9-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.15" class="tag_0"><a name="93c097a4-1a54-11ea-8371-0050569f678a"></a>The libxml library is updated to version 2.9.10.</li><li title="Версия 8.3.15" class="tag_0"><a name="ab551855-1a54-11ea-8371-0050569f678a"></a>The libxslt library is updated to version 1.1.34.</li><li title="Версия 8.3.15" class="tag_0"><a name="6aacb755-222c-11ea-8371-0050569f678a"></a>The libpng library is updated to version 1.6.37.</li><li title="Версия 8.3.15" class="tag_0"><a name="894b6dcc-222c-11ea-8371-0050569f678a"></a>The libtiff library is updated to version 4.1.0.</li><li title="Версия 8.3.15" class="tag_0"><a name="a6a667ab-222c-11ea-8371-0050569f678a"></a>The sqlite library is updated to version 3.30.1.</li><li title="Версия 8.3.15" class="tag_0"><a name="4b4e6b10-5c76-11ea-8371-0050569f678a"></a>The curl library is updated to version 7.67.0.
</li></ul><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cbb-14ce-11e9-a3f7-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.15" class="tag_0"><a name="083e3c90-546c-11e9-84bd-0050569f678a"></a>In the form of the stored files list, you can see an example on how to use new file operation methods.</li><li title="Версия 8.3.15" class="tag_0"><a name="6096498d-546c-11e9-84bd-0050569f678a"></a>The check box is displayed as a switch in the <span class="term">MobileDeviceSettings </span>common form and in the main form of the <span class="term">SalesAggregateManagement </span>data processor.<p>
</p></li><li title="Версия 8.3.15" class="tag_0"><a name="df959aa7-546c-11e9-84bd-0050569f678a"></a>Implemented the form for selecting collaboration system users (the <span class="term">FormCollaborationSystemUserSelection </span>common form) to demonstrate processing of collaboration system user selection.</li><li title="Версия 8.3.15" class="tag_0"><a name="52d1bb70-546d-11e9-84bd-0050569f678a"></a>Implemented a global search demo example. The example is implemented in the application module and in common modules <span class="term">GlobalSearchClient </span>and <span class="term">GlobalSearchServer</span>.</li><li title="Версия 8.3.15" class="tag_0"><a name="04d338d5-5472-11e9-84bd-0050569f678a"></a>New features for spreadsheet document headers and footers available in the <span class="term">HeaderFooter </span>extension, which is delivered together with the demo configuration.<p>
</p></li><li title="Версия 8.3.15" class="tag_0"><a name="8e518470-f57a-11e9-8371-0050569f678a"></a>Examples of using donut charts are implemented in the Charts demo configuration. You can download the demo configuration from the ITS disk <a href="https://its.1c.ru/db/metod8dev#content:5952:hdoc" target="_blank">Read more</a>., or explore it directly on the demo configurations website <a href="http://demo-ma.1c.ru" target="_blank">Read more</a>..</li></ul><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cbc-14ce-11e9-a3f7-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.15" class="tag_7"><td><a name="cb99b094-85d9-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br></td><td>Initial population of a database copy is faster now if source data includes documents generating records in registers and containing a large number of rows in tabular sections.</td><td>Initial population of a database copy took more time if source data included documents generating records in registers and containing a large number of rows in tabular sections.</td><td>Upgrade: faster initial population of a database copy.</td></tr><tr title="Версия 8.3.15" class="tag_4"><td><a name="006f7994-85e8-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>On overriding the selection list of collaboration system users, on creating a context conversation message, the need to disable a user notification (displayed in the user interface as <span class="interface">No notification</span>) is passed as a special value of the <span class="term">ChoiceData </span>parameter of the <span class="term">CollaborationSystemUserAutoComplete </span>data processor.<p>A special value can be created using the constructor of the <span class="term">CollaborationSystemUserID </span>object without specifying a collaboration system user ID.</p><p>The <span class="term">Undefined </span>value is no longer allowed as a value of the <span class="term">ChoiceData </span>parameter of the <span class="term">CollaborationSystemUserID </span>data processor.</p></td><td>On overriding the list of selecting collaboration system users, on creating a context conversation message, the need to disable a user notification (displayed in the user interface as <span class="interface">No notification</span>) was passed as the <span class="term">Undefined </span>value, which prevented distinguishing notification disable and closing the user selection form without any choice.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_52"><td><a name="4ba88ef4-85ee-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>In client/server mode, a pessimistic object lock will be unconditionally released by the server cluster if the following conditions are met:<ul><li>There is an attempt to release an object lock set by another user (in a remote client application).</li><li>The collaboration system is used to release the lock.</li><li>The remote client application did not release the lock 5 seconds after sending the collaboration system message.</li></ul></td><td>In client/server mode, an attempt to release a pessimistic object lock resulted in the message stating that editing was not possible if the following conditions were met:<ul><li>There was an attempt to release an object lock set by another user (in a remote client application).</li><li>The collaboration system was used to release the lock.</li><li>The remote client application did not release the lock 5 seconds after sending the collaboration system message.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_6"><td><a name="72540962-981b-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved failover cluster reliability.</td><td>Failover cluster was unreliable.</td><td>Improved failover cluster reliability.</td></tr><tr title="Версия 8.3.15" class="tag_31 tag_30 tag_32"><td><a name="9f150ac2-9835-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>1C:Enterprise mobile platform running Android now supports 64-bit processors.Mobile application builder creates 4 versions of application that targets Android upon building:<ul><li>32-bit x86 application</li><li>32-bit ARM application</li><li>64-bit x86_64 application</li><li>64-bit ARM64 application.</li></ul><p>
</p><p>You can now publish 64-bit applications in Google Play.</p><p>Changed files in the following mobile version distribution archive: <span class="interface">mobile.zip</span>.
</p></td><td>Mobile platform 1C:Enterprise running Android supported 32-bit processors only. Mobile application builder could not build and publish 64-bit mobile application versions in Google Play.</td><td>Expanded list of supported processor architectures for a mobile version running Android.<p>Built mobile applications running Android are larger now. Built mobile applications running Android now perform faster.</p></td></tr><tr title="Версия 8.3.15" class="tag_30 tag_31 tag_32"><td><a name="9be81602-9838-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Some single mobile application permissions were replaced by multiple permissions in order to meet requirements of application store owners.<p>
</p><p>The Telephony permission is replaced with:
Dialing
Read the phone log
Call handling
Automatically send text messages
Get text messages
Text message log.
The Media permission is replaced with:
Camera
Microphone
Music library
Picture and video library
Audio and video playback.
New permissions are grouped by purpose and functional cohesion.</p><p>Configurations exported by version 8.3.14 or earlier versions cannot be built using mobile version 8.3.15 or higher. The reverse is also true.</p></td><td>Mobile application permissions had a different composition.</td><td>Mobile application permissions include changed requirements of application store owners.</td></tr><tr title="Версия 8.3.15" class="tag_30 tag_31 tag_32"><td><a name="efe3f982-9839-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>In Designer, you can now edit request bodies of permissions that are required by the mobile application. Request bodies of permissions that have an applied meaning for the user are editable.<p>Mobile application builder allows you to build mobile applications that contain both configurations with the specified permission request bodies and configurations without them (exported in previous 1C:Enterprise platform versions).</p></td><td>Permission request bodies were not editable in Designer.</td><td>You can now specify permission request bodies that meet the mobile application requirements as accurately as possible.</td></tr><tr title="Версия 8.3.15" class="tag_30 tag_31 tag_54"><td><a name="245e0a28-98e3-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 54); return false;">Global search</a>.<br></td><td>Upgrade: global search is now available in 1C:Enterprise mobile version.</td><td>This feature was not supported in the mobile version.</td><td>Upgrade: 1C:Enterprise mobile version now has the features that were implemented earlier in 1C:Enterprise version for a personal computer.</td></tr><tr title="Версия 8.3.15" class="tag_20"><td><a name="f3d53618-9bf1-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Implemented the following changes in Syntax Assistant:<ul><li>Deprecated objects (properties, functions, procedures, etc.) are not deleted from Syntax Assistant but saved to it.</li><li>Accessibility of deprecated objects (objects that are not yet available or not recommended for use in the current compatibility mode) in Syntax Assistant tree can be managed using the check box in Syntax Assistant settings:<span class="interface"> Display </span><span class="interface">deprecated </span><span class="interface">objects</span>.</li><li>Upgrade: an addition version, a depreciation version, and a version where significant information about an object was last edited can be displayed.</li><li>For deprecated objects, objects recommended for usage instead of the deprecated object can be displayed now.</li><li>The syntax assistant font is the default font of the WebKit library used to display HTML documents.</li><li>For Syntax Assistant content window, the width limit is 1,000 pixels.</li><li>Decreased indents before and after bulleted lists.</li></ul><p>
</p><p>Regardless of the state of the <span class="interface">Display deprecated objects</span> setting check box, search using Ctrl+F1 always results in information about a Syntax Assistant object being displayed.</p><p>Addition version information is filled in for all objects of Syntax Assistant. Deletion version information is filled in for all objects of Syntax Assistant. Objects recommended for replacement are filled in only if the object was declared deprecated in version 8.3.14 and above.</p><p>Specified changes in Syntax Assistant are valid starting from version 8.3.15 and above.</p></td><td>Syntax Assistant did not have any information about object versions (of addition, depreciation, or change) and objects that are recommended for usage instead of the deprecated ones. Deprecated objects were deleted from Syntax Assistant. It was impossible to access such objects.</td><td>Syntax Assistant became more informative and useful for developers.</td></tr><tr title="Версия 8.3.15" class="tag_30 tag_31 tag_48"><td><a name="40ad5a18-9bf4-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>You can now use additional authentication to access mobile application features. Authentication is done by the used mobile operating system and includes authentication using biometrics (a fingerprint, face recognition, or iris recognition) or a password (pattern lock and so on). New global context property: <span class="term">AdditionalUserValidation</span>.<p>Upgrade: safe storage of confidential information on a user mobile device. Information is protected by the mobile operating system. You can now manage the need for additional authentication to access confidential information. New global context property: <span class="term">SecureStore</span>.</p></td><td>These features were not provided.</td><td>Added functionality of 1C:Enterprise mobile version for additional user authentication and confidential information storage.</td></tr><tr title="Версия 8.3.15" class="tag_31"><td><a name="9a29af8a-cf28-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Biometric authentication for simplified login to the application is now available in the mobile client.<p><span class="interface">Use biometrics</span> check box should be enabled on the mobile devices that support biometric authentication, in the mobile client infobase properties, and in the dialog boxes for entering the username and password generated by the mobile client.</p></td><td>This feature was not provided.</td><td>Authentication to an application on devices that support biometric authentication can now be simplified.</td></tr><tr title="Версия 8.3.15" class="tag_70"><td><a name="94bc4686-bcde-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>Windows client application installer now supports Vietnamese language.</td><td>The Windows client application installer did not support Vietnamese.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_68"><td><a name="24577b06-bce1-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>Implemented the following features for standard <span class="interface">Data h</span><span class="interface">istory processor</span>:<ul><li>Starting object queue data processor after writing versions.</li><li>Removing objects from the object data processor queue after writing versions.</li></ul><p>
These features are available from the data processor form using the <span class="interface">More - Data history management command.</span></p></td><td>These features were not provided.</td><td>The standard data processor supports new features of the data history component previously implemented in the platform.</td></tr><tr title="Версия 8.3.15" class="tag_4 tag_59"><td><a name="b458aa26-bce2-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br></td><td>When calling the <span class="term">BeginGetConversation()</span> form method, a context conversation is created if the resulting context conversation is missing by the time the method is called.</td><td>When calling the <span class="term">BeginGetConversation()</span> form method, the context conversation was not created.</td><td>When calling the <span class="term">BeginGetConversation()</span> form method, a context conversation is automatically created if it was not created before..</td></tr><tr title="Версия 8.3.15" class="tag_33"><td><a name="517b7d17-bceb-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>The documents state that 1C:Enterprise can operate with clusters that are created using PostgreSQL DBMS versions listed in the system requirements for the platform.</td><td>The list of PostgreSQL DBMS versions using which a cluster is created to operate with 1C:Enterprise was specified incorrectly.</td><td>Fixed the error in the documents.</td></tr><tr title="Версия 8.3.15" class="tag_6"><td><a name="9c9d2537-bcf2-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Optimized the final step of load balancing algorithm (in the selection mode with a performance priority) when the workflows selected in the previous steps differ in available performance.</td><td>The documents did not contain information on configuring web servers for the correct operation of the background jobs feature in the file infobase.</td><td>Optimized load balancing algorithm in a server cluster.</td></tr><tr title="Версия 8.3.15" class="tag_81"><td><a name="2ef99357-bcfd-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>The documents contain information on configuring web servers for the correct background jobs feature operation in the file infobase.</td><td>The documents did not contain information on configuring web servers for the correct operation of the background jobs feature in the file infobase.</td><td>Updated platform documents.</td></tr><tr title="Версия 8.3.15" class="tag_78"><td><a name="8dee7630-bda7-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>When using the <span class="term">BeginPutFile</span><span class="term">()</span>/<span class="term">BeginPuttingFiles</span><span class="term">()</span> methods, the downloaded file(s) are split into parts and the transfer to the server is performed in parts. As a result, the user interface remains operational.<p>Also implemented the option to start putting new files, even if the previously started putting of files is not yet complete.</p></td><td>When using the <span class="term">BeginPutFile()</span>/<span class="term">BeginPuttingFiles()</span> methods, the uploaded file/files were transferred fully. The client application did not respond to user actions during the transfer.<p>It was impossible to start putting a new file until the previously started putting of one or more files was completed.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="compat tag_121 tag_23 tag_1"><td><a name="5dfe5038-c26e-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 121); return false;">Calculation registers</a>.<br><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Implemented the feature to include sequences and recalculations in the common attributes.<p>This change is not implemented in version 8.3.14 compatibility mode.
</p></td><td>This feature was not provided.</td><td>Expanded the structure of configuration objects, which may be part of common attributes.</td></tr><tr title="Версия 8.3.15" class="tag_116"><td><a name="d77d9e1a-cd60-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>Starting the client application and Designer on PCs running on Linux or macOS when using basic configurations has been accelerated for cases, when the PC has a large number of disk partitions or processor cores.<p>The list of key hardware parameters used when activating the base software license on Linux and macOS is aligned with the list of key parameters in Windows.</p></td><td>Starting the client application and Designer on PCs running Linux and macOS when using basic configurations when the PC had a large number of disk partitions or processor cores took a long time.<p>The list of key hardware parameters used when activating the base software license on Linux and macOS was different from the list of key parameters in Windows.</p></td><td>Starting the client application and Designer when using the basic configuration in Linux and macOS has been accelerated.</td></tr><tr title="Версия 8.3.15" class="tag_31"><td><a name="c715a6da-cd6a-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The <span class="term">TextDocument </span>object is now available in mobile client.</td><td>The <span class="term">TextDocument </span>object was not available in mobile client.</td><td>Added new mobile client features.</td></tr><tr title="Версия 8.3.15" class="tag_6"><td><a name="05631cdc-e4ee-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The <span class="interface">Critical amount of process memory</span>, <span class="interface">Temporarily allowed amount of process memory</span>, and <span class="interface">Period of exceeding the process memory threshold</span> parameters can be changed with a PROF license.<p>However, these parameters only affect the restart of processes. The effect of these parameters on the server calls interruption is only supported for CORP licenses.</p><p>If the server is running with a PROF license, the limit memory size, after which the client’s server call is interrupted, is defined as 80% of the physical memory of the computer, regardless of the <span class="interface">Temporarily allowed amount of process memory</span> parameter value.</p></td><td>The <span class="interface">Critical amount of process memory</span>, <span class="interface">Temporarily allowed amount of process memory</span>, and <span class="interface">Period of exceeding the process memory threshold</span> parameters could only be changed with a CORP license.</td><td>Restarting the working processes depending on the amount of RAM used is now possible for a server cluster running PROF license.</td></tr><tr title="Версия 8.3.15" class="tag_59 tag_96"><td><a name="66d07ba8-ea66-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td><span class="interface">Alt+L</span> shortcut is now used for the <span class="interface">Search everywhere</span> command of the form elements context menu.</td><td><span class="interface">Ctrl+Shift+C</span> shortcut was used for the <span class="interface">Search everywhere</span> command of the form elements context menu.</td><td>Fixed the conflict between the platform feature keyboard shortcut and the established keyboard shortcuts of typical applications.</td></tr><tr title="Версия 8.3.15" class="tag_96"><td><a name="0854a28a-eb30-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The form menu is added in the <span class="interface">Taxi </span>interface. It is called by the three dots button, located in the top right section of the form (except for the dialog boxes generated by the <span class="term">Question()</span>, <span class="term">ShowQuestion()</span>, <span class="term">Warning()</span> and <span class="term">ShowWarning()</span> methods). The home page displays a single form menu. The form menu items depend on the current (active) form element:<ul><li>The <span class="interface">File </span>menu is available if save and print commands are available for the current element.</li><li>Search commands are displayed if search or replace is supported for the current element. Search commands will not be displayed if the current form element is a table that displays a dynamic list or form data collection.</li><li>Clipboard commands are displayed if the current element supports the clipboard.</li><li>If the current element supports cancel and return commands, these commands are available in the form menu.</li><li>The command for displaying properties is available when viewing the properties of the current element is available.</li><li>The special paste command is displayed if special pasting is available (in thin and thick client applications only).</li><li>The command to configure the form navigation panel is displayed only if this feature is available.</li><li>The <span class="interface">Messages </span>command is displayed if messages were displayed in the form.</li><li>Commands for merging and docking windows are not displayed in the form menu if the form is displayed in an auxiliary window.</li></ul><p>
The following changes have been made to the <span class="interface">Service and Settings</span> menu:</p><ul><li>The window merging and docking commands have been removed from the <span class="interface">Windows </span>menu.</li><li>The commands for displaying the message window and settings of the form navigation panel have been removed from the <span class="interface">Settings </span>menu.</li><li>The save, print (and print settings) commands only affect the current (active) element of the current client application form.</li></ul><p>
Clipboard commands for numbers (put in the clipboard, add to/subtract from the clipboard) can be displayed in the main application window or in the auxiliary application window title. To enable/disable these commands, use the <span class="interface">Show, </span><span class="interface">M</span>, <span class="interface">M</span><span class="interface">+</span>, <span class="interface">M-</span> command in the <span class="interface">Service and Settings</span> menu.</p><p><span class="interface">Alt+F</span> keyboard shortcut opens the advanced search dialog box in the form table that displays a dynamic list.
</p></td><td>There was no form menu. Form menu commands were located in the <span class="interface">Service and Settings</span> menu.</td><td>Improved navigation in the application.</td></tr><tr title="Версия 8.3.15" class="tag_21"><td><a name="86a0162b-e437-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Fixed the problem of searching for words ending in "*" using full-text search.<p>If the platform can detect that the current full-text search index is incorrect, it will automatically delete it.</p><p>We recommend to clear and rebuild the full-text search index when upgrading to version 8.3.15.</p></td><td>Searching words ending in "*" using full-text search was not available.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_10"><td><a name="2eb02d82-f579-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The 1C:Enterprise distribution package now includes files that enable the installer operation on Windows XP (the names of such files have the <span class="interface">_xp</span> suffix).<p>The 1C:Enterprise installers now use the UTF-8 encoding on Windows. The 1C:Enterprise installer on Windows XP use the ANSI encoding.</p><p>The 1C:Enterprise installer on Windows XP does not support Vietnamese language.</p><p>Provided that Windows XP is not used, we recommend to exclude the files of distribution package for Windows XP when updating the 1C:Enterprise through web server.</p></td><td>The 1C:Enterprise installer could display some national symbols incorrectly on Windows XP.</td><td>There is now a separate distribution package for obsolete Windows XP.</td></tr><tr title="Версия 8.3.15" class="tag_26"><td><a name="e40eaeaf-f960-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Search control commands are now available in the <span class="interface">More </span>menu of the report form and the spreadsheet document form.<p>Commands for working with table and editing commands are no longer available in the <span class="interface">More </span>menu of a spreadsheet document.
</p></td><td>Search control commands were only available in the report form and spreadsheet document menu.<p>Commands for working with table and editing commands were available in the <span class="interface">More </span>menu of a spreadsheet document form. The same commands were available in the form menu.</p></td><td>The distribution of commands between the form menu and the <span class="interface">More </span>menu in the report and spreadsheet document forms has become more logical and understandable.</td></tr><tr title="Версия 8.3.15" class="tag_96"><td><a name="1a00f483-f962-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>Save and print settings commands are no longer available in the <span class="interface">Service and Settings - File </span>menu.</td><td>Save and print settings commands were available in the <span class="interface">Service and Settings - File </span>menu.</td><td>Removed duplication of commands in various application menus.</td></tr><tr title="Версия 8.3.15" class="tag_96"><td><a name="bd6378b8-10e3-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td><span class="interface">Zoom </span>command was moved to the form menu.</td><td><span class="interface">Zoom</span> command was available in <span class="interface">Service and Settings </span>menu.</td><td>The form context command is now available in the form directly.</td></tr><tr title="Версия 8.3.15" class="tag_10"><td><a name="530534f0-222e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The system integrity control utility is implemented by making calculating the hash function of files through the SHA-256 and GOST R 31.11-2012 (512 bit) algorithms possible.<p>In the <span class="term">m</span><span class="term">ake </span>utility's operating mode the <span class="term">--method </span>parameter is implemented. Now you can specify the algorithm used in the hash function calculation.</p><p>
</p><p>
</p></td><td>To calculate the hash function of the files, the system integrity control utility was using the SHA-1 algorithm.</td><td>Now you can use stronger algorithms to calculate the hash functions.</td></tr><tr title="Версия 8.3.15" class="tag_68"><td><a name="5a4f4d33-35f1-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>The data history update is now performed faster (with the <span class="term">DataHistory.UpdateHistory()</span> method) in case there is a large number of versions that need to be transferred to the data history.</td><td>The data history update (with the <span class="term">DataHistory.UpdateHistory()</span> method) took a very long time in case there is a large number of versions in the system that need to be transferred to the data history.
</td><td>Data history update is improved. The data history can be updated in the background.</td></tr><tr title="Версия 8.3.15" class="tag_21"><td><a name="b134118f-3760-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Reduced the time of the full-text search index generation. Reduced disk space requirements of the full-text search index.
If you enter a search string consisting of one or two chars and the "*" substitution char (any sequence of chars), an error may occur with the suggestion to refine the search string (if the search result is large).
</td><td>Full-text search index generation took more time. The index required more disk space.
If you entered a search string consisting of one or two chars and the "*" substitution char (any sequence of chars), an error with the suggestion to refine the search string (if the search result is large) did not occurr.
</td><td>The full-text search index generation is now faster. Reduced disk space requirements of the full-text search index.
</td></tr><tr title="Версия 8.3.15" class="tag_73"><td><a name="df8ac2dd-4746-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>Restructuring of the database table will not be performed if all the following conditions are met:<ul><li>The optimized mechanism of restructuring (mode v2) is used.</li><li>Microsoft SQL Server DBMS is used.</li><li>The object has subordinate objects (attributes, dimensions, etc.) of value storage, string of unlimited length or date type.</li><li>Such objects were included in version 8.3.7 and earlier compatibility mode.</li><li>In version 8.3.8 and later compatibility mode these objects were not restructured.</li><li>All changes in the configuration object are not applied to the attributes of the above-mentioned types.</li></ul><p>If all the above-mentioned conditions are met, the optimized restructuring mechanism will only process the actual changes (if possible) without the complete restructuring of the database table.
The non-optimized infobase restructuring mechanism performed the complete database restructuring after any changes made in the configuration object metadata.</p></td><td>The database table was restructured if all the following conditions were met simultaneously:<ul><li>The optimized mechanism of restructuring (mode v2) was used.</li><li>Microsoft SQL Server DBMS was used.</li><li>The object had subordinate objects (attributes, dimensions, etc.) of value storage, string of unlimited length or date type.</li><li>Such objects were included in version 8.3.7 and earlier compatibility mode.</li><li>In version 8.3.8 and later compatibility mode these objects were not restructured.</li><li>All changes in the configuration object were not applied to the attributes of the above-mentioned types.
</li></ul></td><td>In some cases the optimized mechanism of restructuring will update the database tables much faster than the previous one.
</td></tr><tr title="Версия 8.3.15" class="tag_17"><td><a name="f7cb78ed-6cdb-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>The description of <span class="term">CLSTR </span>event properties was updated in the documentation.</td><td>The documentation contained an obsolete <span class="term">CLSTR </span>event properties description.</td><td>Documentation was updated.</td></tr><tr title="Версия 8.3.15" class="tag_59 tag_86"><td><a name="18183ed1-6cf9-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 59); return false;">Client application form</a>.<br><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>Added the following buttons to the client application form header: <span class="interface">Save</span>, <span class="interface">Print</span>, and<span class="interface"> Print Preview</span>. These buttons and the <span class="interface">File </span>form submenu are displayed if there is at least one visible form field of the following types:<ul><li>Spreadsheet document field</li><li>Text document field</li><li>Graphical schema field</li><li>HTML document field</li><li>Formatted document field</li><li>Geographical schema field</li><li>Planner field</li></ul><p>
Save and print commands are available if there is at least one form field of one of above-mentioned types that supports these commands.</p><p>The form menu can now be called by pressing<span class="interface"> Alt + -.</span></p></td><td>The <span class="interface">Save</span>, <span class="interface">Print</span>, and <span class="interface">Print Preview </span>commands were displayed in the system command bar and in the main menu. These commands were available if the current form item or a single visible form item supported these commands and was of one of the following types:<ul><li>Spreadsheet document field</li><li>Text document field</li><li>Graphical schema field</li><li>HTML document field</li><li>Formatted document field</li><li>Geographical schema field</li><li>Planner field
</li></ul></td><td>Simplified interaction with the form items that support save and print options.</td></tr><tr title="Версия 8.3.15" class="tag_30 tag_31 tag_29"><td><a name="62ec952b-7985-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The iOs 7.x versions are no longer supported. The earliest supported iOS version is 8.0.</td><td>The iOS 7.x versions were supported.</td><td>Ended support for legacy iOS versions. Apple iPhone 4 is no longer supported.</td></tr><tr title="Версия 8.3.15" class="tag_38"><td><a name="f16fdbf9-8578-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Base configurations can now use extensions. The extension and the base configuration must be signed with the same key.<p>Added the <span class="term">/SignCfg</span> command for Designer batch mode.</p><p>Added the<span class="term"> sign-cfg </span>parameter of the <span class="term">config </span>mode for Designer agent mode.</p></td><td>Extensions were not supported by the base configurations.</td><td>Base configurations developers can now release configuration fixes using extensions.</td></tr><tr title="Версия 8.3.15" class="tag_81"><td><a name="e96f24c8-8579-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>You cannot publish the web service on Apache web server if the web server bitness does not match the Designer bitness.</td><td>During the web service publication there was no check that Apache web server bitness match the Designer bitness.</td><td>There are less unexpected errors during the publication caused by the Apache web server bitness and the Designer bitness mismatch.</td></tr><tr title="Версия 8.3.15" class="tag_10"><td><a name="bbcb8bc7-9697-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can now update your client application through a web server with the PROF license.</td><td>CORP license was required to update the client application through a web server.</td><td>Simplified the update of client applications through a web server.</td></tr><tr title="Версия 8.3.15" class="tag_6"><td><a name="0364447a-9900-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Now the cluster monitoring system analyzes both memory usage settings specified in the cluster settings and memory space occupied by every working process:<ul><li>If memory consumption exceeds 80% of the virtual address space, the working process will be terminated in normal mode.</li><li>If memory consumption exceeds 95% of the virtual address space, the working process will be terminated abnormally.</li></ul><p>
The cluster mechanisms that use data on available RAM consider changes made to the RAM size while the computer is operating. For example, if you change parameters of the virtual machine where the server cluster runs.</p></td><td>The cluster monitoring system did not analyze memory space occupied by every working process.<p>The cluster mechanisms that used data on available RAM relied on RAM data that was retrieved once upon the cluster start.</p></td><td>Improved server cluster stability if the 32-bit 1C:Enterprise server cluster runs 64-bit operating systems.</td></tr><tr title="Версия 8.3.15" class="tag_26"><td><a name="976adaba-cfd4-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Spreadsheet documents created in 1C:Enterprise v8.3.17 are supported.</td><td>Spreadsheet documents created in 1C:Enterprise v8.3.17 were not supported.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_79"><td><a name="615c239f-cfe4-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>Multipage TIFF files are supported.<p>New methods: <span class="term">Picture.FramesNumber()</span> and <span class="term">PictureToProcess.GetPictures()</span>.</p><p>New picture constructor for the <span class="term">PictureToProcess </span>object, which takes an array of pictures as the argument and the resulting picture format as the parameter. New parameters for the <span class="term">PictureToProcess </span>object: <span class="term">Frames </span>and <span class="term">Format</span>.
Implemented the <span class="term">CurrentFrameNumber </span>property and the <span class="term">FramesNumber()</span> method for the form field extension of the client application for a picture.</p></td><td>Only the first frame of a multipage TIFF file could be unloaded.</td><td>Multipage TIFF files are supported.</td></tr><tr title="Версия 8.3.15" class="tag_14 tag_10"><td><a name="ae6dea02-f335-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>In the dialog box where you enter your username or password, you can now place hyperlinks to navigate to the help page and recover your password.<p>You can recover your password on the website, via email, or using the OpenID provider tools. New feature: each infobase user can recover their password. A configured system does not require human involvement to recover the user password.</p><p>New properties for the <span class="term">InfobaseUser </span>object: <span class="term">EmailAddress </span>and <span class="term">CannotRecoverPassword</span>.</p><p>New global context property: <span class="term">AdditionalAuthenticationSettings</span>.</p><p>Implemented the following event log events: <span class="interface">Session. Attempting to recover the password, Session. An error occurred while attempting to recover the password, Infobase. Changing additional authentication settings, Infobase. An error occurred while changing additional authentication settings.</span></p></td><td>The user password could be recovered with infobase administrator involvement only.</td><td>Now it is easier for a user to recover their password. Password recovery no longer requires direct administrator involvement.</td></tr><tr title="Версия 8.3.15" class="tag_43 tag_25"><td><a name="e35a167d-12ca-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Eliminated the error restoring data composition system settings and dynamic list settings when the settings were saved in version 8.3.16 or later but configuration compatibility mode was set to <span class="interface">Version 8.3.15</span>.
</td><td>If configuration compatibility mode was set to <span class="interface">Version 8.3.15</span> and data composition system settings or dynamic list settings were saved in platform version 8.3.16 or later, it was not possible to restore the settings.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.15" class="tag_14 tag_70 tag_10"><td><a name="5e737f3a-33d2-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can now distribute the client application via the web server using web server extensions, without configuring the <span class="interface">default.vrd </span>file. The client application distribution package will be searched in the <span class="interface">distr </span>directory of the version whose web server extension is running on the web server.<p>Implemented new versions of client application distribution packages that can be installed in addition to the full-fledged distribution package of 1C:Enterprise and contain packaged distribution packages of client applications. This option for delivering client applications is supported only for Windows and macOS</p></td><td>This feature was not provided.<p>The client application distribution package could be obtained from the web server only after the default.vrd file was configured correctly.</p></td><td>It is now easier to configure distribution of client application distribution packages when updating the 1C:Enterprise system version.
</td></tr></table><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="83bf2cbd-14ce-11e9-a3f7-0050569f678a">Transition from the previous version to the version 8.3.15</a></h2><ul><li title="Версия 8.3.15" class="tag_0"><a name="83bf2cbe-14ce-11e9-a3f7-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.15.
</li><li title="Версия 8.3.15" class="tag_0"><a name="83bf2cbf-14ce-11e9-a3f7-0050569f678a"></a>Some features that are added in version 8.3.15 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.15" class="tag_0"><a name="524c3711-239f-11e9-a3f7-0050569f678a"></a>To make accounting register performance increase noticeable, disable the compatibility mode. Accounting registers will be restructured. If infobase size exceeds 10 GB, it is recommended that you use optimized tool of database configuration update for restructuring.</li><li title="Версия 8.3.15" class="tag_0"><a name="936fcbf5-e43d-11e9-8371-0050569f678a"></a>It is recommended to completely rebuild the full-text search index to make searching for words ending in "*" character available.</li></ul><p><a href="#83bf2cb2-14ce-11e9-a3f7-0050569f678a"><small>Table of contents</small></a></p><h1><a name="e5c8dbf0-9a30-11e8-a3f7-0050569f678a">Version 8.3.14</a></h1><p title="Версия 8.3.14" class="tag_0"><a name="e5c8dbfe-9a30-11e8-a3f7-0050569f678a"></a>Version 8.3.14 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.14" class="tag_0"><a name="f2a3605d-9fc8-11e8-a3f7-0050569f678a"></a>Improved database configuration update mechanism graduated out of beta.</p><p title="Версия 8.3.14" class="tag_0"><a name="4fa5ec57-9fc9-11e8-a3f7-0050569f678a"></a>Windows-based 64-bit client application (thin client, thick client, and Designer) graduated out of beta.<p>
</p></p><p title="Версия 8.3.14" class="tag_0"><a name="22896d18-01ed-11e9-a3f7-0050569f678a"></a>The mobile client has graduated out of beta.</p><p title="Версия 8.3.14" class="tag_0"><a name="539357a4-01ed-11e9-a3f7-0050569f678a"></a>The Windows-compatible mobile platform has graduated out of beta.
</p><p title="Версия 8.3.14" class="tag_0"><a name="8720d84b-13eb-11e9-a3f7-0050569f678a"></a>Thin client for macOS graduated out of beta. Thick client and Designer for macOS are still in beta testing.</p><p title="Версия 8.3.14" class="tag_0"><a name="44ce899b-a534-11e8-a3f7-0050569f678a"></a>The term "managed application" is replaced with the term "client application." Unless necessary, the term "managed" is no longer used in V8Update file, help files, and documentation. For example, "managed application" is replaced with "client application" and "managed form input field extension" is replaced with "form input field extension." The renaming is applied to related UI texts in client applications and Designer.</p><hr></hr><ul><li><a href="#e5c8dbf1-9a30-11e8-a3f7-0050569f678a">New functionality and changes</a></li><li><a href="#e5c8dbf2-9a30-11e8-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#e5c8dbf3-9a30-11e8-a3f7-0050569f678a">Optimization</a></li><li><a href="#e5c8dbf4-9a30-11e8-a3f7-0050569f678a">Changes that affect system behavior</a></li><li><a href="#e5c8dbf5-9a30-11e8-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#e5c8dbf6-9a30-11e8-a3f7-0050569f678a">Renamed objects</a></li><li><a href="#e5c8dbf7-9a30-11e8-a3f7-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#e5c8dbf8-9a30-11e8-a3f7-0050569f678a">Library updates
</a></li><li><a href="#e5c8dbf9-9a30-11e8-a3f7-0050569f678a">Demo configuration changes</a></li><li><a href="#e5c8dbfa-9a30-11e8-a3f7-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#e5c8dbfb-9a30-11e8-a3f7-0050569f678a">Transition from the previous version to the version 8.3.14</a></li></ul><h2><a name="e5c8dbf1-9a30-11e8-a3f7-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.14" class="compat tag_2 tag_1"><td><a name="23fb0a7b-9a31-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.13</span> is now implemented.</td><td>Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.12 was implemented.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.13 or earlier can run on version 8.3.14 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.14 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.13 after the migration to version 8.3.14, even if you have disabled the compatibility mode (simply enable it again).
</td></tr><tr title="Версия 8.3.14" class="tag_6"><td><a name="faafeed4-9fc5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New standalone 1C:Enterprise server. It can handle client applications that operate an infobase over HTTP protocol.<p>The standalone server provides HTTP connection, the web-server is no longer required. The standalone server uses computer resources more efficiently.</p><p>A single instance of the standalone server provides access to a singe infobase. The standalone server does not support the Designer mode. You can operate the standalone server by the command-line utility. The standalone server supports both file and client/server mode of infobase.</p><p>It can handle up to 3 client applications in file mode (without sessions of background jobs, web-services etc.) without server license. It requires a server license of any type in other cases.</p><p>The standalone server has some limited functionality. For more info see documentation.</p><p>The standalone server provides some inbound administrative tools.</p><p>This feature is provided solely for beta testing purpose.
</p></td><td>This feature was not provided.</td><td>The new 1C:Enterprise architecture improves the stability and effectiveness of server operations.</td></tr><tr title="Версия 8.3.14" class="tag_7 tag_6 tag_19"><td><a name="03243339-ab81-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 7); return false;">Database copies</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Copies of tables that can intensify the DBMS load when used in reports or queries now can be stored in an external database (external to the 1C:Enterprise database). The feature is supported only in client/server mode.<p>You can define which database will be addressed by a specific report or query.</p><p>Table copies can be stored in a DBMS of any supported type. The server cluster DBMS type can differ from a database copy DBMS type.</p><p>The synchronization between the server cluster database and a database copy can be carried out by the means of DBMS or 1C:Enterprise.</p><p>New global context property: <span class="term">DatabaseCopies</span>. New <span class="term">Query </span>object properties: <span class="term">RequiredDataRelevance </span>and <span class="term">RequiredDataRelevanceTime</span>. New <span class="term">QueryResult </span>object properties: <span class="term">DataIsRelevant</span>, <span class="term">DataRelevanceTime</span>, and <span class="term">DatabaseCopy</span>. New <span class="term">DataCompositionOutputParameterValues </span>object properties: <span class="term">RequiredDataRelevance</span>, <span class="term">RequiredDataRelevanceTime</span>, <span class="term">DataRelevanceOutput</span>, and <span class="term">DatabaseCopyOutput</span>. New functions of the data composition system expression language: <span class="term">DataIsRelevant()</span>, <span class="term">DataRelevanceTime()</span>, and <span class="term">DatabaseCopy()</span>.</p><p>New system background jobs:<span class="interface"> Initial population of a database copy </span>and <span class="interface">Database copy notification handler</span>.</p><p>New cluster services: <span class="interface">Database copy service</span> and <span class="interface">Database copy time service</span>.</p><p>New standard function: <span class="interface">Database copy management</span>.</p><p>New technological log event: <span class="term">&lt;DBCOPIES&gt;</span>.</p><p>The database copy feature requires a CORP license.</p><p>This feature is provided solely for beta testing purpose.</p></td><td>This feature was not provided.</td><td>New feature: infobase load can be distributed among a few physical DBMS. For example, the main database can process all document entries, and the database copies can process reports and queries that significantly affect the database performance.</td></tr><tr title="Версия 8.3.14" class="tag_6 tag_29"><td><a name="af247bf3-9fc8-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>New feature: the accelerator of analytical report generation (Data accelerator). It is possible due to a new server cluster service, which acts as a database stored in RAM. Data accelerator is based on the database copy engine.<p>New server cluster service: <span class="interface">Data accelerator service</span>.</p><p>Data accelerator runs only on 64-bit operating systems. It does not support Windows XP and Windows Vista.</p><p>The database copy feature requires a CORP license.</p><p>This feature is provided solely for beta testing purpose. The Data accelerator service requires a beta testing license. It is not available without a beta testing license.</p></td><td>This feature was not provided.</td><td>The generation time of complicated analytical reports is significantly reduced.
</td></tr><tr title="Версия 8.3.14" class="tag_4"><td><a name="72060664-a20f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The collaboration system supports file operations. Collaboration system servers support the following file storages: Amazon S3, Google Cloud and other storages based on Amazon S3 protocol.<p>The following limitations can be set on collaboration system servers:</p><ul><li>Maximum attachment file size.</li><li>Total size of daily uploaded files.</li><li>Total size of daily received files.</li></ul><p>New property: <span class="term">CollaborationSystemMessage.Attachments</span>. New collaboration system methods: <span class="term">AttachmentsSupported()</span>, <span class="term">AttachCommandsGenerationHandler()</span>, and <span class="term">DetachCommandsGenerationHandler()</span>.</p></td><td>This feature was not provided.</td><td>Expanded collaboration system capabilities.</td></tr><tr title="Версия 8.3.14" class="tag_4"><td><a name="70ffaefa-a220-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Upgrade: more than two people can join a video conference. Participants can join and leave a conference at any moment. Upgrade: it is possible to establish video conferences between 1C:Enterprise 8.3.13 and 8.3.14. In this case, only one-on-one video conference is possible.</td><td>This feature was not provided.<p>Only video calls (one-on-one video conferences) were possible.</p></td><td>Expanded collaboration system capabilities.</td></tr><tr title="Версия 8.3.14" class="tag_20"><td><a name="50f8e6a2-a228-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New features for Designer agent mode (similar to the features provided by Designer command line):<ul><li>Dump a mobile platform configuration to XML files.</li><li>Generate a mobile client signature.</li><li>Dump a mobile client configuration.</li><li>Dump a configuration or extension to a file.</li><li>Restore a configuration or extension from a file.</li><li>Disable configuration support.</li><li>Dump an infobase.</li><li>Restore an infobase.</li><li>Delete infobase data.</li></ul><p>New features for Designer agent mode (not available in other modes):</p><ul><li>Create an empty extension.</li><li>Delete an extension.</li><li>Get extension properties.</li><li>Set extension properties.</li></ul><p>New feature: show status of time-consuming operations in agent mode (for some commands).</p><p>Upgrade: more errors are described by specific code in <span class="term">error-</span><span class="term">type</span> field.</p><p>Upgrade: messages returned after a command execution in agent mode contain more details.</p></td><td>These features were not provided.</td><td>New features for Designer in agent mode.</td></tr><tr title="Версия 8.3.14" class="tag_6 tag_10"><td><a name="7149f8f7-a510-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New feature: you can administer server clusters using 1C:Enterprise language. The administration is based on <span class="interface">ras </span>server, without using COM technology. The cluster supports servers with 1C:Enterprise versions different from the client application version. The administration tools are available from the thin client and from the server.<p>New object: <span class="term">ServerAdministration</span>.</p></td><td>This feature was not provided.<p>Server cluster administration was available from 1C:Enterprise language only over COM connections on a server running on Windows. Server administration required a 1C:Enterprise version identical to the server version.</p></td><td>You can implement cross-platform administration interfaces for 1C:Enterprise server clusters with the client application version different from the server cluster version. You can implement cluster consoles for Linux. It is not necessary to use the cluster console that requires Microsoft Management Console.</td></tr><tr title="Версия 8.3.14" class="tag_64"><td><a name="f00c440f-a515-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New feature: number-noun agreement. New global context method: <span class="term">GetStringDeclensionsByNumber()</span>.</td><td>This feature was not provided.</td><td>Generating sentences with numbers (in words or figures) is more convenient.</td></tr><tr title="Версия 8.3.14" class="tag_36"><td><a name="b33c947f-a529-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>New feature: solving systems of linear equations. New object: <span class="term">SolvingLinearEquationsSystems</span></td><td>This feature was not provided.</td><td>Solving large systems of linear equations takes less time.</td></tr><tr title="Версия 8.3.14" class="tag_64"><td><a name="afa7e125-a5e3-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New picture added to the picture library: <span class="term">Attach</span>.</td><td>The picture was not available in the library.</td><td>The picture library is upgraded.</td></tr><tr title="Версия 8.3.14" class="tag_38"><td><a name="9ec39b65-a5f1-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New feature: an adopted enumeration value set can be extended.<p>When an extension with an extended enumeration value set is deleted, the infobase object attributes that stored the deleted values take a blank reference to the enumeration as their values.</p></td><td>This feature was not provided.</td><td>Enumeration management is upgraded.</td></tr><tr title="Версия 8.3.14" class="tag_38"><td><a name="650c33ac-a5f2-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New property for metadata objects adopted to extensions: <span class="term">Comment</span>. The property is intended solely for developers and ignored when building the final configuration or during extension applicability tests.</td><td>This feature was not provided.</td><td>Developers can describe the purpose of extension objects using built-in means.</td></tr><tr title="Версия 8.3.14" class="tag_38 tag_36"><td><a name="e59abe6f-a5f2-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>You can create native session parameters in a configuration extension. They can be included in access restriction text.</td><td>This feature was not provided.</td><td> Extended configuration extension options.</td></tr><tr title="Версия 8.3.14" class="tag_121"><td><a name="0f82069e-a78e-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 121); return false;">Calculation registers</a>.<br></td><td>New feature: you can get the effective period of a calculation register record set before the set is written. New method for calculation register record sets: <span class="term">GetAdjustedEffectivePeriod()</span>.</td><td>The effective period could be calculated only after a calculation register record set was written. </td><td>Due to reducing the number of writing operations, parallel register calculations and performance are improved in certain scenarios.</td></tr><tr title="Версия 8.3.14" class="tag_6"><td><a name="46398cc8-a791-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New filters for resource consumption counters: by safe mode and by security profile.<p>New comparison operator for filtering resource consumption counters: inequality.</p><p>New resource consumption counter filter feature: a number of conditions with the same filter type can be combined using the AND operator. </p></td><td>These features were not provided.</td><td>Advanced performance analysis for applications running in client/server mode.</td></tr><tr title="Версия 8.3.14" class="compat tag_25 tag_1"><td><a name="a06301e2-a9ff-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The data composition system can display pictures stored in the infobase. Reports can include both pictures specified as URLs and pictures stored in attributes of <span class="term">ValueStorage </span>type.<p>New properties of <span class="term">DataCompositionAppearance </span>and <span class="term">DataCompositionAreaTemplateTableCellAppearance </span>objects: <span class="term">PictureOutput</span>, <span class="term">PictureSize</span>, <span class="term">TextPositionRelativeToPicture</span>, <span class="term">PictureHorizontalAlign</span>, and <span class="term">PictureVerticalAlign</span>.</p><p>The default behavior is not changed in Version 8.3.13 compatibility mode.</p></td><td>The data composition system did not provide means for displaying pictures stored in the infobase.</td><td>New formatting options for the data composition system.</td></tr><tr title="Версия 8.3.14" class="tag_63"><td><a name="b5b05b84-aaa9-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>New feature: editing sets of chart series and points. New methods for <span class="term">ChartPoints </span>and <span class="term">ChartSeriesCollection </span>objects: <span class="term">Insert(),</span> <span class="term">Move()</span>, <span class="term">Delete()</span>, and <span class="term">Clear()</span>.</td><td>This feature was not provided.<p>To edit a point or value, one had to refill all chart data.</p></td><td>New chart features.<p>For example, you can create autoscrolling charts where the first point of a chart is removed and the last one is added with a certain period.</p></td></tr><tr title="Версия 8.3.14" class="tag_14"><td><a name="73f36bf9-ac5a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Batch mode is implemented for the thin and thick clients. The batch mode is available from the start of a client application till the completion of the <span class="term">BeforeStart </span>handler in the application module. Then the batch mode is turned off automatically. The batch mode suppresses all system dialog boxes.<p>The <span class="term">/DisableStartupDialogs </span>command-line option switches a client application to the batch mode. For more information about the batch mode, see 1C:Enterprise documentation.</p><p>New global context method: <span class="term">ProhibitFormOpening()</span>. </p><p>You can add the option that enables batch mode to client application startup parameters in Designer.</p><p>Runtime errors in the <span class="term">RunApp()</span> or <span class="term">BeginRunningApplication()</span> method generate exceptions in batch mode.</p></td><td>This feature was not provided.<p>Only Designer supported the batch mode.</p><p>Runtime errors in the <span class="term">RunApp()</span> or <span class="term">BeginRunningApplication() </span>method generated dialog boxes with error descriptions on the server.</p></td><td>Client application startup scenarios where you can suppress opening dialog boxes that normally block programmatic handling of startup issues are now possible.</td></tr><tr title="Версия 8.3.14" class="tag_29"><td><a name="515d82d1-d831-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>New feature: software license for beta testing. The license is complementary to 1C:Enterprise server license. Beta testing license cannot replace a 1C:Enterprise server licence. The number of beta testing licenses must be equal to or greater than the number of server licenses for the server cluster that runs the tests.<p>If a new feature requires a beta testing license, it is mentioned in the feature announcement.</p><p>To apply for a beta testing license, send your request to <a href="mailto:betaplatform@1c.ru" target="_blank">betaplatform@1c.ru</a>.</p><p>Licensing utility now supports feature testing licenses.
</p></td><td>Feature beta testing did not require special licenses.</td><td>In some cases, feature beta testing requires beta testing licenses.</td></tr></table><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbf2-9a30-11e8-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.14" class="tag_28"><td><a name="469ee425-a52f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The web client does not support configurations with Version 8.2 interface. The web client does not support switching between Version 8.2 and <span class="interface">Taxi </span>interfaces. Command-line options <span class="term">itdi </span>and <span class="term">itaxi </span>are ignored. The options are considered obsolete and not recommended for use. Regardless of the value of the <span class="term">ClientSettings.ClientApplicationInterfaceVariant </span>property, the <span class="interface">Taxi </span>interface is used. </td><td>The web client supported Version 8.2 interface.</td><td>Support of obsolete client application interface type is discontinued. Web client stability is improved.</td></tr><tr title="Версия 8.3.14" class="tag_4"><td><a name="bb858ce2-a9d1-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Upgrade: a user can separately turn off the camera or microphone during a video call.</td><td>When a user turned off the camera during a video call, the microphone turned off automatically.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_86"><td><a name="2ad2e2cc-a9de-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>Upgrade: if a section or command interface command has a help topic, its tooltip does not contain the "Help" hyperlink.<p>The help topics are still available from the help window.</p><p>In the current section functions panel and the functions menu, lists and configuration objects have tooltips with their explanations or extended presentations.</p></td><td>The tooltip behavior was as follows:<ul><li>If a section had a help topic, the tooltip for the section in the sections panel contained the "Help" hyperlink.</li><li>If a command had a help topic, the tooltip for the command in the current section functions panel contained the "Help" hyperlink.</li><li>The functions menu commands did not have tooltips.</li><li>In the web client, section tooltips in the sections panel contained the section synonyms, not the explanations.</li><li>In the web client, in the current section functions panel, tooltips of lists and objects contained the command synonyms, not the explanations or extended presentations of lists and objects.</li></ul></td><td>Faster command interface displaying in the thin client. Standardized view of section and command tooltips in different client applications</td></tr><tr title="Версия 8.3.14" class="tag_38 tag_28"><td><a name="c0fcc268-aacd-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client, if an infobase contains extensions, browsers cache pictures according to the following rules:<ul><li>Extended configuration pictures are cached for all sessions of the infobase.</li><li>Extension pictures are cached for each session.</li></ul></td><td>In the web client, if an infobase contains extensions, browsers cached all configuration pictures for each session.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbf3-9a30-11e8-a3f7-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.14" class="tag_63"><td><a name="a864b94d-a782-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Upgrade: improved performance of charts that contain large data sets.<p>We recommend that you analyze charts in your applications and refactor them as follows:</p><ul><li>The initial data population is performed on the server.</li><li>Major data changes (including data repopulations) are performed on the server.</li><li>Minor data changes can be performed on the client.</li></ul></td><td>Inefficient performance of charts that contained large data sets.</td><td>Improved performance of charts that contain large data sets.</td></tr><tr title="Версия 8.3.14" class="tag_10"><td><a name="e0710511-aa05-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Upgrade: the user list in Designer opens faster. The improvement is noticeable if the list contains many users and roles.
</td><td>In an infobase that contained many users and roles, the user list opened slowly.</td><td>The user list opens faster.</td></tr><tr title="Версия 8.3.14" class="tag_82 tag_42"><td><a name="a8192fe0-aa09-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br></td><td>Upgrade: faster totals recalculation for accounting registers and accumulation registers in the following cases:<ul><li>During <span class="interface">Verify and repair </span>operation in Designer.</li><li>Using the <span class="term">RecalcTotals()</span> method when the following conditions are met:</li></ul></td><td>Totals recalculation for accounting registers and accumulation registers took a significant amount of time.</td><td>Totals recalculation for accounting registers and accumulation registers takes less time.</td></tr><tr title="Версия 8.3.14" class="compat tag_21 tag_1"><td><a name="522efd6c-ab74-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Upgrade: faster search for expressions like "word*" when an application has many instances of "word". Upgrade: exceeding search word threshold is less likely for expressions like "word*".<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>Search for expressions like "word*" could fail due to exceeding search word threshold error.</td><td>Optimization of full-text search.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="dd23743d-ab92-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Upgrade: faster restructuring of infobases based on Microsoft SQL Server and IBM Db2.</td><td>Restructuring of infobases based on Microsoft SQL Server and IBM Db2 took more time.</td><td>Faster restructuring of infobases based on Microsoft SQL Server and IBM Db2.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="a98985e7-ac61-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Upgrade: simultaneous release of a number of connections with Microsoft SQL Server is less likely, which improves <span class="term">TempDB </span>performance.</td><td>There was a possibility of simultaneous release of a number of connections with Microsoft SQL Server, which significantly reduced <span class="term">TempDB </span>performance.</td><td>Optimized operation of TempDB on Microsoft SQL Server.</td></tr><tr title="Версия 8.3.14" class="tag_121"><td><a name="966b93be-ad09-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 121); return false;">Calculation registers</a>.<br></td><td>New feature: clustered index by recorder for calculation registers. An index is rebuilt during calculation register restructuring or during Verify and repair operation.<p>Upon deleting records from an effective period table, if there is no filter by register dimensions, the deletion query does not require establishing connection to the main register table. </p></td><td>Clustered index was not available for calculation registers.<p>Upon deleting records from an effective period table, if there was no filter by register dimensions, the deletion query always established connection to the main register table. </p></td><td>Reduced possibility of table lock upon deleting calculation register effective period records.</td></tr></table><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbf4-9a30-11e8-a3f7-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.14" class="tag_122"><td><a name="6caa655b-a46d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 122); return false;">Client applications</a>.<br></td><td>New feature: the thin client (connected over HTTP/HTTPS) supports all OpenID authentication providers that support OpenID Connect protocol.</td><td>This feature was not provided.<p>Only the web client supported such OpenID authentication providers.</p></td><td>New user authentication option for the thin client.</td></tr><tr title="Версия 8.3.14" class="tag_14"><td><a name="fefc3734-a484-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>New feature: user authentication with Unified System for Identification and Authentication (USIA) in the web client or thin client (connected over HTTP/HTTPS).<p>New properties in OpenID Connect provider description in the <span class="interface">default.vrd </span>file (the <span class="term">&lt;providers&gt;</span> element): <span class="term">dialect </span>and <span class="term">crypto</span>.</p><p>In the thin client, authentication with USIA is possible only if the infobase is published on an Apache web server.</p></td><td>This feature was not provided.</td><td>New user authentication option.</td></tr><tr title="Версия 8.3.14" class="tag_45 tag_25"><td><a name="b257083f-a517-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New feature: when managing queries with the <span class="term">QuerySchema </span>object, you can use the query language extension for the data composition system.<p>New property: <span class="term">QuerySchema.DataCompositionMode</span>. New properties for the <span class="term">QuerySchemaSelectQuery </span>object: <span class="term">DataCompositionSelectionFields </span>and <span class="term">Characteristics</span>. New property: <span class="term">QuerySchemaSelectOperator.DataCompositionFilterExpression</span>. New property: <span class="term">QuerySchemaTable.DataCompositionParameters</span>.</p><p>New feature: query wizard in 1C:Enterprise mode supports the query language extension for the data composition system.</p><p>New property: <span class="term">QueryWizard.DataCompositionMode</span>. </p></td><td>The <span class="term">QuerySchema </span>object did not support the query extension for the data composition system.<p>Query wizard in 1C:Enterprise mode did not support the query language extension for the data composition system.</p></td><td>New features for queries in 1C:Enterprise mode related to the extension for the data composition system.</td></tr><tr title="Версия 8.3.14" class="tag_6"><td><a name="3bcd1e3c-a529-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Upgrade: on cluster manager crash the details of the running and completed background jobs are saved. Scheduled jobs starting and processing is not interrupted.</td><td>Cluster manager crash caused the following:<ul><li>For all infobases, the details of the running and completed background jobs were lost, as well as background job-related messages.</li><li>If a client application was waiting for background jobs to complete, it stopped responding for indefinite period.</li><li>Execution of scheduled job stopped for one minute, till the data was reread from the infobases.</li></ul></td><td>Improved fault tolerance of server cluster operations related to background and scheduled jobs. Users of applications that run background or scheduled jobs do not notice cluster manager crashes.</td></tr><tr title="Версия 8.3.14" class="compat tag_43 tag_1"><td><a name="6c7f9b9e-a54d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>New feature: you can specify fields that will be used as selection key fields. New properties for the <span class="term">DynamicList </span>object: <span class="term">KeyType </span>and <span class="term">KeyFields</span>. New object: <span class="term">DynamicListRowKey</span>. New feature: dynamic list query settings dialog box allows customization of the fields that form row keys.<p>This feature is ignored in 8.3.7 version compatibility mode.</p><p>We recommend that you revise all dynamic lists (excluding <span class="term">RecordsWithExtDimensions</span>, <span class="term">TasksByPerformer</span>, filter criterion, and information register slice tables) with no main table specified or where the main table is a virtual table without a key toward using keys of <span class="interface">Field value </span>or <span class="interface">Row key </span>types.</p></td><td>This feature was not provided.<p>Key fields were defined by the main dynamic list table.</p></td><td>New feature for dynamic lists with no main table. Improved performance of dynamic lists with no main table. For example, now such dynamic lists support groupings.</td></tr><tr title="Версия 8.3.14" class="tag_20"><td><a name="0de9424e-a5e7-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New feature: in Designer agent mode, names of user working directories contain numeric codes. The directory–user mapping is stored in <span class="interface">agentbasedir.json</span> file located in the agent working directory (the <span class="term">AgentBaseDir </span>command-line option).</td><td>In Designer agent mode, names of user working directories contained the usernames.</td><td>Working directory names do not reveal the names of the users that work in Designer agent mode. Shorter paths to user working directories.
</td></tr><tr title="Версия 8.3.14" class="tag_38"><td><a name="942a217d-a5ee-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Upgrade: when a form is adopted by an extension, only form items are adopted. After adoption, you can edit all item properties from an extension using the form editor. By default, other form objects (such as attributes, commands, and parameters) are not adopted, so they are not editable. To edit such objects, you must include them in the extension.<p>When a form is adopted, the parent configuration object of the form is not adopted.</p><p>The upgrade does not affect the forms adopted to extensions in the previous 1C:Enterprise versions.</p></td><td>When a form was adopted by an extension, the parent configuration object and all the extension objects were adopted.</td><td>Managing adopted configuration object forms is more convenient. Adjusting extensions to new configuration versions is more convenient.</td></tr><tr title="Версия 8.3.14" class="compat tag_63 tag_25 tag_1"><td><a name="9f8d1bd7-a5f4-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Upgrade: when you print a report, each chart fits one page. Upon printing, the data composition system output processor sets <span class="term">StayWithNext </span>property value to <span class="term">True </span>for the spreadsheet document rows that follow the chart.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>In a printed report, a chart could be ripped by a page break.</td><td>Printed reports are more readable.</td></tr><tr title="Версия 8.3.14" class="tag_115"><td><a name="ddeb26b8-a5fe-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Upgrade: in the thin, thick, and web clients, a form unlocks objects in one minute after the modification flag is cleared.</td><td>In the thin, thick, and web client, a form unlocked objects after the form had been closed.</td><td>Parallel operation is improved in some cases.</td></tr><tr title="Версия 8.3.14" class="compat tag_63 tag_1"><td><a name="f8c6f1dd-a786-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The algorithm that calculates the plot area size for a pie chart is revised. It reserves more space for highlighting the sector where the pointer is.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>The plot area of a pie chart occupied all available space. This might cause cropping of the highlighted sector area.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_38"><td><a name="b7d96e38-a789-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Upgrade: when a configuration extension is applied, the number of parameters and <span class="term">Val </span>keyword before event handler parameters are not checked.</td><td>When a configuration extension was applied, the number of parameters and <span class="term">Val </span>keyword before event handler parameters were checked. The number of parameters in an extension had to match the number of parameters in an extended configuration.</td><td>Extension behavior complies with the platform behavior for the main configuration. Upon an event handler call, the number of parameters is not checked.</td></tr><tr title="Версия 8.3.14" class="compat tag_25 tag_1"><td><a name="506f708a-a9ee-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Upgrade: upon data composition template generation, a field alias includes the source field alias and the field details (the presentation of the field attribute, the aggregate function, and so on).<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>Upon data composition template generation, default query wizard naming rules were applied to create a field alias.</td><td>A field content is more transparent by its alias.</td></tr><tr title="Версия 8.3.14" class="tag_79"><td><a name="471fbde4-aaaa-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>New feature: support of GIF pictures with "XMP DataXMP" extension.</td><td>This feature was not provided.</td><td>Extended list of supported picture formats. 1C:Enterprise supports GIF pictures created with Adobe tools.</td></tr><tr title="Версия 8.3.14" class="tag_19 tag_17"><td><a name="3ac9fcb9-aab0-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>Upgrade: for PostgreSQL DBMS, the technological log (<span class="term">&lt;plansql&gt;</span> event) keeps query plans for <span class="term">UPDATE</span>, <span class="term">DELETE</span>, and <span class="term">INSERT</span> queries.</td><td>For PostgreSQL DBMS, the technological log (<span class="term">&lt;plansql&gt;</span> event) kept query plans only for <span class="term">SELECT</span> queries.</td><td>Analyzing applications based on PostgreSQL DBMS is more convenient.
</td></tr><tr title="Версия 8.3.14" class="tag_20"><td><a name="07a8a096-ac35-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Upgrade: upon comparing configuration modules, you can see which methods are unchanged but moved to another preprocessor instruction or region.
</td><td>Upon comparing configuration modules, methods that were unchanged but moved to another preprocessor instruction or region were displayed as changed, which could be misleading.</td><td>Module comparison is more transparent and convenient.</td></tr><tr title="Версия 8.3.14" class="tag_26 tag_63"><td><a name="487c6001-ac3c-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>When a spreadsheet document is displayed in the edit mode in the thin client, thick client, or Designer, pointing to a chart area opens its properties.</td><td>When a spreadsheet document was displayed in the edit mode in the thin client, thick client, or Designer, opening chart area properties required the following steps: first double-click the chart, and then point to the area.</td><td>Simplified interaction with charts embedded to spreadsheet documents.</td></tr><tr title="Версия 8.3.14" class="tag_73"><td><a name="889a6958-ad08-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>New feature: critical errors of the optimized database configuration update mechanism are displayed in Designer and in the <span class="term">&lt;EXCP&gt;</span> event of the technological log.</td><td>Critical errors of the optimized database configuration update mechanism were not displayed in Designer or in the <span class="term">&lt;EXCP&gt;</span> event of the technological log.</td><td>Improved diagnostics of critical errors in the optimized database configuration update mechanism.</td></tr><tr title="Версия 8.3.14" class="tag_26"><td><a name="39ecc505-d83a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Upgrade: data import from Microsoft Office OpenXML (Microsoft Excel 2007 or later) and ODT (OpenDocument) files is updated. Some bugs related to import from these file types are fixed.</td><td>Importing data from Microsoft Office OpenXML (Microsoft Excel 2007 or later) and ODT (OpenDocument) files could cause errors.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_26 tag_1"><td><a name="f912f348-d842-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Upgrade: when exporting a spreadsheet document from an XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) file, if a shape or picture text in the source spreadsheet is blank or contains only spaces, a drawing of Text type is not created in the target spreadsheet.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>When importing a spreadsheet document from an XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) file, the following behavior occurred:<ul><li>For shapes, if the text was blank, the import was not performed; if the text contained only spaces, the import was performed.</li><li>For pictures, if the text was blank or contained only spaces, the import was performed.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_27"><td><a name="781ec93c-d847-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>When the configuration root is restored from XML partially and there is no external property file with support settings, the restore settings will be cleared. The configuration support will disabled as a result.</td><td>When the configuration root was restored from XML partially and there was no external property file with support settings, the restore settings remained intact. The configuration support mode remained intact as well.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_26 tag_1"><td><a name="daf4b6b9-d849-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Upgrade: for spreadsheet document drawings that are comments, the <span class="term">DrawingType </span>property value is <span class="term">SpreadsheetDocumentDrawingType.Comment</span>.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>For spreadsheet document drawings that were comments, the <span class="term">DrawingType </span>property value was <span class="term">SpreadsheetDocumentDrawingType.Text.</span></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_26 tag_1"><td><a name="68e275c2-d84a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Text is displayed correctly in spreadsheet document cells with "Justify" alignment. <p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>Text in spreadsheet document cells with "Justify" alignment looked as text with "Left" alignment.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_25 tag_1"><td><a name="89e9cfab-dcec-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The data composition system template generator outputs resource field groupings to templates even if a predefined template describes the output of the parent grouping and resources are not specified in the selected fields of the parent grouping but specified in the fields of the child grouping.<p>This might change the look of some reports.</p><p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>The data composition system template generator did not output resource field groupings to templates if a predefined template described the output of the parent grouping and resources were not specified in the selected fields of the parent grouping but were specified in the fields of the child grouping.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_17"><td><a name="b1b52821-e25d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>New technological log properties for DBMS access events (<span class="term">DB2</span>, <span class="term">DBMSSQL</span>, <span class="term">DBPOSTGRS</span>, and <span class="term">DBORACLE</span>) and <span class="term">EXCP </span>and <span class="term">SDBL </span>events: <span class="term">Dbms</span>, <span class="term">Database</span>, and <span class="term">DBCopy</span>.</td><td>This feature was not provided.</td><td>More convenient DBMS selection diagnostics when managing database copies.</td></tr><tr title="Версия 8.3.14" class="tag_20"><td><a name="bfba751d-e25e-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Upgrade: when comparing configurations, you can view the detailed differences in help topics. Upgrade: you can compare help topics in selected language, similar to other platform multilingual tools.</td><td>When comparing configurations, you could only see if the help topics were different, without any details on the differences.</td><td>Comparing help topics in configurations is more convenient.</td></tr></table><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbf5-9a30-11e8-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.14" class="tag_10 tag_116"><td><a name="55a3045d-a51c-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>New feature: <span class="interface">ring </span>command-line utility and its <span class="interface">license </span>module are provided as a standalone distribution package (<span class="interface">1C:Enterprise licensing utility</span>). The distribution package supports Windows 7 and later, and Linux x86 and x86-64.<p>The distribution archive names comply with the following pattern: <span class="interface">1c-enterprise-license-tools-a.b.c+d-os-arch.zip</span>. The archive is included into 1C:Enterprise distribution package.</p><p>The distribution packages of the <span class="interface">ring </span>utility and its <span class="interface">license </span>module are no longer stored to the <span class="interface">ExtDst </span>directory.</p><p>You can find 1C:Enterprise installer documentation on the ITS DVD <a href="https://its.1c.ru/db/inst10doc" target="_blank">Read more</a>..</p></td><td>The <span class="interface">ring </span>utility and its <span class="interface">license </span>module were a part of 1C:Enterprise distribution package and were stored to the <span class="interface">ExtDst </span>directory. The installation of the ring utility was available only after the installation of 1C:Enterprise.</td><td>Distribution and update of the <span class="interface">ring </span>utility and its <span class="interface">license </span>module are more convenient. To install or update the licensing utility, you do not have to install the entire 1C:Enterprise.</td></tr><tr title="Версия 8.3.14" class="tag_116"><td><a name="769f1fe3-a52e-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>New feature: upon activating ("<span class="interface">activate</span>" command) a software license and upon creating a response file ("<span class="interface">acquire</span>" command) with the <span class="interface">ring </span>utility, you can specify an alternative Licensing Center. A Licensing Center can be set in the <span class="term">ExternalResourcesMode </span>parameter of the <span class="interface">conf.cfg </span>file.<p>New parameter for the "<span class="interface">ring license activate</span>" and "ring <span class="interface">license acquire</span>" commands:<span class="term"> --conf-location</span>, which is used to specify the directory for the <span class="interface">conf.cfg </span>file.</p></td><td>This feature was not provided.<p>Only one Licensing Center was available.</p></td><td>Licensing Center selection is similar to selection of other internet resources required by 1C:Enterprise. The system behavior is more consistent.</td></tr><tr title="Версия 8.3.14" class="tag_37 tag_64"><td><a name="6f87e624-a531-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New feature: client applications that run on Windows use WebKit library to manage help, Syntax Assistant, HTML document fields, planner, formatted documents, and HTML document editor. In these cases, Microsoft Internet Explorer is no longer applicable.<p>WebKit is included into 1C:Enterprise distribution package and does not require separate installation.</p><p>The <span class="term">HTMLDocumentField.Document </span>property value type is <span class="term">ExternalObject</span>. The DOM model that can be accessed by this property is changed.</p><p>We recommend that you review the use of <span class="term">HTMLDocumentField </span>form item in your applications and update applications that use features specific for Microsoft Internet Explorer. </p></td><td>Client applications that ran on Windows used Microsoft Internet Explorer to manage help, Syntax Assistant, HTML document fields, planner, formatted documents, and HTML document editor.</td><td>Managing HTML documents is more consistent, regardless of the operating system.</td></tr><tr title="Версия 8.3.14" class="tag_93"><td><a name="7a392f8a-a549-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br></td><td>New feature to ensure the correct identification of two-digit years: the first year of the century. The default first year of the century is changed from 1930 to 1950, meaning 49 is identified as 2049 and 50 as 1950. In a separated infobase, each data area defined by a set of independent separators has its own first year of the century.<p>New global context methods: <span class="term">SetInfobaseBeginningOfCentury()</span>, <span class="term">GetInfobaseBeginningOfCentury()</span>, and <span class="term">SessionBeginningOfCentury()</span>.</p></td><td>The default first year of the century to identify two-digit years was 1930. The year could not be changed.</td><td>System behavior related to two-digit years is more transparent. You can customize the first year of the century.</td></tr><tr title="Версия 8.3.14" class="tag_28 tag_20"><td><a name="98ae1610-a5fc-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Upgrade: for a file infobase published on a web server, connecting the web client to the infobase in debug mode is only allowed if the infobase was published with the option that allows debugging. Otherwise, debugging is not available.<p>To debug an application using the web client with a file infobase, you have to republish the infobase with debugging allowed.</p></td><td>Debugging applications using the web client with a file infobase was available regardless of the debugging status in the infobase publishing settings.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_38 tag_110 tag_1"><td><a name="32c5bd10-a614-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br></td><td>New pattern of roles–extensions interaction:<ul><li>Users have access to all extension objects if the extension and the extended configuration do not contain roles.</li><li>"<span class="interface">Set rights for new objects</span>" role property in the extended configuration also covers the extension objects.</li><li>"<span class="interface">Set rights for attributes and tabular sections by default</span>" role property in the extended configuration also covers the extension objects.</li><li>"<span class="interface">Set rights for native attributes and tabular sections by default</span>" role property in the extension's native role also covers attributes and tabular sections of the adopted extension objects.</li></ul><p>
Adopt roles into extensions only when you need to set the extension object rights that do not match the extended configuration's default rights.</p><p>Upgrade: <span class="term">DefaultRoles </span>property can be expanded.</p><p>This pattern is ignored in 8.3.13 version compatibility mode.</p></td><td>Old pattern of roles–extensions interaction:<ul><li>Users had access to all extension objects if the extension did not contain roles.</li><li>To set rights for extension objects (including attributes and tabular sections) you had to adopt all roles you needed to change into the extension.</li></ul></td><td>More convenient roles–extensions interaction pattern. The interaction logic is more transparent.</td></tr><tr title="Версия 8.3.14" class="tag_63 tag_25"><td><a name="9ef960fb-a786-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New chart tooltip types and view options. New feature: reference lines and tooltips can be displayed at the same time.<p>New properties for the <span class="term">Chart </span>object: <span class="term">ChartValuesTooltipDisplayMode</span>, <span class="term">ValueTooltipFillType</span>, <span class="term">PointsPopUpReferenceLineRepresentation</span>, and <span class="term">ValuesPopUpReferenceLineRepresentation</span>.</p><p>New feature: chart items can be selected manually or programmatically. A selection can include nonadjacent items.</p><p>New property for the <span class="term">Chart </span>object: <span class="term">SelectionMode</span>. New event and methods for chart field extensions of field forms. Event: <span class="term">OnActivate</span>. Methods: <span class="term">GetSelectedItems</span>() and <span class="term">SetSelectedItems()</span>. New methods for the <span class="term">SpreadsheetDocumentDrawing </span>object: <span class="term">GetSelectedItems()</span> and <span class="term">SetSelectedItems()</span>.</p><p>New properties for the <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroupOutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance </span>objects: <span class="term">ChartType.ValueTooltipDisplayMode</span>, <span class="term">ChartType.ChartValuesTooltipFillType</span>, <span class="term">ChartType.PointsPopUpReferenceLineRepresentation</span>, <span class="term">ChartType.ValuesPopUpReferenceLineRepresentation</span>, and <span class="term">ChartType.SelectionMode</span>.</p></td><td>The following chart features were available:<ul><li>Upon hovering over a chart item, display a tooltip.</li><li>Upon double-clicking a chart item, trigger the <span class="term">Selection </span>event.</li><li>Upon double-clicking a chart value, point, or series with details, trigger the <span class="term">DetailProcessing </span>event.</li></ul></td><td>Improved chart interactivity.</td></tr><tr title="Версия 8.3.14" class="compat tag_115 tag_1"><td><a name="06a27f74-a9df-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Upgrade: if a form input field contains a value of reference type, its <span class="term">ChoiceFoldersAndItems </span>property value set to <span class="term">Auto </span>is interpreted as <span class="term">Items</span>.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>If a form input field contained a value of reference type, its <span class="term">ChoiceFoldersAndItems </span>property value set to <span class="term">Auto </span>was interpreted as <span class="term">FoldersAndItems</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_25 tag_1"><td><a name="2f7dd713-a9ec-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Upgrade: upon generation of a data set selection query, the data composition template generator makes an attempt to aggregate the data using the DBMS query language. Query language functions applied to a single field for data aggregation: <span class="term">SUM()</span>, <span class="term">MINIMUM()</span>, and <span class="term">MAXIMUM()</span>.<p>New property that manages aggregate calculation with query language: <span class="term">DataCompositionSchemaDataSetQuery.UseQueryGroupsIfPossible</span>.</p><p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>The data composition system did not use grouping to aggregate data in queries, unless it was explicitly specified by the <span class="term">GROUP BY</span> clause.</td><td>Improved data acquisition by the data composition system in some cases.</td></tr><tr title="Версия 8.3.14" class="compat tag_25 tag_1"><td><a name="7c057a95-a9fe-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New comparison algorithm for arrays, value tables, and other nonprimitive types in the data composition system:<ul><li>For arrays, the algorithm output is the result of element-by-element comparison.</li><li>For value tables, the algorithm output is the result of element-by-element comparison.</li><li>For objects of types other than primitive, reference, array, and value table types, the following comparison algorithm is applied:</li><p>
</p><p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></ul></td><td>The algorithm output for objects of the same type (including arrays and value tables, excluding objects of primitive type and reference type) was comparison of the object RAM addresses.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_6 tag_10"><td><a name="f951aa2c-aaad-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New properties for the <span class="term">IClusterInfo </span>object: <span class="term">ErrorsCountThreshold </span>(the number of server errors that is considered critical) and <span class="term">KillProblemProcesses </span>(force closes corrupted processes).</td><td>This feature was not provided.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_45 tag_1"><td><a name="ae79757c-aab6-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Upgrade: if a query selection list does not contain tabular section attributes, but the query contains a comparison of tabular section attributes combined with "AND" operator, the conditions are applied together to each tabular section row.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>If a query selection list did not contain tabular section attributes, but the query contained a comparison of tabular section attributes combined with "AND" operator, the conditions were applied separately, which could lead to incorrect comparison results.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_79"><td><a name="243db2f1-aadc-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>New feature: you can use 1C:Enterprise language to change picture parameters, such as format, size, DPI, and color depth. New picture management logic:<ul><li>The Picture object contains only picture details and supports picture reading and writing.</li><li>New object for picture editing: PictureToProcess.</li></ul><p>New methods for the <span class="term">Picture </span>object: <span class="term">Width()</span>, <span class="term">Height()</span>, <span class="term">ColorDepth()</span>, <span class="term">GrayScale()</span>, <span class="term">HorizontalDensity()</span>, <span class="term">VerticalDensity()</span>, and <span class="term">FileSize()</span>.</p><p>The <span class="term">Picture.Convert()</span> method is deprecated. The <span class="term">PictureProcessor </span>object is deprecated. All <span class="term">PictureProcessor </span>object's methods have matching <span class="term">PictureToProcess </span>object's methods.</p><p>We recommend that you analyze your applications and replace the deprecated methods and objects with the new ones.</p></td><td>These features were not provided.<p>The only editable picture parameter was picture format.</p></td><td>You can change the parameters of any picture stored in an infobase, for example when you need to send it to a third party having specific requirements to pictures.</td></tr></table><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbf6-9a30-11e8-a3f7-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.14" class="tag_0"><td><a name="7d5e536e-a534-11e8-a3f7-0050569f678a"></a>The name of the type that describes client application forms.</td><td><ul><li><span class="term">ManagedForm.</span></li></ul></td><td><ul><li><span class="term">ClientApplicationForm.</span></li></ul></td></tr><tr title="Версия 8.3.14" class="compat tag_0 tag_1"><td><a name="99c7d942-a784-11e8-a3f7-0050569f678a"></a>Spreadsheet document form field extension handler that is called upon an area selection in a spreadsheet document or an action in a chart.<p> In 8.3.13 version compatibility mode, the renaming is ignored.</p><p>We recommend that you analyze your applications and rename handlers of this type.</p></td><td><ul><li> <span class="term">OnActivateArea().</span></li></ul></td><td><ul><li> <span class="term">OnActivate().</span></li></ul></td></tr><tr title="Версия 8.3.14" class="tag_0"><td><a name="63afaedb-f482-11e8-a3f7-0050569f678a"></a>Columns on <span class="interface">Data composition </span>tab, Query wizard.</td><td><span class="interface">Use subordinate fields</span></td><td><span class="interface">Use attributes</span></td></tr></table><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbf7-9a30-11e8-a3f7-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.14" class="tag_30 tag_20"><td><a name="1ad37c0a-ac4b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New feature for the mobile platform: report generation based on the data composition system (including data composition system settings dialog boxes).<p>New configuration properties for mobile applications:<span class="interface"> Default report form</span>, <span class="interface">Default report settings form</span>, and<span class="interface"> Default report option form</span>.</p><p>Upgrade: data composition system settings forms are adjusted for mobile devices.</p></td><td>This feature was not provided.<p>The mobile platform did not support reports. The data composition system supported only preprogrammed reports without user interaction.</p></td><td>The mobile platform supports reports, including user interaction (users can customize reports).</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_31 tag_32"><td><a name="a19ebff8-ac64-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Upgrade: you can turn off some advertising features when building a mobile application. To turn off the features, clear the <span class="term">Ads </span>check box in the mobile application permissions.</td><td>This feature was not provided.</td><td>Publishing mobile applications in app stores is more convenient.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_31"><td><a name="1490d9ee-ac66-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New objects available in the mobile version of 1C:Enterprise: <span class="term">FontChooseDialog </span>and <span class="term">ColorChooseDialog</span>.</td><td>These objects were not provided in the mobile version of 1C:Enterprise.</td><td>Advanced color and font features in the mobile version of 1C:Enterprise.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_32"><td><a name="9725df09-acf7-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Upgrade: faster creation of an infobase at the first start of a mobile application. The upgrade is valid only if the mobile application has been built by exporting (file <span class="interface">1cema.zip</span>) from Designer v. 8.3.14.<p>New format of exporting configurations from Designer. Export to an .xml file is no longer supported.</p><p>Mobile application builder versions 2.0.8 and earlier do not support configurations exported in the new format.
</p></td><td>Creation of an infobase at the first start of a mobile application took more time.</td><td>Faster creation of an infobase at the first start of a mobile application.</td></tr><tr title="Версия 8.3.14" class="tag_48 tag_30"><td><a name="e731319e-acf9-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>New feature for Windows-based mobile applications: support of in-app purchase service (Windows InAppPurchase).<p>New property: I<span class="term">nAppPurchaseService.WindowsInAppPurchase.</span> New feature for the <span class="term">InAppPurchaseReceipt </span>object: a constructor.
</p></td><td>Only iOS and Android-based mobile applications supported in-app purchase services. </td><td>Windows-based mobile applications support in-app purchase services.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_31 tag_48"><td><a name="0e54645a-ad03-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>New feature: integrate rewarded video ads.<p>New feature: get rewarded video ad status.</p><p>New methods for the <span class="term">AdRepresentationManager </span>object: <span class="term">GetAdStatus()</span>, <span class="term">SetRewardedVideoID()</span>, <span class="term">GetRewardedVideoID()</span>, <span class="term">ShowRewardedVideo()</span>, <span class="term">StartRewardedVideoDownloading()</span>, <span class="term">StartAdBannerDownloading()</span>, and <span class="term">StartRewardedVideoDownloading()</span>.</p></td><td>This feature was not provided.</td><td>Advanced advertising features for mobile applications.</td></tr><tr title="Версия 8.3.14" class="tag_64"><td><a name="075394dd-d844-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New mobile platform feature: custom styles and style elements. The feature is available for configurations imported from 1C:Enterprise platform version 8.3.14 and later.<p>Mobile application color scheme ignores the <span class="term">NavigationColor</span>, <span class="term">AuxiliaryNavigationColor</span>, and <span class="term">ImportantColor </span>style properties.</p></td><td>This feature was not provided.</td><td>New options for mobile application appearance management.
</td></tr></table><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbf8-9a30-11e8-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.14" class="tag_0"><a name="1413ab94-85d1-11e9-8371-0050569f678a"></a>Changes were made to cURL library to remediate vulnerabilities.</li></ul><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbf9-9a30-11e8-a3f7-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.14" class="tag_0"><a name="31cd2860-d82f-11e8-a3f7-0050569f678a"></a>Upgrade: new sales invoice printing functionality that can demonstrate the <span class="term">GetStringDeclensionsByNumber</span><span class="term">()</span> function features.</li><li title="Версия 8.3.14" class="tag_0"><a name="8a926a35-d82f-11e8-a3f7-0050569f678a"></a>New feature: collaboration system file and picture management demonstration. It includes new attachment context menu commands: <span class="interface">Set as product picture </span>(if the attachment is a picture) and <span class="interface">Add file to product profile</span>.</li><li title="Версия 8.3.14" class="tag_0"><a name="a8aba070-d82f-11e8-a3f7-0050569f678a"></a>The <span class="interface">price list </span>report contains demonstration of picture operations in the data composition system.<p>
</p></li><li title="Версия 8.3.14" class="tag_0"><a name="f2561dcb-3c35-11e9-b692-0050569f678a"></a>Implemented demo configuration containing different examples of chart operations. You can find the demo configuration on the ITS disk <a href="https://its.1c.ru/db/metod8dev#content:5952:hdoc" target="_blank">Read more</a>..</li></ul><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbfa-9a30-11e8-a3f7-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.14" class="tag_45"><td><a name="cc3e1833-ebe3-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Clarified the error message that appears during an attempt to create a temporary table if the specified temporary table manager has already been closed. The new error text is <span class="interface">Cannot use a closed temporary table manager</span>.</td><td>The error message that appeared at an attempt to create a temporary table if the specified temporary table manager had already been closed might mislead users. The error text was <span class="interface">Temporary table manager is not set</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_25"><td><a name="3ec8955c-ebe4-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When the data composition system template generator outputs fields to chart grouping templates, it applies conditional appearance to all of the fields. As a result, in reports based on data composition schemas the conditional appearance applied to resource fields is also applied to charts.<p>This might change the look of reports containing charts with resources that have conditional appearance.</p></td><td>When the data composition system template generator output fields to chart grouping templates, it applied conditional appearance only to nonresource fields.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_25"><td><a name="0bb124c9-ebef-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a report is displayed in compact mode, reports opened using the Drill down command are also displayed in compact mode.<p>A setting that shows whether the result is displayed in compact mode is available. The name of the setting key is client application-specific.</p><p>New report form parameter: <span class="term">ResultViewMode</span>. Use it to explicitly specify the report view mode.</p><p>New method: <span class="term">GetRecommendedCompactWidth()</span>. It returns spreadsheet document cell width. The <span class="term">ConvertToCompactMode()</span> method of spreadsheet document takes its return value as a parameter.</p></td><td>Reports opened using the Drill down command did not inherit the main report mode (compact or normal).</td><td>Reports opened in the client application using the Drill down command inherit the main report mode.</td></tr><tr title="Версия 8.3.14" class="tag_18 tag_14 tag_10"><td><a name="a14f1cce-f157-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New feature: distribution packages for the thin client running on macOS.<p>New feature: users can select the version and type of client applications running on macOS.</p><p>New feature: uninstall wizard for client applications.</p><p>New directory tree in macOS <span class="interface">Applications </span>directory.</p><p>New directories for some 1C:Enterprise application files.</p><p>New feature: you can create self-extracting installers (DMG images) for client applications. The archive can contain <span class="interface">1cestart.cfg </span>configuration file that contains setup, runtime, and update settings. The executable files support macOS only. New utility: <span class="interface">1CEClientSetupMake</span>.</p></td><td>Self-extracting installers for macOS were not provided. Users could not select client application version. Users could select client application type only within one version.<p>File tree in <span class="interface">Application </span>directory was different.</p><p><span class="interface">1CEClientSetupMake </span>utility was not provided.</p></td><td>Administration of client applications on macOS is more convenient.</td></tr><tr title="Версия 8.3.14" class="tag_18 tag_14 tag_10"><td><a name="bb6ae125-f15c-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New feature: client applications on macOS can be updated over the network. New field in the dialog window for publishing applications on web server where you can specify the path to the client application distribution package. Fields that contain paths to the client application on Windows renamed according to the bitness.<p>New <span class="interface">conf.cfg </span>configuration file parameters: <span class="term">PublishDistributiveLocationMacOS64</span>, <span class="term">PublishDistributiveLocationWindows32</span>, and <span class="term">PublishDistributiveLocationWindows64</span>. The <span class="interface">conf.cfg </span>configuration file parameters <span class="term">PublishDistributiveLocation32 </span>and <span class="term">PublishDistributiveLocation64 </span>are obsolete.</p><p>New attributes for &lt;<span class="term">point</span>&gt; item of<span class="interface"> default.vrd </span>configuration file: <span class="term">pubdstmac64</span>, <span class="term">pubdstwin32</span>, and <span class="term">pubdstwin64</span>. The attributes for &lt;<span class="term">point</span>&gt; item of<span class="interface"> default.vrd </span>configuration file <span class="term">pubdst</span>, <span class="term">pubdst32</span>, and <span class="term">pubdst64 </span>are obsolete.</p><p>New feature: 1C:Enterprise on macOS supports launchers stored on network drives.</p><p>Upgrade: the web service that receives client application distribution packages supports macOS.</p></td><td>These features were not provided.</td><td>Client application update is more convenient.</td></tr><tr title="Версия 8.3.14" class="tag_6 tag_47"><td><a name="01acafca-f15f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 47); return false;">Standalone server</a>.<br></td><td>New parameters for the standalone server configuration file that define path to client application distribution package on Windows and macOS: <span class="term">win32</span>, <span class="term">win64</span>, and <span class="term">mac64</span>. The parameters <span class="term">x86 </span>and <span class="term">x86</span><span class="term">_</span><span class="term">64 </span>are obsolete.</td><td>The standalone server configuration file supported only Windows operating system.</td><td>The standalone server configuration file supports macOS operating system.</td></tr><tr title="Версия 8.3.14" class="compat tag_56 tag_1"><td><a name="7efa656e-f160-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>Upgrade: the result of a spreadsheet document serialization does not depend on whether the document was transferred between a client and a server. The resulting document always has the same structure.<p>The upgrade does not affect the appearance of spreadsheet documents and usage of 1C:Enterprise language to manage them.</p><p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>The result of a spreadsheet document serialization depended on whether the document had been transferred between a client and a server. The resulting documents could have different structures.</td><td>Comparison of spreadsheet documents serialized to XML documents is more convenient.</td></tr><tr title="Версия 8.3.14" class="tag_31 tag_4"><td><a name="435ee693-f166-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New feature: the mobile client supports file transfer over the collaboration system.</td><td>This feature was not provided.</td><td>New collaboration system features for the mobile client.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_32"><td><a name="a14c2274-f168-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>New configuration export format for the Mobile application builder. The format is supported by the Mobile application builder version 2.0.9 or later. Version 2.0.8 and earlier do not support new format.<p>Upgrade: faster initial start of mobile applications built with Designer version 8.3.14.</p></td><td>These features were not provided.<p>The initial mobile application start took more time.</p></td><td>Faster initial start of mobile applications exported in new format.</td></tr><tr title="Версия 8.3.14" class="tag_32"><td><a name="195d87dd-f169-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>New feature: you can specify the default application presentation in multiple languages for mobile applications that contain multiple configurations. The default presentation is automatically applied to all new versions of this mobile application.</td><td>Each new version of a mobile application that contained multiple configurations was based on the first configuration added to the build. Developers had to change the presentation manually.</td><td>Developing mobile applications that contain multiple configurations is more convenient.</td></tr><tr title="Версия 8.3.14" class="tag_26 tag_15 tag_6"><td><a name="f7255540-f3a8-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Upgrade: 1C:Enterprise server clusters running on Linux process spreadsheet documents faster.</td><td>1C:Enterprise server clusters running on Linux took more time to process spreadsheet documents.</td><td>Improved performance of 1C:Enterprise server clusters running on Linux in processing spreadsheet documents.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="b86bec70-f3db-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Upgrade: for PostgreSQL DBMS on Windows, the limitation of 1,200 simultaneously open files per PostgreSQL process is removed (the <span class="term">max_files_per_process</span> DBMS parameter).</td><td>For PostgreSQL on Windows, the limitation of 1,200 simultaneously open files per PostgreSQL process was applied.</td><td>Improved PostgreSQL DMBS performance with large-size configurations, such as 1C:ERP.</td></tr><tr title="Версия 8.3.14" class="tag_27"><td><a name="d796727c-fc7d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>Upgrade: when exporting a configuration to files with 1C:Enterprise version 8.3.14 or later (export format 2.8 or later), the name of the spreadsheet document form field extension event that is called upon selection a spreadsheet document area or upon any operation with the chart is <span class="term">OnActivate </span>regardless of the compatibility mode.<p>When exporting a configuration to files in export format 2.8 or earlier, the even name <span class="term">OnActivate </span>is equivalent to the event name <span class="term">OnActivateArea</span>.</p></td><td>The name of the spreadsheet document form field extension event that was called upon selection a spreadsheet document area or upon any operation with the chart depended on the compatibility mode.</td><td>The form item event name does not depend on the compatibility mode.
</td></tr><tr title="Версия 8.3.14" class="tag_43"><td><a name="48bea104-fc83-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Upgrade: in the thin client, users can perform search in a dynamic list composite column <span class="interface">by part of the string </span>and <span class="interface">by the substring</span>.</td><td>In the thin client, users could not perform search in a dynamic list composite column<span class="interface"> by part of the string </span>and<span class="interface"> by the substring</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_32"><td><a name="bf88ea2d-ff7a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Upgrade: the Mobile application builder defines the amount of RAM the Java process requires to build Android mobile applications more precisely.<p>If you use a 32-bit Java version to build an application in a 64-bit environment, a log record that suggests to specify the 64-bit Java in the Mobile application builder settings is created.</p></td><td>In some cases, the Mobile application builder defined incorrect amount of RAM the Java process required to build Android mobile applications. This could lead to build errors due to insufficient memory.<p>If you used a 32-bit Java version to build an application in a 64-bit environment, a log record that suggests to specify the 64-bit Java in the Mobile application builder settings was not created.</p></td><td>Fixed some bugs that caused insufficient memory errors during Android application building.</td></tr><tr title="Версия 8.3.14" class="compat tag_115 tag_1"><td><a name="414f762b-01d7-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Upgrade: for the <span class="interface">Taxi </span>interface on the thin and thick client, if a form field is in the list selection mode, <span class="term">StartChoice </span>event handler ignores standard processing, and the choice list is empty, the drop-down list is always collapsed. The upgrade is ignored in the web client.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>For the <span class="interface">Taxi </span>interface in the thin and thick client, if a form field was in the list selection mode, <span class="term">StartChoice </span>event handler ignored standard processing, and the choice list was empty, the drop-down list was expanded and filled with the choice list values.<p>In the web client, under the same conditions, the list was always collapsed.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_38 tag_1"><td><a name="011ab1b3-01e9-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>New configuration extension property: <span class="term">DefaultRoles</span>. With this property, you can specify the roles that define accessibility of extension objects when the user list is empty.<p>New configuration extension property: <span class="term">ForceDefaultRolesForAllUsers</span>. With this property, you can assign all users in an attached extension with the rights defined by the extension default roles. You can edit the property in Designer (extension list) or with the standard extension management function.</p><p>When you manage user access rights in Designer, the full name of the role added by an extension is displayed.</p><p>When an extension is created, a special role that grants access rights to all objects of the extension is created automatically. DefaultRoles property value is set to this role. You can edit the role without any limitations.</p><p>If an extension is attached to a file database in safe mode, access rights to extended configuration objects cannot be granted. This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>Developers could not specify default role lists for configuration extensions.<p>When developers managed user access rights in Designer, the full name of the role added by an extension was unavailable.</p><p>When an extension was created, a special role that granted access rights to all objects of the extension was not created.</p><p>If an extension was attached to a file database in safe mode, access rights to extended configuration objects could be granted.</p></td><td>Сonfiguration extension access right management is more convenient.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_31 tag_48 tag_32"><td><a name="0e5b9fb4-01ee-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>New push notification service that supports Windows Push Notification Services (WNS) and Firebase Cloud Messaging (FCM).<p>The Mobile application builder supports new push notification options.</p></td><td>This feature was not provided.<p>The notification service supported only Google Cloud Messaging (GCM) and Apple Push Notification Service (APNs).</p></td><td>The notification service is now compliant to the mobile version of 1C:Enterprise.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_31"><td><a name="d820d833-01ef-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New features: the mobile version of 1C:Enterprise supports groups for pop-up forms and forms with <span class="term">United </span>property set to <span class="term">False</span>.</td><td>These features were not provided.
</td><td>Form management in the mobile version of 1C:Enterprise is more flexible.</td></tr><tr title="Версия 8.3.14" class="compat tag_45 tag_1"><td><a name="7d46230a-1406-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Upgrade: the query language <span class="term">ValueType()</span> function applied to an expression that contains the <span class="term">IsFolder </span>field returns the correct value.<p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>The query language <span class="term">ValueType()</span> function applied to an expression that contained the <span class="term">IsFolder </span>field returned an incorrect value. Result was calculated as if the IsFolder field value contained an inverted value.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="compat tag_45 tag_1"><td><a name="2606e06f-1408-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Upgrade: if a parameter expression of the query language <span class="term">ValueType()</span> function contains a virtual field and a primitive type value, the function returns a correct value.<p>This upgrade is ignored in 8.3.13 version compatibility mode. </p></td><td>If a parameter expression of the query language <span class="term">ValueType()</span> function contained a virtual field and a primitive type value, the function returned an incorrect value.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_4"><td><a name="e9151c5d-1411-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Upgrade: user search in the collaboration system is performed only by the beginning of words.<p>The search algorithm for headings of noncontext group conversations and participant lists of one-to-on conversations is improved. Conversations in search results are ranked higher if they have:</p><ul><li>Recent messages (the message date is concerned).</li><li>The search string is at the beginning of the word.</li></ul></td><td>User search in the collaboration system used the string-matching algorithm.<p>Search result was ranked in the same order order the conversations had been found in the database.</p></td><td>The search algorithm in the collaboration system is improved.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_31 tag_32 tag_29"><td><a name="f670144e-1f1d-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Windows 8.1 and Windows Phone 8.1 operating systems are no longer supported by 1C:Enterprise mobile platform.<p>New: Windows 10 operating system is supported for ARM architecture.</p><p>Upgrade: components of a distribution package of 1C:Enterprise mobile platform is changed (<span class="interface">mobile.zip </span>file).</p><p>Mobile application builder can no longer build mobile applications for Windows 8.1 and Windows Phone 8.1 using 1C:Enterprise mobile platform 8.3.14 and later.</p></td><td>1C:Enterprise mobile platform supported Windows 8.1 and Windows Phone 8.1.<p>1C:Enterprise mobile platform did not support Windows 10 for ARM architecture.</p></td><td>A list of supported Windows versions is updated.</td></tr><tr title="Версия 8.3.14" class="tag_6"><td><a name="faec98bf-1804-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New property <span class="term">AdministrationClusterManager.ClusterManagerID</span>.</td><td>This feature was not provided.</td><td>Now you can unambiguously identify a cluster manager upon using the <span class="term">ServerAdministration </span>object.</td></tr><tr title="Версия 8.3.14" class="compat tag_25 tag_1"><td><a name="c2e40243-2915-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Upon adding a filter to query of composition schema data set that includes unions, the filter is necessarily added to every part of the union if automatic filling of available fields is enabled for the data set or the field, to which the filter is applied, is accessed via the point from the field available for filtering.<p>Besides, if the filter item group contained a field that was not available in one of unions and another field that was available, and if all fields were available in another part of the union, the filter would be applied to the part where it was unavailable, and all unavailable fields would be replaced by <span class="term">NULL</span>.</p><p>If a query with unions is used in a report or a dynamic list, and it is required that filter for a particular field is included only in certain union parts, it is recommend that you disable automatic filling of available fields for the data set and add the required field only to the union parts you need.</p><p>This upgrade is ignored in 8.3.13 version compatibility mode.</p></td><td>Whenever a filter was added to a query of composition schema data set that included unions, this filter was necessarily added to every part of the union if it could be included at least in one part of the union. In union parts, in which the filter could not be used as fields used in the filter were missing, these fields were replaced by <span class="term">NULL </span>in conditions being added.<p>Besides, if a filter item group contained a field, which was unavailable in one of the unions, and another field, which was available, and all fields were available in another part of the union, then such filter was applied outside query, on the level of data set of a data composition template.</p></td><td>Now you can create reports, which use queries with unions and in which the filter by some fields can be applied not to all queries inside the union.</td></tr><tr title="Версия 8.3.14" class="tag_22 tag_45"><td><a name="80f610ca-3c35-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>New feature: now Data accelerator supports queries containing the IN HIERARCHY expression.</td><td>Data accelerator did not support queries containing the IN HIERARCHY expression.
</td><td>Advanced features of Data accelerator.</td></tr><tr title="Версия 8.3.14" class="compat tag_79 tag_1"><td><a name="62ed602f-495c-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>The <span class="term">ColorDepth </span>system enumeration is available in Russian in <span class="interface">Version 8.3.14</span><span class="interface"> </span>or later compatibility mode only.<p>In <span class="interface">V</span><span class="interface">ersion 8.3.13</span> or earlier compatibility mode, this enumeration is available only in the English <span class="term">ColorDepth </span>option.</p></td><td>The ColorDepth system enumeration was available in Russian in any compatibility mode.</td><td>Resolved the conflict between platform IDs and names of variables of released applications.</td></tr><tr title="Версия 8.3.14" class="tag_32"><td><a name="052cbcb8-495d-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Full number of a mobile application built by the Mobile application builder and designed for Windows always has "0" as a last digit in the full application version number.</td><td>Full number of a mobile application built by the Mobile application builder and designed for Windows had the current build number, which was unique within one mobile application, as a last digit in the full application version number.</td><td>Now the Mobile application builder meets Windows Store requirements for the version number of a mobile application being published.</td></tr><tr title="Версия 8.3.14" class="tag_32 tag_31"><td><a name="2120f9c2-495e-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Now you can specify the following upon setting up a mobile client application builder:<ul><li>Server certificate validation method.</li><li>Сertificate used for server authentication.</li><li>Сertificate used for client identification.</li></ul><p>You can use the specified features if the address of an infobase or a web service with a shared infobase list starts with the "https://" prefix. Otherwise, certificate operations are not available.</p></td><td>This feature was not provided.</td><td>Now you can use the mobile client if accessing an infobase requires secure connection and placing the required certificates on end-user mobile devices is not available.</td></tr><tr title="Версия 8.3.14" class="tag_56"><td><a name="6d3c013c-5602-11e9-84bd-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>New feature: the platform supports XSD schemas containing types, in which attributes are defined via references to global attributes, but overriding such properties as <span class="term">default </span>or <span class="term">fixed </span>ones.</td><td>Upon trying to use in the platform XSD schemas containing types, in which attributes were defined via references to global attributes, but overriding such properties as <span class="term">default </span>or <span class="term">fixed </span>ones, errors occurred when checking the XDTO model, and such schemas were not available.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.14" class="tag_22 tag_45"><td><a name="0547e1e2-5788-11e9-84bd-0050569f678a"></a><a href="#" onclick="onTagClick(this, 22); return false;">Data accelerator</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>New feature: now Data accelerator supports queries using tabular sections and the <span class="term">RECORDAUTONUMBER</span><span class="term">()</span> query language function.</td><td>Data accelerator did not support queries using tabular sections and the <span class="term">RECORDAUTONUMBER()</span> query language function.</td><td>Advanced features of Data accelerator.</td></tr><tr title="Версия 8.3.14" class="tag_84"><td><a name="6bc1c03a-60f1-11e9-84bd-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Localized client application interface for Italian (<span class="interface">it</span>).</td><td>This feature was not provided.</td><td>1C:Enterprise is available to Italian-speaking users.</td></tr><tr title="Версия 8.3.14" class="tag_96"><td><a name="44033cb4-85d3-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>New feature: search bar is available in the <span class="interface">All functions</span> dialog box. Search begins when you try to type a search expression in the сonfiguration object tree. The whole list of objects in the dialog box is searched, regardless of whether the branches of the сonfiguration object tree are expanded or not. You can enter several search words in the search bar. In this case, the search will be done using all entered words of the search query. You can also access the search bar by pressing <span class="interface">Ctrl+F</span>.<p>To search using the standard dialog box, press <span class="interface">Alt+F</span>. Only expanded branches of the сonfiguration object tree are searched.</p></td><td>Search in the <span class="interface">All functions</span> dialog box was available only using the standard search dialog box, which searched only expanded branches of the сonfiguration object tree. This dialog box was accessible by pressing <span class="interface">Ctrl+F</span>. In the <span class="interface">All functions</span> dialog box, search by several words was not available.
</td><td>The search in the <span class="interface">All functions</span> dialog box is much easier now.
</td></tr><tr title="Версия 8.3.14" class="tag_116"><td><a name="fc066dd1-98cd-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>Security profiles are not technically blocked in 1C:Enterprise when a PROF license is used. To use security profiles, the user must still have a CORP license.</td><td>Security profiles were technically blocked in 1C:Enterprise when a PROF license was used.</td><td>Changed functions in CORP licenses, whose availability is checked technically.</td></tr><tr title="Версия 8.3.14" class="tag_29 tag_19"><td><a name="ab858d91-98ce-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 9.6.6 from AstraLinux Special Edition 1.6 is supported now if the en_US.UTF8 locale is set up in this operating system.</td><td>PostgreSQL 9.6.6 from AstraLinux Special Edition 1.6 was not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.14" class="tag_31"><td><a name="d97bbc38-9bec-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Collaboration system push notifications are sent to a mobile device using Firebase Cloud Messaging.</td><td>Collaboration system push notifications were sent to a mobile device using Google Cloud Messaging.</td><td>Outdated technology of push notification delivery in the collaboration system is no longer used. Upgrade: faster delivery of push notifications from the collaboration system to client mobile devices.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_31"><td><a name="63062f38-9bed-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>If case of unexpected shutdown of the mobile application, you will be taken to the application list.</td><td>If case of unexpected shutdown of the mobile application, the mobile application itself was shut down. As a result, it was impossible to restore an infobase from a backup (when using a mobile platform) or change connection settings (when using a mobile client).</td><td>Improved behavior of the mobile application in case of unexpected shutdown.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_31 tag_123"><td><a name="708e4b9a-cd6b-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 123); return false;">Mobile Application Builder</a>.<br></td><td>1C:Enterprise mobile platform now supports 1244x2208 and 2208x1244 splash screens when running Android OS.<p>Splash screen support of this size is now included in Mobile Application Builder.</p></td><td>1C:Enterprise mobile platform did not support 1244x2208 and 2208x1244 splash screens when running Android OS.<p>Mobile Application Builder did not support this size for splash screen.</p></td><td>Implemented splash screen support for high-resolution screens when running Android OS.
</td></tr><tr title="Версия 8.3.14" class="tag_20 tag_30 tag_31"><td><a name="c971c53a-cd6f-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>You can now create a configuration file of the mobile platform in zip format only. You can no longer create an xml configuration file. The change relates to exporting with both the Designer interactive mode and the Designer command line (<span class="term">/MobileAppWriteFile</span> option).</td><td>The configuration file of the mobile platform could have zip or xml format.</td><td>Configuration export format for the 1C:Enterprise mobile platform has changed.
</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="9b2511fa-e4fd-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 10.8 is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="b4cecf6a-e4fd-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 10.9 is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="e08beb02-fbef-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 10.10 is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_10 tag_116"><td><a name="85a94066-e9d5-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>The <span class="interface">1C:Enterprise licensing utility</span> distribution package includes the following utilities versions:<ul><li><span class="interface">Ring </span>command line utility - version 0.17.0+1.</li><li><span class="interface">License </span>module - version 0.12.0+3.</li><li>1C:Enterprise installer - version 1.6.0+4.
</li></ul></td><td>The <span class="interface">1C:Enterprise licensing utility</span> distribution package included the previous versions of utilities.</td><td>Minor errors and typos fixed.</td></tr><tr title="Версия 8.3.14" class="tag_30 tag_33"><td><a name="4e7d0c80-ea67-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>The documentation describes the directory structure created when publishing a mobile application on a web server with Designer. It also describes the MIME types that the web server must support to be capable of hosting mobile application configurations and application debugging.</td><td>The documentation did not contain information about data located on the web server after publishing the mobile application with Designer.</td><td>Updated platform documentation.</td></tr><tr title="Версия 8.3.14" class="tag_4"><td><a name="9f5d0aec-f95f-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented the <span class="term">CollaborationSystemAttachment.ContentRemoved</span> property to display the fact of deleting the attachment from the 1C:Enterprise file storage.<p>Updated the messages displayed when transferring the file with the collaboration system failed.</p></td><td>There was no way to detect from the 1C:Enterprise language that the attachment was removed from the collaboration system file storage.</td><td>You can now detect that the attachment was removed from the collaboration system file storage.</td></tr><tr title="Версия 8.3.14" class="tag_4"><td><a name="3c2ec464-f95e-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>If the 1C:Dialog service is used to operate the collaboration system, the file transfer has the following limitations: <a href="https://1cdialog.com/ru/pricing/" target="_blank">Read more</a>.</td><td>Conditions of storing files in the 1C:Dialog service were not defined.</td><td>Conditions of storing files in the 1C:Dialog service are now defined.</td></tr><tr title="Версия 8.3.14" class="tag_19 tag_29"><td><a name="8734cfae-faed-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The server cluster can only interact with Oracle Database DBMS provided that Instant Client 10.2.0.5 is installed on the cluster computer.<p>Oracle Database client libraries were excluded from 1C:Enterprise distribution package.</p></td><td>Oracle Database client libraries were included in 1C:Enterprise distribution package.<p>The server cluster was able to interact with Oracle Database DBMS with no additional software required.</p></td><td>The 1C:Enterprise distribution package content was changed.<p>
</p></td></tr><tr title="Версия 8.3.14" class="tag_29 tag_30 tag_31"><td><a name="edcbb5b0-382c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Android version 4.0 is no longer supported.
</td><td>Android version 4.0 was supported.
</td><td>Ended support for legacy Android versions.
</td></tr><tr title="Версия 8.3.14" class="tag_19 tag_29"><td><a name="29401fcb-3b8d-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>PostgreSQL DBMS 11.5 (x86-64) is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_32"><td><a name="43892bc6-4731-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>The mobile application builder supports Firebase Cloud Messaging push notifications (FCM, for Android) and Windows Push Notification Services (WNS, for Windows) when working through 1C:Enterprise secondary service (<a href="https://pushnotifications.1c.com" target="_blank">https://pushnotifications.1c.com</a>).
Google Cloud Messaging service for sending push notifications (GCM, for Android) is disabled when using the 1C:Enterprise secondary service (<a href="https://pushnotifications.1c.com" target="_blank">https://pushnotifications.1c.com</a>) with the mobile application builder.
</td><td>When using the 1C:Enterprise secondary service (<a href="https://pushnotifications.1c.com" target="_blank">https://pushnotifications.1c.com</a>) with the mobile applications builder, the Apple Push Notification Service (APNs, for iOS) and Google Cloud Messaging (GCM, for Android) were actually available.
</td><td>When using the 1C:Enterprise secondary service (<a href="https://pushnotifications.1c.com" target="_blank">https://pushnotifications.1c.com</a>) from the mobile applications builder, the builder actually supports the features of the service.
</td></tr><tr title="Версия 8.3.14" class="tag_20 tag_18"><td><a name="dfbe9968-685e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br></td><td>The HASP key driver distribution package has been excluded from the client applications distribution package for macOS. To install the security key driver, you will need to download it from Gemalto website first.</td><td>The client applications distribution package for macOS included the HASP key driver distribution package.</td><td>Compliance with Apple requirements is now available. Creating the 1C:Enterprise distribution package, which can be installed on macOS version 10.15 and later, is not available without such compliance.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="5e58f05a-9906-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 10.12 is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="d495bcda-9906-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 11,7 is now supported.<p>
</p></td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_29 tag_124"><td><a name="7b826e42-b6b7-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 124); return false;">Administration</a>.<br></td><td>1C:Enterprise distribution packages for Windows and macOS include HASP Device Driver 7.92.</td><td>1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 7.63.</td><td>1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver.</td></tr><tr title="Версия 8.3.14" class="tag_96"><td><a name="ad47cf00-c02e-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The <span class="interface">About...</span> window includes the hyperlink <span class="interface">Add-in licenses</span>, which opens the list of the third-party add-ins used in 1C:Enterprise.</td><td>The <span class="interface">About...</span> window didn't provide the information about the third-party add-ins used in 1C:Enterprise.</td><td>Conformity with GNU LGPL v2.1.</td></tr><tr title="Версия 8.3.14" class="tag_29 tag_19"><td><a name="0f02bfba-12d7-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):<ul><li>Postgres Pro 1C 9.6.18.1,</li><li>Postgres Pro 1C 10.13.1,</li><li>Postgres Pro 1C 11.8.1,</li><li>Postgres Pro Standard 9.6.18.1,</li><li>Postgres Pro Standard 10.13.1,</li><li>Postgres Pro Standard 11.8.1,</li><li>Postgres Pro Enterprise 9.6.18.1,</li><li>Postgres Pro Enterprise 10.13.1,</li><li>Postgres Pro Enterprise 11.8.1.</li></ul></td><td>The following Postgres Pro DBMS versions were not supported:<ul><li>Postgres Pro 1C 9.6.18.1,</li><li>Postgres Pro 1C 10.13.1,</li><li>Postgres Pro 1C 11.8.1,</li><li>Postgres Pro Standard 9.6.18.1,</li><li>Postgres Pro Standard 10.13.1,</li><li>Postgres Pro Standard 11.8.1,</li><li>Postgres Pro Enterprise 9.6.18.1,</li><li>Postgres Pro Enterprise 10.13.1,</li><li>Postgres Pro Enterprise 11.8.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.14" class="tag_29 tag_19"><td><a name="4f16339b-12d7-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):<ul><li>Postgres Pro 1C 9.6.19.1,</li><li>Postgres Pro 1C 10.14.1,</li><li>Postgres Pro 1C 11.9.1,</li><li>Postgres Pro Standard 9.6.19.1,</li><li>Postgres Pro Standard 10.14.1,</li><li>Postgres Pro Standard 11.9.1,</li><li>Postgres Pro Enterprise 9.6.19.1,</li><li>Postgres Pro Enterprise 10.14.1,</li><li>Postgres Pro Enterprise 11.9.1.</li></ul></td><td>The following Postgres Pro DBMS versions were not supported:<ul><li>Postgres Pro 1C 9.6.19.1,</li><li>Postgres Pro 1C 10.14.1,</li><li>Postgres Pro 1C 11.9.1,</li><li>Postgres Pro Standard 9.6.19.1,</li><li>Postgres Pro Standard 10.14.1,</li><li>Postgres Pro Standard 11.9.1,</li><li>Postgres Pro Enterprise 9.6.19.1,</li><li>Postgres Pro Enterprise 10.14.1,</li><li>Postgres Pro Enterprise 11.9.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="66aa3214-12d8-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 10.13 (x86-64) is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="8746514d-12d8-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 11,8 (x86-64) is now supported.<p>
</p></td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="94c44d6e-12d8-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 12,3 (x86-64) is now supported.<p>
</p></td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="48228b3e-12d9-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 10.14 (x86-64) is now supported.</td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="58044bc0-12d9-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 11,9 (x86-64) is now supported.<p>
</p></td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr><tr title="Версия 8.3.14" class="tag_19"><td><a name="643505bd-12d9-11eb-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>PostgreSQL 12,4 (x86-64) is now supported.<p>
</p></td><td>This PostgreSQL DBMS version was not supported.</td><td>More PostgreSQL DBMS versions are now supported.</td></tr></table><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e5c8dbfb-9a30-11e8-a3f7-0050569f678a">Transition from the previous version to the version 8.3.14</a></h2><ul><li title="Версия 8.3.14" class="tag_0"><a name="e5c8dbfc-9a30-11e8-a3f7-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.14.
</li><li title="Версия 8.3.14" class="tag_0"><a name="e5c8dbfd-9a30-11e8-a3f7-0050569f678a"></a>Some features that are added in version 8.3.14 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.14" class="tag_0"><a name="4888fbb2-f3dc-11e8-a3f7-0050569f678a"></a>When you upgrade a PostgreSQL DBMS to PostgreSQL 10.5, we recommend that you reindex database tables. There are two ways to reindex database tables:<ul><li>In Designer, verify and repair the infobase with the <span class="interface">Reindex infobase tables </span>option selected.</li><li>In the DBMS, run the <span class="term">reindex database &lt;database name&gt;</span> command.</li></ul></li></ul><p><a href="#e5c8dbf0-9a30-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h1><a name="199f74c5-0668-11e8-a3f7-0050569f678a">Version 8.3.13</a></h1><p title="Версия 8.3.13" class="tag_0"><a name="199f74d2-0668-11e8-a3f7-0050569f678a"></a>Version 8.3.13 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.13" class="tag_0"><a name="fd5ea6a6-1189-11e8-a3f7-0050569f678a"></a>Finished the beta testing of the Designer agent mode.</p><p title="Версия 8.3.13" class="tag_0"><a name="945cd1ec-d82e-11e8-a3f7-0050569f678a"></a>The local collaboration system server feature graduated from beta. Local collaboration servers require COPR-level client and server licenses.<a href="http://1c.ru/news/info.jsp?id=24993" target="_blank">Read more</a>.</p><hr></hr><ul><li><a href="#199f74c6-0668-11e8-a3f7-0050569f678a">New functionality and changes</a></li><li><a href="#199f74c7-0668-11e8-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#199f74c8-0668-11e8-a3f7-0050569f678a">Optimization</a></li><li><a href="#199f74c9-0668-11e8-a3f7-0050569f678a">Changes that affect system behavior</a></li><li><a href="#199f74ca-0668-11e8-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#199f74cb-0668-11e8-a3f7-0050569f678a">Renamed objects</a></li><li><a href="#199f74cc-0668-11e8-a3f7-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#199f74cd-0668-11e8-a3f7-0050569f678a">Library updates
</a></li><li><a href="#63097281-25f7-11e8-a3f7-0050569f678a">Demo configuration changes</a></li><li><a href="#199f74ce-0668-11e8-a3f7-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#199f74cf-0668-11e8-a3f7-0050569f678a">Transition from the previous version to the version 8.3.13</a></li></ul><h2><a name="199f74c6-0668-11e8-a3f7-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.13" class="compat tag_2 tag_1"><td><a name="bdd9cc69-0678-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.12</span> is now implemented.</td><td>Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.11 was implemented.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.12 or earlier can run on version 8.3.13 without any changes to configuration or to data structures. This allows for transition to version 8.3.13 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.12 after the transition to version 8.3.13, even if you disabled the compatibility mode (if you did, enable it again).</td></tr><tr title="Версия 8.3.13" class="tag_19 tag_29"><td><a name="2716bf65-0679-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>PostgreSQL version 10 is supported.</td><td>PostgreSQL version 10 was not supported.</td><td>The list of supported DBMS is extended.</td></tr><tr title="Версия 8.3.13" class="tag_4"><td><a name="1b1666af-0747-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented 1C:Enterprise. Startup and notifications application. It provides the following features:<ul><li>A single notification center for all client applications (including the web client).</li><li>Displaying notifications from applications that are not running (available for infobases connected to the agent).</li><li>Opening a specific conversation when a client application is started or a client application window is maximized.</li><li>Disabling notifications from a specific infobase.</li><li>Quick access to 1C:Enterprise applications.</li></ul><p>
The application is available for Windows and Linux, and also for Google Chrome, Mozilla Firefox, and Microsoft Internet Explorer. Implemented the option to display the new messages from the collaboration system and the notification center when starting a client application. </p><p>Implemented the DisplayUserNotificationList command-line option of the client application startup in the thin, thick, and web clients.</p></td><td>Notifications from a specific application were displayed on a computer only if the application was running on that computer.</td><td>The collaboration system notifications from a specific application are available even if the application is not running.</td></tr><tr title="Версия 8.3.13" class="tag_28"><td><a name="96cff12e-0805-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client an option to specify the OpenID authentication provider (or the list of providers) is implemented. Each specified provider must support the OpenID Connect protocol.<p>The <span class="term">openidconnect </span>parameter is added to the <span class="interface">default.vrd </span>file.</p><p>Implemented the <span class="term">OidcSelectedProvider </span>command-line option in the web client.</p><p>This feature is not available if the infobase is published from Designer.</p><p>This feature is available in the web client only.</p></td><td>This feature was not provided.<p>Only the 1C:Enterprise infobase could be used as the OpenID authentication provider in the web client.</p></td><td>Expanded the authentication options list in the web client.</td></tr><tr title="Версия 8.3.13" class="tag_51"><td><a name="cca8076b-0809-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>For <span class="term">TestedFormDecoration </span>and <span class="term">TestedFormField </span>objects, implemented the <span class="term">ClickFormattedStringHyperlink() </span>method. The method emulates clicking a hyperlink in a formatted string.</td><td>This feature was not provided.</td><td>Extended automated testing capabilities.</td></tr><tr title="Версия 8.3.13" class="tag_125 tag_30 tag_31"><td><a name="faf66cdf-0818-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 125); return false;">InterfaceConfiguration extensions</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Implemented the option to create custom styles and style elements.<p>The <span class="term">DefaultStyle </span>configuration property is now available in the managed application.</p><p><span class="interface">Styles</span> and <span class="interface">Style elements</span> are now available in the <span class="interface">Common </span>metadata tree branch.</p><p>Implemented the following system colors: </p><ul><li><span class="term">NavigationColor</span></li><li><span class="term">AuxiliaryNavigationColor</span></li><li><span class="term">ActivityColor</span></li><li><span class="term">ImportantColor</span></li><li><span class="term">AccentColor</span></li></ul><p>In version 8.3.12 compatibility mode, style elements of <span class="term">Color </span>and <span class="term">Font </span>type that are included in a style retain their values, provided that the style was not used in the ordinary application and the values of those style elements were not changed.</p><p>The color of several interface items was slightly changed.</p><p>In configuration extensions, you can create and adopt styles and style elements. Configuration extensions can override the <span class="term">DefaultStyle </span>property.</p></td><td>This feature was not provided.</td><td>New options for client application appearance management.</td></tr><tr title="Версия 8.3.13" class="tag_14"><td><a name="c8800f4b-0819-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The application startup splash can be disabled now. Implemented the <span class="term">DisableSplash </span>command-line option. It is available in the thin, thick and web client.</td><td>This feature was not provided.<p>The application startup splash could not be disabled.
</p></td><td>Extended capabilities for 1C:Enterprise integration with third-party systems.</td></tr><tr title="Версия 8.3.13" class="tag_38"><td><a name="c771b44d-081a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The following objects can now be created in the configuration extension:<ul><li>chart of characteristic types</li><li>chart of accounts</li><li>chart of calculation types</li><li>accumulation register</li><li>accounting register</li><li>calculation register</li></ul><p>Configuration extension native accumulation registers do not support aggregates.</p><p>The records of native and adopted configuration extension documents can now include the configuration extension native registers.</p></td><td>This feature was not provided.</td><td> Extended configuration extension usage options.</td></tr><tr title="Версия 8.3.13" class="tag_64"><td><a name="64432be7-081b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Implemented the text declension feature. Implemented the <span class="term">GetStringDeclensions() </span>global context method.</td><td>This feature was not provided.</td><td>1C:Enterprise is now capable of declining various texts, for example, in reports and documents.</td></tr><tr title="Версия 8.3.13" class="tag_120"><td><a name="6e6da165-081e-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>Implemented the option to wait for the completion of one or several background jobs within the specified period. For <span class="term">BackgroundJob </span>and <span class="term">BackgroundJobsManager </span>objects, implemented <span class="term">WaitForExecutionCompletion</span><span class="term">()</span> method.<p>The <span class="term">WaitForCompletion</span><span class="term">()</span> method is deprecated.</p><p>We recommend that you review your algorithms that involve background jobs.</p><p>The message informing about waiting for the completion of a background job that is missing from the lists of running and completed jobs is more accurate.</p><p>1C:Enterprise can detect situations where the current user that does not have the <span class="term">Administration </span>access right attempts to wait for the completion of a background job started by another user.</p></td><td>This feature was not provided.<p>Waiting for completion of one or several background jobs was available. If the background job completed abnormally, an exception was thrown.</p><p>The message informing about waiting for the completion of a background job that did not exist was not clear.</p></td><td>Simplified waiting for background job completion. Simplified other operations performing while waiting for background job completion.</td></tr><tr title="Версия 8.3.13" class="tag_6"><td><a name="b5a30ffb-0b1f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New feature: evaluation of CPU load in the current session. The following time spans are available:<ul><li>The current server call</li><li>The last 5 minutes</li><li>The entire session</li></ul><p>New session properties for the <span class="interface">rac </span>utility: <span class="term">cpu-time-current</span>, <span class="term">cpu-time-5min-last</span>, and <span class="term">cpu-time-total</span>. New properties of the <span class="term">ISessionInfo </span>object: <span class="term">cpuTimeCurrent</span>, <span class="term">cpuTimeLast5Min</span>, and <span class="term">cpuTimeAll</span>.</p><p>New property of the <span class="term">&lt;CALL&gt;</span> event: <span class="term">CpuTime</span>. It stores the duration of a completed server call (in milliseconds).</p><p>New feature: developers can create custom resource consumption counters with multiple indicators, such as CPU time, memory usage, and disk I/O data volume.</p><p>The cluster console now supports resource consumption counter management.</p><p>New <span class="interface">rac </span>utility commands:</p><ul><li><span class="term">counter update</span>. Create or edit a resource counter.</li><li><span class="term">counter remove</span>. Delete a resource counter.</li><li><span class="term">counter values</span>. Display the current counter values.</li><li><span class="term">counter list</span>. Display the settings of the selected counter.</li></ul><p>Implemented the option to run the following session management operations upon reaching the specified resource consumption values:</p><ul><li>Terminate both the server call and the session.</li><li>Terminate the server call without terminating the session (if possible).</li><li>Decrease the priority of the server call thread.</li><li>Write the details to the technological log <span class="term">(&lt;ATTN&gt;</span> event).</li></ul><p>You can specify resource consumption limits in the cluster console.</p><p>New <span class="interface">rac </span>utility commands:</p><ul><li><span class="term">limit update</span>. Add a limit.</li><li><span class="term">limit list</span>. Display the list of limits.</li></ul><p>New feature: developers can manage resource consumption with Java interface for 1C:Enterprise server cluster administration (<a href="http://1c-dn.com/library/1c_enterprise_8_administrative_service_api/" target="_blank">read more</a>).
Resource consumption level feature requires CORP license.</p></td><td>These features were not provided.</td><td>You can set the resource load limits on the computer with cluster server. Improved system reliability.</td></tr><tr title="Версия 8.3.13" class="tag_25"><td><a name="30516a19-0b2f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Implemented the <span class="term">DataCompositionUserSettings.GetMainSettingsByUserSettingID() </span>method. This method returns the array of main settings by the user setting ID. It can be used to specify user settings properties that are otherwise read-only.</td><td>This feature was not provided.</td><td>Simplified access to user settings of the data composition system.</td></tr><tr title="Версия 8.3.13" class="tag_26"><td><a name="945610f1-0b4a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Implemented the option to optimize the view of spreadsheet documents that do not fit the screen width (mostly on mobile devices). The optimization eliminates the need for horizontal scrolling.<p>For spreadsheet document, implemented <span class="term">GetCompactDocument()</span> method. It returns the compact version of a spreadsheet document. For spreadsheet document, implemented <span class="term">SetAutoWidth()</span> method. It sets the horizontal stretching mode for spreadsheet document columns.</p><p>For spreadsheet document, implemented <span class="term">ConvertToCompactMode() </span>and <span class="term">RevertToDefaultMode() </span>methods. They respectively create and delete a copy of a spreadsheet document that fits the width of a small screen. When a spreadsheet document is printed or saved, the original non-optimized spreadsheet document is used as a source.</p><p>Implemented the <span class="term">ResultViewMode </span>property of the report managed form field extension. It allows you to manage the report transformation. Implemented the <span class="interface">Compact Mode </span>command of the report managed form field extension. It allows you to edit the <span class="term">ResultViewMode </span>property value.</p><p>The current report view modes for the mobile client and other client applications are separately stored in the system settings storage.</p></td><td>These features were not provided.<p>The spreadsheet document could not be transformed to fit the width of the small screen.</p></td><td>Improved spreadsheet document appearance on a small screen (for example the mobile device screen).</td></tr><tr title="Версия 8.3.13" class="tag_87"><td><a name="788ec9ef-0bf9-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 87); return false;">Metadata objects</a>.<br></td><td>The option to analyze metadata, stored in <span class="interface">.cf </span>or <span class="interface">.cfe </span>file, is implemented. Implemented the <span class="term">ConfigurationMetadataObject </span>constructor.<p>You can now get the configuration name, version, and vendor from the <span class="interface">.cf </span>or <span class="interface">.cfe </span>file. Implemented the <span class="term">ConfigurationDescription </span>object.</p><p>You can now get the list of versions, suitable for the update, and the resulting version number from a .cfu file. Implemented the <span class="term">ConfigurationUpdateDescription </span>object.</p></td><td>This feature was not provided.<p>The information about the configuration or the configuration update was not available.</p></td><td>Simplified development of automated configuration updating and distribution packages creating tools.</td></tr><tr title="Версия 8.3.13" class="tag_38"><td><a name="2759e89d-0bfb-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The following configuration properties can now be adopted: <ul><li>main section picture</li><li>splash</li><li>logo</li></ul><p>You can now adopt the <span class="term">Picture </span>type objects by replacing the current picture.</p><p>The following configuration extension properties can now be specified:</p><ul><li>brief extension information</li><li>detailed extension information</li><li>extension copyright</li><li>vendor information address</li><li>extension information address.</li></ul></td><td>These features were not provided.</td><td> Extended configuration extension usage options.</td></tr><tr title="Версия 8.3.13" class="tag_38 tag_105"><td><a name="9e1bc06b-0c0a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>The extension native exchange plan can now include adopted objects.<p>You can now adopt the exchange plan data (create exchange plan attributes, tabular sections, and tabular section attributes).</p></td><td>The extension native exchange plan could include the extension native objects only.<p>The exchange plan data could not be adopted.</p></td><td>More configuration extension management options.</td></tr><tr title="Версия 8.3.13" class="tag_68"><td><a name="aabd948f-0c0c-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>You can now override default data history forms. Added the following properties of the Configuration object: <ul><li><span class="term">DefaultDataHistoryChangeHistoryForm</span></li><li><span class="term">DefaultDataHistoryDataVersionForm</span></li><li><span class="term">DefaultDataHistoryVersionDifferenceForm</span>.</li></ul><p>
</p><p>Implemented <span class="term">DataHistoryVersionFilterDialog </span>and <span class="term">DataHistoryUsersChooseDialog </span>objects.</p></td><td>Default data history forms overriding was not available.</td><td>Extended data history options.</td></tr><tr title="Версия 8.3.13" class="tag_37"><td><a name="6bd74754-0cc3-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Implemented the following HTML document options:<ul><li>Delete all document items of a certain category. Implemented the<span class="term"> HTMLDocument.DeleteByCategory() </span>method.</li><li>Get a string with all readable text from the document. Implemented the <span class="term">HTMLDocument.ExtractPlainText()</span> method.</li><li>Select all document items by a specific filter. Implemented the <span class="term">HTMLDocument.FindByFilter() </span>method.</li><li>Delete all document items by a specific filter. Implemented the <span class="term">HTMLDocument.DeleteByFilter() </span>method.</li></ul></td><td>These features were not provided.<p>The only available option was to cycle HTML document DOM model and perform actions with its items.</p></td><td>Simplified and improved the HTML document performance in particular scenarios (for example if you want to delete all <span class="term">&lt;script&gt;</span> tags)</td></tr><tr title="Версия 8.3.13" class="tag_37"><td><a name="5788b40c-0cd8-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Emails can now use OAuth2 protocol together with IMAP protocol.<p>Implemented the following <span class="term">InternetMailProfile </span>object properties: <span class="term">TokenAuthentication </span>and <span class="term">AccessToken</span>.</p></td><td>This feature was not provided.</td><td>The email servers with the OAuth2 authentication protocol are now supported.</td></tr><tr title="Версия 8.3.13" class="tag_45"><td><a name="28d343da-0d75-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>A field with consequently increasing unique values can now be added to the temporary table.<p>Implemented the <span class="term">RECORDAUTONUMBER</span><span class="term">()</span> query language function. It is available for a temporary table only.</p><p>The <span class="term">RECORDAUTONUMBER() </span>function is not supported in the following cases:</p><ul><li>there is a <span class="term">UNION </span>keyword on the top level</li><li>query does not create a temporary table</li><li>outside the selection list</li><li>in expressions.</li></ul></td><td>This feature was not provided.</td><td>Simplified adding the unique field with consequently increasing values to a temporary table.</td></tr><tr title="Версия 8.3.13" class="tag_51"><td><a name="d0b22b03-10cb-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>Implemented the following options of the spreadsheet document extension of the <span class="term">TestedFormField </span>object:<ul><li>Getting the number of columns that contain data. Implemented the <span class="term">GetDocumentDataAreaHorizontalSize() </span>method.</li><li>Getting the number of rows that contain data. Implemented the <span class="term">GetDocumentDataAreaVerticalSize() </span>method.</li></ul></td><td>These features were not provided.</td><td>Extended automated testing capabilities.</td></tr><tr title="Версия 8.3.13" class="tag_68"><td><a name="7cc5b83c-116d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>The option to handle the data version restoration in the object module and in the managed form module is now available.<p>If a form displays one of the older object version, the version number is displayed in the form header.</p><p>Implemented a dynamic list command that displays the selected object data history (if supported). It is available for users with <span class="term">ViewDataHistory </span>access right.</p><p>Implemented the <span class="term">VersionNumberSwitchToDataHistoryVersion</span><span class="term"> </span>managed form parameter.</p><p>Implemented the <span class="term">GenerateFromDataHistoryVersionProcessing</span><span class="term">()</span><span class="term"> </span>event handler in the following modules:</p><ul><li>catalog object module</li><li>document object module</li><li>chart of accounts object module</li><li>business process object module</li><li>task object module</li><li>information register record set module.</li></ul><p>
</p><p>This handler is called when the object is generated based on the data history version.</p></td><td>The developer could not handle the object version restoration.<p>The object history could be displayed in the object form or the register record form only.</p></td><td>Extended data history options. Improved data history security.</td></tr><tr title="Версия 8.3.13" class="tag_64"><td><a name="cb118380-3e34-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New pictures were added to the picture library: <span class="term">Conversations</span>, <span class="term">NewConversation</span>, <span class="term">Notifications</span>.</td><td>The listed pictures were not available in the picture library.</td><td>More content for the picture library.</td></tr><tr title="Версия 8.3.13" class="tag_68"><td><a name="17e35a26-43b6-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>Implemented the data history of exchange plans, charts of calculation types, and constants.</td><td>This feature was not provided.</td><td>Data history is now available for more objects.</td></tr><tr title="Версия 8.3.13" class="tag_23"><td><a name="92eecd86-43b6-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Implemented the <span class="term">ConstantValueKey </span>object.<p>Implemented the <span class="term">CreateConstantValueKey()</span> method of the constant manager.</p></td><td>This feature was not provided.</td><td>Expanded constant management capabilities.</td></tr><tr title="Версия 8.3.13" class="tag_20"><td><a name="a85f1b4a-5a73-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Implemented the option to create a macOS-compatible distribution package.<p>The application distribution package now includes the .zip archive that contains the distribution file and the installer executable files for each supported operating system (Windows, Linux, macOS). The executable files now have the right parameters (Linux, macOS), so you can now unpack the distribution package and install the applicaton.</p><p>Implemented the <span class="term">CreativeDistributivePackage </span>command-line option of the Designer batch mode. The <span class="term">CreateDistributive </span>command-line option of the Designer batch mode is deprecated.</p></td><td>Creating an application distribution package for Windows and Linux only was allowed. The application could not be installed on macOS.<p>There was no option to create an application distribution package with correct executable files for each supported operating system. You had to specify the correct parameter in the Linux executable file to install the application.</p></td><td>You can now install the application on any supported operating system.<p>The distribution package is now compatible to any supported operating system.</p></td></tr><tr title="Версия 8.3.13" class="tag_29 tag_67"><td><a name="272141bd-5dc8-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>Implemented the 64-bit configuration repository server on Linux.</td><td>There was only the 32-bit configuration repository server available on Linux.</td><td>The functionality of configuration repository server is now fully available on 64-bit Linux.</td></tr><tr title="Версия 8.3.13" class="tag_68"><td><a name="6c641441-6269-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>Implemented the option to force the update of data history of specific infobase object. Imolemented the <span class="term">UpdateHistory</span><span class="term">() </span>method of the <span class="term">DataHistory </span>object.</td><td>This feature was not provided.<p>The data history update was available for all infobase objects at once only. If a specific object data history form was opened, some versions might not be displayed.</p></td><td>The specific object data history form now displays the full history.</td></tr></table><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74c7-0668-11e8-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.13" class="tag_4"><td><a name="7f4f80a6-0fe5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Converstation participants receive notifications in the conversation form if one of them is typing a message.<p>The following user statuses are now available: offline, away, do not disturb, and online. The Away status is available in thick and thin clients on Windows only.</p><p>Updated the new message notification.</p><p>You can now start a conversation with user from the user information form.</p><p>Updated the collaboration system main window.</p><p>Updated <span class="interface">Collaboration system management </span>standard function. Updated registration and cancelling registration forms.</p></td><td>These features were not provided.</td><td>Improved the collaboration system interface.</td></tr><tr title="Версия 8.3.13" class="tag_96"><td><a name="ba6b5fe6-117b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>Implemented the following changes In the <span class="interface">Taxi </span>interface:<ul><li>Managed form cell indents are reduced proportionally to the managed form scale if it is less than 100%. Implemented the factor of proportionality.</li><li>When the managed form scale is 80%, the table row height equals to the table row height in the compact mode, depending on the font and the screen DPI.</li><li>Reduced left and right table cell indents.</li><li>Reduced left and right indents of spreadsheet document columns generated by the <span class="interface">Output list </span>command.</li></ul></td><td>The Taxi interface behaved the following way:<ul><li>There was no factor of proportionality in reducing the managed form table cell indents.</li><li>Left and right table cell indents were wider.</li><li>Left and right indents of a spreadsheet document columns generated by the <span class="interface">Output list </span>command, were wider.</li></ul></td><td>Improved the spreadsheet document and managed form table appearance in managed form with custom scale.</td></tr><tr title="Версия 8.3.13" class="compat tag_96 tag_1"><td><a name="ec55bc87-1191-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>All incorrect links are displayed as a link (not link's presentation). When the user favorites settings dialog box is closed, incorrect links remain in the favorites list and can be used or edited.<p>Implemented the <span class="term">URLPresentation.Presentation() </span>method.</p><p>The <span class="term">GetURLsPresentations() </span>method always returns the array of <span class="term">URLPresentation objects</span>. Each <span class="term">URLPresentation </span>object in this array will have different values depending on the link.</p><p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>Incorrect links had a blank interface presentation and were not available.<p>They were deleted from the user work history after the user favorites settings dialog box was closed.</p><p>The <span class="term">GetURLsPresentations() </span>method applied to an incorrect link returned <span class="term">Undefined</span>.</p></td><td>Improved links performance.</td></tr><tr title="Версия 8.3.13" class="tag_28 tag_26"><td><a name="7b506cd4-1631-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Eliminated spreadsheet document printing faults in the web client if the HTML print method is selected.</td><td>A spreadsheet document might be printed with faults in the web client if the HTML print method was selected.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74c8-0668-11e8-a3f7-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.13" class="tag_16"><td><a name="0055064e-0a7f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>Implemented the cluster index based on dimensions of slice first and slice last physical tables of an information register. Index structure description <a href="https://its.1c.ru/db/metod8dev#content:1590:hdoc" target="_blank">Read more</a>..<p>Disabled index uniqueness verification.</p><p>Optimized performance of queries operating with slice tables.</p><p>This index can be built the following ways:</p><ul><li>restructuring the information register</li><li>database restructuring when the verification and repair operation is performed.
</li></ul></td><td>Physical slice first and slice last tables were not indexed.<p>The performance of the queries operating with slice tables was not optimal.</p></td><td>Improved physical slice tables performance in configurations with large number of users. Eliminated deadlocks when updating the physical slice tables.</td></tr><tr title="Версия 8.3.13" class="compat tag_21 tag_1"><td><a name="322c708b-0a83-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Reduced the size of temporary files created during the update of full-text search index. This change affects infobases with many separators the most.<p>The new temporary file format is used when the compatibility mode is disabled.</p><p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>Temporary files created during the update of full-text search index were significantly larger.</td><td>Reduced the disk space allocated for a full-text search index generating when the infobase contains many separators.</td></tr><tr title="Версия 8.3.13" class="tag_19"><td><a name="959fec93-0bec-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Improved performance of virtual turnover tables of accumulation and accounting registers when they are grouped by day, month, or year, or when the <span class="term">BeginOfPeriod() </span>query language function is used.<p>This change is available in all supported DBMS, except for Microsoft SQL Server versions earlier than 2012.</p></td><td>Performance of virtual turnover tables of accumulation and accounting registers when they were grouped by day, month, or year, or when the<span class="term"> BeginOfPeriod()</span> query language function was used, was suboptimal.</td><td>Improved performance of virtual turnover tables of accumulation and accounting registers.</td></tr><tr title="Версия 8.3.13" class="tag_36"><td><a name="695f83ad-0c0d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>Improved performance of the following <span class="term">ValueTreeRowCollection </span>object methods: <span class="term">Remove(), </span><span class="term">Insert()</span>,<span class="term"> Index(), </span>and<span class="term"> Move(). </span></td><td>The performance of the following <span class="term">ValueTreeRowCollection </span>object methods was insufficient: <span class="term">Remove</span><span class="term">()</span>, <span class="term">Insert</span><span class="term">()</span>, <span class="term">Index()</span>, and <span class="term">Move()</span>.</td><td>Improved performance of the value tree rows from 1C:Enterprise script.</td></tr><tr title="Версия 8.3.13" class="tag_80"><td><a name="6adbeeb9-0c0f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 80); return false;">External reports and data processors</a>.<br></td><td>Improved performance of loading external reports and data processors opened by large number of users.</td><td>Loading external reports and data processors opened by large number of users was longer.</td><td>Improved performance of loading external reports and data processors opened by large number of users.</td></tr><tr title="Версия 8.3.13" class="tag_120 tag_38"><td><a name="265e9fb7-0c11-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Improved performance of second and further background job startups if they use the same set of configuration extensions. This change is available In file mode.</td><td>In file mode second and further background job startups were longer even if they used the same set of configuration extensions.</td><td>Improved background job startups in the file mode if they are operating with configuration extensions.</td></tr><tr title="Версия 8.3.13" class="tag_36"><td><a name="13b106a9-0cc5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>Optimized filling and deleting rows of a table of values.</td><td>Filling and deleting rows of a table of values were longer.</td><td>Improved table of values performance.</td></tr><tr title="Версия 8.3.13" class="tag_28"><td><a name="3b31a21e-0cd7-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Optimized page titles (tabs) rendering in the web client.</td><td>Page titles (tabs) rendering in the web client was slow and suboptimal.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_58"><td><a name="f33468c0-0cdb-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>Improved opening forms performance in a configuration that uses common attributes.</td><td>Forms opened relatively slow if a configuration used common attributes.</td><td>Forms in a configuration that uses common attributes now open faster.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_1"><td><a name="6bd751fb-109b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Sometimes the data composition system template composer attempts to sort the data set by the DBMS means. The data composition system does not use it's own means in these cases. But the composition result may be incorrect because the row comparison operations are different in various DBMS and 1C:Enterprise platform.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>Data composition system template composer always sorts the data set by the data composition system means.</td><td>Improved the sorting performance during the report building in some scenarios.</td></tr><tr title="Версия 8.3.13" class="tag_25"><td><a name="76903677-10c4-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Improved the data composition system template generation if the data composition schema is composed of many queries that generate temporary tables with many fields that are not used in the composition process.</td><td>The data composition system template generation process was longer if the data composition schema was composed of many queries that generated temporary tables with many fields that were not used in the composition process.</td><td>Improved complex reports with many temporary tables building performance.</td></tr><tr title="Версия 8.3.13" class="compat tag_45 tag_1"><td><a name="7946ee38-1178-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If a query contains an <span class="term">IN </span>subquery then a join with table from the <span class="term">IN </span>subquery is used instead. This change is performed only if it does not affect the query result.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a query contained an <span class="term">IN </span>subquery, the DBMS always used this subquery.</td><td>Improved the DBMS query plan in some scenarios.</td></tr><tr title="Версия 8.3.13" class="tag_20 tag_6"><td><a name="cc415481-2064-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved the configuration database update performance when it is initiated from a debug session in client/server mode.</td><td>The configuration database update was longer when it was initiated from a debug session in client/server mode.</td><td>Improved the configuration database update performance when it is initiated from a debug session in client/server mode. </td></tr><tr title="Версия 8.3.13" class="tag_26"><td><a name="a2c82faf-2b56-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Improved the <span class="term">CheckPut() </span>method performance if a spreadsheet document contains multiple sheets.</td><td>The <span class="term">CheckPut()</span> method performance for a spreadsheet document with many sheets was insufficient. </td><td>Improved performance of spreadsheet document display.</td></tr><tr title="Версия 8.3.13" class="tag_26"><td><a name="93d5149b-30d2-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Improved copying to clipboard performance. Improved the <span class="term">GetArea() </span>spreadsheet document method performance when applied to the spreadsheet document area with multiple rows with custom column formatting.</td><td>Copying to clipboard performance and the<span class="term"> GetArea() </span>spreadsheet document method performance when applied to the spreadsheet document area with multiple rows with custom column formatting were insufficient</td><td>Improved performance of obtaining the spreadsheet document area with multiple rows with custom column formatting.</td></tr><tr title="Версия 8.3.13" class="tag_26 tag_28"><td><a name="f9d090bf-3e38-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Improved performance of spreadsheet document groups collapsing and expanding in the web client.</td><td>The collapsing and expanding of spreadsheet document groups in the web client was longer.</td><td>Improved spreadsheet document performance in the web client.</td></tr><tr title="Версия 8.3.13" class="tag_120"><td><a name="e6e8c76b-4ac1-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>Improved the background jobs execution and waiting for their completion.</td><td>The background jobs execution and waiting for their completion were longer.</td><td>The background jobs execution and waiting for their completion are now faster.</td></tr></table><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74c9-0668-11e8-a3f7-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.13" class="tag_4"><td><a name="c6d80ec6-080a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented the correct data area switching when a collaboration server is used. If the new data area is already registered in the collaboration server, this registration will be used.</td><td>This feature was not provided.<p>The reconnection to the collaboration server was not performed if the data area was switched.
</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_115"><td><a name="7a1f71c6-080c-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Changed the selected row view of the managed form table in the <span class="interface">Taxi </span>interface. The current row color now affects the selected row view.</td><td>The current row color did not affect the selected row view in the <span class="interface">Taxi </span>interface.</td><td>Improved the selected row view of the managed form table in the <span class="interface">Taxi </span>interface.</td></tr><tr title="Версия 8.3.13" class="tag_20"><td><a name="c4e18499-0cc4-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Modules locked with password are ignored in the Designer batch mode.<p>A diagnostic message is displayed instead.
</p></td><td>When modules locked with password were accessed in the Designer batch mode, the password request dialog box might be displayed.</td><td>Eliminated all interactive actions in the Designer batch mode, which does not support them.</td></tr><tr title="Версия 8.3.13" class="tag_64"><td><a name="a2d95fc2-0cdb-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>If the space is used as a group separator in the format string wizard the resulting format string the will use the nonbreaking space instead.</td><td>If the space was used as a group separator in the format string wizard the space was used in the resulting format string too.</td><td>Eliminated unexpected system behavior.<p>Decreased number of issues caused by the incorrect group separator.</p></td></tr><tr title="Версия 8.3.13" class="tag_4"><td><a name="7ab36123-0fe7-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td><span class="term">Implemented</span> noncontext conversations with two participants (face-to-face). Other users can not take part in such conversations.<p>Implemented the <span class="term">CollaborationSystemConversation.Group</span> and <span class="term">CollaborationSystemConversationsFilter.Group </span>properties.</p><p>Implemented the capability to combine subscribers applications (infobases or data areas). Implemented the capability to match users of different applications. Implemented the capability to combine context conversations from different applications. Only the subscriber owner can perform the listed above actions.</p><p>The <span class="interface">Collaboration system</span> management standard function can now merge applications, cancel applications merging, match users and context conversations.</p><p>Implemented the <span class="term">CollaborationSystemUser.MappingKey</span> property. Implemented the following methods of the collaboration system manager:</p><ul><li><span class="term">CurrentApplicationID()</span></li><li><span class="term">GetApplication()</span></li><li><span class="term">GetSubscriberApplications()</span></li><li><span class="term">SetSubscriberApplicationLinks()</span></li><li><span class="term">CancelSubscriberApplicationLinks()</span></li><li><span class="term">GetSubscriberApplicationLinks().</span></li></ul></td><td>These features were not provided.<p>The collaboration might be established only within a single subscriber application.
</p></td><td>Expanded the collaboration system capabilities.</td></tr><tr title="Версия 8.3.13" class="tag_20"><td><a name="2f04209e-10c3-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Error and warnings that are generated by the metadata check, are now displayed as <span class="term">dbstru </span>type messages. <p>Implemented the <span class="term">DBRestuctError </span>value for the<span class="term"> error-type </span>message. It describes the infobase restructuring error.</p><p>Implemented the <span class="term">CommandFormatError </span>value for the <span class="term">error-type </span>message. It describes the invalid command format error.
</p></td><td>Error and warnings that were generated by the metadata check, were displayed as <span class="term">log </span>type messages.</td><td>Improved the diagnostics of issues that occur in the Designer agent mode.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_1"><td><a name="c46ec29a-1179-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The composite type child fields are available in user settings if the user has the <span class="term">View </span>right to<span class="term"> </span>at least one table of that type and the field itself. The composite type child field can be used in filters, sorting, conditional appearance and other available user settings.<p>Implemented the<span class="term"> </span><span class="term">RestrictGettingFieldsByRefByViewRight </span>property of the <span class="term">DataCompositionProcessor.Initialize()</span> method.</p><p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If the user did not have the <span class="term">V</span><span class="term">iew</span> right to at least one table of the composite type, there were no child fields of the locked type in the user settings.</td><td>The user can now obtain the child fields data that he has a <span class="term">View </span>right on.</td></tr><tr title="Версия 8.3.13" class="compat tag_63 tag_1"><td><a name="cf5aa4f2-118d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The following options are now available in the chart type input field:<ul><li>The picture of a selected chart type is displayed in the input field.</li><li>The picture of chart type is displayed in the chart type selection list.</li><li>Implemented the autoselection when typing the chart name.</li><li>Implemented the input field selection button that opens the chart type selection dialog box.</li></ul><p>Implemented the <span class="term">ChartTypeChooseDialog </span>object.</p><p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The chart type input field behavior was the following:<ul><li>There was no selected chart type picture in the input field.</li><li>There was no chart type picture in the selection list.</li><li>There was no autoselection when typing the chart name.</li><li>There was no selection button that opened the chart type selection dialog box.</li></ul></td><td>Improved the chart type selection in some scenarios.</td></tr><tr title="Версия 8.3.13" class="tag_4"><td><a name="7d95919f-118e-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The video call can not be performed if one of the participants do not have the microphone available. The appropriate message is generated.<p>The collaboration system displays the microphone and camera diagnostic icons during the conversation.</p></td><td>The hardware diagnostics was not performed before and during the video call.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_20 tag_1"><td><a name="8cecc6a2-1632-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The attribute or the tabular section can not be named <span class="term">Presentation</span> if it is stored in the database.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>An attribute or a tabular section could be named <span class="term">Presentation</span>, but this might cause different issues.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_115"><td><a name="0584eb04-2068-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Implemented the following changes, when managed form tabs are displayed to the left or right of the <span class="term">Pages </span>item:<ul><li>The height of tabs headers is not affected by the form height. You can now scroll tabs headers vertically if they do not fit the form height.</li><li>You can use the wheel button to scroll tabs headers.</li><li>You can now use touchscreen to scroll tabs headers in the thin client on Windows.</li></ul></td><td>When managed form tabs were displayed to the left or right of the <span class="term">Pages</span>, the tabs headers height was decreased to fit the form height.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_115 tag_31"><td><a name="628126ea-25fe-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The different form <span class="interface">Auto </span>values of managed form table <span class="term">HeightControlVariant </span>property can now be used in configurations with<span class="interface"> version 8.3.7</span> or earlier compatibility mode.</td><td>The different form <span class="interface">Auto </span>values of managed form table <span class="term">HeightControlVariant </span>property were used in configurations with version<span class="interface"> 8.3.10 </span>or earlier compatibility mode.</td><td>Options of controlling the height of managed form table are now compliant with the mobile client.</td></tr><tr title="Версия 8.3.13" class="compat tag_115 tag_43 tag_1"><td><a name="337a8f25-4acc-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>If the main table of the dynamic list has both groups and elements, the form conditional appearance is applied to columns that are not linked with the main table, regardless whether the current row displays either an element or a group of the main table.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If the main table of the dynamic list had both groups and elements, the form conditional appearance was applied to columns that were not linked with the main table, in the following way:<ul><li>to a column that displays the common field (not expresiion) provided that the current row displays the main table element. </li><li>otherwise the form conditional appearance is applied when the current row displays the main table group.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_82 tag_1"><td><a name="34a21531-576c-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>If the <span class="interface">Period a</span><span class="interface">djustment</span> property of an accounting register is greater than 0, the <span class="term">PeriodAdjustment </span>standard attribute is displayed in the edit standard attributes form and becomes available in the <span class="term">StandardAttributes </span>collection of the <span class="term">AccountingRegister </span>metadata object (there is no <span class="term">PeriodAdjustment </span>attribute in the <span class="term">StandardAttributes </span>collection in version 8.3.12 compatibility mode).
</td><td>The <span class="term">PeriodAdjustment </span>standard attribute was not displayed in the edit standard attributes form and was not available in the <span class="term">StandardAttributes </span>collection of the <span class="term">AccountingRegister </span>metadata object.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_73 tag_1"><td><a name="c2cf6215-dcf4-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>If an infobase compatibility mode is <span class="interface">Version 8.3.10 </span>or earlier and its database configuration was changed in 1C:Enterprise version 8.3.10 or earlier, the chance of getting a message about incomplete configuration structure conversion when opening the infobase in a client application version 8.3.13 is reduced.</td><td>If an infobase compatibility mode was<span class="interface"> Version 8.3.10 </span>or earlier and its database configuration was changed in 1C:Enterprise version 8.3.10 or earlier, an attempt to open the infobase in a client application version 8.3.11 could not be completed. It returned a message about incomplete configuration structure conversion. The only way to recover the infobase was to open it in Designer version 8.3.11 or later and run infobase restructuring.</td><td>Smoother migration from 1C:Enterprise version 8.3.10 to later versions.</td></tr></table><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74ca-0668-11e8-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.13" class="compat tag_25 tag_63 tag_1"><td><a name="f6ca89b1-067d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The processor of data composition result output sets the automatic column width calculation for all cells in the spreadsheet document area that contains a chart.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The processor of data composition result output did not set the automatic column width calculation for all cells in the spreadsheet document area that contained a chart.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_1"><td><a name="d909e8b5-0734-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If the predefined grouping templates are used during the table columns output, then the grand totals template height is automatically calculated to fit all resource headers. The template generator automatically increases the predefined grouping template height If it is less than the grand totals template height.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If the predefined grouping templates were used in the table columns output and the grand totals template height was greater than the predefined grouping templates height, some resource headers might not be displayed in the grand totals template.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_4 tag_1"><td><a name="df8dfc8a-0816-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented the <span class="term">CollaborationSystemManager.IsEnabled() </span>method. It returns the following flags:<ul><li>The infobase is registered in the collaboration service.</li><li>The infobase registration is active.</li><li>There are collaboration system users in the infobase.</li></ul><p>The <span class="term">CollaborationSystemManager.InfoBaseRegistered() </span>method returns whether the infobase is registered in the collaboration service and the registration is active. This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The <span class="term">CollaborationSystemManager.InfoBaseRegistered() </span>method returned the following flags:<ul><li>The infobase was registered in the collaboration service.</li><li>The infobase registration was active.</li><li>There were collaboration system users in the infobase.</li></ul></td><td>You can now get the information about the infobase registration and the collaboration system availability separately.</td></tr><tr title="Версия 8.3.13" class="compat tag_26 tag_1"><td><a name="d804775f-0a83-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The spreadsheet document width and height (<span class="term">PageHeight </span>and <span class="term">PageWidth </span>properties) are limited to 5000 mm.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The spreadsheet document width and height (<span class="term">PageHeight </span>and <span class="term">PageWidth </span>properties) were unlimited.</td><td>Eliminated problems of the spreadsheet document with large pages export to other formats.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_1"><td><a name="1c6a775e-0b43-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If an unavailable property of a data composition system object is accessed, an exception is thrown.<ul><li>The <span class="term">UserSettingPresentation </span>property of <span class="term">DataCompositionFilter</span>, <span class="term">DataCompositionSelectedFields</span>, <span class="term">DataCompositionConditionalAppearance</span> objects.</li><li>The <span class="term">UserSettingPresentation</span>, <span class="term">Presentation</span>, <span class="term">LeftValue</span>, <span class="term">Application</span>, <span class="term">Parent</span> properties of the <span class="term">DataCompositionFilterItem</span> object.</li><li>The <span class="term">UserSettingPresentation</span>, <span class="term">Presentation</span>, <span class="term">Application</span>, <span class="term">Parent</span>, <span class="term">GroupType</span>, <span class="term">Items</span> properties of the <span class="term">DataCompositionFilterItemGroup</span> object.</li><li>The <span class="term">UserSettingPresentation</span>, <span class="term">Presentation</span>, <span class="term">Fields</span>, <span class="term">Filter</span>, <span class="term">UseInGroup</span>, <span class="term">UseInHeader</span>, <span class="term">UseInFieldsHeader</span>, <span class="term">UseInHierarchicalGroup</span>, <span class="term">UseInOverall</span>, <span class="term">UseInFilter</span>, <span class="term">UseInParameters</span> properties of the <span class="term">DataCompositionConditionalAppearanceItem</span> object.</li><li>The <span class="term">UserSettingPresentation</span>, <span class="term">NestedParameterValues</span>, <span class="term">Parent</span>, <span class="term">Para</span><span class="term">meter</span> (only when setting the property value) properties of the <span class="term">DataCompositionSettingsParameterValue</span> object.</li><li>The <span class="term">UserSettingPresentation</span>, <span class="term">ID</span>, <span class="term">Name</span>, <span class="term">Choice</span>, <span class="term">Filter</span>, <span class="term">OutputParameters</span>, <span class="term">GroupFields</span>, <span class="term">Order</span>, <span class="term">Parent</span>, <span class="term">State</span>, <span class="term">Structure</span>, <span class="term">ConditionalAppearance</span> properties of the <span class="term">DataCompositionGroup</span>, <span class="term">DataCompositionTableGroup</span>, <span class="term">DataCompositionChartGroup</span> objects.</li><li>The <span class="term">UserSettingPresentation</span>, <span class="term">Choice</span>, <span class="term">ID</span>, <span class="term">Name</span>, <span class="term">Columns</span>, <span class="term">OutputParameters</span>, <span class="term">Parent</span>, <span class="term">Strings</span>, <span class="term">ConditionalAppearance</span> properties of the <span class="term">DataCompositionTable</span> object.</li><li>The <span class="term">UserSettingPresentation</span>, <span class="term">Choice</span>, <span class="term">ID</span>, <span class="term">Name</span>, <span class="term">Outp</span><span class="term">utParameters</span>, <span class="term">Parent</span>, <span class="term">Sreies</span>, <span class="term">Points</span>, <span class="term">ConditionalAppearance</span> properties of the <span class="term">DataCompositionChart</span> object.</li><li>The <span class="term">UserSettingPresentation</span>, <span class="term">ID</span>, <span class="term">ObjectID</span>, <span class="term">Name</span>, <span class="term">Settings</span>, <span class="term">Parent</span> properties of the <span class="term">DataCompositionNestedObjectSettings</span> object.</li><li>The <span class="term">UserSettingPre</span><span class="term">sentation</span> and <span class="term">ViewMode</span> properties of the <span class="term">DataCompositionSettingStructureItemCollection</span> object. This change is available only if the parent of the <span class="term">DataCompositionSettingStructureItemCollection</span> object is a <span class="term">DataCompositionSettingStructure</span> type object that is included in the <span class="term">DataCompositionUserSettingsItemCollection</span> collection.</li></ul><p>This change is not implemented in version 8.3.12 compatibility mode.
</p></td><td>Accessing the listed above properties of the user settings objects was meaningless and did not throw an exception.</td><td>Eliminated the incorrect accessing to data composition system object properties.</td></tr><tr title="Версия 8.3.13" class="compat tag_120 tag_1"><td><a name="79bce5c1-0c0e-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>The maximum size of serialized background job parameters is 1 GB. Otherwise an exception is thrown.<p>If the version 8.3.12 compatibility mode is set, an exception is thrown if the size of serialized background job parameters is greater than 2 GB.</p></td><td>If the size of serialized background job parameters was greater than 2 GB the session was abnormally terminated.</td><td>Improved background jobs stability. Decreased the background job impact on the system performance if very large parameters were sent.</td></tr><tr title="Версия 8.3.13" class="compat tag_43 tag_1"><td><a name="d6f7c719-0cd6-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The <span class="term">OnChange </span>event occurs once per deleting dynamic list rows in the thin client.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The <span class="term">OnChange </span>event might occur multiple times when dynamic list rows were deleted in the thin client. The number of event calls depended on the deleted rows number:<ul><li>less or equal to 100 rows. The number of event calls was equal to the rows number.</li><li>more than 100 rows. The event was called once.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_36 tag_1"><td><a name="cb2fd2e0-0cd7-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The <span class="term">Font </span>object constructor returns the <span class="interface">Common style text </span><span class="interface">font </span>if the <span class="term">FontName </span>constructor parameter is not specified.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The <span class="term">Font </span>object constructor returned <span class="interface">Dialog and menu </span><span class="interface">font </span>if the <span class="term">FontName </span>constructor parameter was not specified.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_29 tag_15"><td><a name="c3dbc448-0cd8-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The ImageMagick library from the 1C:Enterprise platform distribution package is used.</td><td>The ImageMagick library from the operating system was used.</td><td>Reduced the number of issues that might arise due to the incorrect ImageMagic library version in the operating system.</td></tr><tr title="Версия 8.3.13" class="compat tag_115 tag_1"><td><a name="9b300c12-0cd9-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The <span class="term">AddRow()</span>, <span class="term">ChangeRow()</span>, <span class="term">CopyRow()</span> and <span class="term">EndEditRow()</span> methods of the <span class="term">ManagedFormTable </span>object do not perform any actions if their related interactive commands are not available.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The behavior of the <span class="term">AddRow()</span>, <span class="term">ChangeRow()</span>, <span class="term">CopyRow()</span> and <span class="term">EndEditRow()</span> methods of the <span class="term">ManagedFormTable </span>object depended on the client application type.<p>In the thin client they performed the related actions.
In the web client no actions were performed.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_20"><td><a name="a6d8f860-0cda-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The English version of ID, attribute name and metadata object name is now saved in the configuration merge settings file.<p>The following actions are performed when reading the configuration merge settings file: attempt to read IDs in English. If failed, attemt to read IDs in Russian.</p></td><td>The version of ID, attribute name and metadata object name that were saved in the configuration merge settings file, depended on the configuration script variant.</td><td>The result of the configuration merge settings loading does not depend on the configuration script variant.</td></tr><tr title="Версия 8.3.13" class="compat tag_28 tag_78 tag_1"><td><a name="07736471-0d7a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>Improved web client file operations.<p>Implemented the new file selection dialog box. It supports multiple file choice and dragging. The file system extension is not required for this dialog box.</p><p>Implemented the limited editing of the file selection dialog box <span class="term">BeginPutFile() </span>and <span class="term">BeginPuttingFiles() </span>methods.</p><p>The <span class="term">BeginPutFile</span><span class="term">()</span> method does not require the file system extension installed.</p><p>Added the option to manage specific parameters of files before transfering them to server. Implemented the <span class="term">BeforeBeginPuttingFilesNotificationDescriprion </span>parameter of the <span class="term">BeginPutFile()</span> and <span class="term">BeginPuttingFiles()</span> methods.</p><p>Implemented the <span class="term">FullName </span>and <span class="term">FileID </span>properties of the <span class="term">TransferredFileDescription </span>object. The <span class="term">Name </span>property of the TransferredFileDescription contains only the transferred file name. The <span class="term">BeginPutFile</span><span class="term">()</span> method allows other calls and methods in the thin client. This change is not implemented in version 8.3.12 compatibility mode.
You can now drag files on the following form items: managed form field extension for a picture, managed form decoration extension for a picture, and managed form table. Implemented the <span class="term">FileDragMode </span>property of the listed above managed form items. Implemented the <span class="term">FileRef </span>object.</p><p>The <span class="term">PutFile()</span>,<span class="term"> </span><span class="term">PutFiles()</span>, and <span class="term">GetFiles()</span> methods are deprecated.</p><p>It is recommended to rework file operations in applications that use the web client.</p></td><td>The file operations in the web client were limited if the file system extension was not installed.<p>In the thin client, while the <span class="term">BeginPutFile</span><span class="term">()</span> method was being executed, calls of other methods were not allowed.</p><p>The <span class="term">TransferredFileDescription.Name</span> property contained the full file name.</p></td><td>Expanded the file operations in the web client that do not require the file system extension installed. The web client supports and handles the file dragging.</td></tr><tr title="Версия 8.3.13" class="compat tag_63 tag_1"><td><a name="772660c9-0d87-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>If the chart data contains non-numeric values (<span class="term">NULL </span>or <span class="term">Undefined</span>), the chart behavior can be specified. Implemented the <span class="term">NonnumericValueUse</span> and <span class="term">PointsConnectionAcrossSkippedValues</span> properties of the <span class="term">Chart</span> object.<p>Implemented the <span class="term">ChartType</span>.<span class="term">NonnumericValueUse</span> and <span class="term">ChartType.PointsConnectionAcrossSkippedValues </span>properties of the following objects: <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, <span class="term">DataCompositionAreaTemplateChartAppearance</span>.</p><p>If displaying of a series marker is disabled (<span class="term">ChartMarkerType.None </span>is set) and a series value in some point is separated (values in the next and previous points are omitted), then this value is displayed as a circle. The width of the circle line equals to the series line width. Chart lines connections are now rounded. This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The chart behavior could not be specified if the chart data contained non-numeric values.<p>If displaying of a series marker was disabled (<span class="term">ChartMarkerType.None </span>was set) and a series value in some point was separated (values in the next and previous points were omitted), then this value was not displayed on a chart.</p><p>The chart lines connection was not rounded.</p></td><td>Expanded operations with charts.</td></tr><tr title="Версия 8.3.13" class="compat tag_51 tag_1"><td><a name="06bf2bd6-0d8d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>The <span class="term">TestedFormTable.Expand() </span>method can now expand subordinate nodes on the next level of the selected node only. Implemented the <span class="term">WithSubordinates </span>parameter of the <span class="term">TestedFormTable.Expand() </span>method.<p>This change is not implemented in version 8.3.12 compatibility mode.
It is recommended to review and rework all code fragments with the <span class="term">TestedFormTable.Expand() </span>method.</p></td><td>The <span class="term">T</span><span class="term">estedFormTable.Expand()</span> method expanded the selected node and all subordinate nodes.</td><td>The automated testing features now correspond the 1C:Enterprise platform capabilities.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_43 tag_62 tag_1"><td><a name="b2c3f35d-0fe9-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>If a dynamic list field in a report may be <span class="term">NULL</span>, the following ordering rule is applied to that field: <span class="term">NULL</span> values come first.<p>If a dynamic list field is based on an external data source table field, and the external data source contains the<span class="term"> CASE ... WHEN</span> selection that might return <span class="term">NULL</span>, the following ordering rule is applied to that field: <span class="term">NULL</span> values come first.</p><p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a dynamic list was ordered by a field that might be <span class="term">NULL</span> , rows with <span class="term">NULL</span> and with the default field type value were placed together.<p>If a dynamic list was ordered by a field that was based on the external data source table of any type, the final ordering depended on the DBMS type.</p></td><td>Dynamic list ordering by the field that might be <span class="term">NULL</span> rule is now the same as the other objects ordering rule.</td></tr><tr title="Версия 8.3.13" class="compat tag_115 tag_1"><td><a name="96938edd-10d4-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When the <span class="term">AutoMarkIncomplete </span>property of a managed form table is set to True, the <span class="term">MarkIncomplete </span>property of that table obtains the correct value after the script execution.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>The <span class="term">MarkIncomplete </span>property of a managed form table was refreshed only when the table was refreshed or the current table cell was changed.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_45 tag_1"><td><a name="4f916e28-116b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>The <span class="term">IS NULL </span>function returns <span class="term">FALSE</span> if it is applied to the combination of virtual fields. The <span class="term">IS NULL </span>function returns <span class="term">TRUE</span> if it is applied to the combination of virtual fields and the expression without virtual fields that returns <span class="term">NULL</span>. The <span class="term">IS NULL </span>function returns <span class="term">FALSE</span> if it is applied to the combination of virtual fields and the expression without virtual fields that does not return <span class="term">NULL</span>.<p>This change is not implemented in version 8.3.12 compatibility mode.</p><p>It is recommended to review all <span class="term">IS NULL </span>functions in existing applications.</p></td><td>The <span class="term">IS NULL </span>function returned <span class="term">FALSE</span> if it was applied to the combination of virtual fields or to the combination of virtual fields and the expression without virtual fields.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_78 tag_6"><td><a name="86a38a65-1232-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>If a security profile that blocks access to the file system is set in the infobase, the <span class="term">TempFilesDir()</span> and <span class="term">GetTempFileName() </span>global context methods return paths with separators, provided by the current operating system.</td><td>If a security profile that blocked access to the file system was set in the infobase, the <span class="term">TempFilesDir</span><span class="term">()</span> and <span class="term">GetTempFileName()</span> global context methods returned paths with separators, provided by the Linux operating system.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_78"><td><a name="b6a91ca3-1234-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>If the parameter of the following File object methods is set to date before the January 1, 1601 in the Windows operating system, these methods throw the<span class="interface"> File access denied </span>exception: <ul><li><span class="term">SetModificationTime</span><span class="term">()</span></li><li><span class="term">SetModificationUniversalTime</span><span class="term">()</span></li><li><span class="term">BeginSettingModificationTime</span><span class="term">()</span></li><li><span class="term">BeginSettingModificationUniversalTime</span><span class="term">()</span>.</li></ul><p>All errors of <span class="term">File </span>object methods throw the same exception.</p></td><td>If the parameter of the following <span class="term">File </span>object methods was set to date before the January 1, 1601 in the Windows operating system, these methods returned the random date:<ul><li><span class="term">SetModificationTime()</span></li><li><span class="term">SetModificationUniversalTime()</span></li><li><span class="term">BeginSettingModificationTime()</span></li><li><span class="term">BeginSettingModificationUniversalTime().</span></li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_1"><td><a name="d144ccf1-2062-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If the <span class="term">CASE </span>operation is used in the data composition system calculated expression, and the resulting field type is unknown (it is a values table field or the field type is not specified) and the <span class="term">ELSE </span>section contains the <span class="term">Undefined </span>value, the result field type in the result values collection will be set to <span class="term">Custom </span>(the type description will be blank).<p>This change is not implemented in version 8.3.12 compatibility mode. </p></td><td>If the <span class="term">CASE </span>operation was used in the data composition system calculated expression, and the resulting field type was unknown (it was a values table field or the field type was not specified) and the <span class="term">ELSE </span>section contained the <span class="term">Undefined </span>value, the result field type in the result values collection would be <span class="term">NULL</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_115 tag_1"><td><a name="e8358d91-2063-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Only methods with the <span class="term">Export </span>keyword are available in expressions containing <span class="term">ThisObject</span>. This change affects from module as well as other modules, where <span class="term">ThisObject </span>is passed.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>All methods were available in expressions containing <span class="term">ThisObject</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_1"><td><a name="584f0dcf-2064-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a filter with the <span class="term">filled</span>/<span class="term">not filled </span>comparison type is used in the data composition system settings and this filter is applied to the calculated field, which type is custom, <span class="term">Characteristics </span>type, or any reference type, then the filter will consider types, included in the <span class="term">Characteristic</span>, custom type or any reference type.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a filter with the <span class="term">filled</span>/<span class="term">not filled </span>comparison type was used in the data composition system settings and this filter was applied to the calculated field, which type was custom, <span class="term">Characteristics </span>type, or any reference type, then the filter ignored types, included in the <span class="term">Characteristic</span>, custom type or any reference type.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_45 tag_1"><td><a name="db821fb2-30d0-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If a temporary table is created by the <span class="term">INTO </span>clause, the temporary table field with <span class="term">NULL </span>value has a compound data type. This compound data type includes the following types:<ul><li><span class="term">Number </span>with 1.0 precision</li><li><span class="term">String </span>of 1 character</li><li><span class="term">DateTime</span></li><li><span class="term">Boolean</span></li><li><span class="term">NULL</span></li></ul><p>
</p><p>It is recommended to review all temporary table fields that might have <span class="term">NULL </span>value.</p><p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a temporary table was created by the <span class="term">INTO </span>clause, the temporary table field with <span class="term">NULL </span>value had <span class="term">NULL </span>type.</td><td>Temporary table fields with <span class="term">NULL </span>values are now available in expressions that do not support <span class="term">NULL </span>value. The <span class="term">CAST() </span>function can be used in such cases.</td></tr><tr title="Версия 8.3.13" class="compat tag_104 tag_1"><td><a name="616f0051-3e43-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>If a functional option value is stored in a periodic information register resource, it is obtained from the slice last. The date from the functional option <span class="term">Period </span>parameter, or the current date (if the functional option <span class="term">Period </span>parameter is not specified) is used as a slice last date.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a functional option value was stored in a periodic information register resource, it was calculated by the logical OR operation across all stored resource values, if only the <span class="term">Period </span>parameter was specified.</td><td>Eliminated unexpected system behavior. <p>The system behavior is now compliant to documentation.</p></td></tr><tr title="Версия 8.3.13" class="compat tag_115 tag_1"><td><a name="c17230db-4152-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Managed form table rows are filtered if there are multiple filter items and the first item filter value is <span class="term">Undefined</span>.<p>This change is not implemented in version 8.3.12 compatibility mode.
</p></td><td>Managed form table rows were not filtered if there were multiple filter items and the first item filter value was <span class="term">Undefined</span>.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74cb-0668-11e8-a3f7-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.13" class="tag_0"><td><a name="dc66bb4a-10cc-11e8-a3f7-0050569f678a"></a>The getting/setting HTML document methods of formatted document extension of the <span class="term">TestedFormField </span>object. <p>The former names are supported for compatibility purposes.</p></td><td><ul><li><span class="term">GetHTML()</span></li><li><span class="term">SetHTML()</span></li></ul></td><td><ul><li><span class="term">GetDocumentHTML</span><span class="term">()</span></li><li><span class="term">SetDocumentHTML</span><span class="term">()</span></li></ul></td></tr></table><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74cc-0668-11e8-a3f7-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.13" class="tag_48"><td><a name="022c1384-2066-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Push notifications on Android use Firebase Cloud Messaging service. It is recommended to transfer push notifications to this platform in current applications.<p>Implemented the <span class="term">DeliverableNotificationSubscriberType.FCM </span>enumeration value.</p><p>The Google Cloud Messaging service is supported for compatibility purposes and is not recommended for use.</p><p>The <span class="term">DeliverableNotificationSubscriberType.G</span><span class="term">CM </span>value is obsolete and supported for compatibility purposes. The <span class="term">GoogleCloudApplicationNumber </span>parameter of the <span class="term">ReceiveNotificationSubscriberID()</span> method is optional on Android. </p></td><td>Push notifications on Android used Google Cloud Messaging service.</td><td>The legacy push notifications delivery service is no longer used. Transfered to the latest version of the service.</td></tr><tr title="Версия 8.3.13" class="tag_48 tag_30 tag_31"><td><a name="256e22be-2069-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Implemented the capability of managing the camera backlight interactively (on Android and Windows Phone) and from the 1C:Enterprise script (on all mobile operating systems).<p>Implemented the <span class="term">DeviceTools </span>global context property. Implemented the <span class="term">CameraBacklightType </span>parameter of the <span class="term">MultimediaTools.MakePhoto() </span>method.</p><p>You can now use a camera flash as a flashlight. Implemented the <span class="term">DeviceTools </span>global context property. Implemented the <span class="term">FlashlightSupported() </span>and <span class="term">TurnFlashlightOn()</span> methods of the device tools manager.</p></td><td>Managing the camera backlight from the 1C:Enterprise script was not available.<p>Interactive managing of the camera backlight was available only on iOS.</p><p>There was no option to use a camera flash as a flashlight.</p></td><td>Extended the mobile device camera operations.</td></tr><tr title="Версия 8.3.13" class="tag_26 tag_30"><td><a name="24adc145-30d8-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC.</td><td>A PDF type document generated on the mobile platform was less similar to the same PDF type document generated on PC.
</td><td>A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC.</td></tr><tr title="Версия 8.3.13" class="tag_48 tag_31 tag_30"><td><a name="45d19167-4156-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>Implemented acquiring purchase receipts feature in 1C:Enterprise mobile version. It is now available to validate the purchase receipt on a mobile device.<p>Implemented the following <span class="term">InAppPurchasesManager </span>object methods:</p><ul><li><span class="term">PurchaseHistorySupported</span><span class="term">()</span></li><li><span class="term">GetPurchaseHistory</span><span class="term">()</span></li><li><span class="term">GetInAppPurchaseReceipts</span><span class="term">()</span></li><li><span class="term">GetInAppPurchaseReceiptsData().</span></li></ul><p>
</p><p>The <span class="term">InAppPurchasesManager</span> object is now available in the mobile client and in the mobile platform client. Implemented the <span class="term">InAppPurchasesValidationManager</span>.<span class="term">ValidateInAppPurchaseReceiptAtMobileDevice</span><span class="term">()</span> method on the mobile client and on the mobile platform client.</p><p>The global context <span class="term">InAppPurchasesValidation</span> property is now available on the mobile client and on the mobile platform client.</p><p>Acquiring the list of internal purchases is now available in the mobile application builder purchase emulator.</p></td><td>Acquiring purchase receipts feature was not available.<p>The <span class="term">InAppPurchasesValidationManager</span> object and the <span class="term">InAppPurchasesValidation</span> global context property were available only on the server of the PC platform.</p></td><td>Improved the internal purchases feature, provided by the appropriate application store.</td></tr><tr title="Версия 8.3.13" class="tag_30"><td><a name="88ed9105-415f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>Implemented the following form control properties:<ul><li><span class="term">DisplayImportance </span>for all controls</li><li><span class="term">CurrentRowUse </span>and <span class="term">TableBehaviorOnHorizontalCompression </span>for a form table.</li></ul><p>
Implemented input hints for multiline input fields.</p></td><td>These features were available in the mobile client only.</td><td>Managed forms are now displayed the same way in different 1C:Enterprise mobile versions.</td></tr></table><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74cd-0668-11e8-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.13" class="tag_0"><a name="d4e59dd3-0c11-11e8-a3f7-0050569f678a"></a>The LibEtPan library is updated to version 1.8.</li><li title="Версия 8.3.13" class="tag_0"><a name="072ea13b-0c12-11e8-a3f7-0050569f678a"></a>The WebSocket library is updated to version 0.7.0.</li><li title="Версия 8.3.13" class="tag_0"><a name="72cb6461-6313-11e8-a3f7-0050569f678a"></a>The Micosoft JDBC Driver for SQL Server is updated to version 6.2.</li></ul><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="63097281-25f7-11e8-a3f7-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.13" class="tag_0"><a name="d35b18c6-626c-11e8-a3f7-0050569f678a"></a>Implemented the option to specify the image of the good by dragging it to the form of the good.</li><li title="Версия 8.3.13" class="tag_0"><a name="0014ae86-626d-11e8-a3f7-0050569f678a"></a>Expanded options of the user settings form if the collaboration system is linked to the infobase: install and update the client application agent, create or cancel the link between the application and the client application agent.</li><li title="Версия 8.3.13" class="tag_0"><a name="1cc1b5ad-626d-11e8-a3f7-0050569f678a"></a>The new messages notification was changed to show the options of the <span class="term">StringWithNumber() </span>function.<p>
</p></li></ul><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74ce-0668-11e8-a3f7-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.13" class="tag_96"><td><a name="03441b2e-7856-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In <span class="interface">Taxi</span> interface the command check in the menu now displays the same way in different displaying options and different client application types.</td><td>The command check in the menu could be different depending on displaying options and client application types.</td><td>The command check in the menu now displays the same way.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_1"><td><a name="11b285ec-7857-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a filter is added to a query of composition schema data set that includes union, this filter is added to every part of the union. If a particular union part does not contain a field that is used in the filter, this field is replaced by <span class="term">NULL</span>. <p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a filter was added to a query of composition schema data set that includes union, this filter was added to parts of the union that contained the field that was used in the filter.
</td><td>Unified filter operations in data composition system between the union data set and query data set, where the query contained a union.</td></tr><tr title="Версия 8.3.13" class="tag_37"><td><a name="42bdbf4d-7859-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The parameters of the following <span class="term">FTPConnection </span>object methods were renamed in the Syntax Assistant: <span class="term">Get() </span>and <span class="term">Put().</span><p>This change is available in the Syntax Assistant only.</p></td><td>The parameters of the following <span class="term">FTPConnection </span>object methods were different in the Syntax Assistant:<span class="term"> Get() </span>and<span class="term"> Put().</span></td><td>The names of the FTP methods parameters became more clear.</td></tr><tr title="Версия 8.3.13" class="tag_48 tag_30 tag_31"><td><a name="87fa5149-7865-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The <span class="term">DeliverableNotification.Title </span>value is now displayed when a notification is shown on iOS version 8.2 and later mobile device.</td><td>The <span class="term">DeliverableNotification.Title </span>value was available on Android only.</td><td>Improved notifications on iOS.</td></tr><tr title="Версия 8.3.13" class="tag_4 tag_30 tag_31"><td><a name="a2c54317-7867-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The collaboration system notifications now contain the sender name. The noncontext conversation title is displayed in the notification title.
</td><td>The collaboration system notifications did not contain the sender name. The noncontext conversation title was displayed both in the notification title and text.</td><td>Improved collaboration system notifications.</td></tr><tr title="Версия 8.3.13" class="tag_37"><td><a name="4f4a6528-9402-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>macOS certificate store is now supported.<p>New objects: <span class="term">MacOSCertificationAuthorityCertificates</span>, <span class="term">MacOSCertificateSelectMode</span>, and <span class="term">MacOSClientCertificate</span>.</p><p>macOS certificate store support is added to object <span class="term">OSCertificationAuthorityCertificates</span>.</p><p>New <span class="term">-</span><span class="term">macos</span> parameter for <span class="term">/HttpsCA</span> and <span class="term">/HttpsCert</span> command-line options of the client application.</p><p>New technological log event: <span class="term">&lt;MACCERT&gt;</span>.</p></td><td>macOS certificate store was not supported. Secured connection was only available if certificates were stored in files.</td><td>You can use the system certificate store to establish secured connection on macOS.</td></tr><tr title="Версия 8.3.13" class="tag_4"><td><a name="1746c15f-9494-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The client application agent supports multiple versions of the collaboration system server's exchange protocol.<p>New <span class="interface">1ceclac </span>application is provided. The client application agent's directory structure is changed.</p></td><td>The client application agent supports a single version of the collaboration system server's exchange protocol.</td><td>The client application agent supports the previous versions of the collaboration system server's exchange protocol.
</td></tr><tr title="Версия 8.3.13" class="tag_43"><td><a name="ddd887a5-94a0-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The following restrictions apply to search in dynamic lists:<ul><li>The search string cannot exceed 1000 characters.</li><li>The search string cannot contain more that 20 words.</li></ul><p>If the search string does not comply with the listed requirements, an exception is generated. For details on splitting the search string into words, see 1C:Enterprise documentation.</p></td><td>There were no restrictions to search in dynamic lists.</td><td>Improved application server reliability when searching in dynamic lists.</td></tr><tr title="Версия 8.3.13" class="compat tag_43 tag_25 tag_1"><td><a name="17814592-94ab-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When opening report forms or dynamic list forms, if user settings are not available in the storage, the system performs the following actions:<ul><li>Items with unavailable or missing fields are deleted from the main dynamic list settings and report option settings that are marked as user settings.</li><li>Items with unavailable or missing fields are deleted from the default user settings.</li><li><span class="term">BeforeLoadUserSettingsAtServer </span>and <span class="term">OnLoadUserSettingsAtServer </span>event handlers are executed.</li></ul><p>New <span class="term">UseDefaultSettings </span>parameter for <span class="term">BeforeLoadUserSettingsAtServer </span>and <span class="term">OnLoadUserSettingsAtServer </span>event handlers.</p><p>The<span class="interface"> Set default settings </span>command of report and dynamic list forms performs the following actions:</p><ul><li>Items with unavailable or missing fields are deleted from the main dynamic list settings and report option settings that are marked as user settings.</li><li>Items with unavailable or missing fields are deleted from the default user settings.</li><li>If the user settings of a dynamic list or a report option were not changed on the client (interactively or from 1C:Enterprise language) since the form was opened, the current user settings are deleted from the system storage when the form is closed</li></ul><p>Method <span class="term">DataCompositionSettingsComposer.Refresh() </span>with parameter <span class="term">DataCompositionSettingsRefreshMethod.Full </span>performs the following actions: sets the <span class="interface">Use </span>flag to False for main settings items that lost their linking to available fields, and deletes items of main settings and user settings that are marked as user settings but contain fields absent from the collection of available fields or not available for the current functional options and rights.</p><p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>When opening report forms or dynamic list forms, if user settings were not available in the storage, the system performed the following actions:<ul><li>Items with unavailable or missing fields were not deleted from the main dynamic list settings and report option settings that were marked as user settings.</li><li>Items with unavailable or missing fields were not deleted from the default user settings.</li><li><span class="term">BeforeLoadUserSettingsAtServer </span>and <span class="term">OnLoadUserSettingsAtServer </span>event handlers were not executed.</li></ul><p>The <span class="interface">Set default settings</span> command of report and dynamic list forms had the following behavior:</p><ul><li>Items with unavailable or missing fields were not deleted from the main dynamic list settings and report option settings that were marked as user settings.</li><li>Items with unavailable or missing fields were not deleted from the default user settings.</li><li>If the user settings of a dynamic list or a report option were not changed on the client (interactively or from 1C:Enterprise language) since the form was opened, the default settings generated based on the main dynamic list settings or on the current report option settings were saved as user settings when the form was closed.</li></ul><p>Method <span class="term">DataCompositionSettingsComposer.Refresh()</span> with parameter <span class="term">DataCompositionSettingsRefreshMethod.Full </span>set the <span class="interface">Use </span>flag to False for main settings items that lost their linking to available fields.</p></td><td>Unavailable fields cannot be added to the default user settings of reports or dynamic lists.</td></tr><tr title="Версия 8.3.13" class="compat tag_126 tag_1"><td><a name="8e08b39a-94af-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 126); return false;">Data analysis</a>.<br></td><td>If a data set contains an even number of elements, its median is calculated as the arithmetic mean of the two middle elements of the ordered set. In particular, this rule applies to data sets that contain two elements.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a data set contained an even number of elements, its median was calculated as follows:<ul><li>For data sets with more than 2 elements, the arithmetic mean of the two middle elements of the ordered set.</li><li>For data sets with 2 elements, the value of the second element.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_37 tag_1"><td><a name="e511ed89-94b4-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For SMTP operations, added support of <span class="term">NOTIFY </span>parameter of <span class="term">RCPT </span>command and <span class="term">RET </span>parameter of <span class="term">MAIL </span>command. This provides support for mail delivery receipts described in RFC 1891.<p><span class="term">InternetMailMessage.DeliveryReceiptAddresses</span> property is deprecated. This property is only available in Version 8.3.12 compatibility mode.</p><p>Note that some SMTP server implementations or some of their settings can prevent receiving mail delivery receipts.</p><p>It is recommended that you do not use <span class="term">DeliveryReceiptAddresses </span>property of <span class="term">InternetMailMessage </span>object. Use the following properties instead:</p><ul><li><span class="term">ReadReceiptAddresses </span>and <span class="term">RequestReadReceipt </span>to receive read receipts.</li><li><span class="term">RequestDeliveryReceipt </span>to receive delivery receipts.</li></ul></td><td>Instead of delivery receipts, read receipts were generated.</td><td>Eliminated unexpected system behavior.<p>Both delivery and read receipts are now available.</p></td></tr><tr title="Версия 8.3.13" class="compat tag_37 tag_1"><td><a name="53aed289-94b5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>If a mailbox does not contain any messages matching the IDs specified in the parameter of <span class="term">InternetMail.GetMessagesFlags() </span>method, the method returns a blank map.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a mailbox did not contain any messages matching the IDs specified in the parameter of <span class="term">InternetMail.GetMessagesFlags()</span> method, the method generated an exception.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_26"><td><a name="463cad8b-94c7-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>An attempt to save a spreadsheet document with pictures in 1C:Enterprise 7.7 format on a server or in an external connection generates an exception. Only spreadsheet documents without pictures can be saved in this format.</td><td>An attempt to save a spreadsheet document with pictures in 1C:Enterprise 7.7 format on a server or in an external connection resulted in generation of a corrupted document that could not be opened.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_115 tag_1"><td><a name="6c313441-94c9-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If the <span class="term">Width </span>property of a form field is not 0 and horizontal stretching is not applied, this property defines the field width without the input field buttons (<span class="interface">Select</span>, <span class="interface">Clear</span>, and others). The resulting field width is equal to the sum of the <span class="term">Width </span>value and all button widths.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If the <span class="term">Width </span>property of a form field was not 0 and horizontal stretching was not applied, this property defined the field width as follows:<ul><li>If input field buttons were available, it defined the field width without the buttons.</li><li>If input field buttons were not available, the actual width was slightly greater than the specified one.</li></ul><p>Thus, adding or removing input field buttons could change the field width.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_4"><td><a name="8cc1baf2-9567-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>If several applications share a collaboration server, the message counter of the client application agent is incremented once per message.</td><td>If several applications shared a collaboration server, the message counter of the client application agent was incremented several times (once per application).
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_11 tag_18"><td><a name="9b24216d-9621-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br></td><td>Client applications running on macOS now support add-ins based on Native API.<p>The add-in technology documentation and examples are updated accordingly (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>).</p></td><td>Client applications running on macOS did not support add-ins based on Native API.</td><td>Client applications running on macOS now support add-ins.</td></tr><tr title="Версия 8.3.13" class="tag_11 tag_30 tag_31"><td><a name="2e7989a3-acf6-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>For add-ins intended to run on iOS, you can specify a set of properties to be included in the application properties (file <span class="interface">info.plist</span>). The properties required by the add-in are added by the Mobile application builder.<p>The add-in technology documentation is updated. (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>)</p></td><td>This feature was not provided.<p>Add-ins could not add properties to the <span class="interface">info.plist </span>file.</p></td><td>Development of add-ins intended to run on iOS is more convenient.
</td></tr><tr title="Версия 8.3.13" class="tag_4 tag_14"><td><a name="71fbae4c-bfcc-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>When a collaboration system notification is deleted from the notification center, the conversation is marked as read. Deleting a notification here means either deleting a single notification or clearing the notification list.</td><td>When a collaboration system notification was deleted from the notification center, the conversation was not marked as read. Deleting a notification here means either deleting a single notification or clearing the notification list.</td><td>The collaboration system behavior is more logical and predictable.</td></tr><tr title="Версия 8.3.13" class="tag_25 tag_56"><td><a name="c5f783bc-bfcf-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>When XDTO deserialization is applied to data composition parameters, only parameters that are included in the list of the available parameters of the current platform version are deserialized. No deserialization attempts are performed for parameters that are not included in the list of available ones. This ensures successful restoration of parameters.</td><td>When XDTO deserialization was applied to data composition parameters, the platform attempted to deserialize all of the serialized parameters. Attempts to restore data composition settings using an earlier platform version where the list included parameters unavailable in the current version generate errors.</td><td>You can use an earlier platform version to restore data composition schemas and data composition settings saved in a later platform version. At that, data composition parameters available only in the later version are ignored.</td></tr><tr title="Версия 8.3.13" class="compat tag_31 tag_6 tag_68 tag_1"><td><a name="4e8e926f-bfd5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>If mobile client version 8.3.12 is connected to a 1C:Enterprise server 8.3.13:<ul><li>An attempt to view the change history always opens the default change history form.</li><li>An attempt to view the change history of a constant returns an error.</li></ul><p>If mobile client version 8.3.13 is connected to a 1C:Enterprise server 8.3.12, an attempt to view the change history always opens the default change history form.</p></td><td>If mobile client version 8.3.12 was connected to a 1C:Enterprise server 8.3.13, the change history was unavailable.</td><td>Eliminated unexpected system behavior.
</td></tr><tr title="Версия 8.3.13" class="tag_19 tag_29"><td><a name="8618707c-ebf0-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>PostgreSQL version 10.3 is supported.</td><td>PostgreSQL version 10.3 was not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.13" class="compat tag_115 tag_14 tag_1"><td><a name="1547735b-bfd8-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>If a form table does not have a current row (for example, it is blank) and a column group is hidden from the table header, its parent column group is also hidden from the header.<p>If a form table has a current row and a column group is shown in the header, its nested column group is shown in the header only if the current row contains cells that belong to the nested group.</p><p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>If a form table did not have a current row (for example, it was blank) and a column group was hidden from the table header, its parent column group was shown in the header as a blank column.<p>If a form table had a current row and a column group was shown in the header, its nested column groups were always shown in the header.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="compat tag_25 tag_1"><td><a name="b1897e91-bfdb-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Predefined resource templates that describe intersections of table row groupings (template type: <span class="interface">Title </span>or <span class="interface">Footer</span>) with table column groupings (template type: <span class="interface">Grand Total Title</span> or <span class="interface">Grand Total Footer</span>) are displayed in a report even if the resource fields are not displayed in the table columns.<p>This change is not implemented in version 8.3.12 compatibility mode.</p></td><td>In data composition system tables, if resource fields were not displayed in table columns, predefined resource templates were not displayed for row totals.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_68"><td><a name="e5a0133f-bfdf-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>In a data structure that is generated by the <span class="term">DataHistoryManager.GetVersionDiff() </span>method and describes moving a table row:<ul><li>The <span class="term">RowNumberInBeforeChangeVersion </span>property contains the number that the row had before applying any of the version changes.</li><li>The <span class="term">RowNumberInAfterChangeVersion </span>contains the number that the row has after applying all of the version changes.</li></ul><p>This change is also applied to the standard version difference report.</p></td><td>In a data structure that was generated by the <span class="term">DataHistoryManager.GetVersionDiff()</span> method and described moving a table row:<ul><li>The <span class="term">RowNumberInBeforeChangeVersion </span>property contained the number that the row had after applying all of the previous changes but before applying the current change.</li><li>The <span class="term">RowNumberInAfterChangeVersion </span>contained the number that the row had after applying the current change.</li></ul></td><td>Eliminated unexpected system behavior.<p>The row numbering is now more intuitive.</p></td></tr><tr title="Версия 8.3.13" class="tag_8"><td><a name="7edba81c-c160-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>An interactive mode of password-related operations is implemented for the cryptography manager. If the cryptography manager is initialized in the interactive mode, the password to access the private key that is defined in the object is ignored, and the user is asked to enter the password. The option to remember the password is implemented. The interactive mode of the cryptography manager is supported only on the client. An attempt to use the interactive mode on the server generates an error.<p><span class="term">InteractiveModeUse </span>parameter is implemented for <span class="term">CryptoManager </span>constructor and <span class="term">CryptoManager.BeginInitialization() </span>method.</p><p>We recommend that you analyse the cases where the cryptography manager is used and implement interactive mode on the client to improve the user experience.</p></td><td>The only way to specify the password to access a private key was through the cryptography manager property. Users could not set the password themselves.</td><td>More secure and user-friendly mode of managing private key passwords is implemented.</td></tr><tr title="Версия 8.3.13" class="compat tag_115 tag_1"><td><a name="e69942ba-c165-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If a form input field contains modified data and it is not the current form item, an attempt to set its <span class="term">Visible</span>, <span class="term">Ena</span><span class="term">bl</span><span class="term">ed</span>, or <span class="term">EditText </span>property to False or set its <span class="term">ReadOnly </span>property to <span class="term">True </span>results in the following:<ul><li><span class="term">TextEditEnd </span>event handler is called.</li><li>After the <span class="term">TextEditEnd </span>event handler is completed, if the <span class="term">StandardProcessing </span>parameter is set to <span class="term">True</span>:</li></ul><p>
</p><ul><li>If a valid value is generated from the field text, the <span class="term">OnChange </span>event handler is called.</li><li>If a valid value cannot be generated from the field text, the input field value is set to the value of the attribute linked to the input field.</li></ul><p>
</p><ul><li>After the <span class="term">TextEditEnd </span>event handler is completed, if the <span class="term">StandardProcessing </span>parameter is set to <span class="term">False </span>and a valid value cannot be generated from the field text, the input field value is set to the value of the attribute linked to the input field.
</li></ul><p>If a form input field contains unmodified data and it is not the current form item, an attempt to set its <span class="term">Visible</span>, <span class="term">Enabled</span>, or <span class="term">EditText </span>property to <span class="term">False </span>or set its <span class="term">ReadOnly </span>property value to <span class="term">True </span>results in closing the drop-down list (if the list was open).
This change is not implemented in version 8.3.13 compatibility mode.</p><p>
</p></td><td>Setting the <span class="term">Visible </span>property of an input field to <span class="term">False </span>results in the following:<ul><li>If the field is linked to a text value, its value is generated from the field text and then the <span class="term">OnChange </span>event handler is called.</li><li>If the field is linked to a reference value and a user has not finished filling it, the resulting field state might be inconsistent.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.13" class="tag_31 tag_37"><td><a name="fccf8541-c168-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Mobile clients can connect to infobases over HTTPS. The infobase access parameters of the mobile client now include the client certificate source and the server certificate verification options.<p>The client certificate source can be an application certificate store or a file (for iOS and Android).</p><p>The source of root certificates for server certificate verification can be a system certificate store, application certificate store, or file (for iOS and Android).</p></td><td>This feature was not provided.</td><td>Added new mobile client features.</td></tr><tr title="Версия 8.3.13" class="tag_31 tag_115"><td><a name="392212cf-c17f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the mobile client, customization of form command bars is implemented. A new form property: <span class="term">MobileDeviceFormCommandBarContent</span>.<p>In the mobile client, the property content (unless it is blank) is displayed in the form command bar, replacing the default command bar. Including a form command bar into the <span class="term">MobileDeviceFormCommandBarContent </span>property content is not supported.</p><p>If a form group title is defined but not displayed, the title is considered when generating the title of an automatically collapsed group on the mobile client.</p></td><td>In the mobile client, form command bar customization was not supported.<p>If a form group title was defined but not displayed, the title was not considered when generating the title of an automatically collapsed group on the mobile client.</p></td><td>Form customization on the mobile client is upgraded.
</td></tr><tr title="Версия 8.3.13" class="tag_19 tag_29"><td><a name="ba2f315a-ebf0-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>PostgreSQL version 10.5 (for 32-bit and 64-bit operating systems) is supported.</td><td>PostgreSQL version 10.5 was not supported.</td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.13" class="tag_31 tag_4"><td><a name="599c0fa2-036d-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>New features for the mobile client:<ul><li>Someone-is-typing indicator.</li><li>One-on-one voice calls.</li><li>User status. Users with "Do not disturb" status do not receive push notifications.</li></ul><p>New objects supported by the mobile client:</p><ul><li><span class="term">CollaborationSystemConversation.Group </span>property.</li><li><span class="term">CurrentApplicationID()</span> method.</li></ul><p>The version of the collaboration system on the mobile client is defined by the collaboration system version on the 1C:Enterprise server.</p><p>Mobile client collaboration system features are defined by the collaboration system version on the 1C:Enterprise server and do not depend on the server version.</p></td><td>These features were not provided.</td><td>The collaboration system features on the mobile client match the features on the thin client.
</td></tr><tr title="Версия 8.3.13" class="tag_29 tag_30 tag_31"><td><a name="8397c82d-0371-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The mobile version of 1C:Enterprise supports Android 9, iOS 12, and the following Apple devices: iPhone Xs, Xs Max, and Xr.</td><td>The mobile version of 1C:Enterprise did not support Android 9 and iOS 12.<p>The mobile version of 1C:Enterprise did not support iPhone Xs, Xs Max, and Xr.</p></td><td>1C:Enterprise supports new operating systems and devices.</td></tr><tr title="Версия 8.3.13" class="tag_32"><td><a name="67d4363c-26f4-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>New: now you can manage permissions of mobile applications running under Android OS even more accurately if it is required to grant <span class="term">Telephony </span>permission in the application.<p>If the permission is required, then the builder prompts you to define which permission out of 6 ones is required by the mobile application.</p></td><td>If the application required the <span class="term">Telephony </span>permission, the mobile application builder provided the mobile application with 6 permissions at once.</td><td>Requirements for permissions that appeared in a new edition of Google Play developer rules are considered. Now you can define only the permissions required by the mobile application.</td></tr><tr title="Версия 8.3.13" class="tag_29 tag_19"><td><a name="968c8690-3c34-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented:<ul><li>Postgres Pro 1C 9.4.19,</li><li>Postgres Pro 1C 9.6.11,</li><li>Postgres Pro 1C 10.6,</li><li>Postgres Pro Enterprise 9.6.11,</li><li>Postgres Pro Enterprise 10.3.3,</li><li>Postgres Pro Enterprise 10.6,</li><li>Postgres Pro Standard 10.6.</li></ul></td><td>The following Postgres Pro DBMS versions were not supported:<ul><li>Postgres Pro 1C 9.4.19,</li><li>Postgres Pro 1C 9.6.11,</li><li>Postgres Pro 1C 10.6,</li><li>Postgres Pro Enterprise 9.6.11,</li><li>Postgres Pro Enterprise 10.3.3,</li><li>Postgres Pro Enterprise 10.6,</li><li>Postgres Pro Standard 10.6.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.13" class="tag_84"><td><a name="f840c690-4957-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Localized client application interface for Spanish (<span class="interface">es</span>).</td><td>This feature was not provided.</td><td>1C:Enterprise is available to Spanish-speaking users.</td></tr><tr title="Версия 8.3.13" class="tag_84"><td><a name="2f9d9892-4958-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Localized client application interface for Greek (<span class="interface">el</span>).</td><td>This feature was not provided.</td><td>1C:Enterprise is available to Greek-speaking users.</td></tr><tr title="Версия 8.3.13" class="tag_83"><td><a name="d43c0ad4-85d0-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 83); return false;">HTML support</a>.<br></td><td>Upon reading an HTML document using the <span class="term">HTMLReader </span>object (using the <span class="term">OpenFile()</span>, <span class="term">OpenStream()</span>, and <span class="term">SetString()</span> methods), document parsing will be stopped when the nesting reaches 1,024 tags. The user will get access to a part of the document only.</td><td>Upon reading an HTML document using the <span class="term">HTMLReader </span>object, there were no restrictions on the number of nested tags, which might lead to abnormal shutdown.</td><td>Upgrade: better system reliability upon parsing HTML documents with high tag nesting.</td></tr><tr title="Версия 8.3.13" class="tag_19"><td><a name="617ef56a-e4fd-11e9-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following DBMS are now supported (64-bit versions only):<ul><li>PostgresPro PostgreSQL 10.9.1.</li><li>PostgresPro PostgreSQL 11.4.1.</li><li>PostgresPro Standard 9.6.14.1.</li><li>PostgresPro Standard 10.9.1.</li><li>PostgresPro Standard 11.4.1.</li><li>PostgresPro Enterprise 9.6.14.1.</li><li>PostgresPro Enterprise 10.9.1.</li><li>PostgresPro Enterprise 11.4.1.</li><li>PostgresPro Enterprise 11.4.2.</li></ul></td><td>These PostgresPro DBMS versions were not supported.</td><td>More PostgresPro DBMS versions are now supported.</td></tr><tr title="Версия 8.3.13" class="tag_29 tag_19"><td><a name="9d77f1ec-3b6c-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):<ul><li>Postgres Pro 1C 9.6.16,</li><li>Postgres Pro 1C 10.11.1,</li><li>Postgres Pro 1C 11.6.1,</li><li>Postgres Pro Standard 9.6.16,</li><li>Postgres Pro Standard 10.11.1,</li><li>Postgres Pro Standard 11.6.1,</li><li>Postgres Pro Enterprise 9.6.16,</li><li>Postgres Pro Enterprise 10.11.1,</li><li>Postgres Pro Enterprise 11.6.1.</li></ul></td><td>The following Postgres Pro DBMS versions were not supported:<ul><li>Postgres Pro 1C 9.6.16,</li><li>Postgres Pro 1C 10.11.1,</li><li>Postgres Pro 1C 11.6.1,</li><li>Postgres Pro Standard 9.6.16,</li><li>Postgres Pro Standard 10.11.1,</li><li>Postgres Pro Standard 11.6.1,</li><li>Postgres Pro Enterprise 9.6.16,</li><li>Postgres Pro Enterprise 10.11.1,</li><li>Postgres Pro Enterprise 11.6.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr><tr title="Версия 8.3.13" class="tag_30"><td><a name="7eb661c2-3b97-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>When creating a secure OpenSSL connection, server certificate validation is performed using the certificates installed on the mobile device if the value of the <span class="term">CertificationAuthorityCertificates</span> parameter of the <span class="term">OpenSSLSecureConnection</span> constructor is Undefined or is of the <span class="term">OSCertificationAuthorityCertificates</span> type.
</td><td>When creating a secure OpenSSL connection, server certificate validation was not performed if the value of the <span class="term">CertificationAuthorityCertificates</span> parameter of the <span class="term">OpenSSLSecureConnection</span> constructor was Undefined or was of the <span class="term">OSCertificationAuthorityCertificates</span> type.
</td><td>Eliminated unexpected system behavior.
</td></tr><tr title="Версия 8.3.13" class="tag_29 tag_19"><td><a name="40d3c769-7810-11ea-8371-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):<ul><li>Postgres Pro 1C 9.6.17,</li><li>Postgres Pro 1C 10.12.1,</li><li>Postgres Pro 1C 11.7.1,</li><li>Postgres Pro Standard 9.6.17,</li><li>Postgres Pro Standard 10.12.1,</li><li>Postgres Pro Standard 11.7.1,</li><li>Postgres Pro Enterprise 9.6.17,</li><li>Postgres Pro Enterprise 10.12.1,</li><li>Postgres Pro Enterprise 11.7.1.</li></ul></td><td>The following Postgres Pro DBMS versions were not supported:<ul><li>Postgres Pro 1C 9.6.17,</li><li>Postgres Pro 1C 10.12.1,</li><li>Postgres Pro 1C 11.7.1,</li><li>Postgres Pro Standard 9.6.17,</li><li>Postgres Pro Standard 10.12.1,</li><li>Postgres Pro Standard 11.7.1,</li><li>Postgres Pro Enterprise 9.6.17,</li><li>Postgres Pro Enterprise 10.12.1,</li><li>Postgres Pro Enterprise 11.7.1.</li></ul></td><td>Extended list of supported DBMS.</td></tr></table><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="199f74cf-0668-11e8-a3f7-0050569f678a">Transition from the previous version to the version 8.3.13</a></h2><ul><li title="Версия 8.3.13" class="tag_0"><a name="199f74d0-0668-11e8-a3f7-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.13.
</li><li title="Версия 8.3.13" class="tag_0"><a name="199f74d1-0668-11e8-a3f7-0050569f678a"></a>Some features that are added in version 8.3.13 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.13" class="tag_0"><a name="443917ed-68b0-11e8-a3f7-0050569f678a"></a>It is recommended that you uninstall your HASP Device Driver and then install HASP Device Driver 7.63, which is a part of 1C:Enterprise distribution package.</li></ul><p><a href="#199f74c5-0668-11e8-a3f7-0050569f678a"><small>Table of contents</small></a></p><h1><a name="e4150058-9163-11e7-a3f7-0050569f678a">Version 8.3.12</a></h1><p title="Версия 8.3.12" class="tag_0"><a name="e4150064-9163-11e7-a3f7-0050569f678a"></a>Version 8.3.12 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.12" class="tag_0"><a name="8a008d75-ddae-11e8-a3f7-0050569f678a"></a>Before adapting an application to the mobile client, we recommend that you read the ITS article <a href="https://its.1c.ru/db/metod8dev#content:5948:hdoc" target="_blank">Read more</a>..</p><p title="Версия 8.3.12" class="tag_0"><a name="e2ef2035-1189-11e8-a3f7-0050569f678a"></a>Finished the beta testing of the application debug by HTTP protocol option.</p><hr></hr><ul><li><a href="#e4150059-9163-11e7-a3f7-0050569f678a">New functionality and changes</a></li><li><a href="#e415005a-9163-11e7-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#e415005b-9163-11e7-a3f7-0050569f678a">Optimization</a></li><li><a href="#e415005c-9163-11e7-a3f7-0050569f678a">Changes that affect system behavior</a></li><li><a href="#e415005d-9163-11e7-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#e415005e-9163-11e7-a3f7-0050569f678a">Renamed objects</a></li><li><a href="#e415005f-9163-11e7-a3f7-0050569f678a">Mobile version of "1C:Enterprise"</a></li><li><a href="#e4150060-9163-11e7-a3f7-0050569f678a">Library updates
</a></li><li><a href="#2a6c4180-25f6-11e8-a3f7-0050569f678a">Demo configuration changes</a></li><li><a href="#1cdb06e7-f51b-11e7-a3f7-0050569f678a">Changes made after the publication of the version
</a></li><li><a href="#e4150061-9163-11e7-a3f7-0050569f678a">Transition from the previous version to the version 8.3.12</a></li></ul><h2><a name="e4150059-9163-11e7-a3f7-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.12" class="compat tag_2 tag_1"><td><a name="10015577-9165-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.11</span> is now implemented.</td><td>Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.10 was implemented.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.11 or earlier can run on version 8.3.12 without any changes to configuration or to data structures. This allows for transition to version 8.3.12 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.11 after the transition to version 8.3.12, even if you disabled the compatibility mode (if you did, enable it again).</td></tr><tr title="Версия 8.3.12" class="tag_14"><td><a name="ccfd1039-9209-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>On 64-bit Windows, you can set the bitness of a client application at application startup.<p>In the <span class="interface">Startup window settings</span> dialog box, the option to specify the application bitness is implemented. This value is stored to the <span class="term">DefalutVersion </span>parameter of <span class="interface">1CEStart.cfg</span> file.</p><p>In the infobase properties, the option to specify the bitness of the client application used with this infobase is implemented. This value is stored to the <span class="term">AppArch</span><span class="term"> </span>parameter of <span class="interface">ibases.v8i</span> file.
The command-line option <span class="term">/AppArch</span> is implemented for the thin and thick client applications.</p></td><td>This feature was not provided.<p>On 64-bit Windows, users could not select the bitness of client applications. </p></td><td>On 64-bit Windows, the option to select the bitness of a client application is implemented.<p>You can explicitly specify a 32-bit application in scenarios where a 64-bit application cannot work properly (for example, in a scenario where 64-bit add-ins are not available).</p></td></tr><tr title="Версия 8.3.12" class="tag_38"><td><a name="ff533c01-97af-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The option to select the application area of configuration extensions, as well as activate or deactivate them, is implemented.<p>The following application areas are available: the current data area and the entire infobase.</p><p>When an extension is deactivated, it is not deleted from an infobase.</p><p>For <span class="term">ConfigurationExtension </span>object, implemented <span class="term">Scope</span> and <span class="term">Active</span> properties.</p><p>The extension activation order is changed. Extensions that are applied to the entire infobase are activated first.</p></td><td>These features were not provided.<p>Extensions were always attached to specific data areas.</p><p>Disabling extensions without deleting them was not available.</p></td><td>More configuration extension management options.<p>You can add configuration extensions to all of the infibase data areas at once. You can use this feature to apply hotfixes.</p></td></tr><tr title="Версия 8.3.12" class="tag_4"><td><a name="2fe9c252-97bc-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Automatic conversion of character sequences to pictures ("smileys") is implemented.<p>Sound alerts for the following events are implemented: new message, incoming call, waiting for reply to a video call, and end of video call.</p><p>Links to conversations, getting links to conversations, and opening links to conversations (both interactively and using <span class="term">GotoURL</span><span class="term">()</span> method) are implemented. The option to add such links to Favorites is implemented. The option to get presentations of such links using <span class="term">GetURLsPresentations</span><span class="term">()</span> method is implemented. In conversation messages, links to conversations are displayed as hyperlinks.</p><p>In the thin and thick clients for Windows, taskbar blinking upon receiving a notification is implemented.</p><p>In the main collaboration system form, a context menu is implemented for the conversation list. A context menu is implemented for collaboration system messages.</p><p>For noncontext conversations, service collaboration system messages are implemented for the following events: conversation topic changed, a user joined/left a conversation. The search ignores service messages.</p><p>The conversation participant list view is changed.</p><p>Special marking for unsent outgoing messages is implemented.</p><p>The collaboration system settings dialog box is implemented.</p><p>The user picture (avatar) editor is implemented.</p><p>The message list view is changed.</p></td><td>These features were not provided.</td><td>Improved collaboration system usability.</td></tr><tr title="Версия 8.3.12" class="tag_68"><td><a name="5e548d58-97be-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>Support of data history for charts of accounts and charts of characteristic types is implemented.<p>For <span class="term">ChartOfAccountsObject </span>and <span class="term">ChartOfCharacteristicTypesObject </span>objects, methods <span class="term">SetDataHistoryVersionComment() </span>and <span class="term">GetDataHistoryVersionComment() </span>are implemented. </p></td><td>This feature was not provided.</td><td>Data history is now available for more objects.</td></tr><tr title="Версия 8.3.12" class="tag_38"><td><a name="3886694b-97c5-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>For native and adopted extension objects, the option to generate records in all adopted registers is implemented, except for turnover accumulation registers with aggregates.</td><td>This feature was not provided.<p>Extension documents could generate records only in native information registers available in the extension.</p></td><td>Extended configuration extension capabilities.</td></tr><tr title="Версия 8.3.12" class="tag_38 tag_20 tag_40"><td><a name="673d7532-97c7-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 40); return false;">Settings storage</a>.<br></td><td>The option to store configuration extensions in configuration repositories is implemented. All of the Designer batch mode command-line options that are related to configuration repositories support configuration extensions.<p>For Designer batch mode, the following changes are implemented:</p><ul><li><span class="term">-Extension</span> parameter is implemented for the following command-line options: <span class="term">СonfigurationRepositoryAddUser</span>, <span class="term">ConfigurationRepositoryBindCfg</span>, <span class="term">ConfigurationRepositoryDumpCfg</span>, <span class="term">ConfigurationRepositoryClearCache</span>, <span class="term">ConfigurationRepositoryClearGlobalCache</span>, <span class="term">ConfigurationRepositoryClearLocalCache</span>, <span class="term">ConfigurationRepositoryCommit</span>, <span class="term">ConfigurationRepositoryCopyUsers</span>, <span class="term">ConfigurationRepositoryCreate</span>, <span class="term">ConfigurationRepositoryLock</span>, <span class="term">ConfigurationRepositoryOptimizeData</span>, <span class="term">ConfigurationRepositoryReport</span>, <span class="term">ConfigurationRepositorySetLabel</span>, <span class="term">ConfigurationRepositoryUpdateCfg</span>, <span class="term">ConfigurationRepositoryUnbindCfg</span>, and <span class="term">ConfigurationRepositoryUnlock</span>.</li><li><span class="term">ExtensionConfigurationRepository</span> value is implemented for <span class="term">-FirstConfigurationType</span> and <span class="term">-SecondConfigurationType</span> parameters of <span class="term">CompareCfg</span> command-line option.</li><li><span class="term">-FirstName</span>, <span class="term">-FirstFile</span>, <span class="term">-FirstVersion</span>, <span class="term">-FirstName</span>, <span class="term">-FirstFile</span>, and <span class="term">-FirstVersion</span> parameters are implemented for <span class="term">CompareCfg</span> command-line option.</li></ul></td><td>This feature was not provided.<p>Configuration extensions could not be stored in configuration repositories, making development unnecessarily complicated.</p></td><td>Simplified group development and versioning of configuration extensions.</td></tr><tr title="Версия 8.3.12" class="tag_38"><td><a name="48621689-9953-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Creation of enumerations in configuration extensions is now supported.</td><td>This feature was not provided.</td><td>Extended configuration extension capabilities.</td></tr><tr title="Версия 8.3.12" class="tag_37"><td><a name="3b4ada10-9869-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Moving email messages between IMAP mailboxes is now supported. Method <span class="term">InternetMail.MoveToMailbox()</span> is implemented.<p>Getting and setting flags of IMAP email messages is implemented. For <span class="term">InternetMail </span>object, methods <span class="term">GetMessageFlags()</span> and <span class="term">SetMessageFlags()</span> are implemented.</p></td><td>These features were not provided.</td><td>Extended support of IMAP email operations.</td></tr><tr title="Версия 8.3.12" class="tag_63 tag_25"><td><a name="1ffd10c6-9874-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Highlighting specific chart intervals and values is implemented. This feature is available for the following chart types: stock, open-high-low-close, all types of column charts, all types of bar charts (except for bar graph), line, step, stacked line, area (all types), scatter, bubble, radar (all types), and gauge.
<p>For <span class="term">Chart </span>object, the following properties are implemented: <span class="term">C</span><span class="term">olorP</span><span class="term">aletteDescription</span>, <span class="term">DataIntervalsColorPaletteDescri</span><span class="term">ption</span>, <span class="term">ValueDataLines</span>, <span class="term">PointDataLines</span>, <span class="term">Value</span><span class="term">DataIntervals</span>, and <span class="term">PointD</span><span class="term">ataIntervals</span>.</p><p>For <span class="term">ChartLabelArea</span>, the following properties are implemented: <span class="term">Orientation </span>and <span class="term">Angle</span>.</p><p>For data composition system objects <span class="term">DataCompositionOutputParameterValues</span>, </p><p><span class="term">DataCompositionGroupOutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance</span>, the following parameters are implemented: <span class="term">ChartType</span><span class="term">.</span><span class="term">C</span><span class="term">olorP</span><span class="term">aletteDescription</span>, <span class="term">ChartType</span><span class="term">.</span><span class="term">DataIntervalsColorPaletteDescri</span><span class="term">ption</span>, <span class="term">ChartType</span><span class="term">.</span><span class="term">ValueDataLines</span>, <span class="term">ChartType</span><span class="term">.</span><span class="term">PointDataLines</span>, <span class="term">ChartType</span><span class="term">.</span><span class="term">Value</span><span class="term">DataIntervals</span>, and <span class="term">ChartType</span><span class="term">.</span><span class="term">PointD</span><span class="term">ataIntervals</span>.</p><p>The following properties and methods of <span class="term">Chart </span>object are obsolete and not recommended for use: <span class="term">ColorPalette</span>, <span class="term">GradientPaletteStartColor</span>, <span class="term">GradientPaletteEndColor</span>, <span class="term">GradientPaletteMaxColors</span>, <span class="term">GetPalette()</span>, and <span class="term">SetPalette</span><span class="term">()</span>.</p></td><td>This feature was not provided.</td><td>Additional chart layout features are introduced.</td></tr><tr title="Версия 8.3.12" class="tag_26"><td><a name="8eb981c1-9877-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Implemented representable document batch export to the following formats: XLS (Microsoft Excel 97-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later), and ODT (OpenDocument). You can export each spreadsheet document of the batch to a separate sheet of the resulting document.<p>Implemented <span class="term">RepresentableDocumentBatchItem.Title </span>property. Use it to specify the sheet name.</p><p>Implemented <span class="term">Write() </span>and <span class="term">BeginWriting() </span>methods of <span class="term">RepresentableDocumentBatch </span>object.</p></td><td>This feature was not provided.</td><td>You can save several 1C:Enterprise spreadsheet documents to the resulting XLS, XLSX, or ODT document.</td></tr><tr title="Версия 8.3.12" class="tag_21 tag_6 tag_17"><td><a name="31eb79c5-988c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>In client/server mode, the option to set the number of background jobs that update the full-text search index is implemented. You can use requirements of functionality purpose to set the number of background jobs that update the full-text search index.<p>For <span class="term">FullTextSearchManager</span> object, the following methods are implemented: <span class="term">SetIndexingJobsCount()</span> and <span class="term">GetIndexingJobsCount()</span>.</p><p>For <span class="term">FTEXTUpd</span> technological log event, the following properties are implemented: <span class="term">MinDataId</span>, <span class="term">MemoryUsed</span>, <span class="term">BackgroundJobCreated</span>, <span class="term">JobCanceledByLoadLimit</span>, <span class="term">TotalJobsCount</span>, and <span class="term">FailedJobsCount</span>.</p></td><td>This feature was not provided.<p>The update of the full-text search index was always performed as a single background job.</p></td><td>Improved performance of full-text search index updates (especially in scenarios with full index rebuilding).</td></tr><tr title="Версия 8.3.12" class="tag_38 tag_75"><td><a name="6140e68d-988e-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 75); return false;">Distributed infobases</a>.<br></td><td>Support of configuration extensions in distributed infobases is implemented.<p>For exchange plans, <span class="term">IncludeConfigurationExtensions </span>property is implemented.</p><p>For configuration extrensions, <span class="term">UseInDistributedInfobase </span>and <span class="term">MasterNode </span>properties are implemented.</p></td><td>This feature was not provided.</td><td>Extended configuration extension usage options. You can manage the replication of configuration extensions in distributed infobases.</td></tr><tr title="Версия 8.3.12" class="tag_63"><td><a name="81781b40-9938-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>In charts, the option to manage automatic calculation of header, legend, and plot area sizes and positions is implemented. For <span class="term">ChartLegendArea</span>, <span class="term">GanttChartLegendArea</span>, <span class="term">PivotChartLegendArea</span>, <span class="term">ChartPlotArea</span>, <span class="term">GanttChartPlotArea</span>, <span class="term">PivotChartPlotArea</span>, <span class="term">ChartTitleArea</span>, <span class="term">GanttChartTitleArea</span>, and <span class="term">PivotChartTitleArea</span> objects, property <span class="term">Placement</span> is implemented.<p>Property <span class="term">ShowLegend</span> of <span class="term">Chart</span>, <span class="term">GanttChart</span>, and <span class="term">PivotChart</span> objects is deprecated.</p><p>Property <span class="term">ShowTitle</span> of <span class="term">Chart</span>, <span class="term">GanttChart</span>, and <span class="term">PivotChart</span> objects is deprecated.</p></td><td>Charts only provided the option to manage header and legend view.</td><td>Improved chart customization options.</td></tr><tr title="Версия 8.3.12" class="tag_45"><td><a name="a41e9a58-9959-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In the query language, extended support of <span class="term">UUID</span> and <span class="term">ValueStorage</span> types.<p>The option to create temporary tables based on value tables that contain columns of these types is implemented.</p><p>The option to use fields and expressions of <span class="term">UUID</span> type in queries where <span class="term">IN</span> is applied to a selection of multiple fields is implemented.</p></td><td>This feature was not provided.</td><td>Extended query language capabilities.</td></tr><tr title="Версия 8.3.12" class="tag_25"><td><a name="65009e38-995c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In data composition settings, the option to use a period addition in scenarios where the reporting period does not match a regular calendar period is implemented. You can specify month size, either a calendar month or "4-5-5". In the latter case, a year is divided into 4 quarters. Each quarter has two 4-week months and the third 5-week month.
For system enumeration <span class="term">DataCompositionPeriodAdditionType</span>, the following values are implemented:<ul><li><span class="term">YearFromBeginningOfPeriod</span></li><li><span class="term">Day</span><span class="term">FromBeginningOfPeriod</span></li><li><span class="term">QuarterFromBeginningOfPeriod</span></li><li><span class="term">Month</span><span class="term">FromBeginningOfPeriod</span></li><li><span class="term">Minute</span><span class="term">FromBeginningOfPeriod</span></li><li><span class="term">Week</span><span class="term">FromBeginningOfPeriod</span></li><li><span class="term">HalfYear</span><span class="term">FromBeginningOfPeriod</span></li><li><span class="term">Hour</span><span class="term">FromBeginningOfPeriod</span></li><li><span class="term">YearFromBeginningOfPeriod</span><span class="term">445</span></li><li><span class="term">QuarterFromBeginningOfPeriod</span><span class="term">445</span></li><li><span class="term">Month</span><span class="term">FromBeginningOfPeriod</span><span class="term">445</span></li><li><span class="term">HalfYear</span><span class="term">FromBeginningOfPeriod</span><span class="term">445</span></li></ul></td><td>The data composition system always used period additions based on calendar beginning of quarter or year.</td><td>Simplified reporting in scenarios where the reporting period does not match a regular calendar period.</td></tr><tr title="Версия 8.3.12" class="tag_115"><td><a name="770b5ea7-9964-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For managed forms, collapsible pop-up groups are implemented. When a pop-up group is collapsed, a form displays its title; clicking the title opens a pop-up window, which contains all of the group items. In a form, you can view the content of a single pop-up group at a time.<p>The option to toggle the state of collapsible and pop-up groups from 1C:Enterprise script is implemented.</p><p>The following system enumeration value is implemented: <span class="term">UsualGroupBehavior</span><span class="term">.PopUp</span>.</p><p>For managed form group extensions for usual groups, the following methods are implemented: <span class="term">IsHidden()</span>, <span class="term">Show(),</span> and <span class="term">Hide()</span>.</p><p>For managed form group extensions, <span class="term">HiddenV</span><span class="term">iew</span><span class="term">Ti</span><span class="term">tleBackgroundColor </span>property is implemented.</p></td><td>These features were not provided.</td><td>New options for grouping managed form items.</td></tr><tr title="Версия 8.3.12" class="tag_73"><td><a name="aff5ec17-9d21-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>In the optimized restructuring mechanism (version 2), added the support of restructuring configuration objects having at least one extension (that extends data) attached in any of the data areas. This is only applicable to restructuring main database configurations. Restructuring that is performed during extension updates does not use the optimized restructuring mechanism (version 2).</td><td>This feature was not provided.<p>For main database configurations, if any of the areas had an extension (that extended data) attached, the regular restructuring mechanism (version 1) was used.</p></td><td>Improved interaction between platform mechanisms.</td></tr><tr title="Версия 8.3.12" class="tag_51"><td><a name="05e459b8-9df6-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>For <span class="term">TestedFormField</span> objects that represent form items of radio button, input field, and label (with hyperlink flag set) types, method <span class="term">GetDisplayedText()</span> is implemented. It gets the text displayed on the item.<p>For <span class="term">TestedFormField</span> objects that represent form items of radio button and input field types, method <span class="term">GetChoiceListPresentation()</span> is implemented. It gets a fixed array that contains presentations of the form item choice list.</p></td><td>This feature was not provided.</td><td>Extended automated testing capabilities.</td></tr><tr title="Версия 8.3.12" class="tag_31"><td><a name="324ee4d7-9df9-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Implemented the mobile client, which is equivalent to the thin client running on a mobile device. Its interface is similar to mobile platform interface. The mobile client supports only HTTP connections to infobases. It does not support TCP connections. The exact match between the mobile client version and the server (or the web server extension) version is not required.<p>The mobile client provides online access to the majority of the features available in the thin client and in the web client. The mobile client supports all mobile device-specific features, such as camera, location, and notifications.</p><p>The collaboration system uses push notifications to deliver messages. Messages are delivered even if applications that generated them are not running or inactive.</p><p>Mobile client applications are always built to run with a specific list of configurations. Changing the assortment of configuration objects in an infobase connected to a mobile client application is not supported. You can modify a configuration without modifying the assortment of its objects. If the assortment of objects changes, you have to republish the mobile application. A mobile client application cannot run with configurations that are not in the list because of application store requirements. The mobile client uses digital configuration signatures to check whether a configuration is in the list.</p><p>Implemented automatic adjustment of configuration forms to mobile device screens. You can use new form item properties to modify the adjustment rules. In the managed form editor, implemented the form preview for mobile client mode.</p><p>In the mobile client, the list of home page forms is identical to that of the thin and web clients (but different from the list of home page forms of the mobile platform). When you start an application, it displays the first form in the list, while the other forms are available through a menu.</p><p>The mobile client supports add-ins.</p><p>The mobile client does not support interactive opening of external reports and data processors.</p><p>The mobile client can run configurations with <span class="interface">compatibility mode</span> <span class="interface">Version 8.3.7</span> or later.</p><p>In Designer, implemented commands for interactive start of the mobile client on a mobile device.</p><p>The mobile application builder can now build mobile client applications. You can select the type of application to build: a mobile client application or a mobile platform application.</p><p>Implemented <span class="term">MobileClient </span>access right. Implemented <span class="term">MobileClient </span>preprocessor command. In the Syntax Assistant, implemented a new availability option for objects, properties, and methods.</p><p>For managed forms, implemented <span class="term">CollapseItemsByImportance </span>property. For managed form items, implemented <span class="term">DisplayImportance </span>property. It affects the adjustments of the form layout. For managed form tables, implemented <span class="term">CurrentRowUse </span>and <span class="term">BehaviorOnHorizontalCompression </span>properties. For form groups, implemented <span class="term">CurrentRowUse </span>and <span class="term">AssociatedTable </span>properties. For Designer batch mode, implemented the following command-line options and parameters: <span class="term">MobileClientWriteFile </span>and <span class="term">MobileClientDigiSign </span>options <span class="term">-MobileClient </span>parameter for <span class="term">CheckModules </span>and <span class="term">CheckConfig </span>options <span class="term">-MobileClientDigiSign</span> parameter for <span class="term">CheckConfig </span>option</p><p>Changed the content of the mobile platform distribution package (<span class="interface">mobile.zip</span>). Now it contains the mobile client files required to develop and build mobile applications, as well as distribute them through application stores.</p><p>This feature is included for beta testing purpose only.
</p></td><td>This feature was not provided.<p>The mobile platform was capable of running specialized offline applications.</p></td><td>Mobile devices can be used in the new way now. You can now work online with all application features that were available on the thin client and on the web client without the significant configuration refactoring.</td></tr><tr title="Версия 8.3.12" class="tag_10"><td><a name="239ec57f-b7fa-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>In Designer batch mode, for command-line options <span class="term">CreateDistributionFiles</span> and <span class="term">CreateDistributive</span>, implemented parameter <span class="term">WarningAsError</span>.</td><td>This feature was not provided.</td><td>You can apply stricter validation rules (treat all warnings as errors) to generation of application distribution kits.</td></tr><tr title="Версия 8.3.12" class="tag_6"><td><a name="9da6b4d0-e62f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Implemented new values for session and connection attributes. They indicate the duration of cluster service calls initiated by a session or a connection. They are available in all administrative tools: the cluster console, COM connection, Java administrative API, and the administration server.<p>Implemented the following <span class="term">IInfoBaseConnectionInfo </span>object and <span class="term">ISessionInfo </span>object properties: </p><ul><li><span class="term">durationCurrentService </span>– the current cluster service operation time</li><li><span class="term">CurrentServiceName </span>– the current service name</li><li><span class="term">durationLast5MinService </span>– the total duration of cluster service calls within the last 5 minutes</li><li><span class="term">durationAllService </span>– the total duration of cluster service calls since the beginning of the session or the connection</li></ul><p>Added the same attributes to the session list, connection list, and the connection properties dialog box in the cluster console.</p><p>Added the following parameters of <span class="term">connection list</span> commands and <span class="term">session list </span>commands for the cluster service command-line utility (<span class="interface">rac</span>): <span class="term">duration-current-service</span><span class="term">, current-service-name</span>, <span class="term">duration-last-5min-service</span>, and <span class="term">duration-all-service</span>.</p></td><td>This feature was not provided.</td><td>The duration of cluster service calls initiated by a specific connection or a specific session is now available.</td></tr><tr title="Версия 8.3.12" class="tag_29 tag_14"><td><a name="f9629754-ea1c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The client application for Linux needs the 1.4.3 version or higher of the<span class="interface"> webkitgtk-3.0</span> library installed.</td><td>The client application for Linux needed the 1.4.3 version or higher of the <span class="interface">webkitgtk-1.0</span> library installed.</td><td>Unified the Linux and MacOs client applications operation.</td></tr><tr title="Версия 8.3.12" class="tag_11"><td><a name="5b7d971b-eb91-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>Implemented the new global context method <span class="term">DynamicAddInInstallationSupported</span>(). It shows whether the add-in loading is available from the current infobase.<p>The dynamic add-in loading is available only on Android mobile devices. Otherwise add-ins should be included in the mobile application and are available only from the <span class="interface">Add-in </span>type configuration templates.</p><p>The dynamic add-in loading is available in the thick client, in the thin client, and in the web client (this behavior did not change).</p></td><td>Add-ins were available only from the mobile application and you could not load them from the infobase.<p>You could not define the availability of dynamic add-in loading feature.</p></td><td>Now you can get the availability of dynamic add-in loading feature.</td></tr></table><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e415005a-9163-11e7-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.12" class="tag_115"><td><a name="53a727e9-9d24-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Keyboard navigation is now available for managed form decorations and fields, provided that they do not have the <span class="term">Hyperlink </span>flag set and they display <span class="term">FormattedString</span> values.<p>Keyboard navigation provides the option to move between hyperlinks available in a formatted string.</p></td><td>This feature was not provided.</td><td>Improved managed form usability.</td></tr><tr title="Версия 8.3.12" class="tag_28 tag_26"><td><a name="a05ce430-9d40-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the web client, implemented all of the interactive spreadsheet document editing features that are available in other clients.<p> Implemented the following spreadsheet document commands: <span class="term">AlignPictureLeft</span>, <span class="term">AlignPictureCenter</span>, <span class="term">AlignPictureRight</span>, <span class="term">AlignPictureTop</span>, <span class="term">AlignPictureMiddle</span>, <span class="term">AlignPictureBottom</span>, <span class="term">PicturesEqualWidth</span>, <span class="term">PicturesEqualHeight</span>, <span class="term">PicturesEqualSize</span>, <span class="term">DistributePicturesVertically</span>, <span class="term">DistributePicturesHorizontally</span>, <span class="term">BringPictureForward</span>, <span class="term">SendPictureBack</span>, <span class="term">PringPictureToFront</span>, and <span class="term">SendPictureToBack</span>.</p></td><td>The options for interactive editing of spreadsheet documents were limited.<p>The availability of interactive commands that affected spreadsheet document view was limited.</p><p>Displaying row and column headers and grid lines was not supported.</p></td><td>Extended interactive spreadsheet document operations in the web client.</td></tr><tr title="Версия 8.3.12" class="tag_26"><td><a name="81695cdc-9d46-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the thin client, in the paste special dialog box for spreadsheet documents, the option to include or exclude the following items is implemented:<ul><li>Merged cells</li><li>Cell pictures</li><li>Drawings</li><li>Row and column groups</li><li>Header and footer</li></ul><p>In this dialog box, the <span class="interface">All</span> check box is replaced with buttons that select and clear all of the check boxes available in the dialog box.</p></td><td>In the thin client, the paste special dialog box for spreadsheet documents did not provide the option to include or exclude the following items:<ul><li>Merged cells</li><li>Cell pictures</li><li>Drawings</li><li>Row and column groups</li><li>Header and footer</li></ul><p>In this dialog box, the <span class="interface">All</span> check box was available.</p></td><td>Extended paste special options for spreadsheet documents.</td></tr><tr title="Версия 8.3.12" class="tag_96"><td><a name="021b4142-d8fd-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In actions panel and navigation panel customization forms, the correct picture is set for <span class="interface">Move to group</span> command.</td><td>In actions panel and navigation panel customization forms, the picture of <span class="interface">Move to group</span> command was incorrect.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e415005b-9163-11e7-a3f7-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.12" class="tag_14"><td><a name="0fe39cd9-9937-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The client application interface rendering is now faster.<p>The client application load on the operating system is reduced.</p></td><td>The client application interface rendering was slower and used more operating system resources.</td><td>Improved client application usability.</td></tr><tr title="Версия 8.3.12" class="tag_120"><td><a name="1c98ca3b-9958-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>Background jobs now start faster.</td><td>Background job startup took more time.</td><td>Background jobs now start faster.</td></tr><tr title="Версия 8.3.12" class="tag_49"><td><a name="3a51a404-d8e9-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 49); return false;">Binary data</a>.<br></td><td>Optimized performance and memory usage of the following 1C:Enterprise script function:<ul><li><span class="term">GetStringFromBinaryData()</span>;</li><li><span class="term">GetStringFromBinaryDataBuffer()</span>;</li><li><span class="term">GetHexStringFromBinaryData()</span>;</li><li><span class="term">GetHexStringFromBinaryDataBuffer()</span>;</li><li><span class="term">GetBase64StringFromBinaryData()</span>;</li><li><span class="term">GetBase64StringFromBinaryDataBuffer()</span>.</li></ul></td><td>The performance and memory usage of the following 1C:Enterprise script functions were insufficient:<ul><li><span class="term">GetStringFromBinaryData()</span>;</li><li><span class="term">GetStringFromBinaryDataBuffer()</span>;</li><li><span class="term">GetHexStringFromBinaryData()</span>;</li><li><span class="term">GetHexStringFromBinaryDataBuffer()</span>;</li><li><span class="term">GetBase64StringFromBinaryData()</span>;</li><li><span class="term">GetBase64StringFromBinaryDataBuffer()</span>.</li></ul></td><td>Improved performance and stability of several functions that process binary data.</td></tr><tr title="Версия 8.3.12" class="tag_38"><td><a name="f5423dab-e4bd-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Reduced database configuration update time for configuration extensions that do not affect the database structure.</td><td>The database configuration update time was longer if the configuration extension did not affect the database structure.</td><td>Reduced database configuration update time if the update includes applying changes to the configuration extensions that do not affect the database structure.</td></tr></table><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e415005c-9163-11e7-a3f7-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.12" class="tag_63"><td><a name="b0bf7bcb-9174-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The option to display Gantt chart intervals that would occupy less than 2 pixels in the current chart scale is implemented. They are displayed as 2-pixel intervals.</td><td>In some cases, Gantt chart intervals that would occupy less than 2 pixels in the current chart scale were not displayed.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="c24fe924-97a1-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The value of<span class="term"> </span><span class="term">ResourcesAutoPosition</span> data composition system parameter does not affect how column totals are displayed in data composition system reports.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In data composition system report spreadsheets, column totals were not displayed if <span class="term">ResourcesAutoPosition</span> data composition system parameter was set to <span class="term">DontUse</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_20"><td><a name="82e71177-97a7-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In configuration comparison reports, the description of differences in <span class="term">XDTOPackages </span>properties of <span class="interface">Web service</span> object is more detailed. The report includes the list of added and removed packages (with package names included) and their namespace data.</td><td>In configuration comparison reports, the description of differences in <span class="term">XDTOPackages </span>properties of <span class="interface">Web service</span> object was less detailed.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_63 tag_26 tag_1"><td><a name="a935f17c-9866-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In black-and-white view mode:<ul><li>Charts are displayed in black-and-white mode.</li><li>Geographical schemas are displayed in black-and-white mode.</li><li>Pictures and OLE objects are displayed in grayscale.</li></ul><p>In black-and-white printing mode:</p><ul><li>Charts are printed in black-and-white mode (this behavior is not changed).</li><li>Geographical schemas are printed in black-and-white mode (this behavior is not changed).</li><li>Pictures and OLE objects are displayed in grayscale.</li></ul><p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In black-and-white view mode:<ul><li>Charts were displayed in full color.</li><li>Geographical schemas were displayed in full color.</li><li>OLE objects were displayed in full color.</li><li>SVG, EMF, and WMF pictures were displayed in full color.</li><li>Other pictures were displayed in grayscale.</li></ul><p>In black-and-white printing mode:</p><ul><li>Charts were printed in black-and-white mode.</li><li>Geographical schemas were printed in black-and-white mode.</li><li>OLE objects were printed in full color.</li><li>SVG, EMF, and WMF pictures were printed in full color.</li><li>Other pictures were printed in grayscale.</li></ul></td><td>For spreadsheet document objects, eliminated differences between black-and-white view and black-and-white printing.</td></tr><tr title="Версия 8.3.12" class="compat tag_63 tag_1"><td><a name="1a590597-9953-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The background patterns used in black-and-white chart printing are based on original chart colors. If a pattern based on an original color is already in use, the next available pattern is used instead. The total number of available patterns in increased to 27.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>The background patterns used in black-and-white chart printing were based on original chart colors (no check for duplicate patterns). The total number of available patterns was 12.</td><td>Improved chart view for black-and-white printing.</td></tr><tr title="Версия 8.3.12" class="compat tag_62 tag_1"><td><a name="21c78f0a-9867-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>During a configuration update, the platform checks whether the <span class="term">Group </span>property of external data source cube commands and external data source dimension table commands is filled. If the property is not filled, the update is canceled.<p>This change is not implemented in 8.3.11 compatibility mode. </p></td><td>During a configuration update, the platform did not check whether the <span class="term">Group </span>property of external data source cube commands and external data source dimension table commands was filled.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_68 tag_38"><td><a name="b3d56f6f-988c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Support of data history is added to native and adopted extension objects.</td><td>Native and adopted extension objects did not support data history.</td><td>Data history is available for configuration extensions.</td></tr><tr title="Версия 8.3.12" class="tag_26"><td><a name="b3657c01-995a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In spreadsheet document headers and footers, the option to specify the first page number is implemented.<p>The following property is implemented: <span class="term">SpreadsheetDocument.FirstP</span><span class="term">ageNumber</span>. In the spreadsheet document headers and footers dialog box, the option to specify the first page number is implemented.</p><p>When a spreadsheet document is exported to OpenXML or OpenDocument format, the first page number is exported to the respective document property.</p></td><td>This feature was not provided.<p>The number of the first page was always 1.</p></td><td>You can generate spreadsheet documents that match the requirements of regulatory authorities.</td></tr><tr title="Версия 8.3.12" class="tag_37"><td><a name="d09350c4-9962-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The platform no longer uses the imaplib library.<p>The behavior of <span class="term">InternetMail</span> object is not changed. The functionality previously provided by the library is now provided by the platform.</p></td><td>1C:Enterprise used the imaplib library, which provided a part of <span class="term">In</span><span class="term">ternetMail</span> object functionality in compatibility modes <span class="interface">Version 8.</span><span class="interface">3.</span><span class="interface">5</span> and earlier.</td><td>Improved platform stability and security.</td></tr><tr title="Версия 8.3.12" class="tag_21 tag_96"><td><a name="1cb3ca0f-9965-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The standard full-text search form is updated.<p>The <span class="term">History</span> picture is added to the picture library.</p></td><td>The standard full-text search form looked differently.</td><td>Improved usability of the standard full-text search form.</td></tr><tr title="Версия 8.3.12" class="tag_20"><td><a name="cbc61bb7-9c54-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The following features are added to the managed form editor:<ul><li>In the device selection menu (for mobile device view), the current device is marked.</li><li>In the scale selection menu (for mobile device view), the current scale is marked. Scale options similar to scale options for personal computers are implemented in this menu.</li><li>In the scale selection menu (for personal computer view), the current scale is marked.</li><li>In the resolution selection menu (for personal computer view), the following features are implemented:</li><ul><li>Information about the current resolution.</li><li>The option to select a display (the one where the Designer window is displayed).</li><li>Information about typical DPI for each resolution.</li><li>The option to select display resolutions 4K (3840*2160 pixels) and 5K (5120*2880 pixels).</li></ul></ul></td><td>These features were not provided.</td><td>Improved form editor usability.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="a5dc9299-9c58-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a query parameter belongs to a query language expression that has a name, or the parameter is an independent expression, it is available for use in data composition system data parameteres (however, it is not visible to end users).<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>If a query parameter belonged to a query language expression that had a name, or the parameter was an independent expression, it was not included in the list of available data parameters of the data composition system.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_43 tag_1"><td><a name="1dfec2e6-9c59-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>If a column of a table linked to a dynamic list belongs to a column group with <span class="interface">In cell</span> grouping, in a document generated using the <span class="interface">Output list</span> command, the column header is taken from the managed form table column header.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>If a column of a table linked to a dynamic list belonged to a column group with <span class="interface">In cell</span> grouping, in a document generated using the <span class="interface">Output list</span> command, the column header was:<ul><li>In the thin client, the form table column name.</li><li>In the web client, the form table column header.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_51"><td><a name="386decf9-9c73-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>The option to set and get timeouts for automated testing operations is implemented.<p>For <span class="term">TestedApplication</span> object, methods <span class="term">SetActionTimeout</span><span class="term">()</span> and <span class="term">GetActionT</span><span class="term">imeout</span><span class="term">()</span> are implemented.</p><p>Clarified wordings of error messages related to attempts to connect to and/or operate applications being tested.</p></td><td>The option to set and get timeouts for automated testing operations was not available.<p>Wordings of error messages related to attempts to connect to and/or operate applications being tested were less detailed and less accurate.</p></td><td>You can set timeouts for automated testing operations.<p>Improved diagnostics for automated testing errors.</p></td></tr><tr title="Версия 8.3.12" class="compat tag_26 tag_1"><td><a name="07ee8d97-9c7c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>If a spreadsheet document has docked rows or columns, the lines that outline the docked areas are only displayed after the document has been scrolled vertically (for rows) or horizontally (for columns).<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>If a spreadsheet document had docked rows or columns, the lines that outlined the docked areas were always displayed.</td><td>Improved report view.</td></tr><tr title="Версия 8.3.12" class="compat tag_115 tag_1"><td><a name="e6d5b294-9d29-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If the width specified for a managed form group is less than the total width of its subordinate items (at their minimum possible sizes), the specified width value is ignored. Instead, the width is calculated as follows:<ul><li>For vertical groupings, the maximum value among the minimum width values of subordinate items.</li><li>For horizontal groupings, the sum of minimum width values of all subordinate items plus the total width of gaps between them.</li></ul><p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>If the width specified for a managed form group was too small and some of the subordinate items could not fit even at their minimum possible sizes, the group still had the specified width.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_45"><td><a name="07447ddf-9d4c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>An attempt to execute a query that contains a nested query with <span class="term">AUTOORDER</span> keyword generates the following error: <span class="interface">Nested queries cannot contain AUTOORDER</span><span class="interface"> operation</span>.</td><td>An attempt to execute a query that contained a nested query with <span class="term">AUTOORDER</span> keyword generated the following error: <span class="interface">Nested queries cannot contain ORDER BY operation without TOP construction</span>.</td><td>The error message is more accurate.</td></tr><tr title="Версия 8.3.12" class="tag_38"><td><a name="5eb3347b-9d4f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Notifications related to applying configuration extensions have <span class="interface">Important</span> status. Therefore, they are available in the notification center and users who miss them can read them later.</td><td>Notifications related to applying configuration extensions had <span class="interface">Information</span> status. Therefore, they were not available in the notification center and, if errors occurred when applying configuration extensions, users who missed the notifications at the time they were generated missed them completely.</td><td>Better diagnostics of errors related to applying configuration extensions.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_43 tag_1"><td><a name="23c51b38-9df1-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>When a new parameter that is a part of <span class="term">IN</span> clause is added to a data set query, the data composition schema wizard automatically sets the option to use a value list as the parameter value.<p>If a description of a query parameter that is a part of <span class="term">IN</span> clause is missing from a data composition schema, the option to use a value list as the parameter value is automatically added to the available parameter of the source of available data composition settings.</p><p>If a parameter of a dynamic list query is a part of <span class="term">IN</span> clause, you can assign a value of value list type to this parameter in the dynamic list composition settings, and the dynamic list will pass the correct value list to the query.</p><p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>The data composition schema wizard did not automatically set the option to use a value list as the value of a data composition schema parameter.<p>If a parameter description was missing from a data composition schema, only a single value could be used as the parameter value.</p><p>Dynamic lists processed query parameters of value list type incorrectly.</p></td><td>Eliminated unexpected system behavior.<p>Improved data composition system behavior in scenarios where queries use value lists to set filters.</p></td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="7166b658-a75c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the data composition system, header templates (available for reports, tables, groupings, and charts) are not followed by blank line templates. As a result, a table or a chart header is always followed by a single blank line.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In the data composition system, header templates (available for reports, tables, groupings, and charts) were followed by blank line templates. As a result, a table or a chart header was always followed by two blank lines.</td><td>Eliminated unexpected system behavior.<p>A table or a chart header is now followed by a single blank line instead of two blank lines.</p></td></tr><tr title="Версия 8.3.12" class="tag_12"><td><a name="f517bb7e-a75c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>In the standard full-text search management function, the option to set the maximum size of objects to be indexed and the option to set the number of background jobs used for indexing are implemented.<p>To set these parameters, use the dialog box that is opened using the <span class="interface">Additional parameters</span> button of the standard full-text search management function form.</p></td><td>This feature was not provided.</td><td>You can specify additional parameters for full-text search indexing.</td></tr><tr title="Версия 8.3.12" class="compat tag_26 tag_1"><td><a name="9e12dae9-b25e-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the thin client, when a spreadsheet document is saved to a PDF file, if the spreadsheet page size is not specified, the page size setting of the current printer is used instead.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In the thin client, when a spreadsheet document was saved to a PDF file, if the spreadsheet page size was not specified, size A4 was used instead.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_64 tag_1"><td><a name="50f7557a-b30f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>In Designer, thin client, and thick client, in the font selection dialog box, when you select a font by name (for example, "Arial"), the <span class="interface">Scale</span> value is applied to the resulting font. <p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In Designer, thin client, and thick client, in the font selection dialog box, when font was selected by name (for example, "Arial"), the <span class="interface">Scale</span> value was not applied to the resulting font.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="d5de74c2-b318-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag does not set that flag to its parent parameter.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag also set that flag to its parent parameter.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_115"><td><a name="ae196e88-c469-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the property palette, the field linked to the font property displays the font name, style, appearance (bold, italic, or strikethrough), and scale.</td><td>In the property palette, the field linked to the font property displays the font name and style.</td><td>You can view the current font parameters in the property palette, without opening the font dialog box.</td></tr><tr title="Версия 8.3.12" class="tag_115"><td><a name="f97d8d84-e498-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Implemented the new <span class="term">AlwaysHorizontal </span>value of the <span class="term">ChildFormItemsGroup </span>system enum.<p>The <span class="term">Horizontal </span>value of the <span class="term">ChildFormItemsGroup </span>system enum is deprecated</p><p>If the <span class="term">Horizontal </span>value is used in the application, the PC platform wil use the <span class="term">AlwaysHorizontal </span>value, and the mobile platform – the <span class="term">HorizontalIfPossible </span>value instead.</p><p>We recommend to replace the <span class="term">Horizontal </span>by the <span class="term">HorizontalIfPossible </span>value in applications in most cases. The <span class="term">AlwaysHorizontal </span>value should be used only if a group must be horizontal on any screen, including mobile device screens. For example, if there is a group with an input field and a button with a picture and without text, linked to this field. </p></td><td>The following options of horizontal alignment of forms and form groups were available: <span class="term">Horizontal </span>and <span class="term">HorizontalIfPossible</span>.</td><td>The smooth conversion of previously created form to the mobile client usage is available.</td></tr></table><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e415005d-9163-11e7-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.12" class="compat tag_40 tag_1"><td><a name="6c8a675c-9172-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 40); return false;">Settings storage</a>.<br></td><td>If a report form is opened with <span class="term">UserSettingsKey</span> parameter specified and <span class="term">UserSettings</span> parameter missing:<ul><li>If settings with the specified key are found in the user settings storage, these settings are loaded.</li><li>Otherwise the default user settings for the current report option are loaded.</li></ul><p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>If a report form was opened with <span class="term">UserSettingsKey</span> parameter specified and <span class="term">UserSettings</span> parameter missing:<ul><li>If user settings for the current report option were found in the system settings storage, these settings were loaded.</li><li>Otherwise, if settings with the specified key were found in the user settings storage, these settings were loaded.</li><li>Otherwise the default user settings for the current report option were loaded.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_70"><td><a name="9292a19e-96e6-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>1C:Enterprise launcher searches for distribution packages of new 1C:Enterprise versions in the following directories: <span class="interface">Setup</span> (32-bit platform) and <span class="interface">Setup64full</span><span class="interface"> </span>(64-bit platform).</td><td>1C:Enterprise launcher searched for distribution packages of new 1C:Enterprise versions only in directories that contained specific versions (ignoring subdirectories).</td><td>Automatic client application updates support scenarios where client applications are both 32-bit and 64-bit.</td></tr><tr title="Версия 8.3.12" class="compat tag_63 tag_1"><td><a name="5221704c-97a3-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>When <span class="term">OnIntervalEditEnd</span> handler of a form item that displays a Gantt charts is executed:<ul><li>The chart interval is passed to <span class="term">Interval</span> handler parameter.</li><li>If <span class="term">CancelEdit</span> handler parameter is set to <span class="term">False</span>, all of the interval values are applied to the chart.</li><li>If <span class="term">CancelEdit</span> handler parameter is set to <span class="term">True</span>, interval properties <span class="term">Begin</span> and <span class="term">End</span> are not applied to the chart, while the rest of the interval properties are applied.</li></ul><p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>When <span class="term">OnIntervalEditEnd</span> handler of a form item that displays a Gantt charts was executed:<ul><li>A copy of the chart interval was passed to <span class="term">Interval</span> handler parameter.</li><li>The changes made in the passed interval were not applied to the chart.</li></ul></td><td>The behavior of <span class="term">OnIntervalEditEnd</span> handler of form items that display Gantt charts is more logical.</td></tr><tr title="Версия 8.3.12" class="tag_39"><td><a name="b398b60e-9891-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>Interactive editing of event log format is implemented.<p>The new event log event <span class="term">_$InfoBase$_.EventLogSettingsUpdate </span>indicates the format change.</p><p>In file infobases, changing event log format requires exclusive infobase access.</p><p>Global context method <span class="term">ClearEventLog</span><span class="term">()</span> is deprecated and only applicable to logs that have SQLite format. It is recommended that you do not use this method.
If selection from event log records takes a long time, you can abort it by deleting the session that initiated the selection.</p><p>The following limitations are applied to time-consuming selections from the event log:</p><ul><li>In a nonseparated infobase: 4 sessions.</li><li>In a separated infobase: 1 session per data area.</li></ul><p>The default event log format (the one that is selected in newly created infobases) is sequential format.</p></td><td>Interactive editing of event log format was not available.<p>The default event log format (the one that was selected in newly created infobases) was SQLite format. </p></td><td>Interactive selection of event log format is now available.<p>Applications no longer stop responding when performing time-consuming selections from the event log.</p></td></tr><tr title="Версия 8.3.12" class="compat tag_127 tag_1"><td><a name="005224b9-993b-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 127); return false;">Temporary storages</a>.<br></td><td>If the <span class="term">Address</span> parameter of <span class="term">PutToTempStorage</span><span class="term">()</span> method contains a value that was previously used in <span class="term">DeleteFromTempStorage</span><span class="term">()</span> method, an exception is generated. <p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>If an <span class="term">Address</span> parameter value was previously used in <span class="term">PutToTempStorage</span><span class="term">()</span> method and then in <span class="term">DeleteFromTempStorage</span><span class="term">()</span> method, an attempt to use the value in <span class="term">PutToTempStorage</span><span class="term">()</span> method again was only successful if it was a UUID of a form that was open at that time.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_63 tag_1"><td><a name="0aaac274-9c62-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The algorithm of displaying stacked charts that have negative values is changed:<ul><li>For charts that support base values:</li><ul><li>For each point, calculate two sums: one less than the base value, the other one greater than the base value.</li><li>Before stacking, subtract the base value from the current value.</li><li>Stack the resulting value to one of the sums, depending on its sign.</li></ul><li>For charts that do not support base values:</li><ul><li>For each point, calculate two sums: a negative one and a positive one.</li><li>Stack the current value to one of the sums, based on its sign.</li></ul><li>For each point, display two chart columns that represent the two sums.</li></ul><p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In stacked charts, each point had a single column that represented the sum of all values (calculated with appropriate signs).</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="688a7894-9c7a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In data composition settings composer, when the source of user-defined settings is specified, if a data parameter value contains an array and the option to use a value list in this parameter is enabled, the parameter value is set to a value list containing all of the values from the source array. <p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In data composition settings composer, when the source of user-defined settings was specified, if a data parameter value contained an array and the option to use a value list in this parameter was enabled, the parameter value was set to a value list containing a single value (the default value for the parameter value type).</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_115 tag_1"><td><a name="60320261-9c80-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When form item properties <span class="term">DataPath</span>, <span class="term">FooterDataPath</span>, <span class="term">HeaderDataPath</span>, <span class="term">TitleDataPath</span>, and <span class="term">RowPictureDataPath</span> are set from 1C:Enterprise script or a configuration with these properties is loaded from a file, if any of these properties contains a path that refers to a form item that has a row index, an error is generated.<p>This change is not implemented in 8.3.11 compatibility mode.</p><p>
</p></td><td>When form item properties <span class="term">DataPath</span>, <span class="term">FooterDataPath</span>, <span class="term">HeaderDataPath</span>, <span class="term">TitleDataPath</span>, and <span class="term">RowPictureDataPath</span> were set from 1C:Enterprise script or a configuration with these properties was loaded from a file, if any of these properties contained a path that referred to a form item that had a row index, no errors were generated. Such property values were set but they were actually ignored.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_43 tag_1"><td><a name="44172636-a75f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as <span class="term">Ref.Products.Product.[S</span><span class="term">tate</span><span class="term"> of origin]</span>) are not available for filtering, sorting, or grouping.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as <span class="term">Ref.Products.Product.[S</span><span class="term">tate</span><span class="term"> of origin]</span>) were available for filtering, sorting, or grouping. However, an attempt to set a filter by a value of such field returned an error.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="c11184bf-b24c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If an expression of a calculated data composition system field is empty, <span class="term">NULL</span> is substituted for the field value in detailed records.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>If an expression of a calculated data composition system field was empty, an attempt to use the field in detailed records generated a "field not found" error.</td><td>Eliminated unexpected system behavior.<p>The system behavior is improved in scenarios where a user selects a custom field with no expression specified.</p></td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="1690a2b5-b252-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If calculation of <span class="term">EvalExpression</span><span class="term">()</span> function result includes division by 0, the result of the expression calculated with this function is <span class="interface">D</span><span class="interface">ivision by zero</span>.<p>This change is not implemented in 8.3.11 compatibility mode.</p></td><td>If calculation of <span class="term">EvalExpression</span><span class="term">()</span> function result included division by 0, the expression calculated with this function was fully calculated (<span class="interface">Division by z</span><span class="interface">ero </span>was used as the function result).</td><td>Eliminated unexpected system behavior.
</td></tr><tr title="Версия 8.3.12" class="tag_40"><td><a name="314e1025-b258-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 40); return false;">Settings storage</a>.<br></td><td>Each operation with the standard settings storage includes a check for <span class="term">SaveUserData </span>access right.<p>Calls of <span class="term">StandardSettingsStorageManager</span><span class="term">.</span><span class="term">SetDescription</span><span class="term">()</span> method include a check for <span class="term">SaveUserData </span>access right.</p></td><td>Operations with the standard settings storage included checks for <span class="term">SaveUserData </span>access right only if they were performed from 1C:Enterprise script.<p>Calls of <span class="term">StandardSettingsStorageManager</span><span class="term">.</span><span class="term">SetDescription</span><span class="term">()</span> method did not include a check for <span class="term">SaveUserData </span>access right.</p></td><td>Eliminated unexpected system behavior. In particular, commands related to dynamic list settings are no longer available to users that do not have <span class="term">SaveUserData </span>access right.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="c2485f98-bd52-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Items of conditional appearance of data composition system are applied using the following rules:<ul><li>More specific conditional appearance items have higher priorities (this behavior did not change).For example, if a report, a table, and a table grouping have conditional appearances, they are prioritized as follows: table grouping (the highest priority), table, and report (the lowest priority).</li><li>Parts of a conditional appearance item are prioritized in accordance with their relative positions in the list: the lower the position, the higher the priority.</li></ul><p>This change is not implemented in version 8.3.11 compatibility mode.
</p></td><td>Items of conditional appearance of data composition system were applied using the following rules:<ul><li>More specific conditional appearance items had higher priorities.</li><li>Parts of a conditional appearance item were prioritized in accordance with their relative positions in the list—the lower the position, the higher the priority.The only exception to this rule was the list of conditional appearance items that included parts with specified filters and specified or unspecified formatted fields. In this case the conditional appearance items with formatted fields specified were applied first.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="e93802c2-bd54-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field affects the filter presentation.<p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td>In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field did not affect the filter presentation.</td><td>Improved filter presentations in dynamic lists and data composition system-based reports.</td></tr><tr title="Версия 8.3.12" class="tag_93"><td><a name="3a76c9df-bd76-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br></td><td>When administrative infobase parameters are set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior is different from that of the previous versions. For details, see 1C:Enterprise documentation.</td><td>When administrative infobase parameters were set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior was different. This behavior was not documented.</td><td>Setting administrative infobase parameters is more intuitive and predictable.</td></tr><tr title="Версия 8.3.12" class="compat tag_96 tag_1"><td><a name="bc742f2b-c455-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In managed applications, calls of <span class="term">SwitchInterface() </span>global context method are ignored in all client modes. We recommend that you do not use ordinary forms in managed client application mode. This change is not implemented in version 8.3.11 compatibility mode.</td><td>In managed applications, calls of <span class="term">SwitchInterface() </span>global context method displayed command bars.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_69 tag_1"><td><a name="4cbacfbf-c465-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>When <span class="term">CurrentLanguage()</span> global context function is called on the server, in the thick client, or in an external connection, it returns the interface language of the current user. If the current user is not specified, or the interface language is not specified, or the specified interface language is not included in the configuration, the function returns the default configuration language.<p>The <span class="term">CurrentLanguage()</span> function behavior is now uniform across all modes.</p><p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td>When <span class="term">CurrentLanguage() </span>global context function was called on the server, in the thick client, or in an external connection, if the interface language specified for the current user was not included in the configuration, the function returned <span class="term">Undefined</span>.<p>The <span class="term">CurrentLanguage()</span> function behavior on the client and on the server was not uniform.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="a8005c7c-d8e8-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In a nested query included in the right part of a left join, its <span class="term">WHERE </span>section does not include an explicitly specified field, and the parent query includes a different field with the same data composition name, the template composer does not include the filter to the nested query.<p>To preserve the previous query behavior, explicitly specify a field in the <span class="term">WHERE </span>section.</p><p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td>When filling available data set fields, the template composer always included the filter in the nested query.</td><td>The result of automatic filling of available data set fields is more predictable.</td></tr><tr title="Версия 8.3.12" class="tag_37"><td><a name="430982fe-e008-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>In <span class="term">InternetMail.Logon()</span> method, implemented authentication request with the user name and password if APOP authentication fails.</td><td>The <span class="term">InternetMail.Logon() </span>method generated an exception if APOP authentication failed. The authentication attempt with the user name and password was not performed.</td><td>The user authentication on the mail server better complies with RFC 1939 standard.</td></tr><tr title="Версия 8.3.12" class="compat tag_115 tag_1"><td><a name="2d3d4513-e00b-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In <span class="term">OpenForm() </span>method, changed the algorithm of searching for an open form instance.<ul><li>When a data processor form or a report form is opened, the search algorithm analyzes the owner of that form.</li><li>When a main object form specified in the configuration or the overriding form specified in <span class="term">FormGetProcessing() </span>handler is opened, if its owner is not specified, the owner window is not blocked, and a form instance is already open, the search will find it (in the thin and web clients).</li></ul><p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td>The following algorithm of searching for an open form instance was used.<ul><li>When a data processor form or a report form was opened, the search algorithm did not analyze the owner of that form.</li><li>When a main object form specified in the configuration or the overriding form specified in <span class="term">FormGetProcessing() </span>handler was opened, if its owner was not specified, the owner window was not blocked, and a form instance was already open, a new form instance was opened (in the thin and web clients).</li></ul></td><td>Eliminated unexpected system behavior. Unified the algorithm that searches for an open form in different client application modes.</td></tr></table><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e415005e-9163-11e7-a3f7-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.12" class="tag_0"><td><a name="e3c7a284-985e-11e7-a3f7-0050569f678a"></a>Parameters of <span class="term">CompareCfg</span> command-line option of Designer batch mode that define the first and second configurations to be used in a comparison.</td><td><ul><li><span class="term">FirstConfigurationKey</span></li><li><span class="term">Second</span><span class="term">ConfigurationKey</span></li></ul></td><td><ul><li><span class="term">FirstConfigurationType</span></li><li><span class="term">SecondConfigurationType</span></li></ul></td></tr><tr title="Версия 8.3.12" class="tag_0"><td><a name="36adbd1b-cac0-11e7-a3f7-0050569f678a"></a>Batch Designer mode command-line options that apply to mobile device applications. The former names are supported for compatibility purposes.</td><td><ul><li><span class="term">MAUpdatePublication</span>;</li><li><span class="term">MAWriteFile</span>.</li></ul></td><td><ul><li><span class="term">MobileAppUpdatePublication</span>;</li><li><span class="term">MobileAppWriteFile</span>.</li></ul></td></tr><tr title="Версия 8.3.12" class="tag_0"><td><a name="eb6f34be-dfea-11e7-a3f7-0050569f678a"></a>Configuration and managed form use purposes. The former names are supported for compatibility purposes.</td><td><ul><li><span class="term">MobileDevice</span></li><li><span class="term">PersonalComputer</span></li></ul></td><td><ul><li><span class="term">MobilePlatformApplication</span></li><li><span class="term">PlatformApplication</span></li></ul></td></tr><tr title="Версия 8.3.12" class="compat tag_0 tag_1"><td><a name="a7d981d7-e0da-11e7-a3f7-0050569f678a"></a>Spreadsheet document command groups.<p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td><ul><li><span class="term">Print</span></li><li><span class="term">View</span></li><li><span class="term">Format</span></li><li><span class="term">Font</span></li><li><span class="term">Borders</span></li><li><span class="term">Alignment</span></li><li><span class="term">Groups</span></li><li><span class="term">Names</span></li><li><span class="term">PrintOptions</span></li><li><span class="term">Pictures</span></li><li><span class="term">Alignment1</span></li><li><span class="term">Size</span></li><li><span class="term">Distribute</span></li><li><span class="term">Order</span></li><li><span class="term">Comments</span></li><li><span class="term">Cells</span></li><li><span class="term">Merging</span></li><li><span class="term">Insert</span></li><li><span class="term">InsertCells</span></li><li><span class="term">InsertColumns</span></li><li><span class="term">ShowHideCells</span></li><li><span class="term">Sizes</span></li><li><span class="term">Other</span></li><li><span class="term">Other1</span></li><li><span class="term">Other2</span></li><li><span class="term">Other3</span></li></ul></td><td><ul><li><span class="term">CommandsPrint</span></li><li><span class="term">CommandsView</span></li><li><span class="term">CommandsFormat</span></li><li><span class="term">CommandsFont</span></li><li><span class="term">CommandsBorders</span></li><li><span class="term">CommandsAlignment</span></li><li><span class="term">CommandsGroups</span></li><li><span class="term">CommandsNames</span></li><li><span class="term">CommandsPrintOptions</span></li><li><span class="term">CommandsPictures</span></li><li><span class="term">CommandsPisturesAlignment</span></li><li><span class="term">CommandsSize</span></li><li><span class="term">CommandsDistribute</span></li><li><span class="term">CommandsOrder</span></li><li><span class="term">CommandsComments</span></li><li><span class="term">CommandsCells</span></li><li><span class="term">CommandsMerging</span></li><li><span class="term">CommandsInsert</span></li><li><span class="term">CommandsInsertCells</span></li><li><span class="term">CommandsInsertColumns</span></li><li><span class="term">CommandsShowHideCells</span></li><li><span class="term">CommandsSizes</span></li><li><span class="term">CommandsOther</span></li><li><span class="term">CommandsOtherUndo</span></li><li><span class="term">CommandsOtherClipboard</span></li><li><span class="term">CommandsOtherProperties</span></li></ul></td></tr></table><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e415005f-9163-11e7-a3f7-0050569f678a">Mobile version of "1C:Enterprise"</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.12" class="tag_115"><td><a name="ebfc799c-9965-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>On Android, context menus are displayed next to the items where they belong. Opening a context menu does not change the form layout.</td><td>The context menu was displayed at the top of a form. Opening a context menu changed the form layout and repositioned form items.</td><td>On Android, improved usability of accessing context menus of form items.</td></tr><tr title="Версия 8.3.12" class="tag_48"><td><a name="335edac4-9df2-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Optimized <span class="term">MultimediaData </span>object generation algorithm used during device camera operations.</td><td>The <span class="term">MultimediaData </span>object generation algorithm used during device camera operations was not optimal.</td><td>Improved performance of device camera operations in mobile applications.</td></tr><tr title="Версия 8.3.12" class="tag_96"><td><a name="d39e5b10-e003-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>Changed the calendar view on mobile devices:<ul><li>Better visibility of the current date</li><li>Implemented switching between single and multiple date choices</li><li>Added the context menu</li><li>Added the <span class="term">Choice </span>event</li></ul></td><td>The calendar view on the mobile device was different:<ul><li>The current date marking was more subtle</li><li>Switching between single and multiple date choices was unavailable (only multiple date choice was available)</li><li>No context menu</li><li>No <span class="term">Choice </span>event</li></ul></td><td>Improved calendar usability on mobile devices.</td></tr></table><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e4150060-9163-11e7-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.12" class="tag_0"><a name="bb0b7a7d-3e35-11e8-a3f7-0050569f678a"></a>The OpenSSL library is updated to version 1.1.0h.</li></ul><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="2a6c4180-25f6-11e8-a3f7-0050569f678a">Demo configuration changes</a></h2><ul><li title="Версия 8.3.12" class="tag_0"><a name="1417d811-25f9-11e8-a3f7-0050569f678a"></a>The demo configuration was renamed. New name is <span class="interface">Demo application</span>.<p>
</p></li><li title="Версия 8.3.12" class="tag_0"><a name="fef77d37-30da-11e8-a3f7-0050569f678a"></a>All documents in the demo application were dated the current year.</li></ul><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="1cdb06e7-f51b-11e7-a3f7-0050569f678a">Changes made after the publication of the version
</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.12" class="tag_28"><td><a name="a0111a9f-00f3-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Implemented the following features for file system extensions for Google Chrome and Mozilla Firefox:<ul><li>Web server certificate authentication (users are prompted to select the authentication certificate).</li><li>Operating system authentication in the following scenario: a computer that runs the web client is not included in a domain, and the web server supports operating system authentication (users are prompted to specify the domain user name and password).</li></ul></td><td>File system extensions for Google Chrome and Mozilla Firefox did not support the following:<ul><li>Web server certificate authentication.</li><li>Operating system authentication in the following scenario: a computer that runs the web client is not included in a domain, and the web server supports operating system authentication.</li></ul></td><td>Improved secure connection support. Improved web client security.</td></tr><tr title="Версия 8.3.12" class="compat tag_28 tag_1"><td><a name="45a101f7-00f5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client, dragging spreadsheet document cells and pictures is implemented. If <span class="interface">Ctrl </span>is held down, they are copied, otherwise they are moved.<p>The web client behavior is now identical to the thin client behavior.</p><p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td>In the web client, dragging spreadsheet document cells and pictures was not supported.</td><td>New interactive spreadsheet document operations in the web client.</td></tr><tr title="Версия 8.3.12" class="compat tag_51 tag_1"><td><a name="08b2057a-00ef-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>If <span class="term">TestedFormField </span>or a similar object is retrieved using <span class="term">FindObject() </span>or <span class="term">FindObjects() </span>method, its <span class="term">TitleText</span> property always stores the title value set in Designer.<p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td>If <span class="term">TestedFormField</span> or a similar object was retrieved using <span class="term">FindObject() </span>or <span class="term">FindObjects() </span>method, if its title was explicitly specified in the form editor, a colon might be missing from the title.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_115 tag_1"><td><a name="0c239701-fd10-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Changing the Enabled property of managed form item groups and form items in managed form tables does not require server calls.<p>Setting the <span class="term">Visible </span>property of an input field to <span class="term">False </span>results in the following:</p><ul><li>If the field is linked to a text value, its value is generated from the field text and then the <span class="term">OnChange </span>event handler is called.</li><li>If the field is linked to a reference value and a user has not finished filling it, the resulting field state might be inconsistent.</li></ul><p>This change is not implemented in 8.3.11 version compatibility mode.</p></td><td>Changing the Enabled property of managed form item groups and form items in managed form tables required a server call.<p>Setting the <span class="term">Visible </span>property of an input field to <span class="term">False </span>resulted in the following:</p><ul><li>If the field was linked to a text value, its value was generated from the field text, but the OnChange event handler was not called.</li><li>If the field was linked to a reference value, its previous value was restored. </li></ul></td><td>Changing the visibility of some managed form items is optimized.</td></tr><tr title="Версия 8.3.12" class="tag_30 tag_31"><td><a name="887e55c8-00f8-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Implemented the following features of the applications list in the mobile client and mobile application main menu: <ul><li>custom list ordering;</li><li>alphabetical list ordering;</li><li>common infobase list operations (only for the web client).</li></ul><p>Command-line parameters can be specified for each application in the applications list. The following command-line parameters are available in the mobile application and mobile client: <span class="term">N</span>, <span class="term">P</span>, <span class="term">ClearCache</span>, <span class="term">C</span>, <span class="term">WSA</span>, <span class="term">OIDA</span>, <span class="term">Autooff</span>, <span class="term">DisableStartupMessahes</span>, <span class="term">Z</span>, <span class="term">UsePrivilegedMode</span>, <span class="term">HttpsForceSSLv3</span>, <span class="term">HttpsForceTLS</span><span class="term">1</span><span class="term">_0</span>, <span class="term">O</span>, <span class="term">L</span>, <span class="term">VL</span>, <span class="term">WSN</span>, <span class="term">WSP</span>, and <span class="term">URL</span>. Implemented the application startup according with the set of supported command-line parameters.</p></td><td>These features were not provided.</td><td>New application list management operations. You can now specify command-line options to fine tune the application behavior at startup.</td></tr><tr title="Версия 8.3.12" class="compat tag_115 tag_1"><td><a name="6448c67c-118b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the mobile platform and in all client applications, if a form control that has minimum width does not fit the form, the control width is reduced below the minimum.<p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td>If a form control that had minimum width did not fit the form, the control width was not reduced below the minimum.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="97be7de3-072e-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Rows and columns can be docked when generating a grouping header template based on a predefined template.<p>Columns are docked (<span class="term">FixLeft </span>property of a data composition template area cell is set) if the <span class="term">FixLeft </span>report setting is not set or is set to <span class="term">Auto</span>. Rows are docked (<span class="term">FixTop </span>property is set) if the <span class="term">FixTop </span>report setting is not set or is set to <span class="term">Auto</span>.</p><p>This change is not implemented in version 8.3.11 compatibility mode.</p></td><td>Rows and columns were never docked when generating a grouping header template based on a predefined template. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="compat tag_45 tag_1"><td><a name="d0a24841-1192-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If a query contains a <span class="term">UNION </span>expression without the <span class="term">ALL </span>keyword, a <span class="term">CAST AS Reference</span> operation will return a single string with <span class="term">NULL </span>value.<p><span class="term">ISNULL() </span>function applied to a <span class="term">CAST AS Reference </span>expression returns the correct result.</p><p>This change is not implemented in version 8.3.11 compatibility mode</p></td><td>If a query contained a <span class="term">UNION </span>expression without the <span class="term">ALL </span>keyword, a <span class="term">CAST AS Reference </span>operation might return multiple strings with <span class="term">NULL </span>value.<p><span class="term">ISNULL()</span> function applied to a <span class="term">CAST AS Reference</span> expression might return an incorrect result.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_4"><td><a name="57b164a3-1241-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Clarified some of the collaboration system error messages.</td><td>Some of the collaboration system error messages were less clear.</td><td>The collaboration system error messages are more clear now.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_1"><td><a name="ba314f87-1241-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the settings composer of the data composition system, when the source of available settings is specified, if a parameter value is a fixed array and the parameter can store a value list, the value list that includes all the values from the initial fixed array is stored to the parameter.<p>This change is not implemented in version 8.3.11 compatibility mode</p></td><td>In the settings composer of the data composition system, when the source of available settings was specified, if a parameter value was a fixed array and the parameter could store a value list, a value list containing a single element with the default value of the parameter type was stored to the parameter.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_115"><td><a name="d8157e30-2069-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Unified and improved appearance of managed form control tooltips that have <span class="term">ToolTipRepresentation </span>property set to <span class="term">Button</span>. This change is implemented for various types of managed form controls.</td><td>The appearance of managed form control tooltips that had <span class="term">ToolTipRepresentation </span>property set to <span class="term">Button </span>was not unified across different control types.</td><td>Unified tooltip appearance for various types of form controls.</td></tr><tr title="Версия 8.3.12" class="tag_30 tag_31 tag_115 tag_37"><td><a name="1365c5ec-211d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>In mobile applications, for managed form field extension for an HTML document field, the <span class="term">Document </span>property is now available.<p>In mobile applications, for <span class="term">EventData </span>parameter of <span class="term">OnClick </span>event handler of managed form field extension for an HTML document field, <span class="term">Document </span>and <span class="term">Href </span>parameters are now available.</p><p>Mobile platform notifications about calls of methods and properties that do not exist may be different from PC platform notifications.</p></td><td>These features were not provided.<p>On mobile devices, HTML documents displayed in forms were inaccessible.</p></td><td>Extended HTML document capabilities for the mobile platform.</td></tr><tr title="Версия 8.3.12" class="tag_19 tag_29"><td><a name="296a5c0f-268f-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of Microsoft SQL Server 2017 is implemented.</td><td>Microsoft SQL Server 2017 was not supported.</td><td>Support of Microsoft SQL Server 2017 is implemented.</td></tr><tr title="Версия 8.3.12" class="tag_20"><td><a name="c66f9aa1-26a4-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>For <span class="term">TextColor </span>and <span class="term">BackColor </span>properties of managed form buttons, both the property palette and the color selection dialog box now display the actual color values (if these properties are set to <span class="interface">Auto </span>or to any of the system style items).
</td><td>For <span class="term">TextColor </span>and <span class="term">BackColor </span>properties of managed form buttons, both the property palette and the color selection dialog box displayed the color of the system style item (if these properties were set to <span class="interface">Auto </span>or to any of the system style items).</td><td>The property palette now displays property values more accurately.</td></tr><tr title="Версия 8.3.12" class="tag_84"><td><a name="4439c70c-30cf-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The French localization of the client applications is available.</td><td>This feature was not provided.</td><td>1C:Enterprise is available to French-speaking users.</td></tr><tr title="Версия 8.3.12" class="tag_31"><td><a name="e4f2e1e3-30d5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The information in the <span class="interface">About </span>dialog box in the mobile client was expanded.</td><td>There was less information in the <span class="interface">About </span>dialog box in the mobile client.</td><td>The <span class="interface">About </span>dialog box in the mobile client is now closer to the <span class="interface">About </span>dialog box in the thin client.</td></tr><tr title="Версия 8.3.12" class="tag_30 tag_31 tag_4"><td><a name="67933940-30e0-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented the feature of receiving and processing push notifications from the collaboration system. The mobile device application should be built with push notifications extension enabled. Notifications are generated by the pushnotifications.1c.com service from 1C company. The registration in service is performed automatically.</td><td>The collaboration system did not generate mobile push notifications.</td><td>Reduced risk of missing the collaboration system notification when the application is not running, or is hidden, or when the user is operating in another infobase within a single application.</td></tr><tr title="Версия 8.3.12" class="tag_37"><td><a name="69a907b1-3e2e-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Implemented the feature of including external providers in the OpenID authentication process.<p>For the specifics of external providers usage, refer to the documentation.</p></td><td>This feature was not provided.</td><td>Improved the OpenID authentication support.</td></tr><tr title="Версия 8.3.12" class="tag_30 tag_31"><td><a name="02c98ca2-3e45-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The iPhone X screen is now supported in the 1C:Enterprise mobile version.</td><td>This feature was not provided.</td><td>The 1C:Enterprise mobile version interface is adapted to iPhone X.</td></tr><tr title="Версия 8.3.12" class="tag_37"><td><a name="15e8c58b-4154-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>1C:Enterprise 8 now supports cryptographic algorithms that meet the GOST R 34.10-2012 and 34.11-2012 requirements.</td><td>This feature was not provided.</td><td>Internet resources that demand the GOST R 34.10-2012 and 34.11-2012 compliance are now available in 1C:Enterprise 8.</td></tr><tr title="Версия 8.3.12" class="tag_30 tag_31 tag_48"><td><a name="e3032cd8-4ace-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>1C:Enterprise platform does not support barcode scanning, making photos and videos on Windows Desktop.<p>The following methods of the <span class="term">MultimediaTools </span>object return <span class="term">False </span>on Windows Desktop: <span class="term">BarcodeScanningSupported(), </span><span class="term">PhotoSupported()</span>, <span class="term">VideoRecordingSupported()</span>.</p></td><td>The following methods of the <span class="term">MultimediaTools </span>object returned <span class="term">T</span><span class="term">rue</span> on Windows Desktop: <span class="term">BarcodeScanningSupported()</span>, <span class="term">PhotoSupported()</span>, <span class="term">VideoRecordingSupported()</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_79"><td><a name="a45defe7-5297-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>If the name of the picture from a picture library equals to the name of the configuration common picture, a warning will be generated during the database update. The database update process will not be interrupted. When accessing the picture by name, the configuration picture returns.<p>When this warning appears, it is recommended to review picture names in the configuration.</p></td><td>If the name of a picture from a picture library was equal to the name of a configuration common picture, the database update could not be performed.</td><td>The database update is now available if the name of a picture from a picture library is equal to the name of a configuration common picture.</td></tr><tr title="Версия 8.3.12" class="tag_30 tag_31 tag_10"><td><a name="7aaf07df-52a3-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The 1C:Enterprise 8 mobile platform now supports OS authentication.<p>The <span class="term">HTTPConnection </span>object constructor supports the <span class="term">UseOSAuthentication </span>parameter. </p></td><td>This feature was not provided.</td><td>The 1C:Enterprise 8 mobile platform is now sufficient when the OS authentication is required.</td></tr><tr title="Версия 8.3.12" class="tag_64 tag_31"><td><a name="9d651908-52b1-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>The 1C:Enterprise mobile platform now displays messages of the same style as other mobile messages. Messages are generated by the <span class="term">ShowUserNotification()</span> method with the <span class="term">UserNotificationStatus </span>parameter set to <span class="term">UserNotificationStatus.Information</span>.</td><td>If a message was generated by the <span class="term">ShowUserNotification() </span>method with the <span class="term">UserNotificationStatus </span>parameter set to <span class="term">UserNotificationStatus.Information</span>, this message was not displayed.</td><td>Extended capabilities of the ShowUserNotification() method in the mobile client.</td></tr><tr title="Версия 8.3.12" class="tag_30 tag_31 tag_115"><td><a name="77f4ac8c-5760-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The command set and the appearance of the context menu of a managed form table row was changed in the 1C:Enterprise mobile version.</td><td>The command set and the appearance of the context menu of a managed form table row in the 1C:Enterprise mobile version were different.</td><td>Improved the 1C:Enterprise mobile interface.</td></tr><tr title="Версия 8.3.12" class="tag_37"><td><a name="013791ef-5a80-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Improved the analysis of the root certificate revocation.<p>Implemented the option to specify the behavior of the platform when the root certificate revocation can not be verified unambiguously. Implemented the <span class="term">IgnoreServerCertificatesChainRevocationSoftFail </span>parameter of the <span class="interface">conf.cfg </span>file.</p><p>These changes are available in all Internet-enabled features of 1C:Enterprise platform.</p></td><td>The analysis of the root certificate revocation was the same regardless of the reason why the remote node was not validated.<p>There was no option to specify the platform behavior when the root certificate revocation could not be verified unambiguously.</p></td><td>Improved diagnostics of Internet-enabled functionality. In some cases the option to specify the platform behavior is now available.</td></tr><tr title="Версия 8.3.12" class="tag_30"><td><a name="51bd9880-5e72-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>Implemented the database file validation in the verify and repair feature of the mobile platform.<p>This feature checks whether the database file is corrupted and prompts several solutions.</p></td><td>These features were not provided.<p>The verify and repair feature could not validate the database file.</p><p>If the database file was corrupted the session was abnormally terminated.</p></td><td>Improved the database file diagnostics capabilities.</td></tr><tr title="Версия 8.3.12" class="tag_38"><td><a name="3f67a339-081c-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>If the active extension changes the database structure it can not be deleted. If you want to delete the extension you shoud deactivate it first. You will be prompted to confirm the deletion of the inactive extension that changes the database structure.<p>Implemented the <span class="term">ConfigurationExtension.ModifiesDataStructure() </span>method, which shows whether the configuration extension changes the database structure.</p></td><td>When the extension that changed the database structure was deleted no actions preventing the extension data loss were performed.</td><td>Reduced risk of configuration extension data loss.</td></tr><tr title="Версия 8.3.12" class="tag_31 tag_32"><td><a name="542b8081-627a-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>A web page where user can register in the infobase (or service) can now be specified in the mobile client. This page can be reached either automatically (if there are no registered infobases in the mobile client) or manually.<p>You can now specify an URL with the personal account of services that contain infobases for the mobile client. </p><p>The mobile client can now retrieve shared infobase lists from the server through special web services. You can specify multiple addresses of the same server, as well as addresses of multiple servers.</p><p>The following options are now available when building a mobile application:</p><ul><li>Specifying starting page that will be displayed if the mobile client infobase list is empty.</li><li>Specifying a custom URL in the infobase list. This URL will be displayed by the internal mobile client features.</li><li>Specifying multiple web services that return shared infobase lists.</li><li>Entering a custom web service URL to retrieve a shared infobase list.</li></ul><p>The <span class="term">e1c://</span> type hyperlinks are now supported as a starting page and an infobase list element in the mobile client.</p><p>Implemented the <span class="term">AddToStartCfg</span> command-line option for the mobile client. It adds an infobase in the mobile client infobase list. It can be placed in web pages, specified during the mobile application customization.</p><p>OpenID authentication is not supported for accessing web-servers with shared infobase lists.</p></td><td>These features were not provided.</td><td>The registration of an infobase or a web service in the mobile client became more clear and simple.</td></tr><tr title="Версия 8.3.12" class="tag_39"><td><a name="4b1af8c6-6580-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>Implemented the following events:<ul><li>Managing users:</li><ul><li>Error adding a user (<span class="term">_$User$_</span>.<span class="term">NewError</span>),</li><li>Error changing a user (<span class="term">_$User$_.UpdateError</span>),</li><li>Error deleting a user (<span class="term">_$User$_.DeleteError</span>).</li></ul><li>Infobase operations:</li><ul><li>Truncate event log (<span class="term">_$InfoBase$_.EventLogReduce</span>),</li><li>Error truncating event log (<span class="term">_$InfoBase$_.EventLogReduceError</span>),</li><li>Error changing event log parameters (<span class="term">_$InfoBase$_.EventLogSettingsUpdateError</span>),</li><li>Error changing infobase parameters (<span class="term">_$InfoBase$_.InfoBaseAdmParamsUpdateError</span>),</li><li>Start dumping infobase to file (<span class="term">_$InfoBase$_.DumpStart</span>),</li><li>End dumping infobase to file (<span class="term">_$InfoBase$_.DumpFinish</span>),</li><li>Error dumping infobase to file (<span class="term">_$InfoBase$_.DumpError</span>),</li><li>Start restoring infobase from file (<span class="term">_$InfoBase$_.RestoreStart</span>),</li><li>End restoring infobase from file (<span class="term">_$InfoBase$_.RestoreFinish</span>),</li><li>Error restoring infobase from file (<span class="term">_$InfoBase$_.RestoreError</span>),</li><li>Error updating database configuration (<span class="term">_$InfoBase$_.DBConfigUpdateError</span>),</li><li>Error updating extension database configuration (<span class="term">_$InfoBase$_.DBConfigExtensionUpdateError</span>).</li></ul></ul><p>Extended the list of data types that are handled by the following events: <span class="term">_$Access$_.AccessDenied</span>, <span class="term">_$InfoBase$_.EventLogSettingsUpdate</span>.</p><p>New events require the <span class="term">DataAdministration </span>access right to view, except managing users events and the following ones: <span class="term">$</span><span class="term">InfoBase$_.DBConfigUpdateError</span>, and <span class="term">_$InfoBase$_.DBConfigExtensionUpdateError</span>.</p></td><td>There were less registered events and less handled data types.</td><td>Improved logging events.</td></tr><tr title="Версия 8.3.12" class="compat tag_25 tag_63 tag_1"><td><a name="77a6faa0-93e2-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Some of the output parameters of the data composition system are only saved if their <span class="interface">Use </span>flag is set (the exact list of parameters depends on the configuration compatibility mode).<ul><li>In compatibility mode <span class="interface">Version 8.3.10 </span>or earlier: <span class="term">ChartType.PointsScale</span>, <span class="term">ChartType.ValuesScale</span>, and <span class="term">ChartType.SeriesScale</span>.</li><li>In compatibility mode <span class="interface">Version 8.3.11</span> or earlier: <span class="term">ChartType.ColorPaletteDescription</span>, <span class="term">ChartType.ReferenceBandsColorPaletteDescription</span>, <span class="term">ChartType.ValuesReferenceLines</span>, <span class="term">ChartType.ValuesReferenceBands</span>, <span class="term">ChartType.PointsReferenceLines</span>, <span class="term">ChartType.PointsReferenceBands</span>.
</li></ul></td><td>All of the changes in the output parameters of the data composition system were saved. This could cause issues at opening data composition settings in the earlier versions of 1C:Enterprise.</td><td>Data composition settings related to charts are now usable in the earlier platform versions.</td></tr><tr title="Версия 8.3.12" class="tag_28"><td><a name="fb7ee215-93ea-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The Mozilla Firefox add-on that provides access to 1C:Enterprise extensions and 1C:Enterprise add-ins is available in the add-on store <a href="https://addons.mozilla.org" target="_blank">https://addons.mozilla.org</a>. The add-on is automatically updated to newer versions as they appear in the store.</td><td>The Mozilla Firefox add-on that provides access to 1C:Enterprise extensions and 1C:Enterprise add-ins was not available in the add-on store <a href="https://addons.mozilla.org" target="_blank">https://addons.mozilla.org</a>. The add-on updates were delivered and installed with new 1C:Enterprise versions.</td><td>Updates of the Mozilla Firefox add-on are now transparent to users.</td></tr><tr title="Версия 8.3.12" class="tag_31 tag_30 tag_115"><td><a name="9cf54b1d-9592-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the mobile version of 1C:Enterprise, in HTML document fields, full-featured editing of HTML page input fields is now available (if their <span class="term">contentEditable </span>property allows editing). At that, all formatted document functionality is supported.</td><td>In the mobile version of 1C:Enterprise, in HTML document fields, full-featured editing of HTML page input fields was not available (if their <span class="term">contentEditable </span>property allowed editing).
</td><td>Extended HTML document functionality in the mobile version of 1C:Enterprise.</td></tr><tr title="Версия 8.3.12" class="tag_116"><td><a name="5c498b14-aced-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>Software licenses can be associated with dongles.<p>Human-readable information about the license is added to the bottom of activated software license files. Such files are compatible with the earlier 1C:Enterprise versions.
</p></td><td>Software licenses could not be associated with dongles.<p>Activated software license files did not contain human-readable information about the license.</p></td><td>The software licensing features are upgraded.</td></tr><tr title="Версия 8.3.12" class="tag_116"><td><a name="83ac7d6d-ebdd-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>New license type: 1C:Enterprise server CORP license. Implemeted a check for the CORP license if a feature requires it. The following features are available for CORP licenses:<ul><li>More than 12 physical CPU cores</li><li>More than 500 simultaneous client application sessions (including Designer and external connection sessions)</li></ul><p>The following CORP license types are available:</p><ul><li>Software: for a 64-bit server; number of users: 1, 5, 10, 20, 50, 100, 300, 500, or 1000.</li><li>Hardware: for a 64-bit server; number of users: 50, 100, 300, 500, or 1000.</li></ul><p>Licensing utility now supports CORP licenses.</p><p>New command: <span class="interface">ring license update</span>. The command updates all licenses located in the storage.</p></td><td>Having a CORP license was a legal requirement, not a technical requirement.</td><td>A new license type: CORP.
</td></tr><tr title="Версия 8.3.12" class="tag_37 tag_11 tag_8 tag_78"><td><a name="122c2cde-c164-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>Distribution packages of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer are converted into .exe files. Distribution packages in .cab format are considered obsolete, although supported.<p>The add-in technology documentation is updated. (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>)</p></td><td>Distribution packages of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer were provided in .cab files.
</td><td>Installation of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer is more convenient.</td></tr><tr title="Версия 8.3.12" class="tag_29 tag_15"><td><a name="c68038b4-c236-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The following Linux distribution packages are supported:<ul><li>ALT Linux SPT 7</li><li>ALT Server 8</li><li>ALT Workstation K 8</li><li>ALT Workstation 8</li><li>ALT Education 8</li><li>ALT SP 8</li></ul><p>Both 32-bit and 64-bit distribution packages are supported. 1C:Enterprise server clusters and client applications are supported.
</p></td><td>The distribution packages were not supported.</td><td>Extended list of supported Linux distribution packages.</td></tr><tr title="Версия 8.3.12" class="tag_37"><td><a name="33ee1c20-d829-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Upgrade: the credentials used as a basis for <span class="interface">WS-reference</span> and <span class="term">WSDefinition </span>objects are only sent to the primary resource that provides a WSDL definition. If the downloaded schema requires schemas from other secondary resources, they are accessed anonymously.</td><td>The credentials that had been used as a basis for <span class="interface">WS-reference</span> and <span class="term">WSDefinition </span>objects were used to access all resources that provided WSDL definitions.</td><td>To download a web service definition, if a web server requires authorization, the credentials are sent only to the primary resource selected to download the schema.</td></tr><tr title="Версия 8.3.12" class="tag_86"><td><a name="b7547165-a9de-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>Upgrade: for the "<span class="interface">All functions</span>" dialog box in the thick and thin client applications, the search by the first characters is disabled. To open the search box, press<span class="interface"> Ctrl+F</span>. To move to the next search result, press <span class="interface">F3</span>. To move to the previous search result, press <span class="interface">Ctrl+F3</span>.</td><td>In the "<span class="interface">All functions</span>" dialog box, there were two ways to start a search:<ul><li>By opening the search box with <span class="interface">Ctrl+F</span> (in all client applications).</li><li>By typing the search text in the list of configuration objects (in the thick and thin client applications). The web client did not support search by typing the search text in the list of configuration objects.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_94"><td><a name="c99aecc0-e820-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 94); return false;">Regional settings</a>.<br></td><td>Upgrade: in accordance with the Federal Law of the Russian Federation No. 368-FZ, a new time zone is applied for Volgograd oblast. The update is applied to all 1C:Enterprise system components, except for the web client. The web client sets the time in accordance with the time zone information provided by the operating system and web browser.
</td><td>1C:Enterprise ignored the changes introduced by the Federal Law of the Russian Federation No. 368-FZ.</td><td>New time zone settings are applied due to the legislation change.</td></tr><tr title="Версия 8.3.12" class="tag_118"><td><a name="00d501fc-ebe0-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 118); return false;">Configuration comparison and merging</a>.<br></td><td>New feature: on comparing two configurations, the command order changes are displayed for the commands stored in standard command groups.</td><td>On comparing two configurations, the command order changes were not displayed for the commands stored in standard command groups. Therefore, the changes were not applied to the resulting configuration.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_32"><td><a name="357b4ec8-ebe5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Upgrade: Mobile application builder successfully builds applications when an add-in is missing for some mobile operating systems supported by the mobile application. It records warnings about missing add-ins to the mobile application building log.<p>When a mobile application attempts to access a missing add-in, an exception is generated.</p></td><td>Mobile application builder did not allow building applications when an add-in was missing for a mobile operating system supported by the mobile application.</td><td>You can build a mobile application if there is an add-in that is not required on some operating systems supported by the mobile application.
</td></tr><tr title="Версия 8.3.12" class="tag_31 tag_68"><td><a name="8706fb87-ebe5-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>Upgrade: the <span class="interface">Change history</span> command is hidden from context menus of dynamic lists in the mobile client version 8.3.12 connected to 1C:Enterprise server version 8.3.13 or later.</td><td>Two <span class="interface">Change history</span> commands were displayed in the context menus of dynamic lists in the mobile client version 8.3.12 connected to 1C:Enterprise server version 8.3.13 or later. Both commands were unavailable.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.12" class="tag_14"><td><a name="a0fff3f8-f481-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Upgrade: client applications require less RAM to handle pictures.</td><td>Client applications required more RAM to handle pictures.</td><td>RAM consumption by client applications when handling pictures is optimized.</td></tr><tr title="Версия 8.3.12" class="tag_6"><td><a name="ee93226a-f481-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Upgrade: occasional performance degradation of loaded server clusters is fixed.</td><td>Occasionally, performance degradation of loaded server clusters occurred.</td><td>Server cluster performance is more stable.</td></tr><tr title="Версия 8.3.12" class="tag_29 tag_15"><td><a name="e9654fda-fc6b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Upgrade: new approach to Linux OS distribution support. 1C:Enterprise supports only distributions listed in the system requirements. In general, the client-supported distribution list matches the server-supported distribution list, but there might be some exceptions. The list of supported Linux distributions is up-to-date.</td><td>The list of supported Linux distributions was not up-to-date.</td><td>The list of supported Linux distributions is brought up-to-date.</td></tr><tr title="Версия 8.3.12" class="tag_31"><td><a name="b054ba44-0202-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Upgrade: when you use iOS mobile application home page to add an application, the compatibility check is based on the digital signatures of all configurations included in the mobile application build.</td><td>When developers used iOS mobile application home page to add a new application, the application failed.</td><td>You can use iOS mobile application home page to add new applications based on the configurations included in the mobile client application.</td></tr><tr title="Версия 8.3.12" class="tag_31"><td><a name="c712d31c-0205-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>New feature: the favorites setting form contains hint text on how to use this form.<p>Upgrade: If a mobile client form has a link, the <span class="interface">More actions </span>menu always contains the commands <span class="interface">Add to favorites </span>and <span class="interface">Get link.</span></p><p>New command in the <span class="interface">Get link </span>dialog box that adds a link to the favorites.</p></td><td>The favorites setting form did not contain hint text on how to use this form.<p>If a mobile client form had a link, then:</p><ul><li>The commands <span class="interface">Add to favorites </span>and <span class="interface">Get link </span>were added to the <span class="interface">More actions </span>menu only if the following conditions were met: The form had a <span class="interface">blank</span> command bar and the command bar had a non-blank<span class="interface"> More actions </span>menu.</li><li>The commands <span class="interface">Add to favorites </span>and<span class="interface"> Get link </span>were unavailable if the form had no command bar or if the command bar contained only one command.</li></ul><p>Command of adding a link to the favorites was not available in the dialog box of the Add to favorites command.</p></td><td>Mobile client interface is improved.
</td></tr><tr title="Версия 8.3.12" class="tag_31"><td><a name="77a213b4-14bd-11e9-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 31); return false;">Mobile client</a>.<br></td><td>Upgrade: the table row rearrangement command is automatically added to the table context menu instead of commands of moving rows up and down (even if command bar autofill is disabled).<p>Upgrade: if the multiple choice is set for a table (even if command bar autofill is disabled), the command of selecting several table rows is automatically added to the table context menu and table command bar.</p></td><td>The table row rearrangement command was added to the table context menu only if the context menu had been filled automatically or manually.<p>Command of selecting several table rows was added to the table context menu and the table command bar only if the table context menu and the table command bar had been filled automatically or manually.</p></td><td>Mobile client interface is improved.</td></tr></table><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e4150061-9163-11e7-a3f7-0050569f678a">Transition from the previous version to the version 8.3.12</a></h2><ul><li title="Версия 8.3.12" class="tag_0"><a name="e4150062-9163-11e7-a3f7-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.12.
</li><li title="Версия 8.3.12" class="tag_0"><a name="e4150063-9163-11e7-a3f7-0050569f678a"></a>Some features that are added in version 8.3.12 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.12" class="tag_0"><a name="3410022d-68b0-11e8-a3f7-0050569f678a"></a>It is recommended that you uninstall your HASP Device Driver and then install HASP Device Driver 7.63, which is a part of 1C:Enterprise distribution package.</li></ul><p><a href="#e4150058-9163-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h1><a name="717c2d01-026f-11e7-a3f7-0050569f678a">Version 8.3.11</a></h1><p title="Версия 8.3.11" class="tag_0"><a name="717c2d0d-026f-11e7-a3f7-0050569f678a"></a>Version 8.3.11 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.11" class="tag_0"><a name="308fbda0-117a-11e8-a3f7-0050569f678a"></a>Performance optimization for user work history is included in the list of changes implemented in 1C:Enterprise version 8.3.8.</p><hr></hr><ul><li><a href="#717c2d02-026f-11e7-a3f7-0050569f678a">New functionality and changes</a></li><li><a href="#717c2d03-026f-11e7-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#717c2d04-026f-11e7-a3f7-0050569f678a">Optimization</a></li><li><a href="#717c2d05-026f-11e7-a3f7-0050569f678a">Changes that affect system behavior</a></li><li><a href="#717c2d06-026f-11e7-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#717c2d07-026f-11e7-a3f7-0050569f678a">Renamed objects</a></li><li><a href="#717c2d08-026f-11e7-a3f7-0050569f678a">Mobile platform</a></li><li><a href="#717c2d09-026f-11e7-a3f7-0050569f678a">Library updates
</a></li><li><a href="#717c2d0a-026f-11e7-a3f7-0050569f678a">Transition from the previous version to the version 8.3.11</a></li></ul><h2><a name="717c2d02-026f-11e7-a3f7-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.11" class="compat tag_2 tag_1"><td><a name="b7d373c7-026f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.10</span> is now implemented.</td><td>Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.9 was implemented.</td><td>Configurations developed using 1C:Enterprise platform version 8.3.10 or earlier can run on version 8.3.11 without any changes to configuration or to data structures. This allows for transition to version 8.3.11 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.10 after the transition to version 8.3.11, even if you disabled the compatibility mode (if you did, enable it again).</td></tr><tr title="Версия 8.3.11" class="tag_118"><td><a name="a75ef971-0320-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 118); return false;">Configuration comparison and merging</a>.<br></td><td>Merging composite types and the contents of exchange plans, subsystems, and functional options is implemented. Viewing the differences in these objects is available both in interactive mode (in a dialog box) and in a configuration comparison report.<p>Automatic merging of composite types and the contents of exchange plans, subsystems, and functional options is implemented, with the option to specify the configuration that has priority.</p><p>The format of the file that stores configuration comparison and merging settings is changed.</p></td><td>Merging composite types and the contents of exchange plans, subsystems, and functional options was not available. Available options included taking the entire object from the configuration being loaded or keeping the existing objects without changing them.</td><td>Simplified configuration comparison and merging.</td></tr><tr title="Версия 8.3.11" class="tag_68"><td><a name="257a3539-0329-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 68); return false;">Data history</a>.<br></td><td>The history of database object changes is implemented. The<span class="interface"> Data history </span>property is implemented for the following configuration objects: catalogs, documents, business processes, tasks, and information registers. The option to keep the history of attributes of these objects (including standard attributes and tabular sections), common attributes (except for data separators), and information register resources is implemented. The options to view and edit data change history, add comments to data history records, and revert to a specific data version are implemented.<p>Native objects of configuration extensions do not support data history.</p><p>The following access rights are implemented: <span class="term">ReadDataHistory</span>, <span class="term">ReadDataHistoryOfMissingData</span>, <span class="term">UpdateDataHistory</span>, <span class="term">UpdateDataHistoryOfMissingData</span>, <span class="term">UpdateSettingsDataHistory</span>, <span class="term">UpdateDataHistoryVersionComment</span>, <span class="term">ViewDataHistory</span>, <span class="term">EditDataHistoryVersionComment</span>, and <span class="term">Switch</span><span class="term">ToDataHistoryVersion</span>.</p><p>The global context property <span class="term">DataHistory </span>is implemented. It provides access to the data history from 1C:Enterprise script.</p><p>The user interface that provides access to data history is implemented.</p></td><td>This feature was not provided. Implementation of a change history based on built-in 1C:Enterprise tools was possible.</td><td>The data history is now available as a platform-level feature. This simplifies application development and support.</td></tr><tr title="Версия 8.3.11" class="compat tag_20 tag_1"><td><a name="5d399b98-04bb-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the managed form editor, the option to preview a form as it would look on a mobile application is implemented. This option is available in configuration compatibility mode<span class="interface"> Version 8.3.7</span> or later.</td><td>In the managed form editor, the option to preview a form as it would look on a mobile application was not available. The preview always displayed a form as it would look on a PC.</td><td>Improved form development tools for configurations that run on mobile devices.</td></tr><tr title="Версия 8.3.11" class="compat tag_49 tag_1"><td><a name="3b4a5af2-04be-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 49); return false;">Binary data</a>.<br></td><td>A set of functions that perform bitwise operations on integer numbers is implemented. They treat numbers as unsigned 32-bit numbers. The following global context methods are implemented: <span class="term">CheckBit()</span>, <span class="term">CheckBy</span><span class="term">BitMask()</span>, <span class="term">SetBit()</span>, <span class="term">BitwiseAnd()</span>, <span class="term">BitwiseOr()</span>, <span class="term">BitwiseNot()</span>, <span class="term">BitwiseAndNot()</span>, <span class="term">BitwiseXor()</span>, <span class="term">BitwiseShiftRight()</span>, and <span class="term">BitwiseShiftLeft()</span>.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>1C:Enterprise only provided methods for logical operations with data stored in binary data buffers.</td><td>Simplified usage of bitwise operations with numerical operands.</td></tr><tr title="Версия 8.3.11" class="tag_73 tag_6"><td><a name="93d634aa-0567-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>New infobase restructuring algorithm is implemented. It features the following major differences from the previous algorithm:<ul><li>It only processes physical database tables that were changed.</li><li>It performs as many changes as possible without copying tables or replicating data between the copies.</li><li>If replication between table versions is necessary, it is always performed using DBMS tools.</li></ul><p>This feature has beta status. The new restructuring algorithm is only used in client/server mode with Microsoft SQL Server or PostgreSQL DBMS.</p><p>The new restructuring algorithm requires Java 1.8 to be installed on the computer that runs 1C:Enterprise server.</p><p>For the <span class="interface">conf</span><span class="interface">.cfg</span> file, new parameters <span class="term">J</span><span class="term">avaHome</span>, <span class="term">JavaOpts</span>, and <span class="term">UpdateDBCfg</span> are implemented.</p></td><td>This feature was not provided.</td><td>The new algorithm significantly improves the performance of infobase restructuring. This reduces the maintenance downtime during application updates on production servers.</td></tr><tr title="Версия 8.3.11" class="compat tag_64 tag_43 tag_1"><td><a name="8286b9df-057d-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>For the format string parameter of <span class="term">Format()</span> function, the option to include a number format template is implemented. The new <span class="term">NF </span>format string parameter is implemented for this purpose. The template specifies the position of a number in a string.<p>The search in dynamic lists is based on the format specified for list columns. The search results are highlighted even in cells that contain string constants before and/or after the number.</p><p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>These features were not provided.</td><td>You can display formatted values with measurement units in charts and in other interface items that support format strings.</td></tr><tr title="Версия 8.3.11" class="tag_20"><td><a name="980439aa-0596-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In batch Designer mode, the configuration check includes the option to check configuration modules for synchronous method calls.<p>For<span class="term"> /CheckConfig </span>command-line option, the <span class="term">-CheckUseSynchronousCalls</span> parameter is implemented. If you specify this parameter, you also have to specify the <span class="term">-ExtendedModulesCheck</span> parameter for this command-line option.</p></td><td>The option to check configuration modules for synchronous method calls during a configuration check initiated from batch Designer mode was not available. This option was only available if Designer was running in interactive mode.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_65 tag_38"><td><a name="391e018e-0597-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>For native configuration extension objects of web service and HTTP service types, support of configurable session reuse is implemented.</td><td>For native configuration extension objects of web service and HTTP service types, configurable session reuse was not available.</td><td>Unified platform behavior for accessing similar mechanisms from a configuration and from an extension.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="62e16530-088f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Sending messages from a 1C:Enterprise server to a client application is implemented. A configured collaboration system operates as transport for message exchange purposes. Client applications can get messages both synchronously and asynchronously, depending on the server call type: a regular call or a background job.
For collaboration system manager, the following methods are implemented: <span class="term">CreateUser()</span>, <span class="term">DeleteMessage()</span>, <span class="term">BeginAttachNewMessagesHandler()</span>, <span class="term">BeginDetachNewMessagesHandler()</span>, and a new variant of <span class="term">GetConversation() </span>method. For <span class="term">CollaborationS</span><span class="term">ystemConversation</span> object, <span class="term">Key </span>and <span class="term">Visible </span>properties are implemented. For <span class="term">CollaborationSystemConversationsFilter</span> object, <span class="term">Key </span>and <span class="term">Displayed </span>properties are implemented. The <span class="term">CollaborationSystemMessage </span>object and some of its properties (<span class="term">Author</span>, <span class="term">Date</span>, <span class="term">ID</span>, <span class="term">Recipients</span>, and <span class="term">Text</span>) are now available on the client. For <span class="term">CollaborationSystemMessage </span>object, <span class="term">Data </span>and <span class="term">Conversation </span>properties are implemented. Objects <span class="term">CollaborationSystemConversationID </span>and <span class="term">CollaborationSystemMessageID </span>are are now available on the client. Objects <span class="term">CollaborationSystemUserID </span>and <span class="term">CollaborationSystemUserIDCollection</span>, their properties, and their methods are now available on the client.</td><td>This feature was not provided.<p>The <span class="term">CollaborationSystemMessage </span>object and some of its properties (<span class="term">Author</span>, <span class="term">Date</span>, <span class="term">ID</span>, <span class="term">Recipients</span>, and <span class="term">Text</span>) were only available on 1C:Enterprise server. Objects <span class="term">CollaborationSystemConversationID </span>and <span class="term">CollaborationSystemMessageID </span>were only available on 1C:Enterprise server. Objects <span class="term">CollaborationSystemUserID </span>and <span class="term">CollaborationSystemUserIDCollection</span>, their properties, and their methods were only available on 1C:Enterprise server.</p></td><td>You can implement client notifications for events that occur on 1C:Enterprise server.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="58e1447a-089c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The option to attach a handler that is executed after sending a collaboration system message is implemented. A message can now include hyperlinks; clicking a hyperlink executes the handler or a standard action assigned to the hyperlink .<p>For <span class="term">CollaborationSystemManager </span>object, the following methods are implemented: <span class="term">AttachAfterMessageSendHandler()</span>, <span class="term">DetachAfterMessageSendHandler()</span>, <span class="term">AttachMessageActionHandler()</span>, and <span class="term">DetachMessageActionHandler()</span>. The <span class="term">CollaborationSystemMessage.Actions</span> property is implemented.</p><p><span class="term">CollaborationSystemConversation </span>and <span class="term">CollaborationSystemConversationContext </span>objects are now available in client applications.</p></td><td>These features were not provided. <span class="term">CollaborationSystemConversation </span>and <span class="term">CollaborationSystemConversationContext </span>objects were only available on 1C:Enterprise server.<p>
</p></td><td>Expanded collaboration system capabilities. You can implement automatic replies to incoming messages.</td></tr><tr title="Версия 8.3.11" class="tag_45"><td><a name="5912b532-08cb-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>For <span class="term">QuerySchemaQueryBatch</span>, <span class="term">QuerySchemaOperators</span>, <span class="term">QuerySchemaColumns</span>, <span class="term">QuerySchemaIndexExpression</span>, <span class="term">QuerySchemaOrderExpression</span>, and <span class="term">QuerySchemaTotalCalculationFields </span>objects, the <span class="term">MoveTo()</span> method is implemented. It moves a collection element to the specified position.</td><td>This feature was not provided.</td><td>Expanded development tools for some collections related to query schemas.</td></tr><tr title="Версия 8.3.11" class="tag_38 tag_23"><td><a name="a20cfe02-0960-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>In configuration extensions, support of native catalogs, documents, exchange plans, and information registers is implemented.<p>For adopted catalogs and documents, the option to add attributes and tabular setions in extensions is implemented.</p><p>A native exchange plan can only include native extension objects. A native exchange plan cannot be used in a distributed infobase. The option to add native extension objects to adopted exchange plans is implemented.</p><p>The full list of limitations is provided in the documentation.</p><p>Deleting an extension deletes all data that was added to native extension objects from the infobase.</p></td><td>These features were not provided.</td><td>Expanded configuration extension capabilities.<p>An extension attached to an infobase can store its data in the infobase.</p></td></tr><tr title="Версия 8.3.11" class="compat tag_16 tag_1"><td><a name="33547cee-0969-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>For <span class="term">InformationRegisterRecordKey </span>object, the option to get the related metadata object is implemented. The method <span class="term">InformationRegisterRecordKey.Metadata()</span> is implemented.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>Getting the related metadata object directly from the <span class="term">InformationRegisterRecordKey </span>object was not available.</td><td>Getting metadata related to information register record keys is now similar to getting metadata from other configuration objects.</td></tr><tr title="Версия 8.3.11" class="compat tag_63 tag_1"><td><a name="086238a2-1857-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>For stock charts, support of the following properties of <span class="term">ValuesAxis </span>object is implemented: <span class="term">MinValueDetectionMethod</span>, <span class="term">MinValue</span>, <span class="term">Max</span><span class="term">ValueDetectionMethod</span>, and <span class="term">MaxValue</span>.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>For stock charts, values of the following properties of <span class="term">ValuesAxis </span>object did not affect the chart view: <span class="term">MinValueDetectionMethod</span>, <span class="term">MinValue</span>, <span class="term">Max</span><span class="term">ValueDetectionMethod</span>, and <span class="term">MaxValue</span>.</td><td>Improved stock chart display options.</td></tr><tr title="Версия 8.3.11" class="compat tag_12 tag_39 tag_1"><td><a name="4b8522fa-2417-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>In the event log, for <span class="term">Users.Add </span>and <span class="term">Users.Modify</span> events, <span class="term">OpenIDAuthentication </span>and <span class="term">UnsafeOperationProtection </span>properties are implemented (in the <span class="term">Data </span>field of the log record).<p>For <span class="term">Users.Add </span>and <span class="term">Users.Modify</span> events, the log viewer now displays <span class="interface">OpenID authentication </span>and <span class="interface">Unsafe operation protection </span>properties.</p><p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>For events that described adding or modifying a user, the OpenID authentication flag and unsafe operation protection flag were recorded to the event log but were not available for viewing.</td><td>Eliminated unexpected system behavior. You can access data that was previously unavailable.</td></tr><tr title="Версия 8.3.11" class="tag_116"><td><a name="5bc19360-24ea-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>In the license acquisition wizard, selecting a country from a list is implemented.</td><td>In the license acquisition wizard, one could enter any word as a country name.</td><td>Eliminated issues that occurred due to entering incorrect country name during software license acquisition.</td></tr><tr title="Версия 8.3.11" class="tag_19 tag_29"><td><a name="cc99e5b8-71ea-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of Oracle Database version 11.2.0.4 (Linux) is implemented. It is only supported with patch 20954292.<p>Oracle Database version 11.2.0.4 (Windows) is only supported with patches 24591646 and 24591637.</p></td><td>Oracle Database version 11.2.0.4 (Linux) was not supported.<p>Oracle Database version 11.2.0.4 (Windows) was supported without the requirement to install any patches.</p></td><td>Extended list of supported Oracle Database versions.</td></tr><tr title="Версия 8.3.11" class="tag_17"><td><a name="2a31ea7a-78fa-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td><span class="term">&lt;WINCERT&gt;</span> technological log event is implemented. It is intended for investigating errors related to certificate validation using Windows API methods.<p>This event can only be generated on Windows.</p></td><td>This feature was not provided.</td><td>Simplified investigation of errors related to certificate validation on Windows.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="be5c6149-81ac-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Local collaboration system server is now available.<p>The server is provided as a standalone distribution package, it requires separate installation.</p><p>This feature is currently in beta status.</p></td><td>This feature was not provided. The collaboration system only worked over <span class="interface">1cDialog.com</span> service.</td><td>You can install and use a local collaboration system server.</td></tr><tr title="Версия 8.3.11" class="tag_116 tag_29"><td><a name="9ba70472-9d16-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>If one of the key computer parameters was changed, a license activated on 1C:Enterpirse 8.2.15 or later is considered valid when verified with <span class="interface">ring license</span> command with <span class="interface">validate</span> option.<p>Using <span class="interface">--validate</span> parameter with <span class="interface">activate </span>or <span class="interface">prepare-request</span> option returns an error if a run-time error occurs when attempting to retrieve any of the key parameters. The behavior of these options when they are used without this parameter is not changed.</p><p>The <span class="interface">license </span>command requires <span class="interface">ring </span>utility version 0.8.</p></td><td>If one of the key computer parameters was changed, a license activated on 1C:Enterpirse 8.2.15 or later was considered invalid when verified with <span class="interface">ring license</span> command with <span class="interface">validate</span> option.<p>If a run-time error occured when attempting to retrieve any of the key parameters, the license was activated successfully and the corresponding license fields were filled with blank values, making the license impossible to use.</p><p>The <span class="interface">license </span>command required <span class="interface">ring </span>utility version<span class="interface"> </span>0.6.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_19 tag_29"><td><a name="4b95e865-117c-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of PostgreSQL version 9.4.5 from AstraLinux Special Edition 1.5 is implemented, starting with 1C:Enterprise version 8.3.11.3034.</td><td>PostgreSQL version 9.4.5 from AstraLinux Special Edition 1.5 was not supported.</td><td>Extended list of supported DBMS.</td></tr></table><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717c2d03-026f-11e7-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.11" class="compat tag_115 tag_1"><td><a name="93602dd8-0582-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Improved usability of line selection in managed form tables. You can use <span class="interface">Ctrl </span>and <span class="interface">Shift </span>keys, as well as mouse buttons, to select table lines.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>The only way to select multiple lines in a managed form table was clicking each line while holding down <span class="interface">Ctrl</span>.</td><td>Improved usability of line selection in managed form tables.</td></tr><tr title="Версия 8.3.11" class="tag_28"><td><a name="ea9f3c28-059b-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>A single application can be accessed from multiple web browser tabs.</td><td>An attempt to run a second application instance in a second web browser tab generated an error.</td><td>The platform supports running multiple web client sessions in a single web browser.</td></tr><tr title="Версия 8.3.11" class="tag_70"><td><a name="774fea45-0d78-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>Implemented a unified name "access application" for all client application types in messages displayed during client application update over HTTP.</td><td>In messages displayed during client application update over HTTP, two terms were alternately used for client application: "data viewer" and "access program".</td><td>Unified terminology in messages related to access application update over HTTP.</td></tr><tr title="Версия 8.3.11" class="compat tag_115 tag_64 tag_1"><td><a name="75d0378f-0d79-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>When a managed form table is exported using the <span class="interface">Output list </span>command:<ul><li>The view of blank values of <span class="term">Number </span>and <span class="term">Date </span>type in the resulting document exactly matches their view in the form.</li><li>If the table is exported to a text document, tab characters separate all columns of the resulting document.</li></ul><p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>When a managed form table was exported using the <span class="interface">Output list </span>command:<ul><li>The view of blank values of <span class="term">Number </span>and <span class="term">Date </span>type in the resulting document might not exactly match their view in the form.</li><li>If the table was exported to a text document, tab characters were only added after the first column that contained a nonblank value.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_115 tag_64 tag_1"><td><a name="f5c632de-2b27-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>When a managed form table with multiple lines selected is exported using the <span class="interface">Output list </span>command (with the <span class="interface">Selected items only </span>check box selected):<ul><li>The lines are exported in their original order.</li><li>If the table displays a dynamic list in <span class="interface">Hierarchical list </span>or <span class="interface">Tree </span>mode, all of the selected lines are exported, regardless of their positions in the list hierarchy.</li></ul><p>The performance of the <span class="interface">Output list</span> command (with the <span class="interface">Selected items only </span>check box selected) is improved in the following scenario: the table displays a dynamic list, a large number of lines is selected, and the dynamic list query is not efficient.</p><p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>When a managed form table with multiple lines selected was exported using the <span class="interface">Output list </span>command (with the <span class="interface">Selected items only </span>check box selected):<ul><li>The lines were exported in the order they were selected.</li><li>If the table displayed a dynamic list in <span class="interface">Hierarchical list </span>or <span class="interface">Tree </span>mode, some of the lines were not exported.</li></ul><p>The performance of the <span class="interface">Output list</span> command (with the <span class="interface">Selected items only </span>check box selected) was insufficient in the following scenario: the table displayed a dynamic list, a large number of lines was selected, and the dynamic list query was not efficient.</p></td><td>Improved alrogithm of exporting a managed form table to a spreadsheet or text document.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="e0688874-0e27-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>The recipient selection procedure in context conversation messages is modified. If the sender does not want to notify any of the users who can see the message (i.e. users having the right to access the object that provides the context), they must explicitly select <span class="interface">No </span><span class="interface">noti</span><span class="interface">fication</span>.<p>Sending a message to an empty list of recipients is not allowed.</p></td><td>Sending a context message with an empty list of recipients was possible.</td><td>Improved notification usability.</td></tr><tr title="Версия 8.3.11" class="tag_26"><td><a name="008527e4-0fd9-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The commands that perform the following operations are added to the <span class="interface">Table </span>section of the main application menu:<ul><li>Align pictures (<span class="interface">Alignment </span>section)</li><li>Resize pictures (<span class="interface">Size </span>section)</li><li>Auto space multiple pictures (<span class="interface">Distribute </span>section)</li><li>Order pictures (<span class="interface">Order </span>section)</li></ul></td><td>These commands were not available in managed client applications.</td><td>Added support of interactive operations with pictures to managed applications.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="de74819c-2375-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>During video calls in the thin and web clients, 1C:Enterprise performs the diagnostics of Internet connection quality. If the quality is insufficient, 1C:Enterprise displays the diagnostics report over the video feed.</td><td>During video calls, if the Internet connection quality was insufficient, 1C:Enterprise did not display any diagnostics data. In some cases the picture might freeze without any explanations.</td><td>Diagnostics of Internet connection quality during collaboration system video calls are implemented.</td></tr><tr title="Версия 8.3.11" class="tag_12"><td><a name="abecefec-2381-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>If an application does not contain any objects that can be involved in totals management, when you attempt open the totals management dialog box in ordinary application mode (<span class="interface">Main menu</span> – <span class="interface">Operations </span>– <span class="interface">Totals management</span>), 1C:Enterprise displays a diagnostics message instead of the dialog box.</td><td>If an application did not contain any objects that could be involved in totals management, an attempt open the totals management dialog box in ordinary application mode (<span class="interface">Main menu</span> – <span class="interface">Operations </span>– <span class="interface">Totals management</span>) did not open the dialog box and no diagnostics messages were displayed.</td><td>Improved 1C:Enterprise usability.</td></tr><tr title="Версия 8.3.11" class="compat tag_115 tag_1"><td><a name="b977b422-2384-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The tab order of managed form groups does not depend on the <span class="term">United </span>property value of subordinate groups. It depends on group settings (horizontal or vertical).<p>This change is not implemented in 8.3.10 compatibility mode.</p><p>
</p></td><td>The tab order of managed form groups depended on the <span class="term">United </span>property value of subordinate groups. Groups where <span class="term">United </span>was set to <span class="term">False </span>were ignored, their settings did not affect the tab order.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_14"><td><a name="d7f20588-5732-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Pressing<span class="interface"> F1 </span>or using <span class="interface">Help</span><span class="interface"> </span>menu command always opens identical help pages regardless of client application or interface mode.</td><td>Pressing<span class="interface"> F1 </span>or using <span class="interface">Help</span><span class="interface"> </span>menu command might open different help pages depending on client application, interface mode, or help opening method.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="010b54f5-72b0-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>If forced switching to the recipients field of a context collaboration system conversation is performed (after an attempt to send a message without any recipients specified), once a user selects a recipient, the focus is set to the message text field.</td><td>If forced switching to the recipients field of a context collaboration system conversation was performed (after an attempt to send a message without any recipients specified), once a user selected a recipient (i.e. selected any option except for <span class="interface">No notification</span>), the focus stayed in the recipients field.</td><td>Improved interface for sending messages in context collaboration system conversations.</td></tr></table><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717c2d04-026f-11e7-a3f7-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.11" class="compat tag_19 tag_45 tag_1"><td><a name="7dc3e077-031e-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In applications that use PostgreSQL DBMS, the conversion of<span class="term"> LIKE `TEXT%` </span>query language operation to an SQL query operation is optimized.
This change is not implemented in 8.3.10 compatibility mode. </td><td>In applications that used PostgreSQL DBMS, the conversion of<span class="term"> LIKE `TEXT%` </span>query language operation to an SQL query operation was not optimal.</td><td>In applications that use PostgreSQL DBMS, improved performance of search by beginning of a string in the query language.</td></tr><tr title="Версия 8.3.11" class="compat tag_21 tag_1"><td><a name="58016f00-057a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>The access rights verification for full-text search results is optimized in scenarios where the search returns over 100 results.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>The performance of access rights verification for full-text search results in scenarios where the search returned over 100 results was insufficient.</td><td>Reduced time of getting full-text search results for users with access right restrictions in scenarios where the search returns over 100 results.</td></tr><tr title="Версия 8.3.11" class="tag_26"><td><a name="0bacf61e-057e-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The performance of <span class="term">CheckPut()</span> method of spreadsheet document is improved.</td><td>The performance of <span class="term">CheckPut()</span> method of spreadsheet document was insufficient.</td><td>Faster data output to a spreadsheet document in scenarios that include the check whether the output area fits a single page.</td></tr><tr title="Версия 8.3.11" class="tag_80 tag_6 tag_14"><td><a name="00d7b8be-0598-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 80); return false;">External reports and data processors</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Improved performance of loading external reports and data processors in client applications and on 1C:Enterprise server. Intensive work with external reports and data processors does not cause lags.</td><td>The performance of loading external reports and data processors in client applications and on 1C:Enterprise server was insufficient. Intensive work with external reports and data processors caused lags.</td><td>Eliminated 1C:Enterprise server lags in scenarios that involve inrtensive work with external reports and data processors.</td></tr><tr title="Версия 8.3.11" class="tag_37"><td><a name="ad615246-0598-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Improved 1C:Enterprise performance and scalability in scenarios that involve using <span class="term">HTTPConnection </span>and <span class="term">FTPConnection </span>objects on 1C:Enterprise server (if these connections belong to different sessions).<p>
</p></td><td>1C:Enterprise performance was significantly reduced in scenarios that involved using <span class="term">HTTPConnection </span>and <span class="term">FTPConnection </span>objects on 1C:Enterprise server (if these connections belonged to different sessions).</td><td>Improved 1C:Enterprise server performance in scenarios that involve multiple HTTP or FTP connections from different sessions.</td></tr><tr title="Версия 8.3.11" class="tag_19"><td><a name="028a65c0-059a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Improved performance of operations with temporary tables in scenarios that involve the following Microsoft SQL Server versions:<ul><li>2012, version 11.0.5548.0 or earlier</li><li>2014, version 12.0.2430.0 or earlier</li><li>2016</li></ul></td><td>The performance of operations with temporary tables in scenarios that involved some Microsoft SQL Server versions was insufficient.</td><td>Improved performance of operations with temporary tables in scenarios that involve some Microsoft SQL Server versions.</td></tr><tr title="Версия 8.3.11" class="tag_8 tag_37"><td><a name="3694b34e-059b-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>On Windows, improved the performance of cryptography operations and operations over SSL and TLS protocols in scenarios where these operations are running simultaneously in a large number of sessions.</td><td>On Windows, the performance of cryptography operations and operations over SSL and TLS protocols was insufficient in scenarios where these operations were running simultaneously in a large number of sessions.</td><td>On Windows, improved the performance of cryptography operations and operations over SSL and TLS protocols in scenarios where these operations are running simultaneously in a large number of sessions.</td></tr><tr title="Версия 8.3.11" class="tag_120 tag_38"><td><a name="76c354f3-08c5-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The performance of starting background jobs is improved in infobases that run in file mode and use extensions.</td><td>The performance of starting background jobs in infobases that ran in file mode and used extensions was insufficient.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_20"><td><a name="d01b4cf0-08c7-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The performance of the following Designer operations is improved:<ul><li>Opening 1C:Enterprise script editor</li><li>Extended module check</li></ul></td><td>The performance of the following Designer operations was insufficient:<ul><li>Opening 1C:Enterprise script editor</li><li>Extended module check</li></ul></td><td>Improved perfromance of frequently used development tools.</td></tr><tr title="Версия 8.3.11" class="tag_29"><td><a name="4c3dde6a-098c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The size of executable files of 1C:Enterprise is reduced.</td><td>Executable files of 1C:Enterprise required more disk space.</td><td>Reduced 1C:Enterprise requirements to available disk space.</td></tr><tr title="Версия 8.3.11" class="tag_20"><td><a name="9ca46f7f-1454-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In 1C:Enterprise script editor, the performance of the following operations is improved:<ul><li>Opening large modules</li><li>Opening context help</li><li>Switching to method or variable declaration</li><li>Module syntax check</li></ul></td><td>For large modules, the performance of 1C:Enterprise script editor was insufficient.</td><td>Improved usability for application developers.</td></tr><tr title="Версия 8.3.11" class="tag_93"><td><a name="97f344c0-259e-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br></td><td>Improved the performance of loading infobases from <span class="interface">.</span><span class="interface">dt </span>files in systems that use IBM DB2.</td><td>Loading infobases from <span class="interface">.</span><span class="interface">dt </span>files in systems that used IBM DB2 took more time.</td><td>Reduced time of moving infobases in systems that use IBM DB2.</td></tr><tr title="Версия 8.3.11" class="tag_52 tag_6"><td><a name="1a6328c5-267a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The 1C:Enterprise server performance in scenarios with simultaneous posting of large documents (dozens of thousands of lines) is improved.</td><td>Simultaneous posting of large documents (dozens of thousands of lines) could hang the server cluster.</td><td>Improved performance of 1C:Enterprise server under heavy load.</td></tr><tr title="Версия 8.3.11" class="tag_26"><td><a name="279d1f0a-2a67-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The performance of drawing spreadsheet documents with a lot of pictures in hidden rows is improved.</td><td>Drawing spreadsheet documents with a lot of pictures in hidden rows took more time.</td><td>Improved performance of operations with spreadsheet documents that contain a lot of pictures in hidden rows.</td></tr><tr title="Версия 8.3.11" class="tag_19"><td><a name="5b064d48-5729-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Optimized operations with large temporary tables in PostgreSQL.</td><td>The performance of operations with large temporary tables in PostgreSQL was insufficient.</td><td>Improved performance of operations with large temporary tables in PostgreSQL.</td></tr><tr title="Версия 8.3.11" class="tag_19"><td><a name="4b2e3657-819d-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized.<p> </p></td><td>The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient.</td><td>Improved performance of temporary table operations.</td></tr><tr title="Версия 8.3.11" class="tag_93"><td><a name="8d00c7e4-bd4e-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br></td><td>In file infobases that contain large amounts of metadata, improved performance of metadata restructuring. The performance of restructuring data tables has not changed.</td><td>In file infobases that contained large amounts of metadata, metadata resturcturing took more time.</td><td>If a configuration contains a large amount of metadata and its metadata structure has changed, the performance of restructuring file infobases based on this configuration is improved.</td></tr><tr title="Версия 8.3.11" class="tag_115"><td><a name="9a7f6632-d8c6-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Improved performance of adding lines to form attributes of <span class="term">F</span><span class="term">ormDataTree</span> type in the thick and thin clients. The peformance improvement is most noticeable in trees that contain large numbers of lines.</td><td>Adding lines to form attributes of <span class="term">F</span><span class="term">ormDataTree</span> type took more time in trees that contained large numbers of lines.</td><td>Improved performance of operations with form data.</td></tr><tr title="Версия 8.3.11" class="tag_43"><td><a name="ceb6201b-d8c8-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Improved performance of opening forms that contain dynamic lists.</td><td>Opening forms that contained dynamic lists took more time.</td><td>Improved performance of opening forms that contain dynamic lists.</td></tr></table><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717c2d05-026f-11e7-a3f7-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.11" class="tag_14"><td><a name="48998d7b-031d-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>When 1C:Enterprise opens an infobase that is not registered in its infobase list, it creates a directory for storing the service data of the infobase. It creates an individual directory with a unique name for each infobase connection string and each infobase user. The maximum number of directories is 20.</td><td>When 1C:Enterprise opened an infobase that was not registered in its infobase list, it used a directory with a predefined name for storing the service data of all such infobases: <span class="interface">00000000-0000-0000-0000-00000000000</span>.</td><td>The service data of infobases that are not registered in the infobase list is stored in dedicated directories. This facilitates disk space management and prevents the growth of a single directory.</td></tr><tr title="Версия 8.3.11" class="compat tag_20 tag_1"><td><a name="72efc32a-0573-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>When a custom command of a metadata object is renamed, the platform checks whether the new name exactly matches the name of any standard command of that metadata object. The platform also performs this check during the configuration logical integrity check.</td><td>This feature was not provided.<p>Names of custom commands of a metadata object could exactly match the names of its standard commands.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_63"><td><a name="bf00dd88-0574-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The chart scale view settings are expanded, they now include scale view, color, and position, scale label angle, grid line visibility and color, and more.<p>For <span class="term">C</span><span class="term">hartScale </span>object, the following properties are implemented: <span class="term">GridLinesShowMode</span>, <span class="term">GridLine</span>, <span class="term">GridLineC</span><span class="term">olor</span>, <span class="term">LabelF</span><span class="term">ont</span>, <span class="term">LabelC</span><span class="term">olor</span>, <span class="term">LabelOrientation</span>, <span class="term">MaxLabelRows</span>, <span class="term">LabelAngle</span>, <span class="term">LabelFormat</span>, <span class="term">ScaleLocation</span>, <span class="term">ScaleLine</span>, <span class="term">ScaleLineC</span><span class="term">olor</span>, <span class="term">ScaleStep</span>, <span class="term">ScaleMarkLocation</span>, and <span class="term">ScaleLabelLocation</span>.</p><p>The following properties of <span class="term">ChartPlotArea </span>object are deprecated, they are supported solely for compatibility purposes:</p><ul><li><span class="term">ShowSeriesScaleLab</span><span class="term">els</span>. Use <span class="term">SeriesScale.</span><span class="term">ScaleLabelLocation</span> instead.</li><li><span class="term">ShowPointsScaleLabels</span>. Use <span class="term">PointsScale</span><span class="term">.</span><span class="term">ScaleLabelLocation</span> instead.</li><li><span class="term">ShowValuesScaleLabels</span>. Use <span class="term">ValuesScale.</span><span class="term">ScaleLabelLocation</span> instead.</li><li><span class="term">ShowScaleValueLines</span>. Use <span class="term">ValuesScale</span><span class="term">.</span><span class="term">GridLinesShowMode</span> instead.</li><li><span class="term">ValueScaleFormat</span>. Use <span class="term">ValuesScale</span><span class="term">.</span><span class="term">LabelFormat</span> instead.</li><li><span class="term">LabelsOrientation</span>. Use <span class="term">PointsScale</span><span class="term">.</span><span class="term">LabelOrientation</span> instead.</li></ul><p>In version 8.3.10 compatibility mode, the following properties are hidden from the property palette and do not affect the chart view:</p><ul><li><span class="term">LabelAngle</span></li><li><span class="term">ScaleLocation</span></li><li><span class="term">MaxLabelR</span><span class="term">ows</span></li><li><span class="term">ScaleMarkLocation</span></li><li><span class="term">ScaleLabelLocation</span></li></ul></td><td>These features were not provided.<p>The chart scale view settings were simpler.</p></td><td>Expanded chart view options.</td></tr><tr title="Версия 8.3.11" class="compat tag_21 tag_1"><td><a name="e762bfa0-0579-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>The following full-text search features are implemented:<ul><li>In privileged mode, the platform does not check the access rights for objects processed by full-text search.</li><li>The option to specify whether full-text search gets object presentations is implemented. The <span class="term">FullTextSearchList.GetPresentat</span><span class="term">io</span><span class="term">n </span>property is implemented. The platform always checks the access rights for the object fields that form the presentation, regardless of the value of this property.</li><li>The platform always checks the access rights for the object fields that form the object description, regardless of the value of <span class="term">FullTextSearchList.GetDescription</span><span class="term"> </span>property.</li></ul><p>To apply these changes, disable the compatibility mode and rebuild the full-text search index. Previous 1C:Enterprise versions cannot work with indexes built in version 8.3.11 with compatibility mode disabled.
This change is not implemented in 8.3.10 compatibility mode.</p></td><td>Full-text search worked as follows:<ul><li>In privileged mode, the platform checked the access rights for objects processed by full-text search.</li><li>The platform did not check the access rights for object fields that formed the presentation if <span class="term">FullTextSearchList.GetDescription</span><span class="term"> </span>property was set to <span class="term">False</span>.</li></ul></td><td>Optimized full-text search.</td></tr><tr title="Версия 8.3.11" class="compat tag_25 tag_26 tag_1"><td><a name="13913638-057c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the data compostion system, nested charts and tables of the resulting spreadsheet document are located in spreadsheet document groupings. The data composition system template composer creates blank templates with <span class="term">VerticalLevel </span>property set. These templates follow the templates of charts and tables located in groupings.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In the data compostion system, the resulting spreadsheet document did not contain groupings for charts and nested tables that did not have row groupings. The template composer did not create blank templates with <span class="term">VerticalLevel </span>property set that followed the chart templates. For tables located in groupings, the composer created blank templates with <span class="term">VerticalLevel </span>set to 0.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_56 tag_1"><td><a name="231d4200-059e-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>The option to download XSD documents that import schemas that require HTTP requests to external servers (with redirects) is implemented.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>The option to download XSD documents that imported schemas that required HTTP requests to external servers (with redirects) was not available.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_20 tag_14"><td><a name="961f2e5c-089f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>In the search and replace dialog box of the text editor, the following behavior of the <span class="interface">Replace </span>button is implemented:<ul><li>If the selected text fragment matches the search string, replace it and search for the next occurrence.</li><li>Otherwise search for the next occurrence. Clicking <span class="interface">Replace </span>again replaces it. </li></ul></td><td>In the search and replace dialog box of the text editor, clicking the <span class="interface">Replace </span>button searched for the next occurrence of the search string. Clicking <span class="interface">Replace </span>again replaced it.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_26 tag_1"><td><a name="4df032b0-08a5-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the dialog box for setting a spreadsheet document area name, the default name is generated in the language that matches the current 1C:Enterprise script variant.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In the dialog box for setting a spreadsheet document area name, the default name was generated in the language that matched the client application interface language.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_20"><td><a name="62e3f3f2-08c2-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During the creation of a configuration update file, the message stating that the configuration update requires 1C:Enterprise version 8.3.9.2033 or later is no longer displayed.</td><td>During the creation of a configuration update file, the message stating that the configuration update required 1C:Enterprise version 8.3.9.2033 or later was displayed.</td><td>Removed a message that is no longer relevant.</td></tr><tr title="Версия 8.3.11" class="tag_56"><td><a name="66f8da8c-08cc-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>When an XSD schema is imported to an XDTO package, for references to global elements and attributes, the <span class="term">default </span>and <span class="term">fixed </span>properties are imported to <span class="term">DefaultValue </span>and <span class="term">Fixed </span>properties, regardless of the element or attribute declaration type.</td><td>When an XSD schema was imported to an XDTO package, for references to global elements and attributes, the <span class="term">default </span>and <span class="term">fixed </span>properties that were specified locally were not imported.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_43"><td><a name="c1ff7620-08ce-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>If a dynamic list contains <span class="term">PredefinedDataName </span>and <span class="term">DataVersion </span>fields, the following rules apply to these fields:<ul><li>Only the following comparison types are available: <span class="interface">Equal to</span>, <span class="interface">Not equal</span>, <span class="interface">In list</span>, <span class="interface">Not in list</span>, <span class="interface">Filled</span>, and <span class="interface">Empty</span>.</li><li>Search through the search field of the dynamic list is not supported.</li><li>Advanced search is only available by exact match.</li></ul></td><td>If a dynamic list contained <span class="term">PredefinedDataName </span>and <span class="term">DataVersion </span>fields, the following rules applied to these fields:<ul><li>All comparison types were available.</li><li>Search through the search field of the dynamic list generated an error.</li><li>Advanced search allowed selection of any search type but generated an error if search at beginning of line or anywhere in the line was selected.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_69"><td><a name="e3d580aa-0966-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The option to omit a notification description handler is implemented. Use this option in scenarios where you would create an empty handler (because the result of the execution of an asynchronous method is not important and only the handler for the method errors is important).<p>Now you can omit any parameter of the <span class="term">NotifyDescription </span>constructor.</p></td><td>A handler for asynchronous method errors could only be created together with an empty handler for the method execution result.</td><td>Simplified handling of asynchronous method errors.</td></tr><tr title="Версия 8.3.11" class="compat tag_41 tag_1"><td><a name="06e7cfe6-0972-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>When 1C:Enterprise accesses a file name using the properties of <span class="term">ZipFileEntry </span>object (this includes the scenario when a file is being written to the disk), it replaces invalid characters with underscores (_). The list of invalid characters includes all characters that are not allowed in Windows file names. 1C:Enterprise makes the replacement on all operating systems.This change is not implemented in 8.3.10 compatibility mode.<p>To provide access to the original file names (before the character replacement), the following properties are implemented for <span class="term">ZipFileEntry </span>object: <span class="term">OriginalFullName</span>, <span class="term">OriginalName</span>, <span class="term">OriginalPath</span>, <span class="term">OriginalExtension</span>, and <span class="term">OriginalBaseName</span>.</p></td><td>If a name of a file stored in a ZIP archive contained invalid characters, the name was truncated, leaving only the part before the first invalid character. The list of invalid characters included all characters that were not allowed in Windows file names. This might cause issues when extracting files whose names contained invalid characters.</td><td>Any file can be successfully extracted from a ZIP archive on any operating system. The names of the extracted files might change,</td></tr><tr title="Версия 8.3.11" class="tag_64 tag_26"><td><a name="bbe8c4c0-0989-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The look of a spreadsheet document containing SVG pictures in the thin client exactly matches the look of that document in the following cases:<ul><li>In the web client</li><li>When exported to HTML5 format</li></ul></td><td>The look of a spreadsheet document containing SVG pictures in the thin client could differ from the look of that document in the following cases:<ul><li>In the web client</li><li>When exported to HTML5 format</li></ul></td><td>Unified look of spreadsheet documents in various client applications and export formats.</td></tr><tr title="Версия 8.3.11" class="tag_93 tag_6"><td><a name="08034d6f-0d7d-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>In client/server mode, the reliability of the following operations is improved:<ul><li>Restructure database configuration</li><li>Create initial image of a distributed infobase</li><li>Restore infobase from a <span class="interface">.dt </span>file </li></ul></td><td>In client/server mode, the following operations might cause issues:<ul><li>Restructure database configuration</li><li>Create initial image of a distributed infobase</li><li>Restore infobase from a <span class="interface">.dt </span>file</li></ul></td><td>Improved reliability of some operations in client/server mode.</td></tr><tr title="Версия 8.3.11" class="tag_26 tag_28"><td><a name="93dab91e-0e1f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>When a spreadsheet document is exported to PDF format, the resulting document includes the page size and orientation (<span class="term">PickTrayByPDFSize</span> property of a PDF document).<p>If you need to print the resulting document on custom-size paper from a web browser, it is recommended that you set the <span class="term">PrintAccuracy </span>property of the spreadsheet document to <span class="term">Accurate</span>. In Microsoft Internet Explorer, you do not need to use this property.</p></td><td>When a spreadsheet document was exported to PDF format, the resulting document did not include the page size and orientation. Printing the resulting document required a manual check of paper size and orientation in the PDF viewer.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_36 tag_2"><td><a name="83d28e2d-0e29-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>If you access the <span class="term">UsePurpose </span>property of the entire configuration or a managed form from 1C:Enterprise script, it has <span class="term">Undefined </span>value.</td><td>When the <span class="term">UsePurpose </span>property of the entire configuration or a managed form was accessed from 1C:Enterprise script, it had <span class="term">FixedArray </span>type, with the selected values as array elements.</td><td>Eliminated unexpected system behavior. The behavior of this property is now similar to the behavior of other properties that do not affect application functionality in 1C:Enterprise mode.</td></tr><tr title="Версия 8.3.11" class="tag_28"><td><a name="bfaf3e1f-0ef0-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client, the performance of opening system dialog boxes, as well as dialog boxes opened using <span class="term">ShowQueryBox() </span>and <span class="term">ShowMessageBox() </span>methods, is improved.</td><td>In the web client, opening system dialog boxes, as well as dialog boxes opened using <span class="term">ShowQueryBox() </span>and <span class="term">ShowMessageBox() </span>methods, took more time.</td><td>Improved performance and reliability of the window subsystem of the web client.</td></tr><tr title="Версия 8.3.11" class="compat tag_26 tag_1"><td><a name="389df3c3-0ef1-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In spreadsheet documents, there is no spacing between pictures and their borders.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In spreadsheet documents, unexprected spacing might appear between pictures and their borders.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_21 tag_1"><td><a name="ea661063-0ef1-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Morphological full-text search by attribute name is now supported.<p>It is recommended that you rebuild the full-text search index in order to use this feature.</p><p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>Morphological full-text search by attribute name was not supported.</td><td>Full-text search by attribute name is more user-friendly.</td></tr><tr title="Версия 8.3.11" class="compat tag_105 tag_1"><td><a name="569618cd-1088-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td><span class="term">ThisNode() </span>method of <span class="term">ExchangePlan </span>object always returns a reference to the exchange plan item with <span class="term">ThisNode </span>property set to <span class="term">True</span>.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td><span class="term">ThisNode() </span>method of <span class="term">ExchangePlan </span>object did not always return a reference to the exchange plan item with <span class="term">ThisNode </span>property set to <span class="term">True</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_45"><td><a name="3df46765-1469-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In the query language, if a <span class="term">CASE </span>operation includes a nested <span class="term">CASE </span>operation or<span class="term"> </span><span class="term">ISNULL()</span><span class="term"> </span>function, which uses both a virtual field and a nonvirtual field, the <span class="term">CASE </span>calculation result is correct.</td><td>In the query language, if a <span class="term">CASE </span>operation included a nested <span class="term">CASE </span>operation or<span class="term"> </span><span class="term">ISNULL()</span><span class="term"> </span>function, which used both a virtual field and a nonvirtual field, the <span class="term">CASE </span>calculation result was incorrect and this might cause an unexpected shutdown.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_63 tag_1"><td><a name="74f2caed-1471-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The chart view in the thin client and web client is unified:<ul><li>Area sizes specified in the form attribute always affect the chart view.</li><li>Chart behavior is unified across client applications.</li><li>Area sizes used to draw a chart exactly match the area sizes retrieved using 1C:Enterprise script.</li></ul><p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>The chart views in the thin client and web client were different:<ul><li>Area sizes specified in the form attribute did not always affect the chart view.</li><li>Chart behavior was not unified across client applications.</li><li>Area sizes used to draw a chart did not exactly match the area sizes retrieved using 1C:Enterprise script.</li></ul></td><td>Eliminated unexpected system behavior. The chart view is more predictable.</td></tr><tr title="Версия 8.3.11" class="compat tag_20 tag_1"><td><a name="aab0f445-1486-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During application debug, you can access variable properties (provided that it has properties) even if the variable presentation is not available.</td><td>During application debug, if a variable presentation was not available, the variable properties were also not available.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_27"><td><a name="f4e2f140-237d-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>Intertactive export of configurations to files is always performed in hierarchical format. The flat format is only supported in batch Designer mode.<p>It is recommended that you always use the hierarchical format.</p></td><td>The interactive export of configurations to files offered a choice between flat and hierarchical formats.</td><td>The option to export configuration files in flat format is disabled due to possible issues. For example, transferring exported files between different file systems might be difficult.</td></tr><tr title="Версия 8.3.11" class="tag_20"><td><a name="1497ae05-2676-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During debugging over TCP, debugger no longer stops responding while calculating an expression or editing a variable value.</td><td>During debugging over TCP, debugger might stop responding while calculating an expression or editing a variable value.</td><td>Application debugging over TCP is more predictable and reliable.</td></tr><tr title="Версия 8.3.11" class="tag_14"><td><a name="2a482837-4543-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>In the <span class="interface">Start </span>menu, a single shortcut combines 32-bit and 64-bit versions of 1C:Enterprise.<p>1C:Enterprise installation on a computer with any operation system of Windows family adds all of the available 1C:Enterprise shortcuts to the <span class="interface">Start </span>menu.</p><p>Pinning a running 1C:Enterprise application to the taskbar actually pins a shortcut to file <span class="interface">1cestart.exe</span>. If multiple 1C:Enterprise applications are running, they are combined into a single taskbar shortcut.</p><p>The jump list is only available if the shortcut to <span class="interface">1cestart.exe</span> is pinned to the taskbar.</p></td><td>The <span class="interface">Start </span>menu included two 1C:Enterprise shortcuts: one for the 32-bit version and the other one for the 64-bit version.<p>1C:Enterprise installation on Windows 8 or later did not add all of the available 1C:Enterprise shortcuts to the <span class="interface">Start </span>menu.</p><p>Pinning a running 1C:Enterprise application to the taskbar pinned exactly that application. If multiple 1C:Enterprise applications were running, they were combined in this shortcut.</p><p>The jump list was available for any 1C:Enterprise-related shortcut.</p></td><td>All of the 1C:Enterprise components are available on the <span class="interface">St</span><span class="interface">art </span>menu. The jump list behaviour is more predictable.</td></tr><tr title="Версия 8.3.11" class="tag_25"><td><a name="a00c393c-45e9-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The parsing algorithm of data composition system queries validates comparison operations that include <span class="term">String </span>parameters of unlimited length. The parsing is performed when the data composition system wizard is opened and when a schema-based source of available settings is initialized (opening reports also includes this operation).</td><td>The parsing algorithm of data composition system queries that included <span class="term">String </span>parameters of unlimited length generated errors stating that using strings of unlimited length in queries was not allowed.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="19cbae58-45ed-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>In the collaboration system, video calls use peer-to-peer connections instead of using a central server. The central server is only required to establish connections between the conversation participants.</td><td>In the collaboration system, video calls always used the central server and did not use peer-to-peer connections.</td><td>Reduced load on the central server of the collaboration system. If conversation participants belong to a local network, the video call traffic is limited to local network.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="864b4faf-45ee-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>If 1C:Enterprise connects to the collaboration server through a proxy server, it gets the proxy server settings from the operating system settings or from <span class="interface">inetcfg.xml</span> configuration file. NTLM authentication at proxy servers is not supported.</td><td>Connection to the collaboration server through a proxy server was not supported.</td><td>Simplified collaboration system setup in scenarios that include a proxy server.</td></tr><tr title="Версия 8.3.11" class="compat tag_16 tag_1"><td><a name="6d430567-819f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>When an information register record set is written using <span class="term">InformationRegisterRecordSet</span><span class="term">.</span><span class="term">Write</span><span class="term">()</span>, <span class="term">Undefined </span>value is not ignored when setting a managed lock.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>When an information register record set was written using <span class="term">InformationRegisterRecordSet</span><span class="term">.</span><span class="term">Write</span><span class="term">()</span>, <span class="term">Undefined </span>value was ignored when setting a managed lock. This resulted in locking excessive data.</td><td>Improved parallel writing of information register record sets when multiple users write dimensions of composite types where dimension values can be blank.</td></tr><tr title="Версия 8.3.11" class="tag_84"><td><a name="3c94bcab-8287-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Support of Kazakh user interface (<span class="interface">kk</span> language code) is restored.</td><td>Support of Kazakh user interface was not available.</td><td>1C:Enterprise now provides the option to use Kazakh user interface.</td></tr><tr title="Версия 8.3.11" class="tag_84"><td><a name="a69b46bd-93bd-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The French interface language (language code: <span class="interface">fr</span>) is not supported.</td><td>The French interface language (language code: <span class="interface">fr</span>) was supported.</td><td>The French interface language is not supported.</td></tr><tr title="Версия 8.3.11" class="tag_6"><td><a name="ea8c585f-a759-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>On Linux, the working process parameter <span class="interface">Memory occupied</span> is calculated based on VmRSS (resident set size) value.<p>The value of <span class="interface">Memory occupied</span> parameter in absolute terms is reduced and it is more accurate.</p><p>It is recommended that you revise the working process restart options in the working server properties.</p></td><td>On Linux, the working process parameter <span class="interface">Memory occupied</span> was calculated based on VmSize (virtual memory usage) value.<p>
</p><p>
</p></td><td>On Linux, the cluster monitoring system uses a parameter that provides more accurate data.</td></tr><tr title="Версия 8.3.11" class="tag_84"><td><a name="6d54366b-acde-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>Entering Russian Ruble symbol (₽, ISO 4217 643) from the keyboard is supported.</td><td>This feature was not provided.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_23"><td><a name="3b68c0e7-ba58-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>When floating point numbers are converted between 1C:Enterprise format and external formats, the accuracy of their presentations is never lost.<p>In scenarios where previously accuracy losses were possible, the conversion algorithm does not depend on the operating system.</p></td><td>When floating point numbers were converted between 1C:Enterprise format and external formats, accuracy losses were possible.<p>In scenarios where accuracy losses were possible, the conversion algorithm depended on the operation system.</p></td><td>Reduced number of scenarios where conversion of floating point numbers with significant digits in their fractional parts between 1C:Enterprise format and external formats (such as XSL file format) introduces accuracy losses.</td></tr><tr title="Версия 8.3.11" class="tag_15"><td><a name="fa9d61d0-d8c5-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Improved reliability of the Linux version of 1C:Enterprise in some scenarios.</td><td>In some scenarios, reliability of the Linux version of 1C:Enterprise was insufficient.</td><td>Improved stability of the Linux version of 1C:Enterprise.</td></tr><tr title="Версия 8.3.11" class="tag_17"><td><a name="e7f596a9-e17a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>Updated the <span class="term">&lt;ADMIN&gt;</span> event content and description in the documentation and in the technological log configuration file editor. (<a href="http://1c-dn.com/developer_tools/universal_reports_and_data_processors/" target="_blank">read more</a>)</td><td>The <span class="term">&lt;ADMIN&gt;</span> event content and description in the documentation and in the technological log configuration file editor were incorrect.</td><td>The technological log configuration file editor is now up-to-date.</td></tr><tr title="Версия 8.3.11" class="tag_73"><td><a name="1039c9c1-117d-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>The <span class="interface">Cannot reference table... </span>error never occurs after clicking the <span class="interface">Accept </span>button in the <span class="interface">Restructure data </span>window. Previously this prevented database configuration update.<p>This error message appears before you have the option to click the <span class="interface">Accept </span>button. To eliminate the issue that causes the error message, run infobase verification and repair.</p></td><td>The <span class="interface">Cannot reference table...</span> error might occur after clicking the <span class="interface">Accept </span>button in the <span class="interface">Restructure data</span> window. This prevented database configuration update.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_43 tag_1"><td><a name="d378cbf1-4961-11e9-b692-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>When you press <span class="interface">Enter </span>(or double-click) in a row of a table linked to a dynamic list or when you call the <span class="term">ChangeRow()</span> form table method, a form table extension will open a form linked to this row only if there is the <span class="interface">Change </span>command in the commands.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>When you pressed <span class="interface">Enter </span>(or double-clicked) in a row of a table linked to a dynamic list or when you called the <span class="term">ChangeRow() </span>form table method, a form table extension opened a form linked to this row in any case.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717c2d06-026f-11e7-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.11" class="tag_37 tag_28 tag_29"><td><a name="0635eadc-04bc-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The web client no longer supports Microsoft Internet Explorer versions 8 and 9.</td><td>The web client supported Microsoft Internet Explorer versions 8 and 9.</td><td>Legacy versions of Microsoft web browser are no longer supported.
</td></tr><tr title="Версия 8.3.11" class="compat tag_69 tag_20 tag_1"><td><a name="b0db1b02-0599-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the thin and web clients, detection of attempts to assign a value to a nondeclared variable whose name matches a common module name is implemented. As a result, in this scenario the value is not assigned and an error message is generated.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In the thin and web clients, attempts to assign a value to a nondeclared variable whose name matched a common module name were not detected. In the web client, this caused an unexpected shutdown of the client application.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_45 tag_1"><td><a name="65521460-08ca-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>The <span class="term">Move()</span> method of <span class="term">QuerySchemaQueryBatch</span>, <span class="term">QuerySchemaOperators</span>, <span class="term">QuerySchemaColumns</span>, <span class="term">QuerySchemaIndexExpressions</span>, <span class="term">QuerySchemaOrderExpressions</span>, and <span class="term">QuerySchemaTotalCalculationFields </span>objects shifts the specified collection element by the specified number of positions.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>The behavior of the <span class="term">Move() </span>method was different from the standard one:<ul><li>For <span class="term">QuerySchemaQueryBatch</span> and <span class="term">QuerySchemaOperators</span> objects, the method moved the element found by index specified in the first parameter to the position that was calculated as a maximum of the first and second parameters.</li><li>For <span class="term">QuerySchemaColumns</span>, <span class="term">QuerySchemaIndexExpressions</span>, <span class="term">QuerySchemaOrderExpressions</span>, and <span class="term">QuerySchemaTotalCalculationFields </span>objects, the method moved the element found by index specified in the first parameter to the position specified in the second method parameter.</li></ul></td><td>The behavior of the <span class="term">M</span><span class="term">ove() </span>methods is unified with the behavior of <span class="term">Move() </span>methods in other collections.</td></tr><tr title="Версия 8.3.11" class="compat tag_115 tag_43 tag_110 tag_1"><td><a name="96e2a00d-0d7a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br></td><td>Upgrade: if the current user does not have enough rights to access form items related to commands of table or form extensions for dynamic lists, the items are hidden, regardless of the method used to add them (explicitly by application developers or automatically by the extensions).<p>Upgrade: the following commands are removed from the managed form table context menu: O<span class="term">utputList,</span> <span class="term">ListSettings</span>, <span class="term">LoadDynamicListSettings</span>, <span class="term">SaveDynamicListSettings</span>, <span class="term">DynamicListStandardSettings</span>, <span class="term">List</span>, <span class="term">HierarchicalList</span>, and <span class="term">Tree</span>. Upgrade: the submenu <span class="interface">Generate </span>is always added as the last menu item regardless of the hierarchy.</p><p>Upgrade: advanced search commands and list settings commands are added to tables that contain a dynamic list with the main table, filter criterion, or enumeration.</p><p>Upgrade: upon a form creation, if a table is removed, all commands related to the table are also removed. It happens, for example, when the user does not have the right to view the main table of the dynamic list related to the form table.</p><p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>If the current user did not have enough rights to access form items related to commands of table or form extensions for dynamic lists, the items were hidden only if they were added automatically by the extensions. If they were added explicitly by application developers, they were still visible (but unavailable to the user).<p>If the managed form table displayed a dynamic list without the main table, the following commands were added to the context menu: O<span class="term">utputList,</span> <span class="term">ListSettings</span>, <span class="term">LoadDynamicListSettings</span>, <span class="term">SaveDynamicListSettings</span>, and <span class="term">DynamicListStandardSettings</span>. If the managed form table displayed a dynamic list with the main table that supported hierarchy, the following commands were added to the context menu: <span class="term">List</span>, <span class="term">HierarchicalList</span>, and <span class="term">Tree</span>. The submenu <span class="interface">Generate </span>was added to different parts of the context menu depending on the displayed table.</p><p>Advanced search commands and list settings commands were not added to tables that contained a dynamic list with the main table, filter criterion, or enumeration.</p><p>Upon a form creation, if a table is removed, most of commands related to the table were also removed. However, one command (usually, Update) was never removed.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_43 tag_1"><td><a name="6549d3eb-0f04-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>You can hide folder pictures in hierarchical dynamic lists. To hide the pictures, clear the <span class="term">RowPictureDataPath </span>property of the table that displays the hierarchical dynamic list.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>Hiding folder pictures in hierarchical dynamic lists was not available. Clearing the <span class="term">RowPictureDataPath </span>property of the table that displayed the hierarchical dynamic list did not hide the pictures.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_70"><td><a name="b97b3e83-0f06-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>The timeout for downloading a client application distribution kit over HTTP is removed.<p>You can cancel downloading by clicking <span class="interface">Cancel </span>in the dialog box that displays the progress.</p></td><td>Downloading a client application distribution kit over HTTP was terminated if it took more than 600 seconds.</td><td>Downloading a client application distribution kit using a slow connection channel is now possible.</td></tr><tr title="Версия 8.3.11" class="compat tag_36 tag_1"><td><a name="71ffa53e-0fa9-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>In the <span class="term">TextReader </span>object constructor, if <span class="term">LineSplitter </span>parameter is omitted, this is treated as setting it to <span class="term">Chars.LF</span>. If <span class="term">ConvertibleSplitterOfLines </span>parameter is omitted, this is treated as setting it to <span class="term">Chars.LF + Chars.CR</span>.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In the <span class="term">TextReader </span>object constructor, if <span class="term">LineSplitter</span> or <span class="term">ConvertibleSplitterOfLines </span>parameter was omitted, this was treated as setting it to a blank string.</td><td>Eliminated unexpected system behavior. The values of omitted parameters now match the Syntax Assistant descriptions.</td></tr><tr title="Версия 8.3.11" class="compat tag_93 tag_1"><td><a name="29a6be26-0fad-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br></td><td>A composite index that includes attributes with <span class="term">Index </span>property set to <span class="interface">Index with additional ordering</span> no longer depends on the attribute order. The order of the atttributes in the index is fixed.<p>The index is rebuilt during the first object restructuring after disabling compatibility mode.
This change is not implemented in 8.3.10 compatibility mode.</p></td><td>A composite index that included attributes with <span class="term">Index </span>property set to <span class="interface">Index with additional ordering</span> depended on the attribute order. If the order was changed, the platform rebuilt the index.</td><td>The effect of the attribute order on the database index structure is reduced.</td></tr><tr title="Версия 8.3.11" class="compat tag_45 tag_1"><td><a name="b1ee77d4-0faf-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>The attempt to execute a query that contains <span class="term">MIN() </span>or <span class="term">MAX() </span>aggregate function with the following parameter types generates an error:<ul><li><span class="term">UUID </span>and system enumeration</li><li><span class="term">UUID </span>and any primitive type</li><li>System enumeration and any primitive type</li></ul><p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>The attempt to execute a query that contained <span class="term">MIN() </span>or <span class="term">MAX() </span>aggregate function with the following parameter types did not generate an error:<ul><li><span class="term">UUID </span>and system enumeration</li><li><span class="term">UUID </span>and any primitive type</li><li>System enumeration and any primitive type</li></ul><p>Such a query might return an incorrect result or cause an unexpected shutdown.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_45 tag_1"><td><a name="6db0af72-0fb0-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>A query that contains <span class="term">ISNULL()</span> or <span class="term">CASE</span><span class="term">() </span>operation that applies to result of <span class="term">MAX() </span>or <span class="term">MIN() </span>function (provided that parameters of these functions include values of <span class="term">UUID </span>type or system enumerations, and provided that the other operand of <span class="term">ISNULL()</span> or <span class="term">CASE</span><span class="term">() </span>is a value of primitive type or another system enumeration) returns the correct result.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>A query that contained <span class="term">ISNULL()</span> or <span class="term">CASE</span><span class="term">() </span>operation that applied to result of <span class="term">MAX() </span>or <span class="term">MIN() </span>function (provided that parameters of these functions included values of <span class="term">UUID </span>type or system enumerations, and provided that the other operand of <span class="term">ISNULL()</span> or <span class="term">CASE</span><span class="term">()</span> was a value of primitive type or another system enumeration) returned <span class="term">UNDEFINED</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_63 tag_1"><td><a name="3bb7cefe-0fb2-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>In charts that use the default palette, the default colors of chart scales and series are changed. New system enumeration value is implemented: <span class="term">ChartColorPalette.SoftAdaptive</span>.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In charts that used the default palette, the default colors of chart scales and series were different.</td><td>Imoroved view of charts with default settings.</td></tr><tr title="Версия 8.3.11" class="compat tag_115 tag_1"><td><a name="35ee3b36-0fd3-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the standard processing of a <span class="term">ChoiceDataGetProcessing </span>event handler of configuration object managers, correct handling of <span class="term">Undefined </span>value of <span class="term">Parameters.SearchString</span> parameter is implemented. If this value is set to <span class="term">Undefined</span>, the system behavior is similar to quick choice, it returns the list of all database items for this configuration object.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In the standard processing of a <span class="term">ChoiceDataGetProcessing </span>event handler of configuration object managers, if <span class="term">Parameters.SearchString</span> parameter was set to <span class="term">Undefined</span>, it was treated as an empty search string.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_45 tag_1"><td><a name="921552d0-0fd4-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In the <span class="term">Parameters </span>collection of the <span class="term">Query </span>object, the parameter type used in a comparison operation (&gt;, &gt;=, &lt;, &lt;=, =, &lt;&gt;) applies to both operation parameters, however, their type qualifiers do not have to be identical. For example, if the first parameter is a string, you can specify a string of unlimited length as a second parameter.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In the <span class="term">Parameters </span>collection of the <span class="term">Query </span>object, the parameter type used in a comparison operation (&gt;, &gt;=, &lt;, &lt;=, =, &lt;&gt;) and its type qualifier were applied to both operation parameters.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_25 tag_1"><td><a name="0941af76-0fd6-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When you add a condition with <span class="interface">Empty </span>comparison type to a query, the data composition system adds the condition to a nested query in the right part of a left join only if it cannot add the condition to the parent query. Otherwise, it never adds such conditions to nested queries.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>When a condition was added to a query, the data composition system always attempted to add the condition to a nested query. If the nested query was located in the right part of a left join, the condition was duplicated in the parent query.</td><td>When a query includes a nested query located in the right part of a left join, the data composition system provides a more predictable result.</td></tr><tr title="Версия 8.3.11" class="compat tag_78 tag_1"><td><a name="fd234b88-2380-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>The <span class="term">CreateDirectory()</span> and <span class="term">BeginCreatingDirectory()</span> methods generate exceptions if the directory name contains invalid characters.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>The <span class="term">CreateDirectory()</span> and <span class="term">BeginCreatingDirectory()</span> methods did not analyze the directory name. If the directory name contained invalid characters, the directory was not created and no error messages were generated.</td><td>1C:Enterprise checks whether the names of directories to be created are valid.</td></tr><tr title="Версия 8.3.11" class="compat tag_115 tag_1"><td><a name="6bd7ba50-241b-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>A managed form group with <span class="term">HorizontalAlignInGroup </span>property set to <span class="term">Center </span>is centered relative to the parent group.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>A managed form group with <span class="term">HorizontalAlignInGroup </span>property set to <span class="term">Center </span>was aligned left relative to the parent group.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="compat tag_115 tag_1"><td><a name="dd8bfc76-241d-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If <span class="term">ShapeRepresentation </span>property of a managed form button is set to <span class="term">None </span>and its <span class="term">BackColor </span>property is set to any value except <span class="term">Auto</span>, the button has transparent background.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>If <span class="term">ShapeRepresentation </span>property of a managed form button was set to <span class="term">None </span>and its <span class="term">BackColor </span>property was set to any value except <span class="term">Auto</span>, the button background color was taken from the <span class="term">BackColor </span>property.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_81"><td><a name="022edc54-2a6a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>If an application is published to a web server using <span class="interface">webinst </span>utility with <span class="interface">-descriptor</span> option, the <span class="term">pubdst</span>, <span class="term">pubdst32</span>, and <span class="term">pubdst64</span> attributes of the root <span class="term">point</span> element are copied from the publication template to the resulting <span class="interface">default.vrd </span>file.</td><td>If an application was published to a web server using <span class="interface">webinst </span>utility with <span class="interface">-descriptor</span> option, the <span class="term">pubdst</span>, <span class="term">pubdst32</span>, and <span class="term">pubdst64</span> attributes of the root <span class="term">point</span> element were not copied from the publication template to the resulting <span class="interface">default.vrd </span>file.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_33"><td><a name="f12acc2e-78fc-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 33); return false;">Documentation</a>.<br></td><td>The description of <span class="term">SessionParameters</span><span class="term">.</span><span class="term">Clear</span><span class="term">()</span> method in Syntax Assistant now states that calling this method requires the right to change all session parameters that are used in the method (possibly all parameters available in the session).</td><td>The description of <span class="term">SessionParameters</span><span class="term">.</span><span class="term">Clear</span><span class="term">()</span> method in Syntax Assistant was incorrect.</td><td>The Syntax Assistant topic is now up-to-date.</td></tr><tr title="Версия 8.3.11" class="compat tag_115 tag_1"><td><a name="3f5eba81-b7f1-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If a managed form attribute is created using 1C:Enterprise script, it can be accessed only with <span class="term">ThisObject.</span> prefix.<p>This change is not implemented in 8.3.10 compatibility mode.</p></td><td>In some scenarios, managed form attributes created using 1C:Enterprise script could be accessed without <span class="term">ThisObject.</span> prefix.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_10"><td><a name="4be80976-ba52-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>New version of Java-based 1C:Enterprise Administrative Service API, which is compatible with 1C:Enterprise 8.3.11, is available (<a href="http://1c-dn.com/library/1c_enterprise_8_administrative_service_api/" target="_blank">read more</a>).</td><td>The previous version of Java-based 1C:Enterprise Administrative Service API was compatible with 1C:Enterprise versions 8.3.10 and earlier.</td><td>You can select Java-based 1C:Enterprise Administrative Service API version that is compatible with your 1C:Enterprise version.</td></tr><tr title="Версия 8.3.11" class="tag_29"><td><a name="88c6c71c-c087-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The minimum system requirements for some operating systems of Windows family have changed:<ul><li>Windows XP Service Pack 3</li><li>Windows Vista Service Pack 2</li><li>Windows 7 Service Pack 1</li><li>Windows Server 2008 Service Pack 2</li><li>Windows Server 2008R2 Service Pack 1</li></ul><p>The system requirements for other Windows versions have not changed.</p><p>If an operating system does not match the requirements, 1C:Enterprise generates a warning with a recommendation to install the required update.</p><p>If you choose the installation option that does not have user interface and the operating system does not match the requirements, the cluster console and the COM connection module are not registered.</p><p>1C:Enterprise distribution package for Windows includes Visual C++ Redistributable for Visual Studio 2015.</p><p><span class="interface">1CEClientMakeSetup</span> utility requires Visual C++ Redistributable to generate distribution packages for platform versions 8.3.11 and later.</p></td><td>The minimum system requirements for some operating systems of Windows family were:<ul><li>Windows XP Service Pack 3 (the installer did not check whether the service pack was installed)</li><li>Windows Vista</li><li>Windows 7</li><li>Windows Server 2008</li><li>Windows Server 2008R2</li></ul></td><td>The platform installer installs the required redistributables and displays warnings about unsupported operating systems.</td></tr><tr title="Версия 8.3.11" class="tag_6 tag_10"><td><a name="008c030b-e178-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can use server cluster administration tools (both Java-based and administration server-based) for administering any 1C:Enterprise server cluster version, starting with 8.3.9. You can even use features that are not available in some administration server (<span class="interface">ras</span>) versions and server cluster versions.</td><td>Server cluster administration tools (both Java-based and administration server-based) were compatible only with 1C:Enterprise server clusters that had the same version. In most cases, exact version matches were required.</td><td>Simplified server cluster administration. Reduced cost of adapting the administrative infrastructure to new 1C:Enterprise server cluster versions.</td></tr><tr title="Версия 8.3.11" class="tag_4"><td><a name="bb59f253-00ed-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>
<p>Creating a displayed context conversation with a specific list of participants from 1C:Enterprise script is not supported. In this scenario, the <span class="term">CollaborationSystemConversation.Write() </span>method throws an exception.</p></td><td>Creating a displayed context conversation with a specific list of participants was allowed.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_37"><td><a name="bf973098-4478-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Security profile restrictions do not impact the following objects: <ul><li><span class="term">OpenSSLSecureConnection</span></li><li><span class="term">OSCertificationAuthorityCertificates</span></li><li><span class="term">WindowsCertificationAuthorityCertificates</span></li><li><span class="term">LinuxCertificationAuthorityCertificates</span></li><li><span class="term">WindowsClientCertificate</span></li></ul></td><td>If a security profile was applied, the following objects were not available:<ul><li><span class="term">OpenSSLSecureConnection</span></li><li><span class="term">OSCertificationAuthorityCertificates</span></li><li><span class="term">WindowsCertificationAuthorityCertificates</span></li><li><span class="term">LinuxCertificationAuthorityCertificates</span></li><li><span class="term">WindowsClientCertificate</span></li></ul></td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717c2d07-026f-11e7-a3f7-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.11" class="tag_0"><td><a name="31fd7cc4-04ba-11e7-a3f7-0050569f678a"></a>The name of <span class="term">CREATEINFOBASE</span> command-line option parameter that specifies whether the infobase is added to the infobase list. The previous name is supported for compatibility purposes.</td><td><ul><li><span class="term">AddInList</span>.</li></ul></td><td><ul><li><span class="term">AddToList</span>.</li></ul></td></tr><tr title="Версия 8.3.11" class="tag_0"><td><a name="04e38150-0575-11e7-a3f7-0050569f678a"></a>Name of the property of <span class="term">ChartPlotArea </span>object. The previous name is supported for compatibility purposes.</td><td><ul><li><span class="term">ShowScale</span></li></ul></td><td><ul><li><span class="term">ShowScales</span></li></ul></td></tr><tr title="Версия 8.3.11" class="compat tag_0 tag_1"><td><a name="4f94d4e1-71d8-11e7-a3f7-0050569f678a"></a>Data composition system output parameter property <span class="term">ChartType.ChartBubbleSizing</span>.<p>In 8.3.10 compatibility mode, the old name is used (in 1C:Enterprise language and when writing the parameter to an XML file).</p></td><td><ul><li><span class="term">ChartType.ChartBubbleSizing</span>.</li></ul></td><td><ul><li><span class="term">ChartType.BubbleSizing</span>.</li></ul></td></tr></table><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717c2d08-026f-11e7-a3f7-0050569f678a">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.11" class="tag_48"><td><a name="dbc6a697-0eea-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The following permissions are implemented for iOS mobile applications:<ul><li><span class="interface">Background location</span>. The mobile application gets location data even when it is inactive.</li><li><span class="interface">Background audio playback</span>. The mobile application plays audio even when it is inactive.</li><li><span class="interface">File exchange with PC</span>. Use this permission for mobile applications that exchange files through iTunes.</li></ul></td><td>These features were not provided.</td><td>Expanded settings for iOS mobile applications.</td></tr><tr title="Версия 8.3.11" class="tag_115"><td><a name="0ac3d3f0-0fda-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the mobile platform, the object that visualizes planner data (the planner) is now available.<p>For the object usage specifics, see the documentation.</p></td><td>The planner was only available on the platform for personal computer.</td><td>Expanded data presentation options on mobile devices.</td></tr><tr title="Версия 8.3.11" class="compat tag_48 tag_1"><td><a name="8ad5b664-0fdc-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Support of local and push notifications is added to the mobile platform for Windows. 1C:Enterprise uses Windows Notification Services for this purpose. The notification sending service provided by 1C Company does not support Windows Notification Services.<p>The system enumeration value <span class="term">DeliverableNotificationSubscriberType.WNS</span> is implemented.The <span class="term">DeliverableNotificationSendManager.GetAccessToken() </span>method is implemented.</p><p>Notification sending errors are returned in the return value of <span class="term">DeliverableNotificationSendManager.Sen</span><span class="term">d()</span> method.This change is not implemented in 8.3.10 compatibility mode.</p><p>The system enumeration <span class="term">DeliverableNotificationSendErrorType </span>is implemented. The <span class="term">DeliverableNotificationSendIssue</span><span class="term">Information</span><span class="term"> </span>object is implemented.</p><p>For <span class="term">DeliverableNotificationSendManager.Sen</span><span class="term">d()</span> method, the <span class="term">DeliverableNotificationSendIssuesInformation </span>parameter is implemented.</p><p>The option to get a local notification when a device is crossing a geofence border is implemented.</p></td><td>Support of local and push notifications was only available for iOS and Android devices.<p>Notification sending errors generated exceptions.</p></td><td>Standard user notifications are now available on mobile Windows devices. Both mobile applications and desktop applications can generate notifications (local and push notifications, respectively).</td></tr><tr title="Версия 8.3.11" class="tag_29"><td><a name="1987df6e-0fdf-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support for Android versions earlier than 4.0 is ended. The earliest supported API version is API 14 (Androuid 4.0).</td><td>Android versions with API 9 (Android 2.3) or later were supported.</td><td>Ended support for legacy Android versions.</td></tr><tr title="Версия 8.3.11" class="tag_77 tag_26"><td><a name="b8be71c8-0fdf-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the mobile platform, support of batch printing is implemented.</td><td>This feature was not provided.</td><td>Batch printing is now available in the mobile platform.</td></tr><tr title="Версия 8.3.11" class="tag_78"><td><a name="a0fe20cc-0fe1-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>On the mobile platform, the file selection dialog box now supports multiple file masks. The search by mask in the file selection dialog box and the search by mask with <span class="term">FindFiles() </span>method are now case-insensitive. The file selection dialog box and <span class="term">FindFiles() </span>method now support iOS and Android wildcards.</td><td>The file selection dialog box did not support multiple file masks. The search by mask in the file selection dialog box and the search by mask with <span class="term">FindFiles() </span>method were case-sensitive. The file selection dialog box and <span class="term">FindFiles() </span>method did not support iOS and Android wildcards.</td><td>Expanded file operation tools in the mobile platform. These tools are unified with file operation tools available in the desktop platform.</td></tr><tr title="Версия 8.3.11" class="tag_111"><td><a name="126c1002-1859-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 111); return false;">Formatted documents</a>.<br></td><td>The mobile platform now supports <span class="term">FormattedDocument </span>object (and can display formatted documents in managed forms).</td><td>This feature was not provided.</td><td>Expanded support of formatted text in mobile applications.</td></tr><tr title="Версия 8.3.11" class="tag_48"><td><a name="3a985d20-4520-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>On the mobile platform for Windows (except Windows 8.1), support of map operations is implemented. The following methods are now available: <span class="term">ShowOnMap()</span>, <span class="term">GetAddressByLocation()</span>, and <span class="term">GetLocationByAddress()</span>.<p>Global context method <span class="term">MapRepresentationSupported()</span> is implemented.</p></td><td>Map operations were not supported on Windows mobile devices.</td><td>Extended mobile platform capabilities on Windows. Determining whether map operations are available is standardized with other operations that might be unavailable on some devices or operating systems.</td></tr><tr title="Версия 8.3.11" class="tag_128"><td><a name="2a7cfc67-452c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 128); return false;">Mobile applications</a>.<br></td><td>When a configuration that was saved using an earlier 1C:Enterprise version for personal computer is loaded to a mobile application, the mobile device displays a warning and provides the option to cancel the operation.</td><td>When a configuration was loaded on a mobile device, 1C:Enterprise did not check whether the configuration was saved using an earlier 1C:Enterprise version for personal computer.</td><td>Implemented diagnostics of potential compatibility issues between the mobile platform and the configuration to be loaded (in scenarios where the configuration was saved using an earlier 1C:Enterprise version for personal computer).</td></tr><tr title="Версия 8.3.11" class="tag_48"><td><a name="fd8093b6-5724-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>On Android devices, the following operations with SMS messages are implemented:<ul><li>Get SMS log and check whether getting the log is allowed. For <span class="term">TelephonyTools </span>object, methods <span class="term">SMSLogSupported()</span> and <span class="term">GetSMSLog()</span> are implemented.The <span class="term">SMSLog </span>object is implemented.</li><li>Filter SMS messages.</li><li>Create a message based on another message. The wizard that creates an SMS message based on an SMS log entry is implemented.</li></ul><p>On Android devices, in method <span class="term">SMSLog.FindRecords()</span>, ungrouped filter items are combined using AND operator.</p></td><td>On Android devices, access to SMS message log was not provided.<p>On Android devices, in method <span class="term">SMSLog.FindRecords()</span>, ungrouped filter items were combined using OR operator.
</p></td><td>Introduced advanced SMS management tools on Android devices.<p>The behavior of the filter used in a search in the SMS message log is unified with other filters.</p></td></tr><tr title="Версия 8.3.11" class="tag_73"><td><a name="d1709af2-72b1-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>In built mobile applications, the message stating that unused data will be deleted is no longer displayed after configuration updates.<p>The mobile platform for developers displays a message stating that the update changes metadata structure (only when it actually changes it).</p><p>The developers are now responsible for preventing data losses caused by configuration updates.</p></td><td>If a configuration update changed metadata structure, a message stating that unused data will be deleted was displayed after the update.<p>The message was displayed both in built mobile applications and in the mobile platform for developers.</p></td><td>Configuration updates are now less distressing to end users. In patricular, end users do not get a message that their data will be lost (which was not always true). At the same time, developers must be more cautious when implementing configuration changes that might cause losses or user data.</td></tr><tr title="Версия 8.3.11" class="compat tag_48 tag_1"><td><a name="01af48e6-46cf-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Universal date type values are now used in the following properties: <span class="term">CallLogRecord.Date</span>, <span class="term">CalendarEventData.Start</span>, and <span class="term">CalendarEventData.End</span>.<p>This change is not implemented in version 8.3.10 compatibility mode.</p></td><td>Local date type values were used in the following properties: <span class="term">CallLogRecord.Date</span>, <span class="term">CalendarEventData.Start</span>, and <span class="term">CalendarEventData.End</span>.</td><td>Date presentation now meets the general requirements of 1C:Enterprise platform.</td></tr><tr title="Версия 8.3.11" class="tag_48"><td><a name="ff93ccb1-52a0-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The split screen implemented in Android 7 is no longer supported in the mobile platform.</td><td>The split screen implemented in Android 7 was supported incorrectly.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.11" class="tag_48"><td><a name="ac807563-7869-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The mobile application now contains a set of predefined messages that describe mobile application demands on different permissions. They are displayed when a specific permission is required.<p>Developers cannot modify these messages.</p></td><td>If a specific permission was required for a mobile application, a user prompt contained only the name of the permission and response variants.There was no reason of permission demand stated in the prompt.</td><td>The mobile application permission prompts now meet the requirements of application stores and provide more information about the required permission.</td></tr></table><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717c2d09-026f-11e7-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.11" class="tag_0"><a name="9f0b1cb3-f5eb-11e7-a3f7-0050569f678a"></a>The libtiff library is updated to version 4.0.9.</li><li title="Версия 8.3.11" class="tag_0"><a name="21a7a4b2-00ec-11e8-a3f7-0050569f678a"></a>The libpng library is updated to version 1.6.34.</li><li title="Версия 8.3.11" class="tag_0"><a name="32b2c797-00ec-11e8-a3f7-0050569f678a"></a>The zlib library is updated to version 1.2.11.<p>
</p></li><li title="Версия 8.3.11" class="tag_0"><a name="c589cab2-e97f-11e7-a3f7-0050569f678a"></a>The curl library is updated to version 7.57.0.</li><li title="Версия 8.3.11" class="tag_0"><a name="d59d59ad-e97f-11e7-a3f7-0050569f678a"></a>The OpenSSL library is updated to version 1.0.2n.</li></ul><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="717c2d0a-026f-11e7-a3f7-0050569f678a">Transition from the previous version to the version 8.3.11</a></h2><ul><li title="Версия 8.3.11" class="tag_0"><a name="717c2d0b-026f-11e7-a3f7-0050569f678a"></a>Conversion of configurations, infobases, external data processors, and external reports is not required during the transition from the previous version to the version 8.3.11.
</li><li title="Версия 8.3.11" class="tag_0"><a name="717c2d0c-026f-11e7-a3f7-0050569f678a"></a>Some features that are added in version 8.3.11 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.11" class="tag_0"><a name="080cf859-0ef2-11e7-a3f7-0050569f678a"></a>It is recommended that you rebuild the full-text search index in order to use morphological full-text search by attribute name.</li><li title="Версия 8.3.11" class="tag_0"><a name="7f1b1d68-7e7b-11e7-a3f7-0050569f678a"></a>In order to use the collaboration system in 1C:Enterprise 8.3.11 test release, you have to reregister the infobase. After the update to 1C:Enterprise 8.3.11 final release, you have to reregister it. The message history for the period between these two registrations will not be preserved.<p>
</p></li><li title="Версия 8.3.11" class="tag_0"><a name="1f6489cc-c9ec-11e7-a3f7-0050569f678a"></a>It is recommended that you uninstall your HASP Device Driver and then install HASP Device Driver 7.63, which is a part of 1C:Enterprise distribution package.</li></ul><p><a href="#717c2d01-026f-11e7-a3f7-0050569f678a"><small>Table of contents</small></a></p><h1><a name="ce205a1e-37b8-11e6-a3f7-0050569f678a">Version 8.3.10</a></h1><p title="Версия 8.3.10" class="tag_0"><a name="ce205a2a-37b8-11e6-a3f7-0050569f678a"></a>Version 8.3.10 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#ce205a1f-37b8-11e6-a3f7-0050569f678a">New functionality and changes</a></li><li><a href="#ce205a20-37b8-11e6-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#ce205a21-37b8-11e6-a3f7-0050569f678a">Optimization</a></li><li><a href="#ce205a22-37b8-11e6-a3f7-0050569f678a">Changes that affect system behavior</a></li><li><a href="#ce205a23-37b8-11e6-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#ce205a24-37b8-11e6-a3f7-0050569f678a">Renamed objects</a></li><li><a href="#ce205a25-37b8-11e6-a3f7-0050569f678a">Mobile platform</a></li><li><a href="#ce205a26-37b8-11e6-a3f7-0050569f678a">Library updates
</a></li><li><a href="#ce205a27-37b8-11e6-a3f7-0050569f678a">Transition from the previous version to the version 8.3.10</a></li></ul><h2><a name="ce205a1f-37b8-11e6-a3f7-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.10" class="compat tag_2 tag_1"><td><a name="aa6bc911-897b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>For configuration property <span class="interface">Compatibility mode</span>, new value <span class="interface">Version 8.3.9</span> is now implemented.</td><td>Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.8 was implemented.</td><td>Configurations developed in version 8.3.9 or earlier now run in version 8.3.10 without requiring any changes to configuration or to data structures. This allows for transition to version 8.3.10 in two stages: first, version update is applied (without any changes to configuration); then, any needed changes are applied and compatibility mode is disabled. This also allows using version 8.3.9 for infobase operations, if necessary, after transition to version 8.3.10. Compatibility mode must be enabled to use version 8.3.9. If you disabled it, enable it again.</td></tr><tr title="Версия 8.3.10" class="tag_81"><td><a name="40e781e5-897b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>In the "publish to web server" dialog box, parameters related to OpenID authentication are now on a separate tab.
In the "publish to web server" dialog box, also implemented entering a list of URLs that can be used for user redirection after OpenID authentication.</td><td>The only method of specifying a list of URLs that can be used for user redirection after OpenID authentication was to edit <span class="interface">default.vrd</span> file manually.</td><td>When publishing to web servers, you can interactlvely specify all of the parameters defined in <span class="interface">default.vrd</span> file.</td></tr><tr title="Версия 8.3.10" class="tag_70"><td><a name="b35a6905-8a0b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>Rules for detecting computers with Ukrainian language pack are improved. When a 1C:Enterprise client application is being installed on Windows, the installer language and the default platform language are set to Ukrainian if at least two of the following conditions are met:<ul><li>The home location specified in the operating system settings is Ukraine.</li><li>Ukrainian keyboard layout is installed.</li><li>Ukrainian hryvnia (UAH) is selected as the currency unit.</li><li>Ukrainian locale is selected in the operating system settings.</li><li>Ukrainian is set as the default operating system language.</li></ul></td><td>When a 1C:Enterprise client application was being installed on Windows, the default platform language was set to Ukrainian only if the primary operating system language was Ukrainian. The only way to run the installer in Urkainian was using the <span class="interface">/luk</span> command-line option.</td><td>Improved 1C:Enterprise installer usability for Ukrainian speakers.</td></tr><tr title="Версия 8.3.10" class="tag_69 tag_10"><td><a name="43092c4b-8b19-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Implemented functionality for collecting information on circular references during 1C:Enterprise script execution. Using this feature may result in reduced application performance. It is recommended that you use this feature for testing purposes only.
Implemented global context method <span class="term">CheckScriptCircularRefs()</span>. For technological log settings file (<span class="interface">logcfg.xml</span>), implemented item <span class="term">&lt;SCRIPTCIRCREFS&gt;</span>. Implemented technological log event <span class="term">&lt;SCRIPTCIRCREFS&gt;</span>.
Implemented command-line option for the thin client and thick client startup: <span class="term">/EnableCheckScriptCircularRefs</span>. Implemented command-line parameter for 1C:Enterprise server startup: <span class="term">-EnableCheckScriptCircularRefs</span>.
In the dialog box used to specify client application startup parameters from Designer, implemented parameter<span class="interface"> Detect 1C:Enterprise script circular references</span>.
Implemented parameter <span class="term">EnableCheckScriptCircularRefs</span> in file <span class="interface">conf.cfg</span>.
If 1C:Enterprise is started with option/parameter <span class="term">EnableCheckScriptCircularRefs</span>, discovery of any circular reference will result in unrecoverable error containing information on the discovered circular reference.</td><td>This feature was not provided.</td><td>Diagnostics of circular reference usage in 1C:Enterprise script is now more intuitive.</td></tr><tr title="Версия 8.3.10" class="tag_38"><td><a name="ae1fb022-8b1a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>In module editor, implemented functionality for adding a specific method to extension (when working with a configuration being extended).
In module editor, implemented navigation from annotation of extending method to method being extended (when working with an extension).
Implemented keyboard shortcut<span class="term"> Alt+Shift+F2 </span>for command <span class="interface">Add to extension</span>. Keyboard shortcut <span class="term">Alt+F2 </span>for this command is now disabled.</td><td>User-friendly functionality for adding methods to extensions was not available.
Navigation from annotation of extending method to method being extended was not available.
Keyboard shortcut <span class="term">Alt+F2 </span>was used for command <span class="interface">Add to extension</span>.</td><td>Creating 1C:Enterprise script-based module extensions is now more ergonomic.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="f7e48492-8edd-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Implemented additional processing for data received by a dynamic list before the data is displayed. Implemented event <span class="term">OnGet</span><span class="term">Data</span><span class="term">AtServer</span>.
In version 8.3.7 compatibility mode, behavior remained unchanged.</td><td>This feature was not provided.</td><td>It is now easier to use dynamic lists to output linked data that was previously extremely difficult or impossible to obtain through dynamic list query.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="f8fe9c4e-8f87-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Implemented arbitrary scaling of managed forms in <span class="interface">Taxi </span>interface. If compact display mode is set at application level, interactive scaling is disabled. Form size settings are saved per DPI value and per form scale value. Implemented managed form property <span class="term">Scale</span>, command <span class="interface">Change scale </span>in client application menu <span class="interface">View</span>, and system command bar button used to open the scale change dialog box. This change is not implemented in 8.3.6 compatibility mode.
Implemented support for picture variant sets in client applications for PC (thick client, thin client, and web client).
Added variants of system pictures used for client applications.
Implemented new resolutions for picture variants: bldpi (85% scale), aldpi (125% scale), amdpi (175% scale), and udpi (400% scale). In picture variant set manifest, implemented choice of target interface for each variant. To define size of picture variants more precisely, implemented parameters for height and width of each variant in picture variant set manifest.
For system enumeration <span class="term">PictureSize</span>, implemented values <span class="term">Real</span><span class="term">SizeIgnore</span><span class="term">Scale</span> and <span class="term">AutoSizeIgnore</span><span class="term">Scale</span>.</td><td>This feature was not provided. Compact viewing mode was available at form level and at application level (through 1C:Enterprise script).
Picture variant sets were supported in mobile application only.</td><td>Interface customization is now more user-friendly.</td></tr><tr title="Версия 8.3.10" class="tag_69"><td><a name="c691dc90-8fc0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Implemented generation of text strings whose content depends on a number specified in a string. Examples: <span class="interface">1st week of the month</span>, <span class="interface">2nd week of the month</span>. Implemented the<span class="term"> StringWith</span><span class="term">Number()</span> function.
The following langauges are supported: Azerbaijanian, Belarusian, Chinese, Bulgarian, English, Estonian, Finnish, French, Georgian, German, Hungarian, Kazakh, Kyrgyz, Latvian, Lithuanian, Polish, Romanian, Russian, Turkish, Turkmenian, Ukrainian, and Vietnamese,</td><td>This feature was not provided.</td><td>Generation of text strings whose content depends on a number specified in a string is now streamlined.</td></tr><tr title="Версия 8.3.10" class="tag_26"><td><a name="cd734820-8fc1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Implemented getting data area size value during import from third-party spreadsheet formats: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument).
For object <span class="term">SpreadsheetDocument</span>, implemented methods <span class="term">GetDataAreaHorizontalSize()</span> and <span class="term">GetDataAreaVertical</span><span class="term">Size()</span>.</td><td>This feature was not provided.</td><td>It is now easier to import documents in third-party spreadsheet formats without clearly defined boundaries of imported data area.</td></tr><tr title="Версия 8.3.10" class="tag_20 tag_129"><td><a name="17e30660-905f-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 129); return false;">OData interface</a>.<br></td><td>Implemented server debug item <span class="interface">Standard OData interface </span>intended for debugging 1C:Enterprise script running during queries to standard OData interface.
Changed debug item sorting rules that apply to debug item lists (for HTTP debug protocol). Changed auto attachment dialog box (for TCP debug protocol). </td><td>Debugging of 1C:Enterprise script running at the server side during infobase calls through standard OData interface was not supported. Debug item sorting rules that apply to debug item lists (for HTTP debug protocol) were different. Auto attachment dialog box for TCP debug protocol displayed debug items in a different order. </td><td>It is now easier to debug 1C:Enterprise scripts using standard OData interface.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="81b00608-95e5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The option to manage height for managed form tables that display data other than dynamic lists is implemented. This includes the option to have table height resized automatically based on the amount of data displayed. The <span class="term">HeightControlVariant </span>managed form table property is implemented.<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>This option was not provided on the desktop platform. It was only available on the mobile platform. The <span class="term">HeightControlVariant </span>managed form table property was ignored on the desktop platform.</td><td>The option to add a form table that does not display dynamic list data and still is automatically resized based on the number of rows is implemented. This reduces the number of scroll bars and saves form space.</td></tr><tr title="Версия 8.3.10" class="tag_116 tag_17"><td><a name="baf5e2c2-ec4a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>For technological log, implemented registration of events associated with:<ul><li>Granting and releasing licenses (both software and HASP)</li><li>Granting licenses to base versions</li><li>Regular checks for discrepancies between the actual hardware and the list of hardware components stated in a license</li></ul><p>Implemented technological log event <span class="term">&lt;LIC&gt;</span>.</p><p>The <span class="term">&lt;HASP&gt;</span> technological log event allows to analyze technological aspects of HASP management only (HASP interface calls); it does not allow to monitor granted or released licenses with HASP keys.</p></td><td>This feature was not provided. Only the option to check HASP key operations using the <span class="term">&lt;HASP&gt;</span> event was provided.</td><td>Easier investigation of license-related issues.</td></tr><tr title="Версия 8.3.10" class="tag_25"><td><a name="88924768-9780-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Values of type <span class="term">DataComposionSchemaNested</span><span class="term">DataSet</span> can now be added to collection <span class="term">DataComposionSchemaDataSetFields</span>. Implemented values of type <span class="term">DataComposionSchemaDataSetFields </span>to be used in methods<span class="term"> Add() </span>and <span class="term">Insert() </span>of object <span class="term">DataComposionSchemaDataSetFields</span>.</td><td>Values of type <span class="term">DataComposionSchemaNested</span><span class="term">DataSet</span> could not be added to collection <span class="term">DataComposionSchemaDataSetFields</span>.</td><td>Now it is possible to create a data composition schema with nested data sets using 1C:Enterprise script.</td></tr><tr title="Версия 8.3.10" class="tag_115"><td><a name="506a2e10-99de-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Implemented control of planner interval background color in accordance with values of measurements associated with this interval.
Implemented property <span class="term">Planner</span><span class="term">BackgroundInterval.DimensionValues</span>.</td><td>Planner interval background color management based on the values of dimensions associated with this interval was not available. Planner interval background color could only be changed for date intervals.</td><td>Visual customization of planner is enriched.</td></tr><tr title="Версия 8.3.10" class="tag_20"><td><a name="61c96d4f-b164-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Implemented option for running Designer in agent mode. This is a variation of batch mode where Designer operates as an SSH or SFTP server and accepts commands sent through these protocols.
While in agent mode, Designer can only work with a single infobase at a time. If access to multiple infobases is required, it is recommended that you run several instances of Designer in agent mode.
Implemented command-line options for batch mode: <span class="term">/AgentMode</span>, <span class="term">/AgentPort</span>, <span class="term">/AgentListenAddress</span>,<span class="term"> /AgentSSHHostKey</span>, <span class="term">/AgentSSHHostKeyAuto</span>, and <span class="term">/AgentBaseDir</span>.
Changed behavior of command-line options <span class="term">/Visible </span>and <span class="term">/LoadConfigFromFiles </span>when used in agent mode.
If you need a client application to connect to SSH or SFTP servers, you can now use any application with SSH/SFTP functionality that supports text command exchange with SSH and SFTP servers (examples: putty, winscp, MobaXTerm).
This functionality is currently available in beta status.</td><td>This feature was not provided.</td><td>Designer connectivity automation capabilities are now expanded. Response time of Designer is improved because a separate instance of Designer is no longer started on each call.</td></tr><tr title="Версия 8.3.10" class="tag_111"><td><a name="be3d892b-b21e-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 111); return false;">Formatted documents</a>.<br></td><td>Implemented saving formatted documents in PDF format (both in interactive mode and by using method <span class="term">FormattedDocument.Write()</span>) .
Implemented value <span class="term">FormattedDocumentFileType.PDF</span>.</td><td>This feature was not provided. Formatted documents could be only saved in HTML format or as plain text without formatting.</td><td>Formatted document management capabilities are now expanded.</td></tr><tr title="Версия 8.3.10" class="tag_26"><td><a name="ed34a078-b220-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Implemented 1C:Enterprise script-based management of how row, column, and cell names are displayed in spreadsheet documents.
For object <span class="term">SpreadsheetDocument</span>, implemented properties <span class="term">Show</span><span class="term">RowAndColumnNames </span>and <span class="term">Show</span><span class="term">CellNames</span>.
In spreadsheet document editor menu (in 1C:Enterprise mode), implemented commands for defining view of named areas and for assigning area names. </td><td>1C:Enterprise script-based management of how row, column, and cell names are displayed in spreadsheet documents was unavailable.</td><td>It is now easier to organize editing of spreadsheet documents containing named areas.</td></tr><tr title="Версия 8.3.10" class="tag_17"><td><a name="7a1c52ca-b226-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>Implemented logging of events that occur upon initial connection of 1C:Enterprise server to Microsoft SQL Server database. The events are saved in the technological log. The logging is based on event <span class="term">&lt;DBMSSQLCONN&gt;</span>.</td><td>This feature was not provided.</td><td>It is now easier to investigate incidents associated with loss of connection between 1C:Enterprise server and Microsoft SQL Server database.</td></tr><tr title="Версия 8.3.10" class="tag_38"><td><a name="59721717-b227-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The help available in a configuration being extended includes reference information on extension objects.
The reference information on the extension is included in the help search results.</td><td>This feature was not provided. Reference information implemented in a configuration extension was missing from the help tree and could not be accessed through searching.</td><td>Eliminated unexpected system behavior. Reference information from an extension is included in the help available in the configuration being extended, making it easier to use the resulting configuration.</td></tr><tr title="Версия 8.3.10" class="compat tag_26 tag_1"><td><a name="b34c61bf-b249-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When importing spreadsheet documents from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files, areas of the resulting document that match sheets of the original document are marked up as named row ranges. Names of sheets of the original document are converted into range names so as to satisfy rules of 1C:Enterprise script ID generation.<p>When importing spreadsheet documents from Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) files, sheets with no names provided are imported normally and areas defining these sheets are given automatically generated names. This change is not implemented in 8.3.9 compatibility mode.
</p></td><td>When importing spreadsheet documents from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files, areas of the resulting document that matched sheets of the original document were not marked up.<p>When importing spreadsheet documents from Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) files, sheets with no names provided were not imported.</p><p>
</p><p>
</p></td><td>It is now easier to process spreadsheet documents created by importing multipage XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files. It is now easier to recognize pages of the imported documents.</td></tr><tr title="Версия 8.3.10" class="tag_38"><td><a name="cb5caa1a-b2f5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>For configuration extensions, implemented configuration extension purposes: <span class="term">Patch</span>, <span class="term">Customization</span>, and <span class="term">AddO</span><span class="term">n</span>.<p>Extensions are applied in the following order:</p><ul><li>All extensions with purpose <span class="term">Patch</span></li><li>All extensions with purpose <span class="term">Customization</span></li><li>All extensions with purpose <span class="term">AddO</span><span class="term">n</span></li></ul><p>Multiple extensions with the same purpose are applied in no specific order.
Purpose of extensions that are already loaded to the infobase is automatically set to <span class="term">Customization</span>.
Implemented property <span class="term">ConfigurationExtension.Purpose</span>.</p></td><td>This feature was not provided.
All extensions were applied with the same priority.<p>
</p></td><td>It is now possible to sort extensions by function. It is now easier to understand the purpose of any extension.</td></tr><tr title="Версия 8.3.10" class="tag_38 tag_26"><td><a name="453bd0d7-b2fa-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Implemented extensions for spreadsheet documents.
Implemented merging of spreadsheet documents during configuration update that uses a file in <span class="interface">.cf </span>or <span class="interface">.cfu </span>format.</td><td>The spreadsheet document extension feature was not provided.<p>The feature allowing spreadsheet document merging during configuration update was not provided.</p></td><td>Configuration extension offers more features now.
Additional spreadsheet document management features are now provided for supported configurations.</td></tr><tr title="Версия 8.3.10" class="tag_79"><td><a name="2eac2a11-b56f-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>Implemented getting a specific picture from a picture variant collection based on DPI, display scale factor, and template picture flag.
For methods <span class="term">Convert()</span>, <span class="term">Write()</span>, <span class="term">GetBinaryData()</span>, and <span class="term">FileNameFilter()</span> of <span class="term">Picture </span>object , implemented parameters <span class="term">AllVariants </span>and <span class="term">Select</span><span class="term">Variant</span>.</td><td>Platform behavior upon attempt to get a specific picture from a picture variant collection was not defined. This activity could result in system failure.</td><td>Eliminated unexpected system behavior.
Getting a specific picture (best matching the current display mode) from a picture variant collection is now supported.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_1"><td><a name="cd2d262a-99f0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Now fractional values can be used to define boundaries of gauge chart bands.
This change is not implemented in 8.3.9 compatibility mode.</td><td>Fractional values could not be used to define boundaries of gauge chart bands.</td><td>An additional chart appearance control feature is now implemented.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_25 tag_1"><td><a name="e3ec9cc7-95e2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Implemented the following chart display options (also available in data composition system):<ul><li>Displaying trendlines</li><li>Customizing appearance of series in charts</li><li>Customizing appearance of series in chart legends</li></ul><p>Implemented system enumerations <span class="term">ChartTrendl</span><span class="term">ineApproximationType</span>, <span class="term">ChartTrendl</span><span class="term">ineFactor</span>, <span class="term">StockChartUsedPointValue</span>, <span class="term">ShowInChart</span>, and <span class="term">Show</span><span class="term">InChartLegend</span>. For system enumeration <span class="term">ChartLabel</span><span class="term">Location</span>, implemented values: <span class="term">Auto</span>, <span class="term">TopLeft</span>, <span class="term">BottomLeft</span>, <span class="term">TopRight</span>, <span class="term">BottomRight</span>, <span class="term">TopAndLeftS</span><span class="term">pecified</span>, and <span class="term">Empty</span><span class="term">Space</span>. For system enumeration <span class="term">ChartMa</span><span class="term">rkerType</span>, implemented values <span class="term">Alternation</span><span class="term"> </span>and <span class="term">Auto</span>.
Implemented objects <span class="term">ChartLabelArea </span>and <span class="term">ChartTrendl</span><span class="term">ine</span>.</p><p>For object <span class="term">ChartSeries</span>, implemented properties <span class="term">Trendl</span><span class="term">ines</span>, <span class="term">ShowGraphicalData</span><span class="term">Representation</span><span class="term">InChart</span>, and
<span class="term">ShowGraphicalData</span><span class="term">Representation</span><span class="term">InChartLegend</span>.
For property <span class="term">ChartSeries</span><span class="term">.Marker</span>, the default value is set to <span class="term">Auto</span>. This change is not implemented in 8.3.9 compatibility mode.
For objects <span class="term">DataCompositionAreaTemplateChartGroup</span><span class="term">Appearance </span>and <span class="term">DataCo</span><span class="term">mpositionAppearance</span>, implemented parameters <span class="term">ChartTrendline</span>,
<span class="term">ShowGraphicalData</span><span class="term">Representation</span><span class="term">InChart</span>, and
<span class="term">ShowGraphicalData</span><span class="term">Representation</span><span class="term">InChartLegend</span>.</p></td><td>These features were not provided.
Value of property <span class="term">ChartSeries</span><span class="term">.Marker</span> was set to <span class="term">Rect</span>, <span class="term">Circle</span>, or <span class="term">Rho</span><span class="term">mb</span>, based on series number.</td><td>Additional chart features, related to appearance control and analytics, are now implemented.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_25 tag_1"><td><a name="f578d490-b622-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Implemented new chart types: scatter chart and bubble chart. For <span class="term">Chart </span>object, implemented properties <span class="term">BubbleSizeCommonSeries</span>, <span class="term">BubbleSizeValueSource</span>, <span class="term">DefaultBubbleSize</span>, <span class="term">Min</span><span class="term">BubbleSize</span>, <span class="term">MaxBubbleSize</span>, <span class="term">ChartBubbleSizing</span>, and <span class="term">BubbleChartNegativeValuesShowMode</span>.<p>Implemented the following chart management features:</p><ul><li>Selecting data source for point axis. For <span class="term">Chart </span>object , implemented properties <span class="term">PointsAxisValuesSource </span>and <span class="term">PointsAxisSeries</span>.</li><li>Managing chart axis display options. For <span class="term">Chart </span>object, implemented properties <span class="term">ValuesAxis </span>and <span class="term">PointsAxis</span>.</li><li>Specifying fractional values for minimum and maximum chart values. Specifyimng the method used to determine minimum and maximum chart values. This change is not implemented in 8.3.9 compatibility mode.</li><li>Managing line connections between chart dots (where possible). Implemented property <span class="term">Chart.Points</span><span class="term">Connection</span>.</li><li>Use automated calculation of chart transparency. For system enumeration <span class="term">ChartSemit</span><span class="term">ransparencyMode</span>, implemented value <span class="term">AutoCalculate</span>.</li></ul><p>Expanded set of values that can be used in chart labels. For <span class="term">ChartLabelType </span>system enumeration, implemented values <span class="term">ValueSize</span>, <span class="term">SeriesSize</span>, <span class="term">SeriesValueSize</span>, <span class="term">SeriesPointSize</span>, <span class="term">SeriesPointValueSize</span>, <span class="term">PointSize</span>, and <span class="term">PointValueSize</span>.</p><p>For data composition system objects <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroup</span><span class="term">OutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance</span>, implemented parameters <span class="term">ChartType.ValuesAxis</span>, <span class="term">ChartType.PointsAxis</span>, <span class="term">ChartType.PointsAxisValuesSource</span>, <span class="term">ChartType.PointsAxisSeries</span>, <span class="term">ChartType.BubbleSizeValueSource</span>, <span class="term">ChartType.BubbleSizeCommonSeries</span>, <span class="term">ChartType.DefaultBubbleSize</span>, <span class="term">ChartType.MinBu</span><span class="term">bbleSize</span>, <span class="term">ChartType.Max</span><span class="term">BubbleSize</span>, <span class="term">ChartType.ChartBubbleSizing</span>, <span class="term">ChartType.BubbleChartNegativeValuesShowMode</span>, and <span class="term">ChartType.Po</span><span class="term">ints</span><span class="term">Connection</span>. For data composition system object <span class="term">DataCompositionAreaTemplateChartGroup</span><span class="term">Appearance</span>, implemented properties <span class="term">Put</span><span class="term">On</span><span class="term">PointsAxis</span> and <span class="term">UseAsCommonBubbleSize</span><span class="term">Series</span>.
Properties <span class="term">AutoMax</span><span class="term">Value </span>and <span class="term">AutoMin</span><span class="term">Value </span>are now deprecated and supported for compatibility purposes only.</p></td><td>These features were not provided.
Scatter charts and bubble charts were not implemented.
Fractional values could not be used for properties <span class="term">Min</span><span class="term">Value </span>and <span class="term">Max</span><span class="term">Value </span>of <span class="term">Chart </span>object. Properties <span class="term">AutoMin</span><span class="term">Value </span>and <span class="term">AutoMax</span><span class="term">Value </span>were used for calculating minimum and maximum chart values. </td><td>Additional chart features are now implemented.</td></tr><tr title="Версия 8.3.10" class="tag_63 tag_25"><td><a name="2bf2e04e-b639-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Implemented custom labels for chart scales. For <span class="term">ChartPlotArea </span>object, implemented properties <span class="term">PointsScale</span>, <span class="term">ValuesScale</span>, and <span class="term">SeriesScale</span>.
For data composition system objects <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroup</span><span class="term">OutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance</span>, implemented parameters <span class="term">ChartType.PointsScale</span>, <span class="term">ChartType.ValuesScale</span>, and <span class="term">ChartType.SeriesScale</span>.</td><td>These features were not provided.</td><td>Additional chart appearance control features are now implemented.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_25 tag_1"><td><a name="a1e7f0dc-b63c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Implemented custom point display order for bar charts. For <span class="term">Charts </span>object, implemented property <span class="term">BarChartPointsOrder</span>. This change is not implemented in 8.3.9 compatibility mode.<p>For data composition system objects <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroupOutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance</span>, implemented parameter <span class="term">ChartType.BarChartPoints</span><span class="term">Order</span>.</p></td><td>These features were not provided.
Points in bar charts were always displayed in bottom-to-top order (the first point at the bottom of the chart).</td><td>Additional chart appearance control features are now implemented.</td></tr><tr title="Версия 8.3.10" class="tag_25 tag_63"><td><a name="cf45a763-b63d-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Implemented customization of scale lines, scale color, series markers, series indicators, and series line types when displaying charts.
For data composition system objects <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroup</span><span class="term">OutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance</span>, implemented parameters <span class="term">ChartType.ScaleLines </span>and <span class="term">ChartType.ScaleColor</span>.
For data composition system objects <span class="term">DataCompositionAreaTemplateChartGroup</span><span class="term">Appearance </span>and <span class="term">DataCompositionAppearance</span>, implemented properties <span class="term">LineInChart</span>, <span class="term">MarkerInChart</span>, and <span class="term">IndicatorInChart</span>.</td><td>These features were not provided.</td><td>Additional features of chart appearance control through data composition system are now implemented.</td></tr><tr title="Версия 8.3.10" class="compat tag_4 tag_1"><td><a name="f004dee5-b6ee-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 4); return false;">Collaboration system</a>.<br></td><td>Implemented the "collaboration system" feature that supports interaction between the server, client applications, and users of a single infobase. The collaboration system simplifies automation of enterprise business processes and provides an easy way to establish work-related communication. 1C:Enterprise application uses can exchange text messages and call each other (audio calls with optional video feed). Text conversations can be related to specific infobase objects (context conversations) or not related to any object (noncontext conversations). Access to conversations is allowed or denied based on the object access rights.<p>Implemented <span class="interface">Collaboration system management</span> standard function.</p><p>Implemented notifications about new messages.</p><p>Implemented conversation management using 1C:Enterprise script tools. Implemented <span class="term">CollaborationSystem </span>global context property. For <span class="term">ManagedForm </span>object, implemented <span class="term">ConversationsRepresentation </span>property. This property is not available in 8.3.9 compatibility mode. Implemented <span class="term">CollaborationS</span><span class="term">ystemInfoBaseRegistration</span> access right.</p><p>The web client supports the collaboration system if it runs in one of the following browsers: Google Chrome, Mozilla Firefox, Safari, Microsoft Edge, or Microsoft Internet Eхplorer version 10.0 or later.</p><p>All of the messages are stored on the collaboration system server. To start using the collaboration system, you have to register your infobase on the collaboration system server. Initially the server is available as the <span class="interface">1cDialog.com</span> service hosted by 1C Company. Note that in order to use the collaboration system you have to open Internet access to <span class="interface">wss://1cdialog.com</span>. </p><p>A distribution kit for a local collaboration system server will be available in a future release.</p><p>Therefore, you will have a choice between using <span class="interface">1cDialog.com</span> service and running a local server.</p><p>Using calls is limited during the beta testing period. Call usage instructions will be available separately.</p><p>This feature currently has beta status. The service access terms will be available separately. The email message with the registration code sent from <span class="interface">1cDialog.com </span>when you request registration in the service will include instructions for enabling video calls.</p></td><td>This feature was not provided.</td><td>The new feature provides 1C:Enterprise application users with communication options that are tightly integrated into the application interface and business logic.</td></tr><tr title="Версия 8.3.10" class="tag_27"><td><a name="3e23e307-b700-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>Implemented partial dump of the configuration being edited to XML files. During partial dump, only objects that were modified since the previous dump are dumped. The file <span class="interface">ConfigDumpInfo.xml</span> containing information about all dumped configuration objects is created. This file also contains internal versions of all dumped objects. An object is not dumped during a partial dump if its version numbers in Designer and in file <span class="interface">ConfigDumpInfo.xml</span> are identical.
Moreover, a file containing information about the differences between the current and the previous dump can be generated.
When restoring data from XML files, users can specify that the file containing information about dumped configuration objects must be updated. In this case, information matching the configuration state after it is restored is saved to this file.
For Designer batch mode command-line option /DumpConfigToFiles, implemented parameters <span class="term">update</span>, <span class="term">force</span>, <span class="term">getChanges</span>, <span class="term">configDumpInfoForChanges</span>, and <span class="term">listFile</span>.
For Designer batch mode command-line option /LoadConfigFromFiles, implemented parameter <span class="term">updateConfigDumpInfo</span>.</td><td>Partial dump of configurations to XML files was not supported. Only full configuration dump was implemented.</td><td>Dumping configurations to XML files is now faster. especially dumping very large configurations with minor changes.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="798b5aea-bbbf-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Implemented management of availability of dynamic list fields (including subordinate fields) for use in groupings, filters, and order settings. Implemented methods <span class="term">Set</span><span class="term">RestrictionsForUseInGroup</span><span class="term">()</span>, <span class="term">Set</span><span class="term">RestrictionsForUseInOrder()</span>, <span class="term">Set</span><span class="term">Restrictions</span><span class="term">ForUse</span><span class="term">InFilter()</span>, <span class="term">Get</span><span class="term">Restrictions</span><span class="term">ForUse</span><span class="term">InGroup</span><span class="term">()</span>, <span class="term">Get</span><span class="term">Restrictions</span><span class="term">ForUse</span><span class="term">InOrder()</span>, and <span class="term">Get</span><span class="term">Restrictions</span><span class="term">ForUse</span><span class="term">InFilter()</span>.</td><td>These features were not provided.</td><td>Now developers can explicitly prohibit groupings, ordering, and filtering for fields not intended for these operations.</td></tr><tr title="Версия 8.3.10" class="tag_99 tag_27"><td><a name="0fce0058-c20e-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 99); return false;">Window-based interface</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>Implemented visibility management for managed form title. Implemented property <span class="term">ManagedForm.Show</span><span class="term">Title</span>.
Implemented visibility management for form closing button. Implemented property <span class="term">ManagedForm.Sho</span><span class="term">w</span><span class="term">Close</span><span class="term">Button</span>.
Implemented selection of main application window display mode.<ul><li>Normal. Default display mode for main application window.</li><li>Workstation. Many items on the system commands area are hidden; all panes in the main application window are hidden; navigation buttons on the home page (including the home page label) are hidden; some of the keyboard shortcuts are disabled.</li><li>Full-screen workstation. Same as Workstation mode but the application window is displayed in full-screen mode.</li><li>Kiosk. Same as Full-screen workstation mode but the <span class="interface">About </span>button and the hyperlink with user name located in the system commands area are hidden.</li></ul><p>Implemented global context property <span class="term">ClientApplication</span> that provides access to client application settings (such as getting and changing the client application window title). For metadata object that describes the configuration, implemented property <span class="term">MainClientApplicationWindowMode</span>.</p><p>Changed version number of format used for dumping configurations to files.</p><p>The following global context methods are now deprecated. It is recommended that you do not use any of these: <span class="term">SetShort</span><span class="term">ApplicationCaption</span><span class="term">()</span>, <span class="term">GetShort</span><span class="term">ApplicationCaption</span><span class="term">()</span>, <span class="term">SetClientApplicationCaption</span><span class="term">()</span>, <span class="term">GetClientApplicationCaption</span><span class="term">()</span>, <span class="term">ClientApplicationBaseFontCurrentVariant</span><span class="term">()</span>, and <span class="term">ClientApplicationInterfaceCurrentVariant()</span>.
The above features are available in <span class="interface">Taxi </span>interface.</p></td><td>These features were not provided.</td><td>Expanded capabilities of client application appearance management. Now a specific interface can be enabled (cashier's interface, self-service kiosk, and more).</td></tr><tr title="Версия 8.3.10" class="tag_38 tag_58"><td><a name="77d4dd8c-c2a6-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>Implemented a flag specifying whether a common attribute used as a separator can separate configuration extensions. For <span class="term">CommonAttribute </span>configuration object, implemented property <span class="term">ConfigurationExtensionsSeparation</span>.
It is recommended that you disable extension separation for separators in <span class="interface">Independent and shared </span>mode.</td><td>Any configuration separators could be used to separate configuration extensions. Disabling extension separation was not possible if data separation was enabled at infobase level.</td><td>Now developers have control over separation of configuration extensions to be used in the infobase. For example, a configuration developer can specify that none of the separators available in the application can be used to separate configuration extensions.</td></tr><tr title="Версия 8.3.10" class="tag_14"><td><a name="02c937ec-fdb5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>For the thin and thick client applications that directly connect to a 1C:Enterprise server, the disconnection monitoring mechanism is implemented. If a server connection issue is detected, the client application automatically attempts to reestablish the connection and repeat the server call. If the connection cannot be established, the application is shut down.<p>The following timeouts are applied:</p><ul><li>Thin client: ping every 3 seconds, wait for connection for 15 seconds.</li><li>Thick client: ping every 12 seconds, wait for connection for 60 seconds.</li></ul><p>The timeout values cannot be changed.</p></td><td>If any server connection issues occurred in the thin or thick client application that was directly connected to a 1C:Enterprise server, the client application might stop responding for a long period (several minutes). That period was defined by TCP stack settings in the operating system.</td><td>Improved reliability of client applications that directly connect to a 1C:Enterprise server. Reduced chance of situations when an application stops responding.</td></tr><tr title="Версия 8.3.10" class="tag_19 tag_29"><td><a name="57124091-2e50-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of PostgreSQL version 9.6 is implemented.</td><td>This PostgreSQL version was not supported.</td><td>Extended list of supported PostgreSQL versions.</td></tr><tr title="Версия 8.3.10" class="tag_19 tag_29"><td><a name="4d3b595d-7144-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of Postgres Pro Enterprise version 9.6 is implemented (only in managed lock management mode).</td><td>Postgres Pro Enterprise was not supported.</td><td>Extended list of supported DBMS versions.</td></tr><tr title="Версия 8.3.10" class="tag_29 tag_28"><td><a name="ec514d41-f5e5-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Ended support of Mozilla Firefox versions 51 and earlier.</td><td>Mozilla Firefox versions 51 and earlier were supported.</td><td>Ended support for legacy Mozilla Firefox versions.</td></tr></table><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="ce205a20-37b8-11e6-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.10" class="tag_28 tag_26"><td><a name="7f59ccf2-8ad4-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Implemented automated marking of blank fields when entering data into spreadsheet documents in the web client.</td><td>Automated marking of blank fields was not performed when entering data into spreadsheet documents in the web client.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="a21f6270-8fb4-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Implemented changes to calculation of page tab size and the appearance of page tabs in vertical mode.
<p>Implemented scaling of pictures in page tabs when changing DPI (both for thin client and thick client). This change is not implemented in 8.3.9 compatibility mode.</p><p>Implemented slight size and position changes for several types of managed form items.</p><p>Changed appearance of slider (both in <span class="interface">Taxi </span>interface and in the web client with <span class="interface">Version 8.2</span> interface). The slider appearance in the web client differs from its appearance in the thick and thin clients.</p><p>The size of the colored picture used for input fields that display data of <span class="term">Color </span>type differs between the web client and the thick/thin clients.</p><p>Changed appearance of system forms (in <span class="interface">Taxi </span>interface for both thick and thin clients) for better conformity with general visual interface style.</p><p>Increased hit boxes for icons that collapse and expand tree nodes in tables (in <span class="interface">Taxi </span>interface).</p><p>Improved appearance of controls for non-standard DPI values.
Modified size calculation for slider fields in forms.</p></td><td>The interface appearance was different. Pictures in page tabs were not resized when changing DPI (both for thin client and thick client).</td><td>Improved appearance of client applications.</td></tr><tr title="Версия 8.3.10" class="tag_115"><td><a name="986c5f0f-8fbb-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Changed appearance of form navigation panel in <span class="interface">Taxi </span>interface. In Russian localization, the name of panel item <span class="interface">Main </span>is now slightly changed.
All commands are displayed in the form navigation panel. Full names are displayed for all of the panel commands. If a command does not fit the form actions panel, the command is displayed in the <span class="interface">More </span>menu.</td><td>Appearance of form navigation panel was different. In Russian localization, the name of panel item <span class="interface">Main </span>was slightly different.
The following rule was in force when displaying commands: if the <span class="interface">Important </span>group contained more than two commands, only two commands were displayed on the navigation panel. Commands that did not fit the form navigation panel were available through the <span class="interface">More </span>menu.
Long names were shortened and marked with ellipses (...) both in the thick and thin clients.</td><td>Application UI was improved.</td></tr><tr title="Версия 8.3.10" class="tag_96"><td><a name="4d47c6f0-95f2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The opened items panel was redesigned in <span class="interface">Taxi </span>interface:<ul><li>The width of each panel item now depends on the window title.</li><li>If the panel is horizontal, one line is used to display the title; if the panel is vertical, an unlimited number of lines can be used.</li><li>If the panel is horizontal, the control item used to access the full list of open windows is located in the right section of the panel.</li><li>If the panel is vertical, a scroll bar might be displayed. In this case, the panel and the work area of the main window can be scrolled separately.</li><li>Implemented closing windows by clicking the wheel button on a corresponding item on the opened items panel.</li><li>Implemented multiple window closing methods in the context menu of a panel item.</li><li>Implemented dragging windows within the panel to change their order.</li><li>If the opened items panel is displayed, the home page button is hidden from the work area of the main window.</li></ul></td><td>Appearance and functionality of the opened items panel (in <span class="interface">Taxi </span>interface) were different:<ul><li>The width of each panel item was fixed regardless of the item content.</li><li>If the panel was horizontal, one or two lines were used to display the item title.</li><li>Windows could not be closed by clicking the wheel button on a corresponding item on the opened items panel.</li><li>The window order on the opened items panel could not be changed interactively.</li><li>The home page button was always displayed in the work area of the main window.</li></ul></td><td>It is now easier to use the opened items panel in <span class="interface">Taxi </span>interface.</td></tr><tr title="Версия 8.3.10" class="tag_26 tag_28"><td><a name="4033343f-96b2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>All border types are now displayed in spreadsheet documents opened in the web client. Appearance of border lines of spreadsheet documents opened in the web client depends on the browser and may differ from appearance of border lines of spreadsheet documents opened in the thick or thin client.</td><td>Only border lines of these types were displayed for spreadsheet document cells: <span class="term">Solid</span>, <span class="term">Dotted</span>, and <span class="term">None</span>. All other line types were replaced by the above types as follows:<ul><li>Line type <span class="term">Double </span>was replaced by <span class="term">Solid</span>.</li><li>Line types <span class="term">Thin</span><span class="term">Dashed</span>, <span class="term">ThickDashed</span>, and <span class="term">LargeDashed</span><span class="term"> </span>were replaced by type <span class="term">Dotted</span>.</li></ul></td><td>Eliminated unexpected system behavior. Border lines of spreadsheet documents opened in the web client now more closely conform to border lines of spreadsheet documents opened in the thick or thin client.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="7eb15c22-96b7-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If the freeze area of a managed form table exceeds the visible area of the table, column freeze is canceled automatically.<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>If the freeze area exceeded the size of the whole table, the table could not be scrolled horizontally.</td><td>It is now easier to work with tables in small forms.</td></tr><tr title="Версия 8.3.10" class="compat tag_25 tag_1"><td><a name="95900af2-96ce-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the "Main" data composition appearance template used in <span class="interface">Taxi </span>interface, text color is set to <span class="term">Auto </span>for all template areas except the report header.<p>This change is not implemented in 8.3.9 compatibility mode
</p></td><td>In the "Main" data composition appearance template used in <span class="interface">Taxi </span>interface, gray text color was used for some of the template areas (except the report header).</td><td>Now optimal text color is chosen whenever a report is displayed or printed, improving readability.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="f41478ba-99f2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Implemented sorting for dynamic lists by clicking any column header in the table displaying dynamic list data, provided that the query text contains aggregate functions and<span class="term"> </span><span class="term">GROUP BY </span>expressions.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>Dynamic list sorting by clicking any column header in the table displaying dynamic list data was not supported, regardless of whether the query text contained aggregate functions or <span class="term">GROUP BY </span>expressions.</td><td>Behavior of tables displaying dynamic list data is now more intuitive and predictable.</td></tr><tr title="Версия 8.3.10" class="tag_115"><td><a name="2b999c49-b2f1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the thin and thick clients, the wheel button scrolls a form item where mouse cursor is currently located (provided that such form item is scrollable). The form item is scrolled regardless of whether it has received input focus.
After the form item is fully scrolled, the parent form item starts scrolling (provided that it is scrollable).</td><td>In the thin and thick clients, the wheel button only scrolled active form items.
In the web client, the wheel button scrolled both active and nonactive form items.</td><td>Managed form navigation is now more user-friendly.
Unified scrolling behavior between the web client, the thin client, and the thick client.</td></tr><tr title="Версия 8.3.10" class="tag_14 tag_64"><td><a name="8ce323d1-b2f3-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>All standard pictures used by client applications are implemented as sets of pictures optimized for a variety of DPI and display scale values.
Standard pictures are redesigned.</td><td>Standard pictures used by client applications were not optimized for current DPI and display scale values. Therefore, applying non-standard DPI could result in blurry standard pictures. </td><td>Optimized appearance of client interface for non-standard DPI and display scale values.</td></tr><tr title="Версия 8.3.10" class="tag_70"><td><a name="09f80955-0d76-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>If any issue occurs during the thin client update over HTTP, you have the option to get the name of the file that cannot be updated. This option is provided in the following scenarios:<ul><li>The archive is corrupted or has invalid structure (the archive file name is provided).</li><li>One of the distribution kit files has invalid digital signature (the name of this file is provided).</li></ul></td><td>If any issue occurred during the thin client update over HTTP, the option to get the name of the file that cannot be updated was not available. In particular, there was no way to get the file name of a corrupted archive of the name of the file that had invalid digital signature.<p>
</p></td><td>Improved issue diagnostics during the thin client update over HTTP.</td></tr></table><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="ce205a21-37b8-11e6-a3f7-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.10" class="tag_6"><td><a name="c511b66f-897f-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td> Improved server cluster scalability for the following cases:<ul><li>Servers run on processors with a large number of cores.</li><li>A large number of users is served.</li><li>Internal data exchange between the client and the server is compressed.</li></ul><p>Reduced amount of RAM used by 1C:Enterprise server to run applications that utilize batch queries.</p></td><td>Poor server cluster scalability was observed in the following cases:<ul><li>Servers run on processors with a large number of cores.</li><li>A large number of users is served.</li><li>Internal data exchange between the client and the server is compressed.</li></ul><p>1C:Enterprise server used a significant amount of RAM to run applications that utilized batch queries.</p></td><td>Improved 1C:Enterprise server cluster scalability.</td></tr><tr title="Версия 8.3.10" class="tag_130"><td><a name="fc4134f1-8ad2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 130); return false;">Встроенный язык</a>.<br></td><td>Faster 1C:Enterprise script execution by 1C:Enterprise server.</td><td>The performance of 1C:Enterprise script execution by 1C:Enterprise server was insufficient.</td><td>Optimized 1C:Enterprise script execution by 1C:Enterprise server.</td></tr><tr title="Версия 8.3.10" class="tag_25"><td><a name="79849579-8ae5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Faster initialization of data composition settings composer by source of available data composition settings when using schemas with a large number of calculated fields.</td><td>The performance of initialization of data composition settings composer by source of available data composition settings when using schemas with a large number of calculated fields was insufficient.</td><td>Improved performance of data composition system initialization in several scenarios.</td></tr><tr title="Версия 8.3.10" class="tag_6"><td><a name="6074b487-8b17-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Reduced amount of RAM used by 1C:Enterprise server to run applications that utilize batch queries.</td><td>Significant amount of RAM was used by 1C:Enterprise server to run applications that utilize batch queries.</td><td>Optimized amount of RAM used by 1C:Enterprise server to run batch queries.</td></tr><tr title="Версия 8.3.10" class="tag_67"><td><a name="4ceda90d-8c6f-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>Optimized updating of local cache of configuration storage when putting objects into storage and getting objects from storage.</td><td>The performance of putting objects into configuration storage and getting objects from storage was insufficient.</td><td>Putting objects into configuration storage and getting objects from storage is now faster.</td></tr><tr title="Версия 8.3.10" class="tag_20"><td><a name="7cbfbe7e-8c71-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Implemented retention of module search index between Designer sessions. Reduced time required for initial generation of module search index. Significantly reduced time required for module search index generation during all subsequent Designer sessions.
Running Designer with command-line option<span class="term"> /ClearCache</span> clears the module search index.</td><td>Module search index was not retained between Designer sessions. Index generation required significant time.</td><td>It is now easier to work with large configurations.</td></tr><tr title="Версия 8.3.10" class="tag_69"><td><a name="bca7b6c9-8c76-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>When searching for strings in a value table using the<span class="term"> FindRows</span><span class="term">()</span> method, the index is only analyzed for column content matches between the search parameters and the index. The relative order of columns in the search parameters or in the index is ignored during the search.</td><td>When searching for strings in a value table using the <span class="term">FindRows()</span> method, the index was only used if the relative order of columns in the search parameters matched the index column order.</td><td>Using the index to search value tables by multiple columns is now faster.</td></tr><tr title="Версия 8.3.10" class="tag_21"><td><a name="1e8a5d6f-8fc2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Optimized full-text search index generation and update.</td><td>The performance of initial generation and updates of full-text search index was insufficient.</td><td>Updating the full-text search index is now faster.</td></tr><tr title="Версия 8.3.10" class="tag_19 tag_45"><td><a name="005af77b-953b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Improved processing speed of queries containing keyword <span class="term">DISTINCT </span>that get a large number of records (in file infobases).</td><td>Processing speed of queries containing keyword <span class="term">DISTINCT </span>that get a large number of records (in file infobases) was insufficient.</td><td>Getting large lists of unique records from file infobases is now faster.</td></tr><tr title="Версия 8.3.10" class="tag_19 tag_45"><td><a name="c91f9c23-953b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Faster deletion of large record sets from file infobases.
Faster recalculation of totals for tables with a large number of records in file infobases.</td><td>The following operations in file infobases were insufficiently fast:<ul><li>Deleting large record sets</li><li>Recalculating totals for tables with a large number of records</li></ul></td><td>File infobases now work faster in some scenarios.</td></tr><tr title="Версия 8.3.10" class="tag_43"><td><a name="f2fff22a-95d0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Improved performance when getting data displayed as dynamic list with conditional formatting.<p>
</p></td><td>The performance of getting data displayed as dynamic list with conditional formatting was insufficientl.</td><td>The performance of dynamic lists with conditional formatting is now improved.</td></tr><tr title="Версия 8.3.10" class="tag_43"><td><a name="3c4eb47d-96d5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Faster opening of forms containing dynamic lists with complex queries.</td><td>The performance of opening forms containing dynamic lists with complex queries was insufficient.</td><td>Forms containing dynamic lists with complex queries now open faster.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="c4ed575d-977c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>For dynamic lists, implemented the option to enable or disable getting presentations for values of reference types that are not displayed in the form or are associated with invisible form items. Presentations of key field values for dynamic lists in selection mode are obtained regardless.
Implemented dynamic list property <span class="term">GetInvisibleField</span><span class="term">Presentations</span>.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>In dynamic lists, presentations were obtained for all reference type values to be sent to client side.</td><td>Dynamic lists can now be displayed faster in some cases.</td></tr><tr title="Версия 8.3.10" class="tag_25"><td><a name="7566127a-99fc-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Optimized RAM usage when composing data composition templates with large queries in data composition schema.</td><td>RAM usage when composing data composition templates with large queries in data composition schema was sub-optimal.</td><td>Composing data composition templates with large queries in data composition schema now requires less RAM.</td></tr><tr title="Версия 8.3.10" class="tag_93"><td><a name="fea1c121-b706-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br></td><td>Slightly improved thin client startup time in file infobases when working with large configurations.</td><td>Startup time of the thin client in file infobases when working with large configurations was insufficient.</td><td>Startup time of the thin client in file infobases when working with large configurations is now improved.</td></tr><tr title="Версия 8.3.10" class="tag_67"><td><a name="1b04e7ec-b252-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>Optimized object lock and release operations in configuration repositories.
Changed internal format of locked object data storage for infobases connected to repositories.
The data storage format is changed after the data storage optimization operation is completed using the <span class="interface">Local repository </span><span class="interface">data usage settings</span> dialog box. This optimization is only available if the configuration was bound to a configuration repository in an earlier platform version.
To use the optimized infobase in an earlier platform version, rebind the infobase to the configuration repository in an earlier platform version.
</td><td>The performance of object lock and release operations in configuration repositories was insufficient.</td><td>Working with configuration repositories that store large configurations is now faster.</td></tr><tr title="Версия 8.3.10" class="tag_14"><td><a name="ba230b39-be14-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Improved startup time of client applications after dynamic update.</td><td>Client applications required longer time to start after dynamic update.</td><td>Improved startup time of client applications after dynamic update.</td></tr><tr title="Версия 8.3.10" class="tag_65"><td><a name="33012186-e3ac-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>Every time a method of a web or HTTP service is called, the compiled service module is cashed.</td><td>Every time a method of a web or HTTP service was called, the service module was compiled.</td><td>Improved system performace in scenarios that include a large number of web or HTTP services calls.</td></tr><tr title="Версия 8.3.10" class="tag_82 tag_19"><td><a name="248bd9ca-fd97-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Improved performance of the following accounting register record set operations for infobases running in file mode or in client/server mode with PostgreSQL:<ul><li>Write a record set</li><li>Read a record set</li><li>Open a record set form</li></ul></td><td>The performance of the following accounting register record set operations was insufficient in infobases running in file mode or in client/server mode with PostgreSQL:<ul><li>Write a record set</li><li>Read a record set</li><li>Open a record set form</li></ul></td><td>Optimized accounting register operations for some DBMS.</td></tr><tr title="Версия 8.3.10" class="tag_19"><td><a name="d1d80f63-93bc-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Optimized query plan generation for PostgreSQL version 9.6.3. This improves the performance of complex queries that use data access restriction templates.<p>Optimization is available for PostgreSQL versions 9.6.3-2.1C and later.</p></td><td>In PostgreSQL, performance of complex queries that used data access restriction templates was insufficient, in some cases applications might stop responding during query execution.</td><td>Improved performance of PostgreSQL operations initiated from 1C:Enterprise.</td></tr></table><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="ce205a22-37b8-11e6-a3f7-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.10" class="tag_120 tag_6"><td><a name="f71102eb-8ad1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Changed approach to storing background and scheduled job execution history. In client/server mode, the stored history data was broken down by infobase. The following history data is stored for each infobase:<ul><li>Up to 1 000 1C:Enterprise script-based background jobs</li><li>Up to 1 0000 scheduled jobs</li><li>Up to 1 000 system background jobs (i.e. background jobs created by system)</li></ul><p>For each job (background, scheduled, or system background), information about at least 3 latest job executions is saved, if possible. The three executions limit can be reduced if over 1 000 records are created for any given job type.</p></td><td>In file mode, the stored job history data was broken down by infobase. In client/server mode, the stored job history data was broken down by server cluster. In both cases, data was stored on the total of 1 000 jobs, regardless of job type (background, scheduled, or system background).</td><td>Improved diagnostics of background and scheduled job execution when a large amount of jobs is present in the system. Reduced risk of information about rarely used 1C:Enterprise script-based background jobs being superseded by information about a large amount of scheduled jobs or system background jobs.</td></tr><tr title="Версия 8.3.10" class="tag_64 tag_63"><td><a name="25930418-8c7c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>For objects <span class="term">Chart</span>, <span class="term">GanttChart</span>, <span class="term">Pivot</span><span class="term">Chart</span>, and <span class="term">Dendrogram</span>, the default value of <span class="term">Font</span><span class="term"> </span>property of subordinate objects describing specific chart areas is set to <span class="term">Auto</span>, meaning <span class="interface">Normal text font</span>.
When the web client is running on Windows, the procedures of displaying charts in the web client, exporting spreadsheet documents containing charts to HTML5 format, and exporting charts to SVG format include checks for OS-based substitutions of chart fonts. If the OS substitutes chart fonts, the resulting files include the names of the fonts that are actually used.
When exporting spreadsheet documents to HTML format and displaying spreadsheet documents in the web client, system fonts are not substituted by Arial; instead, the names of the fonts that are actually used are determined.
</td><td>For objects <span class="term">Chart</span>, <span class="term">GanttChart</span>, <span class="term">Pivot</span><span class="term">Chart</span>, and <span class="term">Dendrogram</span>, the default value of <span class="term">Font </span>property of subordinate objects describing specific chart areas was set to <span class="interface">Text font</span>.
When the web client was running on Windows, the procedures of displaying charts in the web client, exporting spreadsheet documents containing charts to HTML5 format, and exporting charts to SVG format included exporting fonts "as is", without attempting to determine which fonts were actually used.
When exporting spreadsheet documents to HTML format and displaying spreadsheet documents in the web client, system fonts were substituted by Arial.</td><td>Unified fonts used to display charts across client applications, including the web client running in a variety of web browsers. Unified fonts used to display spreadsheet documents across client applications.
When exporting spreadsheet documents containing charts, original fonts used to display the charts are retained.</td></tr><tr title="Версия 8.3.10" class="compat tag_49 tag_1"><td><a name="8c35d76b-8ef0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 49); return false;">Binary data</a>.<br></td><td>Binary data management capabilities are now expanded. Implemented bilateral conversion between binary data and the following data types: binary data array, string, binary data buffer, Base64 string, hexadecimal string, and binary data as string.<p>Implemented binary data usage in methods and constructors that previously supported files only.
Implemented bitwise operations (AND, OR, NOT, XOR, NAND, and inversion) for binary data stored in a binary data buffer.
Implemented binary data exchange with add-ins for add-in developers (also available in the web client).
Implemented getting bulk permissions when working with binary data in the web client.
</p><p>Implemented direct copying of binary data from <span class="term">DataReader </span>object to <span class="term">DataWriter </span>object.</p><p>Implemented global context methods <span class="term">Concat</span><span class="term">BinaryData()</span>, <span class="term">Split</span><span class="term">BinaryData()</span>, <span class="term">GetBinaryDataFromString()</span>, <span class="term">GetBinaryDataBufferFromString()</span>, <span class="term">GetStringFromBinaryData()</span>, <span class="term">GetStringFromBinaryDataBuffer()</span>, <span class="term">GetBinaryDataFromBase64String()</span>, <span class="term">GetBinaryDataBufferFromBase64String()</span>, <span class="term">GetBase64StringFromBinaryData()</span>, <span class="term">GetBase64BinaryDataFromBinaryData()</span>, <span class="term">GetBinaryDataFromBase64BinaryData()</span>, <span class="term">GetBase64BinaryDataB</span><span class="term">ufferFromBinaryDataBuffer()</span>, <span class="term">GetBinaryDataB</span><span class="term">ufferFromBase64BinaryDataBuffer()</span>, <span class="term">GetBinaryDataFromHexString()</span>, <span class="term">GetBinaryDataBufferFromHexString()</span>, <span class="term">GetHexStringFromBinaryData()</span>, <span class="term">GetHexStringFromBinaryDataBuffer()</span>, <span class="term">GetHexBinaryDataFromBinaryData()</span>, <span class="term">GetBinaryDataFromHexBinaryData()</span>, <span class="term">GetHexBinaryDataBufferFromBinaryDataBuffer()</span>, <span class="term">GetBinaryDataBufferFromHexBinaryDataBuffer()</span>, <span class="term">GetBinaryDataFromBinaryDataBuffer()</span>, <span class="term">GetBinaryDataBufferFromBinaryData()</span>, <span class="term">NumberFromHexString()</span>, and <span class="term">NumberFromBinaryString()</span>.
Implemented the option to use binary data streams:</p><ul><li>In <span class="term">TextReader</span>, <span class="term">TextWriter</span>, <span class="term">ZipFileReader</span>, and <span class="term">ZipFileWriter </span>object constructors</li><li>In<span class="term"> Open()</span> method of <span class="term">TextReader</span>, <span class="term">TextWriter</span>, <span class="term">Zip</span><span class="term">FileWriter</span>, and <span class="term">Zip</span><span class="term">FileReader </span>objects</li><li>In <span class="term">Write()</span> method of <span class="term">TextDocument</span>, <span class="term">SpreadsheetDocument</span>, <span class="term">FormattedDocument</span>, <span class="term">GeographicalSchema</span>, and <span class="term">Picture </span>objects</li><li>In <span class="term">Put()</span> method of <span class="term">FTPConnection </span>object</li><li>In <span class="term">Read() </span>method of <span class="term">TextDocument</span>, <span class="term">SpreadsheetDocument</span>, and <span class="term">GeographicalSchema</span> objects</li><li>In the following methods of <span class="term">CryptoManager</span> object:<span class="term"> Encrypt()</span>, <span class="term">Decrypt()</span>, <span class="term">Sign()</span>, and <span class="term">VerifySignature()</span></li><li>In method<span class="term"> Crypto</span><span class="term">Certificate.Unload</span><span class="term">()</span></li><li>In method <span class="term">DataHashing.Appen</span><span class="term">d()</span></li><li>In method <span class="term">FTPConnection.Get()</span></li></ul><p>Implemented <span class="term">OpenStream() </span>method for objects <span class="term">HTMLReader</span>, <span class="term">HTMLWriter</span>, <span class="term">JSONReader</span>, <span class="term">JSONWriter</span>, <span class="term">FastInfos</span><span class="term">etReader</span>, <span class="term">FastInfos</span><span class="term">etWriter</span>, <span class="term">XMLReader</span>, and <span class="term">XMLWriter</span>.</p><p>Implemented <span class="term">GetBodyAsStream()</span> method for objects <span class="term">HTTPRequest</span>, <span class="term">HTTPResponse</span>, <span class="term">HTTPServiceRequest</span>, and <span class="term">HTTPServiceResponse</span>.
Implemented method <span class="term">ConversionToCanonicalXML.CanonicalizeToStream()</span>.</p><p>For <span class="term">XSLTransform</span> object, implemented methods <span class="term">Load</span><span class="term">XSLStyleSheet()</span> and <span class="term">Transform</span><span class="term">()</span>.</p><p>Implemented method <span class="term">Zip</span><span class="term">FileWriter.GetBinaryData()</span>.</p><p>For <span class="term">BinaryDataBuffer </span>object, implemented methods<span class="term"> WriteBitwiseAnd</span><span class="term">()</span>, <span class="term">WriteBitwiseOr</span><span class="term">()</span>, <span class="term">WriteBitwiseXor</span><span class="term">()</span>, <span class="term">WriteBitwise</span><span class="term">And</span><span class="term">Not(</span><span class="term">)</span>, and <span class="term">Invert()</span>.</p><p>For <span class="term">DataReader </span>object, implemented methods <span class="term">CopyTo()</span> and <span class="term">Begin</span><span class="term">Copy</span><span class="term">To()</span>.</p><p>For methods <span class="term">CopyTo()</span> and <span class="term">Begin</span><span class="term">Copy</span><span class="term">To()</span> of <span class="term">Stream </span>object, changed the purpose of the second method parameter and the return value: the number of bytes to be copied is passed as the second parameter, and the return value is the actual number of copied bytes. The buffer size is defined automatically. The method descriptions are now uniform with the similar methods of <span class="term">DataReader</span><span class="term"> </span>object. This change is not implemented in 8.3.9 compatibility mode.</p></td><td>For methods <span class="term">CopyTo() </span>and <span class="term">Begin</span><span class="term">CopyingTo() </span>of <span class="term">Stream </span>object, the size of buffer used for copying was passed as the second parameter, and return values were not available.</td><td>It is now easier to use binary data for a range of applied tasks.</td></tr><tr title="Версия 8.3.10" class="tag_39"><td><a name="36c3473a-8fc0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>In the event log (opened from a file or otherwise), each data presentation string recorded to the log when an event was registered is only displayed to users that have the right to view this data or <span class="term">Administration </span>right. If a user does not have <span class="term">Administration </span>right and the data presentation is probably unavailable to them, the saved data presentation is hidden from this user.
If the <span class="term">Data </span>field of an event log record contains a reference and a user probably has no rights to view the related data object, the <span class="interface">Data presentation</span> field is blank.</td><td>Access rights of the current user were not checked when displaying presentation of event log data. </td><td>Users with restricted rights no longer can access data objects that are unavailable to them by accessing presentations of unavailable objects that were saved earlier.</td></tr><tr title="Версия 8.3.10" class="tag_20"><td><a name="4c7cec0c-905c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the call stack window of the debugger, implemented correct display of method parameters containing extremely long text strings or multiline strings. In this case, the presentation is based on the initial 20 characters of the parameter string appended with ellipsis (...), continued with other parameters and the closing bracket of the method.</td><td>In the call stack window of the debugger, method parameters containing extremely long text strings or multiline strings were displayed incorrectly: text presentations of the following parameters (if any) and the closing bracket of the method were missing.</td><td>The accuracy of data in the call stack window is improved.</td></tr><tr title="Версия 8.3.10" class="compat tag_26 tag_1"><td><a name="2bc530c0-95ed-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats, only right-aligned cell text is converted into numeric format. The content of cells without right alignment is saved as text.
This change is not implemented in 8.3.9 compatibility mode.</td><td>When exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats, cell text was converted into numeric format regardless of text alignment.</td><td>Exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats is improved.</td></tr><tr title="Версия 8.3.10" class="compat tag_77 tag_1"><td><a name="1450ba02-960c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>Implemented settings for default page size during printing (including printing to PDF file). This feature is available both for the web client and for documents generated by scheduled jobs. Implemented the <span class="term">PrintSettings </span>object.
In the web client parameters dialog box, implemented <span class="interface">Default page size</span> settings item.
This change is not implemented in 8.3.9 compatibility mode.</td><td>A4 format was used as the default paper size.
In the web client parameters dialog box, <span class="interface">Default page size </span>settings item was not available.</td><td>When printing a document (or saving it to a PDF file) in the web client, the paper size set for the current client application is used for pagination purposes. Thus, the resulting document better satisfies user expectations.
This functionality is now also available for the documents generated by scheduled jobs.</td></tr><tr title="Версия 8.3.10" class="tag_25"><td><a name="2f08ceed-96b8-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When loading data composition schema and data composition settings in interactive mode, style colors and fonts not available in the current configuration are automatically removed from the schema and settings.</td><td>When loading data composition schema and data composition settings in interactive mode, style colors and fonts not available in the current configuration caused XDTO data conversion errors.<p>
</p></td><td>Now data composition schema and data composition settings containing style colors and fonts not available in the current configuration can be used.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="1c5012be-96d1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Content of <span class="interface">System fields</span> folder cannot be used as selection fields in dynamic lists.
If a dynamic list has no main table specified or the specified main table is missing a dynamic list key field, grouping fields cannot be set up for this dynamic list.<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>Content of <span class="interface">System fields </span>folder could be used as selection fields in dynamic lists.
If a dynamic list had no main table specified or the specified main table was missing a dynamic list key field, grouping fields could be set up for this dynamic list, resulting in data retrieval error.</td><td>Eliminated unexpected system behavior. Dynamic lists are more reliable now.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="a88efaf3-96d1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The following properties of <span class="term">DynamicList </span>object are unavailable in the thick client: <span class="term">DynamicDataRead</span>, <span class="term">MainTable</span>, <span class="term">Custom</span><span class="term">Query</span>, and <span class="term">QueryText</span>.
Assigning values to managed form attributes of <span class="term">DynamicList </span>type is not allowed.
Passing attributes of <span class="term">DynamicList </span>type as method parameters or return values in client/server interactions is not allowed.
This change is not implemented in 8.3.9 compatibility mode.</td><td>The following properties of <span class="term">DynamicList </span>object were available in the thick client: <span class="term">DynamicDataRead</span>, <span class="term">MainTable</span>, <span class="term">Custom</span><span class="term">Query</span>, and <span class="term">QueryText</span>. However, changing their values did not affect the dynamic lists in any way.
Assigning values to managed form attributes of <span class="term">DynamicList </span>type was allowed. However, further behavior was not defined.
Passing attributes of <span class="term">DynamicList </span>type as method parameters or return values in client/server interactions was allowed. However, further behavior was not defined.</td><td>Dynamic lists are more reliable now. The listed cases of dynamic list misuse are no longer supported.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_1"><td><a name="f8545631-9773-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Series data (marker) in a chart legend depends on the appearance of the series in the chart (line color, line style, and marker).<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>Series data in chart legend was always represented by a square marker of color matching color of the series in the chart.</td><td>Chart readability is now improved (best results for charts printed in black and white).</td></tr><tr title="Версия 8.3.10" class="compat tag_25 tag_1"><td><a name="86ffe999-9782-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Templates of resources created at intersection with matching predefined templates of grouping titles are initially blank.
This change is not implemented in 8.3.9 compatibility mode.</td><td>Resources were displayed in templates of resources created at intersection with matching predefined templates of grouping titles. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_8 tag_1"><td><a name="9fc6f086-979b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>If a serial number of a certificate starts with a set high bit, a leading zero byte is appended to the serial number.
This change is not implemented in 8.3.8 compatibility mode.</td><td>A leading zero byte was not appended to serial numbers of certificates.</td><td>Defects in encryption management logic are corrected.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="f6e1d1e5-99db-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Implemented disabling auto filling of available fields in dynamic lists. This option is only available for dynamic lists generated using custom queries.
The system behavior is identical to the similar data composition schema option.
Implemented dynamic list property <span class="term">AutoFillAvailableFields</span>.
This change is not implemented in 8.3.7 compatibility mode.</td><td>Auto filling of all available fields was enabled for all dynamic list queries. </td><td>Availability of the list fields can now be changed by the extension of the query language for data composition schema.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_25 tag_1"><td><a name="e7ab83bd-99dc-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Implemented management of series display order in chart legends (also available in the data composition system).
Implemented property <span class="term">Chart.SeriesOrderInLegend</span>.
For<span class="term"> </span><span class="term">ChartType</span> appearance item of <span class="term">DataCompositionAreaTemplateChartAppearance</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, <span class="term">DataCompositionOutputParameterValues</span>, and <span class="term">DataCompositionGroup</span><span class="term">OutputParameterValues </span>objects, implemented parameter <span class="term">SeriesOrderInLegend</span>.
This change is not implemented in 8.3.9 compatibility mode.</td><td>Series display order in chart legends could not be changed.</td><td>Additional chart display features are now implemented.</td></tr><tr title="Версия 8.3.10" class="tag_20"><td><a name="047d6949-99fc-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The user is asked if they want to save their work whenever they attempt to close the query expression editor dialog box (in the query wizard) by pressing Esc or clicking the Close button (X) after making changes to the expression in the editor. </td><td>The user was not asked if they want to save their work whenever they attempted to close the query expression editor dialog box (in the query wizard) by pressing Esc or clicking the Close button (X) after making changes to the expression in the editor. This behavior resulted in loss of user work.</td><td>Eliminated unexpected system behavior.
Reduced risk of loss of user work when editing query expressions.</td></tr><tr title="Версия 8.3.10" class="tag_20"><td><a name="47c7f3fc-afd2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Improved diagnostics and system behavior when an invalid or missing manifest is discovered in a picture archive:<ul><li>Archive validation is performed during the import in interactive mode</li><li>Pictures with invalid or missing manifests are not displayed in Designer</li><li>Accessing the archive from 1C:Enterprise script generates an error more closely related to the actual problem </li></ul></td><td>The system behavior was different when an invalid or missing manifest was discovered in the picture archive:<ul><li>Archive validation was not performed during the import in interactive mode</li><li>Attempts to display the picture in Designer or to call it from 1C:Enterprise script could result in abnormal termination or a vaguely described error</li></ul></td><td>Improved diagnostics and system reliability when accessing picture archives with invalid or missing manifests.
</td></tr><tr title="Версия 8.3.10" class="tag_27"><td><a name="e4dfef79-afd5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>During full restoration of a configuration from files, the following rules apply:<ul><li>Configurations that are not covered by support and not connected to configuration repositories can be restored without any restrictions (as before).</li><li>Configurations that are connected to configuration repositories cannot be restored (the corresponding menu item is disabled).</li><li>Configurations that are covered by support can be restored provided that:</li><ul><li>Editing is allowed.</li><li>All configuration objects can be edited.</li></ul></ul><p>During partial restoration of a configuration from files, the following rules apply:
</p><ul><li>Configurations can only be restored if all objects to be restored are locked in the configuration repository.</li><li>Configurations can be restored if all objects to be restored can be edited (for configurations that are covered by support).</li></ul></td><td>Dumping and restoring configurations from files were executed regardless of whether a configuration is covered by support or connected to a configuration repository.</td><td>Eliminated issues that occurred when attempting to restore a configuration that is covered by support or connected to the configuration repository from files.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="5c0754e4-b0a1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Improved algorithm for searching through search boxes of dynamic lists:<ul><li>Implemented searching for full dates (including both date and time)</li><li>Implemented searching for numbers with integer and fractional parts by entering integer part only</li><li>Better readability of search results</li></ul><p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>Searching through search boxes of dynamic lists was implemented as follows:<ul><li>Searching for full dates (including both date and time) resulted in a separate search for date and a separate search for the string containing time data</li><li>Searching for values similar to numbers with integer and fractional parts resulted in a separate search for the integer part and a separate search for the fractional part, with AND conjunction</li><li>Search results could be displayed inaccurately
</li></ul></td><td>Improved searching using search boxes of dynamic lists.</td></tr><tr title="Версия 8.3.10" class="tag_43"><td><a name="04503a0d-b0bd-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Fields that cannot be used in filters are not available in the advanced search dialog box of dynamic lists (i.e. not displayed in the <span class="interface">Search in </span>field list).
If the current column of the table associated with the dynamic list displays a field that cannot be used in filters, the command that starts the search by current value is not available.</td><td>Fields that could be used in filters were available in the advanced search dialog box of dynamic lists (i.e. displayed in the <span class="interface">Search in</span> field list).
Availability of the command that starts the search by current value was not affected by whether the field displayed in the current column of dynamic list can be used in filters. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="tag_10"><td><a name="e67e4bd0-b0bf-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>During the verification and repair of a file infobase, infobase table records are deleted if their keys become non-unique after the records are modified. At that, a diagnostic message is displayed in the message window.<p>
</p><p>
</p><p>
</p></td><td>During the verification and repair of a file infobase, keys of infobase table records were not checked for uniqueness after the records were modified. This could result in records with non-unique keys occurring in the infobase. To remedy this, it was necessary to run the infobase verification and repair procedure once more.</td><td>Unified behavior of infobase verification and repair procedure between file and client/server infobase modes.</td></tr><tr title="Версия 8.3.10" class="compat tag_69 tag_1"><td><a name="993e2094-b0c3-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Enumerations are present in type selection dialog boxes and type description dialog boxes for all client applications running in managed application mode.
This change is not implemented in 8.3.9 compatibility mode. </td><td>Enumerations were not present in type selection dialog boxes and type description dialog boxes for thick client and thin client applications running in managed application mode.
However, enumerations were present in these dialog boxes for the web client.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_26 tag_1"><td><a name="3cd66311-b18c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When exporting spreadsheet documents to Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) format, the name of XML component of shared strings starts with a lowercase letter: <span class="interface">sharedStrings.xml</span>.
This change is not implemented in 8.3.9 compatibility mode.</td><td>When exporting spreadsheet documents to Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) format, the name of XML component of shared strings started with an uppercase letter: <span class="interface">SharedStrings.xml</span>.</td><td>The platform behavior now conforms to OpenXML standard. Improved compatibility with case-sensitive systems parsing OpenXML files.</td></tr><tr title="Версия 8.3.10" class="tag_115 tag_43"><td><a name="1671dac6-b18d-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Implemented the <span class="interface">Main </span><span class="interface">attribute</span> flag for managed form attribute of <span class="term">DataCompositionSettingsComposer </span>type. In this case, <span class="interface">Managed form extension for settings composer </span>serves as form extension.
The <span class="interface">User-defined </span><span class="interface">settings group</span> form property and <span class="term">OnUpdateUserS</span><span class="term">etting</span><span class="term">SetAt</span><span class="term">Server </span>event handler are now available for the form.</td><td>Managed form property <span class="interface">Main </span><span class="interface">attribute</span> was only set for automatically generated forms of dynamic list settings. Developers were not allowed to create these forms.</td><td>Developers can now create all-purpose data composition settings editing forms.</td></tr><tr title="Версия 8.3.10" class="tag_20"><td><a name="cfb92e49-b2f2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>When comparing and merging modules (without using third-party tools), placement of methods in areas defined by preprocessor instructions (<span class="term">#Region</span>, <span class="term">#If</span>) is taken into account.
Areas defined by preprocessor instructions are isolated as separate entities (together with procedures and functions). For these areas, implemented specifying the merging parameters.</td><td>This feature was not provided.
The preprocessor instructions were processed as comments linked to the procedures they preceded.
Module merging could result in corrupted structure of blocks defined by preprocessor instructions.</td><td>Module merging performed by native Designer tools is now more reliable and user-friendly.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="373783a4-b6e9-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The navigation panel of the item form of an hierarchical catalog or chart of characteristic types contains:<ul><li>Commands used to access subordinate catalogs with item hierarchy or item and folder hierarchy (no changes since the earlier versions)</li><li>Commands used to access information registers whose leading dimension type matches the type of catalog or chart of characteristic types, and whose property <span class="interface">Select folders and items</span> for this dimension is set to <span class="interface">Items </span>or <span class="interface">Folders </span><span class="interface">and items</span></li></ul><p>The navigation panel of the group form of an hierarchical catalog or chart of characteristic types contains:</p><ul><li>Commands used to access subordinate catalogs with folder hierarchy or item and folder hierarchy</li><li>Commands used to access information registers whose leading dimension type matches the type of catalog or chart of characteristic types, and whose property <span class="interface">Select folders and items</span> for this dimension is set to <span class="interface">Items </span>or <span class="interface">Folders </span><span class="interface">and items</span></li></ul><p>
</p><p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>All commands used to access subordinate catalogs were located in the navigation panel of the item form of an hierarchical catalog or chart of characteristic types. The navigation panels of group forms of these configuration objects did not contain any of the commands used to access subordinate catalogs.
All commands used to access information registers were located in the navigation panel of the item form of an hierarchical catalog or chart of characteristic types. The navigation panels of group forms of these configuration objects did not contain any of the commands used to access information registers. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="tag_20 tag_27"><td><a name="d9d45964-b705-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>In the "dump configuration to files" feature, changed the dump format of information about dynamic lists located in managed forms.
It is recommended that you dump all forms containing dynamic lists once more.</td><td>In the "dump configuration to files" feature, the dump format of information about dynamic lists located in managed forms was different.</td><td>In the "dump configuration to files" feature, the format of resulting XML files is improved.</td></tr><tr title="Версия 8.3.10" class="tag_73"><td><a name="71d3fb9c-b707-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>Messages about creation and deletion of options tables for charts of characteristic types, charts of accounts, charts of calculation types, and catalogs are not displayed when updating database configuration.</td><td>Messages about creation and deletion of options tables for charts of characteristic types, charts of accounts, charts of calculation types, and catalogs were displayed when updating database configuration.</td><td>Messages that contain no useful information for the user are no longer displayed when updating database configuration.</td></tr><tr title="Версия 8.3.10" class="tag_63"><td><a name="f11310ef-b709-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>
<p>Expanded set of palettes that can be used to customize chart colors. The palettes can contain either fixed color sets or color sets that vary depending on the quantity of series. Implemented creation of custom color sets for charts. For <span class="term">ChartColorPalette </span>system enumeration, implemented values <span class="term">Auto</span>, <span class="term">Custom</span>, <span class="term">Gradient</span>, <span class="term">Blue</span>, <span class="term">Orange</span>, <span class="term">Green</span>, <span class="term">Yellow</span>, <span class="term">Gra</span><span class="term">y</span>, <span class="term">Warm</span>, <span class="term">Cold</span>, <span class="term">Bright</span>, <span class="term">Soft</span>, and <span class="term">Pastel</span>.
For <span class="term">Chart </span>object, implemented the following:</p><ul><li>Properties <span class="term">GradientPaletteStartColor</span>, <span class="term">GradientPaletteEndColor</span>, and <span class="term">GradientPaletteMaxColors</span></li><li>Methods <span class="term">GetPalette()</span> and <span class="term">SetPalette()</span></li></ul><p>For <span class="term">ChartType</span> appearance item of data composition system objects <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroup</span><span class="term">OutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemp</span><span class="term">lateChartAppearance</span>, implemented parameters <span class="term">ColorPalette</span>, <span class="term">GradientPaletteStartColor</span>, <span class="term">GradientPaletteEndColor</span>, and <span class="term">GradientPaletteMaxColors</span>
</p></td><td>Only two palettes (with 8 and 32 colors respectively) were available for picking chart colors. Creation of custom chart color palettes was not supported.</td><td>Additional chart appearance features are now implemented.</td></tr><tr title="Версия 8.3.10" class="compat tag_25 tag_1"><td><a name="c052b6cc-be03-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When data composition output processor outputs merged cells to a spreadsheet document, width of the columns containing merged cells is adjusted in order to minimize height of the content of these cells.
This change is not implemented in 8.3.9 compatibility mode. </td><td>When data composition processor outputted merged cells to a spreadsheet document, width of the columns containing merged cells was not adjusted in some cases. This could result in inappropriately narrow columns. </td><td>Calculation of width of spreadsheet document columns containing merged cells performed by data composition output processor is improved in some cases.</td></tr><tr title="Версия 8.3.10" class="tag_82"><td><a name="26e035dd-de17-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>The <span class="term">PointInTimeWithPeriodAdjustment </span>type is available in the thin and web clients.</td><td>The <span class="term">PointInTimeWithPeriodAdjustment </span>type was available only in the thick client and only on the server.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="tag_26"><td><a name="0aa9d07b-de28-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>For spreadsheet documents, the option to paste data that has XLS (Microsoft Excel 97-2003) or ODS (OpenDocument Spreadsheet) format is added to the <span class="interface">Paste special </span>operation.</td><td>For spreadsheet documents, the option to paste data that has XLS (Microsoft Excel 97-2003) or ODS (OpenDocument Spreadsheet) format was not available.</td><td>The <span class="interface">Paste special </span>operation now supports selection from all spreadsheet formats that support pasting.</td></tr><tr title="Версия 8.3.10" class="compat tag_26 tag_25 tag_1"><td><a name="a2e1026b-ed1d-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>For spreadsheet documents, the option to automatically adapt column width to the display area is implemented (both for viewing and printing). For <span class="term">SpreadsheetDocumentRange </span>and <span class="term">DataCompositionAreaTemplateTableCellAppearance </span>objects, implemented properties <span class="term">HorizontalStretch </span>and <span class="term">WidthWeightFactor</span>. For <span class="term">DataCompositionAppearance </span>object, implemented appearance parameters <span class="term">HorizontalStretch </span>and <span class="term">WidthWeightFactor</span>.<p>When the data composition system displays a chart in a spreadsheet document, it automatically sizes the chart to fit the display area width.</p><p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>Spreadsheet document column width could not be adapted to the display area width.<p>When the data composition system displayed a chart in a spreadsheet document, the chart had fixed width.</p></td><td>Improved options for adapting spreadsheed documents to the display area.</td></tr><tr title="Версия 8.3.10" class="tag_26"><td><a name="8f0b2303-ed38-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>For form field extension for a spreadsheet document field, the following improvements are implemented:<ul><li>More options for cell selection visibility. You can completely hide the cell selection, or you can make the cell selection visible only when multiple cells are selected (<span class="interface">Show selection</span> property). For <span class="term">SelectionShowMode </span>system enumeration, implemented properties <span class="term">DontShow</span>, <span class="term">WhenMultipleCellsSelected</span>, and <span class="term">WhenMultipleCellsSelectedWhenActive</span>.</li><li>More options for scroll bar visibility: you can have scroll bars displayed only when necessary. The type of <span class="term">VerticalScrollBar </span>и <span class="term">HorizontalScrollBar </span>properties is changed to <span class="term">ScrollBarUse</span>.</li><li>The option to change the shape of pointer located in a form field extension for a spreadsheet document field. The pointer shape can change depending on the spreadsheet document area where it is located. Implemented property <span class="term">PointerType</span>.</li><li>The behavior of arrow keys depends on the <span class="interface">Show selection</span><span class="interface"> </span>property value. If this property is set to <span class="interface">Do not show</span>, the arrow keys scroll the spreadsheet document. If this property is set to any of <span class="interface">When multiple cells...</span> values, pressing the arrow keys while holding down <span class="interface">Shift </span>changes the selection size, and pressing arrow keys without holding down <span class="interface">Shift </span>scrolls the spreadsheet document (while keeping the selection).</li></ul></td><td>The following options were available for form field extension for a spreadsheet document field:<ul><li>The selection was either always visible or visible when a cell was activated.</li><li>The scroll bars were always visible or always hidden. Making scroll bars visible when necessary was not available.</li><li>The pointer shape in a spreadsheet document always depended on the content of the cell where is was located.</li><li>The behavior of arrow keys in a spreadsheet document did not depend on any properties of form field extension for a spreadsheet document field.</li></ul></td><td>Extended display options for spreadsheet documents embedded in managed forms.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="d8f622ed-f42d-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed form tables, improved algorithm for automatic column width calculation based on the font settings.<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>The algorithm for automatic column width calculation based on the font settings sometimes generated poor results.</td><td>Improved view of managed form tables.</td></tr><tr title="Версия 8.3.10" class="tag_27"><td><a name="85bd0602-fd93-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>When restoring help topics from XML files, 1C:Enterprise does not check whether the language of the help topics (<span class="interface">Language </span>configuration object) is available in the configuration.</td><td>When restoring help topics from XML files, 1C:Enterprise did not restore the help topics whose language (<span class="interface">Language </span>configuration object) was not available in the configuration.</td><td>Simplified dumping and restoration of configurations, external reports, and external data processors to or from XML files.</td></tr><tr title="Версия 8.3.10" class="tag_20 tag_38"><td><a name="4753f873-001a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Configuration extension bookmarks, breakpoints, and performance measurements are stored with extension names.</td><td>Configuration extension bookmarks, breakpoints, and performance measurements were stored with internal extension IDs.</td><td>Support for future integration of extension debugging with 1C:Enterprise Development Tools.</td></tr><tr title="Версия 8.3.10" class="tag_18 tag_26"><td><a name="75de6556-0e0f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 18); return false;">macOS</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Implemented export of spreadsheet documents to PDF format on macOS.</td><td>An attempt to export a spreadsheet document to PDF format on macOS generated an error.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="tag_131"><td><a name="af2f4427-0e3b-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 131); return false;">Operating system</a>.<br></td><td>The time zone detection algorithm on Windows is modified. Now the time zone is determined as follows:<ul><li>Get time zone presentation using Windows API.</li><li>Search Windows registry for time zone ID by presentation.</li><li>Use ICU library to determine time zone by ID.</li><li>If the time zone cannot be determined using this algorithm, try the previous algorithm.</li></ul></td><td>The platform used the following time zone detection algorithm on Windows:<ul><li>Get time zone ID from Windows registry.</li><li>Use ICU library to determine time zone by ID.</li><li>If the time zone with this ID is not found in ICU, get time zone using Windows API.</li><li>Apply time zone parameters (offset, daylight saving time, and so on) and search ICU for a matching time zone.</li></ul></td><td>The session time zone is determined correctly on Windows terminal servers.</td></tr><tr title="Версия 8.3.10" class="tag_19"><td><a name="a1ac9957-144e-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>If 1C:Enterprise is running in managed lock mode (in client/server mode) with PostgreSQL version 9.3 or later, it supports setting lock waiting time. The waiting time is retrieved from the infobase parameters, just like in configurations that use other DBMS types.</td><td>If 1C:Enterprise was running in managed lock mode (in client/server mode) with PostgreSQL version 9.3 or later, it did not support setting lock waiting time. In configurations that used PostgreSQL, setting lock waiting time was only supported in automatic lock mode.
</td><td>In configurations that used PostgreSQL, operations with lock waiting time in managed mode are identical to operations with lock waiting time in configurations that use other DBMS.</td></tr><tr title="Версия 8.3.10" class="tag_63 tag_26"><td><a name="93f10c1a-24ec-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When a spreadsheet document that contains a chart is saved to a file, automatically assigned point colors, series colors, and series markers are stored in the format supported by earlier 1C:Enterprise versions. This ensures that the colors and markers are displayed correctly in earlier 1C:Enterprise versions.</td><td>When a spreadsheet document that contained a chart was saved to a file, automatically assigned colors and markers were stored in the format that was not supported by earlier 1C:Enterprise versions. This might significantly alter the chart look in earlier 1C:Enterprise versions.</td><td>The look of spreadsheet documents with charts in earlier 1C:Enterprise versions is very similar to their look in 1C:Enterprise version 8.3.10 or later.</td></tr><tr title="Версия 8.3.10" class="tag_37"><td><a name="bc9cff7f-30db-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The DigiCert certifying center root certificate was added to the cacert.pem file (root certificates file), included in the platform.</td><td>The DigiCert certifying center root certificate was not included in the cacert.pem file (root certificates file).<p>
</p></td><td>1C:Enterprise applications can now connect to 1C company services. Service infrastructure update is needed.</td></tr><tr title="Версия 8.3.10" class="tag_80"><td><a name="4b30c5d9-095a-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 80); return false;">External reports and data processors</a>.<br></td><td>The option to disable the warning of the unsafe operation protection system when you create an external report or data processor object is implemented (use it when you are sure that the file specified in the method parameter contains trusted script).<p>For the <span class="term">Create()</span> method of <span class="term">ExternalReportsManager</span> and <span class="term">ExternalDataProcessorsManager</span> objects, the <span class="term">UnsafeOperationProtection</span> parameter is implemented.</p></td><td>This feature was not provided.</td><td>When adding an external report or an external data processor from a file, you can specify that the file contains trusted script and therefore does not require displaying the unsafe operation protection system warning.</td></tr></table><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="ce205a23-37b8-11e6-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="e4cb9dbf-897c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When collapsing a node of a value tree with subordinate items that is displayed in a managed form, event <span class="term">BeforeCollapse </span>is generated for each node being collapsed throughout the hierarchy.
This change is not implemented in 8.3.9 compatibility mode.</td><td>When collapsing a node of a value tree with subordinate items that is displayed in a managed form, event <span class="term">BeforeCollapse </span>was only generated for top-level tree items.</td><td>Eliminated unexpected system behavior.
Value tree items to be collapsed are now defined more precisely in interactive mode.</td></tr><tr title="Версия 8.3.10" class="compat tag_110 tag_1"><td><a name="19711ac9-897f-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br></td><td>Calling the <span class="term">AccessRight()</span> method generates an exception if the access right being checked cannot be applied to a metadata object.
This change is not implemented in 8.3.9 compatibility mode.</td><td>Calling the <span class="term">AccessRight() </span>method always returned <span class="term">True </span>if the access right being checked could not be applied to a metadata object.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_25 tag_1"><td><a name="eddbaeb1-8ae3-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Data composition schema parameters whose types contain only types disabled by functional options are added to the list of available data composition schema parameters with disabled visibility. Therefore, these parameters cannot be edited by users but can still be accessed from 1C:Enterprise script. Moreover, these parameters are not added to the list of available parameter fields.
When a report option is loaded, the usage flag is cleared for the data parameters disabled by functional options.
The<span class="term"> </span><span class="term">DataCompositionSettingsComposer.Refresh</span><span class="term">()</span> method disables the <span class="term">Us</span><span class="term">e </span>property of data parameters disabled by functional options.
This change is not implemented in 8.3.9 compatibility mode.</td><td>Functional options did not affect the visibility of data composition parameters.
When a report option was loaded, the usage flag was not cleared for the data parameters disabled by functional options.
The<span class="term"> </span><span class="term">DataCompositionSettingsComposer.Refresh</span><span class="term">()</span> method did not modify the <span class="term">Us</span><span class="term">e </span>property of data parameters disabled by functional options.</td><td>Management of report parameters of types disabled by functional options is now more user-friendly.</td></tr><tr title="Версия 8.3.10" class="tag_83"><td><a name="c1ac1a1d-8ae6-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 83); return false;">HTML support</a>.<br></td><td>For <span class="term">HTMLDocumentShell </span>object, implemented property <span class="term">TemplateLanguageCode</span>. If this property is set, the following methods of this object return a result for the specified language: <span class="term">GetCOMObject()</span>, <span class="term">GetHTMLDocument()</span>, and <span class="term">GetText()</span>.</td><td>Selection of language to be used in return values of <span class="term">HTMLDocumentShell </span>object methods was not available for HTML templates. </td><td>Now HTML templates can be used for languages that do not match the language of the current session.</td></tr><tr title="Версия 8.3.10" class="compat tag_29 tag_1"><td><a name="c1cf4a29-8b11-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Changed presentation of Microsoft Windows version, starting from Windows Vista, in <span class="term">SystemInfo</span><span class="term">.OSVersion </span>property. The property text contains the user presentation of the operating system name, as well as technical information (version, build number, and so on).
This change is not implemented in 8.3.9 compatibility mode.</td><td>Presentation of Microsoft Windows version, starting from Windows Vista, in <span class="term">SystemInfo</span><span class="term">.OSVersion </span>property did not contain the user presentation of operating system name.</td><td>Information about Microsoft Windows version stored in <span class="term">SystemInfo</span><span class="term">.OSVersion</span> property (for systems running on Microsoft Windows) now offers better readability.</td></tr><tr title="Версия 8.3.10" class="compat tag_65 tag_37 tag_1"><td><a name="69396c84-8b16-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>When method <span class="term">HTTPConnection.CallHTTPMethod()</span> is called, its parameter <span class="term">HTTPMethod</span> must comply with RFC 7230 <a href="https://datatracker.ietf.org/doc/html/rfc7230" target="_blank">Read more</a>.. If this requirement is not met, an exception is raised.
This change is not implemented in 8.3.9 compatibility mode.</td><td>When method <span class="term">HTTPConnection.CallHTTPMethod()</span> was called, its parameter <span class="term">HTTPMethod </span>could take up any value.</td><td>The behavior of 1C:Enterprise better complies with RFC standards now.</td></tr><tr title="Версия 8.3.10" class="compat tag_19 tag_1"><td><a name="16c6b8ef-8b18-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>When a 1C:Enterprise application runs in client/server mode using a Microsoft SQL Server database, a query containing expression <span class="term">CAST</span><span class="term">(...</span><span class="term"> AS STRING(...</span><span class="term">))</span> adds trailing space characters to the operation result until it reaches the required length.
This change is not implemented in 8.3.9 compatibility mode.</td><td>When a 1C:Enterprise application ran in client/server mode using a Microsoft SQL Server database, a query containing expression <span class="term">CAST</span><span class="term">(...</span><span class="term"> AS STRING(...</span><span class="term">))</span> did not add trailing space characters to the operation result until it reached the required length.</td><td>1C:Enterprise behavior is now uniform across all supported databases.</td></tr><tr title="Версия 8.3.10" class="tag_56"><td><a name="de89098b-7274-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>Serialization of a <span class="term">ValueList </span>object using the <span class="term">XDTOFactory.WriteXML()</span> method creates an XML document based on the schema used for serialization of this object with <span class="term">XDTOSerializer.WriteXML() </span>method.<p>Due to this change:</p><ul><li>Value lists serialized in version 8.3.10 cannot be read in version 8.3.6 or earlier but can be read in version 8.3.7 or later by using <span class="term">XDTOFactory</span></li><li>Value lists serialized in version 8.3.10 can be read in version 8.3.6 or earlier by using <span class="term">XDTOSerializer</span></li><li>Value lists serialized in versions 8.3.7 to 8.3.9 can be read in any version.
</li></ul></td><td>Serialization of a <span class="term">ValueList </span>object using the <span class="term">XDTOFactory.WriteXML()</span> method created an XML document that did not match the schema used for serialization of this object with <span class="term">XDTOSerializer.WriteXML() </span>method.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="1a472edb-9540-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If a hyperlink is displayed in a managed form table cell and <span class="interface">Read only </span>mode is set for this table cell, double-clicking this cell results in raising the <span class="term">Selection </span>table event once.
This change is not implemented in 8.3.9 compatibility mode.</td><td>If a hyperlink was displayed in a managed form table cell and <span class="interface">Read</span><span class="interface"> only</span> mode was set for this table cell, double-clicking this cell resulted in raising two <span class="term">Selection </span>table events.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_20 tag_1"><td><a name="1b116d4e-9542-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>For event subscriptions, implemented the match check for events and source types. The check is performed prior to saving the configuration. If the event does not match the source type, an error is generated and the configuration is not saved.
This change is not implemented in 8.3.9 compatibility mode</td><td>For event subscriptions, the match check for events and source types was not performed. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_45 tag_1"><td><a name="85812272-95ca-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>An error is generated during query analysis if the expression following the temporary table name does not contain the field name.
This change is not implemented in 8.3.9 compatibility mode.</td><td>During query analysis, if the expression following the temporary table name did not contain the field name, the name of the first field of the temporary table was used instead. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_26 tag_1"><td><a name="79f87bfe-96af-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When displaying spreadsheet documents in <span class="interface">Taxi </span>interface, the <span class="term">Auto </span>text color is selected as follows:<ul><li>For displaying on monitors: style-based color for text editing</li><li>For printing: black</li></ul><p>This change is not implemented in 8.3.9 compatibility mode. </p></td><td>When displaying spreadsheet documents in <span class="interface">Taxi </span>interface, black was always used as the <span class="term">Auto </span>text color. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="63c67d19-96b1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For attributes of <span class="term">String </span>or <span class="term">Number </span>type displayed in a managed form input field with list selection mode enabled:<ul><li>Restrictions to the length of string that can be entered are removed</li><li>The input field displaying this data is automatically stretched horizontally</li></ul><p>This change is not implemented in 8.3.9 compatibility mode. </p></td><td>When editing values of <span class="term">Number </span>type in a managed form input field with list selection mode enabled, number qualifiers configured for the attribute were affecting format of the text being edited. </td><td>Improved usability of text input fields.</td></tr><tr title="Версия 8.3.10" class="compat tag_26 tag_1"><td><a name="36dc24b4-9776-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When processing a template in a spreadsheet document cell, content located between the final section [] and an escaped character [ is not removed from the result.
This change is not implemented in 8.3.9 compatibility mode.</td><td>When processing a template in a spreadsheet document cell, content located between the final section [] and an escaped character [ was removed from the result.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="tag_37"><td><a name="beb1aa75-979a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>When 1C:Enterprise is running on Microsoft Windows, web server certificate checks are performed for all chains of trusted certificates registered in the Windows trusted certificate store.</td><td>When 1C:Enterprise was running on Microsoft Windows, web server certificate checks could fail if a trusted parent certificate of the certificate being checked was not registered in the trusted certificate store.</td><td>Eliminated situations that could occur on Microsoft Windows when 1C:Enterprise failed to check a web server certificate via HTTPS/FTPS if the server certificate publisher was not included in the list of trusted root certificates.</td></tr><tr title="Версия 8.3.10" class="compat tag_21 tag_1"><td><a name="4b3b75e5-99f5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>If a full-text search query generates multiple intermediate results and the search result contains under 1 mln records, the user gets the search result. This change is not implemented in 8.3.9 compatibility mode.
To enable this feature, set the configuration compatibility mode to <span class="interface">None </span>and update the full-text search index.
The later a data item was modified, the higher in the full-text search results it is displayed (within a single configuration object, such as a document type). </td><td>If a full-text search query generated multiple intermediate results, the error stating that there are too many search results was displayed to the user. </td><td>Full-text search now returns results when searching for several words that commonly occur separately but rarely occur together.</td></tr><tr title="Версия 8.3.10" class="tag_70"><td><a name="ed3fd0ba-b09f-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>Searching the distribution kit directories for new 1C:Enterprise versions when opening the infobase list window is now faster. The search is performed for the names of distribution kit directories.
Distribution kit type and bitness are determined based on the name of<span class="interface"> .msi </span>file:<ul><li><span class="interface">1CEnterprise 8.msi</span> — 32-bit version, full distribution kit</li><li><span class="interface">1CEnterprise 8 Thin client.msi</span> — 32-bit version, thin client</li><li><span class="interface">1CEnterprise 8 (x86-64).msi </span>— 64-bit version, full distribution kit</li><li><span class="interface">1CEnterprise 8 Thin client (x86-64).msi</span> — 64-bit version, thin client</li></ul><p> </p><p> </p></td><td>Searching the distribution kit directories for new 1C:Enterprise versions was insufficiently fast because it relied on data stored in properties of <span class="interface">.msi </span>files.</td><td>The infobase list dialog box now opens faster if the<span class="interface"> Install new application versions automatically</span> check box is selected in the dialog box settings.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="10b4f064-b0c4-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When attempting to create a managed form group with an invalid value of <span class="term">Type </span>property using 1C:Enterprise script, an exception is raised.
This change is not implemented in 8.3.9 compatibility mode.</td><td>When attempting to create a managed form group with an invalid value of <span class="term">Type </span>property using 1C:Enterprise script, the system behavior was not defined and could result in abnormal termination. </td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="tag_25"><td><a name="0f11de27-b162-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Implemented setting expressions simultaneously both for detailed records and totals records of user-defined fields of the data composition system. Implemented the same for user-defined field presentations in detailed records and totals records of the data composition system.
For <span class="term">DataCompositionUserFieldExpression </span>object, implemented methods <span class="term">SetExpressions()</span> and <span class="term">SetExpressionsPresentation</span><span class="term">()</span>.
Methods<span class="term"> SetDetail</span><span class="term">RecordExpression()</span>, <span class="term">SetTotal</span><span class="term">RecordExpression()</span>, <span class="term">SetDetail</span><span class="term">RecordExpressionPresentation()</span>, and <span class="term">SetT</span><span class="term">otal</span><span class="term">RecordExpressionPresentation()</span> are now deprecated and supported for compatibility purposes only. It is recommended that you do not use any of these. </td><td>Expressions of user-defined fields of the data composition system for detailed records and totals records were set by different methods. Presentations of user-defined fields of the data composition system for detailed records and totals records were also set by different methods. </td><td>Eliminated unexpected system behavior.
User-defined fields of the data composition system that contain deleted or renamed query fields in both expressions are now editable.</td></tr><tr title="Версия 8.3.10" class="compat tag_25 tag_1"><td><a name="e6c77be0-b168-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When automatically filling available fields of query data set for virtual tables of information registers, dimension fields become available for filtering based on virtual table parameters.
This change is not implemented in 8.3.9 compatibility mode.
</td><td>When automatically filling available fields of query data set for virtual tables of information registers, dimension fields did not become available for filtering based on virtual table parameters.</td><td>Getting data from information registers through the data composition system is now more efficient when virtual tables of information registers are used.</td></tr><tr title="Версия 8.3.10" class="compat tag_45 tag_1"><td><a name="7a2595fe-b22c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>When adding filter expressions to a query by using <span class="term">QuerySchemaExpression </span>object constructor, the filter expressions are added without conversion.
This change is not implemented in 8.3.9 compatibility mode. </td><td>When adding filter expressions to a query by using <span class="term">QuerySchemaExpression </span>object constructor, the filter expressions were corrupted due to conversion.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_67 tag_1"><td><a name="2fc07784-be0e-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>New configuration repositories are created in version 8.3.8 format, with page size 8192 bytes.<p>You can use the <span class="interface">cnvdbfl </span>utility to change configuration repository format from version 8.2.14 to version 8.3.8 and vice versa.</p></td><td>The configuration repository database was created in version 8.2.14 format.</td><td>You can set the configuration repository format to version 8.3.8. Repositories that have this format can store larger reporitory history.</td></tr><tr title="Версия 8.3.10" class="compat tag_82 tag_1"><td><a name="dddbb17d-c082-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>If an accounting register resource value is associated with the accounting flag for a chart of accounts, values of this resource in <span class="term">Balance</span>, <span class="term">Turnovers</span>, <span class="term">Balance</span><span class="term">AndTurnovers</span>, and <span class="term">DrCrTurnovers </span>virtual tables depend on the status of this accounting flag for each account. If the accounting flag is set, the resource value has <span class="term">Number </span>type. If the accounting flag is cleared, the resource has value is <span class="term">NULL</span>.
This change is not implemented in 8.3.9 compatibility mode. </td><td>Virtual tables of accounting registers (<span class="term">Balance</span>, <span class="term">Turnovers</span>, <span class="term">BalanceA</span><span class="term">ndTurnovers</span>, and <span class="term">DrCrTurnovers</span>) could return non-<span class="term">NULL </span>values of accounting register resources associated with accounting flags for accounts where these accounting flags were disabled.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_28 tag_14 tag_96 tag_115 tag_23 tag_1"><td><a name="ddb4f238-c206-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Ended support of modal windows in the web client, regardless of web browser used. Any modal method call performed by an application now raises an exception.
For the thin client and web client, ended support of document posting performed in the mode interactively specified by the user. Accessing a document with such posting mode now raises an exception. The system enumeration value <span class="term">PostingModeUs</span><span class="term">e.Ask</span> is no longer supported by the thin client and web client.
The window opening option (<span class="term">Window </span>parameter) is now ignored when used in methods <span class="term">OpenForm()</span> and <span class="term">GetForm()</span>, and when used as a structure property value <span class="term">CommandExecute</span><span class="term">Parameters.Window</span> (with type defined by system enumeration <span class="term">WindowOpenVariant</span>). In the thin client, the <span class="term">Window </span>parameter is ignored when the compatibility mode is disabled. The system enumeration <span class="term">WindowOpenVariant</span><span class="term"> </span>is excluded from the Syntax Assistant.
In the thin client and web client, forms can no longer be opened in separate windows when <span class="interface">Forms i</span><span class="interface">n tabs</span> interface mode is enabled.
In the web client, ended support of interface mode <span class="interface">Forms i</span><span class="interface">n separate windows</span>. In the thin client, interface mode<span class="interface"> Forms i</span><span class="interface">n separate windows </span>cannot be enabled through the client application parameters dialog box. In the web client, ended support of the web client command-line parameter <span class="term">isdi</span>.
The check whether popup windows are blocked is not performed when starting the web client.
</td><td>Windows that locked other windows were supported in the web client.
Document posting mode could be specified by the user interactively, as a part of the posting procedure.
In the thin client and web client, forms could be opened in separate windows when interface mode<span class="interface"> Forms i</span><span class="interface">n tabs </span>was enabled.
In the web client, interface mode <span class="interface">Forms i</span><span class="interface">n separate windows </span>was supported.</td><td>Ended support of interface mode not supported by the current web browsers.</td></tr><tr title="Версия 8.3.10" class="tag_96 tag_64"><td><a name="f0b899eb-c20a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>For global context method<span class="term"> ShowUserNotification</span><span class="term">()</span>, implemented parameters <span class="term">UserNotificationStatus</span> and <span class="term">Uniqueness</span><span class="term">Key</span>. The parameter of <span class="term">URL </span>method is renamed to <span class="term">ActionOnC</span><span class="term">lick</span>.<p>The look of notifications with <span class="term">Info</span><span class="term">rmation </span>status is slightly changed. In <span class="interface">Taxi </span>interface, notifications with <span class="term">Important </span>status are redesigned, including the following changes:</p><ul><li>Displaying multiple notifications simultaneously</li><li>Displaying notifications while the main application window is minimized</li><li>Refreshing the notification window until the user closes it</li><li>Reacting to the user clicking the notification window</li></ul><p>Implemented notification management through the notification center. Dragging the notification window is not supported.
</p><p>For the specifics of notification behavior depending on the operating system and the client application, refer to the documentation.</p></td><td>These features were not provided.
Capabilities of global context method <span class="term">ShowUserNotification() </span>were limited.</td><td>Notifications with <span class="term">Important </span>status are implemented. They are displayed even if the application window is inactive.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_26 tag_1"><td><a name="3c7cf5b6-c2b1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Implemented the availability to open details for Gannt charts displayed in spreadsheet documents. The procedure is identical to opening details for Gannt charts displayed in managed forms.<p>For spreadsheet document event handlers <span class="term">DetailProcessing </span>and <span class="term">AdditionalDetailProcessing</span>, implemented parameter <span class="term">AdditionalParameters</span>. This parameter stores the date that is used as an input parameter for retrieving the details. This change is not implemented in 8.3.9 compatibility mode.
The context menu of Gantt charts in spreadsheet documents now opens on releasing the right mouse button. This change is not implemented in 8.3.9 compatibility mode. </p></td><td>Any attempt to access details for a Gantt chart in a spreadsheet document resulted in opening a window containing a noninteractive list of details.
Spreadsheet document event handlers <span class="term">DetailProcessing </span>and <span class="term">AdditionalDetailProcessing </span>had only two parameters (and did not have the <span class="term">AdditionalParameters </span>parameter).
The context menu of Gantt charts embedded in spreadsheet documents opened on clicking the right mouse button.</td><td>Eliminated unexpected system behavior.
The behavior of Gantt chart details in spreadsheet document is now standardized.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_28 tag_1"><td><a name="f6b8ce05-c2b8-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>If chart properties <span class="interface">Adjust series</span> and <span class="interface">Adjust points</span> are set to <span class="term">False</span>, series colors or point colors now use the custom color palette in the thin client. This change is not implemented in the web client .
This change is not implemented in 8.3.9 compatibility mode.<p>
</p><p>
</p></td><td>If chart properties <span class="interface">Adjust series </span>and <span class="interface">Adjust points </span>were set to <span class="term">False</span>, series colors or point colors used the default color palette in the thin client, and the custom color palette in the web client.</td><td>Eliminated inconsistencies in chart appearance between the web client and thin client.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_1"><td><a name="275da5ad-c2ba-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>During chart deserialization, if <span class="interface">Adjust series </span>or <span class="interface">Adjust points </span>property is set to <span class="term">False</span>, series colors or point colors use the custom color palette (they are set once the palette is loaded).
This change is not implemented in 8.3.9 compatibility mode.</td><td>During chart deserialization, if <span class="interface">Adjust series </span>or <span class="interface">Adjust points</span> property is set to <span class="term">False</span>, series colors or point colors used the default color palette.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_1"><td><a name="ae7d2416-c2ba-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>During interactive chart editing, if <span class="interface">Adjust series </span>or <span class="interface">Adjust points </span>property is set to <span class="term">False</span>, the following operations are performed:<ul><li>Parameters controlling the appearance of series or points are set to default values</li><li>The chart is redrawn.</li></ul><p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>During interactive chart editing, parameters controlling appearance of series or points were not set to default values if <span class="interface">Adjust series </span>or <span class="interface">Adjust points</span> property was set to <span class="term">False</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_63 tag_1"><td><a name="cabf8960-c2bc-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>If <span class="interface">Adjust s</span><span class="interface">eries</span> or <span class="interface">Adjust p</span><span class="interface">oint</span><span class="interface">s</span> chart property is set to <span class="term">False</span>, any attempt to change series properties or point properties for this chart by using 1C:Enterprise script raises an exception.
This change is not implemented in 8.3.9 compatibility mode.
</td><td>Attempts to change a series or point property for a chart by using 1C:Enterprise script did not raise an exception if <span class="interface">Adjust s</span><span class="interface">eries</span> or <span class="interface">Adjust p</span><span class="interface">oint</span><span class="interface">s</span> chart property was set to <span class="term">False</span>. The property was set for series or point instead.</td><td>Invalid chart use is not allowed now</td></tr><tr title="Версия 8.3.10" class="compat tag_36 tag_1"><td><a name="79e121cf-de2d-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>In a value table generated using the <span class="term">Unload()</span> method of a tabular section of any object, names of predefined columns are generated in 1C:Enterprise script language variant specified in the <span class="interface">Script variant </span>configuration property.<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>In a value table generated using the <span class="term">Unload()</span> method of a tabular section of any object, predefined column names could be accessed in the following 1C:Enterprise script language variants:<ul><li>If the resulting value table was not transferred between the client and the server, both English and Russian.</li><li>If the resulting value table was transferred between the client and the server, English only.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_120 tag_58 tag_1"><td><a name="e806cc84-e39a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>When a background job is started with a uniqueness key specified, the key uniqueness is verified within the area described by the current set of separators. For each unique set of separators, you can run a single background job with a uniqueness key specified.<p>This change is not implemented in 8.3.9 compatibility mode.
</p></td><td>When a background job was started with a uniqueness key specified, the key uniqueness was verified within the entire infobase, regardless of the separator values.</td><td>You can run a background job in each unique data area. For example, you can run long calculations in different areas of a separated infobase and avoid conflicts related to duplicate uniqueness keys.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="dd12b336-fd9a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If the <span class="term">Cancel </span>parameter of <span class="term">OnOpen </span>managed form handler is set to <span class="term">True</span>, once the handler execution is completed, the memory occupied by the form is cleared, all related resources (temporary storage, locks, and so on) are released, and idle handlers are disabled.<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>If the <span class="term">Cancel </span>parameter of <span class="term">OnOpen </span>managed form handler was set to <span class="term">True</span>, once the handler execution was completed, in some scenarios the memory occupied by the form was not cleared. Consequently, all related resources (temporary storage, locks, and so on) were not released, and idle handlers were not disabled.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="49ed79ad-0017-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Implemented the option to apply through alignment (<span class="interface">Through alignment </span>property) to managed form groups with <span class="interface">United</span><span class="interface"> </span>property set to <span class="term">False</span>.<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>For managed form groups with <span class="interface">United</span><span class="interface"> </span>property set to <span class="term">False</span>, the value of the <span class="interface">Through alignment </span>property was ignored.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="tag_15 tag_29"><td><a name="f6b203b8-0e0f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>1C:Enterprise system requirements for Linux computers are modified. The freetype library is now included in 1C:Enterprise distribution kit and excluded from the list of libraries whose availability is verified at 1C:Enterprise startup.</td><td>The freetype library was not included in 1C:Enterprise distribution kit. Its availability was verified at 1C:Enterprise startup.</td><td>The system requirements for Linux computers are simplified.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="34c9cca6-0fa4-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If <span class="term">FixingInTable </span>property of a managed form table column group is set to <span class="term">Left </span>or <span class="term">R</span><span class="term">ight</span>, all of the columns belonging to the group are fixed, as well as all other columns with this property set to <span class="term">Left </span>or <span class="term">Right</span>.<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>If <span class="term">FixingInTable </span>property of a managed form table column group was set to <span class="term">Left </span>or <span class="term">R</span><span class="term">ight</span>, only columns to the left or to the right of the group, respectively, were fixed. The columns included in the group were not fixed.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_115 tag_1"><td><a name="3b8677fa-235f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If a managed group form of "command bar" type has <span class="term">GroupVerticalAlign </span>property set to <span class="interface">Auto </span>and it belongs to a group or form with <span class="term">C</span><span class="term">hildItemsVerticalAlign </span>property set to <span class="interface">Auto</span>, the command bar is displayed at the top of the parent group (just below the last item).<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>If a managed group form of "command bar" type had <span class="term">GroupVerticalAlign </span>property set to <span class="interface">Auto </span>and it belonged to a group or form with <span class="term">C</span><span class="term">hildItemsVerticalAlign </span>property set to <span class="interface">Auto</span>, the command bar was displayed at the bottom of the parent group.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_43 tag_1"><td><a name="2421118a-2360-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In dynamic list search field, values that can be interpreted as numbers in exponential notation are treated as strings (the platform searches for the specified string).<p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>In dynamic list search field, values that could be interpreted as numbers in exponential notation were treated as numbers (the platform searched for the number).</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.10" class="compat tag_25 tag_1"><td><a name="68afc84b-4511-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The <span class="interface">Use </span>property of data parameters that can be edited by users but are disabled by functional options is disabled in the following scenarios:<ul><li>Loading a report option</li><li>Calling <span class="term">DataCompositionSettingsComposer</span><span class="term">.Refresh</span><span class="term">()</span></li></ul><p>This change is not implemented in 8.3.9 compatibility mode.</p></td><td>The <span class="interface">Use </span>property of data parameters that were disabled by functional options was disabled in the following scenarios:<ul><li>Loading a report option</li><li>Calling <span class="term">DataCompositionSettingsComposer</span><span class="term">.Refresh</span><span class="term">()</span></li></ul></td><td>Improved compatibility with data composition system queries created using previous 1C:Enterprise versions.</td></tr><tr title="Версия 8.3.10" class="tag_69 tag_28"><td><a name="2e968af5-572b-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client, <span class="term">Title()</span> function only converts strings that contain only Latin characters (A-Z, a-z), numbers, and special characters.<p>In other client applications and on the server, <span class="term">Title()</span> function behavior remains unchanged: the conversion rules are defined in the Unicode standard.</p></td><td>In the web client, <span class="term">Title() </span>function always returned the source string.</td><td>Corrected the behavior of <span class="term">T</span><span class="term">itle() </span>function.</td></tr><tr title="Версия 8.3.10" class="tag_29 tag_124"><td><a name="cfdf9acc-c9eb-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 124); return false;">Administration</a>.<br></td><td>1C:Enterprise distribution packages for Windows and macOS include HASP Device Driver 7.63.</td><td>1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 6.60 or 7.60.</td><td>1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver.</td></tr><tr title="Версия 8.3.10" class="tag_23"><td><a name="5295512b-dfe6-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>After restructuring a chart of calculation types, the order of lines in tabular sections of predefined calculation types changes.</td><td>The order of lines in tabular sections of predefined calculation types was different.</td><td>Changed line order in tabular sections of predefined charts of calculations types. If your application algorithms depend on the line order, we recommend that you eliminate the dependencies.</td></tr><tr title="Версия 8.3.10" class="tag_11 tag_29"><td><a name="7bb25879-f5e7-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The add-in development technology now supports Web Extensions API for Mozilla Firefox. It is recommended that you rebuild add-in distribution packages for Mozilla Firefox with new template projects. The resulting add-ins will be compatible with the same 1C:Enterprise 8 versions as before.<p>Updated the template project included in the add-in development technology (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>)</p></td><td>The add-in development technology did not support Web Extensions API for Mozilla Firefox.</td><td>The add-in development technology is adapted to new Mozilla Firefox requirements. Mozilla Firefox versions 57 and later do not support add-ins that use other interfaces rather then Web Extensions API.</td></tr></table><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="ce205a24-37b8-11e6-a3f7-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.10" class="tag_0"><td><a name="5008367f-8ad3-11e6-a3f7-0050569f678a"></a>Method <span class="term">StrStartWith()</span>. The previous name is now deprecated and supported for compatibility purposes only.</td><td><ul><li><span class="term">StrStartWith()</span>.</li></ul></td><td><ul><li><span class="term">StrStartsWith()</span>.</li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="8fdf5035-8ef9-11e6-a3f7-0050569f678a"></a>XSL stylesheet loading methods of <span class="term">XSLTransform</span> object.<p>The previous names are now deprecated and supported for compatibility purposes only.</p></td><td><ul><li><span class="term">LoadFromString()</span></li><li><span class="term">LoadFromNode()</span></li><li><span class="term">LoadFromFile()</span></li></ul></td><td><ul><li><span class="term">LoadXSLStylesheetFromString()</span></li><li><span class="term">LoadXSLStylesheetFromNode()</span></li><li><span class="term">LoadXSLStylesheetFromFile()</span></li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="fa37a228-905c-11e6-a3f7-0050569f678a"></a>Names of debug items used in file infobases.</td><td><ul><li>For Web services: <span class="interface">Server (file-based variant)</span></li><li>For HTTP services: <span class="interface">Server (file-based variant</span><span class="interface">)</span></li></ul></td><td><ul><li>For Web services: <span class="interface">Web service</span></li><li>For HTTP services: <span class="interface">HTTP service</span></li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="1e88d2ef-960a-11e6-a3f7-0050569f678a"></a>Titles in the sections panel settings dialog box.</td><td><ul><li><span class="interface">Available sections</span></li><li><span class="interface">Selected commands</span></li></ul></td><td><ul><li><span class="interface">Available sections:</span> (added trailing character «:»)</li><li><span class="interface">Selected sections</span></li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="0ac0e13e-b22d-11e6-a3f7-0050569f678a"></a>Changed presentation of spreadsheet document menu commands used for named area display management.</td><td><ul><li><span class="interface">Show Named Rows/Columns</span></li><li><span class="interface">Show Named Cells</span></li></ul></td><td><ul><li><span class="interface">Show row and column names</span></li><li><span class="interface">Show cell names</span></li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="10df0bd5-be14-11e6-a3f7-0050569f678a"></a>Presentations of configuration storage compatibility mode values.</td><td><ul><li><span class="interface">Version 8.3.2</span></li><li><span class="interface">Version </span><span class="interface">8.3.3</span></li></ul></td><td><ul><li><span class="interface">Version</span><span class="interface"> 8.3.2 or eralier</span></li><li><span class="interface">Versions</span><span class="interface"> 8.3.3 - 8.3.5</span></li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="97aa548d-f425-11e6-a3f7-0050569f678a"></a>Property <span class="term">InfoBaseUser</span><span class="term">.</span><span class="term">UnsafeActionProtection</span>. The previous name is now deprecated and supported for compatibility purposes only.</td><td><ul><li><span class="term">UnsafeActionProtection</span>.</li></ul></td><td><ul><li><span class="term">UnsafeOperationProtection</span>.</li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="c1381283-f425-11e6-a3f7-0050569f678a"></a>Object <span class="term">UnsafeActionProtectionDescription</span>. The previous name is now deprecated and supported for compatibility purposes only.</td><td><ul><li><span class="term">UnsafeActionProtectionDescription</span>.</li></ul></td><td><ul><li><span class="term">UnsafeOperationProtectionDescription</span>.</li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="f2df174b-f425-11e6-a3f7-0050569f678a"></a>Property <span class="term">UnsafeActionProtectionDescription.</span><span class="term">WarnAboutUnsafeActions</span>. The previous name is now deprecated and supported for compatibility purposes only.</td><td><ul><li><span class="term">WarnAboutUnsafeActions</span>.</li></ul></td><td><ul><li><span class="term">UnsafeOpe</span><span class="term">rationWarnings</span>.</li></ul></td></tr><tr title="Версия 8.3.10" class="tag_0"><td><a name="192220c9-fe6b-11e6-a3f7-0050569f678a"></a>The system enumeration that defines the height of a managed form table is renamed. The previous name is now deprecated and supported for compatibility purposes only.</td><td><ul><li><span class="term">HeightControlVariant</span>.</li></ul></td><td><ul><li><span class="term">ItemHeightControlVariant</span>.</li></ul></td></tr></table><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="ce205a25-37b8-11e6-a3f7-0050569f678a">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.10" class="tag_48"><td><a name="ab22030e-960e-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Implemented the following location features:<ul><li>Selecting a location provider either from the global list of providers, or from the list of providers available now</li><li>Checking if location service is enabled</li><li>Geofence management</li></ul><p>Implemented the <span class="term">Geofence </span>object. Implemented <span class="term">LocationRelativeToGeofence </span>system enumeration. Implemented <span class="term">L</span><span class="term">ocationProviderInformation.Available</span> property. Implemented <span class="term">AvailableOnly </span>parameter for the following methods of <span class="term">LocationTools </span>object: <span class="term">GetProviders()</span>,<span class="term"> GetProvider()</span>, <span class="term">GetMostAccurate</span><span class="term">Provider()</span>, and <span class="term">GetMostPowerSaving</span><span class="term">Provider()</span>. For <span class="term">L</span><span class="term">ocationTools</span> object , implemented methods:<span class="term"> L</span><span class="term">ocationDataUseEnabled()</span>, <span class="term">AttachProvidersAvailabilityChange</span><span class="term">Handler()</span>, <span class="term">DetachProvidersAvailabilityChange</span><span class="term">Handler()</span>, <span class="term">EnableGeofencesMonitoring()</span>, <span class="term">GetMonitoredGeofences()</span>, <span class="term">GetMonitoredGeofence()</span>, <span class="term">DisableGeofencesMonitoring()</span>, <span class="term">DisableAllGeofencesMonitoring()</span>, and <span class="term">AttachMonitoredGeofencesBordersCrossingDetectionHandler()</span>.</p></td><td>These features were not provided.</td><td>Location management capabilities are now expanded. For example, predefined actions can be performed when a mobile device reaches a specific location.</td></tr><tr title="Версия 8.3.10" class="tag_49"><td><a name="1c05e981-960f-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 49); return false;">Binary data</a>.<br></td><td>Implemented binary data management capabilities for the mobile platform.</td><td>This feature was not provided. Binary data management capabilities were only available for the PC platform.</td><td>Binary data management capabilities are now implemented for the mobile platform.</td></tr><tr title="Версия 8.3.10" class="tag_37"><td><a name="dd63b682-9a02-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Implemented check whether a mobile device is in roaming mode. The Internet connection change handler is called when the roaming mode status is changed.
Implemented method <span class="term">InternetConnectionInformation.GetRoaming</span><span class="term">Usage()</span>.</td><td>Check whether a mobile device is in roaming mode was not implemented.</td><td>A variety of actions can be performed when roaming mode is enabled on a mobile device. For example, access to mobile Internet can be restricted or prohibited due to high Internet charges in roaming.</td></tr><tr title="Версия 8.3.10" class="tag_37"><td><a name="055bd6f0-9a9f-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For mobile platforms running on Windows, implemented secured connection management capabilities.</td><td>Secured connection management capabilities were not available for mobile platforms running on Windows.</td><td>Mobile platforms running on Windows can now access resources that require secured connection.</td></tr><tr title="Версия 8.3.10" class="tag_8"><td><a name="caeffa43-9aa0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>Implemented encryption operations for the mobile platform. The mobile platform behavior is identical to that of the thin client. Details of the encryption operations are described in the documentation.
Implemented <span class="term">C</span><span class="term">rypt</span><span class="term">o</span><span class="term">Manager.Show</span><span class="term">CertificateList() </span>method. Implemented <span class="term">C</span><span class="term">rypt</span><span class="term">o</span><span class="term">KeysContainer </span>object. Changed behavior of the following methods of <span class="term">C</span><span class="term">rypt</span><span class="term">o</span><span class="term">CertificateStore</span> object on the mobile platform: <span class="term">Add()</span>, <span class="term">Delete</span><span class="term">()</span>, <span class="term">Begin</span><span class="term">Adding()</span>, and <span class="term">BeginD</span><span class="term">eleting</span><span class="term">().</span></td><td>Encryption operations were not implemented for the mobile platform.</td><td>On the mobile platform, you can implement a check whether a document stored locally was modified. Sensitive data and documents can now be securely sent through open channels thanks to encryption capabilities.</td></tr><tr title="Версия 8.3.10" class="tag_48"><td><a name="136389a3-9aa5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>For the mobile platform, implemented a check whether contacts and calendars can be added or edited.
For <span class="term">ContactManager </span>object, implemented methods <span class="term">ContactEditing</span><span class="term">Supported()</span> and <span class="term">ContactsAdding</span><span class="term">Supported()</span>.
For <span class="term">CalendarsManager</span> object, implemented methods <span class="term">CalendarEditingSupported()</span> and <span class="term">CalendarsAddingSupported()</span>.
The <span class="term">CalendarManager.</span><span class="term">CalendarEditing</span><span class="term">Supported</span> property is now deprecated and supported for compatibility purposes only.
For 1C:Enterprise applications running on Windows, the <span class="term">CalendarManager.EventEditing</span><span class="term">Supported()</span> method always returns <span class="term">False</span>.</td><td>The check whether contacts can be added or edited was not implemented.
The check whether calendars can be added or edited was implemented in a different way.</td><td>Unified contacts and calendar management as related to adding and editing objects.</td></tr><tr title="Версия 8.3.10" class="tag_48"><td><a name="5aca7135-b0a8-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Implemented new configuration permission: <span class="interface">Ads</span>. This permission is only used by the mobile application builder when selecting a mobile platform version for iOS to be used in the builds. If the <span class="interface">Ads </span>permission is used in the configuration export file, <span class="interface">The app</span><span class="interface"> uses ads </span>check box is unavailable in the mobile configuration form of the mobile application builder.</td><td>The permission specifying that ads are allowed for a mobile application was not implemented in the configuration. Instead, <span class="interface">The app uses ads </span> check box in the mobile application builder was used for this purpose.</td><td>Now the mobile application builder can be forced to use an advertisement-enabled mobile platform version for iOS in the builds.</td></tr><tr title="Версия 8.3.10" class="tag_78"><td><a name="e3fb191c-b225-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>For the mobile platform, implemented getting thumbnails for pictures and video files stored in the corresponding libraries of the mobile device. This feature requires the file path to start with <span class="term">content: </span>schema.
For <span class="term">File </span>object , implemented methods <span class="term">GetMobileDeviceLibraryFileThumbnail</span><span class="term">()</span> and <span class="term">BeginGetMobileDeviceLibraryFileThumbnail</span><span class="term">()</span>.</td><td>This feature was not provided.<p>It was possible to fully load a picture or video file into memory when a thumbnail could be used instead</p></td><td>Optimized mobile device memory use when loading pictures or video files from the corresponding libraries of the mobile device. Reduced risk of insufficient memory error for mobile applications that load a large number of pictures or video files from the corresponding libraries of the mobile device.</td></tr><tr title="Версия 8.3.10" class="tag_52"><td><a name="98cd284f-b578-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>Implemented data lock management for mobile platforms.
Implemented global context methods <span class="term">LockDataForEdit</span><span class="term">()</span>, <span class="term">UnlockDataForEdit</span><span class="term">()</span>, <span class="term">SetLockWaitTime()</span>, and <span class="term">GetLockWaitTime()</span>.
Implemented methods<span class="term"> IsLocked()</span>, <span class="term">Lock()</span>, and <span class="term">Unlock() </span>for objects <span class="term">CatalogObject</span>, <span class="term">DocumentObject</span>, and <span class="term">ExchangePlanObject</span>.
Implemented method <span class="term">AccumulationRegisterRecordSet.LockForUpdate()</span>.
Implemented method <span class="term">ManagedForm.LockFormDataForEdit</span><span class="term">()</span>.
Implemented <span class="term">DataLock </span>and <span class="term">DataLockItem </span>objects.
For <span class="term">Document</span>, <span class="term">Catalog</span>, and <span class="term">ExchangePlan </span>configuration objects, implemented the <span class="term">DataLockFields </span>property. For <span class="term">Configuration</span>, <span class="term">Document</span>, <span class="term">Catalog</span>, <span class="term">ExchangePlan</span>, <span class="term">Constant</span>, <span class="term">Sequence</span>, <span class="term">AccumulationRegister</span>, and <span class="term">InformationRegister </span>configuration objects, implemented <span class="term">DataLockControl</span><span class="term">Mode </span>property.</td><td>Managed lock support was not provided on the mobile platform.</td><td>Object lock management during background job execution on the mobile platform is now available.</td></tr><tr title="Версия 8.3.10" class="tag_78"><td><a name="6624c35b-b57d-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>Implemented getting a file mask that describes all files, as well as getting a file path separator character, regardless of the mobile operating system where 1C:Enterprise is running.
Implemented methods <span class="term">Get</span><span class="term">AllFilesMask()</span>, <span class="term">Get</span><span class="term">ClientAllFilesMask()</span>, <span class="term">GetServerAllF</span><span class="term">ilesMask</span><span class="term">()</span>,<span class="term"> GetPathSeparator()</span>, <span class="term">GetClientPathSeparator()</span>, and <span class="term">GetServerPathSeparator()</span>.
Implemented method <span class="term">BeginGettingMobileDeviceLibraryDir()</span>.</td><td>Getting a file mask that describes all files and getting a file path separator character regardless of the mobile operating system used was not supported.</td><td>File operations in mobile applications are nearly operating system-agnostic now.</td></tr><tr title="Версия 8.3.10" class="tag_29"><td><a name="e0081d48-babc-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Implemented Android 7.0 support. Implemented multiwindow mode for Android 7.0.
For Android versions 6.0 or earlier:<ul><li>Introduced a new API for operations with the mobile device camera</li><li>Implemented dynamic resolutions</li></ul></td><td>Multiwindow mode was not supported for Android 7.0. Dynamic resolutions were not supported for Android versions 6.0 or earlier. Dynamic resolution management was not supported for Android versions 6.0 or earlier.</td><td> Improved support of Android versions 6.0 and earlier.</td></tr><tr title="Версия 8.3.10" class="tag_48"><td><a name="8a4f1b6d-c29b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Implemented barcode scanning capability for mobile devices running Windows 10. Barcode scanning is not supported for mobile devices running Windows 8.1 or earlier.
For devices running Windows 10, implemented availability of <span class="term">MultimediaTools.ShowBarcodeScanning</span><span class="term">()</span> method, while <span class="term">MultimediaTools.BarcodeScanningSupported()</span> method returns a value specifying whether barcode scanning functionality is available.
For successful barcode scanning, continuous auto focus mode must be supported for the primary device camera.</td><td>Barcode scanning was not supported for mobile devices running Windows.</td><td>Expanded mobile platform capabilities for devices running Windows 10.</td></tr><tr title="Версия 8.3.10" class="tag_115"><td><a name="8a80cae4-c2a2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For the mobile platform, implemented form field extension for the calendar field. The form field extension for the calendar field does not support dragging.
</td><td>This feature was not provided. </td><td>Expanded <span class="term">Data </span>type data management capabilities for mobile platform forms.</td></tr><tr title="Версия 8.3.10" class="tag_77"><td><a name="a5fe16ce-04b6-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>Printing is now supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64).</td><td>Printing was not supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64).</td><td>Extended mobile application capabilities on Windows.</td></tr><tr title="Версия 8.3.10" class="tag_128"><td><a name="7b4f88c6-0fdf-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 128); return false;">Mobile applications</a>.<br></td><td>Hardware rendering support is implemented for user interface on Android devices.</td><td>This feature was not provided.</td><td>Improved performance of user interface generation on Android devices.</td></tr><tr title="Версия 8.3.10" class="tag_32"><td><a name="35b5293b-0015-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>In the mobile application builder, automatic deletion of obsolete data is implemented. Obsolete data is defined as mobile application builds and mobile platforms that were last changed (or imported) before a specific date. This date is calculated as follows: current date minus the specified number of days (the gap size). You can specify custom gaps for mobile application builds and mobile platforms.<p>Default values:</p><ul><li>90 days for mobile application builds</li><li>180 days for mobile platform files</li></ul><p>If you set the gap size to 0, obsolete objects are never deleted.</p><p>When you attempt to use an obsolete object, the mobile application builder prompts you to rebuild the mobile application or reimport the mobile platform.</p><p>
</p></td><td>The mobile application builder did not provide tools for automatic deletion of obsolete objects.</td><td>You have the option to keep the size of the mobile application builder infobase within reasonable limits, avoiding significant growth of the disk space occupied by this infobase.</td></tr><tr title="Версия 8.3.10" class="tag_32"><td><a name="34bece36-1a9c-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>The requirements to Android SDK components used to build mobile applications are defined by the requirements of the mobile platform version used to build the applications.<p>The builder uses the latest Android API Level available on the computer, provided that the API Level meets the mobile platform requirements. The requirements to other Android SDK components are defined by Android API Level requirements.</p><p>If the mobile platform was loaded in a previous builder version, the builder requires Android API Level version 24 or later.</p></td><td>The following Android SDK components were required to build mobile applications for Android:<ul><li>Android API Level version 23 or later</li><li>Android Tools version 20.0.3 or later</li><li>Android Platform Tools version 14 or later</li><li>Android Build Tools version 19.0.0 or later</li></ul><p>These requirements were applied regardless of the mobile platform versions used to build mobile applications. They were hardcoded in the mobile application builder.</p></td><td>The requirements to mobile application build infrastructure for Android are defined by the mobile platform version, instead of the requirements hardcoded in the mobile application builder.</td></tr><tr title="Версия 8.3.10" class="tag_32"><td><a name="235f7d86-af22-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>In mobile application builder, Gradle tool now can be used to build mobile applications. On Android SDK version 26 or later, you can build mobile applications using no other tools besides Gradle.<p>You can specify two Android SDK paths in the builder settings: one for version 25 or ealier and the other one for version 26 or later. Therefore, you can build mobile applications that require any specific Android SDK version.</p><p>Building with Gradle requires Java 8 on the computer that runs mobile application builder. It does not require Apache Ant.</p></td><td>Mobile application builder did not support building mobile applications with Gradle tool.</td><td>Building mobile applications that use new Android SDK versions is now available.</td></tr><tr title="Версия 8.3.10" class="tag_128"><td><a name="44bbc990-af31-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 128); return false;">Mobile applications</a>.<br></td><td>Since mobile platform version 8.3.10.71, only building mobile applications with Gradle tool is supported. Use mobile application builder provided as a part of the mobile platform distribution package to build mobile applications.<p>Since mobile platform version 8.3.10.71, Apache Ant is not required for building mobile applications.</p></td><td>Mobile platform versions earlier that 8.3.10.71 did not support Gradle. Building the mobile platform required Apache Ant.</td><td>The mobile application building procedure is modified to comply with the changes in the recommended application building procedure for Android.</td></tr><tr title="Версия 8.3.10" class="tag_29 tag_32"><td><a name="cd082f1e-d99f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>In the mobile platform, implemented iOS 11 support.<p>Extended graphical asset collection for mobile applications that run on iOS 11.</p><p>The mobile application builder supports the new graphical asset collection and building applications for iOS 11.</p></td><td>The mobile platform did not support iOS 11.</td><td>Implemented support of the latest operation system for Apple devices.</td></tr><tr title="Версия 8.3.10" class="tag_53"><td><a name="57ec56ea-00f6-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>In the event of unexpected shutdown of a mobile application on Android, 1C:Enterprise displays a dialog box with a detailed error description, with the option to copy the error description to the clipboard.</td><td>In the event of unexpected shutdown of a mobile application on Android, no error details were displayed.</td><td>Simplified diagnostics of unexpected shutdown causes. Applications users can send error details to mobile application developers.</td></tr><tr title="Версия 8.3.10" class="tag_96 tag_30"><td><a name="d55861bf-786b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 30); return false;">Mobile platform</a>.<br></td><td>A spreadsheet document now supports the <span class="term">Output </span>right on a mobile device. If the <span class="term">Output </span>right is disabled, the following functions are not available: copying to clipboard, printing and saving the displayed data.</td><td>A spreadsheet document did not support the <span class="term">Output </span>right on a mobile device. The following functions were always available: copying to clipboard, printing and saving the displayed data.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="ce205a26-37b8-11e6-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.10" class="tag_0"><a name="95633d1a-450d-11e7-a3f7-0050569f678a"></a>The OpenSSL library is updated to version 1.0.2k and modified to eliminate vulnerabilities.</li><li title="Версия 8.3.10" class="tag_0"><a name="60a9ab86-451d-11e7-a3f7-0050569f678a"></a>The libxml2 library is modified to eliminate vulnerabilities.</li><li title="Версия 8.3.10" class="tag_0"><a name="7182dff2-451d-11e7-a3f7-0050569f678a"></a>The libxslt library is modified to eliminate vulnerabilities.</li><li title="Версия 8.3.10" class="tag_0"><a name="ad21a4c0-45d0-11e7-a3f7-0050569f678a"></a>The libtiff library is updated to version 4.0.8.</li><li title="Версия 8.3.10" class="tag_0"><a name="bee680e9-45d0-11e7-a3f7-0050569f678a"></a>The libpng library is updated to version 1.6.29.</li></ul><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="ce205a27-37b8-11e6-a3f7-0050569f678a">Transition from the previous version to the version 8.3.10</a></h2><ul><li title="Версия 8.3.10" class="tag_0"><a name="ce205a28-37b8-11e6-a3f7-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.10.
</li><li title="Версия 8.3.10" class="tag_0"><a name="ce205a29-37b8-11e6-a3f7-0050569f678a"></a>Some features that are added in version 8.3.10 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.10" class="tag_0"><a name="54fe9343-99fb-11e6-a3f7-0050569f678a"></a>If a full-text search query generates multiple intermediate results and the search result contains under 1 mln records, the user gets the search result. <p>To enable this feature, set the configuration compatibility mode to <span class="interface">None </span>and update the full-text search index.</p></li><li title="Версия 8.3.10" class="tag_0"><a name="8e21de47-e20d-11e6-a3f7-0050569f678a"></a>It is recommended that you convert large configuration repositories (repositories that store 30 000 - 40 000 versions, such as 1C:ERP Enterprise Resource Planning 2) to version 8.3.8 format using the <span class="interface">cnvdbfl</span> utility.</li><li title="Версия 8.3.10" class="tag_0"><a name="113b3bac-c9ec-11e7-a3f7-0050569f678a"></a>It is recommended that you uninstall your HASP Device Driver and then install HASP Device Driver 7.63, which is a part of 1C:Enterprise distribution package.</li></ul><p><a href="#ce205a1e-37b8-11e6-a3f7-0050569f678a"><small>Table of contents</small></a></p><h1><a name="b2d31961-ca4c-11e5-a3f7-0050569f678a">Version 8.3.9</a></h1><p title="Версия 8.3.9" class="tag_0"><a name="b2d3196d-ca4c-11e5-a3f7-0050569f678a"></a>Version 8.3.9 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#b2d31962-ca4c-11e5-a3f7-0050569f678a">New functionality and changes</a></li><li><a href="#b2d31963-ca4c-11e5-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#b2d31964-ca4c-11e5-a3f7-0050569f678a">Optimization</a></li><li><a href="#b2d31965-ca4c-11e5-a3f7-0050569f678a">Changes that affect system behavior</a></li><li><a href="#b2d31966-ca4c-11e5-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#b2d31967-ca4c-11e5-a3f7-0050569f678a">Renamed objects</a></li><li><a href="#b2d31968-ca4c-11e5-a3f7-0050569f678a">Mobile platform</a></li><li><a href="#b2d31969-ca4c-11e5-a3f7-0050569f678a">Library updates
</a></li><li><a href="#b2d3196a-ca4c-11e5-a3f7-0050569f678a">Transition from the previous version to the version 8.3.9</a></li></ul><h2><a name="b2d31962-ca4c-11e5-a3f7-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.9" class="compat tag_2 tag_1"><td><a name="e6c14d21-ca4c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.3.8</span><span class="interface"> </span>is added to the list of available values of the <span class="interface">Compatibility mode</span> property.</td><td>Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, 8.3.6, and 8.3.7.</td><td>In version 8.3.9 you can run configurations created in version 8.3.8 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.9 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also gives you the option to use version 8.3.8 for working with the infobase even after the transition to version 8.3.9. You can use this option both before and after removing the compatibility mode (in the latter case you have to turn the compatibility mode back on).</td></tr><tr title="Версия 8.3.9" class="tag_38 tag_69"><td><a name="62aa84bf-e9c9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>In configuration extensions, the option to adopt the following objects is implemented:<ul><li>Common modules</li><li>Object modules for all object types</li><li>Manager modules for all object types</li><li>Session module</li><li>Managed application module</li><li>External connection module</li><li>Command modules</li></ul><p>The option to adopt ordinary form modules and ordinary application modules is not available.Therefore, you can adopt any module except for modules that are used solely in ordinary applications.</p><p>The following operations are now available:</p><ul><li>Call any methods of the extended module from the extending module</li><li>Add event handlers to adopted modules of abovementioned types</li></ul><p>Export methods and variables of the extended module form the uniform context of the extended module.</p><p>Adopted form modules are now handled differently.</p><p>You have the option to allow or deny extending all modules of abovementioned types (the <span class="interface">all module extensions</span> security profile property). You have the option to provide a list of modules where extension is allowed (the<span class="interface"> Modules available for extension </span>property) or where extension is denied (the <span class="interface">Modules not available for extension </span>property).</p><p>You have the option to create common modules in configuration extensions.</p><p>For <span class="term">ISecurityProfile</span> object, the following properties are implemented: <span class="term">AllModulesExtension</span>, <span class="term">ModulesAvailableForExtension</span>, and <span class="term">ModulesNotAvailableForExtension</span> (software administration of server clusters based on COM objects).</p><p>For <span class="term">ISecurityProfile</span> interface, the following methods are implemented: <span class="term">getAllModulesExtension()</span>, <span class="term">setAllModulesExtension()</span>, <span class="term">getModulesAvailableForExtension()</span>, <span class="term">setModulesAvailableFo</span><span class="term">rExtension()</span>, <span class="term">getModulesNotAvailableForExtension()</span>, and <span class="term">setModulesNotAvailableForExtension()</span> (Java interface for server administration).</p><p>In the server cluster command-line utility (<span class="interface">rac</span>), for the <span class="term">profile</span> command, the following parameters are implemented: <span class="term">all</span><span class="term">-</span><span class="term">module</span><span class="term">s-</span><span class="term">extension</span>, <span class="term">modules</span><span class="term">-available-for-extension</span>, and <span class="term">modules</span><span class="term">-</span><span class="term">not</span><span class="term">-available-for-extension</span>.</p></td><td>The option to adopt modules was not available, except for form modules. The option to create common modules in configuration extensions was not available.<p>Adopted form modules were handled differently.</p><p>The option to specify which modules can be extended was not available.</p></td><td>The configuration extensions feature now provides the option to extend all 1C:Enterprise script modules, except for those used solely in ordinary applications.<p>New security profile options related to configuration extensions.</p></td></tr><tr title="Версия 8.3.9" class="tag_65 tag_129 tag_38 tag_6"><td><a name="f216205e-e9e9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br><a href="#" onclick="onTagClick(this, 129); return false;">OData interface</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The option to manage session lifetime when using Internet services and the standard OData interface is implemented:<ul><li>Automatic reuse of the current session when a new request comes from the same user.</li><li>Session lifetime management using HTTP request headers.</li></ul><p>For web services and HTTP services, the <span class="term">ReuseSessions </span>and <span class="term">SessionMaxAge</span><span class="term"> </span>properties are implemented. If a web service or HTTP service is a native configuration extension object, these properties are read-only.</p><p>The following additions to the <span class="interface">default.vrd</span> file are implemented:</p><ul><li><span class="term">&lt;standardOData&gt;</span> element, which is subordinate to <span class="term">&lt;point&gt;</span> element.</li><li><span class="term">reuseSessions</span>, <span class="term">sessionMaxAge</span>, <span class="term">poolTimeout</span>, and <span class="term">poolSize</span> attributes for <span class="term">&lt;point&gt;</span> and <span class="term">&lt;service&gt;</span> elements.</li></ul><p>The <span class="term">enableStandardOData</span> attribute of the <span class="term">&lt;point&gt;</span> element is deprecated.</p><p>If a web service or an HTTP service is a native configuration extension object and it is either not published in the <span class="interface">default.</span><span class="interface">vrd </span>file or published without the session reuse option, session reuses are not available for that service.</p><p>A server cluster service that manages the automatic pool of reused sessions is implemented. The service name is SessionReuseService (<span class="interface">Session reuse service</span>).</p></td><td>This feature was not provided. A new session was created for each Internet service call and each standard OData interface query.</td><td>Improved performance of Internet services and the standard OData interface.</td></tr><tr title="Версия 8.3.9" class="tag_111"><td><a name="45ce28f3-e9fa-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 111); return false;">Formatted documents</a>.<br></td><td>The behavior of the <span class="interface">Tab </span>key is changed:<ul><li>If a text is selected or the cursor is located at the beginning of a paragraph, pressing <span class="interface">Tab </span>increases the indent.</li><li>Otherwise pressing <span class="interface">Tab </span>adds a tab character. </li></ul><p>The <span class="term">FormattedDocumentBookmark </span>object is linked to a character within a paragraph, not to a character position. If a text is changed, the bookmark position better matches its original position.</p></td><td>Pressing <span class="interface">Tab </span>always increased the indent. The <span class="term">FormattedDocumentBookmark </span>object was linked to a character position within a paragraph.</td><td>Formatted document behavior better meets user expectations.</td></tr><tr title="Версия 8.3.9" class="tag_49"><td><a name="fc0ab7db-ea92-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 49); return false;">Binary data</a>.<br></td><td>Tools for operations with binary data are implemented. They provide the following options:<ul><li>Specifying byte order</li><li>Operations with memory buffer that stores binary data</li><li>File operations where files are treated as binary data</li><li>Byte-by-byte data access</li><li>Reading and writing some data types (String and Number).</li></ul><p>The following objects are implemented: <span class="term">BinaryDataBuffer</span>, <span class="term">Stream</span>, <span class="term">FileStream</span>, <span class="term">MemoryStream</span>, <span class="term">DataReader</span>, <span class="term">DataWriter</span>, <span class="term">ReadData</span><span class="term">Result</span>, <span class="term">FileStreamsManager</span>.
The <span class="term">BinaryData.Size</span><span class="term">()</span> method is now available in the web client.</p><p>For the <span class="term">BinaryData</span><span class="term">.Write</span><span class="term">()</span> method, the option to write data to a stream is implemented.</p><p>The <span class="term">OpenStreamForRead</span><span class="term">()</span> method is implemented, it opens a stream for reading binary data specified in the <span class="term">BinaryData</span> object.</p></td><td>These options were not provided. The only available options were reading files from disk and writing files to disk without any means to perform any other operations with those files.</td><td>Extented capabilities for operations with binary data.</td></tr><tr title="Версия 8.3.9" class="tag_79"><td><a name="5d565f8f-ea9c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>Support of vector images in SVG format is implemented. The <span class="term">PictureFormat</span><span class="term">.</span><span class="term">SVG</span> system enumeration value is implemented. The picture editor in Designer does not support editing pictures that have SVG format. The specifics of SVG format support are described in the documentation.</td><td>This feature was not provided.</td><td>Extended list of supported picture formats. You have the option to use scalable pictures that can be displayed in areas of any size.</td></tr><tr title="Версия 8.3.9" class="tag_10"><td><a name="7f062700-eaba-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>For the <span class="term">/regserver</span> client application command-line option (registration of COM objects), the following optional parameters are implemented: <ul><li><span class="term">-AllUsers</span>. Perform registration for all computer users.</li><li><span class="term">-CurrentUser</span>. Perform registration for the current user.</li><li><span class="term">-Auto</span>. Automatically select registration mode based on the user rights, without displaying any questions.</li></ul><p>The behavior of the <span class="term">/regserver</span> option without parameters is not changed.</p></td><td>When a client application was started with the <span class="term">/regserver</span> command-line option (registration of COM objects), it attempted to perform the registration for all users. If the current user did not have the rights for this, they were prompted to confirm the registration for the current user.</td><td>Simpler usage of the <span class="term">/regserver</span> command-line option in 1C:Enterprise batch startup mode.</td></tr><tr title="Версия 8.3.9" class="tag_56"><td><a name="6337a0fb-eb82-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>Support of Canonical XML 1.1 specification is implemented. <p>The <span class="term">ConversionToCanonicalXML</span> object is implemented. For the <span class="term">XMLCanonicalizationType</span> system enumeration, the following values are implemented: <span class="term">XMLCanonicalization1</span><span class="term">_1</span> and <span class="term">XMLCanonicalization1</span><span class="term">_1</span><span class="term">WithComments</span>.</p><p>The <span class="term">XMLCanonicalizingWriter</span> and <span class="term">DOMCanonicalization</span> objects are deprecated. These objects do not support Canonical XML 1.1 specification.</p></td><td>Only Canonical XML 1.0 specification was supported.</td><td>Extended capabilities for integration with third-party systems.</td></tr><tr title="Версия 8.3.9" class="tag_19 tag_10"><td><a name="a9d13d3b-eb8c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The option to attempt the restoration of database structure from Designer batch mode command line is implemented. The <span class="term">/IBRestoreIntegrity</span> Designer command-line option is implemented.<p>Running Designer with the <span class="term">/IBRestoreIntegrity</span> parameter is recommended if a previous database configuration update (performed either interactively or in batch mode) have not been completed successfully because of unexpected Designer shutdown or power outage.</p></td><td>This feature was not provided.</td><td>Improved infobase fault tolerance in scenarios that include database configuration update.</td></tr><tr title="Версия 8.3.9" class="tag_95 tag_39"><td><a name="a3b56cdb-ec19-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>Recording events related to predefined data restructuring to the event log is implemented. This includes the following events:<ul><li><span class="interface">Infobase</span><span class="interface">.Set predefined data update</span></li><li><span class="interface">Infobase</span><span class="interface">.Predefined data update</span></li><li><span class="interface">Data.</span><span class="interface">Set predefined data initialization</span></li><li><span class="interface">Data</span><span class="interface">.Initialize p</span><span class="interface">redefined data</span></li><li><span class="interface">Data</span><span class="interface">.Add </span><span class="interface">predefined data</span></li><li><span class="interface">Data</span><span class="interface">.</span><span class="interface">Modify </span><span class="interface">predefined data</span></li><li><span class="interface">Data</span><span class="interface">.</span><span class="interface">Delete </span><span class="interface">predefined data</span></li><li><span class="interface">Data.Initialize</span><span class="interface"> predefined data, data not fou</span><span class="interface">nd</span></li></ul></td><td>This feature was not provided.</td><td>Simplified diagnostics of predefined data issues.</td></tr><tr title="Версия 8.3.9" class="compat tag_26 tag_1"><td><a name="a658f8bb-ec24-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The export of spreadsheet documents to Microsoft Office OpenXML (Microsoft Word 2007- 2010) format includes the export of pictures stored in spreadsheet document cells.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The export of spreadsheet documents to Microsoft Office OpenXML (Microsoft Word 2007- 2010) format did not include the export of pictures stored in spreadsheet document cells.</td><td>Spreadsheet documents exported to Microsoft Word better match the original spreadsheet documents.</td></tr><tr title="Версия 8.3.9" class="tag_37"><td><a name="35bb0fc3-ec2c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The following algorithms can be used together with TLS protocol: GOST R 34.10-2001, GOST R 34.10-94, GOST R 34.11-94, and GOST 28147-89.<p>GOST R 34.10-2012 and GOST R 34.11-2012 algorithms are not supported.</p></td><td>This feature was not provided.</td><td>Internet services that use the listed GOST algorithms together with TLS protocol are now supported.</td></tr><tr title="Версия 8.3.9" class="tag_129"><td><a name="630806c9-ef5a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 129); return false;">OData interface</a>.<br></td><td>For the standard OData interface, the option to get the following data is implemented:<ul><li>Predefined data item flag and name.</li><li>Data attribute presentations. The <span class="term">____Presentation</span> field name suffix is used for getting presentations. Presentation fields are only available for use in the <span class="term">$select</span> operator and only if you specify them explicitly.</li><li>Specific attributes of tabular sections or record sets (in the <span class="term">$select </span>operator).</li></ul></td><td>These features were not provided.</td><td>Extended capabilities of the standard OData interface.</td></tr><tr title="Версия 8.3.9" class="tag_129"><td><a name="cb2b473d-ef6b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 129); return false;">OData interface</a>.<br></td><td>For queries to the standard OData interface, support of the <span class="term">$expand</span> operator is implemented. This gives you the option to include referenced entities in the response body.</td><td>This feature was not provided.</td><td>The option to get values of referenced entities together with the main query result is implemented, which eliminates the need to use a separate query for each referenced entity.</td></tr><tr title="Версия 8.3.9" class="compat tag_43 tag_1"><td><a name="9a070df7-ef6c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The following changes are made in the dynamic list query builder:<ul><li>The option to edit batch queries is implemented (the <span class="interface">Query batch</span> wizard page).</li><li>Specifying the number of selected records is not supported but disabling this query option is supported.</li><li>When the query builder is closed, it checks the query for the <span class="term">TOP </span>keyword and, if the keyword is present, reports that.</li></ul><p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The dynamic list query builder did not provide the option to edit batch queries. The option to specify the number of selected records was available but this number was never used.</td><td>The option to edit query batches using the dynamic list query builder is implemented. Better error diagnostics for dynamic list queries.</td></tr><tr title="Версия 8.3.9" class="tag_38"><td><a name="a7f741d1-f03a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The option to change access rights (including data access restrictions) in adopted roles is implemented.<p>The option to add roles to configuration extensions is implemented, this requires the use of 1C:Enterprise script. In Designer, the only operation available for such roles is deletion.</p><p>The option to apply data access restirictions added in a configuration extension to the resulting configuration is implemented through the use of security profiles (the <span class="interface">access rights extension</span> property).</p><p>For the <span class="term">ISecurityP</span><span class="term">rofile </span>object, the <span class="term">RightExtension </span>and <span class="term">RightExtensionDefinitionRoles </span>properties are implemented (for the technology of programmatic cluster administration based on COM objects).</p><p>For the <span class="term">ISecurityP</span><span class="term">rofile </span>object, the <span class="term">RightExtension </span>and <span class="term">RightExtensionDefinitionRoles </span>properties are implemented (for the Java administration server interface).</p><p>For the server cluster command-line utility (<span class="interface">rac</span>), the<span class="term"> right-extension </span>and<span class="term"> right-extension-definition-roles </span>parameters of the <span class="term">profile </span>command are implemented.</p></td><td>In configuration extensions, only the option to set access rights for native extension objects in adopted roles was available. The option to change rights in adopted roles was not available.</td><td>Significant improvements for access right management in configuration extensions.</td></tr><tr title="Версия 8.3.9" class="tag_38 tag_20"><td><a name="e57b84c9-f03e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The following options to check the applicability of a configuration extension without running an applied solution with this extension are implemented:<ul><li>The <span class="interface">Check applicability </span>command in the <span class="interface">Configuration extensions</span> window</li><li>1C:Enterprise script methods</li><li>Designer batch mode option</li></ul><p>When a client application is started, extension compatibility issues are no longer displayed in the message window. Instead, they are added to the information for technical support (which is available from the <span class="interface">About 1C:Enterprise </span>window). If any compatibility issues are encountered, a warning dialog box is also displayed, with a link to the full list of issues.</p><p>For the <span class="term">ConfigurationExtensions</span> object, the <span class="term">CheckCanApplyAll</span><span class="term">()</span> and <span class="term">Get</span><span class="term">SessionApplicationIssuesInformation</span><span class="term">() </span>methods are implemented. For the <span class="term">ConfigurationExtension</span> object, the <span class="term">CheckCanApply</span><span class="term">()</span> method is implemented.</p><p>For Designer batch mode, the <span class="term">/CheckCanApplyConfigurationExtensions</span> command-line option is implemented.</p><p>For the <span class="interface">Configuration extension management</span> standard function, the <span class="interface">Check applicability when adding and loading extensions </span>check box is implemented.</p></td><td>These features were not provided.<p>When an extension was attached, the diagnostics messages were displayed in the message window.</p></td><td>Improved diagnostics for configuration extension attachment issues. The option to automate the diagnostics by running them in the batch mode is implemented.</td></tr><tr title="Версия 8.3.9" class="tag_39"><td><a name="2d2e1165-f360-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>When the event log is exported to an XML file, the state of predefined data update is exported as the value of the <span class="term">Data </span>field.<p>The <span class="term">PredefinedDataUpdate </span>system enumeration is now available in the thin and web clients.</p></td><td>This feature was not provided.</td><td>The event log export to an XML file is adjusted to reflect the new events.</td></tr><tr title="Версия 8.3.9" class="tag_84"><td><a name="9d933a2d-21a4-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The French localization of the client applications is available.</td><td>This feature was not provided.</td><td>1C:Enterprise is available to French-speaking users.</td></tr><tr title="Версия 8.3.9" class="tag_84"><td><a name="ee69bd22-21ab-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The Hungarian localization of the client applications is available.</td><td>This feature was not provided.</td><td>The Hungarian platform interface is available. 1C:Enterprise is available to Hungarian-speaking users.</td></tr><tr title="Версия 8.3.9" class="tag_38 tag_20"><td><a name="5cf10e2c-2f10-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The <span class="term">ConfigurationExtensionsManager</span><span class="term">.</span><span class="term">ExecuteBackgroundJobWithoutExtensions</span><span class="term">()</span> method is implemented. It runs a background job without extensions (configuration extensions available in the database are not applied in the background job session).<p>For all metadata objects, the <span class="term">ChangedByConfigurationExtensions</span><span class="term">()</span> method is implemented. It defines whether a configuration object is available in the current session.</p></td><td>This feature was not provided.</td><td>Simplified 1C:Enterprise script-based operations with configuration extensions.</td></tr><tr title="Версия 8.3.9" class="tag_19 tag_29"><td><a name="c459dd95-390e-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft SQL Server 2016 DBMS is now supported (including its Linux version).</td><td>Microsoft SQL Server 2016 DBMS was not supported.</td><td>Microsoft SQL Server 2016 DBMS is now supported.</td></tr><tr title="Версия 8.3.9" class="tag_14 tag_29"><td><a name="3ea5c79f-41d9-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>A 64-bit client application for Windows is implemented. It includes the thin client (also available as a standalone distribution kit), the thick client, and Designer. The current client application status is beta.<p>When you start a client application, the 32-bit version has priority because most of the add-ins are not yet available for the 64-bit version of 1C:Enteprise platform. Automatic client application updates also install 32-bit versions (provided that the 32-bit versions are available in the distribution kit directories).
The 64-bit client installer is similar to the 32-bit client installer.</p><p>We recommend that you do not install both 64-bit 1C:Enterprise server and applications from the full 64-bit 1C:Enterprise distribution kit on a single computer.</p></td><td>Only 32-bit versions of Windows client applications (including Designer) were available.<p>1C:Enterprise server was the only 1C:Enterprise component that had a 64-bit version.</p></td><td>Support of 64-bit Windows versions is implemented.<p>Issues caused by insufficient memory for operations with large configurations (such as comparing and merging configurations) are eliminated.</p></td></tr><tr title="Версия 8.3.9" class="tag_82 tag_117"><td><a name="d1a877f3-5faf-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>Before you start infobase verification and repair in the interactive mode, 1C:Enterprise displays a recommendation to create an infobase backup.<p>Infobase restructuring and infobase verification and repair now include a check for the following: the table of accounting register extra dimension values contains records that do not have matching records in the main accounting register table (lost extra dimensions). During the repair, lost extra dimensions are deleted from the table of accounting register extra dimension values if the following conditions are met:
</p><ul><li>The <span class="interface">Verify and repair </span>mode is selected.</li><li>The <span class="interface">Check logical infobase integrity</span> option is selected.</li></ul><p>During the restructuring, the check is performed if any of the following entities change:</p><ul><li>The totals splitting flag</li><li>The set of recorders</li><li>The maximum number of extra dimensions</li><li>The type of characteristic value in a chart of characteristic types that is used to specify extra dimensions for a chart of accounts.</li></ul><p>If lost extra dimensions are found during the restructuring, the restructuring is stopped and 1C:Enterprise displays a recommendation to perform infobase verification and repair. </p><p>The check for lost extra dimensions during the infobase verification and repair is implemented. If extra dimensions are lost, it is recommended that you restore the infobase from a backup. The check is performed if the following conditions are met:</p><ul><li>The <span class="interface">Verify and repair </span>mode is selected.</li><li>The following options are selected: <span class="interface">Check logical infobase integrity</span>, <span class="interface">Check referential infobase integrity</span>, <span class="interface">Recalculate totals</span>, and <span class="interface">Restructure infobase tables</span>.</li></ul></td><td>The diagnostics of extra dimension inconsistencies was insufficient.</td><td>Diagnostics and repair of accounting register logical integrity issues that can result in data losses is implemented.</td></tr><tr title="Версия 8.3.9" class="tag_10"><td><a name="7345d404-79bd-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The rules for generation of application and shortcut names displayed in the Windows Start menu are modified. The new name template is <span class="interface">Application name (full version number)</span>.<p>In Windows version 8 or later, the <span class="interface">1C:En</span><span class="interface">terprise 8</span><span class="interface"> </span>folder contains all installed applications (and shortcuts) with their version numbers.</p><p>In Windows version 7 or earlier, the <span class="interface">1C:Enterprise 8</span> folder contains folders for each version number. Each of these folders contains all installed applications (and shortcuts) for a specific version, with their names generated according to the abovementioned rule.</p></td><td>The names of installed applications (and shortcuts) did not include the full system version number.</td><td>Simplified navigation in the Start menu on Windows version 8 and later. Application names now contain full version numbers.</td></tr><tr title="Версия 8.3.9" class="tag_82 tag_27"><td><a name="befed7e3-b616-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>The option to create an accounting register record that only affects the opening balance of a single period and does not affect the closing balance of the previous period is implemented. The implementation is based on the new "period adjustment" concept. A period adjustment is a number that represents the number of time intervals within a single second. The maximum number of intervals is 1000. If a record belongs to any period adjustment interval, the record does not affect the closing balance of a period but affects the opening balance of the next period and does not affect the turnovers of both periods. A register record that belongs to a period adjustment interval only affects turnovers if the turnover period includes the entire point in time of that register record. Now the point in time can inlcude not only the date, time, and recorder, but also a period adjustment. <p>For the accounting register configuration object, the <span class="interface">Period adjustment length </span>property is implemented. If this property is set to 0, the register does not use period adjustments. </p><p>The <span class="term">PeriodAdjustment </span>property is implemented for <span class="term">AccountingRegisterRecord</span> and <span class="term">AccountingRegisterSelection</span><span class="term"> </span>objects. This property is also available in the main accounting register table, the extra dimensions table, and the virtual table of register records with extra dimensions. </p><p>The <span class="term">PeriodAdjustm</span><span class="term">ent </span>value is implemented for the <span class="term">Periodi</span><span class="term">city </span>parameter of the following virtual tables of accounting registers: <span class="term">Turnovers</span>, <span class="term">DrCrTurnovers</span>, and <span class="term">BalanceAndTurnovers</span>.</p><p>The <span class="term">PointInTimeWithPeriodAdjustment </span>object is implemented.</p><p>The XML dump format version is changed.</p><p>If a configuration contains at least one accounting register with period adjustment enabled (the value of the <span class="interface">Period adjustment length </span>property is not 0), this makes the infobase incompatible with the earlier 1C:Enterprise versions, including earlier builds of 1C:Enterprise 8.3.9. When you attempt to open such an infobase with 1C:Enterprise version 8.3.9.2015 or earlier, 1C:Enterprise displays the message <span class="interface">Configuration structure is incompatible with the current program version</span> and shuts down.</p><p>To restore the compatibility, you have to delete all of the accounting registers with period adjustment, or set their <span class="interface">Period adjustment length </span>to 0.</p></td><td>This feature was not provided.<p>The option to create an accounting register record that only affected the opening balance of a single period and did not affect the closing balance of the previous period was not available.</p></td><td>You can implement certain operations related to opening balance corrections at period boundaries.</td></tr><tr title="Версия 8.3.9" class="tag_19 tag_29"><td><a name="48bc83a4-e3b0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of Oracle Database version 11.2.0.4 (Windows) is implemented.</td><td>This Oracle Database version was not supported.</td><td>Extended list of supported Oracle Database versions.</td></tr></table><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b2d31963-ca4c-11e5-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.9" class="compat tag_14 tag_1"><td><a name="d3156deb-ec26-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>All of the common report forms use the following help topic priorities:<ul><li>Report help </li><li>Form help </li><li>Report form help provided by the platform</li></ul><p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>Common report froms used the following help topic priorities:<ul><li>Form help</li><li>Report help </li><li>Report form help provided by the platform</li></ul></td><td>Help topics are displayed in more logical order.</td></tr><tr title="Версия 8.3.9" class="tag_96 tag_14"><td><a name="8b0c4cef-ec41-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>For thin client running on Windows operating system, touch screen support is implemented.<p>Support of scrolling with 2-finger gestures in all directions is implemented for all controls that have scroll bars.</p><p>The effect of 1-finger gestures depends on control type:</p><ul><li>Horizontal gesture:</li><ul><li>Scrolling in spreadsheet documents, tables, or forms</li><li>Selection in text documents, multiline text boxes, formatted documents, planner fields, and HTML document fields</li><li>Selection or dragging in graphical and geographical schemas</li></ul><li>Vertical gesture:</li><ul><li>Selection or dragging in geographical schemаs</li><li>Scrolling in other form controls that support vertical scrolling</li></ul></ul><p>The tap detection area is expanded for the following controls:</p><ul><li>Check boxes in form tables</li><li>Buttons that expand or collapse tree branches in form tables</li><li>Buttons that move through hierarchical lists in form tables</li><li>Hyperlinks in command bars</li><li>Buttons with hidden borders</li><li>Cells in form field extensions for period fields</li></ul><p>For graphical schemas, support of scaling using the scaling gesture is implemented.</p><p>For tapping form buttons and command bar buttons, a visual effect is implemented.</p></td><td>The touch screen support was limited.</td><td>Improved 1C:Enterprise usability for touch monitors.</td></tr><tr title="Версия 8.3.9" class="compat tag_26 tag_1"><td><a name="23e838e6-ef50-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In spreadsheet documents, if a search string can be converted to a number, 1C:Enterprise determines the number of digits in that number. Then it searches exactly for the specified number, without further simplifications or conversions. The search does not ignore strings with leading zeros.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>In spreadsheet documents, for searches by number, 1C:Enterprise did not determine the number of digits in that number. Strings with leading zeros were not converted to numbers.</td><td>Better algorithm for searching spreadsheet documents for numeric values.</td></tr><tr title="Версия 8.3.9" class="tag_28"><td><a name="f287bd73-0d55-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>File system extension and cryptography extension are compatible with Mozilla Firefox version 51 and later. The extensions are automatically updated first time they are accessed (after the platform update).</td><td>File system extension and cryptography extension were not compatible with Mozilla Firefox version 51 and later.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b2d31964-ca4c-11e5-a3f7-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.9" class="tag_20"><td><a name="8b48d52f-e9bf-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The performance of the following Designer operations is improved:<ul><li>Module check</li><li>Configuration check</li></ul></td><td>The performance of module and configuration checks was insufficient.</td><td>Improved usability for developers of large applied solutions.</td></tr><tr title="Версия 8.3.9" class="tag_69"><td><a name="1dc1d931-e9c6-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The performance of 1C:Enterprise script execution is slightly improved in the thin and thick client applications.</td><td>The performance of 1C:Enterprise script execution in client applications was insufficient.</td><td>Improved performance of 1C:Enterprise script execution in the thin and thick client applications.</td></tr><tr title="Версия 8.3.9" class="tag_36"><td><a name="64673c9a-eab9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The performance of updating value table column cells in columns that are not a part of any value table index is improved.</td><td>Redundant rebuilding of value table indexes was performed in the event of updating a cell in a column that was not a part of any value table index.</td><td>Improved performance for bulk value changes in columns that are not part of any value table index.</td></tr><tr title="Версия 8.3.9" class="tag_105 tag_6"><td><a name="3741158e-ec16-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The following operations that are performed during the creation of an initial infobase image in client/server mode are optimized: reading accumulation register and information register record sets, and reading calculation register record sets that do not feature action period.<p>The time required to create an initial image of a client/server infobase is significantly reduced.</p></td><td>The performance of creation of an initial image in a client/server infobase was insufficient.</td><td>Improved performance of infobase preparation for new distributed infobase nodes.</td></tr><tr title="Версия 8.3.9" class="tag_86 tag_20"><td><a name="10018f1f-ec17-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Improved performance of opening the configuration command interface editor form.</td><td>The performance of opening the configuration command interface editor form was insufficient.</td><td>Better usability of editing the configuration command inerface.</td></tr><tr title="Версия 8.3.9" class="tag_19 tag_6"><td><a name="dfc638ca-ec20-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The algorithm of 1C:Enteprise server cluster operations with PostgreSQL DBMS is modified. This reduces PostgreSQL memory usage.<p>If a 1C:Enterprise server cluster connection to PostgreSQL DBMS is idle for 30 minutes, it is released.</p></td><td>The algorithm of 1C:Enteprise server cluster operations with PostgreSQL DBMS caused increased PostgreSQL memory usage.<p>1C:Enterprise server cluster did not release idle connections to PostgreSQL DBMS.</p><p>
</p></td><td>Reduced PostgreSQL memory usage for operations with 1C:Enterprise server cluster.</td></tr><tr title="Версия 8.3.9" class="tag_20"><td><a name="1640a3f0-ec23-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Infobase configuration update is optimized. Configuration comparison in scenarios where objects are mapped by their names is optimized.</td><td>The performance of infobase configuration update was insufficient.</td><td>Improved performance of configuration updates.</td></tr><tr title="Версия 8.3.9" class="tag_19"><td><a name="fd8e8318-ec3e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Temporary table operations are optimized in scenarios that use PostgreSQL DBMS.</td><td>The performance of temporary table operations in scenarios that used PostgreSQL DBMS was insufficient.</td><td>Improved performance in multiuser mode in scenarios that use PostgreSQL.</td></tr><tr title="Версия 8.3.9" class="tag_65"><td><a name="571e1978-ec3f-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>Sending large files (tens and hundreds of megabytes) over HTTP services is optimized.</td><td>The performance of sending large files (tens and hundreds of megabytes) over HTTP services was insufficient.</td><td>Improved performance of sending large files over HTTP services.</td></tr><tr title="Версия 8.3.9" class="tag_19"><td><a name="f9e42252-ec4a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Optimized temporary table operations in scenarios that use Microsoft SQL Server and include high load on 1C:Enterprise and active usage of temporary tables. Pauses during the closing of DBMS connections are eliminated.</td><td>The performance of temporary table operations in scenarios that used Microsoft SQL Server and included high load on 1C:Enterprise and active usage of temporary tables was insufficient.</td><td>Improved performance in multiuser mode in scenarios that use Microsoft SQL Server.<p>
</p></td></tr><tr title="Версия 8.3.9" class="tag_19"><td><a name="280d3aac-ed27-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>In the file mode, queries are optimized for scenarios where an applied solution has separators but actually contains a single data area.<p>To apply this optimization to an existing infobase, perform infobase verification and repair with the <span class="interface">Reindex</span><span class="interface"> </span><span class="interface">infobase tables</span> check box selected. Once the restructuring is completed, the optimization is applied to all restructured objects.</p></td><td>In the file mode, in scenarios where an applied solution had separators but actually contained a single data area, the performance of queries was insufficient.</td><td>Improved file infobase performance in scenarios where an applied solution has separators but actually contains a single data area.</td></tr><tr title="Версия 8.3.9" class="tag_20 tag_86"><td><a name="8e475a7a-ef6d-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>Reduced time of displaying changes in configuration objects that affect the configuration command interface. Such changes cause the immediate update of the active form editor, while other form editors are updated when they are activated.</td><td>Changes in configuration objects that affected the configuration command interface caused the update of all open form editors.</td><td>Improved Designer performance during the update of properties of configuration objects that affect the command interface.</td></tr><tr title="Версия 8.3.9" class="tag_111"><td><a name="190de0da-f02a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 111); return false;">Formatted documents</a>.<br></td><td>The performance of formatted documents is improved.</td><td>The performance of formatted documents was insufficient.</td><td>Improved performance of operations with large texts.</td></tr><tr title="Версия 8.3.9" class="tag_52"><td><a name="7a94d122-eaaf-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>Absorption of managed locks is implemented (when two managed locks are applied at the same time, only one will take effect). A lock that does not have all lock areas specified absorbs a lock that has more lock areas specified, provided that the values in their common areas match.<p>If lock escalation causes a conflict with other locks, the escalation is not performed and an attempt to set the requested lock is made instead. This can lead to a total of more than 100 000 locks in a single area.</p><p>In scenarios where a single transaction uses a large number of managed locks with slight differences (for example, a single dimension varies), it is recommended that you set a single managed lock where the value of that dimension is not set.</p></td><td>Lock absorption was not performed. If lock escalation caused a conflict with other locks, the transaction that attempted to escalate the lock was canceled.</td><td>Reduced number of locks and reduced amount of memory used by the cluster manager.<p>Improved system reliability in scenarios with large numbers of simultaneous locks.</p></td></tr><tr title="Версия 8.3.9" class="tag_19 tag_121"><td><a name="77b54bf0-f038-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 121); return false;">Calculation registers</a>.<br></td><td>When deleting records belonging to the actual action period, recording of register sets of calculation registers that support actual action period is performed within several queries, which reduces the chance of escalating the lock to the table level. This does not increase the record set execution time.</td><td>When deleting records belonging to the actual action period, recording of register sets of calculation registers that supported actual action period was performed within a single query, which could cause lock escalation to the table level.</td><td>Reduced chance of table lock, which gives more options for performing parallel operations.</td></tr><tr title="Версия 8.3.9" class="tag_121"><td><a name="93b374cb-ef4b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 121); return false;">Calculation registers</a>.<br></td><td>The index of the actual action period table of a calculation register is complemented by the start date and end date fields, and the index is now clustered. This reduces the chance of lock escalation to the table level when writing record sets of calculation registers that support action period. <p>For the chart of calculation types table that stores serial numbers of calculation type displacements, a nonunique index by displacement number is implemented. As a result, simultaneous editing of a single chart of calculation types in different data areas of a separated infobase never requires waiting for lock releases.</p><p>To apply this optimization to existing infobases, perform the infobase verification and repair operation with the <span class="interface">Restructure infobase tables </span>option selected.</p><p>
</p></td><td>The index of the actual action period table of a calculation register did not include the start date and end date fields, and the index was not clustered.<p>For the chart of calculation types table that stored serial numbers of calculation type displacements, a nonunique index by displacement number was not available.</p></td><td>Improved calculation register performance in large and separated databases.<p>In large databases and especially separated databases, reduced number of table-level locks for the following tables: actual action period table of a calculation register and table that stores serial numbers of calculation type displacements.
</p></td></tr><tr title="Версия 8.3.9" class="tag_115 tag_20"><td><a name="a5b7c1b3-fff9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The first opening of managed form editor in Designer is faster.</td><td>The first opening of managed form editor in Designer took significant time.</td><td>Reduced waiting time in managed form development.</td></tr><tr title="Версия 8.3.9" class="tag_16"><td><a name="80171962-12a5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>Faster writing of information register record sets that have slice first or slice last options enabled.<p>Faster execution of <span class="term">SliceFirst()</span> and <span class="term">SliceLast()</span> information register manager methods.</p></td><td>The performance of writing information register record sets that had slice first or slice last options enabled and the performance of <span class="term">SliceFirst()</span> and <span class="term">SliceLast()</span> information register manager methods was insufficient.</td><td>Improved performance of information registers with slice first or slice last options enabled.</td></tr><tr title="Версия 8.3.9" class="tag_96 tag_115 tag_104"><td><a name="43c3ad7a-23f2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>The performance of <span class="term">RefreshInterface</span><span class="term">()</span>, <span class="term">SetInterfaceFunctionalOptionParameters</span><span class="term">()</span>, and <span class="term">SetFormFunctionalOptionParameters</span><span class="term">()</span> methods is improved. Delays introduced by these methods in applications with multiple simultaneous user connections are eliminated.</td><td>The performance of <span class="term">RefreshInterface</span><span class="term">()</span>, <span class="term">SetInterfaceFunctionalOptionParameters</span><span class="term">()</span>, and <span class="term">SetFormFunctionalOptionParameters</span><span class="term">()</span> methods was insufficient. The performance was reduced in applications that called these methods in scenarios with multiple simultaneous user connections.</td><td>Streamlined operations in applications that use functional options.</td></tr><tr title="Версия 8.3.9" class="tag_115 tag_128"><td><a name="51ed47ff-6471-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 128); return false;">Mobile applications</a>.<br></td><td>In the mobile platform, the performance of operations with large spreadsheet documents is improved.</td><td>In the mobile platform, the performance of operations with large spreadsheet documents was insufficient.</td><td>Improved performance of operations with large spreadsheet documents on mobile devices.</td></tr><tr title="Версия 8.3.9" class="tag_19"><td><a name="7c1b8dd6-9531-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The performance degradation of Microsoft SQL Server 2014 caused by interaction between 1C:Enterprise server and Microsoft SQL Server 2014 is eliminated. 1C:Enterprise server now forces setting TRACE FLAG 4199 for each Microsoft SQL Server 2014 connection. To be able to set the flag, the account that the 1C:Enterprise server uses to connect to the DMBS must have administrator rights.<p>If TRACE FLAG 4199 is set for the entire database, 1C:Enterprise server does not set it for each connection.</p></td><td>In some scenarions interaction between 1C:Enterprise server and Microsoft SQL Server 2014 reduced Microsoft SQL Server 2014 performance. 1C:Enteprise server did not force setting TRACE FLAG 4199 and did not check whether this flag was set for the entire database.</td><td>In some scenarions the performance of operations involving Microsoft SQL Server 2014 is improved.</td></tr><tr title="Версия 8.3.9" class="tag_19"><td><a name="d14cdf59-5016-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>For PostgreSQL, reduced the overhead expenses for processing temporary tables.</td><td>For PostgreSQL, processing temporary tables took a lot of time.</td><td>For PostgreSQL, improved the performance of transactions that actively use temporary tables.</td></tr></table><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b2d31965-ca4c-11e5-a3f7-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.9" class="compat tag_37 tag_1"><td><a name="a21cdd80-e9b9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The option to choose FTPES for communication with FTP servers is implemented. For the constructor of the <span class="term">FTPConnection </span>object, the <span class="term">SecureConnectionLevel </span>property is implemented. This property defines the secure connection requirements to the FTP server.<p>If the parameters of the <span class="term">FTPConnection </span>constructor do not have the required types, an exception is thrown. This change is not implemented in 8.3.8 compatibility mode.</p></td><td>All FTP server operations were performed over FTPS.<p>If the parameters of the <span class="term">FTPConnection </span>constructor did not have the required types, an attempt to convert them to the required types was performed.</p></td><td>Extended secure connection management capabilities for FTP server operations.</td></tr><tr title="Версия 8.3.9" class="compat tag_115 tag_1"><td><a name="741e75f9-ea97-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Clicking a managed form table cell that displays a picture with a hyperlink (the<span class="term"> </span><span class="term">CellHyperlink</span><span class="term"> </span>property is set to <span class="term">True</span>) calls the <span class="term">Selection</span> event of the form table.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>Clicking a managed form table cell that displayed a picture with a hyperlink (the <span class="term">CellHyperlink</span><span class="term"> </span>property was set to <span class="term">True</span>) did not call the <span class="term">Selection</span> event of the form table.</td><td>Eliminated unexpected system behavior.<p>Unified system behavior for different object types that can be displayed in a form table.</p></td></tr><tr title="Версия 8.3.9" class="compat tag_77 tag_1"><td><a name="ed8ff3b3-eab7-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>The option to use duplex printing settings of the printer is implemented. The system enumeration value <span class="term">DuplexPrintingType.UsePrinterSettings</span> is implemented.<p>The <span class="term">DuplexPrinting </span>property of spreadsheet documents, graphical schemas, representable document batches, and text documents has the following default value:</p><ul><li><span class="term">DoNotUse</span> (for 8.3.8 compatibility mode)</li><li><span class="term">UsePrinterSettings</span> (when no compatibility mode is set and for 8.2.16 or earlier compatibility mode)</li></ul><p>Printing spreadsheet documents and representable document batches from the web client to a PDF document and saving a spreadsheet document to a PDF document transfers the <span class="term">DuplexPrinting </span>and <span class="term">PagePlacementAlternation</span> property values to the corresponding PDF document properties. If the PDF viewer software supports these properties, they are applied when the document is printed. If the PDF viewer software does not support these properties, use the print software settings or printer settings for duplex printing.</p></td><td>Duplex printing settings of the printer were ignored during the printing of spreadsheet documents, graphical schemas, representable document batches, and text documents.</td><td>Improved document printing options.</td></tr><tr title="Версия 8.3.9" class="tag_25"><td><a name="28a71d01-eab8-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When the data composition schema wizard is opened, data set fields with duplicate names are deleted, leaving only the first one.</td><td>When the data composition schema wizard was opened, duplicate data set fields were not deleted.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="tag_17"><td><a name="d7aa8226-ec21-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>Debugger exceptions that are thrown during the startup of the debug server (<span class="interface">dbgs</span>) are now saved to the technological log. The <span class="term">&lt;EXCP&gt;</span> event is used for that logging.</td><td>Debugger exceptions that are thrown during the startup of the debug server (<span class="interface">dbgs</span>) were not logged.</td><td>Better error diagnostics for the startup of the debug server (<span class="interface">dbgs</span>).</td></tr><tr title="Версия 8.3.9" class="tag_95 tag_20"><td><a name="e7fd5520-ec27-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>If the result of merging configurations would include predefined data items with duplicate names, a numeric suffix is added to the item taken from the source with lesser priority.</td><td>The result of merging configurations could include predefined data items with duplicate names.
</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="tag_69"><td><a name="96e5f3e1-ec28-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>For the <span class="term">StrTemplate</span><span class="term">()</span> method, the syntax option with a substitution token <span class="term">%(N)</span> is implemented. You can specify a substitution number in parentheses after the percent. With this syntax you can specify a number right after the substitution token in a template string.</td><td>Eliminated unexpected system behavior.</td><td>You can create template strings where the substitution token is followed by a numeric character.</td></tr><tr title="Версия 8.3.9" class="tag_20"><td><a name="f00dd8d8-ec47-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During the configuration check and refactoring, the search for calls of deprecated synchronous methods does not check the modules that cannot be executed at the client application side. In other modules the search ignores client script parts marked with preprocessor insrtructions and compilation directives.</td><td>During the configuration check and refactoring, the search for calls of deprecated synchronous methods ignored the execution context of modules and methods.</td><td>Reduced number of false warnings while searching for calls of deprecated synchronous methods during the configuration check and refactoring.</td></tr><tr title="Версия 8.3.9" class="tag_81"><td><a name="572f0740-ecf2-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>If an attempt of publishing to a web server using an account that does not have administrative rights is made:<ul><li>Designer displays a warning dialog box, providing the options to continue the operation or cancel it.</li><li>The execution of the <span class="interface">webinst</span> utility is not interrupted, but it displays a warning.</li></ul></td><td>If an attempt of publishing to a web server using an account that does not have administrative rights was made, no diagnostics was performed.</td><td>Better diagnostics for publishing to the web sever.</td></tr><tr title="Версия 8.3.9" class="tag_56"><td><a name="09d6e21e-ecfa-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>When an XDTO package is deleted, 1C:Enterprise checks whether the package is used in web services. If web services that use the package are found, a warning with a web service list is displayed.</td><td>When an XDTO package was deleted, 1C:Enterprise did not check whether the package was used in web services,</td><td>Eliminated situations where a web service stopped working due to deletion of an XDTO package.</td></tr><tr title="Версия 8.3.9" class="tag_115"><td><a name="83a90a55-ef52-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The option to set the focus to command bars that do not contain form item commands of contain commands from multiple sources using <span class="interface">Tab</span> or <span class="interface">Shift+Tab</span> is implemented.<p>In the calendar used to enter a date in a text box, selection of the current date by clicking the <span class="interface">Today </span>hyperlink is implemented.</p><p>In the thin and thick clients, in the calendar used to enter a date in a text box, selecting a date that does not belong to the current month adds this date to the text box.</p></td><td>The option to set the focus to command bars that did not contain form item commands of contained commands from multiple sources using <span class="interface">Tab</span> or <span class="interface">Shift+Tab </span>was not available.<p>In the calendar used to enter a date in a text box, clicking the <span class="interface">Today </span>hyperlink set the focus to the current day of the month in the month currently selected in the calendar. </p><p>In the thin and thick clients, selecting a date that did not belong to the current month activated the selected month in the calendar field. In the web client, this added the selected date to the text box.</p></td><td>Eliminated unexpected user interface behavior in some scenarios.<p>Unified system behavior in different client applications.</p></td></tr><tr title="Версия 8.3.9" class="tag_67"><td><a name="4eb2c4e0-11e9-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>When you store an object to a configuration repository, the repository server checks the integrity of object data. In the event of integrity violation an exception is generated and the object is not stored.</td><td>The configuration repository server did not check the integrity of stored object data.</td><td>Reduced chance of storing corrupted configuration object data to a repository.</td></tr><tr title="Версия 8.3.9" class="compat tag_73 tag_1"><td><a name="0e6bcbe2-231a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 73); return false;">Database configuration update</a>.<br></td><td>During a dynamic update, deletion of configuration objects that do not prevent the update and are absent from the new configuration is handled correctly. These objects are only deleted during the exclusive update.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>Deletion of configuration objects that did not prevent the update and were absent from the new configuration was performed immediately, during a dynamic update.</td><td>Reduced number of issues that might arise during a dynamic update if some objects were deleted from the new configuration.</td></tr><tr title="Версия 8.3.9" class="compat tag_65 tag_37 tag_1"><td><a name="3840e7e7-27d3-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td><b>This change is rolled back.</b><p>The URI string encoding (either with the <span class="term">EncodeString</span><span class="term">()</span> function or with internal platform algorithms) replaces the percent sign (<span class="interface">%</span>) with <span class="interface">%25</span><span class="interface">.</span></p><p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The URI string encoding (either with the <span class="term">EncodeString</span><span class="term">()</span> function or with internal platform algorithms) did not replace the percent sign (<span class="interface">%</span>) with <span class="interface">%25</span>. It was left "as is."</td><td>RFC 3986 recommendations for URI string encoding are implemented.</td></tr><tr title="Версия 8.3.9" class="tag_84"><td><a name="b9a83b51-27d5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>In the number-to-words conversion algorithm for Azerbaijani language, a typo is corrected. This affects the numbers beginning with "two" and "twenty."</td><td>The number-to-words conversion algorithm for Azerbaijani language had a typo. This affected the numbers beginning with "two" and "twenty."</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="tag_20"><td><a name="3c1de178-3d17-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the debugger, when a collection (for example, a value table) is being viewed in a new window, its columns are no longer sorted in alphabetical order.</td><td>In the debugger, when a collection (for example, a value table) was being viewed in a new window, its columns were sorted in alphabetical order. This behavior occurred in 1C:Enterprise versions 8.3.7 and 8.3.8.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="tag_58 tag_38"><td><a name="288e881e-5af8-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The data deleted by <span class="term">EraseInfoBaseData</span><span class="term">()</span> method now includes configuration extensions for the entire infobase or for a specific area, depending on the call parameters.</td><td>The <span class="term">EraseInfoBaseData</span><span class="term">()</span> method did not delete configuration extensions.</td><td>The <span class="term">EraseInfoBaseData</span><span class="term">()</span> method clears more data.</td></tr><tr title="Версия 8.3.9" class="tag_43 tag_6"><td><a name="77f956d4-5d48-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>In a dynamic list search box, if you enter a value that can be interpreted as a date with year specified as a 1-digit or 2-digit number, the year is converted to this century year. This prevents the error that occurs when you use Microsoft SQL Server with a zero date offset.</td><td>In a dynamic list search box, if you entered a value that could be interpreted as a date with year specified as a 1-digit or 2-digit number, the year was not converted to this century year. In 1C:Enterprise that used Microsoft SQL Server with a zero date offset, this search scenario returned an error.</td><td>The dynamic list error that occurred if a date was entered in a search box in 1C:Enterprise that used Microsoft SQL Server with a zero date offset is eliminated.</td></tr><tr title="Версия 8.3.9" class="compat tag_26 tag_1"><td><a name="0f07ddd3-5d5a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When a spreadsheet document is exported to Microsoft Excel 97 or later format, if it contains cells with multiline text that is aligned centrally and does not fit a cell, the cell is merged. It is horizontal merging that spreads equally to both sides of the cell so that the entire text fits the new merged cell. The columns overlapped by the left and right borders of the merged cell are split into two columns.<p>The resulting document in Microsoft Excel format better matches the original document.</p><p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>When a spreadsheet document was exported to Microsoft Excel 97 or later format, if it contained cells with multiline text that were aligned centrally and did not fit the cell, such cells were not merged.</td><td>When a spreadsheet document is exported to Microsoft Excel format, the resulting document better matches the original document.</td></tr><tr title="Версия 8.3.9" class="tag_20"><td><a name="f7387378-6ab1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>If programmatic access to Microsoft Internet Explorer browser clipboard is disabled by the <span class="interface">Allow P</span><span class="interface">rogrammatic clipboard access </span>security option, an attempt to use the <span class="interface">Copy </span>command of the Syntax Assistant context menu results in a notification that the clipboard is not available, which includes a workaround recommendation (use a keyboard shortcut).</td><td>If the <span class="interface">Allow P</span><span class="interface">rogrammatic clipboard access</span> security option in Microsoft Internet Explorer was disabled, the <span class="interface">Copy </span>command of the Syntax Assistant context menu did not work.</td><td>Better diagnostics of unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="compat tag_115 tag_1"><td><a name="d641f5cd-6ab4-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For groups with titles that display data, the support of <span class="term">Format </span>property in both interface modes (<span class="interface">Taxi </span>and <span class="interface">Version 8.2</span>) is implemented.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>For groups with titles that display data, the <span class="term">Format </span>property was not supported in some interface modes. This property had some implementation differences between the thin and web clients.</td><td>Uniform behavior of the thin and web clients. Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="tag_20"><td><a name="473f78a0-6acf-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The option to update configurations that include constant forms using update (<span class="interface">.cfu</span>) files is restored.<p>The option to update configurations using update (<span class="interface">.cfu</span>) files is implemented for scenarios where only the <span class="interface">Use always </span>flag in constant forms was changed.</p></td><td>In some scenarios, if the <span class="interface">Use always </span>flag in a constant form was changed in a new configuration, this caused configuration update issues.</td><td>Eliminated the issues that appeared during the update of configurations that included constant forms with update (<span class="interface">.cfu</span>) files.</td></tr><tr title="Версия 8.3.9" class="tag_20"><td><a name="37af4115-b090-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>
<p>If the size of the file that stores new and changed objects, which is created during the generation of a <span class="interface">.cfu </span>update file, exceeds 2 GB, the update file is generated in the new format. If you are creating the update file manually, you get a notification about the new format in a dialog box. If you are creating the update file in batch mode, the notificaton is added to the service message file (<span class="interface">/out</span> comand-line option).</p><p>Update files that have new format can only be used in 1C:Enterprise versions 8.3.9.2033 and later.</p><p>If you attempt to use an update file in an earlier 1C:Enterprise version, you get a message about incorrect data storage format.</p><p>You can use 1C:Enterprise versions 8.3.9.2033 and later to apply any updates, regardless of their file format.</p></td><td>If the size of the file that stored new and changed objects, which was created during the generation of a <span class="interface">.cfu </span>update file, exceeded 2 GB, the update file could not be generated. </td><td>1C:Enteprise supports very large update files (<span class="interface">.cfu</span>).</td></tr><tr title="Версия 8.3.9" class="tag_77"><td><a name="10c0932c-b093-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>The <span class="term">RepresentableDocumentBatch</span><span class="term">.</span><span class="term">Print</span><span class="term">()</span> method splits batches into multiple jobs (in all application types except for the web client). It uses the document batch properties, such as the printer, page orientation, or duplex printing, to generate the jobs (and split document batches).</td><td>The <span class="term">RepresentableDocumentBatch</span><span class="term">.</span><span class="term">Print</span><span class="term">()</span> method printed the entire document batch as a single job (in all application types except for the web client). This might cause issues when the documents were to be printed on different printers or with different print settings because jobs always apply the same settings to all its documents.</td><td>Eliminated document batch printing issues caused by differences of document print settings (such as the printer, page orientation, or duplex printing).</td></tr><tr title="Версия 8.3.9" class="tag_131"><td><a name="2388c3a4-b096-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 131); return false;">Operating system</a>.<br></td><td>1C:Enterprise behavior changed in scenarios that involve switching the computer to sleep mode. 1C:Enterprise prevents switching to the sleep mode if:<ul><li>It uses a hardware protection key</li><li>It runs in file mode and its database file is located on a network resource</li></ul></td><td>1C:Enterprise prevented switching to sleep mode if: <ul><li>It used a hardware protection key</li><li>It ran in file mode and its database file was located on a network resource</li><li>It ran in client/server mode.</li></ul></td><td>Power saving schemes applied when 1C:Enterprise runs are changed.</td></tr><tr title="Версия 8.3.9" class="tag_93"><td><a name="ef625835-b613-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 93); return false;">Infobase operations</a>.<br></td><td>Dumping an infobase to a <span class="interface">.dt</span> file is not interrupted if any issues related to the internal infobase structure are encountered.</td><td>Dumping an infobase to a <span class="interface">.dt</span> file was interrupted if any issues related to the internal infobase structure were encountered.</td><td>Minor infobase data structure issues, which do not impact 1C:Enterprise functionality, no longer block dumping infobases to files.<p>
</p></td></tr><tr title="Версия 8.3.9" class="tag_57"><td><a name="3d309ea0-8b09-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 57); return false;">JSON support</a>.<br></td><td>Improved reliability of JSON operations.</td><td>JSON operations might cause unexpected shutdown.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="tag_6"><td><a name="4bebea5c-deea-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When the <span class="interface">Secure connection</span> cluster property value is changed, this takes effect after restarting the cluster processes. It is recommended that you restart the cluster after changing the <span class="interface">Secure connection</span> property value.</td><td>An attempt to change the <span class="interface">Secure connection</span> cluster property value generated an error and the value was not changed.</td><td>Eliminated unexpected system behavior.</td></tr></table><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b2d31966-ca4c-11e5-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.9" class="compat tag_69 tag_1"><td><a name="35122c67-e9bf-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>During the compilation of 1C:Enteprise script texts, unknown compilation directives cause errors.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>Unknown compilation directives did not cause compilation errors.</td><td>Better control of source texts. Reduced number of issues that are hard to detect (typos in compilation directives).</td></tr><tr title="Версия 8.3.9" class="compat tag_45 tag_1"><td><a name="dbb33ec9-eab8-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>When a transaction is rolled back from the temporary table manager, all temporary tables created within the transaction are deleted. In file databases, temporary tables created within a query transaction are not available in that query after rolling the transaction back (this behavior is now uniform with scenarios that use other DMBS).<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>When a transaction was rolled back from the temporary table manager, temporary tables created within the transaction were not deleted. In file databases, the option to use temporary tables created in a transaction that was rolled back was available. In scenarios that used other DBMS, this option was not available.</td><td>Uniform 1C:Enterprise behavior in scenarios that use different DBMS.</td></tr><tr title="Версия 8.3.9" class="compat tag_66 tag_1"><td><a name="e0980b7b-eb89-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 66); return false;">Navigation links</a>.<br></td><td>An attempt to execute the <span class="term">GetURL</span><span class="term">()</span> method for a value that cannot provide an URL generates an exception.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>An attempt to execute the <span class="term">GetURL</span><span class="term">()</span> method for a value that cannot provide an URL had the following result:<ul><li>In the thin client, the method returned a blank string.</li><li>In the web client, an exception was generated.</li></ul></td><td>Unified system behavior in different client applications.</td></tr><tr title="Версия 8.3.9" class="compat tag_99 tag_53 tag_1"><td><a name="c8eb9296-eb8b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 99); return false;">Window-based interface</a>.<br><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>If the <span class="term">Timeout </span>parameter of the <span class="term">DoQueryBox</span><span class="term">()</span>, <span class="term">ShowQueryBox</span><span class="term">()</span>, <span class="term">DoMessageBox</span><span class="term">()</span>, or <span class="term">ShowMessageBox</span><span class="term">()</span> method has a negative value, an exception is generated.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>If the <span class="term">Timeout </span>parameter of the <span class="term">DoQueryBox</span><span class="term">()</span>, <span class="term">ShowQueryBox</span><span class="term">()</span>, <span class="term">DoMessageBox</span><span class="term">()</span>, or <span class="term">ShowMessageBox</span><span class="term">()</span> method had a negative value:<ul><li>In the thin client, the timeout was counted from 4 294 967 295.</li><li>In the web client, the value was not substituted.</li></ul></td><td>Eliminated unexpected system behavior. Unified system behavior in different client applications.</td></tr><tr title="Версия 8.3.9" class="tag_115"><td><a name="c2f6b1c8-eb8d-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The option to monitor the usage of context server calls (including implicit calls) in form event handlers where such calls are prohibited at run time is implemented.
If you enable this option, diagnostics messages are added to the message window.<p>To enable or disable this option, use the <span class="term">/EnableCheckServerCalls</span> command-line option of the client application. The option to run the client application from Designer is implemented, with this command-line option available.</p></td><td>A tool for monitoring the usage of context server calls in form event handlers where such calls were prohibited was not available.</td><td>Improved diagnostics of incorrect usage of 1C:Enterprise programming interfaces.</td></tr><tr title="Версия 8.3.9" class="tag_19"><td><a name="34a0a521-eb8e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>If a parameter of the <span class="term">In </span>operation of the query language is a value table with a column of <span class="term">String </span>type longer that 1024 characters or <span class="term">BinaryData </span>type longer that 2048 bytes, an exception is generated during the query execution.</td><td>If a parameter of the <span class="term">In </span>operation of the query language was a value table with a column of <span class="term">String </span>type longer that 1024 characters or <span class="term">BinaryData </span>type longer that 2048 bytes, the query might or might not be executed, depending on the DBMS.</td><td>More predictable query results on different DBMS. Improved system reliability.</td></tr><tr title="Версия 8.3.9" class="tag_14 tag_115"><td><a name="a88c80ba-eb92-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>At the thick client startup, the <span class="interface">Synchronous call usage mode for platform extensions and add-ins</span> configuration property is ignored and all synchronous methods are executed without any warnings or exceptions.<p>When the thick client is started from Designer, the <span class="term">/EnableCheckExtensionsAndAddInsSyncCalls</span> option is not passed to the client. The behavior of the thin client and the web client in this scenario is not changed.</p><p>The behaviour of configuration verification and refactoring is not changed: they display warnings for all synchronous methods calls and recommend conversion to asynchronous methods.</p></td><td>At the thick client startup, the <span class="interface">Synchronous call usage mode for platform extensions and add-ins</span> configuration property was not ignored.<p>When the thick client was started from Designer, the <span class="term">/EnableCheckExtensionsAndAddInsSyncCalls</span> option was passed to the client.</p></td><td>Removed checks for synchronous method calls in applied solutions intended to run in thick client only.</td></tr><tr title="Версия 8.3.9" class="compat tag_45 tag_1"><td><a name="a82e8c8a-ec15-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>During the query generation, the query builder (in Designer and in the thick client) and the <span class="term">QuerySchem</span><span class="term">a </span>object (in the thick client) generate aliases for all fields of the first query (in a set of unions) for each query in a batch.<p>This change is not implemented in 8.Х.Х repository compatibility mode.
</p></td><td>During the query generation, the query builder (in Designer and in the thick client) and the <span class="term">QuerySchem</span><span class="term">a </span>object (in the thick client) generated aliases only for expression fields and for fields used for ordering and totals calculation.</td><td>Unified behavior of query builder and the <span class="term">QuerySchem</span><span class="term">a </span>object in different client applications.</td></tr><tr title="Версия 8.3.9" class="compat tag_115 tag_1"><td><a name="32be9436-ec35-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The following object keys are used for storing desktop separator positions:<ul><li><span class="interface">HomePage/WindowSettings</span></li><li><span class="interface">HomePage/Taxi/WindowSettings</span></li></ul><p>Once you turn the compatibility mode off, the keys are renamed. If you set the compatibility mode to <span class="interface">Version 8.3.8</span>, the initial names are applied again.</p><p>When you export a configuration to a set of XML files, the file that stores the <span class="term">HomePageWorkingArea</span> property (former <span class="term">StartPageWorkingArea</span> property) has a different name.</p><p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The following object keys were used for storing desktop separator positions:<ul><li><span class="interface">StartPage/WindowSettings</span>;</li><li><span class="interface">StartPage/Taxi/WindowSettings</span>.</li></ul></td><td>The object key names better reflect their purpose.</td></tr><tr title="Версия 8.3.9" class="compat tag_26 tag_1"><td><a name="5abbab67-ec48-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>If auto grouping or rows is enabled, new groupings inherit the name and visibility from the area that is displayed in the grouping header area.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>If auto grouping or rows was enabled, new groupings inherited the name and visibility from the area that was displayed inside the grouping.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="compat tag_36 tag_1"><td><a name="02affe6c-ec4a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>If the <span class="term">DBMSNames </span>parameter of the <span class="term">GetDBStorageStructureInfo()</span> method <p>has a value of non-Boolean type, an exception is generated.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>A value of any type could be passed to the <span class="term">DBMSNames </span>parameter of the <span class="term">GetDBStorageStructureInfo()</span> method.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="compat tag_26 tag_1"><td><a name="537d3e2e-ec4b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In spreadsheet documents, when a text is displayed with nonhorizontal orientation, it has the same font size as regular text.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>In spreadsheet documents, when a text was displayed with nonhorizontal orientation, it had bigger font size than regular text.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="tag_19"><td><a name="f092f970-ec4b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Changing the data lock timeout in the <span class="interface">Infobase options</span> dialog box in Designer requires administrative rights in a nonseparated session and sets exclusive infobase access mode. If an exclusive lock cannot be set, a message with a list of sessions preventing the lock is displayed, it includes the retry option.<p>The <span class="term">SetLockWaitTime</span><span class="term">()</span> method requires administrative rights in a nonseparated session, sets an exclusive database lock (if it was not set earlier), and throws an exception if the exclusive lock cannot be set.</p><p>The change of the data lock timeout is applied immediately to all DBMS except IBM DB2. Changing the lock timeout in IDB DB2 requires a database restart.</p></td><td>Changing the data lock timeout in the <span class="interface">Infobase options</span> dialog box or using the <span class="term">SetLockWaitTime</span><span class="term">()</span> 1C:Enterprise script method was allowed in infobases running in shared mode.</td><td>Eliminated the issues related to database operations that appeared in some scenarios.</td></tr><tr title="Версия 8.3.9" class="tag_56"><td><a name="8cd611e2-ece9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>For the <span class="term">XMLWriter.OpenFile()</span> method, the <span class="term">AddBOM </span>parameter is implemented. It shows whether the resulting file includes a BOM.</td><td>This feature was not provided.</td><td>Integration with systems that do not expect BOMs in their input XML files is now available.</td></tr><tr title="Версия 8.3.9" class="tag_10 tag_29"><td><a name="870d66f8-eceb-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>In the file infobase, the check for client application versions is implemented. Access to the infobase is only allowed if the versions of all client applications match. If the versions do not match, an error is displayed.</td><td>An attempt to access an infobase using multiple versions from the following list generated an exception: 8.2.19 to 8.3.4, 8.3.6, and 8.3.7.<p>In some cases simultaneous access to a single infobase with different platform versions was allowed, where one version was 8.2.18 or earlier and the other one was in range 8.3.1-8.3.3.</p></td><td>Increased reliability of file infobases. Simultaneous access to a single infobase using different 1C:Enterprise versions is not allowed.</td></tr><tr title="Версия 8.3.9" class="compat tag_41 tag_1"><td><a name="9dd5300e-eced-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>The path separator of the <span class="term">ZipFileEntry </span>object depends on the operating system.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The path separator of the <span class="term">ZipFileEntry </span>object was always a slash mark (<span class="interface">/</span>) and did not depend on the operating system.</td><td>ZIP file operations use the same file path separators as other file operations.</td></tr><tr title="Версия 8.3.9" class="compat tag_25 tag_1"><td><a name="5094ac71-ecf9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When data composition template composer generates parameter names, it does not assign parameter names that are already used in the data composition schema.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>When data composition template composer generated parameter names, it could assign parameter names that were already used in the data composition schema.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="tag_10"><td><a name="a4df4c6c-ed23-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When 1C:Enterprise establishes a secure connection (HTTPS) to the Licensing Center, it automatically selects the root certificate store of the operating system.<p>If the Internet connection uses a proxy server that decrypts secure connection (HTTPS) traffic, the system administrator must add the certificates that sign the proxy server certificate to the trusted root certificate store of the operating system.</p></td><td>When 1C:Enterprise established a secure connection (HTTPS) to the Licensing Center, it searched the file <span class="interface">cacert.pem </span>for a secure connection certificate.</td><td>Reduced number of issues related to interaction with the Licensing Center.</td></tr><tr title="Версия 8.3.9" class="tag_38"><td><a name="de7e520a-ed24-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>For the execution of some configuration object handlers and subscriptions, disabling the safe mode is implemented. Once a handler or subscription is executed, the safe mode and the security profile are restored.<p>You can disable the safe mode manually using the <span class="term">SetSafeModeDisabled</span><span class="term">()</span> and <span class="term">GetSafeModeD</span><span class="term">isabled() </span>global context methods. These methods are not available in configuration extensions.</p><p>The list of handlers where the safe mode is automaticly disabled is provided in the documentation.</p></td><td>The option to disable the safe mode using 1C:Enterprise script tools was not provided.</td><td>You have the option to access objects that have events that require privileged mode in their object modules from configuration extensions and external data processors executed in safe mode.</td></tr><tr title="Версия 8.3.9" class="tag_37"><td><a name="750cffbf-ed26-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>TLS 1.2 protocol is used to establish secure connection because it provides additional security. You can force the use of TLS 1.0 protocol when establishing thin client connection to a web server using the command-line option <span class="term">/</span><span class="term">HttpsFor</span><span class="term">ce</span><span class="term">TLS1_0</span>.<p><span class="term">HTTPConnection</span>, <span class="term">FTPConnection</span>, and <span class="term">WSProxy </span>objects automatically select TLS 1.2 protocol, regardless of the specified client certificate source.</p><p>For the <span class="interface">conf.cfg</span> configuration file, the <span class="term">ForceTLS1_0</span> parameter is implemented.</p><p>Simultaneous use of <span class="term">/HttpsForceTLS1_0</span> and <span class="term">/HttpsForceSSLv3</span> command-line options in the thin client is not supported.</p></td><td>TLS 1.0 protocol was used to establish secure connections.</td><td>Increased security of thin client Internet connections.</td></tr><tr title="Версия 8.3.9" class="compat tag_37 tag_1"><td><a name="6ffd9864-ef69-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>If an SMTP server cannot send an email message to one or several recipients, the <span class="term">InternetMail</span><span class="term">.</span><span class="term">Send</span><span class="term">()</span> method returns a map where recipients are keys and SMTP server diagnostic messages are values.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>If an SMTP server could not send an email message to one or several recipients, the <span class="term">InternetMail</span><span class="term">.</span><span class="term">Send</span><span class="term">()</span> method generated an exception.</td><td>You can determine which recipients cannot be reached by email and view the reasons provided by the SMTP server.</td></tr><tr title="Версия 8.3.9" class="tag_20 tag_2 tag_27"><td><a name="4082b535-ef6e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br><a href="#" onclick="onTagClick(this, 27); return false;">Dumping configurations to files/Restoring configurations from files</a>.<br></td><td>When a configuration is exported to files, the format of <span class="interface">Compatibility mode </span>configuration property in the resulting file is different. The new format eliminates possible loss of compatibility mode data during the import.</td><td>When a configuration with <span class="interface">Compatibility mode</span> property set to <span class="interface">Do not use</span> was exported to files, the property value was exported as <span class="interface">Do not use</span>. Then, if that configuration was imported using a later 1C:Enterprise version, the imported compatibility mode value was incorrect.</td><td>Eliminated the chance to lose compatibility mode data after exporting and importing a configuration.<p>Eliminated unexpected system behavior.</p></td></tr><tr title="Версия 8.3.9" class="compat tag_26 tag_1"><td><a name="87310159-fffa-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The <span class="term">FillPropertyValues</span><span class="term">()</span> method applied to a spreadsheet document copies the <span class="term">Template </span>property of the spreadsheet document.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The <span class="term">FillPropertyValues</span><span class="term">()</span> method applied to a spreadsheet document did not copy the <span class="term">Template </span>property of the spreadsheet document.</td><td>The behavior implemented earlier to streamline migration to the previous version is no longer supported.</td></tr><tr title="Версия 8.3.9" class="tag_10 tag_117"><td><a name="86087071-11e5-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>In the file mode, the default format of new databases is 8.3.8.</td><td>In the file mode, the default format of new databases was 8.2.14.</td><td>The optimized file database format implemented in platform version 8.3.8 becomes the default one.</td></tr><tr title="Версия 8.3.9" class="compat tag_37 tag_1"><td><a name="58636db4-20d4-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The <span class="term">Port </span>property of <span class="term">FTPConnection </span>object and the <span class="term">Port </span>parameter of its constructor have the <span class="term">Number </span>type.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The <span class="term">Port </span>property of <span class="term">FTPConnection </span>object and the <span class="term">Port </span>property of its constructor had <span class="term">String</span><span class="term"> </span>type. The constructor parameter accepted any data that could be converted to <span class="term">Number </span>type.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="compat tag_117 tag_1"><td><a name="9655c717-27c9-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>After calling the <span class="term">GetDBStorageStructureInfo</span><span class="term">()</span> method, tables that do not have presentations in the query language have empty strings for their names (<span class="term">TableName </span>property) and their field names (<span class="term">FieldName</span> property).<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>After calling the <span class="term">GetDBStorageStructureInfo</span><span class="term">()</span> method, tables that did not have presentations in the query language had their table name (<span class="term">TableName </span>property) and field name (<span class="term">FieldName</span> property) values equal to virtual table presentations.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="compat tag_83 tag_1"><td><a name="a0864d70-27d1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 83); return false;">HTML support</a>.<br></td><td>Reading and writing XML documents containing <span class="interface">&lt;?</span><span class="interface">xml</span> does not generate an error message.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>Reading and writing XML documents containing <span class="interface">&lt;?</span><span class="interface">xml</span> generated an error message.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="compat tag_41 tag_1"><td><a name="5878aeee-321d-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>File names in ZIP archives are written in UTF8 encoding.<p>For the <span class="term">ZipFileWriter</span> object constructor and the <span class="term">Open</span><span class="term">()</span><span class="term"> </span>method of the <span class="term">ZipFileWriter</span> object, parameters that define file name encoding in ZIP archives are implemented. These parameters override the <span class="term">FileNamesEncodingInZipFile</span> parameter in the <span class="interface">conf.cfg</span> file.</p><p>The default value of the <span class="term">FileNamesEncodingInZipFile</span> parameter in the <span class="interface">conf.cfg</span> file is <span class="term">UTF8</span>.</p><p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>File names in ZIP archives were written in UTF8 encoding and the current operating system encoding.<p>1C:Enterprise script did not provide methods to specify encoding of file names in ZIP archives.</p><p>The default value of the <span class="term">FileNamesEncodingInZipFile</span> parameter in the <span class="interface">conf.cfg</span> file was <span class="term">OSEncodingWithUTF8</span>.</p></td><td>1C:Enterprise script provides methods to specify the encoding of file names in 1C:Enterprise-generated ZIP archives.</td></tr><tr title="Версия 8.3.9" class="compat tag_43 tag_1"><td><a name="c0508650-385e-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Dynamic list fields included in conditional form appearance item filters are always passed to the client, regardless of the value of the <span class="interface">Use always </span>field property or the availability of a visible linked column.<p>This change is not implemented in 8.3.7 compatibility mode. </p></td><td>Dynamic list fields included in conditional form appearance item filters were not automatically passed to the client. To ensure correct functioning of conditional appearance items, developers had to set the <span class="interface">Use always </span>property for such fields.</td><td>Better usability for 1C:Enterprise developers.</td></tr><tr title="Версия 8.3.9" class="tag_43"><td><a name="d357fcee-3d17-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The recommendation to avoid using conditional form appearance for customizing dynamic list appearance if the desired effect can be achieved by using conditional dynamic list appearance is added to the documentation.</td><td>The recommendation to avoid using conditional form appearance for customizing dynamic list appearance if the desired effect can be achieved by using conditional dynamic list appearance was not available in the documentation.</td><td>1C:Enterprise documentation is improved.</td></tr><tr title="Версия 8.3.9" class="compat tag_25 tag_1"><td><a name="0727cd27-3ea9-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the composition of a data composition system template, the following operations are performed using additional data sets that are automatically generated by a template composer:<ul><li>Getting fields</li><li>Applying filters to fields received using "." (dot) from fields that contain aggregate functions and are obtained from a query</li></ul><p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>In the composition of a data composition system template, the following operations were performed within a query:<p>
</p><ul><li>Getting fields</li><li>Applying filters to fields received using "." (dot) from fields that contain aggregate functions and are obtained from a query</li></ul><p>This might generate incorrect results or errors.
</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.9" class="compat tag_25 tag_1"><td><a name="68e6ae2f-5af6-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In data composition schema templates, when parameters that can have both English and Russian names are generated, their names are generated in the language of the current 1C:Enterprise script variant.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>In data composition schema templates, when parameters that could have both English and Russian names were generated, their names were always generated in English.</td><td>You can use Russian names of data composition schema parameters, which match the parameter names that are automatically retrieved from virtual tables.</td></tr><tr title="Версия 8.3.9" class="compat tag_115 tag_1"><td><a name="fce3d9f2-96b0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>1C:Enterprise behavior in the following scenario is changed: a user types something in a text box and then clicks a decoration hyperlink without exiting the text box, which initiates a context server call. The new behavior consists of the following steps:<ul><li>Call the <span class="term">OnChange </span>event handler for the text box.</li><li>Call the <span class="term">URLProcessing </span>event handler for the decoration.</li><li>The text box displays the typed text.</li></ul><p>This change is not implemented in 8.3.8 compatibility mode.</p><p>
</p></td><td>1C:Enterprise behavior in the following scenario was different: a user types something in a text box and then clicks a decoration hyperlink without exiting the text box, which initiates a context server call. The previous behavior consisted of the following steps:<p>
</p><ul><li>In the thin and thick clients:</li><ul><li>Call the <span class="term">URLProcessing </span>event handler for the decoration.</li><li>The text box displays the text that was there before typing.</li></ul><li>In the web client:</li><ul><li>Call the <span class="term">URLProcessing </span>event handler for the decoration.</li><li>The text box displays the typed text.</li></ul></ul></td><td>Eliminated unexpected system behavior. Unified behavior of client applications.</td></tr><tr title="Версия 8.3.9" class="tag_14 tag_70 tag_11"><td><a name="b37cf07d-fdc0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>Since Windows versions 2008 R2 and later stop trusting SHA-1 certificates in January 2017, the following changes are implemented:<ul><li>On Windows, the file system extension and cryptography extension installers for Google Chrome and Mozilla Firefox are converted to <span class="interface">.exe </span>format and signed with both SHA-1 and SHA-256.</li><li>It is recommended that you sign client application installer <span class="interface">1CEClientSetup.exe</span> with both SHA-1 and SHA-256.</li></ul></td><td>On Windows, the file system extension and cryptography extension installers for Google Chrome and Mozilla Firefox were delivered as <span class="interface">.msi</span> files signed with SHA-1.</td><td>The platform executable files are verified on all supported operating systems of Windows family.</td></tr><tr title="Версия 8.3.9" class="compat tag_51 tag_1"><td><a name="8ceac097-1450-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>The <span class="term">TestedFormButton</span><span class="term">.</span><span class="term">Click</span><span class="term">()</span> method generates an error if the button specified in this method is not visible.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The <span class="term">TestedFormButton</span><span class="term">.</span><span class="term">Click</span><span class="term">()</span> method did not generate an error if the button specified in this method was not visible.</td><td>Eliminated unexpected system behavior.<p>The automated testing only performs the actions that are available to users in interactive mode.</p></td></tr></table><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b2d31967-ca4c-11e5-a3f7-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.9" class="tag_0"><td><a name="5789c6c7-ec32-11e5-a3f7-0050569f678a"></a>The <span class="term">StartPageForms</span> object is renamed. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">StartPageForms</span>.</li></ul></td><td><ul><li><span class="term">HomePageForms</span>.</li></ul></td></tr><tr title="Версия 8.3.9" class="tag_0"><td><a name="b3ce0c22-ec32-11e5-a3f7-0050569f678a"></a>The <span class="term">StartPageSettings</span> object is renamed. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">StartPageSettings</span>.</li></ul></td><td><ul><li><span class="term">HomePageSettings</span>.</li></ul></td></tr><tr title="Версия 8.3.9" class="tag_0"><td><a name="c8dfef08-ec32-11e5-a3f7-0050569f678a"></a>The <span class="term">StartPageWorkingArea</span> object is renamed. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">StartPageWorkingArea</span>.</li></ul></td><td><ul><li><span class="term">HomePageWorkingArea</span>.</li></ul></td></tr><tr title="Версия 8.3.9" class="tag_0"><td><a name="e9dd6fac-ec32-11e5-a3f7-0050569f678a"></a>The <span class="term">ClientApplicationWindow.StartPage</span> property is renamed. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">StartPage</span>.</li></ul></td><td><ul><li><span class="term">HomePage</span>.</li></ul></td></tr><tr title="Версия 8.3.9" class="tag_0"><td><a name="f4ebade7-ec32-11e5-a3f7-0050569f678a"></a>The <span class="term">TestedClientApplicationWindow</span><span class="term">.StartPage</span> property is implemented. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">StartPage</span>.</li></ul></td><td><ul><li><span class="term">HomePage</span>.</li></ul></td></tr><tr title="Версия 8.3.9" class="tag_0"><td><a name="9830d372-0b8d-11e6-a3f7-0050569f678a"></a>Name of the system enumeration that lists item and title alignment options.</td><td><ul><li><span class="term">ItemsAndTitlesAlign</span><span class="term">.</span></li></ul></td><td><ul><li><span class="term">ItemsAndTitlesAlignVariant</span>.</li></ul></td></tr><tr title="Версия 8.3.9" class="compat tag_0 tag_1"><td><a name="9a802391-1370-11e6-a3f7-0050569f678a"></a>The value of the <span class="term">Purpose </span>column of the <span class="term">ExtensionInfo </span>value table returned by <span class="term">GetDBStorageStructureInfo() </span>method.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td><ul><li><span class="term">Main</span>.</li></ul></td><td><ul><li><span class="term">ConfigurationExtensionsInformation</span>.</li></ul></td></tr><tr title="Версия 8.3.9" class="compat tag_0 tag_1"><td><a name="5dfe7362-2d6b-11e6-a3f7-0050569f678a"></a>The value of the <span class="term">Purpose </span>column of the <span class="term">O</span><span class="term">D</span><span class="term">ataSettings</span><span class="term"> </span>value table returned by <span class="term">GetDBStorageStructureInfo() </span>method.<p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td><ul><li><span class="term">Main</span>.</li></ul></td><td><ul><li><span class="term">StandardODataInterfaceOptions</span></li></ul></td></tr></table><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b2d31968-ca4c-11e5-a3f7-0050569f678a">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.9" class="tag_78 tag_132"><td><a name="e3a00a29-d3f1-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 132); return false;">Multimedia support</a>.<br></td><td>On the mobile platform, the <span class="term">FileDialog</span><span class="term"> </span>object is available. For the dialog limitations on specific mobile operating systems, see the Syntax Assistant. For mobile devices, the option to select files interactively is implemented for the following methods: <span class="term">GetFile</span><span class="term">()</span>, <span class="term">GetFiles</span><span class="term">()</span>, <span class="term">PutFile</span><span class="term">()</span>, and <span class="term">PutFiles</span><span class="term">()</span>.<p>The <span class="term">File.GetMobileDeviceLibraryFilePresentation</span><span class="term">()</span> method is implemented. It returns the file presentation for displaying on the mobile device.</p><p>You can use mobile device library file names (with the <span class="interface">content: </span>schema) in constructors of the following objects: <span class="term">File</span>, <span class="term">BinaryData</span>, <span class="term">Picture</span>, and <span class="term">MobileDeviceApplicationRun</span>. You can use them as parameters for the following global context methods: <span class="term">RunApp</span><span class="term">()</span>, <span class="term">GotoURL</span><span class="term">()</span>, <span class="term">FileCopy</span><span class="term">()</span>, <span class="term">MoveFile</span><span class="term">()</span>, <span class="term">DeleteFiles</span><span class="term">()</span>, and <span class="term">FindFiles</span><span class="term">()</span>. On iOS and Android, you can also use them as parameters for the following methods of the <span class="term">MultimediaTools </span>object: <span class="term">PlayAudio() </span>and <span class="term">GetAudioDuration()</span>.</p><p>The <span class="term">MobileDeviceLibraryDir</span><span class="term">()</span> global context method is implemented. It returns a path to a mobile device library (a picture, audio, or video library).</p></td><td>The <span class="term">FileDialog </span>object was not available on the mobile platform.</td><td>Interactive file operations are implemented for the mobile platform.</td></tr><tr title="Версия 8.3.9" class="tag_48"><td><a name="e3535cf4-ecfb-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>For Android operating system, the option to process incoming call data using 1C:Enterprise script tools is implemented.<p>For the <span class="term">TelephonyTools</span> object, the <span class="term">CallsHandlingSupported</span><span class="term">()</span>, <span class="term">AttachCallsHandler</span><span class="term">()</span>, and <span class="term">DetachCallsHandler() </span>methods are implemented. The <span class="term">TelephonyTools</span><span class="term">.</span><span class="term">CallsHandlingSupported</span><span class="term">()</span> method returns <span class="term">True</span> on Android only.</p></td><td>This feature was not provided on the mobile platform.</td><td>The option to process incoming call data in mobile applications using 1C:Enterprise script tools is now available on Android operating system.</td></tr><tr title="Версия 8.3.9" class="tag_48"><td><a name="17146169-ecfd-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>Extended multimedia options for the mobile platform:<ul><li>The option to play a sound or vibration alert is implemented. The <span class="term">MultimediaTools</span><span class="term">.PlaySoundAlert</span><span class="term">()</span> method is implemented.</li><li>The option to play audio data of various types is implemented. Playing is performed using the default application provided with the operating system. The option to stop playing is implemented. For the <span class="term">MultimediaTools</span> object, the <span class="term">PlayAudio()</span>, <span class="term">StopAudioPlayback</span><span class="term">()</span>, and <span class="term">GetAudioDuration</span><span class="term">()</span> methods are implemented.</li><li>The option to read text using the screen reader provided with the operating system is implemented. The option to stop reading is implemented. For the <span class="term">MultimediaTools</span> object, the <span class="term">PlayText</span><span class="term">()</span>, <span class="term">StopTextPlayback()</span>, and <span class="term">TextPlaybackSupported()</span> methods are implemented.</li></ul></td><td>These features were not provided on the mobile platform.</td><td>Extended multimedia support.</td></tr><tr title="Версия 8.3.9" class="tag_25"><td><a name="7cf58204-ed07-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>On the mobile platform, the support of data composition system is implemented, except for the objects that allow user interaction. Therefore, all data composition system operations are performed using 1C:Enterprise script tools.<p>In Designer, the option to create data composition schemas for reports that run in mobile applications is implemented.</p></td><td>This feature was not provided on the mobile platform.</td><td>Extended report development capabilities on the mobile platform.</td></tr><tr title="Версия 8.3.9" class="tag_11"><td><a name="933a6ac0-ed08-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>On the mobile platform, add-in support is implemented. It uses the NativeAPI technology.<p>You can export a mobile configuration from Designer to <span class="interface">1cema.zip</span> format, which includes the add-ins used in the configuration.</p><p>When you connect a mobile device using Android Debug Bridge (ADB), add-ins are copied to the device.</p><p>In the mobile application builder, the option to build applications with add-ins is implemented.</p><p>Add-in development technology documentation and examples are updated (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>).</p></td><td>The mobile platform did not support this feature.</td><td>You have the option to expand mobile platform functionality when its standard features do not cover your needs.</td></tr><tr title="Версия 8.3.9" class="tag_115"><td><a name="0dd40e4b-ed0b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The following features are implemented for the mobile platform:<ul><li>Display a command bar button as a hyperlink.</li><li>Set horizontal picture alignment on a managed form button.</li><li>Set gaps between command bar buttons.</li><li>Set command bar button shapes (except for buttons located in popups).</li><li>Set the view of managed form buttons.</li><li>For text boxes, support of <span class="term">CreateButton</span> and <span class="term">ChoiceButtonRepresentation</span> properties is implemented.</li><li>For text boxes, support of <span class="term">EditTextChange</span> and <span class="term">Creating </span>events is implemented.</li></ul><p>Support of <span class="term">BorderColor</span>, <span class="term">BackColor</span>, <span class="term">TitleTextColor</span>, and <span class="term">TitleFont </span>properties is implemented for buttons of <span class="term">CommandBarButton</span> and <span class="term">CommandBarHyperlink</span> type and for form group extensions for popups.</p></td><td>This feature was not provided on the mobile platform.</td><td>The set of features available on the mobile platform is closer to the set of features available on the desktop platform.</td></tr><tr title="Версия 8.3.9" class="tag_37"><td><a name="d4f92fb0-ed0b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The option to check the availability of data transfer network in mobile applications is implemented.<p>The <span class="term">InternetConnectionInformation </span>global context property is implemented.</p></td><td>This feature was not provided on the mobile platform.</td><td>The option to analyze available data transfer methods and choose the optimal strategy for operations with external data is implemented.</td></tr><tr title="Версия 8.3.9" class="tag_57"><td><a name="e8a843e1-ed1f-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 57); return false;">JSON support</a>.<br></td><td>The mobile platform now supports JSON operations. Serialization of XDTO documents to JSON objects is not supported.</td><td>This feature was not provided on the mobile platform.</td><td>Simplified integration with applications (including web applications) that use JSON data format. The option to store data in JSON format (for example, instead of XML format) is implemented.</td></tr><tr title="Версия 8.3.9" class="compat tag_37 tag_1"><td><a name="0aca7712-ed22-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The behavior of the <span class="term">OpenSSLSecureConnection </span>object is unified with that of the PC platform.<ul><li>If the <span class="term">CertificationAuthorityCertificates </span>parameter of the object constructor is not specified, the certificate is not checked.</li><li>If the <span class="term">CertificationAuthorityCertificates </span>parameter of the object constructor is specified, the check uses the root certificates installed on the device.</li></ul><p>The <span class="term">OS</span><span class="term">CertificationAuthority</span><span class="term">Certificates</span> object is now available on the mobile platform.</p><p>This change is not implemented in 8.3.8 compatibility mode.</p></td><td>The certificate check always used the root certificates installed on the mobile device. The <span class="term">CertificationAuthorityCertificates </span>parameter of the <span class="term">OpenSSLSecureConnection </span>object constructor was ignored.</td><td>Unified behavior of the mobile platform and the PC platform.<p>Eliminated unexpected system behavior.</p></td></tr><tr title="Версия 8.3.9" class="tag_48"><td><a name="6bb2019f-f035-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The option to check the availability of operations with global contact keys, calendars, and calendar events on different mobile operating systems is implemented.<p>For the <span class="term">ContactManager </span>object, the <span class="term">GlobalContactsKeySupported()</span> method is implemented.</p><p>For the <span class="term">CalendarsManager </span>object, the <span class="term">GlobalCalendarsKeysSupported</span><span class="term">()</span> and <span class="term">GlobalEvents</span><span class="term">KeysSupported</span><span class="term">()</span> methods are implemented.</p><p>The <span class="term">GlobalContactKey</span> parameter of the <span class="term">AccountContactData </span>object constructor is no longer supported. The values of properties that describe global contact keys, calendars, and calendar events depend on the result of the function that checks the availability of global key operations. If global key operations are not supported, requests to these values return blank strings.</p><p>Availability of <span class="term">LocalContactKey</span>, <span class="term">LocalCalendarKey</span>, and <span class="term">LocalCalendarEventKey</span><span class="term"> </span>objects on the mobile application server is implemented.</p></td><td>The availability of global contact keys, events, and calendar events depended on the platform where a mobile application was running. Developers had no means to check whether operations with global keys from 1C:Enterprise script were supported.<p>The <span class="term">LocalContactKey</span>, <span class="term">LocalCalendarKey</span>, and <span class="term">LocalCalendarEventKey</span><span class="term"> </span>objects were not available on the mobile application server.</p></td><td>The mobile platform behavior is unified with the general behavior of applications that have features that are not available on some mobile devices or operating systems.</td></tr><tr title="Версия 8.3.9" class="tag_95"><td><a name="69ad52e9-0abc-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>In the mobile platform, support of the following global context methods is implemented: <span class="term">InitializePredefinedData</span><span class="term">()</span>, <span class="term">SetInfoBasePredefinedDataUpdate</span><span class="term">()</span>, and <span class="term">GetInfoBasePredefinedData</span><span class="term">().</span> </td><td>This feature was not provided on the mobile platform.</td><td>Unified desktop and mobile platform features related to predefined data.</td></tr><tr title="Версия 8.3.9" class="tag_115"><td><a name="4be228e3-5fb2-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>New managed form interface features in the mobile platform. Now you can:<ul><li>Create collapsible groups.</li><li>Manage <span class="term">Pages</span><span class="term"> </span>form item visibility if it is displayed either as the current page or as tabs. In this scenario you can use 1C:Enterprise script to switch between the current page and the tabs. The <span class="term">CurrentPagesState </span>property is implemented.</li><li>Manage visibility of open and clear buttons in text boxes. The <span class="term">AutoShowClearButton </span>and <span class="term">AutoShowOpenButton </span>properties are implemented for managed form text boxes.</li><li>Manage multiline text box height. The <span class="term">HeightControlVariant </span>property is implemented for managed form text boxes.</li><li>Switch form items to edit mode. The <span class="term">ManagedForm.BeginEditingItem() </span>method is implemented.</li><li>Manage some service options for text boxes, such as:</li><ul><li>Auto correction. The <span class="term">AutoCorrectionOnTextInput </span>property is implemented.</li><li>Spell checking. The <span class="term">SpellCheckingOnTextInput </span>property is implemented.</li><li>Auto capitalization. The <span class="term">AutoCapitalizationOnTextInput </span>property is implemented.</li><li>Manage the keybord type used to input data. The <span class="term">SpecialTextInputMode </span>property is implemented.</li><li>Change the label of the return keyboard button. The <span class="term">OnScreenKeyboardReturnKeyText </span>property is implemented.</li></ul><li>Manage form table height if data displayed in the table is not a dynamic list. The <span class="term">HeightControlVariant </span>property is implemented.</li><li>Manage the search string position. You can specify whether the search string is displayed in the form header or appears after a user swipes down a table title.</li></ul><p>Command bar commands are no longer included in the <span class="interface">More</span> menu.</p><p>Table row context menu commands can be moved to the <span class="interface">More </span>menu if they do not fit the screen.</p><p>Fixed spreadsheet document areas are displayed in a new way.</p></td><td>These features were not provided.<ul><li>Command bar commands were duplicated as items of the <span class="interface">More </span>menu.</li><li>1C:Enterprise attempted to display all table row context menu commands on the screen.</li><li>Fixed spreadsheet document areas were displayed differently.</li></ul></td><td>The mobile platform interface is closer to the modern interface development standards.</td></tr><tr title="Версия 8.3.9" class="tag_48"><td><a name="ce31eac8-6484-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The implementation of the <span class="term">Beep</span><span class="term">()</span> method is now uniform with the implementation of the <span class="term">MultimediaTools</span><span class="term">.PlaySoundAlert</span><span class="term">(</span><span class="term">SoundAlert</span><span class="term">.Default</span><span class="term">)</span>.</td><td>The <span class="term">Beep</span><span class="term">()</span><span class="term"> </span>method did not perform any actions.</td><td>You can use the <span class="term">Beep</span><span class="term">()</span><span class="term"> </span>method to play the default sound alert of a mobile device.</td></tr><tr title="Версия 8.3.9" class="tag_10"><td><a name="37cdf49e-6486-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>For mobile applications, the following features are implemented:<ul><li>Infobase verification and repair.</li><li>Infobase backup.</li><li>The option to run an automated backup before the application update, so that you can restore the infobase if any issues occur during the update. This option is enabled by default.</li><li>The option to schedule automated infobase backups is implemented.</li></ul><p>The backups are stored to the mobile device storage.</p><p>These options are available in the application settings dialog box (the <span class="interface">Administration </span>button in this dialog box).</p></td><td>This feature was not provided.</td><td>Additional options for mobile application administrators.</td></tr><tr title="Версия 8.3.9" class="tag_48"><td><a name="98ffd8eb-7e6a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>The 1C:Enterprise mobile platform does not support Apple iAd any more as the service is officially shut down. Google AdMob advertisement service is supported for both iOS and Android devices.<p>In Mobile application builder, you can specify that your application uses ads, and the builder picks the appropriate mobile platform for building the application based on the option that you select.</p><p>You do not have to modify your iOS applications that support both services but the applications that support only Apple iAd require modification.</p></td><td>The 1C:Enterprise mobile platform supported Apple iAd and Google AdMob.</td><td>The Apple iAd service, which is now obsolete, is not supported.</td></tr><tr title="Версия 8.3.9" class="tag_32"><td><a name="c24d1fd5-b09b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile application builder can create application builds for OS emulators.</td><td>Mobile application builder could not create application builds for OS emulators.</td><td>More options for iOS application developers.</td></tr></table><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b2d31969-ca4c-11e5-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.9" class="tag_0"><a name="80a1f936-b14f-11e6-a3f7-0050569f678a"></a>The cURL library is modified to eliminate vulnerabilities.</li><li title="Версия 8.3.9" class="tag_0"><a name="6949d29c-c03e-11e6-a3f7-0050569f678a"></a>The libtiff library is updated to version 4.0.7.<p>
</p></li></ul><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b2d3196a-ca4c-11e5-a3f7-0050569f678a">Transition from the previous version to the version 8.3.9</a></h2><ul><li title="Версия 8.3.9" class="tag_0"><a name="b2d3196b-ca4c-11e5-a3f7-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.9.
</li><li title="Версия 8.3.9" class="tag_0"><a name="b2d3196c-ca4c-11e5-a3f7-0050569f678a"></a>Some features that are added in version 8.3.9 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.9" class="tag_0"><a name="0688147e-f02d-11e5-a3f7-0050569f678a"></a>In the file mode, queries are optimized for scenarios where an applied solution has separators but actually contains a single data area.<p>To apply this optimization to an existing infobase, perform infobase verification and repair with the <span class="interface">Reindex</span><span class="interface"> </span><span class="interface">infobase tables</span> check box selected.</p><p>Once the restructuring is completed, the optimization is applied to all restructured objects.</p></li><li title="Версия 8.3.9" class="tag_0"><a name="9432266e-f5b7-11e5-a3f7-0050569f678a"></a>The index of the actual action period table of a calculation register is complemented by the start date and end date fields, and the index is now clustered. This reduces the chance of lock escalation to the table level when writing record sets of calculation registers that support action period. <p>For the chart of calculation types table that stores serial numbers of calculation type displacements, a nonunique index by displacement number is implemented. As a result, simultaneous editing of a single chart of calculation types in different data areas of a separated infobase never requires waiting for lock releases.</p><p>To apply this optimization to existing infobases, perform the infobase verification and repair operation with the <span class="interface">Restructure infobase tables </span>option selected.</p></li><li title="Версия 8.3.9" class="tag_0"><a name="b832b064-8956-11e6-a3f7-0050569f678a"></a>After migration to mobile 1C:Enterprise platform version 8.3.9.67 or later, when you first start an application, 1C:Enterprise performs infobase verification and repair with <span class="interface">Check logical infobase inte</span><span class="interface">grity</span> and <span class="interface">Recalculate totals</span> check boxes selected. If this operation takes a long time to complete, it is recommended that you cancel it on the mobile device, retrieve the backup that you created before the update from the mobile device, and use the cluster administration console (<span class="interface">1cv8a</span>) to verify and repair the infobase, just like you would do for desktop 1C:Enterprise platform. Then, on the mobile device, restore the repaired infobase from the file.</li></ul><p><a href="#b2d31961-ca4c-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h1><a name="5a3fed9c-6292-11e5-a3f7-0050569f678a">Version 8.3.8</a></h1><p title="Версия 8.3.8" class="tag_0"><a name="5a3feda8-6292-11e5-a3f7-0050569f678a"></a>Version 8.3.8 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#5a3fed9d-6292-11e5-a3f7-0050569f678a">New functionality and changes</a></li><li><a href="#5a3fed9e-6292-11e5-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#5a3fed9f-6292-11e5-a3f7-0050569f678a">Optimization</a></li><li><a href="#5a3feda0-6292-11e5-a3f7-0050569f678a">Changes that affect system behavior</a></li><li><a href="#5a3feda1-6292-11e5-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#5a3feda2-6292-11e5-a3f7-0050569f678a">Renamed objects</a></li><li><a href="#5a3feda3-6292-11e5-a3f7-0050569f678a">Mobile platform</a></li><li><a href="#5a3feda4-6292-11e5-a3f7-0050569f678a">Library updates
</a></li><li><a href="#5a3feda5-6292-11e5-a3f7-0050569f678a">Transition from the previous version to the version 8.3.8</a></li></ul><h2><a name="5a3fed9d-6292-11e5-a3f7-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.8" class="compat tag_2 tag_1"><td><a name="70365b50-6297-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.3.7</span><span class="interface"> </span>is added to the list of available values of the <span class="interface">Compatibility mode</span> property.</td><td>Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, and 8.3.6.</td><td>In version 8.3.8 you can run configurations created in version 8.3.7 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.8 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.7 for working with the infobase even after the transition to version 8.3.7. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).</td></tr><tr title="Версия 8.3.8" class="tag_37"><td><a name="69f6f5c0-62a6-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Support of Linux trusted certificate directories (<span class="interface">/etc/ssl/certs </span>and <span class="interface">/</span><span class="interface">etc</span><span class="interface">/</span><span class="interface">pki</span><span class="interface">/</span><span class="interface">tls</span><span class="interface">/</span><span class="interface">cer</span><span class="interface">t</span><span class="interface">s</span>) is implemented. The <span class="term">OSCertificationAuthorityCertificates</span><span class="term"> </span>object enabling cross-OS certificate operations is implemented. The <span class="term">LinuxCertificationAuthorityCertificates </span>object caching certificate data on Linux operating system is implemented. It is recommended that you use the <span class="term">OSCertificationAuthorityCertificates </span>object.<p>The<span class="term"> </span><span class="term">CertificationAuthorityCertificates</span> parameter of <span class="term">OpenSSLSecureConnection </span>object constructor accepts objects of <span class="term">OSCertificationAuthorityCertificates</span><span class="term"> </span>and <span class="term">LinuxCertificationAuthorityCertificates</span><span class="term"> </span>types.</p><p>NSS certificates are no longer supported.</p></td><td>On Linux operating system, the platform used NSS certificate store.</td><td>On Linux operating system, in the thin client, the option to access infobases published on resources that require clent certificates is implemented.</td></tr><tr title="Версия 8.3.8" class="tag_81 tag_29"><td><a name="fa34c8be-62ac-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of Apache 2.4 is implemented for Windows and Linux.<p>For the <span class="interface">webinst</span> utility, the <span class="interface">-apache24</span> key is implemented.
</p></td><td>This feature was not provided.<p>Apache versions 2.0 and 2.2 were supported.</p></td><td>Extended list of supported web servers.</td></tr><tr title="Версия 8.3.8" class="tag_51"><td><a name="ca7a0860-62ad-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>The <span class="interface">About 1C:Enterprise</span> window and the title of the client application window indicate whether the client application is a test manager or a test client.<p>The <span class="term">TestedApplication.SetFile</span><span class="term">DialogResult</span><span class="term">()</span> method is implemented, it provides the result of an operation performed in the file selection dialog box.</p><p>The resulting collection of the <span class="term">TestedApplication</span><span class="term">.</span><span class="term">GetChildObjects</span><span class="term">() </span>method now inlcudes windows that contain text or spreadsheet documents.</p><p>The <span class="term">TestedForm</span><span class="term">.ExecuteChoiceFromList</span><span class="term">()</span> method is implemented, it selects a value from the list opened using the <span class="term">ManagedForm</span><span class="term">.</span><span class="term">ChooseFromList</span><span class="term">()</span> method.</p><p>The <span class="term">TestedForm</span><span class="term">.ExecuteChoiceFromMenu()</span> method is implemented, it selects a value from the menu opened using the <span class="term">ManagedForm</span><span class="term">.</span><span class="term">ChooseFromMenu</span><span class="term">()</span> method.</p><p>For the <span class="term">TestedFormField</span> object, the support of form field extension for a text document is implemented.</p><p>For the <span class="term">TestedFormField </span>object, the support of form field extension for a formatted document is implemented. For the <span class="term">TestedFormField </span>object, the following methods are implemented: <span class="term">Get</span><span class="term">HTML()</span> (returns the formatted document content) and <span class="term">Input</span><span class="term">HTML()</span> (emulates entering text to the formatted document).</p><p>The <span class="term">TestedFormField</span><span class="term">.WriteContentToFile</span><span class="term">()</span> method is implemented, it writes the document file to the hard disk (same as the <span class="interface">Save</span> command). The method is available for spreadsheet document, text document, and formatted document extensions.</p></td><td>These features were not provided.</td><td>Extended automated testing capabilities.</td></tr><tr title="Версия 8.3.8" class="tag_20"><td><a name="8997078c-71b3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The option to save and restore the settings in the configuration comparison and merging window is implemented. A check box that manages automatic automatic saving of the form settings is implemented.<p>The module comparison and merging form is refactored. Now it includes a command bar with the editor commands.</p><p>The filter settings now include the <span class="interface">Show only properties that were changed twice</span> option.</p></td><td>These features were not provided.</td><td>Improved usability for applied solution developers who often perform comparison and merging of configurations with custom settings.</td></tr><tr title="Версия 8.3.8" class="tag_20"><td><a name="a96fb22a-71b3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The following operations are now available as command-line options for batch Designer startup mode:<ul><li>Compare configurations (<span class="term">/CompareCfg</span>)</li><li>Merge configurations (<span class="term">/MergeCfg</span>)</li><li>Lock objects in a configuration repository (<span class="term">/ConfigurationRepositoryLock</span>).</li><li>Release objects in a configuration repository(<span class="term">/ConfigurationRepositoryUnlock</span>).</li><li>Store modified objects to a configuration repository (<span class="term">/ConfigurationRepositoryCommit</span>).</li><li>Label a repository version (<span class="term">/ConfigurationRepositorySetLabel</span>).</li></ul><p>The following parameters are implemented for <span class="term">/</span><span class="term">UpdateCfg</span> command-line option of batch Designer startup:</p><ul><li><span class="term">-DumpListOfTwiceChangedProperties</span>. Generates the list of properties that were changed twice.</li><li><span class="term">-IncludeObjectsByUnresolvedRefs</span>. If the settings include objects that are not in the list of objects to be merged and are not available in the main configuration, but these objects are referred from objects that are in the list, mark them for merging and attempt to continue the merging.</li><li><span class="term">-ClearUnresolvedRefs</span>. Clear references to objects that are not in the list of objects to be merged.</li><li><span class="term">-Settings</span>. Use the merge settings from the specified file.</li><li><span class="term">-force</span>. Automatically resolve merge issues. This affects the platform behavior in the following cases: locked objects are found; properties that were changed twice and do not have the merge mode specified are found; or a warning about deletion of objects refered by objects that do not participate in the merging is issued.</li></ul><p>For <span class="term">/ConfigurationRepositoryUpdateCfg</span> command-line option of batch Designer startup, the <span class="term">-objects</span> parameter is implemented. This parameter specifies that the operation is performed for a specific set of configuration objects.</p></td><td>These features were not provided.<p>The <span class="term">/ConfigurationRepositoryUpdateCfg</span> command-line option of batch Designer startup was only applicable to the entire configuration.</p></td><td>Simplified automatic update of applied solutions.</td></tr><tr title="Версия 8.3.8" class="tag_45"><td><a name="3fe9f5b5-7257-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>For the query debug, the following operations are inplemented: viewing the list of temporary tables, the structure of temporary tables, and the contents of temporary tables. The <span class="term">Query.ExecuteBatchWithIntermediate</span><span class="term">Data(</span><span class="term">) </span>method is implemented. The <span class="term">TempTablesManager</span><span class="term">.</span><span class="term">Tables </span>property is implemented.</td><td>This feature was not provided.</td><td>Extended applied solution debug capabilities, especially when debugging complex batch queries.</td></tr><tr title="Версия 8.3.8" class="tag_62"><td><a name="8cab353f-7258-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>The <span class="term">ExternalDataSourceManager.TransactionActive()</span> method is implemented. It determines whether an external data source has a transaction in progress.</td><td>This feature was not provided.</td><td>The option to determine whether an external data source has a transaction is progress is now available.</td></tr><tr title="Версия 8.3.8" class="tag_65"><td><a name="c89c5b1d-73ec-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>Support of web services that support MTOM standard is implemented (<a href="http://www.w3.org/TR/soap12-mtom/" target="_blank">read more</a>).</td><td>This feature was not provided. Web services that supported MTOM standard were not supported.</td><td>Extended capabilities for 1C:Enterprise integration with third-party systems. Integration with web services that support optimized transfer of binary data is available, which reduces the network traffic and RAM usage.</td></tr><tr title="Версия 8.3.8" class="tag_129"><td><a name="7b373976-7416-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 129); return false;">OData interface</a>.<br></td><td>The following improvements to the standard OData interface are implemented:<ul><li>Filter by composite type</li><li>Lambda expressions</li><li>New query options for filtering the received data:</li><ul><li><span class="term">$ski</span><span class="term">p</span>. Skips several first records in the query result</li><li><span class="term">$inlinecount</span>. Includes the size of the resulting selection to the query result</li><li><span class="term">$orderby</span>. Sets the order of records in the query result</li><li><span class="term">$count</span>. Returns the number or records in the query</li></ul><li>More functions can be used in queries:</li><ul><li>Functions that process string values</li><li>Functions that process date and time values</li><li>Function that checks whether a value has the specified type</li><li>Functions that convert types</li></ul></ul></td><td>The standard OData interface provided more limited functionality</td><td>1C:Enterprise object presentations better conform to the OData standard requirements.</td></tr><tr title="Версия 8.3.8" class="tag_38 tag_20"><td><a name="31d43a42-763d-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The <span class="term">Configura</span><span class="term">tionExtension()</span> method is implemented for configuration objects. It is used to determine the configuration extension where the object belongs.<p>For <span class="term">ConfigurationExtensionsManager.Get()</span><span class="term"> </span>method, the <span class="term">Config</span><span class="term">ExtensionSource </span>parameter is implemented. If specifies which list of extensions is retrieved (database extensions only; extensions available in the current session; or extensions that were disabled or did not pass the check at the attachment stage).</p></td><td>This feature was not provided.</td><td>Simplified configuration extension operations in 1C:Enterprise script.</td></tr><tr title="Версия 8.3.8" class="tag_38"><td><a name="c5d67d26-763d-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>The <span class="term">ConfigurationExtensionC</span><span class="term">ompatibilityMode</span> property of configuration extensions is implemented. This property is used to limit the extension functionality to ensure its compatibility with a specific version of 1C:Enterprise platform, while leaving the option to edit the extension using a later 1C:Enterprise platform version, which provides more features for configuration extensions.The option to create the following objects in configuration extensions is implemented:<ul><li>Common templates</li><li>Common commands</li><li>Common pictures</li><li>Attributes, tabular sections, and attributes of adopted tabular sections for:</li><ul><li>Reports</li><li>Data processors</li></ul><li>Forms, templates, and commands of adopted objects:</li><ul><li>Exchange plans</li><li>Filter criteria</li><li>Settings storage</li><li>Catalogs</li><li>Documents</li><li>Document journals</li><li>Enumerations</li><li>Reports</li><li>Data processors</li><li>Accounting registers</li><li>Accumulation registers</li><li>Calculation registers</li><li>Information registers</li><li>Charts of characteristic types</li><li>Charts of accounts</li><li>Charts of calculation types</li><li>Business processes</li><li>Tasks</li><li>External data sources:</li><ul><li>Tables</li><li>Cubes</li><li>Dimension tables</li></ul></ul></ul><p>In configuration extensions, the option to change the properties of adopted configuration objects, which describe both main and auxiliary forms, is implemented.</p><p>For adopted reports, the option to change the <span class="interface">Main data composition schema</span> property is implemented.</p><p>In configuration extensions, changing the <span class="interface">P</span><span class="interface">icture </span>property of subsystems, command groups, commands, and common commands is available.</p><p>In the module editor, the context help is only displayed for objects included in the current extension.</p></td><td>These features were not provided. In the module editor, the context help was displayed for both the original configuration and the extension.</td><td>Extended configuration extension capabilities.</td></tr><tr title="Версия 8.3.8" class="tag_20 tag_133"><td><a name="875e29ce-764f-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>The option to export external reports and data processors to XML files is implemented. In Designer, the following <span class="interface">File </span>menu commands provide this option: <span class="interface">Save</span>, <span class="interface">Save as</span>, and <span class="interface">Save copy</span>. After the export, changing the object type (external report to external data processor or vice versa) is not available. The import is available using the <span class="interface">Open </span>command of the <span class="interface">File </span>menu.<p>In the external report or data processor editor dialog box, the options to export the report or data processor to files and import it from files are implemented. The export and import commands are available on the <span class="interface">Actions </span>menu of the dialog box.</p><p>The option to compare an external report or data processor with an external report or data processor stored in XML files is implemented. In the external report or data processor editor dialog box, the following <span class="interface">Actions </span>menu command provides this option:<span class="interface"> Compare and</span><span class="interface"> merge with external report or</span><span class="interface"> data processor</span>.</p><p>The option to export and import external reports or data processors to or from XML files using the command-line options of Designer batch mode is implemented. The <span class="term">/DumpExte</span><span class="term">rnalDataProcessorOrReportsToFiles </span>and <span class="term">/Load</span><span class="term">Exte</span><span class="term">rnalDataProcessorOrReportsFrom</span><span class="term">Files </span>keys are implemented.</p><p>Export to both flat and hierarchical file structures is supported. The export is only available in export format version 2.0. The import format is determined automatically during the import.</p></td><td>These features were not provided. External reports and data processors could only be saved in binary format.</td><td>Extended capabilities for external report and data processor operations in scenarios that use external version control systems. The option to use external tools for creating and editing external reports and data processors is implemented.</td></tr><tr title="Версия 8.3.8" class="compat tag_43 tag_1"><td><a name="4ef24c20-7e47-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>For dynamic lists, support of batch queries is implemented. The dynamic list query builder does not support editing batch queries.<p>This change is not implemented in 8.3.7 repository compatibility mode.</p></td><td>Dynamic lists did not support batch queries.</td><td>Extended dynamic list capabilities.</td></tr><tr title="Версия 8.3.8" class="tag_20"><td><a name="bed7d463-9d86-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the Syntax Assistant, more information is added to the description of the HTTP service request handler method. This includes the parameter type and the return value type.</td><td>In the Syntax Assistant, some information was missing from the description of the HTTP service request handler method. It did not provide the parameter type and the return value type.</td><td>Easier developer access to critical information.</td></tr><tr title="Версия 8.3.8" class="compat tag_64 tag_115 tag_1"><td><a name="85b61294-d3ed-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For the <span class="term">StyleColors</span><span class="term"> </span>system enumeration, the following values are implemented:<ul><li><span class="term">ButtonBorderColor</span> (for form buttons and command bar buttons)</li><li><span class="term">TableHeaderBackC</span><span class="term">olor</span> (for table header background)</li><li><span class="term">TableHeaderTextColor</span> (for table header text)</li><li><span class="term">TableFooter</span><span class="term">BackC</span><span class="term">olor</span> (for table footer background)</li><li><span class="term">TableFooter</span><span class="term">TextColor</span> (for table footer text)</li></ul></td><td>The following values of the <span class="term">StyleColors</span><span class="term"> </span>system enumeration were used to format form items:<ul><li><span class="term">BorderColor</span> (for form buttons and command bar buttons)</li><li><span class="term">ButtonBackColor</span> (for table header background)</li><li><span class="term">ButtonTextColor</span> (for table header text)</li><li><span class="term">ButtonBackColor</span> (for table footer background)</li><li><span class="term">ButtonTextColor</span> (for table footer text)</li></ul></td><td>Extended style item usage options.</td></tr><tr title="Версия 8.3.8" class="compat tag_64 tag_115 tag_1"><td><a name="d11e7f79-dc62-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The sizes of form buttons and command bar buttons are changed.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>Form buttons and command bar buttons had different sizes.</td><td>Improved button layout.</td></tr><tr title="Версия 8.3.8" class="tag_17"><td><a name="0a79ea88-0085-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>For the <span class="term">&lt;CALL</span><span class="term">&gt;</span> technological log event, the <span class="term">Usr</span> property is implemented. It stores the name of the authenticated infobase user.</td><td>The <span class="term">Usr</span> property of the <span class="term">&lt;CALL</span><span class="term">&gt;</span> technological log event was not available,</td><td>The <span class="term">&lt;CALL&gt;</span> technological log event is more informative now.</td></tr><tr title="Версия 8.3.8" class="tag_41"><td><a name="131de15e-11df-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>
<p>For the <span class="interface">co</span><span class="interface">nf.cfg</span> configuration file, the <span class="term">FileNamesEncodingInZipFile </span>parameter is implemented. It specifies the file name encoding in 1C:Enterprise-generated ZIP archives. It can have one of the following values: <span class="term">UTF8</span> (UTF8 only) and <span class="term">OSEncodingWithUTF8</span> (both UTF8 and the operating system encoding).
If the parameter value is <span class="term">UTF8</span>, the <span class="term">ZipFileReader </span>object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, display file names with non-English characters inside the archives incorrectly. The built-in decompression program from OS X displays such file names correctly.</p><p>If the parameter value is <span class="term">OSEncodingWithUTF8</span>, the built-in decompression program from OS X displays file names with non-English characters incorrectly but other decompression programs display them correctly.</p></td><td>File names in 1C:Enterprise-generated ZIP archives were always stored in both UTF8 encoding and operating system encoding.</td><td>The option to specify encoding for the file names in 1C:Enterprise-generated ZIP archives is implemented.</td></tr><tr title="Версия 8.3.8" class="tag_19 tag_29"><td><a name="22114fcc-6842-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>IBM DB2 11.1 DBMS is now supported.</td><td>IBM DB2 11.1 DBMS was not supported.</td><td>IBM DB2 11.1 DBMS is now supported.</td></tr><tr title="Версия 8.3.8" class="tag_10"><td><a name="2b43d13c-7996-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The administration console utility (<span class="interface">1cv8a</span>) is available. It includes some of verification and repair features that are available in Designer. You can use the utility to speed up certain operations:<ul><li>Verify and repair exchange plan node tables</li><li>Verify and repair hash fields in infobase tables</li></ul><p>The utility is available for the following operating systems:</p><ul><li>Windows. Installed as a part of the <span class="interface">Administration of 1C:Enterprise server </span>component.</li><li>Linux. Installed unconditionally as a part of the <span class="interface">1c_enterprise83-client-8.3.*</span> package that depends on the <span class="interface">1c_enterprise83-server-8.3.*</span> package of the same version.</li><li>macOS. Installed unconditionally as a part of 1C:Enterprise.</li></ul></td><td>This feature was not provided.<p>Some of the utility features were available as part of the <span class="interface">Verify and repair</span> feature in Designer but they took much more time.</p></td><td>Now you do not have to start Designer to fix some of the infobase issues. This can save valuable time because the utility only processes objects with issues detected and performs a limited set of repair operations.</td></tr><tr title="Версия 8.3.8" class="tag_69 tag_38 tag_10"><td><a name="30d3ce0a-953a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Unsafe operation protection is implemented. When a potentially unsafe operation is attempted, 1C:Enterprise displays a warning that contains its description and why it might be unsafe. Potentially unsafe operations include:<p> </p><ul><li>Loading an external report, an external data processor, or a configuration extension</li><li>Loading or updating a configuration or an extension</li><li>Attempting the following operations from an external report, an external data processor, or a configuration extension:</li><ul><li>Run an operating system command</li><li>Manage users</li><li>Load an add-in</li></ul></ul><p>You have the option to allow or deny a potentially unsafe operation. In some scenarios you have to retry the operation after allowing it.</p><p>When you load or update a configuration from a <span class="interface">.cfu</span><span class="interface"> </span>file, 1C:Enterprise adds the warning to existing Designer dialog boxes.</p><p>The <span class="term">InfoBaseUser</span><span class="term">.</span><span class="term">UnsafeActionProtection</span> property is implemented. The <span class="term">ConfigurationExtension</span><span class="term">.</span><span class="term">UnsafeActionProtection </span>property is implemented. For the <span class="term">Connect()</span> method of <span class="term">ExternalReports</span> and <span class="term">E</span><span class="term">xternalDataProcessors</span> objects, the <span class="term">UnsafeActionProtection</span> parameter is implemented. In the configuration extension management dialog boxes (both in Designer and in the standard functions), the <span class="interface">Unsafe operation protection</span> check box is implemented.</p><p>You can define the list of infobases where unsafe operation protection is disabled. For the <span class="interface">conf.cfg</span> file, the <span class="term">Di</span><span class="term">sableUnsafeActionProte</span><span class="term">ction</span> parameter is implemented.</p></td><td>Unsafe operation protection was not available. Administrators could prohibit running external reports or data processors using security profiles.</td><td>Increased security when running potentially unsafe script.</td></tr><tr title="Версия 8.3.8" class="tag_69 tag_134 tag_80 tag_10"><td><a name="9725be56-fdbb-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 134); return false;">Configuration extensions,</a>.<br><a href="#" onclick="onTagClick(this, 80); return false;">External reports and data processors</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>In the thin and thick client applications, if unsafe operation protection triggers, once the unsafe operation is completed, the application execution continues as if it was not paused. If the user prohibits the unsafe operation, the platform generates an exception that can be caught using 1C:Enterprise script.<p>The web client and server behavior is not changed.</p></td><td>In the thin and thick client applications, if unsafe operation protection triggered during the execution of the client script, the platform paused the script execution and prompted the user to allow or prohibit the operation. Regardless of the user choice, the script execution was not resumed and the user had to restart the operation.</td><td>Simplified application behavior in scenarios where unsafe operation protection triggers in a thin or thick client application.</td></tr><tr title="Версия 8.3.8" class="tag_29"><td><a name="bd69090e-9b99-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>1C:Enterprise now supports Microsoft Windows Server 2016 (x86-64).</td><td>1C:Enterprise did not support Microsoft Windows Server 2016 (x86-64).</td><td>The list of supported operating systems is extended.</td></tr><tr title="Версия 8.3.8" class="tag_29"><td><a name="3cd7805b-b08c-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Astra Linux Special Edition 1.5 is supported.</td><td>This release was not supported.</td><td>New Linux release is supported.</td></tr></table><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="5a3fed9e-6292-11e5-a3f7-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.8" class="tag_96"><td><a name="0daa7936-6da2-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In the <span class="interface">Taxi</span> interface, the appearance of scroll bars is changed.</td><td>In the <span class="interface">Taxi</span> interface, scroll bars had a different appearance.</td><td>Better visibility of scroll bars in managed forms.</td></tr><tr title="Версия 8.3.8" class="tag_96"><td><a name="db2a616c-6da2-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In the search dialog box that can be opened from a managed form table linked to a <span class="term">FormDataCollection</span> attribute, the order of fields is changed: the <span class="interface">Search in </span>field comes before the <span class="interface">Find </span>field.</td><td>In the search dialog box that could be opened from a managed form table linked to a <span class="term">FormDataCollection</span> attribute, the <span class="interface">Find </span>field came before the <span class="interface">Search in </span>field.</td><td>Unified look and feel of search dialog boxes in managed form fields linked to various data types.</td></tr><tr title="Версия 8.3.8" class="tag_115"><td><a name="68f1e0b2-6da8-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the <span class="interface">Taxi </span>interface, the following keyboard shortcuts are implemented for the managed form navigation panel:<ul><li>Go to panel: <span class="interface">Alt + 4</span>.</li><li>Go to next/previous panel item: <span class="interface">Tab/Shift + Tab</span> or <span class="interface">Left Arrow/Right Arrow</span>. Upon reaching the first/last item, the focus does not move to the last/first item.</li><li>Go to the first panel item: <span class="interface">Home</span>.</li><li>Go to the last panel item: <span class="interface">End</span>.</li><li>Exit panel navigation mode: <span class="interface">Esc</span>.</li></ul></td><td>In the <span class="interface">Taxi </span>interface, keyboard shortcuts for moving through navigation panel items were not available.<p>
</p></td><td>Improved usability of 1C:Enterprise client applications that use the <span class="interface">Taxi </span>interface.</td></tr><tr title="Версия 8.3.8" class="tag_96"><td><a name="ed7ba08c-6e6b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In the <span class="interface">Taxi </span>interface, in dynamic lists, the vertical scrollbar is replaced with a set of buttons (go to beginning, go to end, page up, and page down) located at the right bottom part of the table linked to a dynamic list.</td><td>Tables linked to dynamic lists had vertical scroll bars that did not provide comfortable navigation.</td><td>Improved navigation in dynamic lists.</td></tr><tr title="Версия 8.3.8" class="tag_96 tag_43"><td><a name="97bda4ed-6e72-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The following commands are added to the context menu of a table linked to a dynamic list whose main table is a document list or a document journal: <span class="interface">Post </span>and <span class="interface">Clear posting</span>.</td><td>For a table linked to a dynamic list whose main table was a document list or a document journal, the <span class="interface">Post </span>and <span class="interface">Clear </span><span class="interface">posting </span>commands were only available on the <span class="interface">More </span>menu.<p>
</p></td><td>Simplified posting and clearing posting in dynamic lists.</td></tr><tr title="Версия 8.3.8" class="tag_96 tag_43"><td><a name="3cdbbb6f-6e73-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The context menu of a managed form table that is linked to the main attribute of a managed list form having the <span class="interface">Generate </span>command now includes a <span class="interface">Generate </span>submenu.</td><td>The generation commands were only available in the command bar of a managed form table linked to the main attribute of a managed list form.</td><td>Simplified document generation based on dynamic lists.<p>
</p></td></tr><tr title="Версия 8.3.8" class="tag_96"><td><a name="b1099fdb-6e74-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In the thick and thin clients, in the managed mode, the option to add a search string to the system command area is removed from all interface modes.</td><td>The option to add a search string to a system command area was available.</td><td>Removed a feature that was no longer in use.</td></tr><tr title="Версия 8.3.8" class="compat tag_96 tag_1"><td><a name="fbb9f949-6e76-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The system command area displays the current user name. It is a hyperlink that opens a dialog box with the user info. The dialog box includes the option to log out of the client application. If the user is authenticated using OpenID, this also cancels OpenID authentication (so that a single command both exits the application and cancels OpenID authentication). If the infobase does not have users, the user name is not displayed.<p>The option to specify the URL that is opened after the exit from the web client in the .vrd file is implemented (you can also specify the URL in the publishing settings dialog box in Designer, and then the platform writes it to the .vrd file). The <span class="term">&lt;exitURL&gt;</span> element of the <span class="term">&lt;point&gt;</span> element of <span class="interface">default.vrd</span> file is implemented.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>The exit command and the cancel OpenID authentication command were available on the <span class="interface">File </span>menu.</td><td>Client application behavior is closer to the standard behavior of web applications.</td></tr><tr title="Версия 8.3.8" class="tag_28 tag_115"><td><a name="a5ba77a6-71b7-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the web client, streamlined the undo operation in text document fields and input fields.<p>In Safari web browser for Apple iPad, the undo operation is applied to an entire word (and not to each of its characters), just like it is implemented in other web browsers.</p></td><td>In the web client, the undo and redo operations were not optimal.</td><td>Improved usability of text operations in the web client.</td></tr><tr title="Версия 8.3.8" class="tag_14"><td><a name="f3a75638-740a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>On Windows 7 and later and on Linux with Unity desktop shell, support of jump lists is implemented. The last used infobases are automatically added to a jump list, so that a user can open these infobases without opening the 1C:Enterprise start dialog box.<p>On Windows 7 and later, the option to define buttons that are displayed in the application preview taskbar window (using 1C:Enterprise script) is implemented. This is similar to Windows Media Player buttons in its preview window.</p><p>On Windows 7 and later and on Linux with Unity desktop shell, the option to define a picture or a number to be displayed at the bottom right corner of the application taskbar icon (using 1C:Enterprise script) is implemented.</p><p>On Windows XP and later and on Linux with Unity desktop shell, the option to enable blinking of a taskbar application icon (using 1C:Enterprise script) is implemented.</p><p>The <span class="term">OSTaskb</span><span class="term">arManager</span> object is implemented.
</p></td><td>This feature was not provided.</td><td>Inproved usability of 1C:Enterprise applications on some operating systems.</td></tr><tr title="Версия 8.3.8" class="tag_14 tag_96"><td><a name="6035b990-7413-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>1C:Enterprise user interface now has screen reader support, which provides accessibility for blind and visually impaired people. This option is available on Windows XP or later. It uses the NVDA screen reader software (<a href="http://www.nvaccess.org/" target="_blank">read more</a>).<p>Screen reader support is only available for managed forms, in the thick and thin clients that use the <span class="interface">Taxi </span>interface.</p></td><td>This feature was not provided.</td><td>Improved 1C:Enterprise usability for blind and visually impaired people due to screen reader support.</td></tr><tr title="Версия 8.3.8" class="tag_43"><td><a name="6bc5490f-8c68-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the <span class="interface">Change form</span> command on the <span class="interface">More </span>menu) is implemented.<p>Adding subordinate fields is available for fields whose type includes at least one reference type.</p></td><td>In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the <span class="interface">Change form</span> command on the <span class="interface">More </span>menu) was not available.</td><td>Improved data display capabilities in dynamic lists.</td></tr><tr title="Версия 8.3.8" class="tag_28 tag_78"><td><a name="18b7388c-8c6f-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>In the web client, a <span class="term">CreateDirectory()</span> or <span class="term">BeginCreatingDirectory() </span>method call includes the question to the user: <span class="interface">Do you want to create the DirectoryName directory?</span><p>In the <span class="term">RequestUserPermission</span><span class="term">()</span><span class="term"> </span>and <span class="term">BeginRequestingUserPermission() </span>method calls, this confirmation is included in the final question to the user (provided that the confirmation is needed).</p></td><td>In the web client, directories were created without user confirmation.</td><td>The platform behavior conforms to the general security recommendations for file operations in the web client.</td></tr></table><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="5a3fed9f-6292-11e5-a3f7-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.8" class="tag_6"><td><a name="71027ed6-6da1-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Optimized operations with session data. The lags experienced by end users during the periods of high load on the session data storage in client/server mode are eliminated.</td><td>Operations with session data required optimization. End users experienced lags during the periods of high load on the session data storage in client/server mode.</td><td>Improved 1C:Enterprise usability.</td></tr><tr title="Версия 8.3.8" class="tag_96"><td><a name="63bb3cd8-7190-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The impact on the total number of opened forms to the opening of new forms is reduced.</td><td>The impact on the total number of opened forms to the opening of new forms was significant.</td><td>Streamlined form opening when many other forms are open.</td></tr><tr title="Версия 8.3.8" class="compat tag_45 tag_1"><td><a name="581ee5e1-7279-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In the query language, <span class="term">&lt;EXPRESSION&gt; OR TRUE</span> expressions are optimized.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>The query language did not feature additional optimization of query texts.</td><td>In some scenarios, the optimization increases the performance of dynamic lists and access restriction queries because the DMBS generates a simpler query plan.</td></tr><tr title="Версия 8.3.8" class="tag_20"><td><a name="df13b8d6-73eb-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The dump configuration to files and restore configuration from files operations are optimized for scenarios where the configuration includes a large number of managed forms.</td><td>The performance of dump configuration to files and restore configuration from files operations was insufficient.</td><td>In scenarios where the configuration is stored in an external system, improved performance of data exchange between the infobase and that system.</td></tr><tr title="Версия 8.3.8" class="tag_117"><td><a name="9da52991-7417-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>File infobase operations are optimized in the scenario where all of the following conditions are met:<ul><li>A single client application accesses the infobase (Designer counts as a client application, too).</li><li>The client application and the database are located on different computers.</li><li>Both computers support SMB 2.1 protocol (operating system Windows 7 or later).</li><li>A significant number of database write transactions are performed.</li></ul></td><td>In the specified scenario, the file infobase performance was insufficient.</td><td>Improved performance of database configuration updates for file infobases in the scenario where Designer and the database are located on different computers.</td></tr><tr title="Версия 8.3.8" class="tag_105"><td><a name="e438f01a-741a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>The performance of initial infobase image creation is improved.<p>The performance or reading records from independent nonperiodic information registers during the initial image creation is improved. </p></td><td>The performance of initial infobase image creation was insufficient.</td><td>Faster creation of subordinate node infobases in distributed infobases.</td></tr><tr title="Версия 8.3.8" class="tag_19"><td><a name="910a6345-7639-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized.</td><td>The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient.</td><td>Improved performance of temporary table operations.</td></tr><tr title="Версия 8.3.8" class="compat tag_19 tag_1"><td><a name="d45df4ac-765e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>In client/server mode with Oracle Database DBMS, requests containing <span class="term">… IN (&amp;ValueList)</span> have a different execution algorithm when applied to lists containing more than 100 records.<p>This change is not implemented in 8.3.7 compatibility mode.</p><p>
</p><p>
</p><p>
</p></td><td>In client/server mode with Oracle Database DBMS, requests containing <span class="term">… IN (&amp;ValueList)</span> had a different execution algorithm when applied to lists containing more than 1000 records.</td><td>Improved performance for some scenarios that include access to Oracle Database DBMS.</td></tr><tr title="Версия 8.3.8" class="tag_10 tag_17 tag_6 tag_19"><td><a name="61a36f53-741a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Getting DBMS lock data is optimized. The time required for getting the data does not depend on the number of infobases in the cluster.<p>The server cluster service that collects DBMS lock data is implemented. It is named <span class="term">AuxiliaryService</span> (<span class="interface">Utility</span><span class="interface"> cluster</span><span class="interface"> </span><span class="interface">ser</span><span class="interface">vice</span>).</p><p>The option to manage the collection of DBMS lock data is implemented in the technological log (<span class="term">&lt;DBMSLOCKS</span><span class="term">&gt;</span> element). Enabling the data collection increases the DBMS load.</p></td><td>The time required for getting DBMS lock data depended on the number of infobases in the cluster.<p>The option to manage the collection of DBMS lock data using the technological log was not available.</p><p>
</p></td><td>Extended database diagnostics.</td></tr><tr title="Версия 8.3.8" class="compat tag_10 tag_117 tag_1"><td><a name="26834ff8-7419-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>In the file mode, infobase operations are optimized. To support the optimization, the file database data storage format is updated to new version 8.3.8 format. The option to change the page size of the infobase file (<span class="interface">1Cv8.1CD</span>) is implemented. The page size can have one of the following values: 4096, 8192, 16384, 32768, or 65536 bytes.<p>If you set the page size for a database having version 8.3.8 format to 8192 bytes or more, the internal database file size cannot exceed 6 GB.</p><p>1C:Enterprise version 8.3.8 can open infobases created in the earlier 1C:Enteprise versions (and having version 8.2.14 database format) without changing their compatibility modes.</p><p>By default, new infobases have version 8.2.14 format. For the <span class="interface">conf.cfg</span> file, the <span class="term">DBFormatVersion</span> parameter is implemented. It defines the format of newly created file-mode infobases.</p><p>For the infobase connection string, the <span class="term">DBFormat</span> and <span class="term">DBPageSize</span> parameters are implemented. They define the format and page size for new infobases. </p><p>To migrate data between infobase formats, you can use a <span class="interface">.dt</span> file (provided that the target infobase has the required format) or convert the infobase file using <span class="interface">cnvdbfl</span> utility. The <span class="interface">cnvdbfl</span> utility can change the infobase file page size during the conversion.</p></td><td>All infobases had the same format (version 8.2.14). Pages of the infobase file had fixed size: 4096 bytes. The option to change the size was not available. The internal database file size could not exceed 4 GB.</td><td>For infobases with large page sizes, the infobase opening time is reduced and the performance of some queries is improved.</td></tr><tr title="Версия 8.3.8" class="tag_6"><td><a name="11c5a1ea-8799-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Reduced size of session data on the hard disk. Session data is stored in the server cluster in compressed form.</td><td>Session data was stored in the server cluster in uncompressed form.</td><td>The space occupied by internal cluster data is reduced. Some of the internal cluster operations are streamlined. </td></tr><tr title="Версия 8.3.8" class="tag_14"><td><a name="40de4056-a23d-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Faster thin client startup in the file mode.</td><td>The performance of the thin client startup in the file mode was insufficient.</td><td>Faster thin client startup in the file mode.</td></tr><tr title="Версия 8.3.8" class="tag_117"><td><a name="ced2a7bb-3237-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>Restructuring of separated hierarchical catalogs is optimized.</td><td>The performance of restructuring separated hierarchical catalogs was insufficient.</td><td>The performance of restructuring separated hierarchical catalogs is improved.</td></tr><tr title="Версия 8.3.8" class="tag_117"><td><a name="07fefd45-3792-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>The RAM usage is reduced for restructuring a database that contains large amounts of binary data in file mode.</td><td>Restructuring a database that contained large amounts of binary data in file mode might result in an unexpected shutdown due to insufficient RAM.</td><td>Improved system stability for database restructuring in file mode.</td></tr><tr title="Версия 8.3.8" class="tag_96 tag_6"><td><a name="1624bada-117b-11e8-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>For 1C:Enterprise installations that use Microsoft SQL Server, improved performance of opening user work history.<p>The performance improvement will take effect after you perform the following steps: </p><ul><li> Set the<span class="interface"> compatibility mode</span> to <span class="interface">version 8.3.8</span> or later. </li><li> Perform complete infobase restructuring or dump the infobase to a .dt file and then restore it.</li></ul></td><td>For 1C:Enterprise installations that used Microsoft SQL Server, opening user work history was slower.</td><td>Improved performance of opening user work history.</td></tr></table><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="5a3feda0-6292-11e5-a3f7-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.8" class="tag_116 tag_10"><td><a name="3ec667ef-62c8-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The command-line utility for software license management (which includes license activation, getting license data, getting the list of licenses, and more) is implemented. The utility is delivered in two distribution packages, which are located in the <span class="interface">ExtDst</span> subdirectory of the platform version directory (provided that the thick client or 1C:Enterprise server is installed for this platform version). The utility is not installed automatically. In order to use it, you have to install it first. The utility is available for Windows operating system (both architectures) and for Linux operating system (both architectures, as .deb- and .rpm packages).<p>To access the utility, use the <span class="interface">ring </span><span class="interface">license</span> command. The utility requires Java version 8. The detailed utility description is available in 1C:Enterprise documentation.</p></td><td>Software license activation was only available in the interactive mode. No other software management options were available.</td><td>Simplified software license management on the end-user computer.</td></tr><tr title="Версия 8.3.8" class="compat tag_115 tag_1"><td><a name="40003f62-6da5-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>During the automatic generation of managed form items, the names of items that match the <span class="term">CreateByParameter</span> and <span class="term">ShowInList </span>commands are generated according to the following template: <span class="term">&lt;Form&gt;&lt;CommandName&gt;&lt;ConfigurationObjectName&gt;</span><span class="term">.</span><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>During the automatic generation of managed form items, the names of items that matched the <span class="term">CreateByParameter</span> and <span class="term">ShowInList </span>commands were generated according to the following template: <span class="term">&lt;Form&gt;&lt;CommandName&gt;&lt;Sequential</span><span class="term">Number</span><span class="term">&gt;</span><span class="term">.</span><p>
</p></td><td>Better usability for applied solution developers.</td></tr><tr title="Версия 8.3.8" class="tag_115"><td><a name="7dc8c9b9-6e7a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In a managed form, the width of a drop-down list of an input field is adjusted according to the width of data displayed in that list.<p>Pressing the <span class="interface">Home </span>or <span class="interface">End </span>key (as a single key or with any modifier keys) is handled directly in the input field.</p></td><td>In a managed form, each drop-down list of an input field had a fixed width set by the platform or by a developer.<p>Pressing the <span class="interface">Home </span>or <span class="interface">End </span>key (as a single key or with any modifier keys) in an input field had no effect.</p></td><td>Improved usability of input fields in drop-down lists.</td></tr><tr title="Версия 8.3.8" class="tag_20"><td><a name="e17b27e2-719f-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The following features are implemented in the compare and merge modules window : <ul><li>Module line numbers</li><li>Synchronization between the comparison window and the merge result editor window</li><li>The editor window functionality is closer to that of 1C:Enterprise script editor window</li><li>Context help is available in the editor window. The context includes the main configuration (before merging) and the current module (after merging)</li><li>The window title displays the module name</li></ul><p>The following features are implemented in the window that displays the result of merging with a third-party tool:</p><ul><li>The editor window functionality is closer to that of 1C:Enterprise script editor window</li><li>Context help is available in the editor window. The context includes the main configuration (before merging) and the current module (after merging)</li></ul><p>When a supported configuration is being updated, the compare and merge configurations window has a new filter option: <span class="interface">Show only properties with merge conflicts</span>. The filter displays the objects that are not merged with a third-party tool.</p></td><td>This feature was not provided.</td><td>Improved usability for developers working on applied solution update functionality.</td></tr><tr title="Версия 8.3.8" class="tag_20"><td><a name="f35ac347-725a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The <span class="interface">Explanat</span><span class="interface">ion </span>field of the property palette displays Russian property names only when the Russian 1C:Enterprise script variant or the Russian platform interface is selected.</td><td>The <span class="interface">Explanat</span><span class="interface">ion </span>field of the property palette always displayed both Russian and English property names.<p>
</p></td><td>Improved Designer usability for English-speaking developers.</td></tr><tr title="Версия 8.3.8" class="tag_28 tag_26"><td><a name="74de8307-727f-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the web client, the option to display a background picture and a pattern in a spreadsheet document cell is implemented.</td><td>In the web client, displaying background pictures and patterns in spreadsheet document cells was not supported.</td><td>Extended spreadsheet document style options in the web client.</td></tr><tr title="Версия 8.3.8" class="compat tag_64 tag_26 tag_1"><td><a name="d85eb9f4-7328-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In spreadsheet documents exported to PDF format, font substitution for characters that are not available in the current font is implemented.<p>This change is not implemented in 8.3.7 compatibility mode.</p><p>
</p></td><td>In spreadsheet documents exported to PDF format, characters that were not available in the current font were displayed as missing characters (squares).</td><td>In spreadsheet documents exported to PDF format, non-English characters are displayed correctly.</td></tr><tr title="Версия 8.3.8" class="compat tag_26 tag_1"><td><a name="fef2f4cd-732d-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When a spreadsheet document is exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells is implemented.<p>This option is not available when exporting spreadsheet documents to XLS (Microsoft Excel 95) format.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>When a spreadsheet document was exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells was not supported.</td><td>Better conversion of spreadsheet documents to Microsoft Excel and ODS formats.</td></tr><tr title="Версия 8.3.8" class="tag_38"><td><a name="827f1695-7330-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>When an attribute of composite type that does not include references to configuration objects is adopted, the composite type is fully adopted. During the next adoption attempt, the composite type is supplemented with the set of types from the main configuration.<p>When an attribute of composite type that includes references to configuration objects (nonprimitive types) is adopted, it is adopted as <span class="term">AnyRef</span>. During the next adoption attempt, the <span class="term">AnyRef </span>type is only added if the type is no longer composite and does not include <span class="term">CatalogRef</span>, <span class="term">DocumentRef</span>, and similar types.</p><p>When a configuration extension is attached, the following rules apply:</p><ul><li>If an extension configuration attribute type includes <span class="term">AnyRef</span>, this requires the matching main configuration attribute type to include any reference.</li><li>If an extension configuration attribute type includes <span class="term">CatalogRef</span>, <span class="term">DocumentRef</span>, and similar types, this requires the matching main configuration attribute to include any reference type of that kind.</li></ul><p>If an attribute of composite type cannot include <span class="term">AnyRef </span>type, any composite type adopted for this attribute is adopted with a single <span class="term">Arbitrary </span>type. Such attributes cannot cause configuration extension attachment errors.</p></td><td>When a composite type was adopted, primitive types were always adopted, and a single type from the configuration object reference types was adopted.<p>When a configuration extension was attached, the following rule applied: if an extension attribute type included composite types, this required the matching main configuration attribute to include exactly the same composite types.</p></td><td>Simplified usage of composite types in configuration extensions.</td></tr><tr title="Версия 8.3.8" class="tag_65"><td><a name="c79fd9d4-734c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>During a web service call, if an internal server infrastructure error that is not related to SOAP occurs, the error message contains the correct diagnostics text. The web service call error message is more detailed and can include data from the <span class="term">fault</span><span class="term">factor</span> (<span class="term">Node</span>) and <span class="term">Role</span> tags of the web service response.</td><td>During a web service call, if an internal server infrastructure error that was not related to SOAP occurred, an incorrect error message was displayed, and the information about the actual error cause was lost.<p>The web service call error message did not include additional details from the web service response.</p><p>
</p></td><td>The web service call error message is more detailed, which simplifies error diagnostics.</td></tr><tr title="Версия 8.3.8" class="tag_120"><td><a name="4c0a5784-73e3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>When a client application is started with a file infobase, there is a 2-minute delay before starting the execution of scheduled jobs.</td><td>When a client application was started with a file infobase, there was a 1-minute delay before starting the execution of scheduled jobs.</td><td>Faster startup of client applications in file mode.</td></tr><tr title="Версия 8.3.8" class="tag_81"><td><a name="d6cc4ada-73ed-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>When a user disables publishing to a web server from Designer, they are prompted to restart the web server.</td><td>When a user disabled publishing to a web server from Designer, they were not prompted to restart the web server.</td><td>Users are given better understanding of the disable publishing operation, since the publishing is actually disabled when the server is restarted.</td></tr><tr title="Версия 8.3.8" class="tag_20"><td><a name="6c5369d5-763c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer, the option to customize the background of the context method parameter help is implemented.<p>In the context help, links to the Syntax Assistant have the <span class="interface">Identifiers </span>color and normal text has the <span class="interface">Miscellaneous </span>color.</p></td><td>In the context help, links to the Syntax Assistant had the default <span class="interface">Identifiers </span>color and normal text had the default <span class="interface">Miscellaneous </span>color.</td><td>You can customize the context help of method parameters to make it readable when the module editor color scheme has dark background.</td></tr><tr title="Версия 8.3.8" class="compat tag_56 tag_65 tag_1"><td><a name="1146c4ba-766b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>In the XDTO model, new properties are implemented. They ensure correct processing of XSD schemas with any combinations of the following attribute values: <span class="term">elementFormQualified</span> (<span class="interface">Qualified element form</span> package property), <span class="term">attributeFormQualified</span> (<span class="interface">Qualified attribut</span><span class="interface">e form </span>package property), and <span class="term">form</span> (property of the <span class="interface">Qualified </span>element).<p>The XDTO package editor provides the option to view and edit the new properties. In <span class="interface">V</span><span class="interface">ersion 8.3.7</span> or earlier compatibility mode, the new properties have their default values.</p></td><td>When processing XSD schemas, the XDTO model ignored actual values of <span class="term">elementFormDefault</span> and <span class="term">attributeFormDefault</span> attributes. It also ignored the <span class="term">form </span>attribute of XSD schema elements and attributes. Instead, it always used the following values:<ul><li><span class="term">elementFormDefault</span> was always <span class="term">qualified</span>.</li><li><span class="term">attributeFormDefault</span> was always <span class="term">unqualified</span>.</li></ul><p>
</p></td><td>Extended list of web services that are compatible with 1C:Enteprise as they are, without any manual corrections to their descriptions.</td></tr><tr title="Версия 8.3.8" class="tag_10"><td><a name="7273b498-7be9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The wizards used to add and edit infobases are refactored, the number of wizard pages is reduced.<p>Automatic detection of the infobase connection type is implemented, based on the string stored in the clipboard or the string entered in the <span class="interface">S</span><span class="interface">pecify infobase name</span> field. This includes the detection of the path to a file infobase or the URL for accessing an infobase running on a web server. Once the infobase type is detected, all of the related wizard fields are filled in.</p></td><td>The wizards used to add and edit infobases were more complex and had more pages.</td><td>Simplified adding of infobases to the list.</td></tr><tr title="Версия 8.3.8" class="tag_115"><td><a name="b8d8f0ba-7c96-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If an input field of a managed form displays <span class="term">ValueList </span>data, the value list form that is opened for editing the data gets the following properties from the input field:<ul><li><span class="term">ChoiceParameters</span>, supplemented with values based on the <span class="term">ChoiceParameterLinks</span><span class="term"> </span>property</li><li><span class="term">ChoiceForm</span> (in the web client)</li><li><span class="term">ChoiceFoldersAndItems</span> (in the web client)</li><li><span class="term">Mask</span></li><li><span class="term">EditFormat</span></li><li><span class="term">QuickChoice</span></li><li><span class="term">TypeLink</span></li></ul></td><td>If an input field of a managed form displayed <span class="term">ValueList </span>data, the value list form that was opened for editing the data received the following properties from the input field:<ul><li><span class="term">ChoiceParameters</span>, not supplemented with values based on the <span class="term">ChoiceParameterLinks</span><span class="term"> </span>property</li><li><span class="term">ChoiceForm</span> (thin client only)</li><li><span class="term">ChoiceFoldersAndItems</span> (thin client only)</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="tag_21 tag_107 tag_43"><td><a name="b5239125-7cb4-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 107); return false;">Input by string</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Input by string and full-text search in dynamic lists find data that is not yet indexed for the full-text search.</td><td>Input by string and full-text search in dynamic lists did not find data that was not yet indexed for the full-text search.</td><td>Data that is not yet indexed for the full-text search is included in full-text search results and input by string results.</td></tr><tr title="Версия 8.3.8" class="compat tag_115 tag_1"><td><a name="2c100141-7d8c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the <span class="interface">Taxi </span>interface, the appearance of managed form buttons and command bar buttons is changed.<p>For the <span class="term">CommandBarButton</span><span class="term"> </span>and <span class="term">CommandBarHyperlink </span>buttons, support of the following properties is implemented: <span class="term">BackColor</span>, <span class="term">TextColor</span>, <span class="term">Font</span>, <span class="term">BorderColor </span>(except <span class="term">CommandBarHyperlink </span>buttons). For form group extension submenus, support of the following properties is implemented: <span class="term">BorderColor</span>, <span class="term">BackColor</span>, <span class="term">TitleTextColor</span>, and <span class="term">TitleFont</span>. This change is not implemented in version 8.3.7 compatibility mode and in version 8.2 interface compatibility mode.</p><p>For the standard <span class="term">Copy </span>command of dynamic list table extension:</p><ul><li>The <span class="interface">Auto </span>value of <span class="term">Representation </span>property is equivalent to <span class="interface">Picture</span>.</li><li>The <span class="interface">Auto </span>value of <span class="term">OnlyInAllActions </span>property is equivalent to <span class="interface">No</span>.</li></ul><p>For <span class="term">MoveUp</span><span class="term"> </span>and <span class="term">MoveDown </span>managed form table commands, the <span class="interface">Auto </span>value of the <span class="term">OnlyInAllActions </span>property is equivalent to <span class="interface">No</span>. These commands are included in a compact button group.
</p><p>This change is not implemented in version 8.3.7 compatibility mode.</p><p>In version 8.3.7 compatibility mode with compact interface the button height in the thin client differs from the button height in the web client.</p></td><td>In the <span class="interface">Taxi </span>interface, the appearance of managed form buttons and command bar buttons was different.<p>The <span class="term">CommandBarButton</span><span class="term"> </span>buttons had <span class="term">BackColor</span>, <span class="term">TextColor</span>, <span class="term">Font</span>, and <span class="term">BorderColor </span>properties, which were never used. Form group extension submenus had <span class="term">BorderColor</span>, <span class="term">BackColor</span>, <span class="term">TitleTextColor</span>, and <span class="term">TitleFont</span> properties, which were never used.</p><p>For the standard <span class="term">Copy </span>command of dynamic list table extension:</p><ul><li>The <span class="interface">Auto </span>value of <span class="term">Representation </span>property was equivalent to <span class="interface">Text</span>.</li><li>The <span class="interface">Auto </span>value of <span class="term">OnlyInAllActions </span>property was equivalent to <span class="interface">Yes</span>.</li></ul><p>For <span class="term">MoveUp</span><span class="term"> </span>and <span class="term">MoveDown </span>managed form table commands, the <span class="interface">Auto </span>value of the <span class="term">OnlyInAllActions </span>property was equivalent to <span class="interface">Yes</span>.</p></td><td>Improved form creation capabilities in the <span class="interface">Taxi </span>interface.<p>The default location of some frequently used buttons (<span class="interface">Copy </span>in dynamic lists and row movement commands in other tables) changed from the <span class="interface">More </span>menu to the command bar.</p></td></tr><tr title="Версия 8.3.8" class="compat tag_115 tag_1"><td><a name="153f2095-7d67-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The option to display command bar commands as hyperlinks is implemented. Pop-up menus do not support displaying commands as hyperlinks. For the <span class="term">FormButtonType</span><span class="term"> </span>enumeration, the <span class="term">C</span><span class="term">ommandBarHyperlink </span>value is implemented. In 8.3.7 compatibility mode, the <span class="term">FormButtonType.</span><span class="term">C</span><span class="term">ommandBarHyperlink</span> value is treated as <span class="term">FormButtonType.</span><span class="term">C</span><span class="term">ommandBarButton</span>.<p>In the <span class="interface">Taxi</span><span class="interface"> </span>interface, the option to set horizontal picture alignment for managed form buttons is implemented. Pop-up menus do not support this feature. For managed form buttons, the <span class="term">PictureLocation</span><span class="term"> </span>property is implemented. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode.</p><p>The option to set command bar button spacing is implemeneted. Managed form group extension for a button group is implemented. Pop-up menus do not support this feature. The <span class="term">ButtonGroupRepresentation </span>system enumeration is implemented. In 8.3.7 compatibility mode and version 8.2 interface compatibility mode, the button spacing value is ignored.</p><p>The option to set button shape (except pop-up menu buttons) is implemented. For managed form buttons and form group extensions for popups, the <span class="term">Shape </span>property is implemented. Pop-up menu commands do not support this property. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode.</p><p>The option to set managed form button shape is implemented. For managed form buttons and form group extensions for popups, the <span class="term">ShapeRepresentatio</span><span class="term">n </span>property is implemented. The <span class="term">ButtonShapeRepresentation </span>system enumeration is implemented. Pop-up menu commands do not support this feature. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode.</p></td><td>Command bar commands could not be displayed as hyperlinks.<p>The option to set horizontal picture alignment for managed form buttons was not available.</p><p>The option to set command bar button spacing was not available.</p><p>The option to set button shape was not available.</p><p>The option to set command bar button appearance was not available.</p></td><td>More managed form appearance options in the <span class="interface">Taxi </span>interface.</td></tr><tr title="Версия 8.3.8" class="tag_115"><td><a name="9d43fbc2-ba9b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Recommendations about the usage of user messages are added to the documentation. The recommendations are aimed to reduce the chance of situations where users cannot read the displayed messages.</td><td>The documentation did not contain the recommendations aimed to reduce the chance of situations where users cannot read the displayed messages.</td><td>The documentation is improved.</td></tr><tr title="Версия 8.3.8" class="tag_116"><td><a name="3ee0bd4c-ce44-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>Updates of Windows 10 operating system never deactivate software licenses.
</td><td>The software licensing system was not fully compatible with Windows 10. Updates of Windows 10 could deactivate a software license.</td><td>Improved compatibility of the software licensing system with Windows 10.</td></tr><tr title="Версия 8.3.8" class="tag_84"><td><a name="81803859-f4b7-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The Kazakh interface language (language code: <span class="interface">kk</span>) is not supported.</td><td>The Kazakh interface language (language code: <span class="interface">kk</span>) was supported.</td><td>The Kazakh interface language is not supported.</td></tr><tr title="Версия 8.3.8" class="tag_94"><td><a name="b8fb6b44-f814-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 94); return false;">Regional settings</a>.<br></td><td>For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ (Zabaikalye Territory), 27-FZ (Astrakhan Region), 57-FZ (Altai Territory), 58-FZ (Republic of Altai), 59-FZ (Sakhalin Region), 69-FZ (Ulyanovsk Region), 87-FZ (Magadan Region), 109-FZ (Tomsk Region), 271-FZ (Novosibirsk Region), and 395-FZ (Saratov Region). This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.</td><td>The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ, 87-FZ, 109-FZ, 271-FZ, and 395-FZ.</td><td>The time offset changes introduced by the new law are implemented.</td></tr><tr title="Версия 8.3.8" class="tag_26"><td><a name="4afd390b-11e4-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Text copied from Microsoft Excel speadsheet cells is fully pasted to 1C:Enterprise spreadsheet cells, regardless of its length.</td><td>Text copied from Microsoft Excel spreadsheet cells and pasted to 1C:Enterprise spreadsheet cells was cut, only the first 255 characters were copied.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_26 tag_1"><td><a name="d62ed8fd-11eb-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Improved processing of data having date and time format during the import from Microsoft Excel:<ul><li>For standard Microsoft Excel formats, matching 1C:Enterprise format strings are applied.</li><li>1C:Enterprise format strings are defined based on the locale codes explicitly specified in Microsoft Excel format strings.</li><li>The date type uses the first short date format separator found in the infobase.</li><li>Dates where the month is specified by its first letter are converted to 1C:Enteprise dates having short month presentation.</li></ul><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>Processing of data having date and time format during the import from Microsoft Excel was performed as follows:<ul><li>A fixed list of standard Microsoft Excel formats was applied.</li><li>Locale codes explicitly specified in Microsoft Excel format strings were ignored. The current infobase settings were used instead.</li><li>The date type always used the slach (/) separator.</li><li>Dates where the month was specified by its first letter were converted to dates having full month presentation.</li></ul></td><td>Improved accuracy of date and time import from Microsoft Excel.</td></tr><tr title="Версия 8.3.8" class="tag_65"><td><a name="87157d38-6aae-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>For configurations that include HTTP services, setting compatibility mode to <span class="interface">Version 8.3.4</span> or earlier is allowed.<p>If your configuration includes HTTP services and you previously opened it with 1C:Enterprise Designer 8.3.4, when you open it with 1C:Enterprise 8.3.8, perform the following steps:</p><ul><li>Create any configuration object.</li><li>Save the infobase configuration.</li><li>Delete that configuration object.</li><li>Save the infobase configuration.</li></ul></td><td>In 1C:Enterprise 8.3.7 or earlier, if a configuration included HTTP services, setting its compatibility mode to <span class="interface">Version 8.3.4</span> or earlier was not allowed.</td><td>You can add HTTP services to configurations that run in compatibility mode <span class="interface">Version 8.3.4</span> or earlier.</td></tr><tr title="Версия 8.3.8" class="tag_14 tag_37"><td><a name="0b6c5b27-46ae-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>You have the option to select the set of external resources that the platofrm uses (in <span class="term">ExternalResourcesMode</span> parameter of <span class="interface">conf.cfg</span> configuration file).
If this parameter is not specified, the platform selects its value automatically.</td><td>This feature was not provided.</td><td>You have the option to select the set of external resources that the platofrm uses.</td></tr></table><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="5a3feda1-6292-11e5-a3f7-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.8" class="tag_37"><td><a name="452ce0fc-62a4-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The <span class="term">NSSSecureConnection </span>object and NSS certificates are no longer available for use in 1C:Enterprise script.</td><td>1C:Enterprise supported NSS certificates in 8.3.6 compatibility mode.</td><td>Support of NSS certificates is discontinued.</td></tr><tr title="Версия 8.3.8" class="tag_37"><td><a name="de85643c-629f-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Support of TLS protocol versions 1.1 and 1.2 is implemented for scenarios where the client certificate is not specified in the connection settings. The SSL protocol version 3.0 is only used when the client application is started with <span class="interface">/HttpsForce</span><span class="interface">SSLv3</span> command-line option. In all other scenarios SSL version 3.0 is not used.<p>1C:Enterprise ignores the <span class="term">AllowSSLv3</span> parameter in <span class="interface">conf.cfg</span> file.</p><p>The <span class="term">InternetMail </span>object does not support SSL version 3.0.</p></td><td>1C:Enterprise only supported TLS protocol version 1.0.<p>The <span class="term">AllowSSLv3</span> parameter was available for use in <span class="interface">conf.cfg</span> file.</p><p>The <span class="term">InternetMail </span>object supported SSL version 3.0.</p><p>
</p></td><td>Increased security of connections established by client applications for Internet operations.</td></tr><tr title="Версия 8.3.8" class="compat tag_37 tag_1"><td><a name="44fbf240-62ac-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The platform no longer uses <span class="interface">cacert.pem</span> file for creating HTTPS/FTPS connections.<p>The platform uses the root certificate store of the operating system for creating HTTPS/FTPS connections.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>The platform used <span class="interface">cacert.pem</span> file for creating HTTPS/FTPS connections in scenarios where no certificate stores were specified explicitly.</td><td>The outdated technology is no longer supported.</td></tr><tr title="Версия 8.3.8" class="tag_115"><td><a name="38b76d0f-6e6b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For managed forms, the option to update data presentations only for the specified set of form items is implemented. For the <span class="term">RefreshDataRepresentation</span><span class="term">()</span> method, the <span class="term">UpdateItems </span>parameter is implemented. For the <span class="term">EditTextUpdate </span>system enumeration, the <span class="term">Always </span>value is implemented.</td><td>The option to specify a set of form items when updating data presentations using the <span class="term">RefreshDataRepresentation</span><span class="term">()</span> method was not available.</td><td>Form data can be updated in idle handlers without losing the text being edited in a text box.</td></tr><tr title="Версия 8.3.8" class="tag_133"><td><a name="e57149b9-6e79-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>The dump of the <span class="term">Source </span>property of the <span class="term">FormItemAddition </span>object to a file is more human-readable.<p>You can restore configuration from files having both property dump formats.</p></td><td>The dump of the <span class="term">Source </span>property of the <span class="term">FormItemAddition </span>object to a file was less human-readable.</td><td>Dumping configurations to files produces files that are more human-readable.</td></tr><tr title="Версия 8.3.8" class="compat tag_56 tag_20 tag_1"><td><a name="3cc2932c-7182-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Error diagnostics for the creation of WS references (both in Designer and using the <span class="term">WSDefinitions </span>object) is much more detailed.<p>During the creation of <span class="term">WSDefinitions </span>object, exceptions are raised if the used WSDL description has errors.</p><p>The WSDL description used to create <span class="term">WSDefinitions</span> or <span class="term">WSReference</span><span class="term"> </span>objects must comply with the following rules:</p><ul><li>Its first tag is <span class="term">&lt;definitions&gt;</span>.</li><li>It includes the <span class="term">targetNamespace</span> attribute of the <span class="term">&lt;xs:schema&gt;</span> element.</li><li>If it does not comply with the rules, an exception is raised.</li></ul><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>Error diagnostics for the creation of WS references (both in Designer and using the <span class="term">WSDefinitions </span>object) was not sufficiently detailed.<p>During the creation of <span class="term">WSDefinitions </span>object, if the used WSDL description had errors, invalid elements were ignored.</p><p>If the first tag of the WSDL description used to create <span class="term">WSDefinitions</span> or <span class="term">WSReference</span><span class="term"> </span>objects was not <span class="term">&lt;definitions&gt;</span>, empty web service description objects were created.</p><p>If the WSDL description used to create <span class="term">WSDefinitions</span> or <span class="term">WSReference</span><span class="term"> </span>objects did not include the <span class="term">targetNamespace</span> attribute of the <span class="term">&lt;xs:schema&gt;</span> element, the platform set a pseudorandom namespace.</p></td><td>Better diagnostics for WSDL description operations.</td></tr><tr title="Версия 8.3.8" class="compat tag_45 tag_1"><td><a name="00953d08-71b7-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If a constant stores a value of <span class="term">ValueStorage</span>, <span class="term">UUID</span>, or <span class="term">ExternalDataSourceTableRef</span> type, a selection from the constant table that includes a request to the <span class="term">Value </span>field returns a value of that type.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>If a constant stored a value of <span class="term">ValueStorage</span>, <span class="term">UUID</span>, or <span class="term">ExternalDataSourceTableRef</span> type, a selection from the constant table that included a request to the <span class="term">Value </span>field returned a value of <span class="term">BinaryData</span><span class="term"> </span>type.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_77 tag_1"><td><a name="113cc739-7261-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>The following behavior of the <span class="term">RepresentableDocumentBatch</span><span class="term">.</span><span class="term">Print</span><span class="term">()</span> method is implemented:<ul><li>On Windows:</li><ul><li>Create a single printer job.</li><li>Output the entire batch to a file, prompt for the file name before the output.</li></ul><li>On Linux:</li><ul><li>If all documents in the batch have identical print settings, use the Windows scenario.</li><li>If the print settings are different, create a printer job for each document.</li></ul></ul><p>This change is not implemented in 8.3.7 compatibility mode.</p><p>The <span class="term">RepresentableDocumentBatch</span><span class="term">.Title</span>, property is implemented. It is used for generating the batch presentation.</p></td><td>The <span class="term">RepresentableDocumentBatch</span><span class="term">.</span><span class="term">Print</span><span class="term">()</span> method created a job for each document in a batch.</td><td>Improved printing of document batches.</td></tr><tr title="Версия 8.3.8" class="compat tag_25 tag_1"><td><a name="bd042e3b-7264-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td><span class="interface">Text </span>and <span class="interface">Format </span>conditional appearance items are applied to fields of chart grouping templates of data composition systems regardless of the previous <span class="interface">Format </span>value (even if the previous value is taken from the data composition system). <span class="interface">Text </span>conditional appearance item has higher priority than <span class="interface">Format </span>conditional appearance.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td><span class="interface">Text </span>and <span class="interface">Format </span>conditional appearance items were applied to fields of chart grouping templates of data composition systems only if the <span class="interface">Format </span>conditional appearance was not applied to those fields earlier.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_25 tag_1"><td><a name="323bbe94-7268-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The <span class="interface">MarkNegatives</span><span class="interface"> </span>conditional appearance property is only used if this property is set to <span class="term">True </span>and the <span class="interface">Use </span>conditional appearance property is also set to <span class="term">True</span>.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>The <span class="interface">MarkNegatives</span><span class="interface"> </span>conditional appearance property was only used if the <span class="interface">Use </span>conditional appearance property was set to <span class="term">True</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_25 tag_1"><td><a name="2846fdb6-7271-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the query language, the <span class="term">CASE </span>operation result is based on all expression types from all <span class="term">THEN </span>branches of that expression.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>In the query language, the calculation of <span class="term">CASE </span>operation result ignored all <span class="term">THEN </span>branches that included constant expressions with <span class="term">NULL </span>values.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_21 tag_1"><td><a name="47cb157f-727e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>The option to set a size limit for data indexed for the full-text search is implemented. The default size limit is 1 MB.<p>For the <span class="term">FullTextSearchManager</span><span class="term"> </span>object, the <span class="term">SetMaxIndexedData</span><span class="term">Size</span><span class="term">()</span> and <span class="term">GetMaxIndexedDataSize</span><span class="term">()</span> methods are implemented.</p><p>The <span class="term">&lt;FTEXTSKIP</span><span class="term">&gt;</span> technological log event is implemented.</p><p>This change is not implemented in 8.3.7 compatibility mode.
</p></td><td>The option to set a size limit for data indexed for the full-text search was not available. All infobase data was indexed.</td><td>You can limit the full-text search scope by excluding large blocks of data you do not need to search. This increases the performance of full-text search indexing and reduces the index size.</td></tr><tr title="Версия 8.3.8" class="tag_14 tag_37 tag_10"><td><a name="584e3bd2-7289-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The algorithm that retrieves the list of infobases and platform updates over HTTPS no longer uses the <span class="interface">cacert.pem</span> file, which is included in the platform distribution kit.<p>On Linux, the platform gets certificates from the certification centers specified in the operating system. On Windows, the platrorm uses the operating system root certificate store.</p></td><td>On Windows, the platform used the <span class="interface">cacert.pem</span> file and the operating system root certificate store in order to check an HTTPS connection.<p>On Linux, the platform used the <span class="interface">cacert.pem</span> file only.</p></td><td>Simplified administration of platform update over HTTPS.</td></tr><tr title="Версия 8.3.8" class="tag_15 tag_29"><td><a name="d3f5301b-732b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system is refactored. The <span class="interface">fontconfig</span> library is used to get the list of fonts. This library is included in the system requirements.<p>The list of directories used for storing fonts is removed from 1C:Enterprise documentation.</p></td><td>The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system used a fixed directory list, which was described in 1C:Enterprise documentation.<p>The <span class="interface">fontconfig</span> library was not used for getting the list of fonts.</p></td><td>Extended the list of fonts available to 1C:Enterprise on Linux operating system. Simplified 1C:Enterprise administration.</td></tr><tr title="Версия 8.3.8" class="compat tag_29 tag_1"><td><a name="dfc88495-732c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The type specified for a data composition schema parameter affects the type of query fields that use this parameter.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>The type specified for a data composition schema parameter did not affect the type of query fields that used this parameter.</td><td>Data displayed in reports better matches the input parameters.</td></tr><tr title="Версия 8.3.8" class="compat tag_43 tag_1"><td><a name="80eeeb7e-7340-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The dynamic list implementation is refactored in order to increase its quality. The list of virtual dynamic list fields that are not available for use in filter, grouping, and order settings is extended.<p>If the main dynamic list table does not have key fields (according to 1C:Enterprise script object model) and a grouping is set for this table, an error is generated.</p><p>When a filter, sorting, or grouping by a field that is not included in a query is specified using 1C:Enterprise script, an error informing that the field is not found is displayed.</p><p>The list of restrictions to queries used to generate dynamic lists is modified.</p><p>Dynamic list sorting specifics are described in the documentation.</p><p>The description of algorithms that dynamic lists use for getting data is changed.</p><p>The standard row picture is generated based on the standard attributes. If a query includes fields whose aliases are identical to standard attribute names and these fields store other data, these fields are not used in standard picture generation.</p><p>If a dynamic list filter cannot be converted to a query language expression, an error is generated.</p><p>Dynamic list column data that is not displayed and does not have the <span class="interface">Use always </span>property set is not sent to the client. Client access to such columns is not available.</p><p>If a dynamic list column has the <span class="interface">Use always </span>property but the current user does not have the <span class="term">View </span>right for that column, the column data is not sent to the client. Client access to such columns (using the <span class="term">CurrentD</span><span class="term">ata </span>property or the <span class="term">R</span><span class="term">owData()</span> method) is not available.</p><p>Automatic dynamic list filters for standard <span class="term">Owner</span>, <span class="term">Parent</span>, <span class="term">Date</span>, <span class="term">Period</span>, and <span class="term">IsFolder </span>fields are applied using data composition system tools.</p><p>Automatic dynamic list filters for key fields can be applied using data composition system tools or using direct addition of main table filter conditions to query texts.</p><p>When a filter is applied using data composition system tools, it can be applied in nested queries and virtual table parameters. This can significantly change the dynamic list data selection result (compared to the result obtained in 8.3.7 compatibility mode).</p><p>The detailed description of all the changes listed above is included in the documentation.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>The following virtual fields were not available in dynamic list sorting and grouping settings: <span class="term">DataVersion</span>, <span class="term">PredefinedDataName</span>, tabular sections fields, and fields having the following types: <span class="term">Type</span>, <span class="term">String </span>(unlimited length), and <span class="term">BinaryData </span>(unlimited length).<p>The list of restrictions to the grouping and ordering settings was different and it was not full.</p><p>If the main dynamic list table did not have key fields (according to 1C:Enterprise script object model) and a grouping was set for this table, the content of data to be displayed was undefined.</p><p>When a filter by a field that was not included in a query text was set, the filter might be applied without displaying any errors, or ignored. If grouping or sorting by a field that was not included in a query was specified using 1C:Enterprise script, the field was ignored.
The list of restrictions to queries used to generate dynamic lists was different.</p><p>The list of dynamic list sorting specifics was not documented.
The description of algorithms that dynamic lists used for getting data was different.</p><p>If a dynamic list query had fields with aliases matching the names of standard attributes used to generate standard row pictures, they were used in the generation of standard pictures (except the <span class="term">IsFolder </span>attribute).
If a dynamic list filter could not be converted to a query language expression, the filter was applied by data composition schema processor after getting the data, and this might reduce the amount of displayed data.</p><p>If dynamic list settings included grouping or sorting fields that were unavailable (before applying rights and functional options), these fields were ignored.
</p><p>In some scenarios dynamic list column data that was not displayed and did not have the <span class="interface">Use always </span>property set was sent to the client.</p><p>If dynamic list column had the <span class="interface">Use always </span>property but the current user did not have the <span class="term">View </span>right for that column, the column data was sent to the client. In this scenario the default values of specific data types were used as column values.</p><p>Automatic dynamic list filters for key fields and for standard <span class="term">Owner</span>, <span class="term">Parent</span>, <span class="term">Date</span>, <span class="term">Period</span>, and <span class="term">IsFolder </span>fields were applied by direct addition of their conditions to query texts.</p></td><td>Improved quality and reliability of dynamic lists. More details about dynamic list specifics are added to the documentation.</td></tr><tr title="Версия 8.3.8" class="compat tag_120 tag_1"><td><a name="de0b50b7-734b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>When a nonserializable value is passed to <span class="term">BackgroundJobs</span><span class="term">.</span><span class="term">Execute</span><span class="term">()</span> method as a background job parameter, the background job is not started and an exception is raised.<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>When a nonserializable value was passed to the <span class="term">BackgroundJobs</span><span class="term">.</span><span class="term">Execute</span><span class="term">()</span> method as a background job parameter, the background job was started and the <span class="term">Undefined </span>value was stored to that parameter. This did not raise any exceptions.</td><td>The start of background jobs complies with the global error diagnostic rules.</td></tr><tr title="Версия 8.3.8" class="tag_10"><td><a name="8e449b3b-741b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>During an unexpected shutdown of the thin client, the dump generation includes taking a screenshot (<span class="term">prntscrn</span> attribute of <span class="term">dump</span> element of <span class="interface">logcfg.xml </span>file).<p>
</p></td><td>During an unexpected shutdown of the thin client, the dump generation did not include taking a screenshot.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_45 tag_1"><td><a name="3bf09594-763b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>The result of division by <span class="term">NULL </span>is treated as a number of unspecified length . This number cannot be used in operations that do not accept numeric operands (such as <span class="term">AND</span>, <span class="term">OR</span>, <span class="term">NOT</span>).<p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>The result of division by <span class="term">NULL </span>was not treated as a number and therefore could be used in operations that did not accept numeric operands (such as <span class="term">AND</span>, <span class="term">OR</span>, <span class="term">NOT</span>).</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_115 tag_96 tag_1"><td><a name="92d313f9-7644-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The approach to processing the closing of applications and managed forms is changed:<ul><li>The new "exit application" mode is implemented. It requires special processing in the <span class="term">BeforeClose</span> and <span class="term">OnClose </span>managed form event handlers.</li><li>Opening windows and executing server calls is not allowed in <span class="term">BeforeExit </span>and <span class="term">OnExit </span>managed application event handlers, and also in <span class="term">BeforeClose </span>and <span class="term">OnClose</span> managed form event handlers (provided that the form is in the "exit application" mode).</li><li>The option to generate a text message prompting the user to confirm or cancel the exit is implemented (in the web client all messages are combined in a single dialog box).</li></ul><p>This approach is described in detail in the documentation.</p><p>For <span class="term">BeforeC</span><span class="term">lose </span>managed form event handler, the <span class="term">Exit </span>and <span class="term">Warning</span><span class="term">Text </span>parameters are implemented. For <span class="term">OnClose </span>managed form event handler, the <span class="term">Exit </span>parameter is implemented. If <span class="term">BeforeC</span><span class="term">lose </span>or <span class="term">OnClose </span>managed form event handler has the <span class="term">Exit</span> parameter, in version 8.3.7 compatibility mode the parameter is set to <span class="term">Undefined</span>. For <span class="term">BeforeExit</span> managed application module event handler, the <span class="term">Warn</span><span class="term">ingText </span>parameter is implemented.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>Depending on the modality usage mode, different approaches to closing managed forms and the main application window were used.<p>In some scenarios (especially in the web client) these approaches led to errors that were hard to detect and fix.</p></td><td>Unified approach to closing forms and the main application window, which provides acceptable user interaction capabilities in all client applications.<p>The implemented platform behavior conforms to the methodology and technical requirements of modern web browsers.</p></td></tr><tr title="Версия 8.3.8" class="tag_10 tag_70"><td><a name="ef25ecf5-7be5-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>When an infobase that has a platform version specified in a local or global list of infobases is started using <span class="interface">1c</span><span class="interface">v8</span>, <span class="interface">1c</span><span class="interface">v8c</span>, or <span class="interface">1c</span><span class="interface">v8s</span>, the search for the specified version is performed regardless of the presence of <span class="interface">/AppAutoCheckVersion</span> command-line option. If a version that is not available on the local computer is specified and this version cannot be installed, an attempt to run the infobase with the latest 1C:Enterprise version is made<p>During the client application update over HTTP, the check for operating system user right to perform this operation is disabled. If the user does not have sufficient rights for installing the client application, the UAC dialog box prompting to confirm the installation on behalf of a user that has administrative rights is displayed. Error diagnostics during the download and installation of the client application distribution kit over HTTP is improved.</p><p>In the <span class="interface">/AppAutoCheckVersion</span> command-line option, you can explicitly specify whether the search for a specific 1C:Enteprise version is performed.</p></td><td>When an infobase was started using <span class="interface">1c</span><span class="interface">v8</span>, <span class="interface">1c</span><span class="interface">v8c</span>, or <span class="interface">1c</span><span class="interface">v8s</span>, the search for the specified version was only performed if the command line included the <span class="interface">/AppAutoCheckVersion</span> option.
During the client application update over HTTP, the check for operating system user right to perform this operation was performed.</td><td>The usability of selection and update of the client application used to access a specific infobase is improved.<p>Improved reliability of automatic thin client updates over HTTP.</p></td></tr><tr title="Версия 8.3.8" class="tag_10"><td><a name="83beacf8-7bea-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When the thin client is installed from a custom distribution kit, a single <span class="interface">1cestart</span> shortcut is created in the <span class="interface">1C:Enterprise </span>folder.</td><td>When the thin client was installed from a custom distribution kit, the <span class="interface">1C:Enterprise </span>folder included <span class="interface">1cestart</span> shortcut and the <span class="interface">Advanced </span>folder with subfolders for each installed <span class="interface">1C:Enterpr</span><span class="interface">ise </span>version.</td><td>Reduced number of 1C:Enterprise startup options available after the installation of the thin client.</td></tr><tr title="Версия 8.3.8" class="tag_10"><td><a name="4e0ea73c-7bef-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>In the client application startup command line, the rules for parsing mandatory parameters are modified. If an option that has a mandatory parameter is specified, the parameter must be also specified (or the option must be omitted). Parameters beginning with slash marks "/" are allowed.</td><td>In the client application startup command line, the rules for parsing mandatory parameters were different. Mandatory option parameters could be omitted. Parameters beginning with slash marks "/" (full file name on Linux) could be treated as command-line options.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="tag_10"><td><a name="55870eaa-7bf2-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>1C:Enterprise documentation and Designer help include the descriptions of <span class="interface">/Out</span>, <span class="interface">/L</span>, <span class="interface">/VL</span>, and <span class="interface">/O</span> options for the <span class="interface">CREATEINFOBASE</span> startup mode, which were previously missing.<p>For the infobase creation mode (<span class="interface">CREATEINFOBASE</span>), new <span class="interface">/DumpResult</span> option is implemented. It enables writing the operation result to a file.</p><p>In the file mode, batch Designer startup with <span class="interface">/RestoreIB</span> and <span class="interface">/LoadCfg</span> options together with the <span class="interface">/DisableStartupDialogs</span> option automatically creates an infobase if the database file is not available in the directory.</p></td><td>1C:Enterprise documentation and Designer help did not include the descriptions of <span class="interface">/Out</span>, <span class="interface">/L</span>, <span class="interface">/VL</span>, and <span class="interface">/O</span> options for the <span class="interface">CREATEINFOBASE</span> startup mode.<p>In the file mode, during the batch Designer startup with <span class="interface">/RestoreIB</span> and <span class="interface">/LoadCfg</span> options together with the <span class="interface">/DisableStartupDialogs</span> option, if the dababase file was not found in the specified directory, the user was asked for the confirmation of further actions.</p></td><td>Improved 1C:Enterprise documentation and Designer help. Simplified batch Designer startup in some usage scenarios.</td></tr><tr title="Версия 8.3.8" class="compat tag_25 tag_1"><td><a name="321fb8f4-7c97-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If a data set field of a data composition schema has an ordering expression specified and the data composition settings include ordering by this field (<span class="interface">Descending</span>), the direction speficied in the ordering expression is reversed. <p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>If a data set field of a data composition schema had an ordering expression specified, ordering for this field was always taken from the ordering expression, while the direction specified in the field settings was ignored.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_52 tag_82 tag_1"><td><a name="89f19371-7c98-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Managed locks that are set for writing accounting register records in the <span class="term">LockForUpdate </span>mode are set by values of nonturnover extra dimensions only.<p>When you set a lock for further operations with balances, it is recommended that you do not specify turnover extra dimension values (you can use the <span class="term">LockForUpdate </span>property or explicitly use a managed lock). When you set a lock for further operations with turnovers, specify all the required extra dimenstion values, including the values of turnover extra dimensions (use the managed lock explicitly).</p><p>This change is not implemented in version 8.3.7 compatibility mode.</p></td><td>Managed locks that were set for writing accounting register records in the <span class="term">LockForUpdate </span>mode included locks by all extra dimension values.</td><td>The behavior of <span class="term">LockForUpdate </span>property of accounting register object is better suited for solving typical tasks. In the <span class="term">LockForUpdate </span>mode, the resulting lock does not inlcude turnover extra dimensions, which fits the frequently used scenarios where the lock is used to check the balances but not the turnovers.</td></tr><tr title="Версия 8.3.8" class="compat tag_45 tag_1"><td><a name="2c9679c8-7e48-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In a query, if a single system enumeration is retrieved and it is not combined with other types, the <span class="term">GROUP BY</span> operation groups the values of this field regardless of the enumeration value source.<p>A similar behavior is implemented for UUIDs and references to external data source tables.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>In a query, if a single system enumeration was retrieved and it was not combined with other types, the <span class="term">GROUP BY</span> operation might not group the values of this field (depending on the enumeration value source).</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_19 tag_1"><td><a name="b1796070-7e4a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>For Microsoft SQL Server DMBS, types of table fields that store some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) are changed. New field types are used if no compatibility mode is selected and only after restructuring configuration objects.<p>To perform database table restructuring with modification of field types, specify the required compatibility mode and restructure the infobase in Designer (on the <span class="interface">Administration </span>menu, click <span class="interface">Verify and repair</span>).</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>For Microsoft SQL Server DMBS, table fields that stored some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) had different types.</td><td>Better mapping between the stored types and Microsoft SQL Server table field types.</td></tr><tr title="Версия 8.3.8" class="compat tag_19 tag_1"><td><a name="80500d84-7e4b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>For all DBMS, the structure of indexes by fields of composite type is modified. This reduces the total number of indexes. Such indexes are built if no compatibility mode is selected and only after restructuring configuration objects.<p>To perform database table restructuring with index update, specify the required compatibility mode and restructure the infobase in Designer (on the <span class="interface">Administration </span>menu, click <span class="interface">Verify and repair</span>).</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>For all DBMS, the structure of indexes by fields of composite type was different.</td><td>Reduced number of indexes for tables storing objects with fields of composite types. This increases the performance of operations with these object types.</td></tr><tr title="Версия 8.3.8" class="compat tag_38 tag_1"><td><a name="498576c4-83b0-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>When a background job is executed, all the configuration extensions available in the session that startes the job are also attached in the background job session. This change is not implemented in 8.3.7 compatibility mode.<p>For <span class="term">ConfigurationExtensionsManager </span>object, the <span class="term">ExecuteBackgroundJ</span><span class="term">obWithDatabaseExtensions </span>method is implemented. It duplicates the background job execution procedure implemented in earlier 1C:Enterprise versions.</p></td><td>When a background job was executed, all the configuration extensions available in the infobase were attached in the background job session.</td><td>Background job execution environment is closer to the parent session environment.</td></tr><tr title="Версия 8.3.8" class="compat tag_115 tag_1"><td><a name="c3ef1c37-c8c3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the thick and thin clients, when a user starts typing in a cell of a managed form table, the <span class="term">AutoComplete</span> event is fired.<p>This change is not implemented in version 8.3.7 compatibility mode.</p></td><td>In the thick and thin clients, when a user starts typing in a cell of a managed form table, the <span class="term">StartChoice </span>event is fired.</td><td>The behavior of the input field in the scenario where a user starts typing in a table cell is uniform with other input scenarios.</td></tr><tr title="Версия 8.3.8" class="tag_17"><td><a name="66baa061-dada-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>The recommendation to have no more than 20 <span class="term">&lt;LOG&gt;</span> elements in the <span class="interface">logcfg.xml</span> file is added to the documentation. Adding more than 20 <span class="term">&lt;LOG&gt;</span> elements can impact the platform performance.</td><td>The recommendation to have no more than 20 <span class="term">&lt;LOG&gt;</span> elements in the <span class="interface">logcfg.xml</span> file was absent from the documentation.</td><td>The recommendation to avoid inefficient technological log usage scenarios is added to the documentation.</td></tr><tr title="Версия 8.3.8" class="tag_51"><td><a name="1e906f28-e5ed-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>A sections panel that is not displayed in the main window because it contains no items is no longer included in the list of subordinate objects returned by the <span class="term">TestedWindowCommandInterface</span>.<span class="term">GetChildObjects</span><span class="term">()</span> method.</td><td>A sections panel that was not displayed in the main window because it contained no items was included in the list of subordinate objects returned by the <span class="term">TestedWindowCommandInterface</span>.<span class="term">GetChildObjects</span><span class="term">()</span> method.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="tag_51"><td><a name="69c0409e-e60b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>The recommendation to use <span class="term">FindObject</span><span class="term">()</span> and <span class="term">FindObjects</span><span class="term">()</span> methods to access a required item of a subordinate object list (instead of accessing it by index) is added to the documentation.</td><td>The recommendation to use <span class="term">FindObject</span><span class="term">()</span> and <span class="term">FindObjects</span><span class="term">()</span> methods to access a required item of a subordinate object list was absent from the documentation.</td><td>Improved 1C:Enterprise documentation.</td></tr><tr title="Версия 8.3.8" class="compat tag_115 tag_1"><td><a name="e8c0d194-e69a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The <span class="term">OnClose</span> event handler and the notification specified in the <span class="term">OnCloseNotifyDescription</span> form property are not called when a managed form is closed using the <span class="term">Close</span><span class="term">()</span> method called in the <span class="term">OnOpen</span> event handler.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>When a managed form was closed using the <span class="term">Close</span><span class="term">()</span> method called in the <span class="term">OnOpen</span> event handler:<ul><li>In the web client, the <span class="term">OnClose</span> event handler and the notification specified in the <span class="term">OnCloseNotifyDescription</span> form property were not called.</li><li>In the thin client, the <span class="term">OnClose</span> event handler and the notification specified in the <span class="term">OnCloseNotifyDescription</span> form property were called.</li></ul></td><td>Unified client application behavior.</td></tr><tr title="Версия 8.3.8" class="tag_115"><td><a name="a011f3df-e6ae-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The documentation describes the following platform behavior: when a value is assigned to a variable that is not declared earlier and has a name identical to a property name available in the current context, this can generate a runtime error or a configuration check error. It is recommended that you declare variables with such names using the <span class="term">Var</span><span class="term"> </span>operator to eliminate possible errors.</td><td>The documentation did not contain a clear description of this scenario.</td><td>The documentation contains a clear description of a possible scenario and provides recommendations for eliminating possible issues.</td></tr><tr title="Версия 8.3.8" class="tag_99"><td><a name="7e8c6cf5-e6b4-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 99); return false;">Window-based interface</a>.<br></td><td>The order of elements in the collection returned by the <span class="term">GetWindows</span><span class="term">() </span>method is changed. The documentation and the Syntax Assistant state that the order of elements in that collection does not follow any specific rule and application algorithms must not rely on that order.</td><td>The documentation did not state that the order of items in the collection returned by the <span class="term">GetWindows</span><span class="term">() </span>method does not follow any specific rule.</td><td>The documentation provides more detail about the <span class="term">GetWindows</span><span class="term">() </span>method.</td></tr><tr title="Версия 8.3.8" class="compat tag_56 tag_1"><td><a name="f21442a4-11e3-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>An attempt to write an invalid qualified element name generates an exception.<p>This change is not implemented in 8.3.6 and 8.3.7 compatibility modes.</p></td><td>An attempt to write an invalid qualified element name did not generate an exception. This might produce an invalid XML file.</td><td>Eliminated unexpected system behavior introduced in version 8.3.6.</td></tr><tr title="Версия 8.3.8" class="compat tag_43 tag_1"><td><a name="6c873e72-23f0-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>If the current user does not have the <span class="term">View </span>right for a dynamic list key field, an attempt to get dynamic list data generates an access violation error.<p>Information for technical support includes the list of fields that cannot be accessed due to insufficient rights.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>If the current user did not have the <span class="term">View</span><span class="interface"> </span>right for dynamic list key fields, this did not affect the list availability. If a form had conditional formatting based on these key fields, it could not be opened.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="tag_105"><td><a name="c6d33f42-323e-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>Unexpected system behavior during the writing of <span class="term">ThisNode </span>exchange plan object, which was found in 1C:Enterprise versions 8.3.8.1606 - 8.3.8.1861, is eliminated. <p>If you migrate to a new 1C:Enterprise version:</p><ul><li>From version 8.3.7 or earlier, no action is reqiured.</li><li>From version in range 8.3.8.1606 - 8.3.8.1861, it is recommended that after the migration you perform infobase verification and repair with the <span class="interface">Check logical infobase integrity </span>check box selected, or use the administration console utility (<span class="interface">1cv8a</span>) to verify and repair the infobase.</li></ul><p>If your infobase contains objects that refer to exchange plan items and they can contain references to <span class="term">ThisNode </span>item, it is recommended that you correct the references using the <span class="interface">Replace</span><span class="interface"> references to incorrect ThisNode records</span> data processor (<a href="http://1c-dn.com/developer_tools/replace_references_to_incorrect_thisnode_records/" target="_blank">read more</a>). The data processor can use the result provided by the administration console (recommended) of the exchange plan record deletion marks as an input.</p><p>It is recommended that you run the cluster administration console (<span class="interface">1cv8</span><span class="interface">a</span>) in verification and repair mode, with report generation enabled. Then use the report as an input for the <span class="interface">Replace </span><span class="interface">references to incorrect ThisNode records</span> data processor<span class="interface">.</span></p></td><td>1C:Enterprise versions 8.3.8.1606 - 8.3.8.1861 generated incorrect exchange plan records for <span class="term">ThisNode </span>element. This might result in a variety of errors, such as the following:<ul><li>Duplicating <span class="term">ThisNode</span> records</li><li>Missing <span class="term">ThisNode </span>records</li><li>Unexpected shutdown when opening an exchange plan list form</li><li>And more</li></ul><p>1C:Enteprise versions 8.3.7 and earlier did not have this issue.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="compat tag_43 tag_1"><td><a name="e1acf916-32d8-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In the source of available data composition system settings for dynamic lists, the following fields are not available for filtering, sorting, or grouping:<ul><li>Fields subordinate to fields that represent aggregate functions of the query language</li><li>Fields subordinate to fields from other (external) data sources</li><li>Subordinate characteristic fields of tabular section fields</li></ul><p>The search initiated by typing a search string excludes reference fields that represent aggregate functions of the query language.</p><p>This change is not implemented in 8.3.7 compatibility mode.</p></td><td>In the source of available data composition settings for dynamic lists, the following fields were available for filtering, sorting, or grouping:<ul><li>Fields subordinate to fields that represented aggregate functions of the query language</li><li>Fields subordinate to fields from other (external) data sources</li><li>Subordinate characteristic fields of tabular section fields</li></ul><p>When a filter by any of these fields was applied, a dynamic list might display incorrect data (some data or all data might be missing).</p><p>An attempt to search in reference fields that represented aggregate functions of the query language initiated by typing a search string might generate errors. If errors we not generated, a dynamic list might display incorrect data (some data or all data might be missing).</p></td><td>The search intiated by typing a search string in dynamic lists is improved. <p>Reduced number of errors that did not have clear descriptions.</p></td></tr><tr title="Версия 8.3.8" class="compat tag_43 tag_1"><td><a name="30c81c45-4290-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In 1C:Enterprise mode, in a dynamic list with a custom query and the main table specified, the availability of main table fields and their subordinate fields for filtering does not depend on the availability of these fields in the dynamic list query. If main table fields are absent from the query text, they are added implicitly.<p>If a dynamic list query text includes a field with alias identical to an alias of a main table field, this field is used in the filter, regardless of whether the fields themselves are identical.</p><p>Fields having multiple paths (in different 1C:Enterprise script languages) are only available in the current 1C:Enterprise script language.</p><p>This change is not implemented in 8.3.7 and earlier compatibility modes.</p></td><td>Only fields available in a query text and standard main table fields (such as <span class="term">Ref</span>) were available for filtering. A filter that included unavailable fields with names indentical to main table field names might be applied without any errors generated.</td><td>For a dynamic list with a custom query and the main table specified, you can include main table fields that are absent from the query text in choice parameters and choice parameter links.</td></tr><tr title="Версия 8.3.8" class="tag_42 tag_82"><td><a name="a85ecf35-42a6-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Eliminated unexpected system behavior during the calculation of accumulation register and accounting register totals in scenarios where a dimension list includes a dimension of <span class="term">String </span>type <b>and</b> an index by dimensions includes more that 16 database fields.<p>When you migrate to 1C:Enterprise version 8.3.8 or later, it is recommended that you use the data processor available for download at 1c-dn.com (<a href="https://1c-dn.com/user/updates/restore_auxiliary_table_data/" target="_blank">read more</a>). The data processor determines whether additional actions are required.</p><p>If they are required, after the migration perform infobase verification and repair with <span class="interface">Check logical infobase inte</span><span class="interface">grity</span> and <span class="interface">Recalculate totals</span> check boxes selected, or use the cluster administration console (<span class="interface">1cv8a</span>). The latter option is recommended because it is faster.</p></td><td>Accumulation register and accounting register totals might be calculated incorrectly in scenarios where a dimension list included a dimension of <span class="term">String </span>type and an index by dimensions included more that 16 database fields.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="tag_37 tag_81"><td><a name="2731f731-75c1-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 81); return false;">Web client, web service, and HTTP service publishing tools</a>.<br></td><td>The option to block redirection to potentially harmful sites after completing an OpenID provider operation is implemented. In the <span class="interface">default.vrd</span> file, the <span class="term">&lt;retur</span><span class="term">nto&gt;</span> element (subordinate to <span class="term">&lt;provider</span><span class="term">&gt;</span> element) is implemented. It contains the list of allowed redirection URLs.<p>Note that publishing OpenID providers from Designer does not support <span class="term">&lt;retur</span><span class="term">nto&gt;</span> elements (existing elements of this type are deleted and new ones are not generated). You have to add these elements manually.</p><p>If you migrate to a new 1C:Enterprise verson, requests to OpenID providers that include the <span class="term">openid.return_to</span> parameter will return HTTP error 400.</p><p>To eliminate this issue, in the <span class="interface">default.vrd</span> file, add the required number of <span class="term">&lt;returnto&gt;</span> elements with available redirection URLs.</p></td><td>The option to affect redirection after completing OpenID provider operations was not provided.</td><td>Improved security of OpenID provider operations.</td></tr><tr title="Версия 8.3.8" class="tag_29"><td><a name="10823aa9-0d46-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The list of supported operating systems and web browsers is changed:<ul><li>Thin client, thick client, web client, and 1C:Enterprise server (Windows versions):</li><ul><li>Windows XP Service Pack 3</li><li>Windows Vista or later with the latest updates</li><li>Windows Server 2003 or later with the latest updates</li></ul><li>On Windows and Linux, Mozilla Firefox versions 38 and later are supported.</li></ul></td><td>The list of supported operating systems and web browsers was different:<ul><li>Thin client, thick client, web client, and 1C:Enterprise server (Windows versions):</li><ul><li>Windows XP (no Service Pack 3 requirement)</li><li>Windows Vista or later (no latest updates requirement)</li><li>Windows Server 2003 (no latest updates requirement)</li></ul><li>On Windows and Linux, Mozilla Firefox versions 17 and later were supported.</li></ul></td><td>1C:Enterprise requires more secure versions of operating systems of Windows family.</td></tr><tr title="Версия 8.3.8" class="tag_14 tag_70 tag_11"><td><a name="985d6f3b-0d6f-11e7-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>Since Windows versions 2008 R2 and later stop trusting SHA-1 certificates in January 2017, the following changes are implemented:<ul><li><span class="interface">.msi</span> and <span class="interface">.mst </span>files included in 1C:Enterprise platform distribution kit are signed with SHA-256; all other files are signed with both SHA-1 and SHA-256.</li><li>The add-in development technology documentation (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>) now includes the following recommendations: sign add-in installer files with both SHA-1 and SHA-256; sign <span class="interface">.msi </span>files with SHA-256.</li></ul></td><td>All files included in 1C:Enterprise platform distribution kit were signed with SHA-1. <p>The following recommendations were not available in the add-in development technology documentation (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>):</p><ul><li>Sign add-in installer files with both SHA-1 and SHA-256.</li><li>Sign <span class="interface">.msi </span>files with SHA-256.</li></ul></td><td>The platform executable files are verified on all supported operating systems of Windows family.</td></tr></table><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="5a3feda2-6292-11e5-a3f7-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.8" class="tag_0"><td><a name="8cc83871-727b-11e5-a3f7-0050569f678a"></a><span class="interface">Synchronous call usage mode for platform extensions and add-ins</span> property name.</td><td><ul><li><span class="term">SynchronousExtensionAndAddInCallUseMode</span>.</li></ul></td><td><ul><li><span class="term">SynchronousPlatformExtensionAndAddInCallUseMode</span>.</li></ul></td></tr><tr title="Версия 8.3.8" class="tag_0"><td><a name="769956f8-766b-11e5-a3f7-0050569f678a"></a>Directory name parameter in <span class="term">BeginCreatingDirectory</span><span class="term">()</span><span class="term"> </span>method.</td><td><ul><li><span class="term">Directory</span>.</li></ul></td><td><ul><li><span class="term">DirectoryName</span>.</li></ul></td></tr><tr title="Версия 8.3.8" class="tag_0"><td><a name="b0fb9fbc-7bf3-11e5-a3f7-0050569f678a"></a>The update start button in the client application update over HTTP dialog box.</td><td><ul><li><span class="interface">Update</span>.</li></ul></td><td><ul><li><span class="interface">Update an</span><span class="interface">d run</span>.</li></ul></td></tr></table><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="5a3feda3-6292-11e5-a3f7-0050569f678a">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.8" class="tag_20 tag_32"><td><a name="18e7965e-73f0-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>In the mobile platform, support of in-app billing services is added. This includes Apple In-App Purchase (for iOS) and Google Play In-App Billing (for Android). Support of in-app billing for Windows is not provided. The <span class="interface">In-a</span><span class="interface">pp purchases</span> mobile application permission is implemented.<p>The <span class="term">InAppPurchases</span>, <span class="term">InAppPurchase</span>, <span class="term">InAppPurchaseReceipt</span>, and <span class="term">InAppPurchasesValidation</span> objects are implemented.</p><p>In the desktop platform, the <span class="term">InAppPurchasesValidation</span><span class="term"> </span>object is implemented. It is intended for testing in-app purchase algorithms.</p><p>In the mobile platform for developers, a service providing an API similar to Google Play In-App Billing is implemented for Android operating system. It is intended for debugging in-app purchase algorithms.</p><p>The option to test the full purchase cycle is implemented. This includes the purchase creation and the emulation of some related scenarios. The HTTP service (named <span class="term">PurchaseTest</span>) and the testing tools are provided by the mobile application builder.</p><p>The mobile application builder supports building mobile applications with in-app purchases.</p></td><td>This feature was not provided.</td><td>The option to implement purchases and subscriptions in mobile applications is available. You can create applications with paid features.</td></tr><tr title="Версия 8.3.8" class="tag_20 tag_32"><td><a name="afb25aa0-7408-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>For mobile applications, the option to display ads is implemented. It uses iAd service (for iOS) and AdMob service (for Android). Displaying ads on Windows is not supported.<p>The <span class="term">Ad</span><span class="term">Representation</span><span class="term"> </span>object is implemented.</p><p>Mobile application builder supports applications that display ads.</p></td><td>This feature was not provided.</td><td>The option to create mobile applications with advertising monetization model is available.</td></tr><tr title="Версия 8.3.8" class="tag_26"><td><a name="fb468ff9-7651-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Exporting spreadsheet documents fo PDF format is implemented.</td><td>This feature was not provided.</td><td>More options for data presentation in mobile applications.</td></tr><tr title="Версия 8.3.8" class="tag_64"><td><a name="fe020030-7d58-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>On Android version 4.1 or later, numbers are displayed correctly if the <span class="term">NG</span> parameter of the <span class="term">Format </span>function contains two groups.</td><td>On Android version 4.1 or later, numbers were displayed incorrectly if the <span class="term">NG</span> parameter of the <span class="term">Format </span>function contained two groups.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.8" class="tag_78"><td><a name="6efc97b2-7d5b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>In the mobile platform, support of asynchronous file operation methods is implemented (this includes global context methods and the <span class="term">File </span>object).</td><td>This feature was not supported by the mobile platform.</td><td>Improved parallel code implementation for both mobile and desktop platforms.</td></tr><tr title="Версия 8.3.8" class="tag_21"><td><a name="20b66c1d-7d5c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>On the mobile platform, support of <span class="term">FullTextSearchManager.CheckIndex()</span><span class="term"> </span>method is implemented.<p>In the Syntax Assistant, methods of <span class="term">FullTextSearchManager</span><span class="term"> </span>object are marked as available on the mobile platform.</p></td><td>This feature was not supported by the mobile platform.<p>The Syntax Assistant erroneously stated that methods of the <span class="term">FullTextSearchManager</span><span class="term"> </span>object were not available on the mobile platform.</p></td><td>Extended full-text search support on the mobile platform. The Syntax Assistant description is up-to-date.</td></tr><tr title="Версия 8.3.8" class="tag_37"><td><a name="7c9e3c63-7d60-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>On the mobile platform, when specifying request body as a string for an <span class="term">HTTPRequest </span>or <span class="term">HTTPServiceResponse </span>object, you have the option to include BOM characters to the request or exclude them.<p>On the mobile platform, the <span class="term">ByteOrderMarkUsage </span>system enumeration is implemented.</p></td><td>This feature was not supported by the mobile platform.</td><td>Simplified mobile application integration with systems that do not expect BOM characters in HTTP requests.</td></tr><tr title="Версия 8.3.8" class="tag_36"><td><a name="9f8c138a-8c70-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The <span class="term">MobileDeviceApplicationRun </span>object is now available on iOS and Windows platforms. The <span class="term">MobileDeviceApplicationRun.RunningSupported</span> method is implemented to test the availability of this feature. Developers can use this method to determine whether their mobile devices support running external applications.</td><td>The <span class="term">MobileDeviceApplicationRun </span>object was not available on iOS and Windows platforms.</td><td>The platform behavior related to functionalities that are not available on some mobile devices or operating systems is unified across all platforms.<p>
</p></td></tr><tr title="Версия 8.3.8" class="tag_115"><td><a name="5853c10f-98d8-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the Syntax Assistant, more information is added to the descriptions of <span class="interface">Activate by default </span>and <span class="interface">Default b</span><span class="interface">utton </span>managed form items.<p>The<span class="interface"> Unfilled selection mode</span> property of managed form input fields is available in mobile platform forms.</p><p>The <span class="interface">Row selection mode </span>property of managed form tables is no longer available in mobile platform forms.
</p><p>
</p></td><td>The information in the Syntax Assistant was outdated.<p>The availability of some properties of managed form input fields did not match the capabilities of the mobile platform.</p></td><td>Designer and Syntax Assistant now match the capabilities of the mobile platform.</td></tr><tr title="Версия 8.3.8" class="tag_32"><td><a name="04d59465-9d85-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Data storage structure implemented in the mobile application builder is modified. When the mobile application builder is started for the first time after the update, the data conversion may take significant time.</td><td>Data storage structure implemented in the mobile application builder was different.</td><td>Data storage structure implemented in the mobile application builder is now more efficient.</td></tr><tr title="Версия 8.3.8" class="tag_20"><td><a name="74af3948-9d89-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>When a debug server that does not support HTTP is specified in a mobile application, the error message clearly explains the problem: <span class="interface">The mobile platform only supports debugging over HTTP</span>.</td><td>When a debug server that did not support HTTP was specified in a mobile application, the error message did not clearly explain the problem.</td><td>Better problem diagnostics during mobile applicatiobn development.</td></tr><tr title="Версия 8.3.8" class="tag_77"><td><a name="ead2b179-e6c0-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>In the mobile platform, the design of the page setup form is changed:<ul><li>The <span class="interface">ОК</span> button is moved to the window header. </li><li>The duplicate <span class="interface">Scale</span> header is removed.</li></ul></td><td>In the mobile platform, the design of the page setup form was different:<ul><li>The <span class="interface">ОК</span> button was located inside a form.</li><li>The <span class="interface">Scale</span> header was duplicated. </li></ul></td><td>Improved design of the page setup form.</td></tr><tr title="Версия 8.3.8" class="tag_48"><td><a name="0e799674-41cf-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 48); return false;">Mobile device-specific features</a>.<br></td><td>On iOS devices, receiving location updates when an application is running in background is not supported.</td><td>The option to receive location updates when an application is running in background on iOS devices was not documented.</td><td>Clarified the specifics of using mobile applications on iOS devices.</td></tr></table><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="5a3feda4-6292-11e5-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.8" class="tag_0"><a name="4cfac872-6298-11e5-a3f7-0050569f678a"></a>The cURL library is updated to version 7.43 and modified to eliminate vulnerabilities.</li><li title="Версия 8.3.8" class="tag_0"><a name="a1e15671-62a3-11e5-a3f7-0050569f678a"></a>The OpenSSL library is updated to version 1.0.2j and modified to eliminate vulnerabilities.</li><li title="Версия 8.3.8" class="tag_0"><a name="c5620151-1bff-11e6-a3f7-0050569f678a"></a>The libpng library is updated to version 1.6.21.</li><li title="Версия 8.3.8" class="tag_0"><a name="44f8fa2e-36c2-11e6-a3f7-0050569f678a"></a>The libtiff library is updated to eliminate vulnerabilities.</li><li title="Версия 8.3.8" class="tag_0"><a name="16853fea-3942-11e6-a3f7-0050569f678a"></a>The libxml2 library is updated to version 2.9.4 and modified to eliminate vulnerabilities.</li><li title="Версия 8.3.8" class="tag_0"><a name="fbba90c2-54a8-11e6-a3f7-0050569f678a"></a>The libxslt library is modified to eliminate vulnerabilities.</li></ul><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h2><a name="5a3feda5-6292-11e5-a3f7-0050569f678a">Transition from the previous version to the version 8.3.8</a></h2><ul><li title="Версия 8.3.8" class="tag_0"><a name="5a3feda6-6292-11e5-a3f7-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.8.
</li><li title="Версия 8.3.8" class="tag_0"><a name="5a3feda7-6292-11e5-a3f7-0050569f678a"></a>Some features that are added in version 8.3.8 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.8" class="compat tag_0"><a name="ed680694-98c8-11e5-a3f7-0050569f678a"></a>When the <span class="interface">Comp</span><span class="interface">atibility mode</span> is set to <span class="interface">None</span>, the minimum supported version of Microsoft SQL Server is Microsoft SQL Server 2005 (this includes scenarios that use the Native Client). </li><li title="Версия 8.3.8" class="tag_0"><a name="ffa7ec29-f5b7-11e5-a3f7-0050569f678a"></a>In the file mode, infobase operations are optimized. To support the optimization, the file database data storage format is updated to new version 8.3.8 format. The option to change the page size of the infobase file (<span class="interface">1Cv8.1CD</span>) is implemented. The page size can have one of the following values: 4096, 8192, 16384, 32768, or 65536 bytes. <p>To migrate data between infobase formats, you can use a <span class="interface">.dt</span> file (provided that the target infobase has the required format) or convert the infobase file using <span class="interface">cnvdbfl</span> utility. The <span class="interface">cnvdbfl</span> utility can change the infobase file page size during the conversion.</p></li><li title="Версия 8.3.8" class="tag_0"><a name="f41b3164-385c-11e6-a3f7-0050569f678a"></a>If you migrate to a new 1C:Enterprise version:<ul><li>From version 8.3.7 or earlier, no action is reqiured.</li><li>From version in range 8.3.8.1606 - 8.3.8.1861, it is recommended that after the migration you perform infobase verification and repair with the <span class="interface">Check logical infobase integrity </span>check box selected, or use the administration console utility (<span class="interface">1cv8a</span>) to verify and repair the infobase.</li></ul><p>If your infobase contains objects that refer to exchange plan items and they can contain references to <span class="term">ThisNode </span>item, it is recommended that you correct the references using the <span class="interface">Replace</span><span class="interface"> references to incorrect ThisNode records</span> data processor (<a href="http://1c-dn.com/developer_tools/replace_references_to_incorrect_thisnode_records/" target="_blank">read more</a>). The data processor can use the result provided by the administration console (recommended) of the exchange plan record deletion marks as an input.</p><p>It is recommended that you run the cluster administration console (<span class="interface">1cv8</span><span class="interface">a</span>) in verification and repair mode, with report generation enabled. Then use the report as an input for the <span class="interface">Replace </span><span class="interface">references to incorrect ThisNode records</span> data processor<span class="interface">.</span></p></li><li title="Версия 8.3.8" class="tag_0"><a name="98ff9b45-42b1-11e6-a3f7-0050569f678a"></a>When you migrate to 1C:Enterprise version 8.3.8 or later, it is recommended that you use the data processor available for download at 1c-dn.com (<a href="https://1c-dn.com/user/updates/restore_auxiliary_table_data/" target="_blank">read more</a>). The data processor determines whether totals recalculation for accumulation registers and accounting registers is required to correct errors in scenarios where a dimension list includes a dimension of <span class="term">String </span>type and an index by dimensions includes more that 16 database fields.<p>If it is required, after the migration perform infobase verification and repair with <span class="interface">Check logical infobase inte</span><span class="interface">grity</span> and <span class="interface">Recalculate totals</span> check boxes selected, or use the cluster administration console (<span class="interface">1cv8a</span>). The latter option is recommended because it is faster. </p></li><li title="Версия 8.3.8" class="tag_0"><a name="4c2d5c6a-54aa-11e6-a3f7-0050569f678a"></a>After the migration from 1C:Enterprise version 8.3.5 to a later version you might get an error when retrieving characteristics. This is because the earlier versions of the platform allow specifying the <span class="term">Description </span>field instead of the <span class="term">Parent </span>field as a filter field for additional characteristic types of metadata objects. To correct the error, enter the correct value to the type filter field.</li><li title="Версия 8.3.8" class="tag_0"><a name="c894ac26-6aaf-11e6-a3f7-0050569f678a"></a>If your configuration includes HTTP services and you previously opened it with 1C:Enterprise Designer 8.3.4, when you open it with 1C:Enterprise 8.3.8, perform the following steps:<ul><li>Create any configuration object.</li><li>Save the infobase configuration.</li><li>Delete that configuration object.</li><li>Save the infobase configuration.</li></ul></li><li title="Версия 8.3.8" class="tag_0"><a name="a9b6c2f2-75c7-11e6-a3f7-0050569f678a"></a>To eliminate the issue with OpenID provider operations, in the <span class="interface">default.vrd</span> file for OpenID provider publication, add the required number of <span class="term">&lt;returnto&gt;</span> elements with available redirection URLs.</li></ul><p><a href="#5a3fed9c-6292-11e5-a3f7-0050569f678a"><small>Table of contents</small></a></p><h1><a name="e7682089-abaa-11e4-b1db-0050569f678a">Version 8.3.7</a></h1><p title="Версия 8.3.7" class="tag_0"><a name="e7682094-abaa-11e4-b1db-0050569f678a"></a>Version 8.3.7 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#e768208a-abaa-11e4-b1db-0050569f678a">New functionality and changes</a></li><li><a href="#e768208b-abaa-11e4-b1db-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#e768208c-abaa-11e4-b1db-0050569f678a">Optimization</a></li><li><a href="#e768208d-abaa-11e4-b1db-0050569f678a">Changes that affect system behavior</a></li><li><a href="#e768208e-abaa-11e4-b1db-0050569f678a">Changes that require modification of configuration and administrative settings</a></li><li><a href="#e768208f-abaa-11e4-b1db-0050569f678a">Renamed objects</a></li><li><a href="#e7682090-abaa-11e4-b1db-0050569f678a">Mobile platform</a></li><li><a href="#b89795d6-1654-11e5-a3f7-0050569f678a">Library updates
</a></li><li><a href="#e7682091-abaa-11e4-b1db-0050569f678a">Transition from the previous version to the version 8.3.7</a></li></ul><h2><a name="e768208a-abaa-11e4-b1db-0050569f678a">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.7" class="compat tag_2 tag_1"><td><a name="1d21e949-abab-11e4-b1db-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.3.6 </span>is added to the list of available values of the <span class="interface">Compatibility mode</span> property.
</td><td>Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4 and 8.3.5.
</td><td>In version 8.3.7 you can run configurations created in version 8.3.6 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.7 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.6 for working with the infobase even after the transition to version 8.3.7. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).</td></tr><tr title="Версия 8.3.7" class="tag_41"><td><a name="3b187aa9-abb4-11e4-b1db-0050569f678a"></a><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>The <span class="term">ZipFileWriter</span> and <span class="term">ZipFileReader</span> objects are revised to improve stability during intense simultaneous work of a large number of users and to eliminate the issue with national characters in file names.<p>ZIP archive support is implemented using the zipArchive library. The <span class="term">ZIPCompressionMethod</span><span class="term">.BZIP2 </span>system enumeration value is implemented.</p></td><td>The <span class="term">ZipFileWriter</span> and <span class="term">ZipFileReader</span> objects had an issue related to intense simultaneous work of a large number of users, and an issue related to national characters in file names.<p>The Info-ZIP library was used for ZIP archive support. The <span class="term">BZIP2</span> compression method was not supported.</p></td><td>Improved support of ZIP archives (including the support of national characters in file names). You can use the prevalent archive file format on Linux.</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="302a68cb-b1f0-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td> Configuration support settings management is available in Designer batch mode. The <span class="term">/ManageCfgSupport</span> command-line option is implemented for Designer batch mode.</td><td>This feature was not provided.<p>Configuration support settings management was only available in the interactive mode.</p></td><td>Simplified automated building and testing of applied solutions.</td></tr><tr title="Версия 8.3.7" class="compat tag_37 tag_65 tag_1"><td><a name="bd3d298b-b1fc-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>You can use OS authentication for Internet operations and web services. When a WS-reference is created in Designer, the OS authentication option cannot be disabled.<p>When the list of infobases is retrieved using a web service, OS authentication is used, unless the URL contains authentication data.</p><p>OS authentication is not supported on Linux.</p><p>For the <span class="term">InternetProxy </span>object, the option to enable or disable OS authentication for each protocol is implemented. This change is not implemented in 8.3.6 compatibility mode.</p><p>The <span class="term">UseOSAuthentication </span>parameter is implemented for constructors of the following objects: <span class="term">HTTPConnection</span>, <span class="term">WSDefinitions</span>, and <span class="term">WSProxy</span>.</p><p>The <span class="term">UseOSAuthentication </span>property is implemented for the following objects: <span class="term">HTTPConnection</span> and <span class="term">WSProxy</span>.</p><p>For the <span class="term">WSReferenceManager</span>.<span class="term">CreateWSProxy</span><span class="term">()</span> method, the <span class="term">UseOSAuthentication </span>option is implemented.</p><p><span class="term">For the InternetProxy.Set()</span> method, the <span class="term">UseOSAuthentication </span>option is implemented.</p><p>For the <span class="term">InternetProxy </span>object, the <span class="term">UseOSAuthentication() </span>method is implemented.</p></td><td>OS authentication was not implemented for Internet operations and web services.<p>OS authentication was never used for retrieving a list of infobases using a web service.</p><p>For the <span class="term">InternetProxy </span>object, basic authentication was used, provided that the user name and password were set.</p></td><td>Extended capabilities for web service operations, Internet operations, and retrieving the list of infobases in corporate environments.</td></tr><tr title="Версия 8.3.7" class="tag_65"><td><a name="50e3d42b-b1ff-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>You can use a web service whose address is different from the address specified in a WSDL file imported to the applied solution (a <span class="interface">WS-reference</span> object).<p>For the <span class="term">WSProxy </span>object constructor, the <span class="term">Location </span>parameter is implemented.</p><p>For the <span class="term">WSReferenceManager.CreateWSProxy() </span>method, the <span class="term">Location </span>parameter is implemented.</p></td><td>This feature was not provided.<p>A web service could be used only if it was located at the address specified in a WSDL file imported to the applied solution (a <span class="interface">WS reference</span> configuration object).</p></td><td>New usage options for Web services in scenarios where a web service has a fixed interface but can be located at different addresses in the Internet. For example, you can use a web service of some broadly used applied solution.</td></tr><tr title="Версия 8.3.7" class="tag_57 tag_56"><td><a name="f0377ccb-b1ff-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 57); return false;">JSON support</a>.<br><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>XDTO objects can be serialized to JSON.</td><td>This feature was not provided.<p>Only streaming API and object model were supported for JSON.</p></td><td>Simplified usage of JSON format for exchange between various 1C:Enterprise-based systems.</td></tr><tr title="Версия 8.3.7" class="tag_57"><td><a name="957e956b-b200-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 57); return false;">JSON support</a>.<br></td><td>When data is written in JSON format, slash marks (/) can be escaped.<p>For the <span class="term">JSONWriterSettings</span> constructor, the <span class="term">EscapeSlash</span> parameter is implemented. For the <span class="term">JSONWriterSettings</span> object, the <span class="term">EscapeSlash</span> property is implemented.</p><p>The <span class="term">EscapeSlash</span> property is used by the <span class="term">JSONWriter.WriteValue()</span> method.</p></td><td>The option to enable or disable escape of slash marks in JSON operations was not available.</td><td>Better compatibility with external systems that use exchange in JSON format.</td></tr><tr title="Версия 8.3.7" class="tag_84"><td><a name="c210d54b-b203-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The <span class="term">NumberInWords() </span>and <span class="term">PeriodPresentation()</span> global context methods support the Azerbaijani language. The language code is <span class="term">az</span>. The format of the <span class="term">NumerationItemOptions</span> parameter of the <span class="term">NumberInWords()</span> method for this language is described in the Syntax Assistant.</td><td>The <span class="term">NumberInWords()</span> and <span class="term">PeriodPresentation()</span> global context methods did not support the Azerbaijani language.</td><td>Simplified implementation of data presentation for Azerbaijani-speaking users.</td></tr><tr title="Версия 8.3.7" class="tag_84"><td><a name="d75e436b-b203-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The <span class="term">NumberInWords()</span> and <span class="term">PeriodPresentation()</span> global context methods support the Turkish language. The language code is <span class="term">tr</span>. The format of the <span class="term">NumerationItemOptions</span> parameter of the <span class="term">NumberInWords()</span> method for this language is described in the Syntax Assistant.</td><td>The <span class="term">NumberInWords()</span> and <span class="term">PeriodPresentation()</span> global context methods did not support the Turkish language.</td><td>Simplified implementation of data presentation for Turkish-speaking users.</td></tr><tr title="Версия 8.3.7" class="tag_84"><td><a name="43fb60cb-b204-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The <span class="term">NumberInWords()</span> and <span class="term">PeriodPresentation()</span> global context methods support the Hungarian language. The language code is <span class="term">hu</span>. The format of the <span class="term">NumerationItemOptions</span> parameter of the <span class="term">NumberInWords()</span> method for this language is described in the Syntax Assistant.</td><td>The <span class="term">NumberInWords() </span>and <span class="term">PeriodPresentation()</span> global context methods did not support the Hungarian language.</td><td>Simplified implementation of data presentation for Hungarian-speaking users.</td></tr><tr title="Версия 8.3.7" class="compat tag_26 tag_1"><td><a name="ff122fa6-b2aa-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When a spreadsheet document is exported to XLS (Microsoft Excel 97-2003) format, Microsoft Office OpenXML (Microsoft Excel 2007- 2010) format, or ODS (OpenDocument Spreadsheet) format, the following print settings are exported to the resulting file:<ul><li>Margin sizes</li><li>Header sizes</li><li>Page orientation</li><li>Page size</li><li>Scale</li><li>Black-and-white option</li><li>Print area</li><li>Columns and rows that are repeated on each page</li><li>Header text</li></ul><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>When a spreadsheet document was exported to XLS (Microsoft Excel 97-2003) format, Microsoft Office OpenXML (Microsoft Excel 2007- 2010) format, or ODS (OpenDocument Spreadsheet) format, its print settings were not exported.</td><td>More accurate export of spreadsheet documents to popular spreadsheet document formats.</td></tr><tr title="Версия 8.3.7" class="tag_38"><td><a name="697821d0-c7ca-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>In configuration extensions, you can create WS references, XDTO packages, web services, and HTTP services.<p>You can publish Internet services belonging to configuration extensions to web servers.</p><p>In the <span class="interface">default.vrd</span> file, the <span class="term">publishExtensionsByDefault</span> attribute is implemented for ws and</p><p><span class="term">httpServices</span> elements.</p></td><td>This feature was not provided.</td><td>New functionality introduced for configuration extensions.</td></tr><tr title="Версия 8.3.7" class="tag_129"><td><a name="f51ee522-c7d6-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 129); return false;">OData interface</a>.<br></td><td>You can use independent information registers that do not have dimensions in the standard OData interface. The <span class="term">SurrogateKey</span> property is implemented.</td><td>This feature was not provided.</td><td>The 1C:Enterprise object implementation better complies with the OData standard.</td></tr><tr title="Версия 8.3.7" class="tag_120"><td><a name="c917b4ed-c7f1-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>You can quickly determine whether the current session is a background job session.<p>The <span class="term">GetCurrentInfoBase</span><span class="term">Session()</span> global context method is implemented. The <span class="term">InfoBaseSession.GetBackgroundJob()</span> method is implemented.</p></td><td>This feature was not provided.<p>The only way to determine the session type was getting all infobase sessions and iterating through them.</p></td><td>Optimized procedure for determining whether the current session is a background job session. This is handy in such scenarios as dividing initialization scripts for client applications and background jobs.</td></tr><tr title="Версия 8.3.7" class="tag_19"><td><a name="a8f5068d-c7f7-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Dumping an infobase to a <span class="interface">.dt</span> file is interrupted if any issues related to the internal infobase structure are encountered.</td><td>Dumping an infobase to a <span class="interface">.dt</span> file did not include a verification of the internal infobase structure.</td><td>Reduced chance of obtaining a <span class="interface">.dt</span> file that cannot be loaded.</td></tr><tr title="Версия 8.3.7" class="tag_36"><td><a name="2f640735-d9f5-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The option to read and write data in a scenario where synchronous calls are not allowed is implemented for the following objects: <span class="term">TextDocum</span><span class="term">ent</span>, <span class="term">SpreadsheetDocument</span>, <span class="term">FormattedDocument</span>, <span class="term">GraphicalSchema</span>, and <span class="term">RepresentableDocumentBatch </span>(write operation only).<p>The <span class="term">BeginWriting() </span>method is implemented for the following objects: <span class="term">TextDocum</span><span class="term">ent</span>, <span class="term">SpreadsheetDocument</span>, <span class="term">FormattedDocument</span>, and <span class="term">GraphicalSchema</span>.</p><p>The <span class="term">BeginReading</span><span class="term">() </span>method is implemented for the following objects: <span class="term">TextDocum</span><span class="term">ent</span> and <span class="term">GraphicalSchema</span>.</p><p>The <span class="term">RepresentableDocumentBatch.BeginWritingFileForPrinting</span> method is implemented.</p></td><td>These features were not provided.</td><td>The missing functionality is implemented for compatibility with the recent Google Chrome changes.</td></tr><tr title="Версия 8.3.7" class="tag_8"><td><a name="0023b874-da0d-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 8); return false;">Cryptography support</a>.<br></td><td>For the <span class="term">Issuer </span>and <span class="term">Subject </span>properties of the <span class="term">CryptoCertificate </span>object the option to get access to all certificate fields that describe issuer and subject is implemented.<p>For the <span class="term">Issuer </span>and <span class="term">Subject </span>properties of the <span class="term">CryptoCertificate </span>object the <span class="term">Street </span>field is implemented.</p><p>Each of the <span class="term">Issuer </span>and <span class="term">Subject </span>structure fields of the <span class="term">CryptoCertificate </span>object is accessible by:</p><ul><li>Mnemonic key (for example, <span class="term">CN</span>)</li><li>UUID key (for example, <span class="term">OID2_5_4_3</span> for the <span class="term">CN</span> field).</li></ul></td><td>The <span class="term">Issuer </span>and <span class="term">Subject </span>properties of the <span class="term">CryptoCertificate </span>object did not provide access to all certificate fields.</td><td>All certificate fields can be accessed, even those that are present due to regulator requirements.</td></tr><tr title="Версия 8.3.7" class="tag_19"><td><a name="7b6dd093-da0f-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>When the platform attempts to build an index by more than 3 string fields in Oracle DBMS, it automatically creates <span class="term">V81C_INDEX_BIG</span> tablespace.</td><td>When the platform attempted to build an index by more than 3 string fields in Oracle DBMS, if <span class="term">V81C_INDEX_BIG</span> tablespace was missing, an error was generated. Creating the tablespace manually eliminated the error.</td><td>The need to create the tablespace manualy is eliminated.</td></tr><tr title="Версия 8.3.7" class="tag_38 tag_95"><td><a name="fb3b7f43-e4ea-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>The option to adopt predefined data items is implemented for configuration extensions. This makes the following operations available: check extensions for availability of predefined data items, check whether extension exchange plan content and object registration rules include predefined data items, and use extension predefined items in the query builder.</td><td>This feature was not provided.</td><td>Expanded configuration extension functionality.</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="e29ba846-e833-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The option to dump configurations to hierarchical file structures, as well as restore them from such file structures, is implemented.<p>Name length for new configuration objects is limited by 80 characters. Existing configuration objects can have names longer than 80 characters until you attempt to edit their names.</p><p>1C:Enterprise script modules are dumped to <span class="interface">.bsl</span> files.</p><p>In the dump configuration files dialog box you can select the dump format: flat or hierarchical.</p><p>The Format parameter is implemented for <span class="term">/DumpConfigToFiles </span>Designer batch mode command-line option. The new parameter describes the dump format.</p><p>By default configurations are dumped to hierarchical file structures.</p><p>
</p></td><td>Configurations were always dumped to flat file structures.<p>No length restrictions were applied to configuration object names.</p><p>1C:Enterprise script modules were dumped to <span class="interface">.txt </span>files.</p></td><td>Chance of configuration dump procedure being terminated due to length of the output file path and name exceeding the file system limits is significantly reduced (file names are derived from configuration object names).</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="32f71e45-fe30-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>A configuration can be partially restored from files. The following operations are available: adding, modifying, deleting, and renaming configuration objects and modifying some properties of configuration objects (such as their modules or help topics).<p>You can simultaneously load a configuration from files and update database configuration.</p><p>For the <span class="term">/LoadConfigFromFiles</span> Designer batch mode command-line option, the following parameters are implemented: <span class="term">-files</span> (files to load) and <span class="term">-listfile</span> (file containing a list of files to load).</p><p>In the technological log, the <span class="term">CONFLOADFROMFILES</span> event is implemented.</p></td><td>This feature was not provided.<p>Only restoring the entire configuration from files was available.</p></td><td>Better performance of configuration updates in scenarios where a configuration is stored in an external system.</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="af5fd443-ff9e-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New debug option is available: debugging over HTTP. Developers can select this option in Designer.<p>The dialog box with automatic debug item attachment settings is refactored.</p><p>Debug server (<span class="interface">dbgs</span>) is implemented, it can be started from the command line, and also as an operating system service. The new debug protocol is not supported on Linux servers in the scenario where 1C:Enterprise starts automatically during operating system startup.</p><p>The following command-line options are implemented for the server agent (<span class="interface">ragent</span>): <span class="interface">/debug</span>, <span class="interface">/debugServerAddr</span>, <span class="interface">/debugServerPort</span>, and <span class="interface">/debugServerPwd</span>.</p><p>For the client application the following command-line option is implemented: <span class="interface">/debug</span>.</p><p>In <span class="interface">default.vrd </span>file, for the <span class="term">&lt;debug&gt;</span> element, the <span class="term">protocol </span>attribute is implemented.</p><p>In <span class="interface">comcntrcfg.xml</span> file, for the <span class="term">&lt;config&gt;</span> element, the <span class="term">protocol </span>attribute is implemented.</p><p>This option is implemented as beta version.</p></td><td>A single debug option was available.</td><td>You can debug applied solutions when HTTP is the only available connection protocol. This expands Debugger functionality.</td></tr><tr title="Версия 8.3.7" class="tag_84"><td><a name="7ef061fb-158c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The option to localize only a part of 1C:Enterprise platform interface required for a specific applied solution is implemented. Localization tools that support this option are available upon request from 1C Company at <a href="mailto:1c@int.com" target="_blank">MAIL:int@1c.com</a>. This option has the following limitations:<ul><li>Pictures cannot be localized.</li><li>The option to build a platform distribution kit is not provided.</li></ul></td><td>Only the full localization option was available. Localizations were always delivered as part of the platform distribution kit.</td><td>The option to localize the platform interface for specific applied solutions or specific delpoyments is implemented. This option is in demand by users whose native languages are not included in the list of platform localization languages.</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="3d44ee25-1b49-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Designer help includes the list of executable files of predefined external tools used for comparing and merging modules. It is recommended that you specify these names in the settings for comparing and merging modules with external tools.</td><td>Designer help did not include executable file names of predefined external tools used for comparing and merging modules.</td><td>Improved Designer help.</td></tr><tr title="Версия 8.3.7" class="tag_133"><td><a name="bc74e537-40e6-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>Versioning is implemented for the format of dumping configurations to files. 1C:Enterprise 8.3.6 has dump format version 1.0, and 1C:Enteprise version 8.3.7 has dump format version 2.0.<p>If the dump files do not include a version number, they are treated as version 1.0-compliant.</p><p>Files are always dumped in the format that matches the 1C:Enterprise platform version.</p><p>A configuration can be restored from files only if the version of the files is earlier than or equal to the version supported by the 1C:Enterprise platform.</p></td><td>Versioning was not available for the format of dumping configurations to files.</td><td>Some issues related to the incompatibility of dump files generated by different 1C:Enterprise versions are eliminated.</td></tr><tr title="Версия 8.3.7" class="tag_133"><td><a name="005701cd-524a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>The method of dumping the <span class="interface">Parameter </span>property of the <span class="interface">Button </span>managed form item to files is changed. If the <span class="interface">Parameter </span>value references a configuration object, the full name of that configuration object is dumped to files.</td><td>The <span class="interface">Parameter </span>property of the <span class="interface">B</span><span class="interface">utton </span>managed form item was dumped as a UUID of the configuration object type if the <span class="interface">Parameter </span>property referenced a configuration object.</td><td>Eliminated the configuration dump format inconsistency.</td></tr><tr title="Версия 8.3.7" class="tag_10"><td><a name="0f5d8ab7-6072-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Applied solution license validity check is implemented at 1C:Enterprise platform level. The check is performed for applied solutions running in file mode, and it is also performed on the server for 1C:Enterprise 8.3 Server MINI. The license validity check is not performed for applied solutions that use the base version of 1C:Enterprise. The check involves an Internet connection to the Update Validation Center.<p>The result of the check is displayed in the <span class="interface">About 1C:Enterprise</span> dialog box.</p><p>The Designer interface includes new commands related to this functionality.
The following global context methods are implemented: <span class="term">GetConfigurationID</span>, <span class="term">GetLicensingClientName</span>, <span class="term">GetLicensingClientAdditionalParameter</span>, <span class="term">SetLicensing</span><span class="term">ClientParameters</span>,
<span class="term">AttachLicensingClientParametersRequestHandler</span>, and
<span class="term">DetachLicensingClientParametersRequestHandler</span>.</p><p>For the <span class="interface">conf.cfg </span>configuration file, the <span class="term">LicConfigDebugTimeouts</span> parameter is implemented. The parameter is used to reduce the check interval.</p><p>The implementations of this functionality are subject to future announcement.</p></td><td>This feature was not provided.</td><td>The option to perform a license validity check after updating an applied solution is implemented.</td></tr><tr title="Версия 8.3.7" class="tag_19"><td><a name="edc07a78-9f08-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of Oracle Database version 12.1.0.2 (Linux) is implemented.</td><td>This Oracle Database version was not supported.</td><td>Extended list of supported Oracle Database versions.</td></tr><tr title="Версия 8.3.7" class="tag_135 tag_14 tag_136 tag_29"><td><a name="ecc554a6-aad3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 135); return false;">Designer</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 136); return false;">Cross-platform architecture</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The client application for OS X 10.8 or later is available (64-bit version only). It supports the following features:<ul><li>Thin client, thick client, and Designer</li><li>File and client/server modes</li></ul><p>Running 1C:Enterprise server on OS X is not supported. The limitations of the OS X client application are provided in the documentation.</p><p>Installation and simultaneous work of multiple 1C:Enteprise versions is supported.
</p><p>This option is implemented as beta version.</p></td><td>Infobase access via a web client was available on OS X.</td><td>You can develop applied solutions and run client applications on OS X.</td></tr><tr title="Версия 8.3.7" class="tag_29"><td><a name="b5b52a30-c98c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Astra Linux Special Edition 1.4 is supported.</td><td>This release was not supported.</td><td>New Linux release is supported.</td></tr><tr title="Версия 8.3.7" class="tag_11"><td><a name="4ef864a0-dadb-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>The English description of the add-in development technology is provided as an HTML document. This document is available for download for each platform version as a part of 1C:Enterprise platform 8.3 Add-in technology archive.</td><td>The description of the add-in development technology available for download as a part of 1C:Enterprise was only provided in Russian.
</td><td>Better accessibility of add-in development documentation.</td></tr><tr title="Версия 8.3.7" class="tag_41"><td><a name="0bbecb70-136a-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>File names in ZIP archives generated by 1C:Enterprise have both UTF-8 encoding and the current operating system encoding (if is not UTF-8).<p>The <span class="term">ZipFileReader </span>object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, read ZIP archives correctly even when the file names inside the archives contain non-English characters. Note that the built-in decompression program for OS X displays file names in such archives incorrectly.</p></td><td>File names in ZIP archives generated by 1C:Enterprise had UTF-8 encoding only.<p>The <span class="term">ZipFileReader </span>object in 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs in Windows XP/2003/2008/7, displayed file names with non-English characters inside ZIP archives incorrectly. </p></td><td>The <span class="term">ZipFileReader </span>object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, read ZIP archives correctly even when the file names inside the archives contain non-English characters. Note that the built-in decompression program for OS X displays file names in such archives incorrectly.</td></tr></table><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e768208b-abaa-11e4-b1db-0050569f678a">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.7" class="tag_96"><td><a name="874a1b26-b29d-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In the <span class="interface">Taxi</span> interface, when an item is deleted from the <span class="interface">Favorites</span> list, a modal confirmation dialog box is no longer displayed. After the deletion, a link for restoring the deleted item is displayed in the <span class="interface">Favorites</span> panel.</td><td>In the <span class="interface">Taxi</span> interface, when an item was deleted from the <span class="interface">Favorites</span> list, a modal confirmation dialog box was displayed.</td><td>The <span class="interface">Favorites</span> pane functionality is fully supported in web browsers that do not support modal dialog boxes.</td></tr><tr title="Версия 8.3.7" class="tag_96"><td><a name="cf256e9b-d918-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In the <span class="interface">Taxi</span> interface, you can pin forms in the main window work area (so that a form is always available). You can also combine two forms in order to have them always displayed together when any of the two forms is opened.<p>In the system menu, context menu of the opened windows panel, and form title context menu, the corresponding commands are implemented.</p></td><td>This feature was not provided.</td><td>Improved platform usability. For example, users have the option to compare two instances of a single report featuring different periods.</td></tr><tr title="Версия 8.3.7" class="tag_64"><td><a name="da03369b-d91c-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Web service authentication error messages no longer contain HTML text returned by the web server, at no cost to message information value.</td><td>Web service authentication error messages contained HTML text returned by the web server.
</td><td>All information that was not user-friendly is removed from web service authentication error messages</td></tr><tr title="Версия 8.3.7" class="tag_96"><td><a name="324d9475-d9f0-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>Replacement of style elements with actual fonts and colors is improved in some scenarios.</td><td>In some scenarios, replacement of style elements with actual fonts and colors was performed incorrectly.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="tag_14"><td><a name="32fbeac4-1b29-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The client application help includes the description of the keyboard shortcut <span class="interface">Ctrl+Shift+H</span>, which opens the history panel.</td><td>Description of this shortcut was not available in the client application help.</td><td>Client application help is up-tp-date.</td></tr><tr title="Версия 8.3.7" class="tag_28"><td><a name="be92462d-71b8-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In Google Chrome web browser, access to clipboard using context menu commands is implemented (in addition to the previously available keyboard shortcuts).<p>This options requires installing a browser extension. The web client propmts the user to install the extension first time they attempt to access the clipboard using context menu commands. If the extension is not installed, the clipboard can be only accessed using keyboard shortcuts.</p></td><td>In Google Chrome web browser, the clipboard could only be accessed using keyboard shortcuts.<p>Clipboard access using context menu commands was not supported.</p></td><td>Improved web client usability in Google Chrome.</td></tr><tr title="Версия 8.3.7" class="tag_28"><td><a name="7031f909-7d56-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>New version of the browser extension for Mozilla Firefox is available. The extension only supports asynchronous operations. The synchronous methods are no longer supported.</td><td>Another version of browser extension for Mozilla Firefox was available. It supported synchronous operations.</td><td>Support of Mozilla Firefox versions 40 and later, which do not support synchronous operations (just like Google Chrome versions 45 and later), is implemented.</td></tr></table><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e768208c-abaa-11e4-b1db-0050569f678a">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.7" class="tag_20"><td><a name="7567e6eb-b1ed-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The performance of the following Designer operations is improved:<ul><li>Opening a subsystem editor window</li><li>Including an object into a subsystem</li><li>Setting a filter by subsystem in the configuration tree window</li></ul></td><td>The performance of some Designer operations was insufficient.</td><td>Streamlined execution of some Designer operations.</td></tr><tr title="Версия 8.3.7" class="tag_137"><td><a name="ee20428b-b1ed-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 137); return false;">Geographical schemas</a>.<br></td><td>The following geographical schema operations are optimized:<ul><li>Loading and rendering geographical schemas</li><li>Selecting an object in a geographical schema field</li></ul></td><td>The performance of some geographical schema operations was insufficient.</td><td>Improved usability of geographical schemas.</td></tr><tr title="Версия 8.3.7" class="tag_21"><td><a name="89527592-da03-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Improved performance of full-text search and of building the full-text search index.</td><td>Insufficient performance of full-text search and of building the full-text search index.</td><td>Improved performance of full-text search and of building the full-text search index. The improvement is noticeable if the infobase contains indexed objects with a large number of words.</td></tr><tr title="Версия 8.3.7" class="tag_21 tag_43"><td><a name="068bc5cb-da04-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In dynamic lists, the performance of the search initiated from the search string is improved in the following scenario: the full-text search is enabled for the dynamic list main table and filters with <span class="interface">Equal to</span> comparison type are applied to the main table fields. </td><td>In dynamic lists, the performance of the search initiated from the search string was insufficient.</td><td>In dynamic lists, improved performance of the search initiated from the search string.</td></tr><tr title="Версия 8.3.7" class="tag_45"><td><a name="81a34473-da07-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>When a query that accesses only tabular section data is executed, the retrieved table is not joined to the parent object table.</td><td>When a query that accessed only tabular section data was executed, the retrieved table was automatically joined to the parent object table.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="tag_19"><td><a name="4e71dd3a-dc62-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Improved performance of reading objects of the following types from DBMS: <span class="term">DocumentObject</span>, <span class="term">CatalogObject</span>, <span class="term">BusinessProcessObject</span>, <span class="term">TaskObject</span>, <span class="term">ChartOfCalculationTypesObject</span>, <span class="term">ChartOfCharacteristicTypesObject</span>, <span class="term">ExchangePlanObject</span>, and <span class="term">ChartOfAccountsObject</span>. Reading any of these objects is followed by implicit transaction creation only if the object has tabular sections and "dirty read" outside of transactions is allowed in the DBMS.</td><td>Reading objects of the following types from the DBMS was followed by implicit transaction creation if the object had tabular sections: <span class="term">DocumentObject</span>, <span class="term">CatalogObject</span>, <span class="term">BusinessProcessObject</span>, <span class="term">TaskObject</span>, <span class="term">ChartOfCalculationTypesObject</span>, <span class="term">ChartOfCharacteristicTypesObject</span>, <span class="term">ExchangePlanObject</span>, and <span class="term">ChartOfAccountsObject</span>.</td><td>The following values are reduced:<ul><li>Number of data lock waits in the file DBMS.</li><li>Time required for loading an infobase object from a DBMS in the client/server mode.</li><li>Number of waits due to internal 1C:Enterprise server locks during bulk reading of infobase objects from a DBMS.</li><li>DBMS load (due to a significant decrease of the number of transactions).</li></ul></td></tr><tr title="Версия 8.3.7" class="tag_115"><td><a name="c10bf01a-dc62-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Improved performance of managed form conditional appearance. Faster opening of managed forms with a large number of conditional appearance items.</td><td>Insufficient performance of managed form conditional appearance.</td><td>Improved performance of opening managed forms, especially for file mode infobases and on low-performance computers.</td></tr><tr title="Версия 8.3.7" class="tag_95"><td><a name="0ab16800-e37f-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>Improved performance of retrieving predefined data using the <span class="term">PredefinedValue</span><span class="term">()</span> method.</td><td>Insufficient performance of retrieving predefined data using the <span class="term">PredefinedValue</span><span class="term">()</span> method. </td><td>Improved performance of processing predefined data.</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="5e257ec1-e386-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The configuration database update time is reduced for configurations that include a large number of roles, provided that the update does not require database restructuring.</td><td>The configuration database update required significant time for configurations that included a large number of roles, provided that the update did not require database restructuring.</td><td>Reduced database configuration update time.</td></tr><tr title="Версия 8.3.7" class="tag_115 tag_69"><td><a name="d2f15621-e386-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The performance of opening managed forms is improved in the thin client and web client.</td><td>The performance of opening managed forms in the thin client and web client was insufficient.</td><td>Improved platform performance.</td></tr><tr title="Версия 8.3.7" class="tag_138"><td><a name="67e27f60-e388-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 138); return false;">Platform algorithms</a>.<br></td><td>Internal caching algorithms of 1C:Enterprise are optimized. This improves the performance of many 1C:Enterprise features, including the following:<ul><li>Form opening</li><li>Queries</li><li>Functional options</li><li>Predefined data</li><li>Reusable return values</li><li>Data access using "." (dot)</li></ul></td><td>System performance was suboptimal.</td><td>Improved platform performance, especially for infobases running in the file mode and on computers with limited RAM (less than 4 GB).</td></tr><tr title="Версия 8.3.7" class="tag_97"><td><a name="44d7e203-e4e2-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 97); return false;">Data access restrictions</a>.<br></td><td>Query execution is optimized for users that do not have full rights in configurations that use access restrictions and have a large number of roles. The query execution time is not significantly affected by the number of roles assigned to a user.</td><td>Query execution time was insufficient for users that did not have full rights in configurations that used access restrictions. The query execution time was significantly affected by the number of roles assigned to a user.</td><td>Improved performance of configurations with a large number of roles (including form opening performance).</td></tr><tr title="Версия 8.3.7" class="tag_43 tag_21"><td><a name="4abe4384-e80a-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>When a dynamic list is searched from a search box by fields that do not belong to the main dynamic list table, full-text search by source objects of the fields is performed first. Fields of objects where nothing is found by the full-text search are excluded from further search.</td><td>When a dynamic list was searched from a search box, additional conditions were applied to all fields displayed in the table linked to the dynamic list.</td><td>Improved performance of search in dynamic lists in some usage scenarios.</td></tr><tr title="Версия 8.3.7" class="tag_45"><td><a name="e6512563-e819-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In the query language, expressions that include both comparison operators and <span class="term">CASE</span> operators that return only constant values are optimized. The optimization simplifies expressions or their parts.</td><td>In the query language, optimization was not available for expressions that included both comparison operators and <span class="term">CASE</span> operators that returned only constant values.</td><td>Improved query performance in some scenarios.</td></tr><tr title="Версия 8.3.7" class="compat tag_21 tag_1"><td><a name="cd80b409-da02-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>The performance of the input by string feature is improved. The full-text search index data structure is modified. Full-text search index is created in the new format. To convert the index to the new format, clear the index, ensure that the <span class="interface">Compatibility mode</span> configuration property is set to <span class="interface">Do not use</span>, and then generate the index.<p>The <span class="term">&lt;INPUTBYSTRING&gt;</span> technological log event is implemented, it is used for monitoring events related to input by string.</p><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The performance of the input by string feature was insufficient. Full-text search index had a different format.</td><td>Improved performance of the input by string feature, which, in turn, improves the usability of all platform objects that use this feature.</td></tr><tr title="Версия 8.3.7" class="tag_51"><td><a name="8f62ff19-6754-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>In the web client running in the testing client mode, the performance of test scenario commands is improved.</td><td>In the web client running in the testing client mode, the performance of test scenario commands was insufficient.</td><td>Improved performance of automated testing in the web client.</td></tr><tr title="Версия 8.3.7" class="tag_105 tag_58"><td><a name="4ad9d5fe-7325-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>Improved performance of initial infobase image creation in scenarios where the exchange plan used to create the initial image includes a register that is included in independent separator content (provided that separator is not used in the current session).</td><td>The performance of initial infobase image creation in scenarios where the exchange plan used to create the initial image included a register that was included in independent separator content (provided that separator was not used in the current session) was insufficient.</td><td>Improved performance of initial image creation in some scenarios.</td></tr><tr title="Версия 8.3.7" class="tag_36"><td><a name="52e5e806-98c8-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The algorithms of the following methods are optimized: <span class="term">QuerySchemaAvailableTables</span><span class="term">.</span><span class="term">Find</span><span class="term">()</span>, <span class="term">QuerySchemaSources</span><span class="term">.</span><span class="term">Add</span><span class="term">()</span>, and <span class="term">QuerySchemaTableParameters</span><span class="term">.</span><span class="term">Count</span><span class="term">()</span>.</td><td>The performance of <span class="term">QuerySchemaAvailableTables</span><span class="term">.</span><span class="term">Find</span><span class="term">()</span>, <span class="term">QuerySchemaSources</span><span class="term">.</span><span class="term">Add</span><span class="term">()</span>, and <span class="term">QuerySchemaTableParameters</span><span class="term">.</span><span class="term">Count</span><span class="term">()</span> methods was insufficient.</td><td>Improved performance of query schema operations in 1C:Enterprise script.</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="e9ad4e58-a8ad-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Operations in the configuration command interface editor form are optimized for scenarios with a large number of roles. The performance of moving table rows is improved.</td><td>The performance of operations in the configuration command interface editor form was insufficient in scenarios with a large number of roles.</td><td>Improved usability for application developers that edit the command interface of configurations with a large number of roles.</td></tr><tr title="Версия 8.3.7" class="compat tag_19 tag_121 tag_1"><td><a name="27d1025a-b873-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 121); return false;">Calculation registers</a>.<br></td><td>Both in PostgreSQL and IBM DB2, in scenarios where large calculation register record sets are deleted, deletion of records storing actual action periods is performed faster.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>Both in PostgreSQL and IBM DB2, in scenarios where large calculation register record sets were deleted, deletion of records storing actual action periods was impaired.</td><td>Both in PostgreSQL and IBM DB2, optimized deletion of large calculation register record sets.</td></tr><tr title="Версия 8.3.7" class="tag_26"><td><a name="1aa85d2f-b874-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The performance of setting the size and position of spreadsheet document pictures at 1C:Enterprise server side is improved.</td><td>The performance of setting the size and position of spreadsheet document pictures at 1C:Enterprise server side was insufficient.</td><td>Improved performance of spreadsheet document generation in scenarios where the size and position of spreadsheet document pictures are set from 1C:Enterprise script.</td></tr><tr title="Версия 8.3.7" class="tag_115 tag_28 tag_6"><td><a name="fafaf577-05fd-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The performance of opening managed forms is improved in the following scenario: the web client is running in client/server mode and the server cluster is deployed on a Linux computer.</td><td>The performance of opening managed forms was insufficient in the following scenario: the web client was running in client/server mode and the server cluster was deployed on a Linux computer.</td><td>Improved web client performance for Linux server clusters.</td></tr></table><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e768208d-abaa-11e4-b1db-0050569f678a">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.7" class="tag_115"><td><a name="ca69046b-b1f9-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The <span class="interface">Create </span>menu (in a document journal form) does not contain document types disabled by functional options.<p>The <span class="interface">Show in list</span> menu (in a document form) does not contain list forms disabled by functional options. </p></td><td>The <span class="interface">Create </span>menu (in a document journal form) contained document types disabled by functional options.<p>The <span class="interface">Show in list </span>menu (in a document form) contained list forms disabled by functional options.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="tag_6"><td><a name="46e0ec4b-b201-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>In client/server mode, dynamic updates do not require restarting Designer.<p>When a scheduled job is started or completed in an infobase, this does not affect the performance of other infobases in the cluster.</p><p>Improved system reliability in the following scenarios:</p><ul><li>Database configuration update</li><li>Background jobs</li><li>Dynamic update</li></ul></td><td>In client/server mode, dynamic updates required restarting Designer.<p>When a scheduled job was started or completed in an infobase, this affected the performance of other infobases in the cluster.</p><p>The system reliability was insufficient in several scenarios.</p></td><td>Increased stability and reliability of server clusters.</td></tr><tr title="Версия 8.3.7" class="tag_95"><td><a name="65e1750b-b202-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>During infobase verification and repair operations, the platform checks whether the main table of an object (catalog, chart of characteristic types, chart of calculation types, or chart of accounts) contains no more than 1 record for each predefined item in each area. If a duplicate item is found, a predefined item mark is removed from it and a deletion mark is set instead.</td><td>This feature was not provided.</td><td>Improved infobase verification and repair operation.</td></tr><tr title="Версия 8.3.7" class="compat tag_62 tag_1"><td><a name="7c3294e6-b2a4-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>Table fields and cube table dimension fields of external data sources can have NULL values only if the <span class="interface">NULL allowed</span> check box is selected in the object settings. For external data source cube table fields NULL values are always allowed.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>All external data source table fields could have NULL values.</td><td>Improved performance of sorting dynamic lists by fields whose ability to store NULL values is specified correctly.</td></tr><tr title="Версия 8.3.7" class="compat tag_25 tag_1"><td><a name="9921cd06-b2a9-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In a data composition schema, if a query with a nested query is used in a data set, selected fields of the nested query are available for filtering, provided that these fields are not used in aggregate functions of the parent query.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>In a data composition schema, if a query with a nested query was used in a data set, selected fields of the nested query were not available for filtering (except virtual table parameters).</td><td>In a data composition schema, the generation of a resulting query is optimized for scenarios that utilize nested queries with filters by nested query fields.</td></tr><tr title="Версия 8.3.7" class="tag_44 tag_58"><td><a name="d967cb10-c7cc-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 44); return false;">Infobase verification and repair</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>Infobase verification and repair can detect and repair the following issue: objects linked to some tabular section rows are absent from the infobase. The search and restoration are performed taking into account all independent separators that include the missing objects.</td><td>This feature was not provided. </td><td>Improved infobase verification and repair procedure.</td></tr><tr title="Версия 8.3.7" class="tag_43"><td><a name="db66426d-c7dd-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In dynamic lists, search by reference fields with custom presentations is performed by fields that form the presentation. Such fields are obtained with the help of the <span class="term">PresentationFieldsGetProcessing()</span> handler.</td><td>In dynamic lists, search by reference type fields with custom presentation was performed only by fields used in default presentation.</td><td>Improved search by reference fields with custom presentations in dynamic lists.</td></tr><tr title="Версия 8.3.7" class="compat tag_115 tag_86 tag_1"><td><a name="27a1a85b-d90e-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>In the thin client, in the <span class="interface">Taxi</span> interface or in the <span class="interface">Forms in tabs</span> mode, when a command is executed from the navigation panel, the <span class="term">Uniqueness</span> command handler parameter is assigned a <span class="term">BOOLEAN</span> value (<span class="term">TRUE</span> if the command is executed through the <span class="interface">Open new item</span> context menu command, otherwise <span class="term">FALSE</span>).<p>In the thin client, in the <span class="interface">Taxi</span> interface or in the <span class="interface">Forms in tabs</span> mode, when a command is executed from a form navigation panel, the uniqueness of the form being opened is not set.</p><p>This change is not implemented in 8.3.6 compatibility mode and in the <span class="interface">Forms in separate windows </span>mode.</p></td><td>In the thin client, in the <span class="interface">Taxi</span> interface or in the <span class="interface">Forms in tabs </span>mode, when a command was executed from the navigation panel, the <span class="term">Uniqueness</span> command handler parameter was set to the main window identifier. In the web client, in the <span class="interface">Taxi</span> interface or in the <span class="interface">Forms in tabs</span> mode, when a command was executed from the navigation panel, the <span class="term">Uniqueness</span> command handler parameter was assigned a <span class="term">BOOLEAN</span> value.<p>In the thin and web clients, in the <span class="interface">Taxi</span> interface or in the <span class="interface">Forms in tabs</span> mode, when a command was executed from a form navigation panel, the <span class="term">Uniqueness</span> command handler parameter was set to the main window identifier.</p><p>In the<span class="interface"> Forms in separate </span><span class="interface">windows</span> mode, when a command was executed from the navigation panel, the <span class="term">Uniqueness</span> command handler parameter was set to the main window identifier.</p><p>In the <span class="interface">Forms in separate windows </span>mode, when a command was executed from a form navigation panel, the <span class="term">Uniqueness</span> command handler parameter was set to the main window identifier.</p></td><td>Unified platform behavior in various client applications and usage scenarios.</td></tr><tr title="Версия 8.3.7" class="tag_6"><td><a name="fc0b97da-d926-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>For the <span class="interface">ragent</span>, <span class="interface">rmngr</span>, and <span class="interface">rphost</span> commands, which start server cluster processes, the <span class="term">pingPeriod</span> and <span class="term">pingTimeout</span> command-line options are implemented.<p>In <span class="interface">default.vrd</span> file, for the <span class="term">pool</span> item, the <span class="term">serverPingPeriod</span> and <span class="term">serverPingTimeout</span> attributes are implemented.</p><p>In the web server publishing dialog box, the <span class="interface">Check period </span>and<span class="interface"> Check timeout </span>properties are implemented.</p><p>In the technological log, for the <span class="term">CONN</span> event, the list of logged events related to the detection of connection losses between processes in a single cluster is extended.</p></td><td>A less-efficient algorithm was used for detection of connection losses in a cluster.</td><td>Improved server cluster stability, faster and more efficient detection of connection losses in a cluster.</td></tr><tr title="Версия 8.3.7" class="tag_21 tag_43 tag_6"><td><a name="d56c2e55-da05-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When a form that contains a dynamic list is closed, the server cluster is notified about that in order to cancel the background job that performs search in the list (if it was initiated earlier).</td><td>When a form that contained a dynamic list was closed, the server cluster was not notified about that. If a background job that performed search in the list was running at the moment of closing, it was not interrupted once the form was closed. Instead, it continued running till the completion.</td><td>Eliminated unexpected system behavior. Reduced server cluster load in some scenarios.</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="dacb487b-dc49-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer, the <span class="interface">П</span> shortcut is removed from the <span class="interface">Move up </span>and <span class="interface">Move down </span>commands in the Russian interface (it was assigned to both commands previously). Other keyboard shortcuts for these commands are still in effect, as well as the actions associated with these commands.</td><td>In Designer, the <span class="interface">П</span> keyboard shortcut was assigned to both <span class="interface">Move up </span>and <span class="interface">Move down </span>commands in the Russian interface.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="compat tag_25 tag_1"><td><a name="94114e3f-e418-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Presentations of filter items displayed in reports is changed.<p>If a report includes a filter item from the user settings and the user settings item presentation is specified for this filter item, the presentation is used for displaying the filter in the resulting report.</p><p>This change does not affect reports that include filter items that do not belong to user settings. It also does not affect filter items that do not have user settings item presentations specified.</p><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>If a report included a filter item whose presentation was specified, only this presentation was displayed in the report. Otherwise the filter item was displayed in the following format: <span class="interface">&lt;Left value</span><span class="interface">&gt; &lt;Comparison type</span><span class="interface">&gt; &lt;Right value</span><span class="interface">&gt;</span>.</td><td>Filter list presentations in reports are easier to read.</td></tr><tr title="Версия 8.3.7" class="compat tag_26 tag_1"><td><a name="b22be3e9-e440-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The spreadsheet document behavior is modified in scenarios where a rectangular area of cells is inserted or deleted (interactively or using 1C:Enterprise script). If an area being moved overlaps an area of merged cells and the merged area is not fully included into the area being moved, the merging is removed and the cells previously included in the merged area inherit the formatting of the merged area.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>When a rectangular area of cells was inserted or deleted, merged cells that partially overlapped the area being moved were not modified.</td><td>Eliminated unexpected spreadsheet document behavior.</td></tr><tr title="Версия 8.3.7" class="tag_19"><td><a name="fc4d5662-e4d1-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>In Oracle Database DBMS an index created for a temporary table that includes more than three dimensions of <span class="term">String</span> type, each of them containing at least 60 characters, might be truncated (with the last fields discarded) if the index key length does not fit the block size.</td><td>In Oracle Database DBMS an index created for a temporary table that included more than three dimensions of <span class="term">String</span> type resulted in unexpected system shutdown due to DBMS error.</td><td>Eliminated unexpected system behavior. Improved system reliability.</td></tr><tr title="Версия 8.3.7" class="tag_10"><td><a name="67edf865-fe37-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The following requirement is described in the documentation: when an application is updated over HTTP or HTTPS, all <span class="interface">.mst</span>, <span class="interface">.msi</span>, and <span class="interface">.cab</span> files in the distribution kit .zip archive must have a digital signature. The signature is verified on the computer where the application is installed. </td><td>Thew documentation did not include the file digital signature requirement.</td><td>Documentation issue corrected.</td></tr><tr title="Версия 8.3.7" class="tag_20"><td><a name="589d4c70-fee5-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Setting a correspondence between Debugger and a debug item no longer requires the exact match of infobase connection strings in Debugger and in the debug item.<p>The option to edit a variable value during debugging is implemented.</p><p>The option to view all local variables of a method being debugged in a dedicated window is implemented.</p><p>The state of folders (expanded or collapsed) in the immediate window and in the local varibles window is preserved when switching to the next debug step.</p><p>If you use the <span class="interface">Break </span>command (<span class="interface">Shift+F5</span>) to close an application being debugged, the modal exit confirmation dialog box is never displayed.</p></td><td>Setting a correspondence between Debugger and a debug item required the exact match of infobase connection strings in Debugger and in the debug item.<p>The option to edit a variable value during debugging was not provided.</p><p>The option to view all local variables of a method being debugged in a dedicated window was not provided.</p><p>The state of folders (expanded or collapsed) in the immediate window and in the local varibles window was not preserved when switching to the next debug step.</p><p>Using the <span class="interface">Break </span>command (<span class="interface">Shift+F5</span>) to close an application being debugged sometimes opened the modal exit confirmation dialog box.</p></td><td>Expanded debug functionality.</td></tr><tr title="Версия 8.3.7" class="compat tag_25 tag_1"><td><a name="17ca0270-0074-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The overall columns of a data composition system table display the titles of grouped resource fields if grouping templates are specified for the table columns.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The overall columns in the data composition system table header did not display the titles of grouped resource fields if grouping templates were specified for the table columns.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="tag_36 tag_20"><td><a name="155def59-0510-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The <span class="interface">Language code</span> property of the <span class="term">Language </span>configuration object cannot contain the following characters: <span class="interface">#</span>, <span class="interface">*</span>, <span class="interface">|</span>, <span class="interface">\</span>, <span class="interface">:</span>, <span class="interface">"</span>, <span class="interface">&lt;</span>, <span class="interface">&gt;</span>, <span class="interface">?</span>, <span class="interface">/</span>.</td><td>The <span class="interface">Language code</span> property of the <span class="term">Language </span>configuration object could not contain the<span class="interface"> #</span> character.</td><td>Chance of configuration dump procedure being terminated due to incorrect generation of the file name (which is based on the language code) is reduced.</td></tr><tr title="Версия 8.3.7" class="tag_86"><td><a name="eb4e704d-23c3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>In the thin client, in the <span class="interface">Forms in separate windows</span> mode, if a navigation command handler includes the <span class="term">GotoURL</span><span class="term">()</span> global context method with a navigation point reference parameter, after the command execution the current navigation point is set to this command.<p>
</p></td><td>In the thin client, in the <span class="interface">Forms in separate windows</span> mode, if a navigation command handler included the <span class="term">GotoURL</span><span class="term">()</span> global context method with a navigation point reference parameter, after the command execution the current navigation point was set to the point passed in the parameter.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="compat tag_115 tag_1"><td><a name="477e7c52-40e4-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the thin client, the <span class="term">Window</span> property of managed form object is read-only.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>In the thin client, the <span class="term">Window</span> property of managed form object was available for both reading and writing. In the web client, the <span class="term">Window</span> property of managed form object was read-only.</td><td>Unified system behavior in different client applications.</td></tr><tr title="Версия 8.3.7" class="compat tag_16 tag_1"><td><a name="28231b1a-40f7-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>For periodic information registers with resources or attributes indexed, the structure of the index of the slice first/last table is changed. If the information register periodicity is set to <span class="interface">By recorder position</span>, register dimensions are added to the index. If the periodicity has any other value, the index is not unique.<p>When the <span class="interface">Compatibility mode</span> configuration property is set to <span class="interface">None</span>, the platform performs the restructuring of the slice tables.</p><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>For periodic information registers with periodicity set to <span class="interface">By recorder position</span>, register dimensions were not included in the index of slice first/last tables. For periodic information registers with other periodicity values, the index of slice tables was unique.
</td><td>An nonunique index issue is eliminated.</td></tr><tr title="Версия 8.3.7" class="compat tag_95 tag_1"><td><a name="42d78c36-8201-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>The configuration check that is always performed before database configuration update includes a check for duplicate predefined item names. No duplicate predefined item names are allowed for any configuration object. If duplicate predefined items are found, this is reported to the message window but does not prevent the configuration update.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The configuration check that was always performed before database configuration update included a check for duplicate predefined item names, however, duplicate names did not prevent the database configuration from updating.</td><td>Improved reliability of configuration updates for configurations that include predefined data.</td></tr><tr title="Версия 8.3.7" class="tag_17"><td><a name="42ab9d93-c8c3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>Logging of debugger exceptions in the technological log is implemented. The <span class="term">&lt;EXCP&gt;</span> event is used for that logging.</td><td>Logging of debugger exceptions was not performed.</td><td>Better debugger error diagnostics.</td></tr><tr title="Версия 8.3.7" class="tag_10"><td><a name="004d65a1-ec11-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The infobase verification and repair procedure no longer includes a check for spaces at the end of attribute values that have <span class="term">String </span>type and variable length.</td><td>The infobase verification and repair procedure included a check for spaces at the end of attribute values that had <span class="term">String </span>type and variable length.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="tag_94"><td><a name="aee7213c-f814-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 94); return false;">Regional settings</a>.<br></td><td>For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ, and 87-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.</td><td>The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ. and 87-FZ.</td><td>The time offset changes introduced by the new law are implemented.</td></tr></table><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e768208e-abaa-11e4-b1db-0050569f678a">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.7" class="compat tag_37 tag_1"><td><a name="9dbabfa0-e40c-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The <span class="term">NSSSecureConnection</span> object and NSS certificates cannot be accessed from 1C:Enterprise script.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>1C:Enterprise system supported NSS certificates.</td><td>Future platform versions will not support NSS certificates.</td></tr><tr title="Версия 8.3.7" class="compat tag_36 tag_1"><td><a name="8add88f6-b2ab-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>In the thin client, the <span class="term">ValueStorage.Get()</span> method raises an exception.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>In the thin client, the <span class="term">ValueStorage.Get() </span>method did not raise an exception and returned the <span class="term">Undefined </span>value instead. Running this method in the web client raised an exception.</td><td>Uniform system behavior across multiple client applications.</td></tr><tr title="Версия 8.3.7" class="compat tag_96 tag_115 tag_1"><td><a name="aa733cfb-d91b-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The choice history generation rules for managed form text boxes are modified. In particular, the frequency of history item usage is taken into account. The history consists of up to 7 items, which include both frequently used and last used values. The history generation rules are described in detail in the documentation.<p>The system storage of managed form text box choice history stores a value of the <span class="term">ChoiceHistorySettings </span>type.</p><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The choice history generation rules for managed form text boxes were different. The history stored 5 last values.<p>The system storage of managed form text box choice history stored a value of the <span class="term">Array </span>type.</p></td><td>Improved usability of managed form text box choice history.</td></tr><tr title="Версия 8.3.7" class="compat tag_115 tag_1"><td><a name="0f8c306f-d91f-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>New algorithm for automatic arrangement of managed form items is implemented. As a result, item positioning is improved, new item placement options are added, changing some item properties on the client does not require a server call (this includes expanding or collapsing groups and showing or hiding form item addition extension for view status), rules for automatic generation of form separators are modified, and more. In many cases toggling form item visibility no longer requires a server call. Detailed description of this feature is provided in the documentation.<p>In the managed form editor, quick preview of a form with specific screen resolution and specific screen orientation is available.</p><p>For the <span class="term">ChildFormItemsGroup</span> system enumeration, the <span class="term">HorizontalIfPossible</span> value is implemented. The <span class="term">AutoMaxWidth</span>, <span class="term">MaxW</span><span class="term">idth</span>, <span class="term">AutoMaxHeight</span>, and <span class="term">Max</span><span class="term">Height</span> properties are implemented for the following objects: managed form field extension for a label field, text box, picture field, spreadsheet document field, text document field, formatted document field, calendar field, progress bar field, track bar field, chart field, Gantt chart field, dendrogram field, geographical schema field, HTML document field, graphical schema field, period field, planner field, and for managed form items of table, decoration, and button types.</p><p>For managed form items of form, group, and page types the following properties are implemented: <span class="term">HorizontalSpacing</span>, <span class="term">VerticalSpacing</span>, <span class="term">ItemsAndTitlesAlign</span>, <span class="term">ChildItems</span><span class="term">HorizontalAlign</span>, and <span class="term">ChildItems</span><span class="term">VerticalAlign</span>. </p><p>For managed form fields of field, table, decoration, group, button, and addition types, the <span class="term">HorizontalAlignInGroup</span> and <span class="term">VerticalAlignInGroup</span> properties are implemented. For managed form item addition extensions for <span class="interface">search string</span>, <span class="interface">search control</span>, and <span class="interface">view status</span>, the <span class="term">AutoMaxWidth</span> and <span class="term">Max</span><span class="term">Width</span> properties are implemented. For managed form groups, the <span class="term">ThroughAlign</span> property is implemented. For the <span class="term">VerticalFormScroll</span> system enumeration, the <span class="term">UseWithout</span><span class="term">Stretch</span> value is implemented. For managed form group extension for a usual group, the <span class="term">United</span> property is implemented. For managed form group extension for a page, the <span class="term">VerticalScrollOnReduceSize</span> property is implemented.</p><p>This change is not implemented in 8.3.6 compatibility mode. </p><p>The <span class="term">HorizontalStretch</span> and <span class="term">VerticalStretch</span> properties are implemented for the following objects: managed form extensions for graphical schema field and HTML document field, and managed form buttons. For managed form item addition extension for <span class="interface">search control</span>, the <span class="term">HorizontalStretch</span> property is implemented.</p><p>The <span class="term">ChildFormItemsWidth</span> property of form, page, and usual group objects is obsolete and only supported in version 8.3.6 compatibility mode. In configurations that do not use compatibility mode, this property is ignored.</p></td><td>A different algorithm was used for arranging managed form items.</td><td>In managed forms, automatic item arrangement is revised. New arrangement options are available. Several known managed form issues are eliminated.</td></tr><tr title="Версия 8.3.7" class="tag_65"><td><a name="c75e097a-d924-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>If a configuration includes HTTP services, saving a configuration with compatibility mode lower than <span class="interface">Version 8.3.5</span> is not allowed.</td><td>Saving configurations was performed without checking the correspondence between configuration compatibility mode and the availability of HTTP services in the configuration.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="tag_36"><td><a name="76606a93-d9fd-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td><span class="interface">Synchronous call usage mode for extensions and </span><span class="interface">add-ins</span> configuration property value is taken into account by the following methods:<ul><li><span class="term">Read</span><span class="term">()</span> method of the<span class="term">TextDocument</span> object</li><li><span class="term">Write</span><span class="term">()</span> method of the<span class="term">TextDocument</span>, <span class="term">SpreadsheetDocument</span>, <span class="term">FormattedDocument</span>, and <span class="term">GraphicalSchema</span> objects</li><li><span class="term">WriteFileForPrinting</span><span class="term">()</span> method of the <span class="term">RepresentableDocumentBatch</span> object</li></ul></td><td>The <span class="interface">Synchronous call usage mode for extensions and </span><span class="interface">add-ins</span> configuration property was ignored by the listed methods.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="compat tag_139 tag_1"><td><a name="dbde8b35-d9fe-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 139); return false;">Server cluster</a>.<br></td><td>The following background job names are used for specifying requirements of functionality purposes:<ul><li>Scheduled job: <span class="term">BackgroundJob.ScheduledJob.&lt;Metadata object name</span><span class="term">&gt;</span>.</li><li>Input by string: <span class="term">BackgroundJob.InputByString.&lt;Full </span><span class="term">metadata object name</span><span class="term">&gt;</span>.</li><li>Report: <span class="term">BackgroundJob.GenerateReport.&lt;Full report metadata object name</span><span class="term">&gt;</span>.</li><li>External report: <span class="term">BackgroundJob.GenerateReport.&lt;</span><span class="term">Full report metadata object name</span><span class="term">&gt;</span>.</li><li>Search in list: <span class="term">BackgroundJob.DynamicListSearch.&lt;Full form name</span><span class="term">&gt;.&lt;Name of form table </span><span class="term">linked</span><span class="term"> to the list</span><span class="term">&gt;</span>.</li><li>Background restructuring: <span class="term">SystemBackgroundJob.DBConfigUpdate</span>.</li></ul><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The following background job names were used for specifying requirements of functionality purposes:<p>
</p><ul><li>Background job: <span class="term">BackgroundJob</span><span class="term">.</span><span class="term">CommonModule</span><span class="term">.&lt;Module name</span><span class="term">&gt;.&lt;Method name</span><span class="term">&gt;</span>.</li><li>Input by string: <span class="term">BackgroundJob.SystemBackgroundJob</span>.</li><li>Report: <span class="term">BackgroundJob.Report</span>.</li><li>External report: <span class="term">BackgroundJob.Report</span>.</li><li>Search in list: <span class="term">BackgroundJob.SystemBackgroundJob</span>.</li><li>Background restructuring: <span class="term">SystemBackgroundJob</span>.
</li></ul></td><td>Background job names comply with the internal platform requirements, Background job names are more precise.</td></tr><tr title="Версия 8.3.7" class="compat tag_45 tag_1"><td><a name="2eae20f5-d9ff-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>The <span class="term">ValueType</span><span class="term">()</span> query language function returns <span class="term">UNDEFINED</span> when <span class="term">UNDEFINED</span> is passed as the function parameter.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The <span class="term">ValueType</span><span class="term">()</span> query language function returned <span class="term">NULL</span><span class="term"> </span>when <span class="term">UNDEFINED</span> was passed as the function parameter.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="compat tag_139 tag_1"><td><a name="b2775994-da09-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 139); return false;">Server cluster</a>.<br></td><td>You can restrict access to cryptography features using security profiles.<p>For <span class="term">ISecurityProfile</span> object, the <span class="term">CryptographyAllowed</span> property is implemented (programmed administration of server clusters using COM objects).</p><p>For <span class="term">ISecurityProfile</span> object, the <span class="term">getCryptographyAllowed()</span> and <span class="term">setCryptographyAllowed()</span> methods are implemented (Java server administration interface).</p><p>For the server cluster command-line utility (<span class="interface">rac</span>) the <span class="term">crypto</span> parameter for the <span class="interface">profile</span> command is implemented.</p><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The option to restrict access to cryptography features using security profiles was not provided.</td><td>Extended security profile capabilities.</td></tr><tr title="Версия 8.3.7" class="compat tag_110 tag_1"><td><a name="2aeed43b-dc4e-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br></td><td>The access rights check for document journal graph attributes performed using the<span class="term"> AccessRight()</span> method with <span class="term">User/Role</span> parameter specified takes into account the availability of all objects included in the journal graph content.<p>The AccessRight() result is cached by the platform, which is similar to caching reusable return values.</p><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The access rights check for document journal graph attributes performed using the <span class="term">AccessRight() </span>method with <span class="term">User/Role</span> parameter specified did not take into account the availability of all objects included in the journal graph content.<p>The <span class="term">AccessRight()</span> result was not cached by the platform.</p></td><td>Eliminated unexpected system behavior.<p>Improved performance of access rights check for applied solutions with a large number of roles, and for file mode infobases on low-performance computers. This improves the performance of form opening in the listed scenarios.</p></td></tr><tr title="Версия 8.3.7" class="compat tag_84 tag_1"><td><a name="86c6e29a-dc51-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The option to specify the first day of the week is implemented. It can be accessed in Designer (on the <span class="interface">Administration </span>menu, click <span class="interface">Reg</span><span class="interface">ional infobase settings</span>). When you create an infobase using platform version 8.3.7 or later without compatibility mode set, the first day of the week value is set to <span class="interface">Auto</span>. It is defined based on the <span class="interface">Language (Country)</span> property in regional infobase settings.<p>The choice of the first day of the week affects the following features:</p><ul><li>1C:Enterprise script methods: <span class="term">BegOfWeek</span><span class="term">()</span>, <span class="term">EndOfWeek</span><span class="term">()</span>, <span class="term">WeekOfYear</span><span class="term">()</span></li><li>Query language functions: <span class="term">BeginOfPeriod()</span>, <span class="term">E</span><span class="term">ndOfPeriod</span><span class="term">()</span>, <span class="term">Week</span><span class="term">()</span></li><li>Data composition system functions: <span class="term">BeginOfPeriod()</span>, <span class="term">EndOfPeriod()</span>, <span class="term">Week()</span>, and functions of nested fields of <span class="term">Date </span>type: <span class="term">BegOfWeek</span>, <span class="term">EndOfWeek</span>, <span class="term">WeekOfYear</span></li><li>Scheduled job schedules</li><li>Balance virtual tables and balance and turnover virtual tables of accumulation registers</li><li>Balance virtual tables and balance and turnover virtual tables of accounting registers</li></ul><p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The first day of the week was always Monday.</td><td>Better usability in countries where the first day of the week in not Monday.</td></tr><tr title="Версия 8.3.7" class="compat tag_26 tag_1"><td><a name="d8c741c0-e422-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>You can edit multilingual spreadsheet documents in managed forms, provided that these documents are templates. The list of languages is obtained directly from a template.<p>In managed forms, spreadsheet documents are edited and displayed using the language specified in the <span class="term">LanguageCode</span> spreadsheet document property. Strings in other languages are never changed.</p><p>The <span class="term">SpreadsheetDocument</span><span class="term">.Template</span> property is implemented.</p><p>This change is not implemented in 8.3.6 compatibility mode.</p><p>The <span class="term">FillPropertyValues()</span> method never copies the <span class="term">Template</span> property (regardless of the compatibility mode).</p></td><td>In managed forms, spreadsheet documents were always edited using the current language.<p>When the platform displayed a spreadsheet document:</p><ul><li>The thin client did not use the <span class="term">LanguageCode</span> property.</li><li>The web client used the <span class="term">LanguageCode</span> property.</li></ul><p>When spreadsheet document text was edited using 1C:Enterprise script, strings in the current language were written and strings in other languages were lost.</p></td><td>You can edit multilingual spreadsheet documents in 1C:Enterprise mode.</td></tr><tr title="Версия 8.3.7" class="compat tag_23 tag_1"><td><a name="f9d5c989-e441-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>When the <span class="term">Presentation</span> field of the <span class="term">TasksByPerformer</span> virtual table is generated, the fact that the presentation of the corresponding <span class="term">Task</span> object can be redefined is taken into account.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>When the <span class="term">Presentation</span> field of the <span class="term">TasksByPerf</span><span class="term">ormer</span> virtual table was generated, the fact that the presentation of the corresponding <span class="term">Task</span> object could be redefined was not taken into account. The default presentation was always used instead.</td><td>Eliminated unexpected system behavior.
</td></tr><tr title="Версия 8.3.7" class="compat tag_45 tag_1"><td><a name="37c3d009-e444-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>The query object model is improved.<p>The <span class="term">Find() </span>method is implemented for the following objects: <span class="term">QuerySchemaIndexExpressions</span>, <span class="term">QuerySchemaExpressions</span>, <span class="term">QuerySchemaOrderExpressions</span>, <span class="term">QuerySchemaAvailableFields</span>, <span class="term">QuerySchemaAvailableTableParameters</span>, <span class="term">Q</span><span class="term">uerySchemaTableParameters</span>, <span class="term">QuerySchemaFields</span>, <span class="term">QuerySchemaColumns</span>, <span class="term">QuerySchemaTableForUpdate</span>, and <span class="term">QuerySchemaAvailableTables</span>. The <span class="term">FindByName() </span>and <span class="term">FindByAlias() </span>methods are implemented for the following objects: <span class="term">QuerySchemaQuerySourceJoins</span> and <span class="term">QuerySchemaSources</span>. The <span class="term">FindByExpression()</span> method is implemented for the following objects: <span class="term">QuerySchemaTotalCalculationFields</span> and <span class="term">QuerySchemaTotalExpressions</span>. The <span class="term">QuerySchemaTotalCalculationFields</span><span class="term">.FindByColumnName(</span><span class="term">)</span> method is implemented. The <span class="term">QuerySchemaTotalExpressions</span><span class="term">.</span><span class="term">FindByField</span><span class="term">() </span>method is implemented. The <span class="term">QuerySchemaSources</span><span class="term">.GetRootSources</span><span class="term">()</span> method is implemented.</p><p>New <span class="term">Add()</span> method variant is implemented for the following objects: <span class="term">QuerySchemaOrderExpressions</span>, <span class="term">QuerySchemaQuerySourceJoins</span>,<span class="term"> </span><span class="term">QuerySchemaTablesForUpdate</span>, and<span class="term"> </span><span class="term">QuerySchemaTotalExpressions</span><span class="term">.</span></p><p>For the <span class="term">QuerySchemaFields.Add()</span> method the optional <span class="term">Column </span>parameter is implemented.</p><p>The <span class="term">SourceAlias</span> parameter of <span class="term">QuerySchemaQuerySourceJoins</span>.<span class="term">Add()</span> method can have values of the following types: <span class="term">String</span> and <span class="term">QuerySchemaSource</span>.</p><p>The <span class="term">QuerySchemaTotalExpressions.Add() </span>method parameter can have values of the following types: <span class="term">String</span>, <span class="term">QuerySchemaColumn</span>, and <span class="term">QuerySchemaExpression</span>.</p><p>The behavior of <span class="term">QuerySchemaTotalCalculationFields.Add()</span> method is modified for scenarios when its parameter has a value of <span class="term">String</span> type.</p><p>The <span class="term">QuerySchemaNestedTable.Fields</span> property has <span class="term">QuerySchemaFields</span> type. Passing a text containing a batch query or a table drop query to the <span class="term">QuerySchemaSelectQuery.SetQueryText()</span> method raises an exception. The "For a nested table" variant of the <span class="term">QuerySchemaExpressions.Add()</span> method is declared obsolete. This change is not implemented in 8.3.6 compatibility mode.</p></td><td>These features were not provided.<p>The <span class="term">QuerySchemaNestedTable.Fields</span> property had <span class="term">QuerySchemaExpressions</span> type.</p><p>If a text containing a batch query was passed to the <span class="term">QuerySchemaSelectQuery.SetQueryText</span><span class="term">() </span>method, the first query in the batch was used. If a text containing a table drop query was passed to the <span class="term">QuerySchemaSelectQuery.SetQueryText()</span> method, an empty query was created.</p><p>The "For a nested table" variant of the <span class="term">QuerySchemaExpressions.Add() </span>method was available.</p></td><td>Improved usability of query object model.</td></tr><tr title="Версия 8.3.7" class="compat tag_25 tag_1"><td><a name="467b34f3-e743-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the data composition system, the data set link type is replaced with inner link if a filter containing only fields from the data set being linked is applied. Conditions that do not include inner links are added to the <span class="term">RecordsFilter</span> property of groupings that contain at least one data set with fields used in these conditions.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>In the data composition system, the data set link type was always set to inner link when a filter included a linked data set field.</td><td>Eliminated unexpected system behavior when fields from multiple data sets were used in a filter.</td></tr><tr title="Версия 8.3.7" class="compat tag_66 tag_1"><td><a name="99669ea5-09d2-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 66); return false;">Navigation links</a>.<br></td><td>The <span class="term">G</span><span class="term">otoURL </span>method parameter value is not decoded prior to passing it to the operating system (the original link is passed).<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>The <span class="term">GotoURL </span>method parameter value might be decoded prior to passing it to the operating system:<ul><li>In 8.3.4 or earlier compatibility mode it was not decoded (the original link was passed).</li><li>In 8.3.5 and 8.3.6 compatibility modes it was decoded.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.7" class="tag_38"><td><a name="27e4af21-5543-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>Writing an extension to an infobase is available in the following cases: the session that performs the writing is not running in the safe mode, or the session security profile allows this operation.<p>When attaching an extension, the platform does not check whether the extension fits the session security profile restrictions.</p></td><td>Writing an extension to an infobase was only available if the session was running in the safe mode,<p>When attaching an extension, the platform checked whether the extension fit the session security profile restrictions.</p></td><td>Security profiles process extensions in the same way as they process external reports and data processors.</td></tr><tr title="Версия 8.3.7" class="tag_23"><td><a name="03af94f6-a8ad-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>If a new object number (this includes document, catalog item, chart of characteristic types item, business process, and task numbers) is issued inside a transaction, it is reused even if the autonumbering mode is set to <span class="interface">Do not Release Autom</span><span class="interface">atically</span>, including scenarios where the object is not written inside the transaction.<p>The <span class="interface">Do not Release Automatically</span> autonumbering mode only affects the numbers issued outside transactions. In other words, if a number is issued outside a transaction and it is not used (because the object is not written), it is not reused in the <span class="interface">Do not Release Automatically</span> mode, and it is reused in the <span class="interface">Release Automatically</span> mode.</p></td><td>If a new object number (this included document, catalog item, chart of characteristic types item, business process, and task numbers) was issued inside a transaction and the object was not written, that number was not reused in the <span class="interface">Do not Release Automatically</span> mode.</td><td>Reduced number of unused object numbers in scenarios where object numbers are issued in transactions and those objects are not written.</td></tr><tr title="Версия 8.3.7" class="tag_14 tag_64"><td><a name="255efe95-b84f-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>If you want to use fonts other than <span class="interface">Auto </span>in your applied solutions, it is recommended that you select from the following fonts: <ul><li>1C:Enterprise style fonts:</li><ul><li>Small text font</li><li>Normal text font</li><li>Large text font</li><li>Very large text font</li></ul><li>Vector fonts from the "MS Core Fonts" collection:</li><ul><li>Andale Mono</li><li>Arial </li><li>Arial Black </li><li>Comic Sans MS </li><li>Courier New </li><li>Georgia </li><li>Impact </li><li>Times New Roman </li><li>Trebuchet MS </li><li>Verdana</li><li>Webdings</li></ul></ul><p>If you use a font that is not listed here, from items might not be displayed correctly in some modes (including client applications).</p></td><td>The list of recommended fonts was not available.</td><td>A list of fonts recommended for use to ensure uniform applied solution appearance across environments is now available.</td></tr><tr title="Версия 8.3.7" class="compat tag_115 tag_1"><td><a name="68c2820a-b90e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The algorithm that calculates the font size based on the font properties specified for a fortm item is changed. This might lead to the change of the font scale for the form items that have the <span class="interface">Scale </span>part of the <span class="interface">Font </span>property set to a nondefalut value.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>In some cases the <span class="interface">Scale </span>part of the <span class="interface">Font </span>property of form items was ignored, so that the text displayed on a form item had the default size.</td><td>Eliminated unexpected system behavior.<p>In some cases the font size of form items might change.</p></td></tr></table><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e768208f-abaa-11e4-b1db-0050569f678a">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.7" class="tag_0"><td><a name="7ae0d087-e436-11e4-a3f7-0050569f678a"></a>Spreadsheet document property that describes the language for displaying and editing the document. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">TemplateLanguageCode</span>.</li></ul></td><td><ul><li><span class="term">LanguageCode</span>.</li></ul></td></tr><tr title="Версия 8.3.7" class="tag_0"><td><a name="4bee4452-41c7-11e5-a3f7-0050569f678a"></a>Presentations of automatically generated graphical schema field command groups. The command groups are displayed in the form customization dialog box in 1C:Enterprise mode.</td><td><ul><li><span class="interface">Size and alignment</span><span class="interface"> group</span> (contains the <span class="interface">Align left </span>command)</li><li><span class="interface">Size and alignment group </span>(contains the<span class="interface"> Align top </span>command)</li><li><span class="interface">Group </span>group (contains the<span class="interface"> Auto space: horizontal </span>command)</li><li><span class="interface">Group</span> group (contains the <span class="interface">Bring to front </span>command)</li><li><span class="interface">Group </span>group (contains the<span class="interface"> Send to back </span>command)</li></ul></td><td><ul><li><span class="interface">Horizontal alignment</span></li><li><span class="interface">Vertical alignment</span></li><li><span class="interface">Distribute</span></li><li><span class="interface">Bring forward</span></li><li><span class="interface">Send backward</span></li></ul></td></tr></table><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e7682090-abaa-11e4-b1db-0050569f678a">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.7" class="tag_20"><td><a name="077fc13b-40fe-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The option to debug configurations on the mobile platform is implemented. The debugging can only be performed over HTTP (you can select this option in Designer).</td><td>This feature was not provided.</td><td>Streamlined development of applied solutions for the mobile platform.</td></tr><tr title="Версия 8.3.7" class="tag_77"><td><a name="393745b0-4d7b-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br></td><td>The <span class="interface">Print </span>mobile application extension, which is used for printing from mobile applications, is implemented.<p>The mobile application builder supports building mobile applications that require this extension.</p></td><td>This feature was not provided.</td><td>Reduced list of required permissions for mobile applications that do not require printing.</td></tr><tr title="Версия 8.3.7" class="tag_26"><td><a name="431675a5-4d8c-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The brightness of frozen spreadsheet document areas is reduced by 2.5%.</td><td>The brightness of frozen spreadsheet document areas was reduced by 10%.</td><td>Better look and feel of spreadsheet documents with frozen areas.</td></tr><tr title="Версия 8.3.7" class="tag_69"><td><a name="17cb8c66-52d3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The following string processing functions previously available for the personal computer platform are now implemented for the mobile platform: <span class="term">StrTemplate</span><span class="term">()</span>, <span class="term">StrCompare</span><span class="term">()</span>, <span class="term">StrStartWit</span><span class="term">h</span><span class="term">()</span>, <span class="term">StrEndsW</span><span class="term">ith</span><span class="term">()</span>, <span class="term">StrFind()</span>, <span class="term">SrtSplit</span><span class="term">()</span>, and <span class="term">StrConcat</span><span class="term">()</span>.<p>The <span class="term">SearchDirection</span> system enumeration is implemented.</p></td><td>This feature was not provided.</td><td>Unified string processing for the personal computer platform and the mobile platform.</td></tr><tr title="Версия 8.3.7" class="tag_115"><td><a name="d8300166-5548-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The <span class="interface">Representation </span>property of a managed form button located in a form title command bar affects the button view. When the platform defines the button view, it ignores the properties of the command linked to the button.</td><td>The <span class="interface">Representation </span>property of a managed form button located in a form title command bar did not affect the button view. When the platform defined the button view, it ignored the properties of the command linked to the button.</td><td>You can manage the view of buttons located in form title command bars using the button properties.</td></tr><tr title="Версия 8.3.7" class="tag_140"><td><a name="d77919ad-603a-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 140); return false;">Special tools</a>.<br></td><td>For the <span class="term">TelephonyTools.NumberDialingSupported</span><span class="term">()</span> method the <span class="term">DirectCall </span>parameter is implemented. The parameter streamlines the check for number dialing support.</td><td>The <span class="term">TelephonyTools.NumberDialingSupported</span><span class="term">()</span> method did not support any check options.</td><td>Унифицирована возможность проверки работы со специальными возможностями на мобильной платформе.</td></tr><tr title="Версия 8.3.7" class="tag_29"><td><a name="a0029280-61c4-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of Windows Phone operating system version 8.1 or later (ARM and x86 architectures) and touch devices that run Windows version 8.1 or later (ARM and x86) is implemented.<p>The mobile platform for Windows Phone supports all mobile platform features available on other operating systems, excluding:</p><ul><li>Conversion of geographical coordinates to addresses and back, and <span class="term">ShowOnMap</span><span class="term">()</span> global context method</li><li>Barcode scanning</li><li>Phone call log</li><li>Printing</li><li>Receiving text messages</li><li>Notifications</li><li>Contacts</li><li>Calendars</li></ul><p>The mobile platform specifics are described in the documentation.</p><p>The mobile platform distribution file <span class="interface">mobile.zip</span> is complemented with new data.</p><p>This option is implemented as beta version.</p></td><td>This feature was not provided.</td><td>Extended support of operating systems for mobile and touch devices.</td></tr><tr title="Версия 8.3.7" class="tag_32"><td><a name="af699957-61d6-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>Mobile application builder for Windows Phone operating system is implemented. It supports Windows Phone 8.1 or later.<p>New builder parameters are added:</p><ul><li>The option to build applications for Windows operating system</li><li>Support of graphic assets required for Windows operating system</li></ul><p>Publishing of built applications to Windows Store is not supported.</p><p>When loading mobile platform data from the<span class="interface"> mobile.zip </span>file to mobile platform builder, you have the option to load only mobile operating systems that are present in the archive.</p><p>The option to specify different application IDs for different mobile operating systems is supported.</p><p>The option to export developer certificates from the mobile application builder database is implemented.</p></td><td>Mobile application builder did not support Windows operating system.<p>Attempts to load the mobile platform from the <span class="interface">mobile.zip</span> file to mobile application builder were only successful if the file contained platform versions for both Android and iOS.</p><p>A single mobile application ID was assigned for Android and iOS builds.</p><p>Exporting developer cerificates from the mobile application builder database was not supported.</p></td><td>Mobile application builder supports Windows operating system, and features other improvements.</td></tr><tr title="Версия 8.3.7" class="tag_86 tag_115"><td><a name="af636ff8-6811-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>On the mobile platform, the <span class="interface">Show in list</span> command, which was perviously available only on the personal computer platofrm, is implemented.<p>The <span class="term">ManagedForm.ExecuteNavigation()</span> method and the <span class="term">NavigationProcessing</span> managed form event are implemented.</p></td><td>This feature was not provided.</td><td>The interfaces of the mobile and personal computer platforms are unified.</td></tr><tr title="Версия 8.3.7" class="tag_65"><td><a name="33c1f741-6812-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>On the mobile platform, the option to use a web service whose address does not match the address specified in a WSDL file imported to the applied solution (<span class="interface">WS-reference</span> configuration object) is implemented.</td><td>This feature was not provided.</td><td>Web servfice operations on the mobile and personal computer platforms are unified.</td></tr><tr title="Версия 8.3.7" class="tag_115"><td><a name="3a4a22aa-98cb-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>On the mobile platform, the option to use a selection list to provide a value for a managed form input field that displays date and time is implemented.</td><td>On the mobile platform, drop-down lists were not available.</td><td>On the mobile platform, the option to use drop-down lists in the input fields that display date and time is now available.</td></tr><tr title="Версия 8.3.7" class="tag_115"><td><a name="6ad0ab6b-98cc-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The option to switch between the input fields using the <span class="interface">Enter</span> button of the virtual keyboard (i.e. without closing the keyboard) is implemented. The option to switch between the input fields using <span class="interface">Tab</span>/<span class="interface">Shift+Tab</span> keys of a physical keyboard connected via Bluetooth is also implemented.</td><td>The option to switch between the input fields without closing the virtual keyboard was not available. To switch between the fields, a mobile application user had to close the keyboard, then switch to another field, and then open the keyboard.</td><td>Improved mobile application usability is scenarios where multiple input fields are available in a single form.</td></tr></table><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h2><a name="b89795d6-1654-11e5-a3f7-0050569f678a">Library updates
</a></h2><ul><li title="Версия 8.3.7" class="tag_0"><a name="a27f2ca1-3104-11e5-a3f7-0050569f678a"></a>Known vulnerabilities of cURL library are elimitaned.</li><li title="Версия 8.3.7" class="tag_0"><a name="fecd596c-ce44-11e5-a3f7-0050569f678a"></a>The OpenSSL library is updated to version 1.0.0t.</li><li title="Версия 8.3.7" class="tag_0"><a name="c5e91ded-dc53-11e5-a3f7-0050569f678a"></a>The libxml2 library is updated to eliminate vulnerabilities.</li><li title="Версия 8.3.7" class="tag_0"><a name="deb0b979-dc53-11e5-a3f7-0050569f678a"></a>The libxslt library is updated to eliminate vulnerabilities.</li></ul><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h2><a name="e7682091-abaa-11e4-b1db-0050569f678a">Transition from the previous version to the version 8.3.7</a></h2><ul><li title="Версия 8.3.7" class="tag_0"><a name="e7682092-abaa-11e4-b1db-0050569f678a"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.7.
</li><li title="Версия 8.3.7" class="tag_0"><a name="e7682093-abaa-11e4-b1db-0050569f678a"></a>Some features that are added in version 8.3.7 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.7" class="tag_0"><a name="1fa0680e-da03-11e4-a3f7-0050569f678a"></a>In order to use the new format of full-text search index and improve the performance of the input by string feature, clearing the full-text search index and building a new index is required. The <span class="interface">Compatibility mode</span> property must be set to <span class="interface">None</span> during these operations.</li><li title="Версия 8.3.7" class="tag_0"><a name="48490512-da0d-11e4-a3f7-0050569f678a"></a>In the web client, the cryptography extension is required in order to access all certificate fields using the <span class="term">Issuer</span> and <span class="term">Subject</span> properties of the <span class="term">CryptoCertificate</span> object.</li></ul><p><a href="#e7682089-abaa-11e4-b1db-0050569f678a"><small>Table of contents</small></a></p><h1><a name="eb969ada-881f-11e3-b57b-e61f135f174b">Version 8.3.6</a></h1><p title="Версия 8.3.6" class="tag_0"><a name="eb969ae5-881f-11e3-b57b-e61f135f174b"></a>Version 8.3.6 includes known bug fixes and functionality modifications.
</p><p title="Версия 8.3.6" class="tag_0"><a name="f5a1f274-42fc-11e4-a179-0050569f678a"></a>To obtain a link to an entry of the V8Update file, double-click any of the entry lines. This opens a pop-up window with the link available for copying to the clipboard. This feature is only available if JavaScript is enabled.</p><hr></hr><ul><li><a href="#eb969adb-881f-11e3-b57b-e61f135f174b">New functionality and changes</a></li><li><a href="#eb969adc-881f-11e3-b57b-e61f135f174b">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#eb969add-881f-11e3-b57b-e61f135f174b">Optimization</a></li><li><a href="#eb969ade-881f-11e3-b57b-e61f135f174b">Changes that affect system behavior</a></li><li><a href="#eb969adf-881f-11e3-b57b-e61f135f174b">Changes that require modification of configuration and administrative settings</a></li><li><a href="#eb969ae0-881f-11e3-b57b-e61f135f174b">Renamed objects</a></li><li><a href="#eb969ae1-881f-11e3-b57b-e61f135f174b">Mobile platform</a></li><li><a href="#76779dc1-0b55-11e5-a3f7-0050569f678a">Library updates</a></li><li><a href="#eb969ae2-881f-11e3-b57b-e61f135f174b">Transition from the previous version to the version 8.3.6</a></li></ul><h2><a name="eb969adb-881f-11e3-b57b-e61f135f174b">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.6" class="compat tag_2 tag_1"><td><a name="e6e11c5d-e72f-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.3.5</span> is added to the list of available values of the <span class="interface">Compatibility mode</span> property.
</td><td>Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3 and 8.3.4.
</td><td>In version 8.3.6 you can run configurations created in version 8.3.5 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.6 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.5 for working with the infobase even after the transition to version 8.3.6. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
</td></tr><tr title="Версия 8.3.6" class="tag_20"><td><a name="2bd554f7-e7e5-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer, in module text, bookmarks can be preserved between different work and module editing sessions.<p>To access the full list of bookmarks, on the <span class="interface">Edit </span>menu, click <span class="interface">Bookmarks</span>.</p></td><td>This feature was not provided.</td><td>Improved Designer usability,</td></tr><tr title="Версия 8.3.6" class="tag_20"><td><a name="e3dd461e-ea56-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>When renaming a configuration object, you have the option to update the object name usage instances in the entire configuration.<p>When deleting a configuration object, you have the option to search for the object name usage instances in the entire configuration.</p><p>When modifying or deleting a managed form item, attribute, or parameter, the check for usage instances of its name in the form module is performed. When renaming an item, attribute, or parameter, you have the option to update its name usage instances in the form module.</p><p>The<span class="interface"> Find references to object </span>operation now includes the search in module texts.</p><p>You can specify whether you want to use these options in the Designer options window.</p></td><td>These features were not provided.</td><td>Reduced chance of making errors when renaming or deleting configuration objects. Improved usability for developers.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="74e003a5-ebee-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Planner (a visual tool for managing schedule data) is implemented. A new "planner field" type is implemented for managed form fields. The <span class="term">Planner </span>object is implemented.<p>In the <span class="term">TimeScalePosition </span>system enumeration, the following values are implemented: <span class="term">Left </span>and <span class="term">Right</span> (when applied to a Gantt chart, both are treated as <span class="term">Top</span>).</p></td><td>This feature was not provided.</td><td>Improved user experience for scheduling (appointments, calendars, and so on).</td></tr><tr title="Версия 8.3.6" class="tag_67"><td><a name="f4dc0994-f85f-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>In Designer batch mode, you can bind an infobase that is not yet bound to the configuration repository (command-line option <span class="interface">/ConfigurationRepositoryBindCfg</span>).</td><td>This feature was not provided. <p>Infobases could be bound to repositories only interactively.</p></td><td>You can automate more configuration repository operations.</td></tr><tr title="Версия 8.3.6" class="tag_86 tag_115"><td><a name="e7fad4ad-faa7-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For managed form extensions for objects, catalogs, documents, charts of characteristic types, business processes, tasks, and information register records, the <span class="interface">Show in list</span> command is implemented.<p>For managed forms, the<span class="term"> ExecuteNavigation()</span> method and <span class="term">NavigationProcessing</span> event handler are implemented.</p></td><td>This feature was not provided.</td><td>Improved system usability for automatic object selection in a list being opened.</td></tr><tr title="Версия 8.3.6" class="tag_141 tag_14"><td><a name="41f256b3-fae7-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 141); return false;">System enumerations</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>For the <span class="term">SectionsPanelRepresentation</span> system enumeration, the following values are implemented: <span class="term">PictureOnTopAndText</span> and <span class="term">PictureOnLeftAndText</span>.<p>In the client application, in the sections panel editor, the following section view features are available:</p><ul><li>In <span class="interface">Version 8.2</span> interface compatibility mode:</li><ul><li><span class="term">Picture</span></li><li><span class="term">Text</span></li><li><span class="term">PictureAndText</span></li></ul><li>In <span class="interface">Taxi</span> interface compatibility mode:</li><ul><li><span class="term">Picture</span></li><li><span class="term">Text</span></li><li><span class="term">PictureAndText</span></li><li><span class="term">PictureOnTopAndText</span></li></ul></ul></td><td>For the <span class="term">SectionsPanelRepresentation </span>system enumeration, the following values were available: <span class="term">Picture</span>, <span class="term">Text</span>, <span class="term">PictureAndText</span><span class="term">.</span> </td><td>
<p>Extended section view capabilities for the sections panel in the <span class="interface">Taxi</span> interface.</p></td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="a5c6dd12-fdc8-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The option to specify a graphical schema field as a source of command bar and managed form button commands is implemented.<p>The only commands available in the web client are print and preview.</p><p>In the Russian interface some of the graphical schema commands are renamed to the following:</p><ul><li><span class="interface">Выровнять по </span><span class="interface">левому краю</span></li><li><span class="interface">Выровнять по </span><span class="interface">правому краю</span></li><li><span class="interface">Выровнять по ве</span><span class="interface">рхнему краю</span></li><li><span class="interface">Выровнять по нижнему краю</span></li><li><span class="interface">Переместить вперед</span></li><li><span class="interface">Выровнять по центру</span></li><li><span class="interface">Выровнять по середине</span></li></ul></td><td>The option to specify a graphical schema field as a source of command bar and managed form button commands was not provided.<p>In the Russian interface some of the graphical schema commands had different names:
</p><ul><li><span class="interface">Выровнять влево</span></li><li><span class="interface">Выровнять вправо</span></li><li><span class="interface">Выровнять вверх</span></li><li><span class="interface">Выровнять вниз</span></li><li><span class="interface">Переместить вверх</span></li><li><span class="interface">Выровнять по центру горизонтально</span></li><li><span class="interface">Выровнять по центру вертикально</span></li></ul></td><td>Increased graphical schema usability.</td></tr><tr title="Версия 8.3.6" class="tag_10"><td><a name="7d3ae7c6-0037-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>An object integrity check utility is implemented. It checks the state of file system objects and database objects used by 1C:Enterprise and monitors their changes.<p>The 32-bit and 64-bit versions of the utility are available for Windows and Linux operating systems.</p></td><td>This feature was not provided.<p>File change monitoring was only available using third-party tools. Monitoring of database object changes was not available.</p></td><td>The option to perform system integrity checks to provide protection against unauthorized modifications is implemented.</td></tr><tr title="Версия 8.3.6" class="tag_37"><td><a name="ec06e93a-0057-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For the <span class="term">Get() </span>method of the<span class="term"> InternetMail </span>object, the <span class="term">MarkAsRead</span> parameter is implemented. This parameter only makes sense when the platfrom uses IMAP for email operations.<p>If the platform uses POP3, an attempt to use this parameter when it is set to <span class="term">False</span> generates an exception.</p><p>The platform behavior in 8.3.5 compatibility mode is not changed (for the part where the parameter is set to <span class="term">False</span>).</p></td><td>If the platform used IMAP for email operations, the execution of the <span class="term">Get()</span> method of the <span class="term">InternetMail</span> object gave different results depending on the value of the <span class="term">ArrayOfMessageHeadersOrIdentifies</span> parameter.<ul><li>If the parameter was not specified, the flag indicating whether a message was read was not set for messages retrieved from the mail server.</li><li>If the parameter was specified, the flag was set.</li></ul></td><td>Eliminated inconsistency in the platform behavior during email operations that use IMAP.</td></tr><tr title="Версия 8.3.6" class="tag_17"><td><a name="807a3e2b-005e-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>For the <span class="term">SCALL </span>and <span class="term">CALL </span>technological log events, new <span class="term">IName </span>and <span class="term">MNam</span><span class="term">e </span>fields are implemented. They store additional internal system call data. 1C Company experts might use that data while handling support requests.</td><td>This feature was not provided.</td><td>The technological log provides additional data that can be helpful for solving complex issues.</td></tr><tr title="Версия 8.3.6" class="tag_43"><td><a name="7477e74c-00eb-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The option to get data from a dynamic list (adjusted for column visibility settings and search options applied) is implemented.<p>The following methods are implemented for the managed form table extension for dynamic lists:</p><ul><li><span class="term">GetPerforming</span><span class="term">DataCompositionScheme</span><span class="term">()</span></li><li><span class="term">GetPerforming</span><span class="term">DataCompositionSettings()</span></li></ul></td><td>This feature was not provided.</td><td>The option to get dynamic list data that is visible to a user for future processing is available.</td></tr><tr title="Версия 8.3.6" class="tag_25"><td><a name="881bade2-00f4-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The following subordinate fields are implemented for data composition system fields that have <span class="term">Data </span>among their types: <span class="term">BegOfDay</span>, <span class="term">BegOfWeek</span>, <span class="term">BegOfTenDays</span>, <span class="term">BegOfMonth</span>, <span class="term">BegOfQuarter</span>, <span class="term">BegOfHalfYear</span>, <span class="term">BegOfYear</span>, <span class="term">EndOfDay</span>, <span class="term">EndOfWeek</span>, <span class="term">EndOfTenDays</span>, <span class="term">EndOfMonth</span>, <span class="term">EndOfQuarter</span>, <span class="term">EndOfHalfYear</span>, <span class="term">EndOfYear</span>, <span class="term">Day</span>, <span class="term">WeekDay</span>, <span class="term">WeekDayName</span>, <span class="term">DayOfYear</span>, <span class="term">WeekOfYear</span>, <span class="term">Month</span>, <span class="term">MonthName</span>, <span class="term">Quarter</span>, <span class="term">Year</span>, <span class="term">BegOfMinute</span>, <span class="term">BegOfHour</span>, <span class="term">EndOfMinute</span>, <span class="term">EndOfHour</span>, <span class="term">Minute</span>, and <span class="term">Hour</span>.</td><td>This feature was not provided. One could use user-defined expression fields to retrieve this data.</td><td>Simplified end-user operations with fields that include date and time.</td></tr><tr title="Версия 8.3.6" class="compat tag_69 tag_1"><td><a name="df1a5bfb-00fe-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The following string processing functions are implemented:<ul><li><span class="term">StrTemplate</span><span class="term">()</span> - replaces variables (such as %1) in a template string by actual values.</li><li><span class="term">StrCompare</span><span class="term">()</span> - performs lexicographic comparison of strings, case-insensitive.</li><li><span class="term">StrstartWit</span><span class="term">h</span><span class="term">()</span> - checks whether a string begins with a substring.</li><li><span class="term">StrEndsW</span><span class="term">ith</span><span class="term">()</span> - checks whether a string ends with a substring.</li><li><span class="term">StrFind()</span> - searches for a substring in both directions, anywhere in the line.</li><li><span class="term">SrtSplit</span><span class="term">()</span> - splits a string into substrings based on the specified delimiter.</li><li><span class="term">StrConcat</span><span class="term">()</span> - merges strings included in the array of substrings.</li></ul><p>The <span class="term">SearchDirection</span> system enumeration is implemented.</p><p>The <span class="term">Find() </span>function is declared obsolete, it is supported for compatibility purposes.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>This feature was not provided.<p>Developers had the option to implement the functionality introduced in the new functions using 1C:Enterprise script.</p></td><td>Simplified implementation of some standard string processing algorithms.</td></tr><tr title="Версия 8.3.6" class="tag_28"><td><a name="410badb4-0122-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Storing accumulated web client statistics is implemented. This feature is intended for 1C Company experts. To enable it, run the web client with the <span class="term">SYSTEMWEBCLIENTSTAT</span> command-line option.</td><td>This feature was not provided.</td><td>The set of tools intended for platform performance quality control is expanded with a new tool.</td></tr><tr title="Версия 8.3.6" class="tag_26"><td><a name="01f0ea67-0125-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Importing data from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument) formats to spreadsheet documents is implemented. This operation can be performed both interactively and from 1C:Enterprise script.<p>The <span class="term">SpreadsheetDocumentValueReadingMode</span><span class="term"> </span>system enumeration is implemented. For the <span class="term">Read()</span> method of the <span class="term">SpreadsheetDocument</span> object, the <span class="term">ValueReadingMode</span> parameter is implemented.</p><p>Support of pasting areas copied to the clipboard from Microsoft Excel and OpenOffice Calc documents is implemented.</p></td><td>This feature was not provided.</td><td>Simplified data import from spreadsheet documents of the following formats: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument).</td></tr><tr title="Версия 8.3.6" class="tag_25 tag_43"><td><a name="34978c01-037b-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>For the <span class="term">DataCompositionSettingsComposer </span>object. the <span class="term">GetAvailableSettingsSource</span><span class="term">()</span> method is implemented.</td><td>This feature was not provided.</td><td>Simplified access to the available settings source of a data composer from another data composer. For example, you can use this feature when you open a new data composition settings editor form that uses the same source as the previous form.</td></tr><tr title="Версия 8.3.6" class="tag_37 tag_65"><td><a name="c843c2fe-4239-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>You can process JSON data using both stream and object approaches.<p>The following objects can be serialized to or deserialized from JSON: primitive types, <span class="term">Array</span>, <span class="term">FixedArray</span>, <span class="term">Structure</span>, <span class="term">FixedStructure</span>, <span class="term">Map</span>, and <span class="term">FixedMap</span>.</p><p>The <span class="term">JSONReader</span> and <span class="term">JSONWriter</span> objects are implemented. The <span class="term">WriteJSON()</span>, <span class="term">ReadJSON()</span>, <span class="term">WriteJSONDate()</span>, and <span class="term">ReadJSONDate()</span> global context methods are implemented.</p></td><td>This feature was not provided.<p>One could implement processing JSON data using 1C:Enterprise script tools.</p></td><td>Simplified interaction with applications (including web applications) that use JSON data format.<p>You can store various data types in JSON format, which provides an alternative to other formats, such as XML.</p></td></tr><tr title="Версия 8.3.6" class="tag_65"><td><a name="3edbf6ae-247d-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>Web services and HTTP services.<p>For the standard OData interface, getting responses in JSON format is implemented.</p></td><td>This feature was not provided.
For the standard OData interface, responses were only available in <span class="interface">Atom</span> format.
</td><td>The OData format is supported in more detail.<p>Using JSON format minimizes the volume of data transferred between the client and the server.</p></td></tr><tr title="Версия 8.3.6" class="tag_45"><td><a name="b1d73456-26c0-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>You can use logical expressions in descriptions of selection fields and in query result filter expressions (in the <span class="term">WHERE</span> clause).</td><td>This feature was not provided.<p>If a logical expression was required for describing a selection field, you had to use a selection clause.</p><p>Logical expressions in the <span class="term">WHERE</span> clause could be connected only by <span class="term">AND</span>, <span class="term">OR</span>, and <span class="term">NOT</span> logical operators, and they could not be composite.</p></td><td>Simplified writing and understanding of complex queries.</td></tr><tr title="Версия 8.3.6" class="tag_6 tag_10"><td><a name="483e8f9b-2869-11e4-903a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The automatic server cluster status monitoring feature is implemented. This includes monitoring of several cluster parameters and termination of processes that might cause any issues. The central cluster server agent performs the monitoring. The monitoring results are recorded to the technological log.<p>For the cluster, the <span class="interface">Server errors threshold</span> and <span class="interface">Terminate corrupted processes</span> properties are implemented.</p><p>For the<span class="term"> IServerAgentConnection</span> object, the <span class="term">SetClusterRecyclingErrorsCountTheshold()</span> and <span class="term">SetClusterRecyclingKillProblemProcesses()</span> methods are implemented.</p><p>For the <span class="interface">rac</span> utility, the <span class="term">--errors-count-threshold</span> and <span class="term">--kill-problem-processes</span> command-line options are implemented.</p><p>For the technological log, the <span class="term">ATTN</span> event is implemented.</p></td><td>Automatic server cluster status monitoring was not provided.</td><td>Increased server cluster reliability by timely detection and termination of processes that might cause issues.</td></tr><tr title="Версия 8.3.6" class="tag_51"><td><a name="6e918e8b-2939-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>The automated testing supports the <span class="interface">Taxi</span> interface. New automated testing features are added:<ul><li>For the <span class="term">TestedClientApplicationWindow</span>, the <span class="term">StartPage</span> property is implemented.</li><li>Navigation between windows is implemented. For the <span class="term">TestedClientApplicationWindow</span> object, the <span class="term">GotoStartPage(), </span><span class="term">GotoNextWindow()</span>, <span class="term">GotoPreviousWindow()</span>, and <span class="term">CloseUserMessagesPanel()</span> methods are implemented.</li><li>New options for testing managed form fields:</li><li>Create an item. For the <span class="term">TestedFormField</span> object, the <span class="term">Create()</span> method is implemented.</li><li>Cancel editing field data. For the <span class="term">TestedFormField</span> object, the <span class="term">CancelEdit()</span> method is implemented.</li><li>Open a drop-down list, wait for drop-down list generation, and select a list item. For the <span class="term">TestedFormField</span> object, the <span class="term">OpenDropList()</span>, <span class="term">CloseDropList()</span>, <span class="term">ExecuteChoiceFromDropList()</span>, <span class="term">WaitForDropListGeneration()</span>, and <span class="term">DropListIsOpen() </span>methods are implemented.</li></ul><p>
</p></td><td>The automated testing did not support the <span class="interface">Taxi</span> interface.</td><td>The automated testing can be used with the <span class="interface">Taxi</span> interface.</td></tr><tr title="Версия 8.3.6" class="tag_25 tag_43"><td><a name="07715d8f-2e91-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Items of report user settings and dynamic list user settings can be linked to managed form tables.<p>For the <span class="term">DataCompositionUserSettings</span> object, the <span class="term">Filter</span>, <span class="term">Order</span>, <span class="term">Selection</span>, <span class="term">ConditionalAppearance</span>, and <span class="term">Structure</span> columns are implemented.</p><p>The report user settings form and the dynamic list user settings form are modified: instead of text boxes with the option to open editors (filter, order, and so on), tabs with tables are implemented to provide uniformity with the data composition schema editor in Designer.</p><p>The <span class="interface">Settings</span> command of the report form is displayed in the main form command bar.</p></td><td>Items of user report settings and dynamic list settings could be linked only to managed form text boxes.<p>The report and dynamic list user settings forms had a different layout.</p><p>The <span class="interface">Settings</span> command of the report form was available in the <span class="interface">More</span> menu.</p></td><td>Improved standard report and dynamic list user settings form.</td></tr><tr title="Версия 8.3.6" class="compat tag_115 tag_1"><td><a name="4e8e94f5-2e97-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For the <span class="term">Enum</span> metadata object, the <span class="term">ChoiceHistoryOnInput</span> property is implemented. This property defines whether the choice history of a text box linked to an attribute of enumeration type is displayed and saved.<p>For enumerations whose values can be selected in a form, the input history is displayed and saved automatically.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>This feature was not provided.<p>The choice history for a text box linked to an attribute of enumeration type was neither displayed nor saved.</p></td><td>
<p>You can specify whether the choice history for a text box linked to an attribute of enumeration type is displayed and saved.</p></td></tr><tr title="Версия 8.3.6" class="tag_25"><td><a name="94022f52-333d-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>For the <span class="term">DataCompositionDetailsFieldValues</span> object a constructor is implemented.</td><td>The <span class="term">DataCompositionDetailsFieldValues</span><span class="term"> </span>object did not have a constructor.</td><td>You can fill detailed data using 1C:Enterprise script.</td></tr><tr title="Версия 8.3.6" class="tag_65"><td><a name="b4c3652d-38fc-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>For the <span class="term">HTTPConnection</span> object, you can call any HTTP methods (passing the method name as a string). In order to simplify the usage of <span class="term">PATCH</span> and <span class="term">HEAD</span> HTTP methods, the <span class="term">Patch()</span> and <span class="term">Head()</span> methods are implemented for the <span class="term">HTTPConnection</span> object.</td><td>These features were not provided.<p>The <span class="term">HTTPConnection</span> object could only be used to call the <span class="term">GET</span>, <span class="term">PUT</span>, <span class="term">POST</span>, and <span class="term">DELETE</span> methods.</p></td><td>Easier access to the full range of HTTP methods from applied solutions. </td></tr><tr title="Версия 8.3.6" class="tag_6 tag_10"><td><a name="cc7f0718-3cae-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>External<span class="term"> </span>session management functionality is extended. Methods that are called when a session is hibernated or restored from hibernation are implemented. You can specify a timeout for the external session management web service response.<p>For the external session management web service, the <span class="term">onHibernateSession()</span> and <span class="term">onWakeupSession()</span> methods are implemented.</p><p>For external session management web service connection string, the optional parameters are implemented: <span class="term">tout</span> sets an external session management web service response timeout, and <span class="term">wsver </span>specifies the external session management web service interface version. The new features are only available if the <span class="term">wsver</span><span class="term"> </span>parameter is set to 2.</p></td><td>These features were not provided.</td><td>The web service behavior is uniform with the licensing subsystem behavior.</td></tr><tr title="Версия 8.3.6" class="tag_56"><td><a name="7136055f-3cb9-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>FastInfoSet operations are refactored.</td><td>FastInfoSet operations had a different implementation.</td><td>Improved stability of FastInfoSet operations.</td></tr><tr title="Версия 8.3.6" class="tag_21"><td><a name="1bbb269c-3cbf-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>The full-text search index integrity check is implemented. For the full text search manager, the <span class="term">CheckIndex</span><span class="term">()</span> method is implemented.<p>The full-text search index update operations are recorded to the tecnological log. In the tecnological log, the <span class="term">FTEXTCheck</span> and <span class="term">FTEXTUpd</span> events are implemented. In the technological log the <span class="term">ftextupd</span> item is implemented.</p></td><td>These features were not provided.</td><td>Improved stability of full-text search.
An invalid full-text search index can be rebuilt.</td></tr><tr title="Версия 8.3.6" class="tag_45"><td><a name="ba5509d1-3d72-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>For the <span class="term">QuerySchemaTempTableDescription</span> object, the <span class="term">TableName</span> property is implemented. You can specify a temporary table name in the query builder.<p>For the <span class="term">QuerySchemaSources</span> object, the <span class="term">Alias</span> parameter of the <span class="term">Add</span><span class="term">()</span> method is implemented.</p></td><td>These features were not provided.</td><td>Improved functionality of the query software model.</td></tr><tr title="Версия 8.3.6" class="tag_20 tag_58 tag_38"><td><a name="3379567b-59ce-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 38); return false;">Configuration extensions</a>.<br></td><td>More options for modification of applied solutions (including cloud systems) without disabling their support. You can create configuration extensions and use them to implement applied solution modifications (which do not affect the data structure), so that the applied solution support is not disabled, and all modifications take place in a dedicated object (extension), which is easily connected to and disconnected from the applied solution.<p>You can use extensions to modify forms, create reports and data processors, and create new subsystems. You can apply a configuration extension both in 1C:Enterprise mode and in Designer. You can specify a custom extension set for each separated infobase area.</p></td><td>This feature was not provided. Applied solution developers could create external reports and data processors and modify the applied solution configuration, which resulted in disabling support and did not allow making modifications in different areas of a separated infobase.</td><td>The new feature is intended for making small configuration modifications at the deployment stage (including modifications of separated infobases and cloud systems) more easily and with less dependence on vendor configuration modifications.</td></tr><tr title="Версия 8.3.6" class="tag_64"><td><a name="9d652674-a78b-11e4-b1db-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New pictures are added to the picture library: <span class="term">GoForward</span>, <span class="term">Go</span><span class="term">Back</span>, <span class="term">GoToBegin</span>, <span class="term">GoToEnd</span>, <span class="term">Today</span>, <span class="term">ShowInList</span>.</td><td>The listed pictures were not available in the picture library.</td><td>More content for the picture library.</td></tr><tr title="Версия 8.3.6" class="tag_142"><td><a name="b48e1b55-c704-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 142); return false;">Database configuration updates</a>.<br></td><td>The documentation describes Designer batch mode command-line options that manage background and dynamic database configuration updates.</td><td>The new Designer batch mode command-line options that manage background and dynamic database configuration updates were not listed in the documentation.</td><td>Fixed documentation error.</td></tr><tr title="Версия 8.3.6" class="tag_29 tag_28"><td><a name="f5cd8ea2-62cc-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Support of Microsoft Windows 10 operating system is implemented.<p>Support of Microsoft Information Services 10.0 web server is implemented.</p><p>Support of Microsoft Edge web browser is implemented, with the following limitations:</p><ul><li>Add-ins are not supported</li><li>File system extension is not available</li><li>Cryptography extension is not available</li></ul></td><td>Microsoft Windows 10 operating system was not supported.<p>Microsoft Information Services 10.0 web server was not supported.</p><p>Microsoft Edge web browser was not supported.</p></td><td>Extended list of supported operating systems and web browsers.</td></tr><tr title="Версия 8.3.6" class="tag_19"><td><a name="b2fbbfc4-9cb3-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Support of PostgreSQL version 9.4 is implemented.</td><td>This PostgreSQL version was not supported.</td><td>Extended list of supported PostgreSQL versions.</td></tr></table><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="eb969adc-881f-11e3-b57b-e61f135f174b">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.6" class="tag_86"><td><a name="d5e85920-fb81-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>In the <span class="interface">Taxi</span> interface, in the functions menu, you can search for commands by their presentations. The search is performed in all sections (not only in the commands of the current section).<p>Commands for specifying navigation and action panel settings are moved to the submenu to the right of the search field.</p><p>In the <span class="interface">Taxi</span> interface, pressing <span class="interface">F10</span> opens the functions menu.</p></td><td>The option to search for a command by a part of its presentation was not provided.<p>Commands for specifying navigation and action panel settings were displayed as links in the right part of the functions menu.</p><p>In the <span class="interface">Taxi</span> interface, pressing <span class="interface">F10</span> opened the main menu.</p></td><td>Improved usability of the function menu.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="0842f853-fc3a-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If all of the managed form command bar buttons have their <span class="term">OnlyInAllActions</span> parameters set to <span class="term">False</span> and some of these buttons do not fit the command bar width, the <span class="interface">More</span> button is added to the command bar, with a submenu that contains all of the command bar commands.</td><td>If all of the managed form command bar buttons had their <span class="term">OnlyInAllActions</span> parameters set to <span class="term">False</span> and some of these buttons did not fit the command bar width, there was no way to access the commands that did not fit.</td><td>If the command bar has small size, all of its commands are still available.</td></tr><tr title="Версия 8.3.6" class="tag_14"><td><a name="998d2760-26bc-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>You can fully replace the splash screen that is displayed during the startup of the thin, thick, and web clients.<p>To replace a splash screen in your applied solution, submit a request to 1C Company</p></td><td>This feature was not provided.</td><td>In particular cases, you can use a splash screen that is fully customized by the company that uses the applied solution, provided that the splash screen is approved by 1C Company.</td></tr><tr title="Версия 8.3.6" class="tag_28"><td><a name="767b94c4-26be-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Web browser pop-up windows are no longer displayed during the printing of spreadsheet documents.</td><td>When spreadsheet documents were being printed, web browser pop-up windows were displayed.</td><td>Simplified printing of spreadsheet documents for end users.<p>In the <span class="interface">Taxi</span> or <span class="interface">Forms in</span><span class="interface"> tabs</span> interface mode, if the applied solution does not use modal calls, it does not require additional web browser setup.</p></td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="c7a564cc-38eb-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed forms, if the <span class="interface">Create</span> command is available for a text box, it is present in the context menu of the text box.</td><td>The <span class="interface">Create</span> command was never present in text box context menus.</td><td>Improved usability of text boxes.</td></tr></table><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="eb969add-881f-11e3-b57b-e61f135f174b">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.6" class="tag_21"><td><a name="e364a6c2-02b6-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>The full-text search algorithm is optimized for scenarios where a search string is used multiple times (for example, getting the next batch of search results).<p>The full-text search algorithm is optimized for scenarios where a user does not have access rights for some objects returned by the search.</p></td><td>The full-text search performance was insufficient.</td><td>Improved full-text search performance for infobases containing a large number of items, and also in scenarios where a user does not have access rights for some objects returned by the search.</td></tr><tr title="Версия 8.3.6" class="tag_21"><td><a name="bf5103e9-05c2-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Optimized memory usage for fuzzy search (the search that uses the <span class="term">#</span> operator). The search for similar words is optimized.</td><td>Fuzzy search might cause a memory overflow which, in turn, caused the system shutdown.<p>The search for similar words might take a long time.</p></td><td>Increased stability of the fuzzy search in scenarios where the full text search index has a large size.</td></tr><tr title="Версия 8.3.6" class="tag_28"><td><a name="b71d0f74-0058-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The web client performance is improved in the following scenarios:<ul><li>Loading web client,. including scenarios with slow connection</li><li>Opening forms</li><li>General performance improvements in a variety of scenarios</li></ul><p>The web client now uses Google Closure Compiler.
</p></td><td>The web client performance was insufficient.</td><td>Improved web client performance.</td></tr><tr title="Версия 8.3.6" class="tag_69"><td><a name="0e2d589b-247e-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The loading time of 1C:Enterprise script modules is slightly reduced.</td><td>The loading of 1C:Enterprise script modules was not fast enough.</td><td>Slightly reduced startup time for applied solutions that include a large number of 1C:Enterprise script modules.</td></tr><tr title="Версия 8.3.6" class="tag_14"><td><a name="6fc60a9b-247e-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The startup time of the client application (before the authentication dialog appears) is slightly reduced.</td><td>The client application startup was not fast enough.</td><td>Slightly reduced startup time of the client application.</td></tr><tr title="Версия 8.3.6" class="compat tag_67 tag_1"><td><a name="30551786-003b-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>The performance of the following operations is improved:<ul><li>Creating a repository</li><li>First connection to a repository</li><li>Storing objects in a repository</li><li>Updating objects from a repository</li><li>Updating configuration from a repository</li></ul><p>The performance of compatibility mode change operations is improved.</p><p>The 1C:Enterprise version 8.3.3 compatibility mode is implemented for configuration repositories.</p><p>The configuration repository performance is improved in scenarios where the configuration repository compatibility mode is set to <span class="interface">Do no use</span>.</p></td><td>The performance of configuration repository operations was insufficient.</td><td>Improved configuration repository performance.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="68756be5-286a-11e4-903a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The strong data compression algorithm for large data volumes (more than 64 KB) transferred between the client and the server (or a web server extension) is optimized. This slightly reduces the time required to open managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode.</td><td>The strong data compression algorithm was less efficient.</td><td>Slightly reduced time of opening managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode.</td></tr><tr title="Версия 8.3.6" class="tag_65"><td><a name="19991752-38fb-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>Faster processing of requests that call the standard OData interface.</td><td>Performance of requests that called the standard OData interface was insufficient.</td><td>The performance of operations with the standard OData interface is improved.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="6e530e02-3cdb-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Improved performance of opening managed forms in the following scenarios:<ul><li>A form has a large number of items.</li><li>A form has a large number of attributes.</li><li>The list of attributes and form items is significantly changed using 1C:Enterprise script.</li><li>A large number of users are working with managed forms.</li></ul></td><td>The performance of opening managed forms in the listed scenarios was lower.</td><td>Improved usability of managed forms.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="ea53e31a-3cdb-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Managed form conditional appearance is optimized.</td><td>The performance of managed form conditional appearance was lower.</td><td>Improved usability of managed forms with conditional appearance.</td></tr><tr title="Версия 8.3.6" class="tag_20"><td><a name="ed88bbe5-09e0-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Performance of base configuration updates (update configuration from file, load configuration from file, and get specific configuration version from configuration repository) is improved.</td><td>Performance of base configuration updates was insufficient.</td><td>Better usability for developers.</td></tr><tr title="Версия 8.3.6" class="tag_19 tag_10"><td><a name="f5028588-40df-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>For the file mode, the option to restructure the infobase so that all data required to open the infobase is at the beginning of the <span class="interface">1Cv8.1CD</span> file is implemented. This improves the performance of infobase opening.<p>This type of restructuring is performed during the compressing of infobase tables (which is available from a Designer dialog box and as a command-line option), or during infobase verification with the <span class="interface">chdfl</span> utility with the <span class="interface">Correct errors </span>check box selected.</p><p>It is recommended that you always perform this optimization after you make any configuration changes (and the associated infobase restructuring) that result in database structure changes.</p></td><td>Internal information required for opening an infobase was evenly distibuted within the <span class="interface">1Cv8.1CD</span> infobase file.</td><td>Improved performance of opening file infobases, especially in scenarios where the infobase is located on a network resource.</td></tr><tr title="Версия 8.3.6" class="tag_19"><td><a name="99365dc4-7c88-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>In client/server mode with PostgreSQL DMBS, the query that is executed when deleting records from tables of extra dimensions of accounting registers is optimized.</td><td>In client/server mode with PostgreSQL DMBS, the performance of the query that was executed when deleting records from tables of extra dimensions of accounting registers was insufficient.</td><td>Improved performance of deleting accounting register records.</td></tr></table><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="eb969ade-881f-11e3-b57b-e61f135f174b">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.6" class="tag_14"><td><a name="10079bb7-ebd0-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>When a client application is restarted with the <span class="interface">/AppAutoCheckMode</span> key, the platform checks the user rights for running the client application. If the user attempts to start the application in the ordinary mode and does not have the right to run the thick client, they are not allowed to access the infobase. In other scenarios the client application that suits the selected start mode best is selected.</td><td>When a client application was restarted with the <span class="interface">/AppAutoCheckMode</span> key, the platform did not check the user rights for running the client application.</td><td>The client application selection algorithm is improved.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="852cdafa-fb7f-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If editing text in a form field extension for a text box is not allowed (the <span class="term">TextEdit</span> property is set to <span class="term">False</span>), the drop-down list of that box does not display the text "Enter the search string".</td><td>The drop-down list always displayed the text "Enter the search string".</td><td>The recommendation to perform an action that is not allowed is no longer displayed.</td></tr><tr title="Версия 8.3.6" class="tag_20"><td><a name="b3c5e7cc-fdd8-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During the merging of configurations you can modify the results of module merging. You can use external software (not incorporated in Designer) for comparing and merging module texts.<p>You can specify the external software in the Designer options dialog box.</p><p>Ready-to-use settings are available for the following external software:</p><ul><li>For Windows: Araxis Merge, KDiff3, TortoiseMerge, Perforce P4Merge, and DiffMerge</li><li>For Linux: KDiff3 and Perforce P4Merge</li></ul><p>You can specify settings for external software that is not on the list.</p></td><td>The results of module merging could not be modified while merging configurations.<p>Only built-in Designer features were available for comparing and merging module texts.</p></td><td>Developers can use any tool that they find convenient for comparing and merging module texts. They can make changes during the merging of configurations (with the help of external software).</td></tr><tr title="Версия 8.3.6" class="tag_20"><td><a name="1c9c130c-fde2-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Improved setup for the comparison and merging of managed forms. You can specify the comparison and merging rules for a form and for its module directly in the comparison and merging dialog box.</td><td>The comparison and merging rules for managed forms were specified in another dialog box. Also, the rules for the form itself and for its module were separated.</td><td>Simplified setup for the comparison and merging of managed forms and their modules.</td></tr><tr title="Версия 8.3.6" class="tag_20"><td><a name="e800d14b-0039-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The following features are implemented in the managed form editor:<ul><li>If the <span class="interface">Title</span> property of a managed form is not empty, its value is displayed in the window title in the preview area.</li><li>Clicking a title if the preview area selects the entire form. Right-clicking the title opens the form context menu.</li></ul></td><td>The window title bar in the preview area of the form editor did not have any functionality.</td><td>Improved usability of the form preview area in the managed form editor.</td></tr><tr title="Версия 8.3.6" class="tag_37"><td><a name="d7c1db09-005d-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Automatic selection of text encoding in email messages containing national characters is implemented. The automatic selection is only performed when the text contains national characters but their encoding is not specified, which does not comply with the standard. This applies to the following email message parts:<ul><li>Message headers</li><li>Message body</li><li>Message header parameter values, such as attachment file name.</li></ul></td><td>Email message text was displayed in incorrect encoding when no encoding was specified.</td><td>Email messages that do not comply with the standard are processed correctly.</td></tr><tr title="Версия 8.3.6" class="tag_120"><td><a name="d1f5c18f-0060-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>The duration of the first access to the background job manager (the <span class="term">BackgroundJobs </span>global context property) in file infobases is reduced. Now the duration of the first access is approximately the same as the duration of subsequent accesses.</td><td>The long duration of the first access to the background job manager (the <span class="term">BackgroundJobs </span>global context property) in file infobases might cause the user interface to stop responding until loading the backgound job scheduler was complete.</td><td>Reduced duration of the first access to the background job manager (the <span class="term">BackgroundJobs </span>global context property) in file infobases.<p>Faster start of client applications in the file mode (when the background job manager is accessed during the startup).</p></td></tr><tr title="Версия 8.3.6" class="tag_120"><td><a name="990eea57-0061-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>In file infobases, if a client application that performs background jobs is closed, the background jobs are terminated after a 30-second timeout. When a job is terminated, a<span class="term">_$Job$_.Terminate</span> event is recorded to the event log.</td><td>In file infobases, if the platform could not complete background jobs correctly, it displayed a message prompting the user to choose between waiting and terminating the jobs.</td><td>Eliminated unexpected (and not user-friendly) system behavior.</td></tr><tr title="Версия 8.3.6" class="tag_53"><td><a name="721f0681-0105-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>When properties or methods of <span class="term">MetadataObject</span> objects related to external reports or data processors that are no longer available are accessed, the platform generates an exception.</td><td>When properties or methods of <span class="term">MetadataObject</span> objects related to external reports or data processors that were no longer available were accessed, the platform was shut down unexpectedly.</td><td>Improved system stability.</td></tr><tr title="Версия 8.3.6" class="tag_20 tag_37"><td><a name="10cce1ea-0106-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The following information is added to the Syntax Assistant:<ul><li>SSL is supported for POP3 and SMTP.</li><li>Secure connection does not support checking server and client certificates.</li><li>Descriptions of the <span class="term">InternetMail </span>object methods that require IMAP connection now reflect that fact.</li><li>The list of fields filled in the<span class="term"> GetHeaders()</span> method of the <span class="term">InternetMail </span>object is provided.</li></ul></td><td>The Syntax Assistant did not contain this information.</td><td>Improved Syntax Assistant quality.</td></tr><tr title="Версия 8.3.6" class="compat tag_26 tag_1"><td><a name="cbbd4b34-0122-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When a spreadsheet document is exported to Microsoft Excel 2007-2010 format, its comments are converted to Excel table comments.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>When a spreadsheet document was exported to Microsoft Excel 2007-2010 format, its comments were converted to Excel pictures.</td><td>Better conversion of spreadsheet document items to Microsoft Excel format.</td></tr><tr title="Версия 8.3.6" class="tag_120"><td><a name="e55bc806-02b1-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>When a client application is started with a file infobase, there is a 1-minute delay before starting the execution of scheduled jobs.</td><td>When a client application was started with a file infobase, there was no delay before starting the execution of scheduled jobs.</td><td>Faster startup of client applications in file mode.</td></tr><tr title="Версия 8.3.6" class="tag_143"><td><a name="0f566e11-05ba-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 143); return false;">Defined types</a>.<br></td><td>During the update of a supported configuration you have the option to merge the following properties with priorities: the <span class="term">Type</span> property of the <span class="term">DefinedType</span> configuration property and the <span class="term">Type</span> property of the <span class="term">ChartOfCharacteristicTypes </span>object.</td><td>This feature was not provided.</td><td>Improved algorithm for comparing and merging defined types, which simplifies usage of those types in library development tasks.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="fd46d7db-069f-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Presentations of items found during the input by string with full-text search enabled are identical to presentations of items found with full-text search disabled.<p>The order of items in drop-down lists generated by the input by string feature with full-text search enabled matches the order of items returned by the full-text search algorithm.</p><p>The algorithm that generates presentations for <span class="term">Task </span>objects in drop-down lists generated by the input by string feature is modified.</p></td><td>Presentations of items found during the input by string with full-text search enabled were different from presentations of items found with full-text search disabled.<p>The order of items in drop-down lists generated by the input by string feature with full-text search enabled was not defined.</p><p>The algorithm that generated presentations for <span class="term">Task </span>objects in drop-down lists generated by the input by string feature was different.</p></td><td>Improved usability of the input by string feature. Unified generation of presentations for search results.</td></tr><tr title="Версия 8.3.6" class="tag_67"><td><a name="5c9264cb-2479-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>The configuration repository window now displays names of computers where objects are locked.</td><td>The configuration repository window displayed the name of the computer that the current user used for their first connection to the repository.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.6" class="tag_37"><td><a name="da4795c6-247a-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For the <span class="term">InternetMailMessage</span> object, the <span class="term">PostingDateOffset</span> property is implemented.</td><td>This feature was not provided.</td><td>You can define the true date of sending an email message.</td></tr><tr title="Версия 8.3.6" class="compat tag_43 tag_1"><td><a name="bc2e2970-26e2-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>When a form is opened, the <span class="term">Period</span> property of managed form table extension for dynamic lists and the <span class="term">Representation</span> property of a form table linked to a dynamic list are loaded simultaneously with dynamic list user settings.<p>It is recommended that you get the <span class="term">Period</span> property in the <span class="term">OnLoadUserSettingsAtServer</span> managed form event handler.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The <span class="term">Period</span> property of managed form table extension was obtained from the user settings before the execution of the <span class="term">OnCreateAtServe</span><span class="term">r</span> managed form event handler.<p>The <span class="term">Representation</span> property of a form table linked to a dynamic list was obtained from the client settings during the form opening.</p></td><td>
<p>The <span class="term">Period</span> and <span class="term">Representation</span> properties are stored in a similar way to other dynamic list settings, which simplifies operations with these properties using 1C:Enterprise script.</p></td></tr><tr title="Версия 8.3.6" class="tag_26"><td><a name="cdc74a14-2869-11e4-903a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When nonempty spreadsheet document cells with <span class="interface">Placement</span> properties are set to <span class="interface">Auto</span> are displayed, the cells are not merged up to the next filled cell or up to the horizontal boundary of the spreadsheet document.</td><td>When nonempty spreadsheet document cells with <span class="interface">Placement</span> properties set to <span class="interface">Auto</span> were displayed, the cells were merged up to the next filled cell or up to the horizontal boundary of the spreadsheet document.</td><td>The spreadsheet document view in the web client is now closer to the spreadsheet document view in the thin client.</td></tr><tr title="Версия 8.3.6" class="tag_19"><td><a name="cf66d505-286a-11e4-903a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>In the client/server mode with Oracle Database DBMS, executing a query that contains a subquery in the <span class="term">SELECT</span> section and also an aggregate function adds a <span class="term">GROUP BY</span> section with a constant, provided that such section is not yet present in the query.</td><td>In the client/server mode with Oracle Database DBMS, executing a query that contained a subquery in the <span class="term">SELECT </span>section and also an aggregate function resulted in the ORA-937 run-time error.</td><td>Improved stability of Oracle Database operations.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="98293183-2464-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The prevention of unexpected working process or client application shutdown due to managed form operation issues (loss of synchronization between the client and server parts of form data) is implemented. When an issue is detected, only the affected session is closed, and the working process that processes the session is not shut down. By default, the issue details are recorded to the technological log.</td><td>A loss of synchronization between the client and server parts of form data could result in a shutdown of the client application or a working process that processed the affected session.</td><td>
<p>Improved 1C:Enterprise server stability during managed form operations.</p></td></tr><tr title="Версия 8.3.6" class="tag_19"><td><a name="be27fa97-2e97-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The chance of deadlocks in queries that include comparisons with <span class="term">UNDEFINED</span> is reduced.</td><td>The chance of deadlocks in queries that included comparisons with <span class="term">UNDEFINED</span> was higher.</td><td>Increased system stability. Reduced chance of deadlocks that do not have obvious reasons.</td></tr><tr title="Версия 8.3.6" class="tag_14 tag_115 tag_64"><td><a name="abb42f4c-3338-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>For client applications that run on Windows operating systems, Windows scaling is supported. If a custom DPI value is set, interface items are scaled correctly, except pictures that might look a bit blurry.</td><td>Client applications that run on Windows operating systems had scaling issues.</td><td>Eliminated unexpected system behavior in scenarios where a user sets a custom DPI value for their display.</td></tr><tr title="Версия 8.3.6" class="tag_67"><td><a name="0167940a-38f1-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>When a user cancels binding to a configuration repository or when an infobase bound to a repository changes location, the dialog box stating that unbinding from the repository is required is no longer displayed.<p>To unbind a configuration from a repository, you can use the corresponding Designer command.</p></td><td>When a user canceled binding to a configuration repository or when an infobase bound to a repository changed location, the dialog box stating that unbinding from the repository was required was always displayed.</td><td>Improved usability of configuration repositories in some scenarios.</td></tr><tr title="Версия 8.3.6" class="tag_86"><td><a name="75370c72-38fe-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>The visibility settings for commands in subordinate subsystems are no longer lost when command interface settings of a subsystem that contains subordinate subsystems are copied using the <span class="term">Load()</span> and <span class="term">Save()</span> methods of the <span class="term">StandardSettingsStorageManager</span> object.</td><td>When command interface settings of a subsystem that contained subordinate subsystems were copied using the <span class="term">Load()</span> and <span class="term">Save()</span> methods of the <span class="term">StandardSettingsStorageManager</span> object, the visibility settings of commands in subordinate subsystems were lost.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.6" class="tag_28 tag_26"><td><a name="17a77bfc-3cde-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the web client, the option to select pictures in spreadsheet documents is implemented, and when they are selected, the respective event is called.<p>Improved representation of pictures in spreadsheet documents when viewed in the web client:</p><ul><li>Cells overlapped by a picture are not merged.</li><li>Text and pictures in spreadsheet document cells can overlap each other.</li><li>Eliminated issues that appeared when picture borders were close to cell borders.</li></ul></td><td>
<p>Selecting pictures in spreadsheet documents was not supported. Spreadsheet documents had some picture-related issues.</p></td><td>Improved quality of displaying spreadsheet documents with pictures in the web client.</td></tr><tr title="Версия 8.3.6" class="tag_20 tag_144"><td><a name="f8497817-48a9-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 144); return false;">Mobile application</a>.<br></td><td>The picture editor dialog box in Designer supports editing template pictures and the new picture variants format that includes a manifest.<p>Template pictures are used in applied solution development for the mobile platform.</p></td><td>Editing template pictures and the new picture variants format that includes a manifest were not supported.</td><td>Template picture support is implemented.</td></tr><tr title="Версия 8.3.6" class="tag_19"><td><a name="84ff1083-4a31-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The DBMS request that the platform generates based on the <span class="term">VALUETYPE</span> function of the query language is simplified.</td><td>The DBMS request based on the <span class="term">VALUETYPE</span> function was more complicated.</td><td>Eliminated issueds that occured when DBMS could not process a complex request.</td></tr><tr title="Версия 8.3.6" class="tag_20"><td><a name="53da7e38-544e-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During configuration merging and during configuration repository operations, the platform does not perform refactoring operations that are normally performed when configuration objects are renamed or deleted.</td><td>During configuration merging and during configuration repository operations, the platform performed refactoring operations that were normally performed when configuration objects were renamed or deleted.</td><td>Eliminated unexpected system behavior.<p>Operations whose results were ignored are not performed.</p></td></tr><tr title="Версия 8.3.6" class="compat tag_69 tag_1"><td><a name="ca26fada-59d2-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>If an object is passed to a method written in 1C:Enterprise script and its set of properties is changed during the method execution but the property names are not changed, the object property calls are executed correctly. In particular, when a method being executed adds a property, calls of other properties are executed correctly. If any property names are modified, object property calls might not be executed correctly.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>If an object was passed to a method written in 1C:Enterprise script, the method called object properties by their numbers, which were defined at the moment the method was called. If a property number was changed during the method execution (for example, a new property was added), this was not taken into account and the property call was performed using the old number.</td><td>Improved system reliability and reduced chance of errors when a set of properties is changed during method execution.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="dd038c6c-64ec-11e4-9135-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the thin client, formatted strings that are defined during the generation of a drop-down list are displayed accordingly to their formatting if the text box is linked to an attribute of complex type and this attribute has the <span class="term">Undefined</span> value.</td><td>In the thick client, formatted strings that were defined during the generation of drop-down lists were displayed without formatting if the text box was linked to an attribute of complex type and this attribute had the <span class="term">Undefined</span> value.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.6" class="tag_28 tag_115"><td><a name="246f69ce-64ed-11e4-9135-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the web client, drop-down lists have the same color scheme as in other client applications.</td><td>In the web client, drop-down lists had a color scheme different from the color scheme used in other client applications.</td><td>In the web client, drop-down list appearance is uniform with other client applications.</td></tr><tr title="Версия 8.3.6" class="tag_28"><td><a name="cef82959-6fc5-11e4-9135-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client, the appearance of the following interface items is almost identical to their appearance in the thin client:<ul><li>form button</li><li>command bar button</li><li>command bar</li><li>separator
</li></ul></td><td>In the web client, the appearance of the following interface items was different from their appearance in the thin client:<ul><li>form button</li><li>command bar button</li><li>command bar</li><li>separator</li></ul></td><td>Uniform client application appearance.</td></tr><tr title="Версия 8.3.6" class="tag_86"><td><a name="07d57735-a183-11e4-b1db-0050569f678a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>When a user command group is deleted, standard commands that belong to the group are automatically moved to the default standard group specified for those commands.<p>This change is not implemented in 8.3.6 compatibility mode.</p></td><td>When a user command group was deleted, standard commands that belonged to the group were no longer available in the command interface.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.6" class="tag_39"><td><a name="00c3c556-a52b-11e4-b1db-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>The <span class="term">UnloadEventLog()</span> method truncates the event time passed to it to an integer number of seconds.<p>When a filter by time is applied to the event log (<span class="term">UnloadEventLog()</span>, <span class="term">CopyEventLog()</span>, or <span class="term">ClearEventLog()</span> method), an event is included in the result even if the millisecond part of the actual event time exceeds the millisecond part of the time specified in the filter.</p></td><td>The <span class="term">UnloadEventLog() </span>method provided the event time with millisecond accuracy. When a filter by time was applied to the event log (<span class="term">UnloadEventLog()</span>, <span class="term">CopyEventLog()</span>, or <span class="term">ClearEventLog()</span> methods), an event was included in the result only if the exact condition was met (including the millisecond part).</td><td>Eliminated unexpected system behavior.<p>The behavior of the <span class="interface">.lgd </span>log is uniform with that of the<span class="interface"> .lgf </span>log (regarding the event time presentation and filter functionality).</p></td></tr><tr title="Версия 8.3.6" class="compat tag_77 tag_26 tag_1"><td><a name="b7d6a3bc-5b8d-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 77); return false;">Print tools</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The algorithm that calculates spreadsheet document column width for printing is modified. The printed document column width more closely matches the on-screen column width. The chance is noticeable in spreadsheet documents with background pictures.<p>This change is not implemented in 8.3.5 compatibility mode.</p><p>
</p></td><td>For spreadsheet documents, the printed document column width did not exactly match the on-screen column width.<p>
</p></td><td>Improved print layout of spreadsheet documents.</td></tr><tr title="Версия 8.3.6" class="tag_94"><td><a name="bbd47bd3-f7e9-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 94); return false;">Regional settings</a>.<br></td><td>For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, and 69-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.</td><td>The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, and 69-FZ.</td><td>The time offset changes introduced by the new law are implemented.</td></tr></table><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="eb969adf-881f-11e3-b57b-e61f135f174b">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.6" class="tag_37"><td><a name="f12b1e6d-e1b7-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Future 1C:Enterprise versions will not support NSS certificates and related objects, regardless of the compatibility mode.<p>The <span class="term">NSSSecureConnection </span>object will be unavailable for use in 1C:Enterprise script and in thin client HTTPS connection settings.</p></td><td>1C:Enterprise system supports NSS certificates.</td><td>Future platform versions will not support NSS certificates.</td></tr><tr title="Версия 8.3.6" class="compat tag_51 tag_1"><td><a name="d9212876-f861-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>For the <span class="term">TestedFormGroup</span> object, the <span class="term">CurrentVisible</span><span class="term">()</span> function returns <span class="term">False </span>if the object is linked to form group, which is inactive page located in a page group where tabs are not displayed.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>For the <span class="term">TestedFormGroup</span> object, the <span class="term">CurrentVisible</span><span class="term">()</span> function returned <span class="term">True</span> if the object was linked to a form group, which was an inactive page located in a page group where tabs were not displayed.</td><td>The automated testing feature emulates the system functioning and provides form item status data more accurately.</td></tr><tr title="Версия 8.3.6" class="compat tag_115 tag_1"><td><a name="6dd19e46-fae3-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For managed form attributes of spreadsheet document, graphical schema, and text document types, calling the <span class="term">Show()</span> method raises an exception.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The system behavior depended on the attribute location on a form and the client application type:<ul><li>The attribute is linked to a managed form item:</li><ul><li>Thin client:</li><ul><li>Spreadsheet document: the current form is activated.</li><li>Graphical scheme: a new form with a copy of the scheme is opened.</li><li>Text document: a new form with a copy of the document is opened.</li></ul><li>Web client:</li><ul><li>For attributes of any type (spreadsheet document, graphical schema, or text document) the current form is activated.</li></ul><li>The attribute is not linked to a managed form item:</li><li>Thin client:</li><ul><li>For attributes of any type (spreadsheet document, graphical schema, or text document), a form with a copy of the document is opened.</li></ul><li>Web client:</li><ul><li>Spreadsheet document: a new form with a copy of the document is opened.</li><li>Graphical scheme: the current form is activated.</li><li>Text document: the current form is activated.</li></ul></ul></ul></td><td>Unified behavior of various objects in different client applications.</td></tr><tr title="Версия 8.3.6" class="compat tag_115 tag_1"><td><a name="b6468a04-fb7e-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the thin and thick clients, buttons (or hyperlinks) located in managed forms become unavailable when commands (or hyperlinks) linked to these buttons become unavailable.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>In the thin and thick clients, buttons (or hyperlinks) located in managed forms stayed available even when commands (or hyperlinks) linked to these buttons were unavailable.</td><td>The system behaves as expected.<p>Unified system behavior in different client applications.</p></td></tr><tr title="Версия 8.3.6" class="compat tag_115 tag_1"><td><a name="7aa5a831-fc49-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When an item is created in the drop-down list of a text box, you can verify whether the created item matches the choice parameters used for opening the new item form. If the item does not match the choice parameters, a diagnostic message is displayed and the created item is not placed in the text box.<p>The verification is implemented for managed form extensions for objects, catalogs, documents, charts of characteristic types, business processes, and tasks.</p><p>The following features are implemented:</p><ul><li><span class="term">ChoiceParameters</span> standard property of the managed form extension</li><li><span class="term">ChoiceParameters</span> property of the managed form extension</li><li><span class="term">ChoiceAvailable</span> property of the managed form extension</li><li><span class="term">ValueChoice</span> event of the managed form extension</li></ul><p>The <span class="term">ChoiceParameters</span> and <span class="term">ChoiceAvailable</span> properties of the managed form extension are not available in version 8.3.5 compatibility mode.</p></td><td>A new item that did not match the choice parameters specified for a text box could be created and selected in the text box.</td><td>Reduced chance of creating items (from a text box choice list) that do not match the choice parameters specified for the text box.</td></tr><tr title="Версия 8.3.6" class="compat tag_52 tag_1"><td><a name="85ed1274-fdd4-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>The <span class="term">Period </span>field whose value is specified in a periodic information register record set filter is included in the set of managed lock fields for read and write operations on record set data.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The <span class="term">Period </span>field was not included in the set of managed lock fields for read and write operations on periodic information register record set data.</td><td>Improved user experience for periodic information register operations. Reduced chance of deadlocks.</td></tr><tr title="Версия 8.3.6" class="compat tag_58 tag_16 tag_1"><td><a name="b4c28aeb-003e-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>When an information register data set is recorded, the default values of independent and shared separators that include the information register are replaced by the separator values set in the current session.<p>If a separator value is not identical to the default value of that separator type or is not equal to the separator value set in the current session, an error is generated.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>When an information register data set was recorded, the default values of independent and shared separators that included the information register were always replaced by the separator values set in the current session</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.6" class="compat tag_37 tag_1"><td><a name="39ffb240-0044-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>When the <span class="term">InternetMail</span> object is used for interaction with a Microsoft Exchange server, if the filter criterion string value (the Filter parameter of the <span class="term">GetHeaders()</span> and <span class="term">GetUIDL()</span> methods of the InternetMail object) only includes US-ASCII characters, the platform notifies the Exchange server about this in addition to passing the string to the server. Otherwise the platform passes a UTF-8-encoded string.<p>If the filter criterion string value passed to the Exchange server contains not only US-ASCII characters (for example, it includes Cyrillic characters), an error is generated.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The <span class="term">GetHeaders()</span> and <span class="term">GetUIDL()</span> methods of the InternetMail object always returned an empty array when a string value of the <span class="term">Filter</span> parameter was used in interactions with Microsoft Exchange.</td><td>Improved compatibility with Microsoft Exchange during operations with the <span class="term">InternetMail</span> object. You can search in the filter criterion string if all its characters belong to the US-ASCII encoding.</td></tr><tr title="Версия 8.3.6" class="compat tag_37 tag_1"><td><a name="14d86c09-0053-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The <span class="interface">libetpan</span> library is used to work with IMAP, SMTP, and POP3.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The UW IMAP toolkit library was used to work with IMAP, SMTP, and POP3.</td><td>Improved performance and stability of email management features.</td></tr><tr title="Версия 8.3.6" class="compat tag_37 tag_1"><td><a name="41deef31-005b-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>During the creation of an<span class="term"> InternetProxy </span>object on Linux operating systems, if the <span class="term">DefaultProxy</span> constructor parameter value is <span class="term">True </span>and the platform cannot find the file <span class="interface">inetcfg.xml</span>, the constructor uses the values of the following operating system environment variables: <span class="term">http_proxy</span>, <span class="term">https_proxy</span>, <span class="term">ftp_proxy</span>, <span class="term">ftps_proxy</span>, and <span class="term">all_proxy</span>.<p>The methods of the <span class="term">HTTPConnection</span> and <span class="term">FTPConnection</span> objects do not attempt to determine the proxy server settings. Instead, they use the settings stored in the<span class="term"> Proxy </span>property of the respective object.</p><p>For the <span class="term">Set() </span>method of the <span class="term">InternetProxy</span> object, the <span class="term">User</span> and <span class="term">Password</span> parameters are implemented. For the <span class="term">InternetProxy</span> object, the <span class="term">User</span> and <span class="term">Password</span> methods are implemented. The <span class="term">U</span><span class="term">ser</span> and <span class="term">Password</span> properties of the <span class="interface">InternetProxy</span> object are declared obsolete, they are suported for compatibility purposes.</p><p>This change is not implemented in 8.3.5 compatibility mode.
</p></td><td>Environment variables were never used for creation of <span class="term">InternetProxy </span>objects on Linux operating systems. If the proxy server parameters were not specified during the creation of <span class="term">HTTPConnection</span> and <span class="term">FTPConnection</span> objects, methods of these objects attempted to retrieve the proxy server settings from environment varaibles.</td><td>Eliminated the difference in platform behavior on Windows and Linux operating systems. Eliminated unintuitive platform behavior where methods of <span class="term">HTTPConnection</span> and <span class="term">FTPConnection</span> objects attempted to determine the proxy server settings.</td></tr><tr title="Версия 8.3.6" class="compat tag_14 tag_1"><td><a name="dbe1c558-00f6-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Idle handlers are not called while a client application is locked using the <span class="term">LockApplication() </span>global context method or the <span class="interface">Temporary lock</span> command.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>Locking a client application using the <span class="term">LockApplication() </span>global context method or the <span class="interface">Temporary lock</span> command did not affect the execution of idle handlers.</td><td>Increased system security.</td></tr><tr title="Версия 8.3.6" class="compat tag_145 tag_1"><td><a name="0acc1d3a-00f8-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 145); return false;">xBase support</a>.<br></td><td>If an error occurs during a .dbf file operation performed using the <span class="term">XBase</span> object, an exception is generated.
This change is not implemented in 8.3.5 compatibility mode.</td><td>If an error occurred during a .dbf file operation performed using the <span class="term">XBase</span> object, dialog boxes were generated.</td><td>Eliminated scenarios that looked as if the platform stopped responding (for example, errors generated by .dbf file operations at 1C:Enterprise server side).</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="cf531e90-00f9-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For the <span class="term">TypeLink</span> object constructor, you can specify the first parameter (<span class="term">DataPath</span>) as an empty string.</td><td>The <span class="term">TypeLink</span> object constructor did not accept an empty string as the <span class="term">DataPath</span> parameter value.</td><td>You can clear the <span class="term">TypeLink</span> property of a managed form field by replacing its value with a new object of that type that does not have the data path specified.</td></tr><tr title="Версия 8.3.6" class="compat tag_62 tag_1"><td><a name="3301771e-010e-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>For the <span class="term">ExternalDataSourceTableObject</span>, the <span class="term">GetChangeable</span><span class="term">Fields()</span> and <span class="term">Set</span><span class="term">Changeable</span><span class="term">Fields()</span> methods are implemented. These methods are intended both for restricting the list of writable external data table fields and for expanding that list with fields have the read-only flag set in the configuration (the <span class="term">ReadOnly</span> property set to <span class="term">True</span>). The <span class="term">GetFieldsToWrite()</span> and <span class="term">SetFieldsToWrite()</span> methods are declared obsolete, they are supported for compatibility purposes.</td><td>The <span class="term">GetFieldsToWrite()</span> and <span class="term">SetFieldsToWrite()</span> methods only provided the option to reduce the number of fields that were recorded to external data source tables. The option to record data to fields that are marked as read-only in Designer was not provided.</td><td>The platform supports custom algorithms for external data source management. For example, data that is normally not recorded to external data source table fields can now be recorded using a custom algorithm.</td></tr><tr title="Версия 8.3.6" class="tag_10"><td><a name="253e9b7a-02b3-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>When a list of infobases is updated or when a client application distribution kit is downloaded via the Internet, the root certificates of certification authorities are obtained from the Windows certificate store.</td><td>When a list of infobases was updated or when a client application distribution kit was downloaded via the Internet, the root certificates of certification authorities were only obtained from the <span class="interface">cacert.pem</span> file.</td><td>Improved usability of self-signed certificates in the enterprise environment.</td></tr><tr title="Версия 8.3.6" class="tag_6"><td><a name="f5cc30fd-0365-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>You can specify the user on whose behalf the cluster manager (<span class="interface">rmngr</span>) is started, and it can be different from the user on whose behalf the cluster agent (<span class="interface">ragent</span>) is started.<p>You can specify users on whose behalf the cluster manager (<span class="interface">rmngr</span>) and working processes (<span class="interface">rphost</span>) is started for each cluster on a given computer.</p><p>You can specify a custom cluster register directory for each cluster manager (<span class="interface">rmngr</span>) on a given computer.</p><p>The following parameters and parameter groups are implemented for the <span class="interface">swpuser.ini</span> file:</p><ul><li>the <span class="term">rmngr_user</span> and <span class="term">rmngr_pass</span> parameters</li><li>the <span class="term">registry </span>parameter</li><li>the <span class="term">&lt;PortName:&gt;</span> parameter group, which can contain all of the swpuser.ini file parameters.</li></ul></td><td>Only the user on whose behalf the working process (<span class="interface">rphost</span>) was started could be changed.</td><td>You can increase server cluster security in scenarios like this: service users use their own applied solutions, external data processors, and add-ins whose access to the server cluster computer infrastructure should be restricted.</td></tr><tr title="Версия 8.3.6" class="compat tag_97 tag_1"><td><a name="4e407d79-037c-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 97); return false;">Data access restrictions</a>.<br></td><td>Access restriction template parameters that are specified in comments are not replaced by actual values when the template is applied.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>Access restriction template parameters that were specified in comments were not replaced by actual values when the template was applied.</td><td>Increased stability of the access restriction system in some scenarios.</td></tr><tr title="Версия 8.3.6" class="compat tag_25 tag_1"><td><a name="80f8c128-037e-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The option to use nested reports during the export of data composition result to a value collection is implemented.<p>Columns with duplicate names are never created during the export.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The option to use nested reports during the export of data composition result to a value collection was not available.<p>The check for duplicate column names was never performed during the export, so columns with duplicate names might be created.</p></td><td>Extended data composition system functionality.</td></tr><tr title="Версия 8.3.6" class="compat tag_25 tag_1"><td><a name="bb4abc69-05bb-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When additional data is displayed for hierarchical records, hierarchical record data is used.<p>This change is not implemented in 8.2.16 compatibility mode.</p><p>
</p></td><td>When additional data was displayed for hierarchical records, the detailed record data was used.</td><td>Reports display expected data: if a report contains a table with hierarchical groupings in its rows, the data obtained from the hierarchical records is displayed in the columns of additional data for hierarchical grouping rows, not from the detailed records, as it was implemented earlier.</td></tr><tr title="Версия 8.3.6" class="compat tag_25 tag_1"><td><a name="858ff1b4-05bc-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The value assigned to the <span class="interface">Text </span>conditional appearance parameter, which is enabled, is applied to fields of predefined grouping templates and fields of data composition system reports.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The value assigned to the <span class="interface">Text</span> conditional appearance parameter, which was enabled, was not applied to fields of predefined grouping templates or fields of data composition system reports.</td><td>Predefined grouping templates can be used together with the <span class="interface">Text</span> parameter of data composition conditional appearance.</td></tr><tr title="Версия 8.3.6" class="compat tag_25 tag_1"><td><a name="6a30e419-05be-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The appearance of cells that store parent grouping fields is based on the field expressions obtained for the current grouping.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The appearance of cells that stored parent grouping fields was based on the field expressions obtained for the parent grouping.</td><td>The cell appearance is formed as expected.</td></tr><tr title="Версия 8.3.6" class="compat tag_43 tag_1"><td><a name="9371f44f-05d6-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>If the platform cannot generate the list of available dynamic list settings, an exception is generated and the form is not generated.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>If the platform could not generate the list of available dynamic list settings, no exceptions were generated and the managed form continued functioning as if the dynamic list data source did not have any fields available. All of the form items related to dynamic list data disappeared from the managed form.</td><td>Improved error diagnostics during dynamic list operations.</td></tr><tr title="Версия 8.3.6" class="compat tag_25 tag_1"><td><a name="ab1a5603-05d9-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The data composition template composer uses detailed data set fields for hierarchical grouping records. You can use the <span class="term">EvalExpression</span><span class="term">()</span> function for getting hierarchical record values within aggregate functions.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The data composition template composer used hierarchical data set fields for hierarchical records (provided that the fields were available in the set).</td><td>You can use all detailed record fields in aggregate functions calculated for hierarchical records.</td></tr><tr title="Версия 8.3.6" class="compat tag_69 tag_1"><td><a name="f9b133f7-2478-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The <span class="term">FindMarkedForDeletion()</span> method only processes data available to the current user.<p>In the Syntax Assistant, the descriptions of the <span class="term">FindByRef()</span> and <span class="term">DeleteObjects()</span> methods are modified to describe their actual behavior.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The <span class="term">FindMarkedForDeletion()</span> method did not check data access rights. If access was denied, a run-time error was generated.<p>In the Syntax Assistant, the descriptions of the <span class="term">FindByRef()</span> and <span class="term">DeleteObjects()</span> methods did not describe their actual behavior.</p></td><td>The generation of run-time errors during the search for objects marked for deletion is eliminated in scenarios where the user does not have access rights for all objects involved in the search.<p>The description of the system behavior is now correct.</p></td></tr><tr title="Версия 8.3.6" class="compat tag_115 tag_1"><td><a name="7cc64e04-26b7-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the thin client, in the <span class="term">OnOpen</span> managed form event handler, if the <span class="term">Cance</span><span class="term">l</span> parameter is set to <span class="term">TRUE</span>, the <span class="term">OnClose</span> event handler and the notification set in the <span class="term">OnCloseNotifyDescription </span>managed form property are not called.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>In the <span class="term">OnOpen</span> managed form event handler, if the <span class="term">Cancel</span> parameter was set to <span class="term">TRUE</span>, the <span class="term">OnClose</span> event handler and the notification specified in the <span class="term">OnCloseNotifyDescription</span> managed form property had the following behavior:<ul><li>they were called in the thin client;</li><li>they were not called in the web client.</li></ul></td><td>Uniform system behavior across multiple client applications.</td></tr><tr title="Версия 8.3.6" class="tag_51"><td><a name="909500e1-27a2-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>New automated testing features:<ul><li>Operations with performance indicators. For the <span class="term">TestedApplication</span> object, the <span class="term">GetAccumulatedPerformanceIndicators()</span> and <span class="term">ClearAccumulatedPerformanceIndicators()</span> methods are implemented.</li><li>Support of the following managed form items: progress bar fields and track bar fields. The <span class="interface">Tumbler </span>radio button field type is now supported.</li><li>Extended managed form table operations:</li><ul><li>Deletion mark management. For the <span class="term">TestedFormTable</span> object, the <span class="term">SwitchRowDeleteMark()</span> method is implemented.</li><li>Setting row selection and getting selected rows. For the <span class="term">TestedFormTable</span> object, the <span class="term">SelectAllRows()</span> and<span class="term"> GetSelectedRows() </span>methods are implemented. For the <span class="term">GotoRow()</span>, <span class="term">GotoFirstRow()</span>, <span class="term">GotoLastRow()</span>, <span class="term">GotoPreviousRow()</span>, and<span class="term"> GotoNextRow() </span>methods, the <span class="term">Select</span> parameter is implemented.</li><li>Ordering table data. For the <span class="term">TestedFormTable</span> object, the <span class="term">SetOrder()</span> method is implemented.</li></ul><li>Expanding and collapsing managed form groups. For the <span class="term">TestedFormGroup</span> object, the <span class="term">Collapse()</span>, <span class="term">Expand()</span>, and <span class="term">GetCurrentPage()</span> methods are implemented.</li></ul><p>The <span class="term">GetCurrentAreaText()</span> method of the <span class="term">TestedFormField</span> is declared obsolete. It is recommended that you use the <span class="term">GetAreaText() </span>method of the <span class="term">TestedFormField</span> object.</p><p>In the event of unexpected shutdown of a client application the user actions are automatically recorded to the user action log (provided that the user action log recording is enabled). A dump is also recorded to the dump directory.</p><p>The data processor that converts the log of user actions to a 1C:Enterprise script scenario is updated </p><p> URL2.
</p></td><td>Operations with performance indicators were not supported, as well as managed form table and managed form group operations.<p>Progress bar fields, track bar fields, and the <span class="interface">Tumbler</span> radio button field type were not supported.</p><p>In the event of an unexpected shutdown of a client application, the user actions were not recorded to the user action log and the accumulated action log was lost.</p></td><td>New automated testing features. Reduced number of manual operations during the testing.</td></tr><tr title="Версия 8.3.6" class="compat tag_64 tag_1"><td><a name="4cfce75b-0063-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>In sessions that do not have user interface (background and scheduled jobs, web services, and so on), the <span class="term">BriefErrorDescription()</span> and <span class="term">DetailErrorDescription()</span> method generate results that exactly match the results provided by these methods in managed application client sessions.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>In sessions that did not have user interface (background and scheduled jobs, web services, and so on), the <span class="term">BriefErrorDescription()</span> and <span class="term">DetailErrorDescription()</span> methods generated results that exactly matched the results provided by these methods in ordinary application client sessions.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.6" class="tag_36"><td><a name="33f5f702-2dae-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>When a configuration is saved, a check for style elements whose names match the values of the corresponding system value sets is performed:<ul><li>For style elements of <span class="interface">Color</span> type: the <span class="term">StyleColors</span> system value set</li><li>For style elements of <span class="interface">Font</span> type: the <span class="term">StyleFonts</span> system value set</li><li>For style elements of <span class="interface">Border</span> type: the <span class="term">StyleBorders</span> system value set</li></ul><p>If such elements are found, an error is displayed and the configuration is not saved.</p></td><td>When a configuration was saved, a check for style elements whose names matched the values of the corresponding system value sets was not performed.</td><td>Eliminated unexpected system behavior.<p>Eliminated situations where two values with the same name were present in a single system value set whose values were connected to style elements.</p></td></tr><tr title="Версия 8.3.6" class="compat tag_37 tag_1"><td><a name="f5c7da89-38fd-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>In the parsing of Internet mail messages, the message validity check is implemented. The check is available both for messages received from the server and during the generation of outgoing messages using the <span class="term">SetSourceData()</span> method of the <span class="term">InternetMailMessage </span>object. For the <span class="term">InternetMailMessage </span>object, the <span class="term">ParseStatus </span>property is implemented.<p>In the technological log, the <span class="term">&lt;MAILPARSEERR&gt;</span> event is implemented.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>Detection of invalid mail messages resulted in an unexpected shutdown.</td><td>Improved system reliability during email operations in scenarios where email messages being processed contain errors.</td></tr><tr title="Версия 8.3.6" class="compat tag_37 tag_1"><td><a name="a914092d-38fa-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For the <span class="term">SetBodyFromString()</span> method of the <span class="term">HTTPRequest</span> and <span class="term">HTTPServiceResponse</span> objects, the <span class="term">UseBOM</span> parameter is implemented. It manages the availability of BOM in the specified text.<p>In version 8.3.5 compatibility mode, the BOM mark is added by default.</p></td><td>This feature was not provided.</td><td>Simplified interaction with systems that do not expect BOM in HTTP queries.</td></tr><tr title="Версия 8.3.6" class="tag_146"><td><a name="ed8e2a76-4a31-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 146); return false;">Ordinary forms</a>.<br></td><td>The <span class="term">Name</span> property of ordinary form items is read-only.<p>This change is not implemented in 8.3.5 compatibility mode.</p></td><td>The DBMS request based on the <span class="term">VALUETYPE</span> function was more complicated.</td><td>Eliminated issues that occurred when a DBMS could not process a complex request.</td></tr><tr title="Версия 8.3.6" class="tag_147"><td><a name="90184c7b-4d54-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 147); return false;">OData operations</a>.<br></td><td>The list of functions supported by OData standard interface is revised. The description of <span class="term">mod</span> function is removed from the documentation.</td><td>The documentation stated that the <span class="term">mod</span> function was supported by standard Odata interface.</td><td>
<p>The documentation describes the actual platform behavior.</p></td></tr><tr title="Версия 8.3.6" class="tag_78 tag_14"><td><a name="8a76f541-e37b-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Both in thin and thick clients, when a file is obtained interactively using the <span class="term">GetFile()</span> method with the "open file" option, the search for associated application is performed (by the file extension). If an associated application is found, a system dialog box for selecting an application to open the file is displayed. If an associated application is not found, getting the file is canceled.<p>In the web client, the behavior is not changed, so it is now uniform with the behavior of thin and thick client applications.</p></td><td>In both thin and thick clients, when a file was obtained interactively using the <span class="term">GetFile() </span>method with the "open file" option, the search for associated application was performed (by the file extension). If an associated application was found, the file was opened using this application. If an associated application was not found, getting the file was canceled.<p>The web client displayed a system dialog box for selecting an application to open the file.</p></td><td>Eliminated the difference in the web client, thin client, and thick client behavior.</td></tr><tr title="Версия 8.3.6" class="tag_78 tag_28"><td><a name="89c46e36-006e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The <span class="term">File </span>object constructor with a file name parameter is available regardless of the <span class="interface">Sy</span><span class="interface">nchronous call usage mode for extensions and add-ins</span> configuration property value. Configuration verification and refactoring no longer treat the <span class="term">File </span>constructor with a file name parameter as a legacy synchronous call. Execution of this constructor no longer causes an exception in 1C:Enterprise mode.<p>In the web client execution of <span class="term">File </span>constructor with a file name parameter no longer requires installing the file system extension.</p><p>The descriptions of <span class="term">F</span><span class="term">ile </span>constructor without parameters and <span class="term">File.BeginInitialization()</span> methods are removed from the documentation. The <span class="term">File.BeginInitialization()</span> method is supported for compatibility purposes.</p></td><td>The <span class="term">File </span>object constructor with a file name parameter was available when the <span class="interface">Sy</span><span class="interface">nchronous call usage mode for extensions and add-ins</span> configuration property was set to <span class="interface">Use </span>or <span class="interface">Use with warnings</span>. Configuration verification and refactoring treated the <span class="term">File </span>constructor with a file name parameter as a legacy synchronous call. If the <span class="interface">Sy</span><span class="interface">nchronous call usage mode for extensions and add-ins</span> configuration property was set to <span class="interface">Do not use</span>, execution of this constructor caused an exception in 1C:Enterprise mode.<p>In the web client execution of <span class="term">File </span>constructor with a file name parameter required installing the file system extension.</p></td><td>Operations with the <span class="term">File </span>object that do not require access to the file system (such as getting a file extension) no longer require installing the file system extension.</td></tr><tr title="Версия 8.3.6" class="compat tag_37 tag_1"><td><a name="4a1a5d1b-0ac6-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>IDs of email messages received using IMAP do not depend on whether you specify the mailbox by name or use the default one.<p>Once you disable the compatibility mode, the option to map messages to each other using the <span class="term">InternetMailMessage</span><span class="term">.</span><span class="term">MessageID </span>property becomes available.</p><p>This change is not implemented in 8.3.5 compatibility mode.</p><p>
</p></td><td>IDs of email messages received using IMAP did not depend on whether you specified the mailbox by name or used the default one.</td><td>You can unambiguously identify each email message, regardless of the selected mailbox. This simplifies the algorithm for distinguishing between received and new messages.<p>
</p></td></tr><tr title="Версия 8.3.6" class="tag_28 tag_29"><td><a name="6e46b5ee-5b85-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The list of supported web browsers includes Google Chrome for x86-64 architecture. The platform uses 32-bit versions of add-ins and extensions with this browser.</td><td>The list of supported web browsers did not include Google Chrome for x86-64 architecture. </td><td>Extended list of supported web browsers.</td></tr><tr title="Версия 8.3.6" class="compat tag_25 tag_1"><td><a name="423182b8-61de-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When columns of a data composition system report template are output to a value tree or a value table, invalid characters are removed from column names.<p>This change is not implemented in 8.3.5 repository compatibility mode.</p><p>
</p></td><td>When columns of a data composition system report template were output to a value tree or a value table, the column names matched the field names.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.6" class="tag_11"><td><a name="9ae199ba-71ba-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>In the add-in development technology, Mozilla Firefox and Google Chrome support (for all Windows, Linux, and MacOS X architectures) is now uniform. The <span class="interface">xulrunner </span>utility is no longer required for building add-ins and is removed from the distribution kit.<p>It is recommended that you build new installer packages (<span class="interface">.msi</span> and <span class="interface">.s</span><span class="interface">h</span>) for Mozilla Firefox and create a new archive with version <span class="interface">40.</span><span class="interface">*</span> specified in the manifest. For support of earlier platform versions, also add legacy (<span class="interface">.xpi</span>) packages to the archive with version <span class="interface">31.0</span> specified in the manifest.</p><p>The add-in development technology documentation and examples are updated accordingly.</p></td><td>Add-ins created for Mozilla Firefox and Google Chrome were different. The <span class="interface">xulrunner </span>utility was used to build Mozilla Firefox add-ins.</td><td>Support of add-ins for browsers that no longer support legacy add-in creation functions is implemented.</td></tr><tr title="Версия 8.3.6" class="tag_95"><td><a name="44243b2b-7c8e-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>The configuration check that is always performed before database configuration update includes a check for uniqueness of predefined item names. No duplicate predefined item names are allowed for any configuration object. If duplicate predefined items are found, this is reported to the message window but does not prevent the configuration update.</td><td>The configuration check that is always performed before database configuration update did not include a check for uniqueness of predefined item names.</td><td>Improved reliability of configuration updates for configurations that include predefined data.</td></tr></table><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="eb969ae0-881f-11e3-b57b-e61f135f174b">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.6" class="tag_0"><td><a name="fcb2531b-fae7-11e3-98ab-e61f135f174b"></a>The name of the <span class="term">URLProcessing</span> event handler parameter is changed for form decoration, form field extension for a label, and managed form objects.</td><td><ul><li><span class="term">URL</span></li></ul></td><td><ul><li><span class="term">FormattedStringURL</span></li></ul></td></tr><tr title="Версия 8.3.6" class="tag_0"><td><a name="c088ceda-02b2-11e4-98ab-e61f135f174b"></a>Parameter of the<span class="term"> AutoCompleteText </span>and <span class="term">TextEditEnd </span>event handlers of the form text box extension.</td><td><ul><li><span class="term">Parameters</span>.</li></ul></td><td><ul><li><span class="term">DataGet</span><span class="term">Parameters</span>.</li></ul></td></tr><tr title="Версия 8.3.6" class="tag_0"><td><a name="620d3eb4-a78a-11e4-b1db-0050569f678a"></a>The method that obtains the most accurate location provider is renamed. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">GetMostAcurateProvider()</span>.</li></ul></td><td><ul><li><span class="term">GetMostAccurateProvider()</span>.</li></ul><p>
</p>
</td></tr><tr title="Версия 8.3.6" class="tag_0"><td><a name="3cf3fdea-2477-11e5-a3f7-0050569f678a"></a>English name of <span class="term">CryptoCertificate</span><span class="term">.</span><span class="term">BeginUnloading</span><span class="term">()</span> method.<p>The former name is supported for compatibility purposes.</p></td><td><ul><li><span class="term">BeginUnload()</span>.</li></ul></td><td><ul><li><span class="term">BeginUnloading()</span>.</li></ul></td></tr><tr title="Версия 8.3.6" class="tag_0"><td><a name="6ee9a4cb-2477-11e5-a3f7-0050569f678a"></a>English name of <span class="term">BeginCheckingExistence</span><span class="term">()</span> method.<p>
</p><p>The former name is supported for compatibility purposes</p></td><td><ul><li><span class="term">BeginCheckingExist()</span>.</li></ul></td><td><ul><li><span class="term">BeginCheckingExistence</span><span class="term">()</span>.</li></ul></td></tr></table><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="eb969ae1-881f-11e3-b57b-e61f135f174b">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.6" class="tag_14"><td><a name="e7c16091-ebd3-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Faster startup of mobile applications.</td><td>Insufficient startup speed of mobile applications.</td><td>Improved usability of mobile applications.</td></tr><tr title="Версия 8.3.6" class="tag_20 tag_64"><td><a name="fd1aac66-3cd9-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>The set of data stored in picture archives that include variants is modified. The manifest file <span class="interface">manifest.xml</span>, which is included in the archive, stores descriptions of picture variants. Custom names for pictures designed for specific display resolutions are allowed. Template pictures (pictures that have transparent background, which is displayed using the current text color) are supported. It is recommended that you store template pictures in PNG format.</td><td>Picture variants were described by their file names. A manifest file was not included.<p>Template pictures were not supported.</p></td><td>You can use more of mobile application system appearance design features.</td></tr><tr title="Версия 8.3.6" class="tag_21"><td><a name="53b7de77-4a21-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>In the mobile platform, you can use full-text search. The full-text search index is updated automatically upon data modification.<p>The search is not morphological. Additional dictionaries and text extraction are not supported. The index is updated when the mobile platform is not performing any server calls or background jobs.</p></td><td>The mobile platform did not support full-text search.</td><td>You can use full-text search in the mobile platform.</td></tr><tr title="Версия 8.3.6" class="tag_29"><td><a name="4fba38c0-4a2c-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The Google Play store now considers mobile applications optimized not only for phones but also for tablet PCs.<p>The change takes effect when you rebuild the mobile application using the new mobile platform and then republish the application to Google Play.</p></td><td>The Google Play store considered mobile applications optimized for phones only.</td><td>Tablet PC users can see mobile applications in the default Google Play list. Searching by title is not necessary.</td></tr><tr title="Версия 8.3.6" class="compat tag_148 tag_1"><td><a name="88ee15a0-4a2e-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 148); return false;">Calendars</a>.<br></td><td>During the creation of data composition fields, if they include calendar or contact data, you can specify just a field name, without specifying its data type.<p>Creation of data composition fields with data types specified is supported forn compatibility purposes.</p></td><td>During the creation of data composition fields, if they included calendar or contact data, specifying the full field name with its data type was required.</td><td>The system behaves as described in the documentation.<p>Simplified interaction with calendars and contacts in some scenarios.</p></td></tr><tr title="Версия 8.3.6" class="tag_149"><td><a name="ac04f3a4-4dea-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 149); return false;">Window management</a>.<br></td><td>The option to handle the change of mobile device display parameters is now available.<p>The <span class="term">OnChangeDisplaySettings</span> event handler is implemented. The event occurs when the client application display parameters are changed.</p><p>The <span class="term">Width</span> and <span class="term">Height</span> properties of the <span class="term">ClientDisplayInformation</span> object store the actual values (which depend on the screen orientation).</p></td><td>This feature was not provided.<p>The platform could not detect the changes of display parameters.</p><p>The <span class="term">Width</span> and <span class="term">Height</span> properties of the <span class="term">ClientDisplayInformation</span> object stored constant (canonical) values.</p></td><td>You can handle the display size changes caused by mobile device orientation changes or by connecting the mobile device to external displays. You can create applications with better usability.</td></tr><tr title="Версия 8.3.6" class="tag_132"><td><a name="8bf5e7c6-5446-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 132); return false;">Multimedia support</a>.<br></td><td>Photo shoot and video recording quality control implemented (for Android only).<p>Camera control for photo shoots and video recording is implemented.</p><p>In the <span class="term">MultimediaTools</span> object, for the <span class="term">PhotoSupported</span><span class="term">()</span> and <span class="term">VideoRecordingSupported</span><span class="term">()</span> methods, the <span class="term">CameraType</span> parameter is implemented.</p><p>In the <span class="term">MultimediaTools</span> object, for the <span class="term">MakePhoto</span><span class="term">() </span>method, the <span class="term">CameraType</span>, <span class="term">Resolutions</span>, <span class="term">Quality</span>, and <span class="term">Monochrome</span> parameters are implemented. For the <span class="term">MakeVideoRecording</span><span class="term">()</span> method of the <span class="term">MultimediaTools</span> object, the <span class="term">CameraType</span> and <span class="term">Quality </span>parameters are implemented. For the <span class="term">MultimediaTools</span> object, the <span class="term">GetSupportedCameraResolutions</span><span class="term">()</span> method is implemented.</p></td><td>These features were not provided.</td><td>Extended capabilities for mobile device cameras.</td></tr><tr title="Версия 8.3.6" class="tag_150"><td><a name="61dd736e-59c2-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 150); return false;">Printing</a>.<br></td><td>On the mobile platform, you can print spreadsheet documents. Printers that use PCL3 and ZPL protocols are supported. WiFi and Bluetooth are used for connecting to printers (only for Android).</td><td>This feature was not provided.</td><td>You can print spreadsheet documents from mobile applications.</td></tr><tr title="Версия 8.3.6" class="tag_2"><td><a name="48266ff6-64e0-11e4-9135-0050569f678a"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>
<p>The documentation now contains the description of the mobile platform compatibility mode:</p><ul><li>It cannot be managed from Designer.</li><li>It is not changed when an infobase is migrated to a new platform version.</li><li>It is set during the infobase creation as its mobile platform version.</li><li>It is changed to the new mobile platform version when an infobase is migrated to a new mobile platform version.</li></ul><p>The documentation also describes the correspondence of PC platform versions and mobile platform versions.</p></td><td>
<p>The mobile platform compatibility mode was not described in the documentation.</p></td><td>The documentation is updated with the latest information.</td></tr><tr title="Версия 8.3.6" class="tag_115 tag_20"><td><a name="8c45596c-709e-11e4-9135-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Asynchronous dialog box operations are available to mobile platform developers.<p>Selecting <span class="interface">Mobile device</span> in the <span class="interface">Use purposes</span> configuration property does not change the <span class="interface">Modality usage mode</span> configuration property.</p></td><td>Only synchronous dialog box operations were available to mobile platform developers. <p>When the <span class="interface">Mobile device</span> value was selected in the <span class="interface">Use purposes</span> configuration property, a request to confirm the change of the <span class="interface">Modality usage mode</span> configuration property value was displayed (only if the change was required).</p></td><td>Applied solution development for the mobile platform is simplified. Developers no longer need to support two sets of dialog box operations, one for the mobile platform and the other one for the PC platform.</td></tr><tr title="Версия 8.3.6" class="tag_69"><td><a name="c4e18102-70a8-11e4-9135-0050569f678a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>In the mobile platform, the language of generated names of form items, form attributes, form commands, form parameters, and structure properties is defined by the value of the <span class="interface">Script variant</span> configuration property.</td><td>In the mobile platform, the language of generated names of form items, form attributes, form commands, form parameters, and structure properties was English only if the default configuration language was English. Otherwise it was Russian.</td><td>The mobile platform behavior is uniform with the PC-based platform behavior.</td></tr><tr title="Версия 8.3.6" class="tag_20"><td><a name="8ec13d76-70aa-11e4-9135-0050569f678a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Push notification and local notification support is implemented. This feature relies on Apple push notification service and Google Cloud Messaging. The option to display the number of notifications that are not yet processed is implemented: mobile application icon badges (for iOS) or status bar notifications (for Android). Devices running Android 4.1 or later display the notifications diferently from devices with earlier Android version. A dedicated service provided by 1C Company is implemented to simplify the development of notifications for applied solutions that run on the PC platform. Notification senders can choose between using this service, Apple push notification service, and Google Cloud Messaging.<p>For the mobile platform, the <span class="term">DeliverableNotifications</span> global context property, the <span class="term">DeliverableNotificationManager</span> object, and the <span class="term">DeliverableNotification</span> object are implemented.</p><p>For the PC platform, the <span class="term">DeliverableNotificationSend</span> global context property, the </p><p><span class="term">DeliverableNotificationSendManager</span> object, and the <span class="term">DeliverableNotification</span> object are implemented.</p><p>For mobile applications, the <span class="interface">Push notifications</span> and <span class="interface">Local notifications </span>permissions are implemented.</p><p>The mobile application builder supports building mobile applications that use notifications.</p></td><td>This feature was not provided.</td><td>You can use standard user notifications in mobile applications. Notifications can be generated either by a mobile application on the mobile device (local notifications) or by an applied solution running on a PC (push notifications).</td></tr><tr title="Версия 8.3.6" class="tag_43"><td><a name="44013e6b-73e7-11e4-8d08-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Improved performance of dynamic list opening. The process of loading list data now has a visual presentation.</td><td>The process of loading dynamic list data had no visual presentation and took more time.</td><td>Optimized dynamic list operations.</td></tr><tr title="Версия 8.3.6" class="tag_37"><td><a name="f05049f1-8c07-11e4-b1db-0050569f678a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The following mobile platform features support secure connection (HTTPS):<ul><li> HTTP operations</li><li>POP3 and SMTP email operations</li></ul><p>Support of IMAP email operations (including secure connection) is implemented.</p><p>Support of client certificates and certification authority center certificates stored in files is implemented.</p><p>In the mobile platform the <span class="term">FileClientCertificate</span>, <span class="term">FileCertificationAuthorityCertificates</span>, and <span class="term">OpenSSLSecureConnection</span> objects are implemented, together with the corresponding properties of the <span class="term">HTTPConnection</span>, <span class="term">InternetMailProfile</span>, and <span class="term">InternetMail</span> objects.</p></td><td>The mobile platform did not support the following features:<ul><li> Secure connection for HTTP, POP3, and SMTP operations</li><li>IMAP email operations</li></ul><p>Client certificate operations and authority center certificate operations.</p></td><td>
<p>The mobile platform supports secure operations with email and with other resources.</p></td></tr><tr title="Версия 8.3.6" class="tag_53"><td><a name="5a2ae5d5-a181-11e4-b1db-0050569f678a"></a><a href="#" onclick="onTagClick(this, 53); return false;">Error handling</a>.<br></td><td>In the mobile platform for developers, you can obtain error details (the <span class="interface">Details</span> button in the error dialog box) and information for technical support (in the <span class="interface">About 1C:Enterprise</span> window).</td><td>Error details and information for technical support were not available in the mobile platform.</td><td>Improved issue diagnostics in the mobile platform for developers.</td></tr><tr title="Версия 8.3.6" class="tag_96"><td><a name="a3f61356-bcd7-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>New interface for the mobile platform client application, with a large number of improvements. The most significant changes are:<ul><li>The interface style is derived from the <span class="interface">Taxi </span>interface, but optimized for mobile devices to maximum extent.</li><li>The interface appearance is revamped. This change affects the form design, primary colors, and the look of form items. The interface now matches the modern mobile interface standards. </li><li>The main application menu is revised.</li><li>The main section command interface is revised.</li><li>Navigation options are revised.</li><li>A form and main section command interface can be both present on the start page.</li><li>Form command bar placement and generation rules are modified.</li><li>The option to display a form navigation panel is implemented.</li><li>The text input field is optimized for touch screen devices.</li><li>The form title is no longer duplicated in the form body.</li><li>Users have the option to create a list item when selecting a value from a drop-down list. </li><li>Form item context menus are supported.</li><li>Fields that require filling are not highlighted.</li><li>New display options for page groups are implemented.</li><li>Search in dynamic lists is implemented. It is based on full-text search.</li><li>A dynamic list can be sorted by tapping a column header.</li><li>Table operations are significantly revised, including scrolling, table item selection, and row rearrangement.</li><li>In managed form tables the multiple selection option is implemented.</li><li>The option to update a list by pulling the list down or up when the first or last row is on the screen ("pull to refresh") is implemented. </li><li>The approach to handling the current row of a managed form table is changed.</li><li>A managed form table is automatically scaled to fit displayed data by height, unless it displays dynamic list data.</li><li>Spreadsheet documents can be scaled using gestures.</li><li>User message appearance is revised.</li><li>Subsystems are supported (and available in the interface).</li><li>The radio button field and the track bar field are implemented.</li><li>For a managed form table the <span class="term">RefreshRequestProcessing </span>event is implemented. For the <span class="term">FormPagesRepresentation </span>system enumeration the <span class="term">Swipe </span>value is implemented. For a managed form table the <span class="term">RefreshRequest </span>property is implemented.</li><li>The <span class="interface">Move up</span>/<span class="interface">Move down </span>standard table commands are removed.</li><li>For a managed form command the <span class="interface">Use current </span><span class="interface">row </span>and <span class="interface">Associated table </span>properties are implemented (not available from 1C:Enterprise script). For a managed form button the <span class="interface">Representation in context menu</span> property is implemented (not available from 1C:Enterprise script).</li><li>Many other features are implemented. The full list of changes is quite long, therefore it is recommended that you read the chapter about mobile application development in 1C:Enterprise Developer Guide.</li></ul></td><td>The mobile application interface was similar to managed application interface version 8.2. </td><td>The mobile application interface meets the modern requirements to mobile interfaces. Improved mobile application usability. New interface uses the same color scheme and style as the <span class="interface">Taxi </span>interface, at the same time it is optimized for mobile devices.</td></tr><tr title="Версия 8.3.6" class="tag_115"><td><a name="770b1455-c708-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For devices that run Android operation system, predictive text input in multiline text boxes is implemented (with optional automatic correction of the entered text). This feature is available when it is enabled in the virtual keyboard settings.</td><td>This feature was not provided.</td><td>Improved usability for text input.</td></tr><tr title="Версия 8.3.6" class="tag_32"><td><a name="430c3853-e7ff-11e4-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>In mobile application builder, you can publish an application to Apple App Store and Google Play directly from the builder.<p>The mobile application builder help describes how to connect to Google Play Market.</p></td><td>This feature was not provided.<p>Mobile applications required manual publishing.</p></td><td>Publishing mobile applications to Apple App Store and Google Play is simplified.</td></tr><tr title="Версия 8.3.6" class="tag_43"><td><a name="1048a039-0512-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The option to specify dynamic list settings using 1C:Enterprise script is implemented.<p>The <span class="term">DynamicList.SettingsComposer</span> property is now available on the mobile platform.</p><p>The following objects are implemented: <span class="term">DataCompositionSettingsComposer</span>, <span class="term">DataCompositionUserSettings</span>, and <span class="term">DataCompositionSettings</span>, as well as their constructors and methods. Their methods are not available on the mobile platform.</p><p>The <span class="term">DataCompositionUserSettingsItemCollection </span>object is implemented.</p></td><td>This feature was not provided.</td><td>Работа с настройками динамического списка на мобильной платформе приближена к возможностям платформы для персонального компьютера.</td></tr><tr title="Версия 8.3.6" class="tag_43 tag_96"><td><a name="4657a754-78a0-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>When the selection mode is on, dynamic list rows that represent parent groups have left arrows displayed.</td><td>When the selection mode was on, dynamic list rows that represented parent groups did not have left arrows displayed.</td><td>Improved navigation of hierarhical dynamic lists in the selection mode.</td></tr></table><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="76779dc1-0b55-11e5-a3f7-0050569f678a">Library updates</a></h2><ul><li title="Версия 8.3.6" class="tag_0"><a name="9ff01241-0b55-11e5-a3f7-0050569f678a"></a>The libxml2 library is updated from version 2.6.23 to version 2.9.1.</li><li title="Версия 8.3.6" class="tag_0"><a name="bbc485a1-0b55-11e5-a3f7-0050569f678a"></a>The libxslt library is updated from version 1.1.24 to version 1.1.28.</li><li title="Версия 8.3.6" class="tag_0"><a name="d35b8601-0b55-11e5-a3f7-0050569f678a"></a>The OpenSSL library is updated from version 1.0.0o to version 1.0.0s.</li><li title="Версия 8.3.6" class="tag_0"><a name="09983a63-0b56-11e5-a3f7-0050569f678a"></a>The libpng library is updated from version 1.2.19 to version 1.6.19.</li><li title="Версия 8.3.6" class="tag_0"><a name="556764c1-0b56-11e5-a3f7-0050569f678a"></a>The libtiff library is updated from version 3.7.0 to version 4.0.3.<p>
</p></li><li title="Версия 8.3.6" class="tag_0"><a name="99cbe6f5-5b73-11e5-a3f7-0050569f678a"></a>Known vulnerabilities of cURL library are elimitaned.</li></ul><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="eb969ae2-881f-11e3-b57b-e61f135f174b">Transition from the previous version to the version 8.3.6</a></h2><ul><li title="Версия 8.3.6" class="tag_0"><a name="eb969ae3-881f-11e3-b57b-e61f135f174b"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.6.
</li><li title="Версия 8.3.6" class="tag_0"><a name="eb969ae4-881f-11e3-b57b-e61f135f174b"></a>Some features that are added in version 8.3.6 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li></ul><p><a href="#eb969ada-881f-11e3-b57b-e61f135f174b"><small>Table of contents</small></a></p><h1><a name="73b235c3-2a7f-11e3-9afe-e61f135f174b">Version 8.3.5</a></h1><p title="Версия 8.3.5" class="tag_0"><a name="73b235cd-2a7f-11e3-9afe-e61f135f174b"></a>Version 8.3.5 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#73b235c4-2a7f-11e3-9afe-e61f135f174b">New functionality and changes</a></li><li><a href="#73b235c5-2a7f-11e3-9afe-e61f135f174b">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#73b235c6-2a7f-11e3-9afe-e61f135f174b">Optimization</a></li><li><a href="#73b235c7-2a7f-11e3-9afe-e61f135f174b">Changes that affect system behavior</a></li><li><a href="#73b235c8-2a7f-11e3-9afe-e61f135f174b">Changes that require modification of configuration and administrative settings</a></li><li><a href="#73b235c9-2a7f-11e3-9afe-e61f135f174b">Renamed objects</a></li><li><a href="#e416d4fe-2f3b-11e3-9afe-e61f135f174b">Mobile platform</a></li><li><a href="#73b235ca-2a7f-11e3-9afe-e61f135f174b">Transition from the previous version to the version 8.3.5</a></li></ul><h2><a name="73b235c4-2a7f-11e3-9afe-e61f135f174b">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.5" class="compat tag_2 tag_1"><td><a name="0a79da73-2ffd-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.3.4</span> is added to the list of available values of the <span class="interface">Compatibility mode</span> property.
</td><td>Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, and 8.3.3.
</td><td>In version 8.3.5 you can run configurations created in version 8.3.4 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.5 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.4 for working with the infobase even after the transition to version 8.3.5. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="d80d5382-3593-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer, new icons for external data source tables and cubes are implemented.</td><td>Pictures for external data source tables and cubes were different.</td><td>Icons for external data source tables and cubes are uniform with other platform pictures.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="949100b3-3a46-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer, you can filter objects by parts of names, synonyms, comments, or presentations. The filter is available in the following windows:<ul><li>Configuration window</li><li>Configuration object selection dialog box</li><li>Type editing dialog box</li><li>Object properties window</li></ul><p>For the <span class="interface">Subsystem</span> configuration object, a quick filter is implemented in the configuration window. The filter is available from the <span class="interface">Subsystem</span> <span class="interface">objects</span> context menu command of the object.</p><p>In the configuration window, you can set a quick filter for configuration repository objects locked by the current user.</p></td><td>This feature was not provided.<p>Only filtering by objects included in subsystems was available.</p></td><td>Improved usability for developers.</td></tr><tr title="Версия 8.3.5" class="tag_96"><td><a name="479903a2-3c7d-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>1C:Enterprise script provides tools for managing start page (desktop) form contents and positions. <p>The <span class="term">StartPageForms</span> object is implemented. For the <span class="term">StartPageSettings</span> object, the <span class="term">GetForms</span><span class="term">()</span> and <span class="term">SetForms</span><span class="term">()</span> methods and the default constructor are implemented.</p><p>The global context method <span class="term">RefreshInterface()</span> rebuilds the start page (desktop) based on the settings from the system settings storage.</p></td><td>The <span class="term">StartPageSettings</span> object stored the differences between the start page (desktop) settings of the client application and the settings specified in Designer.<p>1C:Enterprise script did not provide tools for managing form contents and positions.</p></td><td>You can manage contents and positions of the client application start page (desktop) forms using 1C:Enterprise script.</td></tr><tr title="Версия 8.3.5" class="tag_10"><td><a name="d0c8a478-3c7e-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>For the <span class="term">Purpose</span> column of value table returned by the <span class="term">GetDBStorageStructureInfo</span><span class="term">()</span> method, new purposes are specified. The full list of database table purposes is available in the description of the <span class="term">GetDBStorageStructureInfo()</span> method in the Syntax Assistant.</td><td>The list of table purposes did not fully describe the current database schema.</td><td>The purposes of database scheme tables are described more clearly.</td></tr><tr title="Версия 8.3.5" class="compat tag_105 tag_1"><td><a name="612bb8da-45fc-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>For exchange plans, the <span class="term">ThisNode</span> standard attribute is implemented. It specifies whether the exchange plane node describes the current infobase.<p>For the <span class="term">ExchangePlanObject</span> object, the <span class="term">DataExchange</span> property is implemented. Only the <span class="term">Load</span> property can be used in this property. The <span class="term">DataExchange</span> property is used for disabling the uniqueness check of the <span class="term">ThisNode</span> item when exchange plan items are edited or deleted.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>The <span class="term">ThisNode</span> standard attribute was not available in exchange plans. Replacing the exchange plan node that described the current infobase was impossible.<p>The <span class="term">ExchangePlanObject </span>object did not have the <span class="term">DataExchange</span> property.</p></td><td>You can define <span class="term">ThisNode</span> items in a distributed infobase in a session that does not use separators.<p>You can replace the data item that describes the current infobase in the exchange plan.</p></td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="6f5e3bfe-4791-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For managed form text boxes, the <span class="term">EditTextChange</span> event is implemented. This event occurs when one of the following actions modifies the text box content:<ul><li>Typing in the text box</li><li>Copying text from the clipboard</li><li>Running <span class="interface">Undo</span> or <span class="interface">Redo</span> command</li><li>Canceling input by pressing <span class="interface">ESC</span></li></ul><p>The event occurs before the <span class="term">AutoComplete</span> event.</p></td><td>There was no event that occurred when text box content was modified. Actions triggered by this modification could be performed in the <span class="term">AutoComplete</span> event handler (with limitations).</td><td>In managed forms, complete implementation of the following scenario is available: text being typed in a text box is used as a filter parameter in the linked dynamic list.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="71376426-47b4-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>New features in the module editor:<ul><li>Find all usage instances of an export variable, procedure, or function in the entire configuration.</li><li>Convert a selected code fragment to a separate procedure or function.</li><li>Rename a local variable, procedure, or function.</li><li>Insert a comment block that describes the function or procedure purpose, parameters, and return value before the function or procedure declaration.</li><li>Convert modal calls to nonmodal calls (in a limited set of cases).</li><li>Convert procedures or functions to types that can be used in sequences of asynchronous calls.</li><li>Convert a selected code fragment to a separate procedure or function suitable for using in sequences of asynchronous calls.</li><li>Find all usage instances of modal methods in the specified module.</li><li>Convert all modal methods that are found to their asynchronous analogs.</li><li>Create notification processing events for methods that lock the interface.</li></ul><p>Commands that perform these functions are located in the <span class="interface">Refactor</span> submenu of the module text editor context menu and in the <span class="interface">Configuration</span> section of the <span class="interface">Designer</span> main menu.</p></td><td>These features were not provided.</td><td>Improved efficiency of routine operations performed by developers.</td></tr><tr title="Версия 8.3.5" class="compat tag_115 tag_1"><td><a name="178d1c4e-4b99-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In text boxes that display values of <span class="term">StandardBeginningDate</span> type, in the date input mode, the <span class="term">AutoComplete</span> (on value input) and <span class="term">TextEditEnd</span> (on generating a value based on the input string) event handlers are implemented.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In text boxes that display values of <span class="term">StandardBeginningDate</span> type, in the date input mode, the <span class="term">AutoComplete</span> (on value input) and <span class="term">TextEditEnd</span> (on generating a value based on the input string) event handlers were not implemented.</td><td>The behavior of text boxes linked to values of <span class="term">StandardBeginningDate</span> type in the date input mode is identical to behavior of text boxes linked to values of <span class="term">Date</span> type. </td></tr><tr title="Версия 8.3.5" class="tag_14"><td><a name="30a63e45-5370-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The option to follow a navigation link during client application startup is implemented, with the navigation link passed as a parameter. This feature is implemented for the 1C:Enterprise launcher, thin and thick clients, the <span class="term">Got</span><span class="term">oURL()</span> method, the standard full-text search form, and the new <span class="interface">Go to link </span>command in the startup window. Only external navigation links (which contain infobase connection settings) are supported. When following a link, the platform attempts to use running client application instances connected to the infobase specified in the navigation link. In 8.3.4 version compatibility mode, the <span class="term">Got</span><span class="term">oURL()</span> method is not modified.<p>The <span class="interface">/url</span> startup option is implemented for the launcher, thin client, and thick client.</p></td><td>This feature was not provided.<p>Users could only follow external links when they accessed the infobase using the web client.</p></td><td>Simplified access to infobase data if a link to this data is provided by third-party tools, such as email.</td></tr><tr title="Версия 8.3.5" class="tag_37"><td><a name="e881bbd4-5377-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For the <span class="term">InternetMailMessage</span> object, the <span class="term">GetSourceData()</span>, <span class="term">SetSourceData()</span>, and <span class="term">GetSourceText()</span> methods are implemented. These methods are intended for getting original email messages without changing the encoding and processing source texts of messages whose encoding was changed.</td><td>This feature was not provided.</td><td>You can save email messages to files and load them from files, provided that they comply with RFC 822 URL9, and you can also perform custom processing of email message source texts.</td></tr><tr title="Версия 8.3.5" class="compat tag_64 tag_63 tag_1"><td><a name="ec6128eb-5cd8-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Animated charts are implemented. The <span class="term">Animation</span> property is implemented for the <span class="term">Chart </span>object. The <span class="term">C</span><span class="term">hartsViewSettings</span> object is implemented. The chart display settings are stored in the system settings storage.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>This feature was not provided.</td><td>More chart display options are available.</td></tr><tr title="Версия 8.3.5" class="compat tag_65 tag_105 tag_117 tag_151 tag_1"><td><a name="daf45607-662b-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br><a href="#" onclick="onTagClick(this, 151); return false;">Web client and web service publishing tools</a>.<br></td><td>1C:Enterprise infobase data can be retrieved and modified using the OData protocol (<a href="http://www.odata.org/" target="_blank">read more</a>) v3 (<a href="http://www.odata.org/documentation/odata-version-3-0/odata-version-3-0-core-protocol/" target="_blank">read more</a>). The following data presentation is supported: <b>atom-xml</b>.<p>Enabling this feature does not require modification of applied solution, it is performed using a web server publication.</p><p>The <span class="term">enableStandardOData</span> attribute is implemented for <span class="term">&lt;point&gt;</span> tag in the <span class="interface">default.vrd</span> file.</p><p>In 8.3.4 version compatibility mode, all configuration objects that support OData protocol are available through this interface. If the compatibility mode is disabled, the access to objects is managed using the <span class="term">SetStandardODataInterfaceContent()</span> method.</p></td><td>Universal access to 1C:Enterprise infobase data was only available on Windows operating systems and was based on COM/OLE features. It was not available on Linux. The option to access data using web services implemented in applied solutions was also available.</td><td>Extended integration features for 1C:Enterprise data, including data access from external Linux systems, which does not require modification of applied solutions .</td></tr><tr title="Версия 8.3.5" class="tag_67"><td><a name="1a0129be-6bb3-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>Optimized selective comparison of forms, access rights, and command interface fragments in scenarios where the configuration repository is located on a network drive or on a repository server.<p>Local data cache is implemented for configuration repositories. You can manage the size and location of local and global repository caches using the configuration repository administration settings dialog box or <span class="interface">cfgrepo.conf</span> configuration files. These files are located in the <span class="interface">cfgrepo</span> subdirectory of the infobase service files directory (for the local cache) or in the configuration repository directory (for the global cache).</p><p>The following features are implemented for batch Designer startup mode:</p><ul><li>Clearing the global configuration repository cache (the <span class="interface">/ConfigurationRepositoryClearGlobalCache</span> command-line option)</li><li>Clearing the local configuration repository cache (the <span class="interface">/ConfigurationRepositoryClearLocalCache</span> command-line option)</li></ul></td><td>The selective comparison of forms, access rights, and command interface fragments lacked efficiency if the configuration repository was located on a network drive or on a repository server.<p>Editing the size and location of the global configuration repository cache was not available. The local cache for configuration repository data was not available.</p></td><td>Selective comparison and some other configuration repository features are optimized.<p>You can manage the size and location of configuration repository data cache.</p></td></tr><tr title="Версия 8.3.5" class="tag_43"><td><a name="4bd48d5a-79d5-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Extended search capabilities in tables that display dynamic lists. A standalone search string box that provides full-text search is implemented. Search by current cell value is available. The search history is implemented. The current search state is clearly visible. The search result includes items that have search words located both in a single column and in different columns. In each column, search by a single value is available (the <span class="interface">Find in search results</span> option is not supported).<p>For automatically created forms that contain tables linked to dynamic lists, the set of items related to search in dynamic lists is modified (together with their appearance). The search dialog box layout is modified.</p><p>The new <span class="term">FormItemAddition</span> managed form item stores additional properties of form items.</p><p>Extensions of form items intended for displaying a search string, a view status, and a search control are implemented.</p><p>For the <span class="term">FormTable</span> managed form item, the predefined items <span class="term">SearchString</span>, <span class="term">ViewStatus</span>, and <span class="term">SearchControl</span>, and also properties <span class="term">SearchStringLocation</span>, <span class="term">ViewStatusLocation</span>, and <span class="term">SearchControlLocation</span> are implemented.</p><p>The search history is stored in the system settings storage with the following key: <span class="interface">Common/TableSearchHistory/&lt;Form name&gt;.&lt;Table name&gt;</span>.</p><p>The <span class="term">SearchControl</span> picture is added to the picture library.</p></td><td>Search in tables was performed using the search dialog box. The option to search a column by multiple values (the <span class="interface">Find in search results</span> check box) was available. The search dialog box had a different layout. There was no simple way to determine whether the search is applied to a table (except for checking the availability of the <span class="interface">Cancel search</span> button if it was present on the command bar).</td><td>The search in managed form tables is improved, it is clearly visible whether the search is applied to a table.</td></tr><tr title="Версия 8.3.5" class="tag_65"><td><a name="abaa4d9b-7c2f-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 65); return false;">Web services and HTTP services</a>.<br></td><td>Developers can create HTTP services in applied solutions. Developers can access HTTP request body, headers, and line.<p>Publishing HTTP services is similar to publishing web services.</p><p>To access HTTP services, use URLs of the following format: <span class="interface">http://&lt;host name&gt;/&lt;base name&gt;/hs/&lt;resourсe identifier&gt;</span>. You can create HTTP services in the Common/HTTP services branch of the configuration tree.</p><p>The following objects are implemented: <span class="term">HTTPServices</span>, <span class="term">HTTPService</span>, <span class="term">HTTPServiceRequest</span>, and <span class="term">HTTPServiceResponse</span>.</p></td><td>This feature was not provided.<p>Only access to web services implemented in the applied solution was available.</p></td><td>You can create services that have the following advantages over web services:<ul><li>Simpler implementation.</li><li>Less amounts of data transferred.</li><li>Less computing power is required to parse a response.</li></ul><p>A different usage model (RESTful services).</p></td></tr><tr title="Версия 8.3.5" class="tag_14 tag_117"><td><a name="d123fdc4-7c34-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>The <span class="interface">Hibernated</span> session state is implemented, which is intended for preserving sessions after unexpected connection losses. Sessions that require licenses release the occupied licenses once they are hibernated. If a connection is assigned to a hibernated session, the session loses its <span class="interface">Hibernated</span> state. During the recovery from hibernation, sessions that require licenses attempt to obtain licenses. If a license cannot be obtained, the session is terminated. The option to set a timeout for automatic shutdown of hibernated sessions is implemented. If a connection to the client is closed by the 1C:Enterprise server, the session is hibernated(instead of being terminated).<p>For the <span class="term">ISessionInfo</span> object, the following properties are implemented: <span class="term">Hibernate</span>, <span class="term">PassiveSessionHibernateTime</span>, and <span class="term">HibernateSessionTerminateTime</span>. New global context methods are implemented: <span class="term">SetPassiveSessionHibernateTime()</span>, <span class="term">GetPassiveSessionHibernateTime()</span>, <span class="term">SetHibernateSessionTerminateTime()</span>, and <span class="term">GetHibernateSessionTerminateTime()</span>.</p><p>The hibernation timeout and the timeout for closing hibernated sessions can be set in Designer, in the infobase parameters dialog box.</p></td><td>This feature was not provided.<p>If a client application was inactive for 20 minutes, the session was closed.</p></td><td>In the client/server mode, in some scenarios the client application continues functioning even when the client computer stays in hibernation mode for a long time.</td></tr><tr title="Версия 8.3.5" class="tag_25"><td><a name="5027ed07-7c5c-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the data composition system, new options are implemented for comparison of string data: <span class="term">BeginsWith</span>, <span class="term">NotBeginsWith</span>, <span class="term">Like</span>, and <span class="term">NotLike</span>.</td><td>This feature was not provided.</td><td>Extended features for filtering by string expressions in reports created using the data composition system and in dynamic lists.</td></tr><tr title="Версия 8.3.5" class="tag_23"><td><a name="6362ed98-7cea-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>For catalog, chart of characteristic types, chart of accounts, chart of calculation types configuration objects, the <span class="term">GetPredefinedNames</span><span class="term">()</span> method is implemented.</td><td>This feature was not provided.</td><td>You can get the flag indicating that a configuration object has predefined items, as well as the full list of predefined item names. Using this list, you can check whether data items are set for all predefined items.</td></tr><tr title="Версия 8.3.5" class="tag_62"><td><a name="26e9075d-7d08-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>You can write data to external data source tables.<p>This feature is intended for integration with other applications, external sources should not be used as applied solution data storages.</p></td><td>This feature was not provided.<p>External data source table data was read-only.</p></td><td>New options for integration with information systems and databases.</td></tr><tr title="Версия 8.3.5" class="tag_45"><td><a name="2b4919b6-7d15-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>A query wizard for managed mode is implemented. For the <span class="term">QueryWizard</span> object, the <span class="term">Show()</span> method is implemented.<p>The following pictures are added to the picture library: </p><p><span class="term">Rename</span>, <span class="term">Attribute</span>, <span class="term">Dimension</span>, <span class="term">Resource</span>, <span class="term">NestedTable</span>, <span class="term">QueryWizardShowChangesTables</span>, <span class="term">QueryWizardCreateNestedQuery</span>, <span class="term">QueryWizardCreateTempTableDescription</span>, <span class="term">QueryWizardReplaceTable</span>, <span class="term">QueryWizardTableParameters</span>, <span class="term">QueryWizardCreateTempTableDropQuery</span></p><p><span class="term">QueryWizardTempTableDescription</span>, <span class="term">QueryWizardGroupTempTables</span>, <span class="term">QueryWizardTempTable</span>, <span class="term">QueryWizardNestedQuery</span>, and <span class="term">CustomExpression</span>.</p></td><td>This feature was not provided.</td><td>New features for using queries in managed applications.</td></tr><tr title="Версия 8.3.5" class="tag_45"><td><a name="0ecaa2c8-7e8e-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>An object model intended for modification of query texts is implemented. The <span class="term">QuerySchema</span> object is implemented.</td><td>This feature was not provided.</td><td>
<p>You can modify queries from 1C:Enterprise script without analyzing the query text.</p></td></tr><tr title="Версия 8.3.5" class="tag_26"><td><a name="8e8b59b9-7dc7-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>You can insert pictures in spreadsheet document cells. You can specify text position relative to the picture in a cell (or an area of cells) of a spreadsheet document. A picture is linked to a cell where it is inserted. <p>For the <span class="term">SpreadsheetDocumentRange </span>object, the following properties are implemented: <span class="term">Picture</span>, <span class="term">PictureSize</span>, <span class="term">PictureHorizontalAlign</span>, <span class="term">PictureVerticalAlign</span>, <span class="term">TextPositionRelativeToPicture</span>, and <span class="term">PictureParameter</span>.</p></td><td>Pictures could only be inserted in spreadsheet documents as images that were not linked to any specific cell (or an area of cells).</td><td>Improved usability of pictures in spreadsheet documents.</td></tr><tr title="Версия 8.3.5" class="tag_29"><td><a name="6dd5e829-7dd1-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Alt Linux SPT 6.0 distribution kit is supported.</td><td>This distribution kit was not supported.</td><td>New Linux distribution kit is supported.</td></tr><tr title="Версия 8.3.5" class="tag_25"><td><a name="66ca33ff-88e7-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>For the <span class="term">DataCompositionFilter</span> object, the default constructor is implemented.</td><td>This feature was not provided.</td><td>In a mobile application, you can set a filter for a list of contacts.</td></tr><tr title="Версия 8.3.5" class="tag_39"><td><a name="260e22b9-9eba-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>The <span class="term">_$Data$_.TotalsMaxPeriodUpdate</span> event with presentation <span class="interface">Data.Modify </span><span class="interface">maximum calculated totals period</span> is implemented. The event is registered when the <span class="term">SetMaxTotalsPeriod()</span> or <span class="term">SetMinAndMaxTotalsPeriods()</span> method is called.<p>The <span class="term">_$Data$_.TotalsPeriodUpdate</span> event is used for compatibility purposes.</p></td><td>The <span class="term">_$Data$_.TotalsPeriodUpdate</span> event was registered when the maximum totals period was set.</td><td>The event log displays actions that set the totals period more consistently.</td></tr><tr title="Версия 8.3.5" class="tag_15 tag_14"><td><a name="b05fe409-a468-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>1C:Enterprise searches for the ImageMagick library by name <span class="interface">libMagickWand-6.Q16</span>.</td><td>1C:Enterprise did not search the ImageMagick library by name <span class="interface">l</span><span class="interface">ibMagickWand-6.Q16</span>.</td><td>During the startup, 1C:Enterprise is not shut down if the ImageMagick library was renamed and then reinstalled.</td></tr><tr title="Версия 8.3.5" class="tag_19"><td><a name="25ea4010-aa78-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Microsoft SQL Server 2014 DBMS is now supported.</td><td>Microsoft SQL Server 2014 DBMS was not supported.</td><td>New Microsoft SQL Server version is now supported.</td></tr><tr title="Версия 8.3.5" class="tag_152"><td><a name="451a40af-ba61-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 152); return false;">Developer tools</a>.<br></td><td>For the Technological log configuration file editor (<a href="http://1c-dn.com/developer_tools/universal_reports_and_data_processors/" target="_blank">read more</a>) and User action log conversion (<a href="http://1c-dn.com/developer_tools/user_action_log_conversion/" target="_blank">read more</a>), data processors, which are distributed via 1c-dn.com, the English interface is implemented. Both data processors are rewritten using the English variant of 1C:Enterprise script.</td><td>The Technological log configuration file editor and User action log convertor data processors had Russian interface only.<p>Both data processors were written using the Russian variant of 1C:Enterprise script.</p></td><td>Simplified usage and modification of the Technological log configuration file editor and User action log convertor data processors for non-Russian-speaking developers.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="02e53f96-c568-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the "dump configuration to files" feature, the approach to dumping standard attribute data is modified. Only attributes whose properties differ from the default values (for the given attribute) are dumped. Changing properties of a single standard attribute results in dumping all of the standard attributes of the configuration object. The same behavior is implemented for loading: if an XML file contains a description of a standard attribute, it is loaded to the configuration even if the description of the standard attribute contains only default values.<p>An external data processor intended for deleting descriptions of standard attributes with default values from XML dump files is implemented.</p><p>The data processor can be used only with files dumped by 1C:Enterprise version 8.3.5. You have to use it once before loading the dumped files back to the configuration.</p><p>
</p></td><td>While dumping configuration files, standard attribute data was always dumped, even if all of the standard attribute properties had default values.</td><td>Reduced configuration file size. Reduced number of "different" objects found when comparing configurations after dumping and subsequent loading.</td></tr><tr title="Версия 8.3.5" class="compat tag_95 tag_23 tag_58 tag_1"><td><a name="aa8a01cf-e000-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>You can edit the flag that shows whether predefined data is initialized in a data area or in the entire infobase. The <span class="term">GetPredefinedDataInitialization()</span> and <span class="term">SetPredefinedDataInitialization()</span> methods are added for catalog managers, charts of characteristic types, charts of accounts, and charts of calculation types.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>Editing the flag that shows whether predefined data is initialized in a data area or in the entire infobase was not available.</td><td>Extended capabilities for processing predefined data. You can inform the system at any time that predefined data in a data area or in the entire infobase is initialized (or not initialized). In a distributed infobase, when you remove infobase subordination to the master node, you can specify that all of the predefined data items are created in the infobase whose subordination is being removed.</td></tr><tr title="Версия 8.3.5" class="tag_29"><td><a name="d8c0e92c-0b28-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft Windows Server 2012 R2 (x86-64) is now supported.</td><td>Microsoft Windows Server 2012 R2 (x86-64) was not supported.</td><td>New version of the Microsoft operating system is now supported.</td></tr><tr title="Версия 8.3.5" class="tag_6 tag_10"><td><a name="4c77f567-1270-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can use an external utility for generating dumps when the platform stops responding.<p>In the <span class="interface">logcfg.xml</span> file, the externaldump attribute of the dump element is implemented.</p><p>The <span class="interface">dumper.exe</span> utility, which is now included in the platform delivery kit, is implemented.</p></td><td>Dumps were generated by the process that stopped responding.</td><td>Eliminated the issue where the system stopped responding while generating a dump for a process that stopped responding.</td></tr><tr title="Версия 8.3.5" class="tag_105"><td><a name="1d688642-26b6-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>The instructions for unbinding an infobase from the root node and restoring a configuration in a distributed infobase node, which take into account the specifics of predefined data usage, are available in the platform documentation.</td><td>This information was not available in the documentation.</td><td>The documentation contains recommendations for using distributed infobases that include predefined data.</td></tr><tr title="Версия 8.3.5" class="tag_14 tag_115"><td><a name="166e3aa9-26d6-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In thin and thick client applications, the system behavior based on the <span class="interface">Modality usage mode</span> configuration property value is modified. For thin and thick client applications, the <span class="term">EnableCheckModal</span> startup parameter is implemented.<p>If <span class="term">EnableCheckModal</span> is not used, modal methods are executed without any warnings or exceptions.</p><p>If <span class="term">EnableCheckModal</span> is used, executing a modal method generates a warning or an exception (depending on the <span class="interface">Modality usage mode</span> configuration property value).</p><p>When an applied solution is started from Designer, the <span class="term">EnableCheckModal</span> parameter is automatically added to the applied solution command line (this behavior cannot be disabled).</p><p>The web client behavior is not modified: the command-line parameter is not used. The web client always generates a warning or an exception (depending on the <span class="interface">Modality usage mode </span>configuration property value) when modal methods are executed.</p></td><td>The modal method behavior was based on the <span class="interface">Modality usage mode</span> configuration property value only. Depending on this property value, modal methods were executed with warnings or exceptions. This behavior could not be changed using command-line parameters.</td><td>You can use external data processors that include modal methods in applied solutions where modality is disabled.</td></tr><tr title="Версия 8.3.5" class="tag_29"><td><a name="cd6c1856-40be-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Support of Microsoft Windows 8.x operating system is implemented.</td><td>Microsoft Windows 8.x operating system was not supported.</td><td>Extended list of supported operating systems.</td></tr></table><p><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="73b235c5-2a7f-11e3-9afe-e61f135f174b">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.5" class="tag_70"><td><a name="19b7b675-46e0-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>While the client application is being updated via the Internet, a dialog box displaying the progress of downloading the distribution kit from the server is being displayed. You have the option to cancel the download.</td><td><p>While the client application was being updated, the progress of downloading the distribution kit was not displayed.</p></td><td>Improved process of updating the client application using Internet services: the progress is displayed and the download can be canceled.</td></tr><tr title="Версия 8.3.5" class="tag_14"><td><a name="26518450-7c54-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The <span class="interface">Help</span> window is opened like any other form:<ul><li>In the<span class="interface"> Forms in separate windows</span> mode, it is opened in a separate window.</li><li>In the <span class="interface">Forms in tabs</span> mode, it is opened in a tab.</li><li>In the <span class="interface">Taxi</span> mode, it is opened in the main window working area.</li><li>If help is opened from a form that locks the entire interface, it is opened on top of all windows and locks the entire interface.</li><li>If help is opened from a modal form, it is opened in a modal form.</li></ul><p>The help command bar is modified.</p><p>The search is started either when the focus leaves the search text box or when the user clicks <span class="interface">Find</span>.</p></td><td><span class="interface">Help</span> was always opened in a new window, regardless of the main application window interface settings.<p>The help command bar had different content.</p><p>The search started while the search expression was still being typed (during a pause in the typing).</p></td><td>The behavior of the <span class="interface">Help</span> window is unified with other forms.</td></tr><tr title="Версия 8.3.5" class="tag_153"><td><a name="b08c1d5f-993b-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 153); return false;">Configuration installation</a>.<br></td><td>New splash screen in the configuration installation wizard.</td><td>The configuration installation wizard used a different splash screen.</td><td>The configuration installation wizard and the platform installation wizard have uniform looks.</td></tr><tr title="Версия 8.3.5" class="tag_14"><td><a name="e8063409-df3d-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>If OpenID authentication is available in an infobase, once you run the thin client and select the infobase, the authentication dialog box will display the name of the last authenticated user.</td><td>The user name box in the OpenID authentication dialog box was always empty.</td><td>The user name box behavior is uniform for all authentication methods.<p>
</p><p>
</p></td></tr><tr title="Версия 8.3.5" class="tag_95"><td><a name="28344649-0031-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>When a catalog, chart of characteristic types, or chart of accounts folder is marked for deletion, unmarked for deletion, or deleted, the platform checks whether the user has enough rights to access subordinate predefined objects.</td><td>When a catalog, chart of characteristic types, or chart of accounts folder was marked for deletion, unmarked for deletion, or deleted, the platform did not check whether the user had enough rights to access subordinate predefined objects.</td><td>The platform does not allow deletion of a catalog, chart of characteristic types, or chart of accounts folder if the folder contains a predefined item and the user does not have the right to delete that item interactively.</td></tr><tr title="Версия 8.3.5" class="tag_28"><td><a name="17ef650c-3e3b-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>When the web client is started in Google Chrome web browser on MacOS X operating system, the message that the web browser is not supported is not displayed.</td><td>When the web client was started in Google Chrome web browser on MacOS X operating system, the message that the web browser was not supported was displayed.</td><td>Improved usability of applied solution startup in the web client that is started in Google Chrome web browser on MacOS X operating system (the message is removed). Support of this web browser is subject to further discussion.</td></tr></table><p><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="73b235c6-2a7f-11e3-9afe-e61f135f174b">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.5" class="tag_58 tag_154"><td><a name="55cefa96-3005-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 154); return false;">File mode</a>.<br></td><td>In separated infobases that run in the file mode, query execution is optimized.</td><td>
<p>In separated infobases that ran in the file mode, query execution lacked efficiency.</p></td><td>Improved performance of separated infobases that run in the file mode.</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="0cca8cfc-a469-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In some scenarios, forms are opened faster.</td><td>Opening forms was not optimized.</td><td>Improved system performance in some scenarios.</td></tr><tr title="Версия 8.3.5" class="tag_117"><td><a name="dc061df1-aa78-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>Improved performance of establishing a connection to an infobase that is running in the file mode and located on a network resource.</td><td>The performance of establishing a connection to an infobase that was running in the file mode and located on a network resource was insufficient.</td><td>For the second and following users, improved performance of establishing a connection to an infobase running in the file mode and located on a network resource.</td></tr><tr title="Версия 8.3.5" class="tag_69"><td><a name="6bb1faeb-b8ab-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties.</td><td>The performance of the following operations was insufficient: execution of 1C:Enterprise script methods and getting configuration object properties.</td><td>Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties.</td></tr><tr title="Версия 8.3.5" class="tag_82"><td><a name="b46f98c9-4a32-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Improved performance of writing to accounting registers for record sets that contains no more than 10 records.</td><td>When a record set with no more than 10 records was written to an accounting register, the writing performance was insufficient.</td><td>Optimized accounting register operations.</td></tr><tr title="Версия 8.3.5" class="tag_19 tag_82 tag_58"><td><a name="95ada2d9-5440-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>In the client/server mode with IBM DB2 or Oracle Database DBMS, improved performance of writing to accounting registers that are included in the contents of common attributes used as separators.</td><td>In the client/server mode with IBM DB2 or Oracle Database DBMS, the performance of writing to accounting registers included in the contents of common attributes that were used as separators was insufficient.</td><td>Optimized accounting register operations in the client/server mode with IBM DB2 or Oracle Database DBMS.</td></tr></table><p><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="73b235c7-2a7f-11e3-9afe-e61f135f174b">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.5" class="compat tag_143 tag_1"><td><a name="89de96e3-34be-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 143); return false;">Defined types</a>.<br></td><td><p>The list of types that can be included in defined types is significantly extended.</p><p>You can use defined types in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators.</p><p>The algorithm of the configuration check for correct usage of defined types is modified: a defined type is considered valid (in each usage instance) if all types that form the defined type are valid when the check is performed.</p><p>The configuration check algorithm is not modified in 8.3.4 compatibility mode.</p></td><td>The list of types that could be included in defined types was significantly shorter.<p>The configuration check was performed as follows: check whether the defined type only includes allowed types, and check whether the defined type is not included in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators.</p></td><td>New defined type usage options in applied solution development. Particularly, integration of applied solutions with third-party subsystems is now simpler.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="3c6c91d9-34ce-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The order of standard attributes in the standard attributes window and in the role settings is modified.<p>The form wizard allows adding predefined data name fields to forms.</p></td><td>The list of standard attributes in the standard attributes window and in the role settings was not ordered.<p>The form wizard did not allow adding predefined data name fields to forms.</p></td><td>Display of standard attributes is uniform with other system features.</td></tr><tr title="Версия 8.3.5" class="compat tag_14 tag_1"><td><a name="84f3a05d-34da-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>For text documents, the <span class="interface">Save as</span> command now saves the document encoding, provided that one of the following encodings is used: ANSI, OEM, UTF-8, or UTF-16. Otherwise, the UTF-8 encoding is set.<p>Closing the <span class="interface">Save as </span>dialog box by clicking <span class="interface">Cancel</span> does not modify the encoding of the open document.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>For text documents, the <span class="interface">Save as</span> command set the UTF-8 encoding for the document being saved, regardless of the encoding that was used when the document was opened.<p>Closing the <span class="interface">Save as </span>dialog box by clicking <span class="interface">Cancel</span> set UTF-8 encoding for the open document.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_115 tag_43"><td><a name="fecf7475-3573-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In the <span class="interface">Customize form</span> dialog box, the <span class="term">DataVersion</span> field cannot be added to a form.</td><td>In the <span class="interface">Customize form</span> dialog box, the <span class="term">DataVersion</span> field could be added to a form.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_120"><td><a name="f89cacad-359b-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>At the start of a background job, the <span class="term">SessionParametersSetting</span> event handler is run after the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on).</td><td>At the start of a background job, the <span class="term">SessionParametersSetting</span> event handler was run prior to the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on).</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_58 tag_16 tag_42 tag_82 tag_121"><td><a name="97e7461b-35a8-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 121); return false;">Calculation registers</a>.<br></td><td>The configuration check and database configuration update include the check whether registers affecting a sequence are included in the same separator content as the documents included in the sequence.<p>If a register affecting a sequence is included in separator content and a document included in a sequence is not included in the content of this separator, the separator is ignored when sequence boundaries are updated in 1C:Enterprise mode.</p></td><td>The check for correspondence between separators included in a document sequence and registers affecting this sequence was not performed.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_127"><td><a name="4ec73a52-3712-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 127); return false;">Temporary storages</a>.<br></td><td>The volume of data transferred between the client and the server cannot exceed 4 GB (in the serialized form) in the following cases:<ul><li>Setting a session parameter</li><li>Single call of the <span class="term">PutToTempStorage() </span>method</li><li>Single call of the <span class="term">PutFile() </span>or<span class="term"> PutFiles(</span>) method</li></ul><p>An attempt to transfer more than 4GB leads to an unrecoverable error.</p></td><td>During an attempt to transfer more than 4GB of data (in serialized form) to the server, the client application stopped responding.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_37"><td><a name="9ccbb014-3a52-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The cURL library is updated to version 7.32. It supports new options, such as downloading files with Cyrillic names from FTP servers.</td><td>The cURL library version 7.18.2 was used.</td><td>Resolved some issues of the previous library version.</td></tr><tr title="Версия 8.3.5" class="tag_56"><td><a name="f21238ca-3a55-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>If an error related to an attempt to write an invalid character to an XML object occurs at the server side, an unrecoverable error is not generated at the client side, and the user is not prompted to restart the client application.<p>The error can be handled using the <span class="term">Try...Except</span> syntax.</p></td><td>If an error related to an attempt to write an invalid character to an XML object occurred at the server side, the unrecoverable error was generated at the client side, and the user was prompted to restart the client application.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_56"><td><a name="5adace72-3a59-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>If the <span class="term">FindDisallowedXMLCharacters</span><span class="term">()</span> method finds an incomplete surrogate Unicode pair, it returns the position of the first character of the incomplete pair.</td><td>If the <span class="term">FindDisallowedXMLCharacters</span><span class="term">()</span> method found an incomplete surrogate Unicode pair, it returned the position of the character that followed the first character of the incomplete pair.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="0483a05c-3b04-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>
<p>In a text box that is in the "choice from the list" mode and displays an empty reference, clicking the <span class="interface">Cancel</span> button is ignored.</p></td><td>In the text box that was in the "choice from the list" mode and displayed an empty reference, clicking the <span class="interface">Cancel </span>button displayed a dialog box with <span class="interface">Undefined</span> text.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_66"><td><a name="0151055a-3d76-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 66); return false;">Navigation links</a>.<br></td><td>When a navigation link is followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation link are ignored. This feature is implemented in the following scenarios:<ul><li>The <span class="term">GotoURL()</span> script method</li><li>Following a navigation link from the <span class="interface">Go to link </span>dialog box (including the scenario when the link is pasted from the clipboard)</li><li>Adding a link to Favorites from the <span class="interface">Go to link</span> dialog box</li></ul></td><td>When navigation links were followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation links were ignored. Users had to delete these characters manually.</td><td>Improved management of navigation links.</td></tr><tr title="Версия 8.3.5" class="compat tag_56 tag_155 tag_1"><td><a name="a7257881-409b-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br><a href="#" onclick="onTagClick(this, 155); return false;">Web services</a>.<br></td><td>When string values are read using the <span class="term">XMLReader</span> object or obtained using a web service, line feed characters keep their original format (they are not converted).<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>When string values were read using the <span class="term">XMLReader</span> object or obtained using a web service, the following replacements were made:<ul><li>Combinations of line feed characters <span class="term">0x0D</span>+<span class="term">0x0A</span> (<span class="interface">CR</span>+<span class="interface">LF</span>) and <span class="term">0x0D</span> (<span class="interface">CR</span>) were replaced with <span class="term">0x0A</span> (<span class="interface">LF</span>).</li><li>Combination of characters <span class="term">0x0A</span>+<span class="term">0x0D</span> (<span class="interface">LF</span>+<span class="interface">CR</span>) was replaced with <span class="term">0x0A</span>+<span class="term">0x0A</span> (<span class="interface">LF</span>+<span class="interface">LF</span>).</li></ul><p>
</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_26 tag_56"><td><a name="1a7357fb-4135-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>Settings of text boxes located in spreadsheet documents can now be serialized to XDTO. A spreadsheet document deserialized from XDTO is equivalent to its source.</td><td>
<p>During XDTO serialization of spreadsheet documents and the following deserialization, text box settings were lost.</p></td><td>Settings of text boxes located in spreadsheet documents are saved after dumping/loading configuration to/from XML files.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="e5b36ef8-413a-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td><ul><li>In the <span class="interface">Evaluate expression</span> dialog box and in the <span class="interface">Immediate</span> window, expressions are not calculated twice in the following cases:</li><li>Opening a value that has properties</li><li>Viewing a property as a collection of values in a separate window</li><li>Viewing property values in a separate window intended for viewing a collection</li><li>Viewing a string value in a separate window</li></ul></td><td>In the <span class="interface">Evaluate expression </span>dialog box and in the <span class="interface">Immediate</span> window, expressions were calculated twice in the following cases:<ul><li>Opening a value that has properties</li><li>Viewing a property as a collection of values in a separate window</li><li>Viewing property values in a separate window intended for viewing a collection</li><li>Viewing a string value in a separate window</li></ul></td><td>Eliminated the issue that introduced inaccuracies to the calculated expression result because the expression could only be calculated once (at the current debugging step).</td></tr><tr title="Версия 8.3.5" class="tag_67"><td><a name="35ab68da-42e2-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>
<p>You can perform selective comparison of form modules without building a form comparison report. The <span class="interface">Form (module)</span> command is added to the following context menus: <span class="interface">Perform selective comparison with the repository object</span>, <span class="interface">Perform selective comparison with the configuration object</span>, and <span class="interface">Perform selective comparison of object versions</span>.</p></td><td>During selective comparison of forms, two comparisons were performed: the comparison of form modules and the comparison of forms. Two reports were displayed as a result of comparison.</td><td>
<p>Improved usability of selective comparison. Comparison of form modules is now a separate command.</p></td></tr><tr title="Версия 8.3.5" class="compat tag_25 tag_1"><td><a name="08e98eba-46df-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In data composition system, the automatically generated title of a field linked to data retrieved using "<span class="term">.</span>" (dot) from a <span class="term">Ref</span> field of a tabular section contains the field presentation only. In particular, a field related to the <span class="term">TabularSection.Ref.Number</span> attribute will have the <span class="interface">Number</span> title.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In data composition system, the automatically generated title of a field linked to data retrieved using "<span class="term">.</span>" (dot) from a <span class="term">Ref</span> field of a tabular section contained the <span class="interface">Ref</span> word and a presentation of the data attribute retrieved using "<span class="interface">.</span>" (dot).</td><td>Improved appearance of reports.</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="2c2278c9-46e2-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Pessimistic lock of data described by the main form attribute is performed for the following actions in text boxes:<ul><li>Clicking the drop-down list button</li><li>Attempting to create an item from the drop-down list</li><li>Attempting to open a choice list</li><li>Starting text input</li></ul><p>If the lock cannot be set, the action is not performed.</p></td><td>Pessimistic data lock was set for the following actions in text boxes:<ul><li>Attempting to open a choice list</li><li>Starting text input</li></ul></td><td>Pessimistic data lock is set for all actions that change text box contents.</td></tr><tr title="Версия 8.3.5" class="tag_56 tag_20"><td><a name="0adda380-4c47-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the "dump configuration to files" feature, XML file format is changed for the following configuration parts: managed forms, dynamic list settings, graphical schema items, geographical schemas, functional option content, and field lists. Tag names now match the names used in 1C:Enterprise script, the XML element name spelling is unified. The dump format is more compact and clear. The properties filled with default values are not dumped.<p>Dynamic list settings are dumped to a single element, which has the data composition schema settings format.</p><p>Managed forms dumped using the previous platform versions cannot be loaded by the latest platform version.</p></td><td>In the "dump configuration to files" feature, XML files that stored managed forms, dynamic list settings, graphical schemas, geographical schemas, functional option content, and field lists had a different format.</td><td>XML files that store configuration data are more compact and better structured.</td></tr><tr title="Версия 8.3.5" class="tag_156 tag_82 tag_105"><td><a name="534d719a-51e4-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 156); return false;">Charts of accounts</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>While a chart of accounts item is being written with <span class="term">DataExchange.Load</span> property set to <span class="term">True</span>, new extra dimension types are checked for uniqueness. The unique ones are added to the table of extra dimension values, and the nonunique values are not added, which eliminates possible errors.</td><td>If a chart of accounts item was being written with <span class="term">DataExchange.Load</span> property set to <span class="term">True</span>, the check for uniqueness of extra dimensions was not performed. This could cause errors while items were being added to the table of extra dimension values.</td><td>The order of loading chart of accounts data and data of linked accounting registers does not matter.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="2e3cd502-527e-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the property palette, the <span class="interface">Sort alphabetically</span> command sorts properties by presentation (if displaying property names is disabled) or by name (if displaying property names is enabled). If a property does not have a name, the sorting is always performed by text presentation.</td><td>In the property palette, the <span class="interface">Sort alphabetically</span> command sorted properties by presentation.</td><td>The sorting command behavior depends on object property presentations.</td></tr><tr title="Версия 8.3.5" class="tag_25"><td><a name="ccf146f1-5281-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the data composition system, the conditional appearance with <span class="interface">Fields header</span> usage area is applied to an area of a vertical template that contains names of displayed fields.<p>The conditional appearance with <span class="interface">Group</span> usage area is applied to an aria of vertical template that contains values of displayed fields.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In the data composition syste, the conditional appearance with <span class="interface">Group</span> usage area was applied to all areas of a vertical template.</td><td>Improved usability of data composition system conditional appearance.</td></tr><tr title="Версия 8.3.5" class="compat tag_157 tag_1"><td><a name="ff9809e4-5282-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 157); return false;">Thick client</a>.<br></td><td>If more than two parameters are passed to the <span class="term">Insert()</span> method of the <span class="term">TableBoxColumns</span> object, an error is generated.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>Up to five parameters could be passed to the <span class="term">Insert()</span> method of the <span class="term">TableBoxColumns</span> object, while only two parameters were used. No errors were generated.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_39"><td><a name="7f1de769-5358-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>The event log format is modified. The log is now stored in an SQLite database. The log file has <span class="interface">.lgd</span> extension. <p>The log location is not changed. The SQLite log format is the default format for new infobases. The performance of accessing event log data is improved.</p><p>Existing event logs can be converted to a new format. Conversion back to the legacy format is not supported.</p><p>The <span class="term">CopyEventLog()</span> and <span class="term">ClearEventLog()</span> methods are implemented.</p><p>The event log stores time in UTC format. The standard event log viewer supports new log file format (<span class="interface">.lgd</span>).</p><p>In the standard event log viewer form the command for viewing a log stored in a file is renamed to <span class="interface">More </span>- <span class="interface">View from file</span>.</p></td><td>The event log had text format.<p>In the standard event log viewer form the command for viewing a log stored in a file had the following name: <span class="interface">More </span>- <span class="interface">Load from fi</span><span class="interface">le</span>.</p></td><td>Improved performance when accessing event log data. Improved event log reliability.<p>Better name for the command for viewing a log stored in a file.</p></td></tr><tr title="Версия 8.3.5" class="tag_39"><td><a name="7969d324-5a94-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>Deletion of a large number of event log records (more than 10 million) takes much less time.<p>You can terminate the reducing of event log size by pressing Ctrl+Break in Designer or by closing the session using administrative tools (as a result, a part of records is deleted, and the rest are not deleted).</p></td><td>The performance of event log record deletion was insufficient.<p>Reducing the event log size could not be terminated.</p></td><td>Reducing the size of a large event log takes reasonable time.<p>This operation can be terminated if needed.</p></td></tr><tr title="Версия 8.3.5" class="compat tag_26 tag_1"><td><a name="cb154739-5375-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When a spreadsheet document is saved to a PDF file, a single document copy is saved. The <span class="term">Copies</span> spreadsheet document property is ignored.<p>To include multiple copies into the PDF file, use the <span class="term">WriteFileForPrinting()</span> method of the <span class="term">RepresentableDocumentBatch</span> object.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>When a spreadsheet document was saved to a PDF file, the file contained the number of document copies specified in the <span class="term">Copies</span> property.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_14 tag_20"><td><a name="c9107209-5736-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer and thick client, customization of the search result selection background is available.</td><td>In Designer and thick client, the search result background color could not be customized.</td><td>Users can specify search result selection background color that fits their text editor settings.</td></tr><tr title="Версия 8.3.5" class="tag_105 tag_58"><td><a name="f86e3435-6637-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>In a session that does not use any separators, while session changes are being registered, the <span class="term">Update</span> right is not required for tables of objects being registered.<p>For sessions that use separators, the following features are implemented:</p><ul><li>Changes can be registered for an empty record set that is subordinate to a recorder. If any of the separators required for the record set are not used in a session, the separator values are obtained from the corresponding recorder fields.</li><li>If the full set of separator values cannot be obtained using a recorder available in the memory, an error is generated and the change registration is stopped.</li></ul></td><td>In a session that did not use any separators, while session changes were being registered, the <span class="term">Update</span> right was required for tables of objects being registered.<p>For sessions that used separators, registering changes for empty record sets that were subordinate to recorders was not available.</p></td><td>In separated mode, changes are registered correctly.</td></tr><tr title="Версия 8.3.5" class="tag_58 tag_117"><td><a name="8744c224-67b5-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>New options for <span class="term">FindMarkedForDeletion()</span>, <span class="term">FindByRef()</span>, and <span class="term">DeleteObjects()</span> methods: <ul><li>You can specify data areas that will be searched for references or where objects will be deleted.</li><li>You can include configuration objects to (or exclude configuration objects from) search or deletion.</li></ul><p>For value tables that are returned by the <span class="term">FindByRef()</span> and <span class="term">DeleteObjects()</span> methods, a new column is implemented. It contains separator values that define the data area where the found object or the object that prevents deletion of another object is located.</p><p>The <span class="term">DeleteObjects()</span> method returns a value of <span class="term">Number </span>type, which stores the number of deleted objects.</p></td><td>The search for references, search for objects marked for deletion, and deletion of marked objects were performed only in data available in the current session with the current separator values. Including individual configuration objects to (or excluding configuration objects from) search or deletion was not available.<p>The value tables that were returned by the <span class="term">FindByRef()</span> and <span class="term">DeleteObjects()</span> methods did not contain columns with separator values.</p><p>The <span class="term">DeleteObjects()</span> method was a procedure.</p></td><td>You can customize the deletion of marked objects, especially in separated infobases. You can design more detailed messages about deletion results (total objects deleted, total objects not deleted, and so on).</td></tr><tr title="Версия 8.3.5" class="tag_143"><td><a name="6af7d7ae-79e5-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 143); return false;">Defined types</a>.<br></td><td>In Designer, properties palette contents for objects that have defined type are generated based on the actual type that describes the defined type.</td><td>The properties palette contents for objects that had defined types were always displayed as if all of the objects had complex type, regardless of their actual types.</td><td>Property customization for objects that have defined types is now similar to property customization for objects whose types are specified explicitly.</td></tr><tr title="Версия 8.3.5" class="tag_116"><td><a name="d159a2b5-79f0-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>In the license activation dialog box, each PIN code is entered in a single text box, which includes an input mask (in all license acquisition scenarios).<p>During license activation by phone, each Licensing Center response line is entered in a single text box, which contains an input mask).</p><p>Pressing <span class="interface">Tab</span> switches between these text boxes.</p><p>The license registration page contains the descriptions of activation options for 5-, 10-, and 20-user licenses.</p><p>Extended error diagnostics during license activation is implemented.</p></td><td>In the license activation dialog box, each PIN code was entered in 5 text boxes (in all license acquisition scenarios).<p>During license activation by phone, the license activation dialog box had 5 text boxes for entering each Licensing Center response line.</p><p>Pressing <span class="interface">Tab</span> switched between the text boxes and response lines.</p><p>Help for various license activation methods was not available directly in the dialog box.</p><p>Some license activation error messages had complicated descriptions that might not be clear to users.</p></td><td>The software license activation dialog box is improved. PINs can be pasted from the clipboard.<p>Improved usability of entering the response from the Licensing Center during license activation by phone.</p><p>The error messages are clearer to users.</p></td></tr><tr title="Версия 8.3.5" class="compat tag_58 tag_1"><td><a name="d3f09077-79fc-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>In version 8.2.16 or earlier compatibility mode, configuration checks and database configuration updates include the check whether each document journal is included in contents of at least one common attribute, and if it does, the appropriate diagnostics is performed.<p>The configuration is not updated in this case.</p></td><td>In version 8.2.16 or earlier compatibility mode, the configuration check did not detect configuration errors if document journals were included in contents of common attributes, and therefore such errors did not prevent the configuration update.</td><td>The system cannot become inconsistent due to the fact that in version 8.2.16 or earlier document journals could not be included in common attribute contents.</td></tr><tr title="Версия 8.3.5" class="compat tag_25 tag_1"><td><a name="b05b0e35-7cf6-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The <span class="term">Group</span><span class="term">Placement</span> parameter of the data composition system does not affect the displaying of totals.<p>This change is not implemented in 8.3.4 compatibility mode.</p><p>
</p></td><td>Grouping totals were not displayed if the <span class="term">Group</span><span class="term">Placemen</span>t data composition system parameter was set to <span class="term">End</span> or <span class="term">None</span> for the selected grouping.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_26 tag_1"><td><a name="df827f8e-7cf8-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>For cells that have single-line height, tooltips that do not fit a single text line are displayed as multiple text lines.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>For cells that had single-line height, tooltips were displayed as single text lines. If tooltip text did not fit a single line, it ended with "...."</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_26 tag_1"><td><a name="1ec4ebd5-7d14-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the thin client, when a spreadsheet document is obtained from the server, empty rows located in document cells are preserved.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In the thin client, when a spreadsheet document was obtained from the server, empty rows located in document cells were lost.</td><td>Eliminated data loss during the transfer of spreadsheet documents from the server to the client.</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="5f5fe0b4-7db4-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In a managed form table cell that has a drop-down list available and the <span class="interface">Directly</span> editing mode set, pressing <span class="interface">Down Arrow</span> or <span class="interface">Up Arrow</span> keys moves the selection to another cell and does not open the drop-down list. The drop-down list is only opened when a new row is added.<p>To open the drop-down list, press<span class="interface"> Ctrl+Down </span><span class="interface">Arrow</span>.</p></td><td>In a managed form table cell (with the <span class="interface">Directly</span> editing mode set), pressing <span class="interface">Down Arrow</span> or <span class="interface">Up Arrow</span> keys might open a drop-down list. This eliminated the option to add a new row by pressing <span class="interface">Down Arrow</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_25 tag_1"><td><a name="dcdc2858-7dce-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When a data composition template is generated, expressions for calculating details that contain fields unavailable due to functional options are removed from predefined templates. <p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>When a data composition template was generated, details expressions were copied from the predefined templates without any modifications.</td><td>During report generation, errors do not occur when templates include fields unavailable due to functional options.</td></tr><tr title="Версия 8.3.5" class="tag_14"><td><a name="0538c135-7dde-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>In managed mode, if any connection issues or server-side issues occur, the client application allows to repeat a request, interrupt the operation, or shut down the application.</td><td>If any connection issues or server-side issues occurred, users were not allowed to repeat their requests. In most cases the client application was simply shut down.</td><td>The client application is more robust against connection issues or 1C:Enterprise server issues.</td></tr><tr title="Версия 8.3.5" class="tag_144"><td><a name="c9063936-7de2-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 144); return false;">Mobile application</a>.<br></td><td>If the interface compatibility mode is set to <span class="interface">Taxi</span> and then the <span class="interface">Use purposes</span> configuration property is set to<span class="interface"> Personal computer</span> and <span class="interface">Mobile device</span>, the<span class="interface"> Interface compatibility mode</span> property is automatically set to Taxi<span class="interface">. Version 8.2</span> <span class="interface">allowed</span>.<p>If changing the <span class="interface">Use purposes</span> property requires modification of <span class="interface">Modality usage mode</span> and <span class="interface">Interface compatibility mode</span> configuration property values, the user is prompted to confirm the change.</p></td><td>Selecting the <span class="interface">Mobile device</span> value in the <span class="interface">Use purposes</span> configuration property made the following changes in configuration properties without any warnings:<ul><li>The <span class="interface">Interface compatibility mode</span> property was set to <span class="interface">Version 8.2</span>.</li><li>The <span class="interface">Modality usage mode</span> property was set to <span class="interface">Use</span>.</li></ul></td><td>Designer behaves as expected.</td></tr><tr title="Версия 8.3.5" class="tag_116"><td><a name="30969ac0-7c2e-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>Users that do not have administrative rights can activate software licenses. In this scenario the license is activated for the current user.</td><td>Only users with administrative rights could activate licenses.</td><td>
<p>A user without administrative rights that does not have write access to the directory where license files for all computer users are located still can activate a software license.</p></td></tr><tr title="Версия 8.3.5" class="compat tag_95 tag_105 tag_58 tag_1"><td><a name="88d58f65-9950-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>When predefined data is changed, changes are only registered for items that are actually modified, added, or deleted.<p>When the compatibility mode is changed from <span class="interface">Version 8.3.2</span> (or earlier) to <span class="interface">Version 8.3.3 </span>(or later), all predefined item changes are registered.</p><p>When the compatibility mode is changed from <span class="interface">Version 8.3.3</span> (or later) to <span class="interface">Version 8.3.2</span> (or earlier), registration of all predefined items is removed.</p><p>When changes are registered for predefined items:</p><ul><li>If the configuration object where predefined items are changed and the exchange plan where the changes are registered do not have common separators, the changes are registered for all nodes of the exchange plan.</li><li>If the configuration object where the predefined items are changed and the exchange plan where the changes are registered have common separators, the changes are only registered for those exchange plan nodes where separator values match the separator values of predefined items.</li></ul></td><td>When predefined data belonging to a specific object was changed, all predefined items of this object were registered as if they were changed. <p>Predefined item changes were registered for all exchange plan nodes available from the session where the predefined items were changed.</p></td><td>When object predefined data is changed, object change registration tables do not significantly increase in size.</td></tr><tr title="Версия 8.3.5" class="tag_115 tag_28"><td><a name="920abbc2-adcb-11e3-a877-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client, if a managed form table cell contains multiple text lines, only lines that fit the cell height are shown. If the text does not fully fit, ellipsis (…) is added to the end of the last line. In Microsoft Internet Explorer 8 web browser, the ellipsis is not displayed.<p>In the thin client, text in managed form table cells better fits the cell height.</p></td><td>In the web client, if a managed form table cell contained multiple text lines, the lines might be cut in the manner that made them unreadable (only the upper character halves were displayed and the lower ones were cut).<p>The ellipsis was not added to the end of the last line.</p><p>In the thin client, sometimes text in managed form table cells did not fit the cell height well, a redundant empty line was added to the bottom of the cell.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_25 tag_1"><td><a name="2de0bea1-c3b1-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items are removed: <ul><li>Items that include references to fields disabled by functional options</li><li>Items that include references to fields unavailable due to access rights restrictions</li><li>Items linked to data composition schema fields that no longer exist</li></ul><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items were removed: <ul><li>Items that included to fields disabled by functional options </li><li>Items that included references to fields unavailable due to access rights restrictions</li></ul></td><td>Improved system stability.</td></tr><tr title="Версия 8.3.5" class="tag_117"><td><a name="85b4b7d1-c565-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>You can load the infobase dump file (<span class="interface">*.dt</span>) that was generated with the following conditions:<ul><li>The dump was created in the file mode .</li><li>1C:Enterprise version 8.3.4 was used for dumping.</li><li>Filled aggregates of turnover accumulation registers were available in the infobase.</li></ul><p>In some scenarios, the aggregates of turnover accumulation registers are cleared after the loading.</p></td><td>Loading the infobase dump file (<span class="interface">*.dt</span>) was not available if the file was generated with the following conditions: <ul><li>The dump was created in the file mode .</li><li>1C:Enterprise version 8.3.4 was used for dumping.</li><li>Filled aggregates of turnover accumulation registers were available in the infobase.</li></ul></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_64"><td><a name="2ea22249-c6d0-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Text fragments found during a search by substring are displayed in a uniform way (bold font and green text) in the following cases:<ul><li>In managed form text box drop-down lists</li><li>In favorites</li><li>In history</li><li>In dynamic lists</li><li>In the full-text search form</li></ul></td><td>The substrings that were found had different looks.</td><td>Uniformed look for different features.</td></tr><tr title="Версия 8.3.5" class="compat tag_56 tag_1"><td><a name="39f4b3b0-cec1-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>For charts of accounts and charts of calculation types, the <span class="term">Predefined</span> field of predefined tabular sections is available for writing. In charts of accounts and charts of calculation types, the predefined records of predefined tabular sections can include only predefined items. During a serialization of a chart of accounts item or a chart of calculation types item to XML(XDTO), the <span class="term">Predefined</span> item, which matches the <span class="term">Predefined</span> property, is written. During the deserialization, the <span class="term">Predefined</span> item value is written to the <span class="term">Predefined</span> property only if the compatibility mode is disabled.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>For charts of accounts and charts of calculation types, the <span class="term">Predefined</span> field of predefined tabular sections was read-only.<p>During the serialization of a chart of account item or a chart of calculation types item to XML(XDTO), the <span class="term">Predefined</span> item was not generated.</p></td><td>During data exchange between configurations, the flags of predefined data are no longer lost in the chart of accounts and chart of calculation types items.</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="8cca731a-dff4-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Getting a choice form in a slow connection scenario is implemented identically to getting forms in other scenarios.</td><td>Getting a choice form in a slow connection scenario was implemented differently from getting forms in other scenarios, it included caching the form.</td><td>Increased relaibility for getting choice forms in a slow connection scenario.</td></tr><tr title="Версия 8.3.5" class="compat tag_23 tag_1"><td><a name="13d91f4b-e003-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>During the restructuring of hierarchical predefined data, if an item parent is not found during the update, the item is moved to the top level.<p>During the creation or restructuring of predefined data, if references to subordinate items are missing from predefined tabular sections, rows with missing references are deleted. Upon deletion, the platform generates a diagnostics message or an event log record, and the tabular section row numbering is updated accordingly.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>Invalid references to parent items or subordinate items in predefined data might cause errors during infobase retructuring.</td><td>Increased system stability in the scenario where predefined data items contain invalid references to parent or subordinate items.</td></tr><tr title="Версия 8.3.5" class="tag_86"><td><a name="7f6a2596-e71d-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>In the <span class="interface">Taxi </span>interface the scaling of pictures in the sections panel of the web client is now identical to that of the thin client. The picture height is calculated as follows:<ul><li>If any of the pictures have height more than 48 pixels, they are scaled to the height of 48 pixels.</li><li>If all of the pictures have height less that 48 pixels, the section panel height is calculated based on the maximum picture height, while smaller pictures are centered at their respective positions.</li></ul></td><td>In the <span class="interface">Taxi</span> interface of the web client 48x48 pixel squares were reserved for section panel pictures. The size of larger pictures was reduced proportionally and smaller pictures were centered within those squares. The section panel height was never reduced.</td><td>The <span class="interface">Taxi </span>interface behavior in the web client is unified with that of the thin client.</td></tr><tr title="Версия 8.3.5" class="tag_26 tag_56"><td><a name="f47b8cce-26af-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file is not important.</td><td>When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file was important.</td><td>Spreadsheet documents serialized to XDTO using 1C:Enterprise version 8.3.4 and earlier can be read without errors.</td></tr><tr title="Версия 8.3.5" class="tag_158"><td><a name="c0258dc0-29e2-11e4-9760-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 158); return false;">Third-party software</a>.<br></td><td>The OpenSSL library is updated to version 1.0.0r.</td><td>OpenSSL version 1.0.0m was used.</td><td>Eliminated OpenSSL security issues.</td></tr><tr title="Версия 8.3.5" class="tag_28"><td><a name="43d7b961-42ef-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The web client is optimized for Google Chrome 37 web browser. The managed form issues where text did not fit the desired area are eliminated.</td><td>The web client had issues related to displaying text in Google Chrome 37 web browser.</td><td>
<p>Improved Google Chrome 37 web browser support.</p></td></tr><tr title="Версия 8.3.5" class="tag_19"><td><a name="69426b7e-4a32-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Improved reliability of PostgreSQL DBMS operations in certain scenarios.</td><td>Insufficient reliability of PostgreSQL DBMS operations in certain scenarios.</td><td>Improved reliability of PostgreSQL DBMS operations.</td></tr><tr title="Версия 8.3.5" class="tag_94"><td><a name="ecd02f33-4e0c-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 94); return false;">Regional settings</a>.<br></td><td>For Russia, a single one-hour time zone shift is applied in line with Federal Law #248-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.<p>
</p></td><td>The platform did not reflect the changes introduced by Federal Law #248-FZ.</td><td>The time offset changes introduced by the new law are implemented.</td></tr><tr title="Версия 8.3.5" class="tag_11"><td><a name="5a899fcd-2ac1-11e5-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>A section describing add-in limitations is added to the Add-in development technology document (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>).</td><td>The Add-in development technology document did not describe add-in limitations.</td><td>Improved add-in technology description.</td></tr><tr title="Версия 8.3.5" class="tag_14 tag_20"><td><a name="3de3029a-079b-11e6-a3f7-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>When the thick client (<span class="interface">1cv8</span>) is started in ordinary application mode, the performance indicator window is not displayed.</td><td>When the thick client (<span class="interface">1cv8</span>) was started in ordinary application mode, the performance indicator window was not displayed.</td><td>The display of performance indicators in ordinary applications is disabled because they are rarely used in this mode.</td></tr></table><p><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="73b235c8-2a7f-11e3-9afe-e61f135f174b">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.5" class="compat tag_43 tag_1"><td><a name="06393dc4-3002-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Dynamic lists cannot be ordered by extra dimension fields of accounting registers. An attempt to order a dynamic list by these fields (for example, by clicking the column header) does not result in a server call.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>An attempt to order a dynamic list by extra dimension fields of accounting registers generated an error message and initiated a server call, which did not retrieve any data.</td><td>Dynamic lists do not allow ordering that does not make sense, therefore the system behaves as expected (from the user’s point of view).</td></tr><tr title="Версия 8.3.5" class="compat tag_23 tag_1"><td><a name="93364be2-3010-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>An attempt to set a value to <span class="term">ThisObject </span>or <span class="term">AdditionalProperties</span> attribute of a <span class="term">CatalogObject</span>, <span class="term">ExchangePlanObject</span>, or <span class="term">ChartOfCharacteristicTypesObject</span> raises an exception.<p>An attempt to set a value to the <span class="term">DataExchange</span> attribute of a <span class="term">CatalogObject </span>or <span class="term">ChartOfCharacteristicTypesObject </span>raises an exception.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>An attempt to set a value to <span class="term">ThisObject</span> or <span class="term">AdditionalProperties</span> attribute of a <span class="term">CatalogObject</span>, <span class="term">ExchangePlanObject</span>, or <span class="term">ChartOfCharacteristicTypesObject</span> did not raise an exception, and the value was not set.<p>An attempt to set a value to the <span class="term">DataExchange</span> attribute of a <span class="term">CatalogObject</span> or <span class="term">ChartOfCharacteristicTypesObject </span>did not raise an exception, and the value was not set.</p></td><td><p>Unified processing of the specified properties: an attempt to set a value for a read-only attribute raises an exception.</p></td></tr><tr title="Версия 8.3.5" class="tag_14 tag_6"><td><a name="a7bf04d7-301a-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>If the client and server application versions do not match, the search for client application distribution kit is performed in the following order:<ul><li>Search in the 1C:Enterprise installation directory (the <span class="term">InstalledLocation</span> property in <span class="interface">1cestart.cfg</span> and <span class="interface">1cescmn.cfg</span> files)</li><li>Search in the directories specified as locations for distribution files of new versions (the <span class="term">DistributiveLocation</span> property in <span class="interface">1cestart.cfg</span> and <span class="interface">1cescmn.cfg</span> files, and the <span class="term">CommonCfgLocation</span> property in the <span class="interface">1cestart.cfg </span>file)</li><li>Search by the URL that is returned in the server exception about the mismatch of client and server application versions (the <span class="term">PublishDistributiveLocation</span> parameter in the <span class="interface">conf.cfg</span> file and the <span class="term">pubdst</span> attribute of the <span class="term">ws</span> tag in the <span class="interface">default.vrd</span> file)</li><li>Search using Internet services for getting the client application distribution kit</li></ul></td><td>If the client and server application versions did not match, the search for client application distribution kit was performed in the following order:<ul><li>Search in the 1C:Enterprise installation directory (the <span class="term">InstalledLocation</span> property in <span class="interface">1cestart.cfg</span> and <span class="interface">1cescmn.cfg</span> files)</li><li>Search in the directories specified as locations for distribution files of new versions (the <span class="term">DistributiveLocation</span> property in <span class="interface">1cestart.cfg</span> and <span class="interface">1cescmn.cfg</span> files, and the <span class="term">CommonCfgLocation</span> property in the <span class="term">1cestart.</span><span class="interface">cfg</span> file)</li><li>Search by the URL, that is returned in the server exception about the mismatch of client and server application versions (the <span class="term">PublishDistributiveLocation</span> parameter in the <span class="interface">conf.cfg</span> file and the <span class="term">pubdst</span> attribute of the <span class="term">ws</span> tag in the <span class="interface">default.vrd</span> file)</li><li>Search using Internet services for getting the client application distribution kit</li></ul></td><td>Search for updates behaves as expected: search in the local network precedes search using Internet services.</td></tr><tr title="Версия 8.3.5" class="compat tag_58 tag_1"><td><a name="88bf7340-34b6-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>The <span class="term">SetPredefinedDataUpdate()</span> and <span class="term">SetInfoBasePredefinedDataUpdate()</span> methods can only be executed in sessions that do not have any separators (in addition to the fact that they require the <span class="interface">Administration</span> right).<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td><p>The<span class="term"> </span><span class="term">SetPredefinedDataUpdate()</span> and <span class="term">SetInfoBasePredefinedDataUpdate()</span> methods could be executed in any session, provided that the user had the <span class="term">Administration</span> right.</p></td><td>Users cannot change the infobase predefined data update mode if they do not have the required rights.</td></tr><tr title="Версия 8.3.5" class="compat tag_66 tag_14 tag_1"><td><a name="c142dbe8-356c-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 66); return false;">Navigation links</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td><p>The <span class="term">ReferencesArray</span> parameter of the <span class="term">GetURLsPresentations()</span> function is mandatory. The return value of this function is always an array. For input array items whose presentations cannot be obtained, the matching output array items contain <span class="term">UNDEFINED</span>.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>The<span class="term"> ReferencesArray</span> parameter of the <span class="term">GetURLsPresentations()</span> function was not mandatory. In cases when a parameter value presentation could not be obtained by its value, uniform system behavior across all client applications was not guaranteed.</td><td>The <span class="term">GetURLsPresentations()</span> function is uniform across all client applications.</td></tr><tr title="Версия 8.3.5" class="tag_28"><td><a name="d67bb561-3570-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client, performing the <span class="term">Execute</span><span class="term">()</span> operator ends in exception.</td><td>In the web client, calling the <span class="term">Execute()</span> operator was ignored and no diagnostic messages were displayed.</td><td>Implemented applied solution error diagnostics (for calling the <span class="term">Execute()</span> operator in the web client).</td></tr><tr title="Версия 8.3.5" class="compat tag_26 tag_1"><td><a name="f3e03d3e-3594-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the <span class="term">SpreadsheetDocumentRange</span> object, the <span class="term">TopBorder</span>, <span class="term">RightBorder</span>, <span class="term">BottomBorder</span>, and <span class="term">LeftBorder</span> properties contain the <span class="term">UNDEFINED</span> value if the corresponding border is not the same for all cells.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In the <span class="term">SpreadsheetDocumentRange</span> object, values of the <span class="term">TopBorder</span>, <span class="term">RightBorder</span>, <span class="term">BottomBorder</span>, and <span class="term">LeftBorder</span> properties were retrieved from the properties of a random cell within the specified range</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_25 tag_1"><td><a name="39731644-3596-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In data composition system batch queries, when a temporary table is created, if the table fields are not used by the next queries of the batch and the table is not included in required joins, the query that creates the table is removed from the batch.<p>This change is not implemented in 8.3.4 compatibility mode</p></td><td>In data composition system batch queries, temporary tables were deleted from the batch if the table fields were not used by the next queries of the batch and the table was not used in other queries of the batch that also created temporary tables.</td><td>Improved management of temporary tables in the data composition system.</td></tr><tr title="Версия 8.3.5" class="tag_105 tag_16"><td><a name="6153db51-3b06-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>Changes in information registers that have dimensions of <span class="term">UUID</span> type that are included in the main filter are recorded correctly.<p>In tables that store the register change records, fields describing dimensions of<span class="term"> UUID </span>type have <span class="term">UUID</span> type.</p></td><td>Changes in information registers that had dimensions of <span class="term">UUID</span> type were recorded incorrectly.<p>In tables that stored the register change records, fields describing dimensions of <span class="term">UUID</span> type had <span class="term">BinaryData</span> type.</p></td><td>Eliminated unexpected system behavior. In exchange plans containing information registers with dimensions of <span class="term">UUID</span> type that are included in the main filter, registering all dimensions is required.</td></tr><tr title="Версия 8.3.5" class="compat tag_69 tag_36 tag_1"><td><a name="e28a97ac-409d-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>In the thin client, the following types are not available: <span class="term">ValueTableRow</span>, <span class="term">ValueTableColumnCollection</span>, <span class="term">ValueTableColumn</span>, <span class="term">CollectionIndexes</span>, <span class="term">CollectionIndex</span>, <span class="term">ValueTreeRowCollection</span>, <span class="term">ValueTreeRow</span>, <span class="term">ValueTreeColumnCollection</span>, and <span class="term">ValueTreeColumn</span>.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In the thin client, the following types were available: <span class="term">ValueTableRow</span>, <span class="term">ValueTableColumnCollection</span>, <span class="term">ValueTableColumn</span>, <span class="term">CollectionIndexes</span>, <span class="term">CollectionIndex</span>, <span class="term">ValueTreeRowCollection</span>, <span class="term">ValueTreeRow</span>, <span class="term">ValueTreeColumnCollection</span>, and <span class="term">ValueTreeColumn</span>.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_115 tag_1"><td><a name="28c5f81b-412a-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed form text boxes, the <span class="term">TextEditEnd</span> event handler is not called when the spin buttons are clicked.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>
<p>In managed form text boxes, the <span class="term">TextEditEnd</span> event handler was called when spin buttons were clicked.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_23 tag_115 tag_1"><td><a name="97dc6693-4133-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When an object is created from a dynamic list filtered by an attribute of <span class="term">Date</span> type, object attributes of that type are filled from the filling data. <p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>When an object was created from a dynamic list filtered by an attribute of <span class="term">Date</span> type, object attributes of that type were not filled from the filling data.<p>For such attributes, the standard <span class="term">FillingValues</span> parameter of the new item form contained values of the <span class="term">StandardBeginningDate </span>type passed from the dynamic list filters.</p></td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_115 tag_1"><td><a name="4fcd36dc-4137-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed form text boxes, if editing a string with an input mask results in a string that matches an empty input mask, an empty string is recorded to the form attribute displayed in the text box. If the string has fixed length, the string consists of spaces.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In managed form text boxes, if editing a string with an input mask resulted in a string that matched an empty input mask, a string that contained spaces and fixed input mask characters was recorded to the form attribute displayed in the text box.</td><td>When a text box is cleared, an empty string is recorded to the linked attribute regardless of the input mask availability. In text boxes linked to attributes of <span class="term">Text</span> type with the input mask set, the automatic "incomplete" mark is displayed correctly.</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="64b4bda1-51e6-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed form text boxes, the procedure of generating a drop-down list during input by string is modified. The procedure is described in the documentation.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In managed form text boxes, the following procedure was used for generating a choice list during input by string:<ul><li>Search by beginning of the string is performed and the first 10 results are added to the list.</li><li>If the list contains less than 10 items, search by substring is performed and its results are added to the list until it contains 10 items.</li><li>If the list still contains less than 10 items, results of search by other fields available for search during input by string are added to the list.</li></ul></td><td>In managed form text boxes, eliminated issues in the procedure of drop-down list generation when search is performed both by beginning of string and by substring.</td></tr><tr title="Версия 8.3.5" class="compat tag_115 tag_1"><td><a name="2683ee38-51e8-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Getting the list of desktop forms is implemented. For the <span class="interface">Forms in tabs</span> and <span class="interface">Taxi</span> interface modes, the <span class="term">ClientApplicationWindows</span> collection contains a separate item that describes the start page (desktop). The <span class="term">Content</span> property of this item contains the list of forms available on the start page (desktop).<p>For the <span class="interface">Forms in separate windows</span> interface mode, the <span class="term">ClientApplicationWindows</span> collection contains <span class="term">ClientApplicationWindow</span> objects that describe forms located on the desktop.</p><p>For the <span class="term">ClientApplicationWindow</span> object, the <span class="term">StartPage</span> and <span class="term">Content</span> properties are implemented.</p><p>The <span class="term">GetContent()</span> method of the <span class="term">ClientApplicationWindow</span> is supported for compatibility purposes.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>This feature was not provided.<p>For the <span class="interface">Forms in tabs</span> and <span class="interface">Taxi</span> interface modes, the <span class="term">ClientApplicationWindows</span> collection did not contain objects describing the start page (desktop).</p><p>For the<span class="interface"> Forms in separate windows</span> interface mode, the <span class="term">ClientApplicationWindows</span> collection did not contain objects describing forms opened on the desktop.</p></td><td>Developers can access forms located on the start page (desktop) using 1C:Enterprise script.</td></tr><tr title="Версия 8.3.5" class="compat tag_51 tag_1"><td><a name="c91439a3-51e8-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>For subordinate objects of the <span class="term">TestedApplication</span> object, the <span class="term">TestedClientApplicationWindow</span> object is implemented. The object describes the start page (desktop).<p>Forms (objects of <span class="term">TestedForm</span> type) included in the start page (desktop) content are subordinate to the <span class="term">TestedClientApplicationWindow</span> object that describes the start page (desktop).</p><p>For the <span class="term">TestedClientApplicationWindow</span> object, the <span class="term">StartPage</span> property is implemented. </p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>The <span class="term">TestedClientApplicationWindow</span> object that described the start page (desktop) was not included in the subordinate objects of the <span class="term">TestedApplication</span> object. <p>Forms included in the start page (desktop) were subordinate to the <span class="term">TestedClientApplicationWindow</span> object that had its <span class="term">IsMain</span> property set to <span class="term">True</span>.</p></td><td>You can access forms located on the start page (desktop) from 1C:Enterprise script using automated testing tools.</td></tr><tr title="Версия 8.3.5" class="tag_58 tag_105"><td><a name="ab85c8e7-51ec-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>An exception that does not cause application termination occurs when predefined data is registered for an unseparated configuration object in a separated exchange plan from a session that uses all separators.</td><td>An exception that caused application termination occurred when predefined data was registered for an unseparated configuration object in a separated exchange plan from a session that used all separators.</td><td>Eliminated issues that resulted in application termination.</td></tr><tr title="Версия 8.3.5" class="compat tag_58 tag_105 tag_1"><td><a name="ab85c8e8-51ec-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>If a configuration object does not use all separators where it is included, calling the <span class="term">InitializePredefinedData()</span> method does not initialize predefined data items for this object.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>If a configuration object did not use all separators where it was included, calling the <span class="term">InitializePredefinedData()</span> method caused an error.</td><td>The <span class="term">InitializePredefinedData</span><span class="term">()</span> method can be used in any session, not only when all separators are used.</td></tr><tr title="Версия 8.3.5" class="tag_19 tag_25 tag_43"><td><a name="e2220fe7-5738-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>For the <span class="term">LIKE</span> query language operation, search in dynamic lists, and filter in the data composition system, the search template length is limited. The limit depends on the DBMS type. If the template length exceeds the limit, an error is generated, which does not lead to 1C:Enterprise shutdown.</td><td>For the <span class="term">LIKE</span> query language operation, search in dynamic lists, and filter in the data composition system, if the search template exceeded 1024 characters, this could cause a DBMS error and 1C:Enterprise shutdown.</td><td>1C:Enterprise is not shut down when a search template is too long.</td></tr><tr title="Версия 8.3.5" class="tag_23"><td><a name="5789034b-5739-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>The value of the <span class="term">IsFolder</span> field is correctly passed to the <span class="term">PresentationGetProcessing</span> handler.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>The value of the <span class="term">IsFolder</span> field passed to the <span class="term">PresentationGetProcessing</span> handler was inverted.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_115 tag_1"><td><a name="55ca70be-6303-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The managed form visibility setting is stored in the system setting storage with a purpose use key. The object key is generated as follows: <span class="term">&lt;Full form name&gt;/&lt;Purpose use key&gt;/FormSettings</span>.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>The managed form visibility setting was stored in the system setting storage without a purpose use key. The object key was generated as follows: <span class="term">&lt;Full form name&gt;/FormSettings</span>.</td><td>You can use a single form for different use purposes, with custom display settings for each use purpose.</td></tr><tr title="Версия 8.3.5" class="compat tag_25 tag_1"><td><a name="fbceca65-7c5a-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Data composition system expressions are calculated in the safe mode.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>
<p>The safe mode was not used when data composition system expressions were calculated.</p></td><td>Improved security of executing reports that might use insecure methods from common modules.</td></tr><tr title="Версия 8.3.5" class="compat tag_115 tag_1"><td><a name="01965a50-7cf4-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed form tables, you can start dragging from an available table cell only. <p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In managed form tables, dragging from any table cell was allowed. When an attempt to drag an unavailable cell was made, the currently selected cell was dragged instead.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_25 tag_1"><td><a name="ff54f8ae-7cfe-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The <span class="interface">Text</span> parameter of conditional appearance that is specified for the <span class="interface">F</span><span class="interface">ields header</span> usage area is applied to grouping field headers.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>The <span class="interface">Text</span> parameter of conditional apperance was never applied to grouping field headers.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_25 tag_1"><td><a name="6a30494e-7dcc-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>The data composition template generator always generates the <span class="term">VerticalLevel</span> property for nested reports. The parent report level is added to the value of this property.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>
<p>Parent report groupings were not taken into account when nested reports were displayed.</p></td><td>Parent report groupings affect nested reports: nested reports are displayed at the same grouping level as the parent report.</td></tr><tr title="Версия 8.3.5" class="compat tag_115 tag_1"><td><a name="526e5990-79c1-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For managed form fields, the <span class="term">PeriodField</span> field type is implemented. It is intended for simplifying selection of periods of several full months.<p>For managed form field extensions for calendar fields, the <span class="term">Border</span> property is implemented. It specifies border parameters for the calendar field.</p><p>The dialog box that was used in the following scenarios is modified:</p><ul><li>Period selection for dynamic lists</li><li>Standard period selection for text boxes that display values of <span class="term">StandardPeriod</span> type</li><li>The <span class="term">StandardPeriodEditDialog </span>object dialog box</li></ul><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>For managed form fields, the PeriodField field type was not available.<p>For managed form field extensions for calendar fields, the Border property was not available.</p><p>A different dialog box was used in the following scenarios:</p><ul><li>Period selection for dynamic lists</li><li>Standard period selection for text boxes that display values of <span class="term">StandardPeriod</span> type</li><li>The <span class="term">StandardPeriodEditDialog </span>object dialog box</li></ul><p>If the period variant was not custom, a drop-down list containing available options was opened in the input field.</p></td><td>The period selection dialog box is improved.</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="523966d2-881c-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed form tables, if a row is added because editing the previous row is finished or by pressing the <span class="interface">Down Arrow</span>, and then the row is neither edited from 1C:Enterprise script nor edited interactively, the new row is automatically deleted once the selection is moved away from it.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In managed form tables, if a row was added because editing the previous row was finished or by pressing the <span class="interface">Down Arrow</span>, and then the row was not edited interactively, the new row was automatically deleted once the selection was moved away from it.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="85307678-881e-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>While a text box choice history is being filled, the check for deleted items is performed. A value presentation is removed from the list if its data was deleted in the current session or its data was deleted in another session but the presentation of deleted data was obtained in this session. If a value is deleted after the choice history is generated, when a user attempts to select this value, a warning is displayed, the value is not selected, and the item is removed from the history list.<p>The feature is implemented for thin and web clients.</p></td><td>Deleted values were displayed in text box choice history as <span class="interface">Object not found</span> items.</td><td>References to objects that are no longer available for selection are removed from the choice history.</td></tr><tr title="Версия 8.3.5" class="compat tag_115 tag_1"><td><a name="279d49fa-b324-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed forms, the length of the <span class="term">PurposeUseKey</span> property value is limited to 128 characters. An attempt to set a value longer than 128 characters or open a form with this property value longer than 128 characters ends with a exception.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>
<p>In managed forms, the length of the <span class="term">PurposeUseKey</span> property value was not limited.</p></td><td>Simplified diagnostics of issues related to <span class="term">PurposeUseKey</span> value being too long. </td></tr><tr title="Версия 8.3.5" class="tag_97"><td><a name="3a88d501-bfe0-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 97); return false;">Data access restrictions</a>.<br></td><td>For each configuration object that is included in separator content and has tabular sections, a data access restriction check is performed (after writing) if the access restriction conditions include attributes from the object tabular section.<p>As a result, a message about insufficient access rights might be displayed in situations where it was not displayed earlier.</p><p>
</p></td><td>For configuration objects that were included in separator content and had tabular sections, data access restriction checks were not performed (after writing) if the access restriction conditions included attributes from the object tabular sections.</td><td>Eliminated unexpected system behavior.
</td></tr><tr title="Версия 8.3.5" class="compat tag_95 tag_156 tag_159 tag_1"><td><a name="a20c656f-e00a-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br><a href="#" onclick="onTagClick(this, 156); return false;">Charts of accounts</a>.<br><a href="#" onclick="onTagClick(this, 159); return false;">Charts of calculation types</a>.<br></td><td>The following rules now apply during infobase restructuring:<ul><li>A row of a predefined tabular section of a chart of accounts or a chart of calculation types, which is added in 1C:Enterprise mode and refers to a predefined item, is marked predefined if a predefined row that refers to the same item is added in Designer mode.</li><li>When a predefined row is deleted from a predefined tabular section of a chart of accounts or a chart of calculation types, the actual row is not deleted. Instead, it loses the "predefined" flag.</li></ul><p>In addition to that, the order of tabular section rows might be changed to ensure that all of the predefined items are at the top.</p><p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In a chart of accounts, adding a predefined extra dimension type in Designer mode was impossible if the extra dimension type was added in 1C:Enterprise mode earlier. When an attempt to delete a predefined row from a predefined tabular section of a chart of accounts was made, the actual row was deleted.<p>Charts of calculation types had the following behavior:</p><ul><li>In 1C:Enterprise version 8.2.12 or earlier, the behavior was the same as in 1C:Enterprise version 8.3.5.</li><li>In 1C:Enterprise versions 8.2.13–8.3.4, if a base, leading, or displacing calculation type that was added earlier in 1C:Enterprise mode was then added in Designer mode, a duplicate calculation type entry was generated. When a predefined row was deleted from a predefined tabular section of a chart of calculation types, the actual row was deleted.</li></ul></td><td>Editing predefined tabular sections no longer might cause data losses.<p>Editing the list of extra dimension types of a predefined account in Designer might result in a message that the account's maximum number of extra dimension types is exceeded.</p></td></tr><tr title="Версия 8.3.5" class="compat tag_82 tag_42 tag_16 tag_121 tag_1"><td><a name="a93a2a51-6fc7-11e4-9135-0050569f678a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br><a href="#" onclick="onTagClick(this, 121); return false;">Calculation registers</a>.<br></td><td>In a value table obtained by the <span class="term">Unload</span><span class="term">()</span> method of an accounting register, accumulation register, calculationregister, or information register record set, the value of the <span class="term">LineNumber</span> column is equal to the line number in the record set.<p>This change is not implemented in 8.3.4 compatibility mode.</p></td><td>In the value table obtained by the <span class="term">Unload</span><span class="term">()</span> method of an accounting register, accumulation register, calculation register, or information register record set, the value of the <span class="term">LineNumber</span> column was equal to the index of the record set index.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="compat tag_14 tag_37 tag_1"><td><a name="526a712b-73e6-11e4-8d08-0050569f678a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The TLS protocol is recommended for secure connections as it is more secure. The SSL protocol version 3.0 is disabled by default. <p>If the web server used for thin client connections can use SSL version 3.0 for connecting to a web server, you can use the thin client command-line option <span class="term">/HttpsAllowSSLv3</span>.</p><p>SSL version 3.0 is not used (by default) with the <span class="term">HTTPConnection</span>, <span class="term">FTPConnection</span>, <span class="term">InternetMail</span>, <span class="term">WSProxy</span>, <span class="term">WSReference</span>, and <span class="term">WSDefinition</span> objects, when connecting to the configuration repository, and in Debugger. If you need to use SSL version 3.0 in these scenarios, use the <span class="term">AllowSSLv3</span> option in the <span class="interface">conf.cfg</span> file. For the conf.cfg configuration file, the <span class="term">AllowSSLv3</span> option is implemented.</p><p>For the <span class="term">InternetMail</span> object in version 8.3.5 and earlier compatibility mode and in earlier 1C:Enterprise versions:</p><ul><li>On Windows, you can enable the SSL protocol version 3.0 by editing the system register.</li><li>On Linux, the availability of SSL protocol version 3.0 is defined by the OpenSSL library version.</li></ul></td><td>The SSL protocol version 3.0 was used for secure connections.</td><td>Improved security of connections established by client applications that work over the Internet.</td></tr><tr title="Версия 8.3.5" class="tag_28 tag_11"><td><a name="ce4eb0e0-4240-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>The file system extension and the cryptography extension are modified (for all supported Windows web browsers). The reason is that the NPAPI technology is no longer supported in Google Chrome browser.<p>New extension versions perform all file and cryptography operations asynchronously (using notifications). </p><p>To be able to use 1C:Enterprise extensions and browser extensions, you are required to install a dedicated web browser extension. The web client prompts you to install that extension once you attempt to enable a browser extension.</p><p>On the client side, add-ins, the file system extension, and the cryptography extension run asynchronously. Synchronous add-in, file system extension, and cryptography extension operations are supported on the client side for compatibility purposes. Refactoring applied solutions, including those that have add-ins, is required to support synchronous operations:</p><ul><li>change method calls to calls of <span class="term">BeginCalling&lt;</span><span class="term">MethodName</span><span class="term">&gt;()</span> asynchronous methods,</li><li>change reading property values to calls of <span class="term">BeginGetting&lt;PropertyName&gt;() </span>asynchronous method,</li><li>change setting property values to calls of <span class="term">BeginSetting&lt;PropertyName&gt;()</span> asynchronous method.</li></ul><p>Refactoring add-ins is not required. The platform automatically adds prefixes and asynchronous behavior support to add-in methods.
The <span class="term">SynchronousExtensionAndAddInCallUseMode </span>configuration property is implemented. If the property is set to Do not use, NPAPI-based extensions are not loaded in the web client and, as a result, synchronous methods cannot be executed. In other cases, an attempt to load an NPAPI-based extension is performed. If an extension is successfully loaded, both synchronous and asynchronous methods can be executed. For more information, see the documentation.</p><p>Previous extension versions can be uninstalled in a regular way.</p><p>Improved add-in development technology (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>).</p><p>The following global context methods are implemented: <span class="term">BeginAttachingCryptoExtension()</span>, <span class="term">BeginAttachingFileSystemExtension()</span>, <span class="term">BeginAttachingAddIn()</span>, <span class="term">BeginCopyingFile(), BeginMovingFile(), BeginDeletingFiles()</span>, <span class="term">BeginFindingFiles()</span>, <span class="term">BeginCreatingDirectory()</span>, <span class="term">BeginGettingTempFilesDir()</span>, <span class="term">BeginGettingDocumentsDir()</span>, <span class="term">BeginGettingUserDataWorkDir()</span>, <span class="term">BeginGettingFiles()</span>, <span class="term">BeginPuttingFiles()</span>, <span class="term">BeginRequestingUserPermission()</span>, and <span class="term">BeginRunningApplication()</span>.</p><p>For the <span class="term">CryptoManager</span> object, a constructor without parameters is implemented, and also the following methods: <span class="term">BeginInitialization()</span>, <span class="term">BeginEncrypting()</span>, <span class="term">BeginSigning()</span>, <span class="term">BeginGettingCryptoModuleInformation()</span>, <span class="term">BeginGettingCertificatesFromSignature()</span>, <span class="term">BeginGettingCertificateStore()</span>, <span class="term">BeginVerifyingSignature()</span>, <span class="term">BeginCheckingCertificate()</span>, and <span class="term">BeginDecrypting()</span>. </p><p>For the <span class="term">CryptoCertificate</span> object, a constructor without parameters is implemented, and also the following methods: <span class="term">BeginInitialization() and BeginUnloa</span><span class="term">d.</span></p><p>For the <span class="term">CryptoTools</span> object, the <span class="term">BeginGettingCryptoModuleInformation()</span> method is implemented.</p><p>For the <span class="term">CryptoCertificateStore</span> object, the <span class="term">BeginAdding()</span>, <span class="term">BeginFindingByThumbprint()</span>, <span class="term">BeginFindingBySerialNumber()</span>, <span class="term">BeginFindingBySubject()</span>, <span class="term">BeginGettingAll()</span>, and <span class="term">BeginDeleting()</span> methods are implemented.</p><p>For the <span class="term">FileDialog</span> object, the <span class="term">Show</span><span class="term">()</span> method is implemented.</p><p>For the <span class="term">File</span> object, a constructor without parameters is implemented, and also the following methods: <span class="term">BeginInitialization()</span>, <span class="term">BeginGettingModificationTime()</span>, <span class="term">BeginGettingHidden()</span>, <span class="term">BeginGettingReadOnly()</span>, <span class="term">BeginGettingSize()</span>, <span class="term">BeginGettingModificationUniversalTime()</span>, <span class="term">BeginCheckingExist()</span>, <span class="term">BeginSettingModificationTime()</span>, <span class="term">BeginSettingHidden()</span>, <span class="term">BeginSettingReadOnly()</span>, <span class="term">BeginSettingModificationUniversalTime()</span>, <span class="term">BeginCheckingIsDirectory()</span>, and <span class="term">BeginCheckingIsFile()</span>.</p><p>You can use the refactoring feature to convert synchronous extension and add-in methods to their asynchronous counterparts. New refactoring settings are available. </p></td><td>The file system extension and the cryptography extension were implemented using the NPAPI technology. The extension methods were executed synchronously. In Google Chrome web browser synchronous execution of methods from add-in APIs was possible. </td><td>
<p>The platform supports asynchronous add-in, cryptography extension, and file system extension operations in the web client, which ensures Google Chrome support.</p><p>Important! Support of synchronous operations in Google Chrome is disabled by default since version 42 (April 2015) and discontinued since version 45 (September 2015). Therefore, synchronous 1C:Enterprise script methods will stop working in Google Chrome even if you use a platform version that supports them.</p><p> </p></td></tr><tr title="Версия 8.3.5" class="tag_28 tag_11"><td><a name="2cc6b50e-48a7-11e4-a179-0050569f678a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>The add-in technology (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>) no longer supports add-in development for Safari web browser for Windows.</td><td>The add-in technology supported add-in development for Safari web browser for Windows.</td><td>The outdated web browser is no longer supported. The Apple company stopped updating Safari web browser for Windows.</td></tr><tr title="Версия 8.3.5" class="tag_11"><td><a name="e6cd743a-8f4e-11e4-b1db-0050569f678a"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>The add-in development technology supports Mozilla Firefox web browser versions 31.0 and later. It is recommended that you build a new installer package for Mozilla Firefox using the new adapter. It is also recommended that you remove installer packages for Mozilla Firefox versions 30.0 and earlier from the add-in archive.<p>The add-in development technology does not support Mozilla Firefox web browser versions 30.0 or earlier.</p><p>Adapters for Mozilla Firefox versions 30.0 or earlier are removed.</p></td><td>The add-in development technology did not support Mozilla Firefox web browser versions 31.0 or later.<p>The add-in development technology supported Mozilla Firefox web browser versions 30.0 and earlier.</p></td><td>The add-in development technology supports the latest versions of Mozilla Firefox web browser (31.0 or later).<p>The add-in development technology does not support older versions of Mozilla Firefox web browser (30.0 or later).</p></td></tr></table><p><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="73b235c9-2a7f-11e3-9afe-e61f135f174b">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.5" class="tag_0"><td><a name="b9eeae1b-8805-11e3-b57b-e61f135f174b"></a>The names of <span class="term">AddressData</span> object properties are changed. For compatibility purposes, the previous names are supported.</td><td><ul><li><span class="term">Street</span></li><li><span class="term">House</span></li></ul></td><td><ul><li><span class="term">PrimaryAddressString</span></li><li><span class="term">AdditionalAddressString</span></li></ul></td></tr><tr title="Версия 8.3.5" class="tag_0"><td><a name="456f247c-9eb9-11e3-8f48-e61f135f174b"></a>In the event log, presentations of the following events are modified: <span class="term">_$</span><span class="term">Data$_.TotalsMinPeriodUpdate</span> and <span class="term">_$</span><span class="term">Data$_.Totals</span><span class="term">PeriodUpdate</span>.</td><td><ul><li><span class="interface">_$Data$_.TotalsMinPeriodUpdate</span></li><li><span class="interface">Data. Modify totals period</span></li></ul></td><td><ul><li><span class="interface">Data</span><span class="interface">. </span><span class="interface">Modify </span><span class="interface">minimum calculated totals </span><span class="interface">period</span></li><li><span class="interface">Data</span><span class="interface">. </span><span class="interface">Modify </span><span class="interface">maximum calculated totals period</span></li></ul></td></tr></table><p><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="e416d4fe-2f3b-11e3-9afe-e61f135f174b">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.5" class="tag_43 tag_45"><td><a name="fb85651f-2ffb-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Custom queries, including queries that generate dynamic lists, are now available in the mobile platform.</td><td>This feature was not provided in the mobile platform.</td><td>In mobile applications, you can use dynamic lists generated based on custom queries, and use queries to the infobase for implementing various features, such as checking balance while posting documents</td></tr><tr title="Версия 8.3.5" class="tag_115"><td><a name="a0a1ea5c-2ffc-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Faster form opening and faster execution of context server calls.</td><td>Insufficient performance of form opening and execution of context server calls.</td><td>Improved user experience by improving the performance of form operations.</td></tr><tr title="Версия 8.3.5" class="tag_23"><td><a name="9740c9c6-34a4-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Predefined items are created at the first call of the corresponding table. Calling the <span class="term">SetPredefinedDataUpdate()</span> method before the first call modifies the flag that shows whether predefined data is created.</td><td>Predefined items were only created when mobile application configuration was updated. After calling the <span class="term">SetPredefinedDataUpdate()</span> method, predefined data was only modified during the next mobile application configuration update.</td><td>Mobile platform behavior is uniform with that of PC platform version 8.3.3.</td></tr><tr title="Версия 8.3.5" class="tag_120"><td><a name="8b56c265-34af-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>Background jobs are now available in the mobile platform.</td><td>This feature was not provided in the mobile platform.</td><td>Background jobs are available in mobile applications.</td></tr><tr title="Версия 8.3.5" class="tag_110 tag_104"><td><a name="dcd8da06-359e-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>In the mobile platform, the following features are available:<ul><li>Functional options and functional option parameters.</li><li>Roles (limited support). Role management of item visibility and availability for forms and for the command interface.</li><li>A role setting for form visibility on the start page. After functional options and roles are applied, the first form from the list of available forms is displayed.</li><li>Infobase users (limited support).</li></ul><p>Limitations of the implemented features are described in the documentation.</p></td><td>These features were not provided in the mobile platform.</td><td>Extended features for applied solution interface management.</td></tr><tr title="Версия 8.3.5" class="tag_117"><td><a name="1c03ad5a-3ba7-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 117); return false;">Database operations</a>.<br></td><td>The <span class="term">EraseInfoBaseData</span><span class="term">()</span> global context method is implemented.</td><td>This feature was not provided on the mobile platform.</td><td>On the mobile platform, you can delete all infobase data.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="e3a628b5-527b-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer, support of Android Debug Bridge (adb) is added. Now you can start a mobile application from Designer on a mobile device emulator or on a physical device connected to a computer.</td><td>This feature was not provided.</td><td>Easier development and debugging of mobile applications for Android OS.</td></tr><tr title="Версия 8.3.5" class="tag_37 tag_160"><td><a name="2ea5c74f-62fb-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 160); return false;">Telephony</a>.<br></td><td>New features:<ul><li>Send and receive emails using the built-in mail client of a mobile device. The <span class="term">MailTools</span> object is implemented.</li><li>Send and receive SMS and MMS messages. The <span class="term">SMSMessage</span> object is implemented.</li><li>Dial phone numbers. The <span class="term">TelephonyTools</span> object is implemented.</li><li>Access the call history filterred by call type(incoming, outgoing, or missed).The <span class="term">CallLog</span> object is implemented.</li></ul><p>The limitations of the telephony tools on supported operating systems are listed in documentation.</p></td><td>Sending SMS messages and making calls was available with some limitations using parameters of the <span class="term">RunApp()</span> and <span class="term">GotoURL()</span> methods.<p>Access to the call history and sent email messages from the built-in email client was not available.</p></td><td>Easy access to mobile device functionality: SMS and MMS, call history, and making calls.</td></tr><tr title="Версия 8.3.5" class="tag_29"><td><a name="295eac3a-7dd1-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The configuration property <span class="term">RequiredMobileApplicationPermissions</span>, specifies permissions that mobile application will require on Android:<ul><li>Multimedia</li><li>Geolocation</li><li>Reading and writing contacts</li><li>Reading and writing calendar events</li><li>Access to telephony</li></ul><p>The Mobile application builder uses the specified permissions.</p></td><td>This feature was not provided.</td><td>You can specify permissions required for your mobile applications more clearly.</td></tr><tr title="Версия 8.3.5" class="tag_161"><td><a name="49b02ed2-7de0-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 161); return false;">Multimedia tools</a>.<br></td><td>Scanning barcodes using the mobile device camera is supported.<p>For the <span class="term">MultimediaTools</span> object, the following methods are implemented: <span class="term">BarcodeScannerScanning</span><span class="term">()</span>, <span class="term">ShowBarcodeScanning</span><span class="term">()</span>, and <span class="term">CloseBarcodeScanning</span><span class="term">()</span>.</p></td><td>This feature was not provided.</td><td>New mobile platform feature.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="8acce749-7dd0-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer, you can edit pictures with variants. You can convert images to images with variants and back.</td><td>You could only load pictures with variants without editing them.</td><td>Creating images for mobile applications became easier.</td></tr><tr title="Версия 8.3.5" class="tag_162"><td><a name="c3bd2dc7-87fc-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 162); return false;">Access to mobile device features</a>.<br></td><td>Access to mobile device contact lists, both local and linked to specific accounts, is implemented. The following objects are implemented: <span class="term">ContactManager</span>, <span class="term">ContactData</span>, <span class="term">AccountContactData</span>, <span class="term">LocalContactKey</span>, <span class="term">ContactAccount</span>, <span class="term">ContactDataItem</span>, and <span class="term">ContactDataItemInstantMessaging</span>.</td><td>This feature was not provided.</td><td>You can access mobile device contacts.</td></tr><tr title="Версия 8.3.5" class="tag_162"><td><a name="782bdd76-8802-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 162); return false;">Access to mobile device features</a>.<br></td><td>Access to mobile device calendars linked to specific accounts is implemented. The following objects are implemented: <span class="term">CalendarManager</span>, <span class="term">CalendarAccount</span>, <span class="term">LocalCalendarKey</span>, <span class="term">LocalCalendarEventKey</span>, <span class="term">CalendarEventData</span>, <span class="term">AccountCalendarEventData</span>, <span class="term">CalendarData</span>, and <span class="term">AccountCalendarData</span>.</td><td>This feature was not provided.</td><td>You can access mobile device calendars.</td></tr><tr title="Версия 8.3.5" class="tag_163"><td><a name="2dde191f-8806-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 163); return false;">Location tools</a>.<br></td><td>For the <span class="term">AddressData</span> object, the <span class="term">AddressString</span> property is implemented. It stores an address fragment starting from the street.</td><td>This feature was not provided.</td><td>The <span class="term">AddressData</span> object functionality is extended. It can be used not only for geolocation purposes, but also for storing various types of contact information.</td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="93c21507-26e0-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The mobile platform distribution kit <span class="interface">mobile.zip</span> now includes the <span class="interface">version.txt</span> file. The file contains the version number of the mobile platform delivered in the archive.</td><td>This feature was not provided.</td><td>Simplified identification of the mobile platform version, including scenarios that use Mobile application builder.</td></tr><tr title="Версия 8.3.5" class="tag_32"><td><a name="5628d9f8-cf65-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>The mobile application builder, which is included in the mobile platform, is improved:<ul><li>The temporary user directory is no longer used for building. An explicitly defined directory is used instead, the path to this directory must contain ASCII characters only.</li><li>The build date of each mobile application is recorded (and displayed).</li><li>You can save graphic assets and mobile configurations to the hard disk.</li><li>When the mobile platform version 8.3.5 is loaded, the version number is obtained automatically from the <span class="interface">version.txt</span> file, which is included in the mobile platform distribution kit (<span class="interface">mobile.zip</span>).</li><li>Android SDK version 17 or later is required for building mobile applications for Android.</li><li>For files that contain graphic assets, the check whether the file contains a full set is implemented (the check is also performed when the file is loaded).</li><li>Files that contain graphic assets support icons for devices with high density screens (size 144 x 144 pixels, file name <span class="interface">Android\icon-144x144.png</span>).</li><li>Other improvements are implemented.</li></ul></td><td>The mobile application builder had the following features:<ul><li>The temporary user directory was used for building mobile applications. The mobile application could not be built for Android if the name of the user on whose behalf the build was performed contained non-ASCII characters.</li><li>Mobile application build dates were not recorded.</li><li>Saving graphic assets and mobile configurations to the hard disk was not available.</li><li>Android SDK version 17 was required for building mobile applications for Android, other versions were not supported.</li><li>The mobile platform did not support icons for Android devices with high density screens.</li></ul></td><td>The usability of the mobile application builder is improved.</td></tr><tr title="Версия 8.3.5" class="tag_14"><td><a name="55b50014-e71b-11e3-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The text displayed on the mobile platform splash screen is translated to all localization languages.</td><td>The text displayed on the mobile platform splash screen was always displayed in Russian.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.5" class="tag_36"><td><a name="8318ea66-05da-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The option to run external applications on mobile devices and get the results of their execution is implemented. This feature is only available on operating systems of Android family.<p>The <span class="term">MobileDeviceApplicationLaunch </span>and <span class="term">MobileDeviceApplicationLaunchExtrasData </span>objects are implemented.
</p></td><td>This feature was not provided.</td><td>Simplified applied solution integration with mobile applications, including the option to get mobile application execution result.<p>This feature is only available on operating systems of Android family.</p></td></tr><tr title="Версия 8.3.5" class="tag_20"><td><a name="22973130-26e2-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During the building of an Xcode project, the "executable" attribute is set for the <span class="interface">1cem</span> file included in the project.</td><td>During the building of an Xcode project, the attributes of the <span class="interface">1cem</span> file included in the project were not changed.</td><td>Eliminated the problem that occurred when a project file was rebuilt on an operating system of Windows family: the "executable" attribute of the 1cem file was cleared.</td></tr><tr title="Версия 8.3.5" class="tag_64 tag_32"><td><a name="6328516f-715b-11e4-8d08-0050569f678a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 32); return false;">Mobile application builder</a>.<br></td><td>In the mobile platform, graphical assets for iPhone 6 and iPhone 6 Plus devices are implemented:<ul><li>splash screens: 750x1334, 2208x1242, and 1242x2208</li><li>icons: 87x87 and 180x180</li></ul><p>In the mobile application builder, support of graphical assets for iPhone 6 and iPhone 6 Plus devices is implemented.</p></td><td>The mobile platform and mobile application builder did not support graphical assets required for iPhone 6 and iPhone 6 Plus devices.</td><td>New Apple mobile devices are supported.</td></tr></table><p><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="73b235ca-2a7f-11e3-9afe-e61f135f174b">Transition from the previous version to the version 8.3.5</a></h2><ul><li title="Версия 8.3.5" class="tag_0"><a name="73b235cb-2a7f-11e3-9afe-e61f135f174b"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.5.
</li><li title="Версия 8.3.5" class="tag_0"><a name="73b235cc-2a7f-11e3-9afe-e61f135f174b"></a>Some features that are added in version 8.3.5 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.5" class="tag_0"><a name="07f93235-01ab-11e4-98ab-e61f135f174b"></a>1C:Enterprise version 8.3.5 cannot share a configuration repository with any of the earlier 1C:Enterprise versions. In this scenario users of the earlier versions receive a diagnostic error message.</li></ul><p><a href="#73b235c3-2a7f-11e3-9afe-e61f135f174b"><small>Table of contents</small></a></p><h1><a name="46d1c4ad-74f7-11e2-adcc-e61f135f174b">Version 8.3.4</a></h1><p title="Версия 8.3.4" class="tag_0"><a name="46d1c4b7-74f7-11e2-adcc-e61f135f174b"></a>Version 8.3.4 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#46d1c4ae-74f7-11e2-adcc-e61f135f174b">New functionality and changes</a></li><li><a href="#46d1c4af-74f7-11e2-adcc-e61f135f174b">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#46d1c4b0-74f7-11e2-adcc-e61f135f174b">Optimization</a></li><li><a href="#46d1c4b1-74f7-11e2-adcc-e61f135f174b">Changes that affect system behavior</a></li><li><a href="#46d1c4b2-74f7-11e2-adcc-e61f135f174b">Changes that require modification of configuration and administrative settings</a></li><li><a href="#46d1c4b3-74f7-11e2-adcc-e61f135f174b">Renamed objects</a></li><li><a href="#c6e539b1-4128-11e3-9afe-e61f135f174b">Mobile platform</a></li><li><a href="#46d1c4b4-74f7-11e2-adcc-e61f135f174b">Transition from the previous version to the version 8.3.4</a></li></ul><h2><a name="46d1c4ae-74f7-11e2-adcc-e61f135f174b">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.4" class="compat tag_2 tag_1"><td><a name="7fd1cd50-d8b8-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.3.3</span> is added to the list of available values of the <span class="interface">Compatibility mode</span> property.
</td><td>Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, and 8.3.2.
</td><td>In version 8.3.4 you can run configurations created in version 8.3.3 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.4 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.3 for working with the infobase even after the transition to version 8.3.4. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
</td></tr><tr title="Версия 8.3.4" class="tag_36"><td><a name="4dd39796-da40-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>In the <span class="term">RepresentableDocumentBatchItems</span> object, the optional parameter <span class="term">DocumentAddress</span> is implemented for the <span class="term">Add()</span> and <span class="term">Insert()</span> methods. This parameter stores the address of the temporary storage for the document being saved.</td><td>This feature was not provided.</td><td>Improved usability of generating document batches for saving and printing.</td></tr><tr title="Версия 8.3.4" class="tag_26"><td><a name="88f14d63-da42-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>You can save spreadsheet documents in HTML 5 format. Сharts and grafic primitives are saved in SVG format; free text rotation is supported.</td><td>This feature was not provided.</td><td>You can save spreadsheet documents in HTML 5 format.</td></tr><tr title="Версия 8.3.4" class="tag_120"><td><a name="0bd211d3-da4d-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>When specifying a value for the <span class="term">Parameters</span> property of the <span class="term">BackgroundJobs</span> object or for the <span class="term">Parameters</span> property of the <span class="term">Execute()</span> method of the <span class="term">ScheduledJob</span> object, you can omit any number of last parameters, provided that their default values are defined in the method that implements the background or scheduled job.</td><td>During the start of a background or scheduled job, if any number of last parameters with default values specified were not specified explicitly, an exception was raised.</td><td>You can modify methods implementing background or scheduled jobs by adding new parameters to the end of the parameter list, provided that their default values are defined. In this case modification of previously created code fragments that describe creation of background or scheduled jobs is not required.</td></tr><tr title="Версия 8.3.4" class="tag_20"><td><a name="647b2806-e3da-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In Designer, the following module editor features are available:<ul><li>Selecting all entries of the identifier marked by cursor location</li><li>Selecting all entries of an identifier marked by a double-click</li><li>Selecting pairs of opening and closing 1C:Enterprise script clauses (including brackets):<span class="term"> Procedure ... EndProcedure</span>,<span class="term"> If ... EndIf</span>, and so on</li></ul><p>Selecting identifiers is disabled by default. To use this feature, enable it in Designer options dialog box. Selecting the search expression is available in Designer, thick client, and thin client.</p></td><td>This features were not provided.</td><td>The 1C:Enterprise script editor is improved.</td></tr><tr title="Версия 8.3.4" class="tag_62"><td><a name="73586b18-f394-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>External data sources support all features of the MySQL query language.<p>In the <span class="term">ExternalDataSourceConnectionParameters</span> object, the MySQL value is implemented for the <span class="term">DBMS</span> property.</p><p>In the technological log, the <span class="term">DBMySQL</span> property is implemented for the <span class="term">DBMS</span> property of the<span class="term"> EDS</span> event..</p></td><td>External data sources did not support all features of the MySQL query language.</td><td>Dynamic lists, temporary tables, and other platform features are now supported for MySQL external data sources.</td></tr><tr title="Версия 8.3.4" class="tag_96"><td><a name="0645c692-f3ab-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>Management of client application interface content from 1C:Enterprise script is implemented.<p>The objects <span class="term">ClientApplicationInterfaceContentSettings</span>, <span class="term">ClientApplicationInterfaceContentSettingsGroup</span>, and <span class="term">ClientApplicationInterfaceContentSettingsItem</span><span class="term"> </span>are implemented. Calling the <span class="term">RefreshInterface</span><span class="term">()</span> global context method rebuilds interface panels according to the settings from the system storage.</p><p>For the <span class="term">ClientApplicationInterfaceSettings</span> object, a constructor and methods <span class="term">GetContent</span><span class="term">()</span> and <span class="term">Set</span><span class="term">C</span><span class="term">ontent</span><span class="term">()</span> are implemented.</p></td><td>The <span class="term">ClientApplicationInterfaceContentSettings</span> object stored the differences between the client application settings and the settings specified in Designer.<p>Interface management from 1C:Enterprise script was not supported.</p></td><td>1C:Enterprise script-based management of application interface panel visibility and positions.</td></tr><tr title="Версия 8.3.4" class="tag_51"><td><a name="dd0a4246-1b80-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>For the <span class="term">TestedFormField</span> object, the <span class="term">WaitForDropListGeneration</span><span class="term">()</span> method is implemented.</td><td>This feature was not provided.</td><td>The option to wait while a dynamic list is being generated is now available. You can use it when the generation takes significant time.</td></tr><tr title="Версия 8.3.4" class="tag_96"><td><a name="3813db62-1b89-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>A new display option intended for improving the view of item-heavy forms without introducing any significant form changes is available in the <span class="interface">Taxi </span>interface. The <span class="interface">Scale</span> property is implemented for managed forms. The property is only available if the <span class="interface">Interface compatibility mode</span> configuration property is set to <span class="interface">Version</span><span class="interface"> 8.2</span>. For the <span class="term">ClientSettings</span> object, the <span class="term">ClientApplicationFormScaleVariant</span> property is implemented.<p>This property modifes the scale of all forms in the applied solution for a specific user.</p></td><td>This feature was not provided. There was no simple way to make a form compact.</td><td>For applications designed for <span class="interface">Version 8.2</span> interface and not yet migrated to <span class="interface">Taxi</span>, a new option that regulates the scale of managed form items is implemented.<p>You can modify both a scale of a single form (which is not yet redesigned for <span class="interface">Taxi</span> interface mode) and the scale of the entire application (you might need this if the applied solution runs on a computer with a low-resolution or small-sized display).</p><p>The scale of a single form is specified in Designer, while the scale for the entire application is specified in the settings for a specific user.</p></td></tr><tr title="Версия 8.3.4" class="tag_115"><td><a name="14e0a145-1bab-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Passing additional parameters to an object creation form that is opened from a managed form text box is implemented (in addition to passing filters and standard parameters). Choice forms are used for storing additional parameters and passing them to item creation forms. Additional parameters are specified in choice parameters and choice parameter links using parameter naming forms (the parameter names must have the <span class="term">Additional.</span> prefix). When item creation is initiated from a text box, these parameters are passed directly to the item creation form. When item creation is initiated from a drop-down list in a text box, they are first passed to the list form and then, when item creation is actually initiated, they are passed to the item creation form.<p>The standard parameter <span class="term">AdditionalParameters</span> of <span class="term">Structure</span> type is implemented for managed form extensions of objects, catalogs, documents, charts of characteristic types, business processes, tasks, and dynamic lists.</p><p>For dynamic list table extensions, the <span class="term">AdditionalCreateParameters</span> property of <span class="term">FixedStructure</span> type is implemented.</p></td><td>Filter values could be passed from text fields to item creation forms as filling values. Additional parameters could not be passed.</td><td>You can pass additional parameters (that are not filter options) to an item creation form that is opened from a text box.</td></tr><tr title="Версия 8.3.4" class="tag_115"><td><a name="9a3b5dc8-1bb3-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>You can enable or disable history for text fields linked to data of the following types: catalog, document, business process, task, chart of characteristic types, chart of calculation types, chart of accounts, or exchange plan.<p>The <span class="term">ChoiceHistoryOnInput </span>property of configuration objects, configuration object attributes, and form items defines whether the history is enabled.</p></td><td>This feature was not provided.</td><td>For text fields whose business logic does not require keeping the history of values, you can disable the history.</td></tr><tr title="Версия 8.3.4" class="tag_115"><td><a name="9e17bcc4-1c4a-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>You can use the <span class="term">DropListWidth </span>property to specify minimum width of drop-down lists for managed form text fields. The actual list width is the minimum value of the following: the property value and the stabdard width (40 characters).</td><td>Drop-down lists in text fields had fixed width (40 characters).</td><td>You can increase the width of drop-down lists that contain long items.</td></tr><tr title="Версия 8.3.4" class="tag_67"><td><a name="33368658-1eda-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>In Designer batch mode, the following features are available:<ul><li>Creating a configuration repository (<span class="interface">/ConfigurationRepositoryCreate</span> command-line option)</li><li>Creating a configuration repository user(<span class="interface">/ConfigurationRepositoryAddUser </span>command-line option)</li><li>Copying users from another configuration repository (<span class="interface">/ConfigurationRepositoryCopyUsers</span> command-line option)</li></ul></td><td>This feature was not provided. Configuration repository administrators only could create new configuration repositories and users interactively.</td><td>You can automate administrative operations on configuration repositories, including automatic creation of repositories for project parts that are being developed independently.</td></tr><tr title="Версия 8.3.4" class="compat tag_43 tag_164 tag_1"><td><a name="b15b3637-1f79-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 164); return false;">Document journals</a>.<br></td><td>In document journals, you can use "Create" commands parametrized by the type of document being created. In a dynamic list that has a document journal table specified as its main table, a document creation button that opens a submenu with the list of documents available for the current user can be generated automatically.<p>For dynamic list form table extensions, a standard <span class="term">CreateByParameter</span> command is implemented.</p><p>For the <span class="term">Button</span> form item, the<span class="term"> Parameter</span> property is implemented. It is available only if the button is linked to the <span class="term">CreateByParameter</span> command.</p><p>For the <span class="term">BeforeAddRow </span>event handler of form tables, the <span class="term">Parameter </span>parameter is implemented. It is used for passing document type values during document creation.</p><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>In a dynamic list that has a document journal specified as a main table, a single <span class="term">Create</span> command that did not open submenus was available. Running this command opened a dialog box for selecting document type. The type of document being created was not passed to the <span class="term">BeforeAddRow</span> event handler of the form table linked to the dynamic list.</td><td>In document journals that contain a small number of document types, you can simplify the type selection during document creation. Easy and fast generation of individual buttons for creating documents of specific types on the form command bar.</td></tr><tr title="Версия 8.3.4" class="tag_6"><td><a name="7374d3e4-4b93-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Licenses with a limited number of simultaneous sessions are implemented for the 1C:Enterprise server. The limitations apply to the following sessions:<ul><li>Designer (except for sessions intended for infobase creation)</li><li>Thin client</li><li>Web client</li><li>Thick client</li><li>External connection</li></ul><p>Licenses can be activated for both 32-bit and 64-bit server versions. The server cluster that uses this license type can only contain a single working server.</p></td><td>This feature was not provided.<p>1C:Enterprise server did not have limitations for the number of simultaneously connected users.</p></td><td>Extended list of supported licenses for 1C:Enterprise server. New delivery option focused on using the server in small businesses or subsidiaries.</td></tr><tr title="Версия 8.3.4" class="tag_37"><td><a name="ce0f2f30-87f9-11e3-b57b-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The thin client supports the TLS protocol since 1C:Enterprise version 8.3.4.428.<p>For the thin client, the <span class="interface">/HttpsForceSSLv3</span> command-line option is implemented. It forces the system not to use the TLS protocol (if the connection is established using a web server), even if the web server supports this protocol.</p></td><td>1C:Enterprise versions 8.3.4.408 (and earlier) and 8.2.19 did not support the TLS protocol.</td><td>You can use the TLS protocol when needed.</td></tr><tr title="Версия 8.3.4" class="tag_165"><td><a name="81277de7-a467-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 165); return false;">National settings</a>.<br></td><td>The following Mongolian locales are supported:<ul><li><span class="term">mn</span> - Mongolian</li><li><span class="term">mn_Cyrl</span> - Mongolian (Cyrillic)</li><li><span class="term">mn_MN</span> - Mongolian (Mongolian)</li><li><span class="term">mn_Mong</span> - Mongolian (Traditional Mongolian)</li><li><span class="term">mn_Mong_CN</span> - Mongolian (Traditional Mongolian, PRC)</li></ul></td><td>Mongolian locales were not supported.</td><td>When 1C:Enterprise is started on a computer with Mongolian national settings, it is not shut down unexpectedly.</td></tr></table><p><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="46d1c4af-74f7-11e2-adcc-e61f135f174b">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.4" class="tag_28"><td><a name="871d3d1f-da58-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In Mozilla Firefox web browser, wordings in the web browser extension installation dialog box are clarified. The user is explicitly offered to install the extension.</td><td>The web browser extension installation dialog box offered the user to enable the extension.</td><td>For the web browser extension, the installation process is clearly differentiated from enabling the installed extension.</td></tr><tr title="Версия 8.3.4" class="tag_166"><td><a name="357d7851-e3d8-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 166); return false;">Advanced error handling</a>.<br></td><td><p>Improved dump generation algorithm in the event of unexpected shutdown. The dump is generated even if a new exception occurs while the first exception is being processed.</p></td><td>If a new exception occurred while an exception was being processed, the dump was not generated.</td><td>The frequency of cases where the cause of an unexpected shutdown cannot be found by analyzing dumps is reduced.</td></tr><tr title="Версия 8.3.4" class="tag_14"><td><a name="5b277a4f-4c46-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>In the web client, the following managed system forms are revised:<ul><li>Select font dialog box</li><li>Search and replace dialog box in spreadsheet documents</li><li>Performance indicator dialog box</li></ul><p>In all managed system forms, the <span class="interface">Help </span>button is located in the command bar, instead of the <span class="interface">More</span> (<span class="interface">All actions</span>) menu.</p></td><td>Managed system forms had different layouts.</td><td>Managed system forms are improved.</td></tr><tr title="Версия 8.3.4" class="tag_37 tag_14"><td><a name="0d97f38f-5735-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Microsoft Internet Explorer 11 web browser is now supported.</td><td>Microsoft Internet Explorer 11 web browser was not supported.</td><td>The new version of Microsoft web browser is now supported.</td></tr></table><p><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="46d1c4b0-74f7-11e2-adcc-e61f135f174b">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.4" class="tag_2"><td><a name="ed855929-dfe5-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td>Configuration change checks are optimized.<p>The execution time is reduced for the following configuration check operations:</p><ul><li>Executing the <span class="term">ConfigurationChanged()</span> method</li><li>Starting a 1C:Enterprise client</li></ul><p>Reading changes using the <span class="term">ReadChanges()</span><span class="interface"> </span>method of an exchange plan manager.</p></td><td>The performance of configuration change checks lacked efficiency.</td><td>Improved performance of configuration change checks.</td></tr><tr title="Версия 8.3.4" class="tag_28"><td><a name="cc3363ec-f394-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Improved web client performance with the <span class="interface">Taxi</span> interface when a large number of forms are open.</td><td>The web client performance with the <span class="interface">Taxi</span> interface when a large number of forms were open lacked efficiency.</td><td>Improved web client performance in the <span class="interface">Taxi</span> interface mode.</td></tr><tr title="Версия 8.3.4" class="tag_6 tag_23"><td><a name="af7f786d-f5cd-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>In the client/server mode, the impact of the numbering service on transaction start and end times is reduced, even when the numbering service is not used within the transaction.<p>In the client/server mode, the performance of the numbering service with a large number of prefixes is improved.</p></td><td>In the client/server mode, the numbering service had negative impact on transaction start and end times, even when the numbering service was not used within the transaction.<p>In the client/server mode, the performance of the numbering service with a large number of prefixes lacked efficiency.</p></td><td>Improved performance in the client/server mode when the numbering service is actively used with a large number of prefixes, e.g. in infobases with a large number of areas.</td></tr><tr title="Версия 8.3.4" class="tag_115"><td><a name="897554d8-f5d3-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Editing a large number of text lines in text boxes with the <span class="interface">MultiLine</span> property set to <span class="interface">Yes</span> was sped up for both thick and thin clients</td><td>The performance of text boxes that contained a large number of text lines was insufficient.</td><td>Reduced response time while editing large multiline texts in text boxes.</td></tr><tr title="Версия 8.3.4" class="tag_67"><td><a name="18d4011f-1c50-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>For configuration repositories that do not use the compatibility mode, performance is improved for the following action types:<ul><li>Open a configuration bound to the repository</li><li>Connect to the repository</li><li>Store objects to the repository</li><li>Update a configuration from the repository, retrieve objects, and cancel object locks</li><li>Store objects to the repository while multiple users are working simultaneously</li></ul></td><td>The specified operations lacked efficiency.</td><td>Improved performance of configuration repository operations.</td></tr><tr title="Версия 8.3.4" class="tag_28"><td><a name="e7eaffeb-1ea9-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In Microsoft Internet Explorer 8 web browser, rounded borders of controls are not displayed in order to increase performance.</td><td>In Microsoft Internet Explorer 8 browser, rounded borders of controls were displayed.</td><td>Improved performance in Microsoft Internet Explorer 8 web browser.</td></tr><tr title="Версия 8.3.4" class="tag_15"><td><a name="b5de216c-1eb0-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>Performance of Linux clients is impoved for some scenarios.</td><td>In some scenarious, Linux clients lacked efficiency.</td><td>Improved performance of Linux clients.</td></tr></table><p><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="46d1c4b1-74f7-11e2-adcc-e61f135f174b">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.4" class="compat tag_23 tag_1"><td><a name="49f935f5-d8cb-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Before restructuring an infobase, the platform checks whether user-created object attributes or tabular sections with reserved names are present in exchange plans. The list of reserved names in English includes: <span class="term">Ref</span>, <span class="term">Code</span>, <span class="term">Description</span>, <span class="term">DeletionMark</span>, <span class="term">ThisObject</span>, <span class="term">DataVersion</span>, <span class="term">AdditionalProperties</span>, <span class="term">SentNo</span>, and <span class="term">ReceivedNo</span>. The list or reserved names in Russian includes: <span class="term">Ссылка</span>, <span class="term">Код</span>, <span class="term">Наименование</span>, <span class="term">ПометкаУдаления</span>, <span class="term">ЭтотОбъект</span>, <span class="term">ВерсияДанных</span>, <span class="term">ДополнительныеСвойства</span>, <span class="term">НомерОтправленного</span>, and <span class="term">НомерПринятого</span>. If any exchange plan contains attributes or tabular sections with names listed above, the infobase cannot be restructured.<p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>Before restructuring an infobase, the platform did not check whether object attributes and tabular sections with reserved names were present in the exchange plans.</td><td>The system behaves as expected during infobase restructuring.</td></tr><tr title="Версия 8.3.4" class="compat tag_23 tag_1"><td><a name="906efe06-d8cd-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>In the <span class="term">FillCheckProcessing()</span> handler, if the <span class="term">Cancel</span> parameter is set to <span class="term">True</span>, event subscription execution is interrupted for the following objects: catalogs, documents, register record sets (including recalculations), document sequences, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks.<p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>In the <span class="term">FillCheckProcessing() </span>handler, if the <span class="term">Cancel</span> parameter was set to <span class="term">True</span>, event subscription execution was never interrupted.</td><td>The system behaves as expected.</td></tr><tr title="Версия 8.3.4" class="tag_58 tag_52"><td><a name="79f2f2a4-d97d-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td><p>In sessions that do not use separators, when data is being written or deleted, managed locks are set not only by reference and explicitly specified fields, but also by common attributes that serve as separators and include the object being written or deleted.</p><p>The common attributes that are not separators can be used in the <span class="term">DataLockFields</span> configuration object property.</p><p>The <span class="term">DataLockFields</span> list of attributes cannot contain common attributes that serve as separators in the <span class="interface">Independently and simultaneously</span> mode. You can specify such attributes as names for lock spaces of <span class="term">DataLock</span> objects. If the separator value used in the <span class="term">DataLock</span> object differs from the separator value used in the session, an exception is raised.</p><p>These changes are implemented for the following object types:</p><ul><li>Catalogs</li><li>Documents</li><li>Charts of characteristic types</li><li>Charts of accounts</li><li>Charts of calculation types</li><li>Exchange plans</li><li>Business processes</li><li>Tasks</li><li>Constants</li></ul></td><td>In sessions that did not use separators, when data was being written or deleted, managed locks were set only by reference and explicitly specified fields.<p>The common attributes that were not separators could not be used in the <span class="term">DataLockFields</span> configuration object property. Such common attributes could not be used as names for lock spaces of <span class="term">DataLock</span> objects.</p></td><td>The number of lock collisions is reduced. In sessions that do not use separators, you can modify data in any data areas within a lock space provided that the data does not belong to the area where the lock has been set. For example, a lock is set to the <span class="term">Products</span> catalog in the <span class="term">O1</span> area. You can modify data in any areas where the separator value is not equal to <span class="term">O1</span>.</td></tr><tr title="Версия 8.3.4" class="tag_26"><td><a name="9d022a4e-da3f-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When a spreadsheet document is saved to a PDF file, charts (<span class="term">Chart</span>, <span class="term">GanttChart</span>, and <span class="term">Dendrogram</span> objects) are saved in the vector format.</td><td>When a spreadsheet document was saved to a PDF file, charts were saved as bitmap images.</td><td>The resulting PDF file size is reduced. Charts are resized when the file display area is changed in the PDF file viewer program.</td></tr><tr title="Версия 8.3.4" class="tag_67"><td><a name="063a29b1-de32-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>The history of comments entered by users when they store objects to the configuration repository is implemented. The history stores last 20 comments. Users can enter comments (which are saved to the history) when they lock repository objects. Users can select comments from the history when they store objects to the repository.</td><td>Comments that users entered when they stored objects to configuration repositories were not saved to a history.</td><td>
<p>In the configuration repository, improved usability of repeated object storing operations related to a single task, such as step-by-step implementation of a single feature.</p></td></tr><tr title="Версия 8.3.4" class="compat tag_110 tag_1"><td><a name="88ed2e27-d8c0-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br></td><td>You can specify multiple roles to be used for defining access rights when the user list is empty.<p>The <span class="term">DefaultRoles</span> configuration property is implemented. The <span class="term">DefaultRole</span> property is supported for compatibility purposes. If the compatibility mode is disabled, accessing the <span class="term">DefaultRole</span> property raises an exception.</p><p>In 8.3.3 version compatibility mode, you can only specify a single role in the <span class="term">DefaultRoles</span> property.</p></td><td>Only a single role could be specified as the default one.</td><td><p>Simplified development of applied solutions that can be run with or without user list.</p></td></tr><tr title="Версия 8.3.4" class="tag_23"><td><a name="095de208-f5c8-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>For configuration objects that can contain predefined data, you can set the <span class="term">PredefinedDataName</span> property to a value of a custom type, which consists of the <span class="interface">#</span> character and the text presentation of a unique identifier.</td><td>The value of the <span class="term">PredefinedDataName</span> property could be set only in the load mode (when the <span class="term">DataExchange</span>.<span class="term">Load</span> property was set to <span class="term">True</span>).</td><td>You can load predefined data from files that have custom format.</td></tr><tr title="Версия 8.3.4" class="tag_51"><td><a name="e433885a-f5d6-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>For user action log entries that are generated as a result of user interaction with managed form fields, buttons, groups, tables, and decorations, the <span class="term">name </span>attribute is implemented. It stores the name of the form item accessed by user.<p>The user action log conversion data processor includes the option that defines how the search for form items is performed: by presentation or by name.
</p></td><td>Form item presentations were recorded to the user action log. <p>The user action log conversion data processor only supported search for form items by item presentation.</p></td><td>The automated testing is more reliable. Search for form items by name is available, which eliminates the dependence of automated tests on localization language, item presentation typos, item presentation uniqueness, and so on.</td></tr><tr title="Версия 8.3.4" class="compat tag_26 tag_1"><td><a name="a9167572-f8e7-11e2-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Spreadsheet documents are printed with the scale specified in their print options.<p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>On some printers, spreadsheet documents were printed at 200% scale.</td><td>If a spreadsheet document is printed using a scale different from 100%, the system behaves as expected.</td></tr><tr title="Версия 8.3.4" class="compat tag_43 tag_1"><td><a name="3167bb56-f9af-11e2-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In dynamic list filters, you can specify tabular section fields of objects that are used in the query that generates the dynamic list.<p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>Tabular section fields of objects could not be used in dynamic list filters.</td><td>The list of dynamic list features is extended.</td></tr><tr title="Версия 8.3.4" class="compat tag_43 tag_1"><td><a name="19d80371-fb51-11e2-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>During the retrieval of dynamic list data, dynamic list settings that are disabled by functional options are deleted.<p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>Settings disabled by functional options were not removed from dynamic list settings.</td><td>Unexpected system behavior is eliminated.</td></tr><tr title="Версия 8.3.4" class="tag_96"><td><a name="654a3b93-1bb1-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The colors of the sections panel and current section command panel in the <span class="interface">Taxi </span>interface are changed.<p>When the current section command panel orientation is vertical, its title is not displayed. The presentation of current section command panel is changed to <span class="interface">current section function panel</span>.</p></td><td>The colors of the sections panel and current section command panel in the <span class="interface">Taxi </span>interface were different.<p>If the current section command panel orientation was vertical, its title was displayed.</p></td><td>Better usability in<span class="interface">Taxi</span> interface mode.</td></tr><tr title="Версия 8.3.4" class="tag_20 tag_67"><td><a name="4779197b-1c5a-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>You can quickly view the selective change history of configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. <p>Selective history is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, objects included in exchange plans, styles, main section working areas, flowcharts, forms, help pages, predefined items, command interface fragments, and role rights.
To view the selective history, right-click anywhere in any of the repository dialog boxes or in the configuration comparison window, and then click <span class="interface">View selective history</span>.</p><p>In the <span class="interface">Filter repository versions</span> dialog box, filter by properties of selected configuration objects is added.
Viewing selective history is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.</p></td><td>This feature was not provided.
Only the full object change history was available.</td><td>Improved usability of configuration repository. Viewing the history of items that are parts of configuration objects is simplified. </td></tr><tr title="Версия 8.3.4" class="tag_151"><td><a name="a6f16b9d-1c76-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 151); return false;">Web client and web service publishing tools</a>.<br></td><td>In Designer, in the dialog box for publishing the web client and web services:<ul><li>You can manage execution of background jobs in file mode (the <span class="term">allowexecutescheduledjobs</span> attribute of the <span class="term">ws</span> tag).</li><li>You can specify whether web services are published by default (the <span class="term">pointEnableCommon</span> attribute of the <span class="term">ws</span> tag).</li></ul></td><td>Managing execution of background jobs in file mode and specifying whether web services are published by default were only available when publishing was performed using the <span class="interface">webinst</span> utility (based on a template). The publishing dialog did not provide access to managing these features.</td><td>You can specify all of the options available in the <span class="interface">default.vrd</span> file during interactive publishing.</td></tr><tr title="Версия 8.3.4" class="tag_26"><td><a name="b1388e1d-1c7a-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>You can use the <span class="term">ViewScalingMode</span> property of spreadsheet document form extension to specify how the spreadsheet document will be displayed: as in platform version 8.2 or enlarged.</td><td>This feature was not provided. Reports with large fonts looked too large in the <span class="interface">Taxi</span> interface mode.</td><td>You can scale displayed spreadsheet documents that have custom (large) fonts.</td></tr><tr title="Версия 8.3.4" class="tag_43"><td><a name="3dc1b6e7-1c7b-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In dynamic lists, presentation fields cannot be used in filters, groupings, or ordering. Searching by presentation fields is not available.</td><td>In dynamic lists, presentation fields could be used in filters, groupings, or ordering. Search by presentation fields was available.</td><td>Unexpected system behavior is eliminated.</td></tr><tr title="Версия 8.3.4" class="tag_62 tag_25 tag_45"><td><a name="f7f757a4-1c7e-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>In external data sources, you can use functions specified in them. A function can return a value, or a table, or nothing.
You can specify types of external data source tables: table or expression (this is required to describe functions that return tables).
To call an external data source function, use one of the following query language expressions:<ul><li><span class="term">ExternalDataSource.&lt; Source name&gt;.Table.&lt;Table function name&gt;(&lt;Parameter 1&gt;,...,&lt; Parameter N&gt;)</span></li><li><span class="term">ExternalDataSource.&lt;Source name&gt;.&lt;Function name&gt;&lt; Parameter 1&gt;,...,&lt; Parameter N&gt;</span></li></ul><p>You can call functions using the object model. This can be performed with either external data source managers or external data source table managers.</p><p>In the picture library, the <span class="term">ExternalDataSourceFunction</span> is implemented.</p></td><td>External data sources did not support functions.</td><td>
<p>The external data source functionality is extended.</p></td></tr><tr title="Версия 8.3.4" class="compat tag_25 tag_1"><td><a name="21b0544d-1ea7-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>If an aggregate function is used in the <span class="term">RecordsFilter </span>parameter of the <span class="term">EvalExpressionWithGroupArray</span><span class="term">()</span> or <span class="term">EvalExpressionWithGroupValueTable</span><span class="term">()</span><span class="term"> </span>functions, an error is generated.<p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>Using aggregate functions in the <span class="term">RecordsFilter </span>parameter of the <span class="term">EvalExpressionWithGroupArray</span><span class="term">()</span> and <span class="term">EvalExpressionWithGroupValueTable</span><span class="term">()</span><span class="term"> </span>functions did not generate an error.</td><td>Unexpected system behavior is eliminated.</td></tr><tr title="Версия 8.3.4" class="tag_28"><td><a name="0fa59ab3-1eac-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In Microsoft Internet Explorer 10 web browser, in managed form text boxes, the <span class="interface">Clear input</span> system button is removed.</td><td>In Microsoft Internet Explorer 10 web browser, in the managed form text box, the <span class="interface">Clear input </span>system button had the same functionality as the <span class="interface">Clear</span> button, which was added by the platform.</td><td>Eliminated web client appearance differences between Microsoft Internet Explorer 10 and other web browsers.</td></tr><tr title="Версия 8.3.4" class="tag_67"><td><a name="d6e2df23-1ed8-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>The <span class="interface">Update configuration from repository</span> command is executed without displaying a dialog box if new objects are found in the repository.<p>New objects are automatically created in the target configuration.</p></td><td>The <span class="interface">Update configuration from repository</span> command opened a dialog box if new objects were found in the repository. If a configuration was updated using Designer batch mode and new objects were found in the repository, the update was not performed.</td><td>Applied solution configurations can be updated automatically (for example, using the a batch file). You can include the update in various scheculed tasks, such as automated testing. The configuration update no longer requires interactive actions, which can pause the batch file execution.</td></tr><tr title="Версия 8.3.4" class="tag_96"><td><a name="f201356b-1f6f-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The splash screens for Designer and all types of client applications are modified: borders are used instead of shadows.</td><td>The splash screens had shadows.</td><td>Eliminated splash screen drawing issues in a number of scenarios.</td></tr><tr title="Версия 8.3.4" class="compat tag_36 tag_1"><td><a name="e9e8be3f-1f7f-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>Checks that determine whether defined type contents are valid are performed for each defined type call in the following scenarios:<ul><li>during configuration verification</li><li> before saving a configuration.</li></ul><p>The check is only performed when the <span class="interface">Compatibility mode</span> configuration property is set to <span class="interface">Version 8.3.3</span> or <span class="interface">None</span>. If the compatibility mode is set to version earlier than version 8.3.3, defined type contents are only checked for the presence of external data source functions.</p></td><td>The checks whether defined type contents were valid were only performed when the dialog box for specifying configuration object attribute type was generated. When a configuration was saved, the checks whether defined type contents were still valid were not performed for each defined type call.</td><td>Eliminated several potential issues that could occur during the development of applied solutions with defined types.</td></tr><tr title="Версия 8.3.4" class="compat tag_115 tag_1"><td><a name="19729de6-46ce-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In 8.2.16 version compatibility mode, if a text box does not have the selection list mode enabled, its drop-down lists do not contain the selection list specified in the text box properties.</td><td>In version 8.3.3, drop-down lists in text boxes always contained the choice lists specified for these text boxes.</td><td>Redesign is not required for applied solutions that run in version 8.2.16 compatibility mode.</td></tr><tr title="Версия 8.3.4" class="compat tag_12 tag_58 tag_1"><td><a name="1765e002-5d91-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td><p>The standard <span class="interface">Delete marked objects</span> data processor attempts to set the exclusive mode for object deletion if the configuration compatibility mode is set to <span class="interface">Version 8.3.3 </span>or later (including the <span class="interface">None</span> value of the Compatibility mode property).</p><p>If the configuration has <span class="interface">Version 8.3.2</span> or earlier compatibility mode, the exclusive mode is only set for sessions that do not use separators or in configurations that are not separated. </p></td><td><p>The standard <span class="interface">Delete marked objects</span> data processor attempted to set the exclusive mode for object deletion only if deletion was performed either in a session that did not use separators or in a configuration that was not separated. The compatibility mode did not affect the criteria for setting exclusive mode.</p></td><td>You can delete marked objects in sessions that use separators.</td></tr><tr title="Версия 8.3.4" class="tag_23"><td><a name="a1e98da2-aa88-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>An automatically assigned object number is reused if the transaction where the object was written is cancelled, regardless of the value of the <span class="interface">Objects Autonumbering Mode</span> configuration property.</td><td>If the <span class="interface">Objects Autonumbering Mode</span> configuration property was set to <span class="interface">Do not Release Automatically</span>, an object number was not reused when the transaction where the object was written was canceled.</td><td>Eliminated unexpected system behavior.</td></tr><tr title="Версия 8.3.4" class="tag_56"><td><a name="7749aa62-ceaf-11e3-9984-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>When data is deserialized from XML- or XDTO-serialized files, the <span class="term">Predefined</span> items are ignored for tabular sections of charts of accounts and charts of calculation types. If such items are found, no errors occur and data is deserialized successfully.</td><td>During the attempt to deserialize items of a chart of accounts or a chart of calculation types, having the <span class="term">Predefined</span> item in a tabular section resulted in an exception and the deserialization could not be performed.</td><td>You can load data serialized in later versions of 1C:Enterprise (version 8.3.5 and later).</td></tr><tr title="Версия 8.3.4" class="tag_158"><td><a name="6f3b2b76-0121-11e4-98ab-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 158); return false;">Third-party software</a>.<br></td><td>The OpenSSL library is updated to version 1.0.0m.</td><td>OpenSSL version 1.0.0l was used.</td><td>Eliminated OpenSSL security issues.</td></tr></table><p><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="46d1c4b2-74f7-11e2-adcc-e61f135f174b">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.4" class="tag_16"><td><a name="a86ccdc3-de2b-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td><p>For information registers with <span class="interface">Enable totals for retieving slice first</span> or <span class="interface">Enable totals for retrieving slice last </span>property enabled, the <span class="term">Active</span> and <span class="term">LineNumber</span> fields are removed from the list of fields of information register slice first/last virtual tables.</p><p>If <span class="interface">Enable totals for retieving slice first</span> or <span class="interface">Enable totals for retrieving slice last </span>property is disabled, the <span class="term">Active</span> and <span class="term">LineNumber</span> fields are included in the slice first/last virtual tables. </p><p> </p></td><td>The <span class="term">Active</span> and <span class="term">LineNumber</span> fields were included in the list of fields of information register slice first/last virtual tables.</td><td>The system behaves as expected. In managed forms, the form items linked to the <span class="term">Active</span> and <span class="term">LineNumber</span> fields are removed automatically.</td></tr><tr title="Версия 8.3.4" class="tag_52"><td><a name="a4d46c75-de35-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>Managed transaction locks (the <span class="term">DataLockFields</span> property) cannot be set by attributes of objects of the following types: string of unlimited length, value storage, characteristic value type, and complex types that include these types.<p>The check is performed during the configuration check, and an error message is displayed if any field does not comply with the limitations.</p></td><td>It was recommended that you did not use attributes of the following types in managed locks: string of unlimited length, value storage, characteristic value type, and composite types that included these types.<p>During the configuration check, the check for managed locks by attributes of these types was not performed.</p></td><td>The configuration performance is optimized.<p>Improved quality control during configuration development.</p></td></tr><tr title="Версия 8.3.4" class="compat tag_110 tag_1"><td><a name="eb5acaf8-f5c8-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br></td><td>The <span class="term">IsInRole()</span> function raises an exception in the following cases:<ul><li>A value that is not a string and not a <span class="term">Role</span> configuration object is passed as a parameter.</li><li>A name of a role that does not exist is passed.</li></ul><p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>The <span class="term">IsInRole()</span> function did not check the parameter value and returned <span class="term">True</span> even when the passed role was missing from the configuration.</td><td>The system behaves as expected. </td></tr><tr title="Версия 8.3.4" class="compat tag_25 tag_1"><td><a name="7569fbaf-f5cb-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td><p>When data composition is performed from 1C:Enterprise script, the platform checks whether the privileged mode is enabled while getting the list of available fields.</p><p>This change is not implemented in 8.3.3 compatibility mode.</p><p> </p></td><td>When data composition was performed from 1C:Enterprise script, the platform did not check whether privileged mode was enabled.</td><td>If privileged mode is enabled, data composition can include fields that users cannot access.</td></tr><tr title="Версия 8.3.4" class="compat tag_155 tag_1"><td><a name="cd1b789d-fb4e-11e2-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 155); return false;">Web services</a>.<br></td><td>The values of the <span class="term">WSParameterDirection</span> system enumeration are corrected:<ul><li>The <span class="term">InOut</span> item represents the <span class="term">InOut</span> value.</li><li>The <span class="term">Out</span> item represents the <span class="term">Out</span> value.</li></ul><p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>The values of the <span class="term">WSParameterDirection</span> system enumeration represented the following:<ul><li>The <span class="term">InOut</span> item represented the <span class="term">Out</span> value.</li><li>The <span class="term">Out</span> item represented the <span class="term">InOut</span> value.</li></ul><p>
</p></td><td>Unexpected system behavior is eliminated.</td></tr><tr title="Версия 8.3.4" class="compat tag_105 tag_1"><td><a name="59c200c2-fb53-11e2-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>
<p>A flag that specifies whether predefined data should be updated for the entire infobase is now available. It can be set both in 1C:Enterprise script and in the command line. In the 1C:Enterprise mode, the predefined data update procedure checks the flag that is set for the entire infobase (in addition to checking the flags set for individual configuration objects, checking the flags set for infobase data, and checking the infobase type: master/not distributed infobase or subordinate infobase).</p><p>The global context methods <span class="term">SetInfoBasePredefinedDataUpdate</span><span class="term">()</span> and <span class="term">G</span><span class="term">etInfoBasePredefinedDataUpdate</span><span class="term">()</span> are implemented.</p><p>The command-line option <span class="term">/SetPredefinedDataUpdate</span> is implemented for Designer batch mode.</p><p>This change is not implemented in 8.3.3 compatibility mode.</p></td><td>The check whether predefined data should be updated was based on infobase data and metadata flags and on the infobase type.</td><td>You have the option to set predefined data update flags easily for infobases that are disconnected from distributed systems for maintenance. Also, the following scenario is now supported: exchange in a nondistributed infobase between two similar applications where predefined data is set in one of the applications and should be replicated to the other one during the exchange.</td></tr><tr title="Версия 8.3.4" class="compat tag_23 tag_1"><td><a name="e26b2668-058a-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>In the thick and thin clients, the <span class="term">WriteParameters </span>parameter is implemented for the <span class="term">AfterWrite</span> handler of managed form extension handlers for constants, information register records, and register record sets.<p>In version 8.3.3 or earlier compatibility mode, the parameter always has the <span class="term">Undefined</span> value. </p><p>The description of the <span class="term">WriteParameters </span>parameter is added to the <span class="term">AfterWrite</span> Syntax Assistant entry.</p></td><td>The <span class="term">AfterWrite</span> handler of managed form extension handlers for constants, information register records, and register record sets lacked the <span class="term">WriteParameters </span>parameter.<p>The description of the <span class="term">WriteParameters </span>parameter was missing from the <span class="term">AfterWrite</span> Syntax Assistant entry.</p></td><td>Unexpected system behavior is corrected.</td></tr><tr title="Версия 8.3.4" class="tag_43 tag_104"><td><a name="ae6e77a9-2458-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>The main managed form attribute of <span class="term">Object</span>(<span class="term">CatalogObject</span>, <span class="term">DocumentObject</span>, and so on) type is disabled if a functional option disables the corresponding configuration object. The main managed form attribute of <span class="term">DynamicList</span> type is disabled if a functional option disables a configuration object that is used a main table for the dynamic list.<p>In both cases, only functional options without parameters are taken into account.</p></td><td>In 1C:Enterprise version 8.2, the main form attribute of <span class="term">Object</span><span class="term"> </span>type was not disabled even if any functional option disabled the corresponding configuration object.<p>In 1C:Enterprise version 8.3, the main form attribute of <span class="term">Object</span> type was disabled if a functional option disabled the corresponding configuration object. All functional options were taken into account.</p><p>In the previous 1C:Enterpise versions, the main form attribute of <span class="term">Dynam</span><span class="term">icList</span> type was disabled if a functional option disabled the configuration object that was used as a main table of the dynamic list. All functional options were taken into account.</p></td><td>The system behaves as expected. In particular, the following issue is eliminated:<ul><li>Editing a form changes a functional option parameter (directly or indirectly).</li><li>The new parameter value causes the functional option to disable the configuration object that is the main form attribute.</li><li>The disabled configuration object clears the entire object form.</li></ul></td></tr><tr title="Версия 8.3.4" class="tag_115"><td><a name="89753049-3b01-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If the interface compatibility mode is set to <span class="interface">Version 8.2</span>, text boxes have the following specifics:<ul><li>When a text box is activated, a drop-down list is not opened.</li><li>For the <span class="term">DropListButton</span> property of the managed form field extension for a text box, the <span class="term">Auto</span> value is interpreted as <span class="term">False</span>.</li><li>For the <span class="term">ChoiceButtonRepresentation</span> property of the managed form field extension for a text box, the <span class="term">Auto</span> value is interpreted as <span class="term">ShowInInputField</span>.</li><li>For the <span class="term">ChoiceButton</span> property of the managed form field extension for a text box, the <span class="term">Auto</span> value is interpreted as in 1C:Enterprise version 8.3.2.</li><li>Clicking the <span class="interface">Down Arrow</span> button opens a choice form, not a drop-down list.</li></ul></td><td>In <span class="interface">Version 8.2</span> interface compatibily mode,the text box behavior was identical to the text box behavior in <span class="interface">Taxi</span> interface compatibility mode.</td><td>For users who migrated to 1C:Enterprise version 8.3 while keeping <span class="interface">Version 8.2</span> interface compatibility mode, the system behavior is similar to previous versions.</td></tr><tr title="Версия 8.3.4" class="tag_29"><td><a name="0bd1b456-6944-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft Windows 2000 operating system is no longer supported.</td><td>Microsoft Windows 2000 operating system was supported.</td><td>An outdated operating system is no longer supported.</td></tr><tr title="Версия 8.3.4" class="tag_14"><td><a name="f73d6d6f-9943-11e3-8f48-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>Client computers that run operating systems of Windows family require Microsoft Internet Explorer web browser version 7.0. On computers with Microsoft Internet Explorer version 6.0 or earlier, users of thick and thin clients of version 8.3.4 or later might experience various issues.</td><td>Client computers that run operating systems of Windows family required Microsoft Internet Explorer web browser version 6.0 or later.</td><td>The out-of-date web browser is no longer supported. The platform features that use Microsoft Internet Explorer now require Microsoft Internet Explorer version specified in the platform system requirements.</td></tr></table><p><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="46d1c4b3-74f7-11e2-adcc-e61f135f174b">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.4" class="tag_0"><td><a name="811cdc00-1c48-11e3-9afe-e61f135f174b"></a>A property of managed form extension for text fields. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">ListSelWidth</span></li></ul></td><td><ul><li><span class="term">DropListWidth</span></li></ul></td></tr><tr title="Версия 8.3.4" class="tag_0"><td><a name="c9d3dabf-1c7b-11e3-9afe-e61f135f174b"></a>The English name for the <span class="term">Choose()</span> method of the <span class="term">QueryResult </span>and <span class="term">QueryResultSelection</span> objects is changed. The former name is supported for compatibility purposes.</td><td><ul><li><span class="term">Choose()</span></li></ul></td><td><ul><li><span class="term">Select()</span></li></ul></td></tr><tr title="Версия 8.3.4" class="compat tag_0 tag_1"><td><a name="4c0c928d-1ea6-11e3-9afe-e61f135f174b"></a>The button linked to the <span class="interface">Cancel </span>command in the managed report form extension, report settings form, and report variant form.<p>The former name is used in version 8.3.3 compatibility mode.</p></td><td><ul><li><span class="term">FormCancel</span></li></ul></td><td><ul><li><span class="term">FormCancelEdit</span></li></ul></td></tr></table><p><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="c6e539b1-4128-11e3-9afe-e61f135f174b">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.4" class="tag_29"><td><a name="1d2f05dc-42d8-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Mobile platform now supports x86 Intel CPU-based devices that run Android OS. The mobile platform for x86 architecture is provided in a separate file.<p>The mobile platform distribution kit contains the following files:</p><ul><li><span class="interface">1cem-arm.apk</span>, the developer's mobile platform for ARM architecture</li><li><span class="interface">cem-x86.apk</span>, the developer's mobile platform for x86 architecture</li><li><span class="interface">prjandroid-arm.zip</span>, the mobile platform for building mobile applications (for ARM architecture)</li><li><span class="interface">prjandroid-x86.zip</span>, the mobile platform for building mobile applications (for x86 architecture)</li></ul></td><td>The mobile platform did not support x86 Intel CPU-based architecture.</td><td>More devices are now supported.</td></tr><tr title="Версия 8.3.4" class="tag_20"><td><a name="30ee9f99-6945-11e3-b57a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Mobile application builder is a new applied solution intended for building mobile applications. It has the following features:<ul><li>Storing mobile configurations</li><li>Storing mobile platforms (starting from version 8.3.4)</li><li>Storing graphic assets</li><li>Building mobile applications</li><li>Storing the built mobile applications</li></ul><p>Mobile application builder can build mobile applications for Android x86 operating systems.</p><p>It can also perform full building of mobile applications for iOS using a Mac computer with Xcode installed.</p><p>The configuration is delivered together with the mobile platform distribution kit. The data processor used for building mobile applications is removed from the mobile platform distribution kit.</p><p>Building can be performed using any Android SDK version.</p></td><td>A data processor was used for building mobile applications. It was included into the mobile platform distribution kit.</td><td>Simplified building of mobile applications. Building mobile applications for iOS no longer requires additional steps.</td></tr><tr title="Версия 8.3.4" class="tag_29"><td><a name="138250d3-286b-11e4-903a-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Android version 2.2 is no longer supported.</td><td>Android version 2.2 was supported.</td><td>Support of the obsolete operating system version has ended.</td></tr></table><p><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="46d1c4b4-74f7-11e2-adcc-e61f135f174b">Transition from the previous version to the version 8.3.4</a></h2><ul><li title="Версия 8.3.4" class="tag_0"><a name="46d1c4b5-74f7-11e2-adcc-e61f135f174b"></a>Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.4.
</li><li title="Версия 8.3.4" class="tag_0"><a name="46d1c4b6-74f7-11e2-adcc-e61f135f174b"></a>Some features that are added in version 8.3.4 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.4" class="tag_0"><a name="33192ee7-41f7-11e3-9afe-e61f135f174b"></a>During the transition to version 8.3.4, if your infobase runs in the file mode, we recommend that you perform infobase verification and repair with the <span class="interface">Compressing Infobase tables</span> check box selected.</li></ul><p><a href="#46d1c4ad-74f7-11e2-adcc-e61f135f174b"><small>Table of contents</small></a></p><h1><a name="4288e495-1835-11e2-b237-e61f135f174b">Version 8.3.3</a></h1><p title="Версия 8.3.3" class="tag_0"><a name="4288e49e-1835-11e2-b237-e61f135f174b"></a>Version 8.3.3 includes known bug fixes and functionality modifications.
</p><hr></hr><ul><li><a href="#4288e496-1835-11e2-b237-e61f135f174b">New functionality and changes</a></li><li><a href="#4288e497-1835-11e2-b237-e61f135f174b">New functionality and changes in the 1C:Enterprise mode</a></li><li><a href="#4288e498-1835-11e2-b237-e61f135f174b">Optimization</a></li><li><a href="#4288e499-1835-11e2-b237-e61f135f174b">Changes that affect system behavior</a></li><li><a href="#4288e49a-1835-11e2-b237-e61f135f174b">Changes that require modification of configuration and administrative settings</a></li><li><a href="#4288e49b-1835-11e2-b237-e61f135f174b">Renamed objects</a></li><li><a href="#fcbb6956-8af0-11e2-adcc-e61f135f174b">Mobile platform</a></li><li><a href="#e55bc2bb-c767-11e2-adcc-e61f135f174b">Transition from the version 8.2 to the version 8.3.3</a></li><li><a href="#4288e49c-1835-11e2-b237-e61f135f174b">Transition from the previous version to version 8.3.3</a></li></ul><h2><a name="4288e496-1835-11e2-b237-e61f135f174b">New functionality and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.3" class="compat tag_2 tag_1"><td><a name="4288e49f-1835-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.3.2</span> is added to the list of available values of the <span class="interface">Compatibility mode</span> property.
</td><td>Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, and 8.3.1.
</td><td>In version 8.3.3 you can run configurations created in version 8.3.2 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.3 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.2 for working with the infobase even after the transition to version 8.3.3. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
</td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="9e218134-1f6f-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>You can specify settings for vertical scaling of form elements, namely the minimum element height, at the development stage in Designer using the new <span class="term">VerticalScroll</span> property. <p>If a form has a vertical scroll bar and the command bar is located above or below all form elements and occupies the entire form width, the area being scrolled does not include the command bar.</p></td><td>Managed form elements could be reduced to the default minimum height by reducing the form height. If a managed form had a vertical scroll bar, the area being scrolled included all form elements.</td><td>Elements of managed forms with vertical scroll bars cannot be compressed below the minimum height guaranteeing comfortable work. The command bar with important form commands, such as <span class="interface">Write and close</span>, is always available because it is not included in the area being scrolled.</td></tr><tr title="Версия 8.3.3" class="tag_115 tag_28"><td><a name="5cb3ac1d-71d1-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client, if the <span class="term">VerticalScroll</span> property of the managed form is set to <span class="term">UseIfNecessary</span>, reducing the vertical form size never leads to reducing the vertical size of the form elements to the point where they can no longer be used.</td><td>In the web client, reducing the vertical form size could lead to reducing the vertical size of the form elements to the point where they could no longer be used.</td><td>Eliminated situations when reducing the vertical form size led to reducing the vertical size of the form elements to the point where they could no longer be used.</td></tr><tr title="Версия 8.3.3" class="tag_20"><td><a name="e869236a-2d9a-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the built-in script editor, you can group an arbitrary number of lines in the same way as they are grouped in some syntax units (conditions or cycles). <p><span class="term">#Region</span> and <span class="term">#EndRegion</span> preprocessor instructions are implemented. These instructions are ignored during script execution.
A template for creating a script fragment with line grouping is added to the set of standard templates.</p></td><td>This feature was not provided. Only a few script syntax units allowed line grouping.</td><td>Improved usability for working with source text. You can group parts of source text in a logical way and hide text that is not used at the moment. </td></tr><tr title="Версия 8.3.3" class="tag_62"><td><a name="46103d15-2fc0-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>Support of the following OLAP sources is added to the external data sources mechanism:<ul><li>Microsoft SQL Server Analysis Services</li><li>IBM InfoSphere Warehouse</li><li>Oracle Essbase</li></ul><p>Requests to OLAP sources and errors that occur during the request execution are recorded to the <span class="term">EDS</span> event of the technological log.</p><p>The following pictures are added to the picture library: <span class="term">ExternalDataSourceCube</span>, <span class="term">ExternalDataSourceCubeDimensionTableObject</span>.</p></td><td>External data sources provided access to relational tables only.</td><td>Both relational data and OLAP sources can be used when creating reports based on data from external systems (external data sources).</td></tr><tr title="Версия 8.3.3" class="tag_96"><td><a name="3ca8140e-324f-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>You can get the resolution and DPI of monitors connected to a computer in the client application (thin client, thick client, web client) and at the server. For the external connection, the <span class="term">GetClientDisplayInformations</span><span class="term">()</span> method returns <span class="term">UNDEFINED</span>.<p>The information on characteristic of client computer monitors is passed through at the session start and when the <span class="term">RefreshInterface</span><span class="term">()</span> method is called.</p></td><td>You could get the information on monitors connected to a computer only on the mobile platform.</td><td>You can determine the number of monitors connected to the computer where the application is being executed, as well as their characteristics.</td></tr><tr title="Версия 8.3.3" class="compat tag_25 tag_1"><td><a name="01ce406a-3893-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>For conditional appearance elements, you can specify areas where the given conditional appearance element will be used.<p>This feature is not used in dynamic lists.</p><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>The conditional appearance was applied both to data area and area header, without further customization</td><td>Extended formatting capabilities for complex reports.</td></tr><tr title="Версия 8.3.3" class="tag_151"><td><a name="347747e7-3eb7-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 151); return false;">Web client and web service publishing tools</a>.<br></td><td>Infobases, web services, and mobile applications can be published from Designer that is running on Linux.
Publishing can only be performed to Apache web servers and only if Designer is running under <span class="interface">root</span> account.</td><td>Publishing of infobases and web services on Linux was possible only using the <span class="interface">webinst</span> utility. Publishing mobile applications was not available on Linux.</td><td>Eliminated some Designer limitations on Linux.</td></tr><tr title="Версия 8.3.3" class="tag_15"><td><a name="88c3d29b-4b66-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>You can create distribution kits in the Linux version of Designer. The platform distribution files now include an installation program that installs templates and updates for applied solutions that run on Linux. The installation program supports both 32-bit and 64-bit Linux versions. The installation program shares the list of Linux operating systems with the client application.</td><td>Creation of distribution kits was not available on Linux.</td><td>You can install templates and update applied solutions on Linux operating systems.</td></tr><tr title="Версия 8.3.3" class="tag_167"><td><a name="2e780bbd-42cf-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 167); return false;">Autorun</a>.<br></td><td>The <span class="interface">Autorun</span> application is capable of running on Linux. The application supports both 32-bit and 64-bit Linux versions. The application shares the list of Linux operating systems with the client applications.
The following properties are added to the <span class="term">Element</span> section of the <span class="interface">autorun.lst</span> configuration file: <span class="term">CommandWindows</span>, <span class="term">CommandLinux</span>, and <span class="term">RunAsRoot</span>. The properties specify how a given item is executed in various operating systems.</td><td>The <span class="interface">Autorun</span> application was not available for Linux systems.
The <span class="interface">autorun.lst</span> configuration file did not include <span class="term">CommandWindows</span>, <span class="term">CommandLinux</span>, and <span class="term">RunAsRoot</span> properties.</td><td>You can create applied solution distribution kits that include the <span class="interface">Autorun</span> application and are delivered on removable media that can be used to install the solution on both Windows and Linux operating systems.</td></tr><tr title="Версия 8.3.3" class="compat tag_23 tag_115 tag_1"><td><a name="df40cdd4-437e-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Objects of reference types can be created while data is being entered in a form. A new property of configuration objects and form elements is implemented for this feature. The form element property manages the visibility of the command that creates a choice list element. The feature is implemented for catalogs, documents, charts of characteristic types, charts of accounts, charts of calculation types, business processes, tasks, and exchange plans.
The command for creating a choice list element is not available in version 8.3.2 compatibility mode.</td><td>This feature was not provided.
Users had the option to open the choice form and create an object there, and then select the created object.</td><td>Improved usability in cases when object creation is required while data is being entered.</td></tr><tr title="Версия 8.3.3" class="tag_115 tag_20"><td><a name="48d35805-48ed-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>In the managed form editor, the list of elements available for adding to the form now includes a usual group without a title.</td><td>In the managed form editor, in order to create a usual group without a title, a developer had to add a usual group and then change the properties that define whether the title is displayed.</td><td>Improved usability of editing managed forms when groups are used for defining element positions on the form.</td></tr><tr title="Версия 8.3.3" class="tag_115 tag_20"><td><a name="84c7ede3-48ef-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During the generation of event handlers for client form elements and commands, you can specify which procedures will be generated:<ul><li>A client handler only</li><li>A client handler and a server procedure (to be executed outside of a context) that is called from the handler</li><li>A client handler and a context server procedure that is called from the handler</li></ul><p>A context server procedure cannot be generated for those client handlers where calling context server procedures is not recommended.</p></td><td>When a client handler was generated, this only included the generation of the handler itself. The associated procedures were not generated.</td><td>Simplified development of forms where actions that are called at client are executed at server. Developers no longer have to create the server method manually and then add the method call to the client handler body.</td></tr><tr title="Версия 8.3.3" class="compat tag_67 tag_1"><td><a name="d7c9c6f9-48f4-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>The data storage format of the configuration repository is modified. Repository objects are stored in the file system. The <span class="interface">1cv8ddb.1CD</span> file stores information on changed objects.
The compatibility mode is implemented for the configuration repository. The new storage format is available only if the compatibility mode is disabled.
Optimization of configuration repository data is introduced. The optimization procedure is available both from the repository administration window and by using the <span class="term">ConfigurationRepositoryOptimizeData </span>command-line option when Designer is started in batch mode.
The format of configuration repository files is not intended for reading or writing by any tools other than 1C:Enterprise.</td><td>All configuration repository data was stored in the <span class="interface">1cv8ddb.1CD</span> file. Optimization of the configuration repository was not available.</td><td>Significantly increased number of changes (versions) that can be stored in the configuration repository.</td></tr><tr title="Версия 8.3.3" class="tag_20 tag_14"><td><a name="20959b03-4918-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The infobase selection dialog box and the two authentication dialog boxes (for access to infobases and configuration repositories) that are displayed during the start of a client application or Designer can be disabled.<p>To disable them, use the <span class="term">DisableStartupDialogs</span> command-line option for the <span class="interface">1cv8.exe/1cv8</span> file.</p><p>If the command-line that starts a client application or Designer contains errors that led to displaying these dialog boxes in earlier platform versions, the dialog boxes are not displayed; diagnostic messages are generated instead. These messages are recorded to the file that stores service messages (the <span class="term">Out</span> command-line option).</p></td><td>During the start of client application or Designer in the batch mode, provided that infobase parameters or authentication parameters contained any errors, modal dialog boxes that prompted users to enter the correct parameters were displayed. This paused the execution of the entire batch.</td><td>When Designer is started in batch mode - especially if Designer is started from another application or service - it is now possible to avoid the hard-to-detect situations when Designer attempts to create a selection dialog box for parameters that cannot be specified interactively, and therefore stops responding. </td></tr><tr title="Версия 8.3.3" class="tag_84"><td><a name="87a5af89-49ad-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 84); return false;">Localization</a>.<br></td><td>The <span class="term">NumberInWords()</span> and <span class="term">PeriodPresentation()</span> global context methods support French language. The language code is as follows: <span class="term">fr</span>, <span class="term">fr_CA</span>. Values of the <span class="term">NumerationItemOptions</span> parameter of the <span class="term">NumberInWords()</span> method are specified similar to English, Finnish, and Kazakh languages.</td><td>The <span class="term">NumberInWords()</span> and <span class="term">PeriodPresentation()</span> global context methods did not support French language.</td><td>Improved presentation of information for French-speaking users.</td></tr><tr title="Версия 8.3.3" class="tag_115 tag_21"><td><a name="deedeca0-616c-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>For the <span class="term">FullTextSearchList</span> object, you can disable the search by presentations of configuration objects. Use the <span class="term">MetadataUse</span> property of this object to enable or disable this feature.</td><td>The search by presentations of configuration objects could not be disabled.</td><td>You can search by data only, without seaching by presentations of configuration objects at the same time.</td></tr><tr title="Версия 8.3.3" class="tag_69"><td><a name="f5d46418-4b5b-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>For the <span class="term">Array</span>, <span class="term">Structure</span>, and <span class="term">Map</span> collections implemented constructors that create these objects based on the corresponding fixed collections (<span class="term">FixedArray</span>, <span class="term">FixedStructure</span>, and <span class="term">FixedMap</span>). Recursive conversion is performed for arrays—a fixed array item that is a fixed array itself is recorded to a regular array.</td><td>Fixed collections could be converted to their regular analogs only by using program loops.</td><td>Simplified editing of values stored in fixed collections.</td></tr><tr title="Версия 8.3.3" class="tag_58"><td><a name="152806f8-4e68-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>Exclusive access can be set for a data area. Exclusive access is not compatible with any data locks set by other sessions in this area. Exclusive access to a data area must be explicitly set or removed using the <span class="term">SetExclusiveMode()</span> method. When a background job is started from a session that set exclusive access to a data area, the background job obtains exclusive access and the parent session loses exclusive access until the parent session is completed. At this time, changing data from the parent session is not available. Exclusive access is returned to the parent session after the background job completion. When a session switches to a different area, this does not affect the list of areas where the session has exclusive access.<p>Exclusive access to an area prohibits the following actions:</p><ul><li>Creation of new sessions with the same set of separators.</li><li>Access to the area-contained data from enveloping areas.</li><li>Setting exclusive access in enveloping areas.</li></ul><p>Setting shared managed locks for an area is ignored if exclusive access is set for this area.</p></td><td>Exclusive access to a data area could not be set. Instead, you only could set an exclusive managed transaction lock to all area-contained data.</td><td>You can perform consistent changes of the data area even if they cannot be included into a transaction.</td></tr><tr title="Версия 8.3.3" class="tag_36"><td><a name="c32cb783-4e7b-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>The <span class="term">DataHashing</span> object can calculate the <b>SHA1</b> and <b>SHA256</b> hash functions.</td><td>The <span class="term">DataHashing</span> objects could calculate only the <b>MD5</b> and <b>CRC32</b> hash functions.</td><td>The list of supported hash functions is extended.</td></tr><tr title="Версия 8.3.3" class="tag_23"><td><a name="b5c514ac-4f23-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>You can create defined types. A defined type consists of one or several allowed types, and it has a unique name. Defined data types can be used as types of configuration object attributes. Defined types cannot be included in complex types and cannot be used as data types for charts of characteristic types.
If you want to run the applied solution on a previous platform version, you have to remove all defined types from the configuration.</td><td>This feature was not provided.</td><td>You can create a type that can be used for defining types of specific attributes. For example, in a universal multipurpose configuration fragment, you can describe attributes that refer to data that will be defined when the fragment is included into a specific configuration.</td></tr><tr title="Версия 8.3.3" class="tag_144"><td><a name="96fd150a-4f30-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 144); return false;">Mobile application</a>.<br></td><td>You can choose a ZIP archive containing multiple pictures of different sizes, instead of a single picture, for the application. This option is targeted for mobile applications that can be used in devices with different screen resolutions. The following mobile device screen types are supported:<ul><li>devices with screen resolution below 140 DPI</li><li>devices with screen resolution from 140 to 180 DPI and Apple devices with standard screens</li><li>devices with screen resolution from 180 to 270 DPI</li><li>devices with screen resolution over 270 DPI and Apple devices with Retina screens</li></ul><p>Each picture corresponds to specific screen settings of the target device. It is recommended that you use the PNG format for the archived pictures and you create the archive without compression.
For the <span class="term">Picture</span> object, the <span class="term">ChoiceSet</span> property is implemented.</p></td><td>This feature was not provided. On the mobile platform, the developer had to specify multiple picture versions for various screen resolutions using 1C:Enterprise script.</td><td>Simplified process of creating applications intended for running on both PC and mobile devices. The developer only has to provide pictures for different display resolutions, and they do not have to write the script for resizing the pictures before displaying them in the 1C:Enterprise mode.</td></tr><tr title="Версия 8.3.3" class="compat tag_42 tag_82 tag_1"><td><a name="a233f9ba-4f3d-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>In accumulation and accounting registers, the interval for storing totals by periods can be limited. You can specify both the lower and the upper boundary of the interval. Totals within this interval can be recalculated automatically when totals outside of the interval are changed. Totals by periods are not stored outside of the interval. They are calculated by register record tables when needed.
For accumulation register managers and accounting register managers, the following methods are implemented: <span class="term">SetMinTotalsPeriod()</span>, <span class="term">GetMinTotalsPeriod()</span>, and <span class="term">SetMinAndMaxTotalsPeriods()</span>.
The totals storage limits are taken into account when the chart of accounts is changed, when register records are generated, when totals are recalculated, and when balance is obtained by balance accumulation and accounting registers.
When totals are enabled, periods are only recalculated if they contain actual changes.
This change is not implemented in 8.3.2 compatibility mode.</td><td>Totals were stored by all periods later than the period of calculated totals for the register. When register records were changed for a prior period, all totals were recalculated for periods later than the modified date.
When using totals was turned on, all register totals were also recalculated.</td><td>This change reduces database size and optimizes performance of administrative operations.
This decreases the system load for databases that store data for long periods (several years), and where changes in prior periods are performed on regular basis but regular data retrieval (using totals) is performed within a limited time interval from the current date. </td></tr><tr title="Версия 8.3.3" class="tag_11"><td><a name="44b778ef-4f69-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>The add-in creation functionality includes the option to display interactive messages to users and the option to store values between sessions in a local web browser cache.<p>The add-in development technology documentation (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">http://1c-dn.com/library/add_in_creation_technology/</a>) is updated by enhancing examples and adding new versions of web browser adapters.</p></td><td>The add-in creation functionality did not include the option to display interactive messages to users or the option to store values between sessions in a local web browser cache.</td><td>When a web browser add-in attempts to access local resources, warnings can be displayed. They are similar to warnings available in the built-in platform features.</td></tr><tr title="Версия 8.3.3" class="tag_28 tag_26 tag_168"><td><a name="890e1cef-4fec-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 168); return false;">Printing documents</a>.<br></td><td>Documents intended for printing can be combined into batches. To print the entire batch, you only have to start printing once.
You can specify printing options for batches. Batches can be nested. A batch can be written to a single PDF file, which simplifies printing in the web client.
The <span class="term">RepresentableDocumentBatch</span> object is implemented.</td><td>Batch printing was not available in the web client. To print a set of documents, the user had to click the Print button for each single document.</td><td>Improved usability of printing muptiple documents (with different printing options) in the web client. To print a batch of documents, the user has to start printing once (regardless of the number or documents in the batch), and the printing options (including page orientation and the number of copies) will be set for each individual document.</td></tr><tr title="Версия 8.3.3" class="tag_6"><td><a name="c8425b88-5b0e-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>In the client/server mode, security profiles are implemented for the purpose of managing applied solution access to the following external resources on 1C:Enterprise server: file system, COM objects, add-ins, operating system applications, Internet resources, privileged mode, external reports and data processors, and global context methods <span class="term">Execute</span><span class="term">()</span> and <span class="term">Eval</span><span class="term">()</span>. A security profile can be assigned to each infobase; a security profile can also be assigned to the source code that is executed in the safe mode.<p>For the purposes of software cluster administration:</p><ul><li><span class="term">ISecurityProfile </span>object is implemented.</li><li><span class="term">ISecurityProfileVirtualDirectory </span>object is implemented.</li><li><span class="term">ISecurityProfileCOMClass </span>object is implemented.</li><li><span class="term">ISecurityProfileAddIn</span> object is implemented.</li><li><span class="term">ISecurityProfileExternalModule</span> object is implemented.</li><li><span class="term">ISecurityProfileApplication</span> object is implemented.</li><li><span class="term">ISecurityProfileInternetResource</span> object is implemented.</li><li>For the <span class="term">IServerAgentConnection</span> object, the following methods are implemented: <span class="term">GetSecurityProfiles</span><span class="term">()</span>, <span class="term">RegSecurityProfile()</span>, <span class="term">UregSecurityProfile()</span>, <span class="term">CreateSecurityProfile()</span>, <span class="term">GetSecurityProfileVirtualDirectories()</span>, <span class="term">RegSecurityProfileVirtualDirectory()</span>, <span class="term">UnregSecurityProfileVirtualDirectory()</span>, <span class="term">CreateSecurityProfileVirtualDirectory()</span>, <span class="term">GetSecurityProfileCOMClasses()</span>, <span class="term">RegSecurityProfileCOMClass()</span>, <span class="term">UnregSecurityProfileCOMClass()</span>, <span class="term">CreateSecurityProfileCOMClass()</span>, <span class="term">GetSecurityProfileAddIns()</span>, <span class="term">RegSecurityProfileAddIn()</span>, <span class="term">UnregSecurityProfileAddIn()</span>,<span class="term">CreateSecurityProfileAddIn()</span>, <span class="term">GetSecurityProfileUnSafeExternalModules()</span>, <span class="term">RegSecurityProfileUnSafeExternalModule()</span>, <span class="term">UnregSecurityProfileUnSafeExternalModule()</span>, <span class="term">CreateSecurityProfileUnSafeExternalModule()</span>, <span class="term">GetSecurityProfileApplications()</span>, <span class="term">RegSecurityProfileApplication()</span>, <span class="term">UnregSecurityProfileApplication()</span>, <span class="term">CreateSecurityProfileApplication()</span>, <span class="term">GetSecurityProfileInternetResources()</span>, <span class="term">RegSecurityProfileInternetResource()</span>, <span class="term">UnregSecurityProfileInternetResource()</span>, and <span class="term">CreateSecurityProfileInternetResource()</span>.</li><li>For the <span class="term">IInfoBase</span> object, the following properties are implemented: <span class="term">SecurityProfileName</span> and <span class="term">SafeModeSecurityProfileName</span>.</li><li>The type of the <span class="term">SafeMode</span> parameter (used in the <span class="term">Create()</span> and <span class="term">Connect()</span> methods of external report and data processor managers and in the <span class="term">SetSafeMode()</span> global context method) was changed from <span class="term">BOOLEAN</span> to <span class="term">STRING</span>. The type of value returned by the <span class="term">SafeMode()</span> global context method was changed from <span class="term">BOOLEAN</span> to <span class="term">STRING</span>. When this parameter (or returned value) has <span class="term">STRING</span> type, it stores the security profile name.</li></ul><p>Similar changes are implemented in:</p><ul><li>Cluster administration utility (<span class="interface">rac</span>) – the <span class="term">profile </span>mode is implemented, and the <span class="term">update</span> command of the <span class="term">infobase</span> mode is modified.</li><li>Java API for server administration.</li></ul></td><td>This feature was not provided.</td><td>You can limit access of applied solutions to the resources of the system in which they run by using administrative tools (without modification of the applied solution source code). The functionality of the source code that is executed in the safe mode (for example, code developed by user) can be extended while preserving the required security level.<p>For example, you can use security profiles to organize individual temporary storage directories for each data area, or describe the list of Internet resources available for use in a specific infobase.</p></td></tr><tr title="Версия 8.3.3" class="tag_51"><td><a name="216a7297-5bdb-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>The following objects are implemented: <p><span class="term">TestedCommandInterfaceButton</span>, <span class="term">TestedCommandInterfaceGroup</span>, and
<span class="term">TestedWindowCommandInterface</span>.
For tested objects, the <span class="term">GetObject()</span> method is implemented. Its set of parameters is similar to that of the <span class="term">FindObject()</span> and <span class="term">FindObjects()</span> methods. If the object is not found, the <span class="term">GetObject()</span> method raises an exception.
Methods for testing user messages are implemented. The list of properties and methods for managing tested objects is extended. You can get the form name, the current window, the command interface, and so on. You can get the information on the last error that occurred in the tested client application.
For the <span class="term">TestedApplication</span> object, the methods <span class="term">GetActiveWindow()</span> and <span class="term">GetCurrentErrorInfo()</span> are implemented. For the <span class="term">TestedClientApplicationWindow</span> object, the methods <span class="term">GetCommandInterface()</span>, <span class="term">GetUserMessageTexts()</span>, and <span class="term">ChooseUserMessage()</span> are implemented. For the <span class="term">TestedForm</span> object, the <span class="term">FormName</span> property and the methods <span class="term">FindDefaultButton()</span>, <span class="term">CurrentModified()</span>, and <span class="term">GetCommandBar()</span> are implemented, while the <span class="term">Close()</span> method is moved to the <span class="term">TestedClientApplicationWindow</span> object. For the <span class="term">TestedFormField</span> object, the methods <span class="term">CurrentModeIsEdit()</span> and <span class="term">GetEditText()</span> are implemented, and the methods <span class="term">BeginEdit</span><span class="term">CurrentArea</span><span class="term">()</span> and <span class="term">EndEditCurrentArea() </span>are modified. For the <span class="term">TestedFormTable</span> object, the method <span class="term">CurrentModeIsEdit()</span> is implemented, and the methods <span class="term">ChangeRow()</span>, <span class="term">EndEditRow()</span>, <span class="term">GotoPreviousRow()</span>, <span class="term">GotoNextRow()</span>, <span class="term">Expand()</span>, and <span class="term">Collapse()</span> are modified. For objects that describe tested form elements, the methods <span class="term">GetToolTipText()</span>, <span class="term">CurrentVisible()</span>, <span class="term">CurrentEnable()</span>, <span class="term">CurrentReadOnly()</span>, <span class="term">GetContextMenu()</span>, and <span class="term">GetCommandBar()</span> are implemented. </p><p> </p></td><td>The application window command interface could not be tested automatically. Operations on user messages were not available during the automated testing.</td><td>You can test the application window command interface automatically.
In test scenarios, simplified the processing of errors that occur when attempts to get non-existent objects are made.</td></tr><tr title="Версия 8.3.3" class="compat tag_43 tag_1"><td><a name="77da89b8-6146-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Dynamic list settings can be saved automatically. For managing this feature, the <span class="interface">Auto</span><span class="interface"> save user settings</span> property is implemented for dynamic lists. For storing settings, the dynamic list settings storage is implemented. For managed form tables linked to dynamic lists, the following functionality is implemented: commands for saving and restoring settings, and events for implementing custom responces to saving, restoring, or editing dynamic list settings. The view mode of the dynamic list (list, tree, or hierarchical list) is stored together with form element settings.<p>You can edit user settings of a dynamic list in a separate group of the form that displays the dynamic list. For that purpose, the <span class="interface">User</span><span class="interface"> settings group</span> property is implemented. Dynamic list settings can be edited in a separate common form, which is specified using the <span class="interface">Default </span><span class="interface">dynamic list settings f</span><span class="interface">orm</span> configuration property.</p><p>For the <span class="term">DynamicList</span> object, the <span class="term">SettingsComposer </span>property is implemented, which is similar to the corresponding property of report objects.</p><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>For dynamic lists, only the following settings were saved automatically: filters (that were restored with disabled usage flag) and conditional appearance. To save and restore other settings, developers had to create custom algorithms in 1C:Enterprise script.</td><td>Improved usability of dynamic lists for end users. Simplified development of dynamic lists with quick access to filters for developers. Development of custom algorigthms for saving or restoring dynamic list settings is not required.</td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="17217271-704a-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>A new permission allowing end users to expand or collapse a managed form group (only vertically) was added. If the permission is granted, a user can collapse the group (hide all of the items that are included in the group). For managed form groups, the following properties are implemented: <span class="term">Behavior</span>, <span class="term">ControlRepresentation</span>, <span class="term">ShowLeftMargin</span>, and <span class="term">CollapsedRepresentationTitle</span>.<p>Only usual groups with displayed titles can be collapsed.</p></td><td>This feature was not provided. The only available method to hide unused items was to change their visibility.</td><td>
<p>Hiding form items that are rarely used is available. This decreases the amount of data that is displayed to an end user. To view the hidden data, an end user can expand the group.</p><p> </p></td></tr><tr title="Версия 8.3.3" class="tag_20"><td><a name="17217272-704a-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed is displayed in the message window.</td><td>On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed was displayed in a modal window.</td><td>
<p>Developers no longer have to close modal dialog boxes many times when they attempt to perform mass modification of objects that cannot be modified (for example, objects stored in a configuration repository that are not locked).</p></td></tr><tr title="Версия 8.3.3" class="tag_96"><td><a name="09181362-7128-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>A new client application interface type "Taxi" is implemented.<p>The <span class="interface">Taxi </span>interface includes a large number of changes, with the following highlights:</p><ul><li>A whole new view: enlarged fonts, increased spacing between elements in forms, modified color scheme and form element layout, enlarged form elements.</li><li>Improved application navigation: focus on a single-window functionality, single purpose panels (such as history or favorites), switching back and forward between previously opened windows, and so on.</li><li>Extended main application window settings: developers can define the content and location of panels for the applied solution, at the same time users can arrange these panels as they like.</li><li>A system form for the full-text search.</li><li>The form navigation panel is located in the upper part of the form.</li><li>The message window is located in the lower part of the form and is only visible when there are messages to display.</li><li>The performance meter is displayed in a separate application window panel, not in a separate window.</li><li>In the <span class="interface">History </span>panel, records are grouped by days with their opening time displayed. You can search for history items and add them to <span class="interface">Favorites</span>.</li><li>In the <span class="interface">Favorites </span>panel, you can search for items, rename them, and "pin" important ones at the top of the list.</li></ul><p>Use the <span class="term">iTaxi </span>command-line option of the client application for the forced start of this interface mode (provided that using <span class="interface">Taxi </span>is allowed in the applied solution). You can also switch between interface modes using the client application settings window.
The following configuration properties are implemented:</p><ul><li><span class="term">InterfaceCompatibilityMode </span>- specifies which interface modes are available in the applied solution.</li><li><span class="term">ClientApplicationInterface </span>- stores the list of panels used by default in the client application, as well as their positions.</li><li><span class="term">DefaultSearchForm </span>- specifies the search form that is used for the full-text search in application data. If the form is not specified, the system full-text search form is used.</li></ul><p> </p><p>A brand new look for the calendar. For the managed form calendar field, the following properties related to the new features are implemented: <span class="term">HeightInMonths</span>, <span class="term">WidthInMonths</span>, and <span class="term">ShowMonthsPanel</span>. These properties are only used in the <span class="interface">Taxi</span> interface.
For the <span class="term">ClientApplicationInterfaceVariant</span> object, the <span class="term">ClientApplicationInterfaceVariant</span> property is implemented (it is used for getting the interface mode), and the global context method <span class="term">ClientApplicationInterfaceCurrentVariant()</span>. The <span class="term">ClientApplicationBaseFontCurrentVariant()</span> global context method is implemented. It gets the size of the base font in the client application.
For the <span class="term">UserWorkFavoritesItem</span> object, the <span class="term">Important</span> and <span class="term">Presentation</span> properties are implemented.
In the <span class="interface">Taxi</span> interface, the <span class="interface">Desktop</span> is renamed to <span class="interface">Start page</span> (the related commands are renamed accordingly). The <span class="interface">Dashboard</span> section of the section pane is used for accessing the command interface.
In the <span class="interface">Taxi </span>interface:</p><ul><li>The <span class="interface">All actions</span> menu is renamed to <span class="interface">More</span>.</li><li>The default presentations of standard commands in forms are changed, as well as command presentations in the command panel and in the <span class="interface">More</span> menu.</li><li>The presentations of form item groups are changed.</li></ul><p>The link to the start page (desktop) of the applied solution has the following format: <span class="term">e1cib/navigationpoint/startpage</span>. Start page (desktop) settings are stored with the settings key <span class="term">StartPage/WindowSettings</span> (for <span class="interface">Taxi</span> interface, <span class="term">StartPage/Taxi/WindowSettings</span>).
In the managed form editor, switching between interface 8.2 and <span class="interface">Taxi</span><span class="term"> </span>modes in the preview window is implemented.</p><p> </p></td><td>The interface implemented in platform version 8.2 was used in managed applications.</td><td>Improved applied solution navigation, improved usability, development according to modern interface design trends.</td></tr><tr title="Версия 8.3.3" class="tag_96"><td><a name="d0b36fdf-71d9-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The <span class="term">NormalTextFont</span> style font used as a basis for size calculation for other style fonts except the <span class="term">TextFont</span> is implemented. The actual choice of font depends on the interface mode of the applied solution (<span class="interface">Taxi</span> or interface 8.2).</td><td>This feature was not provided.</td><td>Using the new font (and the fonts based on it) allows storing fort size proportions for managed form elements in both interface modes.</td></tr><tr title="Версия 8.3.3" class="tag_96"><td><a name="46d1c4a3-74f7-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>The <span class="term">MainSectionPicture</span> configuration property is implemented. In this property, you can specify a picture that will be used for the main section (desktop) in the section panel.</td><td>The desktop had a fixed picture that could not be changed.</td><td>You can create a uniform graphic design for your applied solution, and you can create a desktop look that will be friendly to the primary audience of the solution.</td></tr><tr title="Версия 8.3.3" class="tag_20"><td><a name="c0299593-7a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>A context tooltip can be displayed for the <p>parameters of the function or procedure that is being edited in the module text editor. If the method has several syntax variants, you can select the required variant.
Automatic parsing of procedure and function comments for displaying them in context tooltips is implemented. Procedure and function comments can be sorted for displaying in the context tooltip. The comment format is described in the documentation and complies with the applied solution development standards. Procedure and function templates that comply with this format are included into the distribution kit.
The option that shows or hides the context tooltips is implemented in Designer. In the source code editor, you can open the context tooltip by pressing <span class="interface">Ctrl+Shift+Spacebar</span>. </p></td><td>In Designer, context tooltip for procedure and function parameters was not available. The context tooltip was only available for names of applied solution procedures and functions. Comments to procedures and functions were not used for getting information on their parameters.</td><td>Improved usability of writing source codes. The Syntax Assistant is not required for a quick reference on the order and types of procedure or function parameters.</td></tr><tr title="Версия 8.3.3" class="tag_10"><td><a name="fcbb6955-8af0-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The documentation describes DBMS setup and maintenance features that can be used for 1C:Enterprise administration.</td><td>The documentation did not describe the administration tools that could be used without violating the license agreements.</td><td>You can use DBMS features that do not affect the structure of data used by 1C:Enterprise (the changes that are made do not affect the restructuring and are saved after the restructuring).</td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="b760b07c-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For fields of check box and radio button types, the tumbler look is implemented (several adjacent buttons where the active value has a different color). For managed form fields of these types, the properties <span class="term">CheckBoxType</span> and <span class="term">RadioButtonsType</span> are implemented.</td><td>This feature was not provided.</td><td>New presentation features. Improved usability for touch interfaces.</td></tr><tr title="Версия 8.3.3" class="tag_142 tag_6"><td><a name="b760b084-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 142); return false;">Database configuration updates</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Infobase restructuring is required when a chart of characteristic types is modified or when a chart of accounts where a chart of characteristic types is used as an extra dimension,is modified.<p>The following changes are implemented in the background restructuring procedure:</p><ul><li>You cannot create, edit, or delete exchange plan items if the exchange plan requires the restructuring. The restructuring is performed during the processing phase.</li><li>You cannot create, edit, or delete chart of characteristic types items if the chart is specified as an extra dimension for a chart of accounts and this chart of accounts requires restructuring. In this case the restructuring of the chart of characteristic types is performed during the processing phase.</li><li>The <span class="term">SetPredefinedDataUpdate</span><span class="term">()</span> method cannot be called during the background restructuring.</li></ul></td><td>Charts of characteristic types were restructured when they were modified.<p>All charts of characteristic types and exchange plans were restructured when the changes were applied (during the background restructuring).</p></td><td>In the background database configuration update, the specifics of changing some data structures are taken into account. This prevents mismatching of object data.</td></tr><tr title="Версия 8.3.3" class="tag_29"><td><a name="b760b081-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft Windows Server 2012 (x86-64) is now supported.</td><td>Microsoft Windows Server 2012 (x86-64) was not supported.</td><td>New version of the Microsoft operating system is now supported.</td></tr><tr title="Версия 8.3.3" class="tag_64"><td><a name="df4b0270-a733-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>If the <span class="interface">Interface compatibility mode</span> configuration property is set to <span class="interface">Taxi</span> or <span class="interface">Taxi.Version 8.2 enabled</span>, the <span class="term">Help</span> picture from the picture library corresponds to the <span class="interface">Taxi</span> interface.</td><td>The appearance of the <span class="term">Help</span> picture in the picture library did not depend on the configuration property values.</td><td>The appearance of the <span class="interface">Help</span> button depends on the interface mode.</td></tr></table><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4288e497-1835-11e2-b237-e61f135f174b">New functionality and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.3" class="tag_168"><td><a name="4535b50e-4a88-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 168); return false;">Printing documents</a>.<br></td><td>Changed behavior of print status forms in managed applications in thin and thick clients:<ul><li>In the <span class="interface">F</span><span class="interface">orms in tabs</span> form opening mode, print status forms are opened in separate windows.</li><li>The form is opened in a modal window so that users cannot interact with the interface during printing.</li><li>The form cannot be closed by clicking the "X" button.</li></ul><p>The form cannot be resized.</p></td><td>The print status form had different behavior.</td><td>Improved usability of printing documents.</td></tr><tr title="Версия 8.3.3" class="tag_15"><td><a name="615f4d80-4f38-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The Primary Selection clipboard is now supported (data is copied to this clipboard when a text fragment is selected, without the need to press any keys). Copying to the Primary Selection clipboard is supported for the following form elements:<ul><li>Text box</li><li>Text document field</li><li>Formatted document field</li><li>Spreadsheet document field</li></ul><p>Insertion from the Primary Selection clipboard (available by pressing the middle mouse button) is supported in text boxes.</p></td><td>This feature was not provided.</td><td>Improved usability of client application for users with Linux experience.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_104 tag_1"><td><a name="e71408d5-4f62-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>If a text box is linked to an attribute of complex type where all types except one are disabled by access rights or functional options, when user attempts to select a value in the text box, the choice value form is opened.<p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>If a text box was linked to an attribute of complex type, when a user attempted to select a value in the text box, the type selection dialog box, was displayed even if the list of types contained a single value.</td><td>
<p>Users do not have to select from a single value in the type selection dialog box.</p></td></tr><tr title="Версия 8.3.3" class="tag_51"><td><a name="f110865f-5bf2-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>On closing an application, if the log of user actions is being recorded at the moment, a request for saving the log is sent.</td><td>On closing the application, unsaved data from the log of user actions was lost.</td><td>Reduced chance of losing unsaved data from the log of user actions when the application window that initiated recording to the log of user actions is closed.</td></tr><tr title="Версия 8.3.3" class="tag_28"><td><a name="17217270-704a-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>During the startup of the web client, the check for a pop-up window blocker is only performed if the separate window interface is used and modal windows are enabled.
The check for a pop-up window blocker is performed after the user authentication. <p>
</p><p>
</p></td><td>The check for a pop-up window blocker was always performed during the web client startup.</td><td>Users are not prompted to specify the pop-up blocker settings when it is not required.</td></tr><tr title="Версия 8.3.3" class="tag_96"><td><a name="d0b36fe1-71d9-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>On interface mode change, the user is prompted to restart the client application.</td><td>Changing interface mode did not prompt to restart the client application.</td><td>The procedure of changing the interface mode became more user-friendly: the system now informs the user what they have to do to have the changes take effect.</td></tr><tr title="Версия 8.3.3" class="tag_12"><td><a name="f5ec58fb-ab1f-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>The following changes are implemented in the standard functions:<ul><li>Event log:</li><ul><li>The set of commands in the form command bar is changed, as well as the command presentations.</li><li>The procedures for enabling and disabling the filter are revised.</li><li>You can view log entry data by clicking the link in the corresponding log column.</li><li>You can filter records by date and time.</li></ul><li>Find references to object:</li><ul><li>You can search for references to a reference that is found (from the context menu).</li></ul><li>Manage full-text search:</li><ul><li>The form is revised.</li><li>Enabling or disabling full-text search is performed without opening additional forms.</li></ul><li>Post documents:</li><ul><li>The form is revised.</li></ul><li>Active users:</li><ul><li>You can open the event log filtered by user by clicking a hyperlink in the <span class="interface">User</span> column.</li></ul></ul></td><td>Standard function dialog boxes were less user-friendly.</td><td><p>Improved usability of standard functions.</p></td></tr><tr title="Версия 8.3.3" class="tag_28"><td><a name="ae6a7289-dd85-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The documentation includes recommendations for choosing a web browser for low-performance computers.</td><td>The documentation did not include recommendations for choosing a web browser.</td><td>Recommendations for choosing a web browser are available.</td></tr><tr title="Версия 8.3.3" class="tag_28"><td><a name="0d27d115-93f5-11e3-831f-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In Microsoft Internet Explorer web browser, notification windows do not fade out of view when they are closed automatically.</td><td>In Microsoft Internet Explorer web browser, notification windows faded out of view when they were closed automatically.</td><td>Improved performance of notification windows in Microsoft Internet Explorer web browser.</td></tr></table><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4288e498-1835-11e2-b237-e61f135f174b">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.3" class="tag_19 tag_42 tag_45"><td><a name="f7792ae7-2326-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Optimized performance of accumulation register virtual tables when obtaining totals with a filter that does not include all dimensions.</td><td>Insufficient performance of accumulation register virtual tables when obtaining totals with a filter that did not include all dimensions.</td><td>Performance of accumulation register virtual tables is increased.</td></tr><tr title="Версия 8.3.3" class="tag_6"><td><a name="75765209-5fc8-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Creation of new sessions is optimized.</td><td>Creating of new sessions was performed inefficiently.</td><td>Optimized performance when establishing connections to the 1C:Enterprise server in the following cases:<ul><li>Simultaneous connections from a large number of client applications.</li><li>Connection of a new client application to a cluster that already runs a large number of sessions.</li></ul></td></tr><tr title="Версия 8.3.3" class="compat tag_16 tag_1"><td><a name="61fe8a43-24c0-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>Improved performance of independent, non-periodic information registers that have more than 1 dimension.
This change is not implemented in 8.3.2 compatibility mode.</td><td>Insufficient register performance.</td><td>Increased speed of writing to a register, especially when a large number of users are working.</td></tr><tr title="Версия 8.3.3" class="tag_23"><td><a name="b4321b0e-281e-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Optimized selections from catalogs and charts of characteristic types for certain scenarios.
</td><td>In certain scenarios performance of selections from catalogs and charts of characteristic types was inefficient.</td><td>Increased performance of selections from catalogs and charts of characteristic types in certain scenarios.</td></tr><tr title="Версия 8.3.3" class="tag_43"><td><a name="b4321b0f-281e-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>Improved dynamic list performance in client/server mode when a large number of users are working.</td><td>In certain scenarios dynamic list performance was insufficient.</td><td>Improved dynamic list performance in certain scenarios.</td></tr><tr title="Версия 8.3.3" class="tag_6"><td><a name="3ca81410-324f-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Optimized processing of session data for some scenarios.</td><td>In some scenarios processing of session data was inefficient.</td><td>
<p>Improved performance and scalability of 1C:Enterprise servers.</p></td></tr><tr title="Версия 8.3.3" class="compat tag_42 tag_1"><td><a name="9ede9013-3542-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br></td><td>Optimized execution of queries to turnovers registers with a large number of dimensions that include aggregates (for some scenarios). This change is not implemented in 8.3.2 compatibility mode.</td><td>In some cases execution of queries to turnovers registers with a large number of dimensions that included aggregates was inefficient.</td><td>You can use aggregate functions in more scenarios than before.</td></tr><tr title="Версия 8.3.3" class="tag_19"><td><a name="91a4bdb0-4046-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>In order to optimize some queries to IBM DB2 DMBS, the recommendation to run the <span class="term">db2set DB2_OVERRIDE_BPF=5000</span> command and then restart the DBMS is included into the documentation. Methods of detecting situations when the optimization is required are also described in the documentation.</td><td>Some queries to IBM DB2 DBMS were performed inefficiently.</td><td>Optimized performance during the execution of some types of IBM DB2 DBMS queries.</td></tr><tr title="Версия 8.3.3" class="compat tag_16 tag_1"><td><a name="ca234f20-4a9f-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>For periodic information registers that are subordinate to recorders, the <span class="term">Active</span> field is listed in the following indexes:<ul><li>By period</li><li>By dimensions</li><li>By dimension</li></ul><p>The <span class="term">Active</span> field is the last one in these indexes.
After changing the compatibility mode, full infobase restructuring must be performed for rebuilding indexes.
This change is not implemented in 8.3.2 compatibility mode.</p></td><td>The <span class="term">Active</span> field was not included in the list of indexes of periodic information registers subordinate to recorders.</td><td>Improved performance when retrieving the first and the last slices.</td></tr><tr title="Версия 8.3.3" class="tag_6"><td><a name="2c13d93f-4f5e-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>1C:Enterprise server is optimized to reduce memory usage and fragmentation.</td><td>In some scenarios, 1C:Enterprise server used memory inefficiently. This led to memory fragmentation and increased memory consumption.</td><td>Reduced memory consumption of 1C:Enterprise server, and lower memory fragmentation. This allows to reduce the number of planned 1C:Enterprise server restarts and improves the system stability.</td></tr><tr title="Версия 8.3.3" class="tag_19"><td><a name="1721726d-704a-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Indexes of attributes with additional ordering include deletion marks and all fields that are indexed with additional ordering. This data is added to the end of the index.</td><td>Indexes of attributes with additional ordering did not include deletion marks and all fields that were indexed with additional ordering.</td><td>
<p>Improved performance of dynamic lists filtered by multiple attributes (including the deletion mark).</p></td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="17217273-704a-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Optimized performance of displaying managed forms after server calls (both explicit and implicit ones) that change the form appearance.</td><td>Forms were not displayed fast enough when their appearance was changed from 1C:Enterprise script.</td><td>Optimized performance of displaying forms, for example, when the displayed title of a form element is modified.</td></tr><tr title="Версия 8.3.3" class="compat tag_58 tag_1"><td><a name="2fa966f7-9e07-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>Once the version 8.3.2 compatibility mode is disabled, optimization is performed on the structure that stores data on the table separators connected to objects included in the separator contents. When the version 8.3.2 compatibility mode is enabled, the reverse restructuring of the database tables is performed.</td><td>The structure that stored separator data was not optimal.</td><td>Improved performance due to the changes in the structure that stores separator data.</td></tr><tr title="Версия 8.3.3" class="tag_6"><td><a name="a9fa22e3-bbd0-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>In server cluster, the algorithm for balancing the working process load is optimized. The following parameters are used in addition to parameters used in the previous versions to define the available server performance: size of CPU queue, current processor load, and number of CPU cores.
Values used for defining the available server performance are recorded to the <span class="term">TXT</span> property of the <span class="term">CLSTR</span> event in the technological log.
To obtain performance parameters, the user on whose behalf the 1C:Enterprise server is running must be included in the <span class="interface">Performance Log Users</span> group.</td><td>In the server cluster, the algorithm for balancing the working process load took less number of parameters into account.</td><td>Improved reactivity of the load balancing algorithm. The algorithm defines overloaded CPUs and stops sending new tasks to them.</td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="20673242-bc60-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Optimized performance of opening managed forms with multiline text boxes that contain a large number of line breaks.</td><td>Performance of opening forms with multiline text boxes containing a large number of line breaks was not high enough.</td><td>Forms with multiline text boxes that contain a large number of line breaks are opened faster.</td></tr></table><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4288e499-1835-11e2-b237-e61f135f174b">Changes that affect system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.3" class="tag_116"><td><a name="427ec7cb-185a-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>Licenses for basic configurations are available on Linux.</td><td>Basic version licenses for Linux were unavailable.</td><td>You can run basic 1C:Enterprise configuration versions on Linux.</td></tr><tr title="Версия 8.3.3" class="tag_23"><td><a name="427ec7cc-185a-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Infobase object autonumbering logic is revised. The check for number or code uniqueness (including automatically generated codes and numbers) is always performed while the object is being written.<p>The message informing the user that a number or code is not unique now specifies the value of the non-unique number or code.</p><p>Numbers or codes that are no longer used are never re-assigned automatically, even when the desired prefix is not specified explicitly. In the event when the desired prefix is not specified explicitly, the platform forms a number or code as follows: it selects the greatest of the prefixes that match the specified pattern and then adds the next subsequent number (prefixes are compared according to their alphabetical order, for example, B is greater than A).</p></td><td>The uniqueness check was not performed for automatically generated numbers or codes while the object was being written.<p>The message informing the user that a number or code was not unique did not include the value of the non-unique number or code.</p><p>Numbers or codes that were no longer used might be re-assigned automatically in the event when the desired prefix was not specified explicitly–the platform might assign a code that was used before when its prefix matched the specified pattern and the prefix was not the greatest one among those matching the pattern (prefixes are compared according to their alphabetical order, for example, B is greater than A).</p></td><td>Increased stability and reliability of infobase object autonumbering.
Messages informing the user that a number or code is not unique now contain more information.
The autonumbering is more logical: numbers or codes are always issued in the ascending order.</td></tr><tr title="Версия 8.3.3" class="tag_23"><td><a name="790da231-18ed-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>If a text value presentation cannot be calculated during debugging, the string <span class="interface">Error getting</span><span class="interface"> value presentation</span> is returned as a text presentation.</td><td>If a text value presentation could not be calculated, Designer might stop responding.</td><td>Improved system stability during debugging.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_1"><td><a name="115a9435-21ac-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Visibility of the command for switching to the calculation register (in a recorder form) is set to <span class="term">True</span> by default.<p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>Visibility of the command for switching to the calculation register (in a recorder form) was set to <span class="term">False</span> by default.</td><td>Default visibility of commands for switching to registers is the same for all registers.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_1"><td><a name="bb57dca2-2296-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When attributes of <span class="term">Number</span> type that have minimum or maximum values set are cleared interactively, the attribute values after clearing cannot exceed the specified limits.
This change is not implemented in 8.3.2 compatibility mode.</td><td>When attributes of <span class="term">Number</span> type were cleared interactively, their minimum and maximum values were ignored.</td><td>Users cannot enter data that does not meet the conditions specified by the developer.</td></tr><tr title="Версия 8.3.3" class="compat tag_23 tag_1"><td><a name="bb57dca3-2296-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>When a spreadsheet document is saved to a <span class="interface">.docx</span> file, image border styles are preserved.
This change is not implemented in 8.3.2 compatibility mode.</td><td>When a spreadsheet document was saved to a <span class="interface">.docx</span> file, images always had borders.</td><td>More accurate export of spreadsheet document styles to <span class="interface">.docx</span> format.</td></tr><tr title="Версия 8.3.3" class="tag_23"><td><a name="bb57dca4-2296-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>When a spreadsheet document is saved to a <span class="interface">.docx</span> file the following spreadsheet document print options are preserved:<ul><li>paper size</li><li>page orientation</li><li>scale</li><li>pagination</li><li>margins</li><li>headers and footers</li><li>repeating rows</li><li>displaying headers and footers on the first page</li></ul><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>Print options were not preserved when a spreadsheet document was saved to a <span class="interface">.docx</span> file.</td><td>Improved usability of spreadsheet documents saved in <span class="interface">.docx</span> format.</td></tr><tr title="Версия 8.3.3" class="compat tag_25 tag_1"><td><a name="bb57dca6-2296-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When a user field is added to data composition system settings and the source of available settings is not specified, the file name is generated using the language of the current script variant.<p>This change is not implemented in 8.2.16 compatibility mode.
</p></td><td>When a user field was added to data composition system settings and the source of available settings was not specified, the file name was generated in English.</td><td>The data composition system behavior is uniform with behavior of similar platform features.</td></tr><tr title="Версия 8.3.3" class="tag_78"><td><a name="f65853b1-24b8-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>The look and behavior of the file selection dialog box (including the <span class="term">FileDialog</span> object) in Windows Vista and later Windows versions complies with the standards of these operating systems. In Windows XP and earlier and in the web client the look of the dialog box is not changed.</td><td>In Windows Vista and later, an outdated file selection dialog box was used.</td><td>The look of the file selection dialog box corresponds to the operating system being used.</td></tr><tr title="Версия 8.3.3" class="tag_78"><td><a name="f65853b2-24b8-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>If both <span class="term">Directory</span> and <span class="term">FullFileName</span> are specified for a <span class="term">FileDialog</span> object, the dialog box is opened in the specified directory and with the specified file name.</td><td>If both <span class="term">Directory</span> and <span class="term">FullFileName</span> were specified for a <span class="term">FileDialog</span> object, the dialog box ignored the specified directory and used the directory that was obtained from the full file name.</td><td>Improved usability of the file choice dialog.</td></tr><tr title="Версия 8.3.3" class="tag_51"><td><a name="4288e4a1-1835-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>Wildcard support implemented for the <span class="term">InputText()</span> method of the <span class="term">TestedFormField</span> object.</td><td>The automated testing mechanism did not support wildcards in text input fields.</td><td>Extended functionality of the automated testing system.</td></tr><tr title="Версия 8.3.3" class="tag_133"><td><a name="790da22c-18ed-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>When dumping a configuration to XML files, names of metadata object commands follow this convention: <span class="term">Catalog.CatalogName.Command.CommandName</span>.<p>Configurations dumped using earlier platform versions cannot be loaded.</p></td><td>When dumping a configuration to XML files, names of metadata object commands followed this convention: <span class="term">Catalog.CatalogName.CommandName</span>.</td><td>Command names are uniform; you can figure out the command purpose from its name.</td></tr><tr title="Версия 8.3.3" class="tag_133"><td><a name="790da22d-18ed-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>When dumping a configuration to XML files, names of metadata object commands follow this convention: <span class="term">Catalog.CatalogName.Command.CommandName</span>.<p>Configurations dumped using earlier platform versions cannot be loaded.</p></td><td>When dumping a configuration to XML files, names of metadata object commands followed this convention: <span class="term">Catalog.CatalogName.CommandName</span>.</td><td>Command names are uniform; you can figure out the command purpose from its name.</td></tr><tr title="Версия 8.3.3" class="tag_133"><td><a name="790da22e-18ed-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>When dumping a configuration to XML files, names of standard commands of managed forms follow this convention: <span class="term">Form.StandardCommand.CommandName</span>.
Configurations dumped using earlier platform versions cannot be loaded.</td><td>When dumping a configuration to XML files, names of standard commands followed this convention:
<span class="term">FormStdCommand.CommandName</span>.</td><td>Command names are uniform; you can figure out the command purpose from its name.</td></tr><tr title="Версия 8.3.3" class="tag_133"><td><a name="790da22f-18ed-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>When dumping a configuration to XML files, names of managed form commands follow this convention: <span class="term">Form.Command.FormCommandName</span>.
Configurations dumped earlier will not be loaded.</td><td>When dumping a configuration to XML files, names of managed form commands followed this convention: <span class="term">FormCommand.FormCommandName</span>.</td><td>Command names are uniform; you can figure out the command purpose from its name.</td></tr><tr title="Версия 8.3.3" class="tag_133"><td><a name="790da230-18ed-11e2-b237-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>When dumping a configuration to XML files, names of standard commands of managed form elements follow this convention: <span class="term">Form.Item.ElementName.StandardCommand.StandardCommandName</span>. Configurations dumped earlier will not be loaded.</td><td>When dumping a configuration to XML files, the standard commands of managed form elements followed this convention: <span class="term">Form&lt;ElementType&gt;.ElementName.StandardCommandName</span>.</td><td>Command names are uniform; you can figure out the command purpose from its name.</td></tr><tr title="Версия 8.3.3" class="tag_133"><td><a name="6c7e97ec-4f66-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>When a configuration is dumped to files:<ul><li>References to missing configuration objects are dumped as text presentations of identifiers of missing configuration objects.</li><li>Properties of the <span class="term">ManagedForm </span>element of a managed form that make sense only in the 1C:Enterprise mode are not dumped.</li><li>For attributes and elements of managed forms, the internal identifiers required for saving their settings are dumped.</li></ul><p>For elements of business process flowcharts, element identifiers are dumped.</p></td><td>
<p>When a configuration was dumped to files:</p><ul><li>References to missing configuration objects were ignored.</li><li>Properties of the <span class="term">ManagedForm </span>element of a managed form that made sense only in the 1C:Enterprise mode were dumped.</li><li>For attributes and elements of managed forms, the internal identifiers required for saving their settings were not dumped.</li><li>For elements of business process flowcharts, element identifiers were not dumped.</li></ul></td><td>In dumping/loading of configurations, the following improvements are implemented:<ul><li>User settings are preserved when a configuration is dumped and then loaded.</li><li>The accuracy of configuration comparison (after a configuration is dumped and then loaded) is increased.</li></ul></td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="e8692369-2d9a-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When <span class="interface">Esc </span>is pressed in a text box (except multiline text boxes), the following actions are performed:<ul><li>If the initial text box content was modified in any way, the text box reverts to the initial content.</li><li>If the initial content was not modified, the text box does not process pressing the <span class="interface">Esc</span> key and passes the processing to the form.</li></ul></td><td>Pressing <span class="interface">Esc</span> was always processed by the form. The text box did not perform any actions if <span class="interface">Esc</span> was pressed while the text was being edited.</td><td>You can cancel editing a value in a text box.</td></tr><tr title="Версия 8.3.3" class="tag_52"><td><a name="e869236c-2d9a-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>The maximum number of managed locks is 100 000 (exceeding this limit locks the entire lock space).</td><td>The maximum number of managed locks was 20 000 (exceeding this limit locked the entire lock space).</td><td>Improved user experience when using transactions with a large number of locks (more than 20 000) in a single lock space.</td></tr><tr title="Версия 8.3.3" class="compat tag_16 tag_105 tag_1"><td><a name="833357b4-2e38-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br></td><td>When a set of information register records is passed to the <span class="term">SelectChanges()</span> method as a filter value, the system behavior depends on the compatibility mode:<ul><li>In version 8.2.16 or earlier compatibility mode, the selection includes data that does not match the filter criteria defined by the record set;</li><li>In version 8.3.1 or later compatibility mode (or if the compatibility mode is not used), the selection only contains data that exactly matches the filter criteria.</li></ul></td><td>When a set of information register records was passed to the <span class="term">SelectChanges()</span> method as a filter value, the system behavior did not depend on the compatibility mode.<ul><li>In version 8.2.16 or earlier, the selection included data that did not match the filter criteria defined by the record set </li><li>In version 8.3.1 or later, the selection only contained data that exactly matched the filter criteria.</li></ul></td><td>Improved compatibility with previous platform versions.</td></tr><tr title="Версия 8.3.3" class="tag_43"><td><a name="6e0d0e8b-2ef6-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>In the data composition system and query wizard, syntax units enclosed in braces <span class="interface">{</span><span class="interface">}</span> do not lead to errors in dynamic lists.</td><td>In the data composition system and query wizard, syntax units enclosed in braces led to errors in dynamic lists in some cases.</td><td>Better stability of dynamic list.
</td></tr><tr title="Версия 8.3.3" class="tag_169"><td><a name="3ca8140f-324f-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 169); return false;">Cryptography</a>.<br></td><td>The value of the <span class="term">CryptoModuleName</span> parameter in the <span class="term">CryptoManager</span> object wizard is case insensitive.</td><td>The value of the <span class="term">CryptoModuleName</span> parameter in the <span class="term">CryptoManager</span> object wizard was case sensitive.</td><td>The system behavior complies with common standards.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_146 tag_1"><td><a name="f6c4a20f-3320-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 146); return false;">Ordinary forms</a>.<br></td><td>In managed and ordinary forms, if the second parameter (<span class="term">FormElement</span>) of the <span class="term">ChooseFromMenu()</span> method is a managed form table, a managed form, a table box, or an ordinary form, the menu that is opened using this method is displayed in the following location:<ul><li>For a table box or a managed form table, the menu is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table if the current cell cannot be determined.</li><li>For a form, the menu is displayed in the upper left corner.</li></ul><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>
<p>If the second parameter (<span class="term">FormElement</span>) of the <span class="term">ChooseFromMenu()</span> method was a managed form table, a managed form, a table box, or an ordinary form, the menu was displayed in the following location:</p><ul><li>For a table box or a managed form table, the menu was displayed in the lower left corner of the element passed as the parameter value.</li><li>For a form, the menu was displayed in the lower left corner of the current form element. If the current form element could not be determined, the menu was displayed in the lower left corner of the form. In the web client, the menu was displayed in the center of the screen.</li></ul></td><td>Uniform behavior when the system opens similar menus (e.g. context menu in a managed form table) or the applied solution opens such menus (using the <span class="term">ChooseFromMenu()</span> method).</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_146 tag_1"><td><a name="47b04cbc-33dc-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 146); return false;">Ordinary forms</a>.<br></td><td>In managed and ordinary forms, if the second parameter (<span class="term">FormElement</span>) of the <span class="term">ChooseFromList()</span> method is a managed form table, a managed form, a table box, or an ordinary form, the list that is opened using this method is displayed in the following location:<ul><li>For a table box or a managed form table, the list is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table, if the current cell cannot be determined.</li><li>For a form, the list is displayed in the upper left corner.</li></ul><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>If the second parameter (<span class="term">FormElement</span>) of the <span class="term">ChooseFromList()</span> method was a managed form table, a managed form, a table box, or an ordinary form, the list was opened in the following way:<ul><li>For a table box or a managed form table, the list was displayed in the lower left corner of the element passed as the parameter value.</li><li>For a form, the list was displayed in the lower left corner of the current form element. If the current form element could not be determined, the list was displayed in the lower left corner of the form.</li><li>In the web client, the list was displayed according to form settings because a system form was used to display it.</li></ul></td><td>Uniform behavior when executing similar actions (the <span class="term">ChooseFromMenu</span><span class="term">()</span> and <span class="term">ChooseFromList</span><span class="term">()</span> methods).
</td></tr><tr title="Версия 8.3.3" class="tag_20"><td><a name="47b04cbd-33dc-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>You can search and replace in the <span class="term">ChoiceParameters</span> property of configuration objects. The search and replace algorithm is modified for the <span class="term">ChoiceList</span> and <span class="term">ChoiceParameterLinks</span> configuration objects.
The search and replace are performed:<ul><li>For the <span class="term">ChoiceParameters</span> property: in the <span class="term">Name</span> and the <span class="term">Value</span> columns (including fixed array elements). The search is performed on values of <span class="term">String</span> type.</li><li>For the <span class="term">ChoiceList</span> property: in the <span class="term">Presentation</span> column and in the <span class="term">Value</span> column if the value has the <span class="term">String</span> type.</li><li>For the <span class="term">ChoiceParameterLinks</span> property: in the <span class="term">Name</span> column.</li><li>Every time the search string is found, the search/replace procedure is paused and a message prompting to resume the procedure is displayed.</li></ul><p>Search in the <span class="term">LinkByType</span> property of configuration objects is no longer supported.</p></td><td>Search and replace in the <span class="term">ChoiceParameterLinks</span> property of configuration objects was performed only in the <span class="term">Name</span> column.
Search and replace in the <span class="term">ChoiceList</span> property of configuration objects was performed only in the <span class="term">Presentation</span> column.
Search and replace was not performed in the <span class="term">ChoiceParameters</span> property of configuration objects.
Search could be performed in the <span class="term">LinkByType</span> property of configuration objects.</td><td>The search and replace operations in configuration object properties are now uniform to similar operations in texts.</td></tr><tr title="Версия 8.3.3" class="tag_20"><td><a name="47b04cbe-33dc-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The presentation of the <span class="term">ChoiceParameters</span> property of configuration objects in the object properties editing window is changed. If a value of any property element is a fixed array, presentations of array values are used.
The presentation of the <span class="term">ChoiceList</span> property of configuration objects in the object properties window is changed. A presentation now consists of both list item values and their presentations (if the presentations are specified).</td><td>If an element of a <span class="term">ChoiceParameters</span> property was a fixed array, its presentation was a <span class="interface">FixedArray</span> string.
For the <span class="term">ChoiceList</span> property of configuration objects, the presentation in the object properties window was generated from the list item values only.</td><td>Improved usability of <span class="term">ChoiceParameters</span> and <span class="term">ChoiceList</span> properties in Designer.</td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="47b04cbf-33dc-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Improved look and behavior of drop-down lists in text box fields that can be edited and contain data of reference type, enumerations, or system enumerations:<ul><li>If a field contains data of reference type or an enumeration, the field includes the choice button, and the characters typed in the field do not match any choice list values, the <span class="interface">Click s</span><span class="interface">how all</span> <span class="interface">to select item</span> message is displayed in the list.</li><li>If the drop-down list is displayed and a value is selected in it, pressing <span class="interface">Tab</span>, <span class="interface">Shift+Tab</span>, or <span class="interface">Enter</span> selects the current value from the list. Clicking another form element does not select the current value; the list is closed instead (same effect as pressing <span class="interface">Esc</span>). The selection is not moved to the form element that was clicked.</li><li>If the drop-down list is not displayed and the characters typed in the field uniquely identify a choice list value, pressing <span class="interface">Tab</span>, <span class="interface">Shift+Tab</span>, or <span class="interface">Enter</span> selects this value. Clicking another form element also selects this value.</li></ul><p>If the drop-down list is not displayed and the characters typed in the field match multiple choice list values, pressing <span class="interface">Tab</span>, <span class="interface">Shift+Tab</span>, or <span class="interface">Enter</span> opens the drop-down list. Clicking another form element also opens the drop-down list. </p></td><td>The drop-down list had a different look and behavior. </td><td>Improved usability of text box fields that contain data of reference type, enumerations, or system enumerations.</td></tr><tr title="Версия 8.3.3" class="compat tag_42 tag_1"><td><a name="8d2fd265-3537-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br></td><td>You can enable the aggregates mode for any turnovers accumulation register, regardless of the actual presence of aggregates in metadata.
In the client/server mode you can create new optimal aggregates (and remove outdated ones) when aggregates are being rebuilt in 1C:Enterprise mode.
This change is not implemented in 8.3.2 compatibility mode.</td><td>Developers had to add aggregates in Designer to keep the list of optimal aggregates up to date.</td><td>Simplified support of optimal aggregate list: you only have to rebuild aggregates on regular basis.</td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="86186d62-3544-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In text boxes containing data of reference type, only the color of the text presentation of the value is changed on element activation.</td><td>In text boxes containing data of reference type, the color of the entire field changed on element activation.</td><td>Better text box usability. A tooltip can be displayed in a text box linked to data of reference type if the text box is first in the tab order of the form.</td></tr><tr title="Версия 8.3.3" class="tag_20 tag_67"><td><a name="043ab6bd-388c-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>You can perform quick comparison of selected configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. Selective comparison is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, exchange plan content objects, styles, desktop workspaces, maps, forms, online help pages, predefined items, command interface fragments, and role rights.
To run the selective comparison command, right-click anywhere in any of the repository dialog boxes or in the compare configurations window, and then click <span class="interface">Perform</span><span class="interface"> selective comparison with the</span><span class="interface"> configuration object</span>.
Selective comparison of configuration objects is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.</td><td>This feature was not provided.
When comparison was initiated for a specific object, full comparison of two configurations was performed. The focus in the comparison window was set to that object.</td><td>Improved usability of configuration repository. Optimized comparison procedure when it is performed for a single configuration object.</td></tr><tr title="Версия 8.3.3" class="tag_19"><td><a name="d8687ab3-4048-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later is now available.<p>All of the required settings are specified automatically by the installation program of the patched PostgreSQL version unless a cluster created by the standard PostgreSQL version is found on the computer.</p></td><td>Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later was not available.</td><td>1C:Enterprise supports clusters created by the following versions of PostgreSQL DBMS:<ul><li>PostgreSQL 8.1.5-X.1C - 9.1.2-1.1C</li><li>PostgreSQL 9.2.1-2.1C</li><li>Standard version of PostgreSQL provided that the cluster locale is identical to the infobase locale.</li></ul><p>You can upgrade or downgrade 1C:Enteprise without upgrading or downgrading the associated PostgreSQL instance; this does not require any manual configuration.</p><p>Note that once you migrate to a new PostgreSQL version, you cannot use 1C:Enterprise version 8.3.2 or earlier. This only applies to new infobases that were created using PostgreSQL 9.2.1-2.1C. Do not create infobases using PostgreSQL 9.2.1-2.1C if you are planning to access them from earlier platform versions.</p></td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_1"><td><a name="e941e64b-4a90-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If the <span class="term">ChoiceDataGetProcessing</span> event handler of the enumeration manager returns an empty list and the formal parameter <span class="term">StandardProcessing</span> returned by this handler is set to <span class="term">False</span>, the returned list is used for filling the choice list.
This change is not implemented in 8.3.2 compatibility mode.</td><td>If the <span class="term">ChoiceDataGetProcessing</span> event handler of the enumeration manager returned an empty list and the formal parameter <span class="term">StandardProcessing</span> returned by this handler was set to <span class="term">F</span><span class="term">alse</span>, the client application filled the choice list by all enumeration values.</td><td>The system behaves as expected when a developer decides to disable selection of enumeration values.</td></tr><tr title="Версия 8.3.3" class="tag_12"><td><a name="91d69032-4b65-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>In the default event log form, filter presentation is localized.</td><td>In the default event log form, filter presentation was always displayed with Russian names of event log columns.</td><td>The filter presentation is uniform with other platform features.</td></tr><tr title="Версия 8.3.3" class="compat tag_67 tag_1"><td><a name="cc5d3f43-4b6a-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>Optimized the reference integrity check algorithm for configuration repository operations (storing and retrieving) on objects that are deleted from the repository and objects that reference to deleted ones.
In some cases, it is not necessary to lock objects that contain references to objects being deleted during the deletion. The reference integrity check algorithm used when deleting objects from the repository is uniform with the reference integrity check algorithm used when deleting objects from a configuration that is not bound to a repository.
This change is not implemented in 8.3.2 compatibility mode.</td><td>The reference integrity check algorithm for configuration repository operations was not optimized.
The reference integrity check algorithm used when deleting objects from a repository was different from the reference integrity check algorithm used when deleting objects from a configuration that was not bound to a repository.</td><td>Eliminated problems that occurred when deleting objects from configurations because of the reference integrity check differences. Storing deleted objects to the configuration repository is optimized.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_1"><td><a name="0b0741cc-4f2c-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the managed mode of the thick client, if the <span class="interface">In </span><span class="interface">list</span> editing mode is selected for a configuration object, calling the <span class="term">OpenValue()</span> method or clicking the <span class="interface">Open</span> button in the text input area opens the regular list form, provided that the following conditions are met:<ul><li>The <span class="interface">In </span><span class="interface">list</span> editing mode is selected.</li><li>A regular list form exists and it is selected as a default or additional one.</li><li>Using regular forms in the managed application is allowed in this applied solution.</li><li>The list or object managed form that is used as a default or additional one is missing.</li></ul><p>In all other cases, this opens the object form.</p><p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>In the managed mode of the thick client, if the <span class="interface">In</span><span class="interface"> list </span>editing mode was selected, calling the <span class="term">OpenValue()</span> method or clicking the <span class="interface">Open</span> button in the text input area opened the managed list form.</td><td>To display configuration objects that have the <span class="interface">In </span><span class="interface">list</span> editing mode set, or for editing their elements, the system opens the regular list form. This behavior is more consistent than before.</td></tr><tr title="Версия 8.3.3" class="tag_20"><td><a name="115b93b6-4f67-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The following changes are implemented in the configuration comparison feature:<ul><li>The parent node of predefined data elements is excluded from the comparison.</li><li>Missing help data is considered identical to empty help data.</li><li>Additional properties of the <span class="term">ManagedForm</span> managed form element that make sense only in the 1C:Enterprise mode are excluded from the comparison.</li></ul></td><td>When configurations were compared:<ul><li>The node to which predefined data items were subordinate was included into the comparison.</li><li>Missing help data was considered different from empty help data.</li><li>Additional properties of the <span class="term">ManagedForm</span> managed form element that make sense only in the 1C:Enterprise mode were included into the comparison.</li></ul></td><td>The configuration comparison is perfomed as expected.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_1"><td><a name="4bf031aa-4ff6-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When a choice list is generated for form fields linked to data of <span class="term">EnumRef</span> type, it is based on the choice parameters and choice parameter links of the form element.<p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>When a choice list was generated for form fields linked to data of <span class="term">EnumRef</span> type, the choice parameters and choice parameter links were not taken into account.</td><td>The choice list generation for enumerations is uniform with other similar system features.</td></tr><tr title="Версия 8.3.3" class="compat tag_37 tag_1"><td><a name="98c642e2-4ffa-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For the <span class="term">InternetMailProfile</span> object, the <span class="term">SMTPAuthentication</span> property (which is obsolete) is set to <span class="term">SMTPAuthenticationMode</span><span class="term">.</span><span class="term">Default</span>.<p>This change is not implemented in version 8.2.16 compatibility mode. </p></td><td>For the <span class="term">InternetMailProfile</span> object, the obsolete property <span class="term">SMTPAuthentication</span> was set to <span class="term">SMTPAuthenticationMode</span><span class="term">.</span><span class="term">None</span>.</td><td>The default settings of the authentication method is the safest among those supported by the mail server.</td></tr><tr title="Версия 8.3.3" class="tag_37"><td><a name="20845ca6-4ffe-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>If the <span class="term">SMTPSecureAuthenticationOnly</span> property of the <span class="term">InternetMailProfile</span> object is set to <span class="term">TRUE</span>, authentication attempts are performed independently of other settings.<p>User authentication on the SMTP server is not performed in the following scenarios:</p><ul><li>The <span class="term">SMTPUser</span> property of the <span class="term">InternetMailProfile</span> object is an empty string.</li><li>The <span class="term">SMTPAuthentication</span> property of the <span class="term">InternetMailProfile</span> object is set to <span class="term">SMTPAuthenticationMode</span><span class="term">.None</span>.</li><li>The <span class="term">POP3BeforeSMTP</span> property of the <span class="term">InternetMailProfile</span> object is set to <span class="term">TRUE</span>.</li></ul><p>
</p></td><td>User authentication on the SMTP server was not performed if the name of the SMTP server user was not specified (the <span class="term">SMTPUser</span> property of the <span class="term">InternetMailProfile</span> object).</td><td>User authentication on the SMTP server can be performed using a POP3 server if the <span class="term">SMTPSecureAuthenticationOnly</span> property is not set. The value of the <span class="term">SMTPUser</span> property of <span class="term">InternetMailProfile </span>object does not affect this behavior. At the same time, the authentication is not performed if the mail server does not support the secure authentication methods.<p>When connecting to a mail server, you can exclude insecure authentication methods from the list of available ones.</p></td></tr><tr title="Версия 8.3.3" class="tag_116"><td><a name="75ec7dcc-5000-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>If a license acquisition dialog box appears at the start of the client application, the first page of the dialog box specifies which kind of license (server or client) the application requires.
A hyperlink to 1C:Licensing center contact information is displayed on the license registration pages and on the page that appears when license activation is not successful. A dialog box that displays 1C:Licensing center contact information is added.
When a user types a PIN code or a response from a licensing center operator in the license aсquisition dialog box, once they have completed a text field, the cursor moves to the next field automatically. <p> </p></td><td>If a license acquisition dialog box appeared at the start of the client application, the first page of the dialog box did not specify which kind of license (server or client) was not found.
The license registration pages and the page that appeared when license activation was not successful only contained information how to find 1C:Licensing center contacts in the printed documentation.
When a user typed a PIN code or a response from a licensing center operator in the license aсquisition dialog box, the cursor did not move to the next field automatically.</td><td>Improved usability of license acquisition dialog box.</td></tr><tr title="Версия 8.3.3" class="tag_26 tag_28"><td><a name="269ad077-500e-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The web client now supports text orientation in spreadsheet document cells.</td><td>The web client did not support text orientation in spreadsheet document cells.</td><td>Extended formatting capabilities for spreadsheet documents in the web client.</td></tr><tr title="Версия 8.3.3" class="tag_6"><td><a name="decf5e3b-5fb2-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When a cluster service is reassigned from one cluster manager to another, the service status is replicated to the new cluster manager and the service is shut down on the former cluster manager, which releases the resources used by the service.
The status is replicated for the following services: object locks, numbering, and background restructuring.
In the technological log, the <span class="term">&lt;SRVC</span><span class="term">&gt;</span> event is implemented. It describes the following operations with cluster services: starting, stopping, and various alerts. Descriptions of operations being executed are generated in the <span class="term">Descr</span> property.
Each cluster manager stores its session data in a dedicated directory. You can choose how a working process is selected when a new connection is created: by available performance or by available memory. If the selection is performed by available memory, either the working process that currently maintains connections to the infobase is used, or the working process that is running on the server and has the maximum amount of available memory.
In the cluster properties, the <span class="interface">Load balancing mode</span> property is implemented. For the <span class="term">IClusterInfo</span> object, the <span class="term">LoadBalancingMode</span> property is implemented.
For starting a background job, the working process that maintains the session that initiated the background job is selected with the highest priority (this rule is ignored if the selection is performed by available memory).
You can specify a priority for each assignment rule. If several identical assignment rules are found during assignment rule selection and all other conditions are equal, the rule with the highest priority is used. Assignment rules now have the <span class="interface">Priority</span> property. For the <span class="term">IAssignmentRule</span> object, the <span class="term">Priority</span> property is implemented. In the <span class="interface">cluster</span> mode of the server cluster administration utility (<span class="interface">rac</span>), the <span class="interface">load-balancing-mode</span> parameter is implemented for the <span class="interface">create</span> and <span class="interface">update</span> commands. Similar changes are implemented in the Java server administration API.
When determining available working process performance, the CPU load of the working server and the number of threads in the execution queue are taken into account, in addition to other factors.</td><td>In some cases, used resources were not released after the reassignment of services.
The status was not replicated for the following services: object locks, numbering, and background restructuring. In the technological log, there were no events that described operations with cluster services.
Data belonging to all sessions was stored in a single directory, which could lead to access collisions.
When a background job was created, the working process for handling the job was always selected by available performance.
If several identical assignment rules were found during assignment rule selection, the rule that was applied could not always be determined unambiguously.
When available working process performance was determined, the CPU load and the number of threads in the execution queue were not taken into account.</td><td>Increased fault tolerance of clusters. Improved quality and manageability of load balancing between cluster servers. A new setting ensures efficient memory usage when a cluster maintains a large number of infobases with a small number of sessions from each infobase. </td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="7bf1d0e9-5fc9-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For unavailable groups, colors of the title and border (line) are changed.</td><td>For unavailable groups, the title and border (line) had different colors.</td><td>The look of unavailable groups is uniform with the look of other unavailable elements.</td></tr><tr title="Версия 8.3.3" class="compat tag_23 tag_58 tag_110 tag_105 tag_144 tag_1"><td><a name="89a6fcb6-6073-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br><a href="#" onclick="onTagClick(this, 105); return false;">Data exchange</a>.<br><a href="#" onclick="onTagClick(this, 144); return false;">Mobile application</a>.<br></td><td>Predefined data is available for configuration objects included in separator contents in the <span class="interface">Independent and Shared</span> mode. Predefined items can be linked to any data elements of matching type. The linking is optional. If data elements are not linked, the predefined data is considered empty. For configuration objects that can contain predefined data, the <span class="term">PredefinedDataName</span> property is implemented. Support of predefined data items that refer to deleted predefined items is implemented. Identical references to predefined items are never generated, even for objects included in separator contents in the <span class="interface">Independent</span> mode, and even for items that belong to different areas. The <span class="term">GetPredefinedItemName</span>() method is declared deprecated is only supported for compatibility purposes. Predefined data is registered in exchange plans like any other data. You can manage creation and update of predefined data in the infobase using the new configuration object property <span class="term">PredefinedDataUpdate</span> and the new methods <span class="term">GetUpdatingPredefinedData()</span> and <span class="term">SetPredefinedDataUpdate</span><span class="term">()</span>. The global context method <span class="term">InitializePredefinedData()</span> is implemented. Using this method, you can create data objects for predefined items that are not linked to any data (in the current data area).
Access rights and restrictions are specified simultaneously for the <span class="term">Predefined</span> and <span class="term">PredefinedDataName</span> fields.
These features are also implemented for the mobile platform. The new access rights <span class="term">InteractiveDeletePredefinedData</span>, <span class="term">InteractiveSetDeletionMarkPredefinedData</span>, <span class="term">InteractiveClearDeletionMarkPredefinedData</span>, and <span class="term">InteractiveDeleteMarkedPredefinedData</span> are implemented. They specify whether editing of predefined data is allowed. <p>Restrictions for editing predefined data in charts of accounts and charts of calculation types are eliminated. Predefined data can be marked for deletion, and it can be completely deleted. A chart of accounts must be included into the contents of all separators that contain all extra dimensions used in the chart. The infobase restructuring process is modified. This change is not implemented in 8.3.2 compatibility mode.</p></td><td>Predefined data was not available for configuration objects included in separator contents in the <span class="interface">Independent and Shared</span> mode. Predefined data could not be linked to any existing data object. Each predefined item had identical references in all data areas. During data exchange in a distributed infobase, predefined data was replicated only together with applied solution configuration changes. Creation and update of predefined data were not available.</td><td>You can use predefined data in all separation modes. Predefined data management is more flexible than before.</td></tr><tr title="Версия 8.3.3" class="tag_96"><td><a name="d0b36fde-71d9-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>In the help topics, links to external resources are opened in the default web browser of the operating system.</td><td>In the help topics, links to external resources were opened in the built-in web browser of 1C:Enterprise.</td><td>Improved usability of viewing the resources that are opened by clicking links in the help topics.</td></tr><tr title="Версия 8.3.3" class="compat tag_96 tag_1"><td><a name="46d1c4a0-74f7-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>For new users, the interface mode is set to <span class="interface">Forms in tabs</span>, provided that the platform version compatibility mode is not used and the interface compatibility mode is set to <span class="term">Version82</span> or <span class="term">Version82TaxiAllowed</span>.</td><td>For new users, the interface mode was set to <span class="interface">Forms in separate windows</span>.</td><td>The <span class="interface">Forms in tabs</span> interface is the default option for new users. This interface mode provides better usability.</td></tr><tr title="Версия 8.3.3" class="tag_96"><td><a name="8421ae52-9b6d-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>For a text box in a managed form table, the drop-down list is always opened at the start of editing.</td><td>For a text box in a managed form table, the drop-down list was opened at the start of editing only if the editing was started using the mouse.</td><td>Quick access to the drop-down list is implemented for text boxes located in managed form tables.</td></tr><tr title="Версия 8.3.3" class="compat tag_58 tag_69 tag_1"><td><a name="b760b083-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>After deleting data from a data area (or deleting an infobase) by using the <span class="term">EraseInfoBaseData()</span> method (or the <span class="term">/EraseData</span> command-line option), the data area state matches the state that the data area had when it was accessed for the first time. In particular:<ul><li>Tables of enumerations are not modified.</li><li>If the version 8.3.2 or later compatibility mode is set, predefined data values revert to the values specified in Designer or to the default values. If the compatibility mode is disabled, predefined data items will be created on the first attempt to access them.</li><li>In the exchange plans, the values of <span class="term">ThisNode</span> element attributes revert to the default values.</li><li>Values of nonseparated constants revert to the default values, while values of separated constants are deleted.</li></ul></td><td>After deleting data from a data area (or deleting an infobase) by using the <span class="term">EraseInfoBaseData()</span> method (or the <span class="term">/EraseData</span> command-line option), the data area state did not match the state that the data area had when it was first accessed:<ul><li>Tables of enumerations were removed.</li><li>For nonseparated objects, the predefined data values were saved.</li><li>In the exchange plans, the values of <span class="term">ThisNode</span> element attributes were saved.</li><li>Constant values were preserved.</li></ul></td><td>After deleting data from a data area (or deleting an infobase) by using the <span class="term">EraseInfoBaseData()</span> method (or the <span class="term">/EraseData</span> command-line option), the state of the data area now reflects its initial state much better than it did in the previous platform versions. </td></tr><tr title="Версия 8.3.3" class="tag_170"><td><a name="6f1cf3fa-c148-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 170); return false;">Application appearance</a>.<br></td><td>New splash screens are implemented for Designer, client application, <span class="interface">Autorun</span> program, and the installation program.
The splash screen size (and the size of the applied solution splash screen template) is 600 x 255 pixels.</td><td>Splash screens that were used for various parts of the system had different looks. The size of the applied solution splash screen template was 305 x 110 pixels.</td><td>The new splash screens better fit the new user unterface.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_1"><td><a name="71e2a3ce-c38c-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When a value is entered or selected in a text box, it is converted to the text box value type, and then the value presentation is displayed in the text box.
This change is not implemented in 8.3.2 compatibility mode.</td><td>When a value was entered or selected in a text box, the resulting text displayed in the box might not match the entered or selected value.</td><td>The system behaves as expected. Eliminated incorrect system behavior.</td></tr><tr title="Версия 8.3.3" class="tag_14"><td><a name="fcd8ac0a-3184-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The message that is displayed before updating a client application using an insecure connection is clarified. </td><td>The message was not clear enough.</td><td>The message describes the situation more clearly.</td></tr></table><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4288e49a-1835-11e2-b237-e61f135f174b">Changes that require modification of configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.3" class="tag_133"><td><a name="6e0d0e8a-2ef6-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br></td><td>Only access rights that have nondefault values are included in dump files. The default values are defined by the <span class="interface">Set rights for new objects</span> and <span class="interface">Set rights for attributes and tabular sections by default</span> properties. Values of these properties are default values for access rights to metadata objects and access rights to attributes and tabular sections respectively.</td><td>All access rights were included in dump files, including those having default values.</td><td>Improved performance of dumping configurations to files. Reduced size of dump files.</td></tr><tr title="Версия 8.3.3" class="tag_133 tag_23"><td><a name="e869236b-2d9a-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 133); return false;">Dumping/loading configurations to files</a>.<br><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>When dumping a configuration to XML files, English descriptions of document journal selection types follow this convention: <span class="term">DocumentJournalSelection.DocumentJournalName</span>.</td><td>When dumping a configuration to XML files, English descriptions of document journal selection types followed this convention: <span class="term">DocumentJournalsManager.DocumentJournalName</span>.</td><td>Type names are uniform.</td></tr><tr title="Версия 8.3.3" class="compat tag_78 tag_1"><td><a name="455985ac-3aca-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br></td><td>When one or multiple files are obtained from the infobase using the <span class="term">GetFile()</span> or <span class="term">GetFiles()</span> method, the <span class="term">View</span> right is checked for the attributes that store the file data. If the <span class="term">GetFiles()</span> method is used and access to at least one the requested files is denied, the entire operation is canceled.
This change is not implemented in 8.3.2 compatibility mode.</td><td>
<p>When one or multiple files are obtained from the infobase using the <span class="term">GetFile()</span> or <span class="term">GetFiles()</span> method, the <span class="term">View</span> right was not checked for the attributes that stored the file data.</p></td><td>The behavior of the <span class="term">GetFile()</span> and <span class="term">GetFiles()</span> methods is uniform with other system features.</td></tr><tr title="Версия 8.3.3" class="compat tag_20 tag_1"><td><a name="9e6a5d32-3ad8-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Before database configuration update, the check whether the <span class="term">Ref</span> attribute is present is performed for tabular sections of catalogs, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks. If this attribute exists, restructuring cannot be performed.
This change is not implemented in 8.3.2 compatibility mode.</td><td>Before database configuration update, the check whether the <span class="term">Ref</span> attribute is present was not performed for tabular sections of catalogs, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks.</td><td>Eliminated this type of errors in applied solutions.</td></tr><tr title="Версия 8.3.3" class="tag_6"><td><a name="1be36fd5-3ea5-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>In the server cluster administration utility (<span class="interface">rac</span>), the <span class="term">name</span> and <span class="term">cluster-port</span> options of the <span class="term">server update</span> command are removed. In the Java-based administration server interface, the <span class="term">setName()</span> and <span class="term">setClusterMainPort()</span> methods are removed from the <span class="term">IWorkingServerInfo</span> interface.
In the server cluster administration utility (<span class="interface">rac</span>), the <span class="term">security-level</span> option of the <span class="term">infobase update</span> command is removed. In the Java-based administration server interface, the <span class="term">setSecurityLevel()</span> method is removed from the <span class="term">IInfoBaseInfo</span> interface.</td><td>In the server cluster administration utility (<span class="interface">rac</span>), the <span class="term">name</span> and <span class="term">cluster-port</span> options were available for the <span class="term">server update</span> command. The values specified in these options were never used and no error messages were displayed when the command was run with these options. <p>In the Java-based administration server interface, the <span class="term">IWorkingServerInfo</span> interface included the <span class="term">setName()</span> and <span class="term">setClusterMainPort()</span> methods. These methods did not perform any actions and there were no error messages when these methods were called.</p><p>In the server cluster administration utility (<span class="interface">rac</span>), the <span class="term">security-level</span> option was available for the <span class="term">infobase update</span> command. The value specified in this option was never used and no error messages were displayed when the command was run with this option.</p><p>In the Java-based administration server interface, the <span class="term">IInfoBaseInfo</span> interface included the <span class="term">setSecurityLevel()</span> method. This method did not perform any actions and there were no error messages when this method was called.</p><p> </p></td><td>Options of the administration utility (<span class="interface">rac</span>) and the set of Java-based administration server interface methods match the set of actions that the system can actually perform. Working server parameters can be specified during the registration of the working server in the cluster.
The infobase security level can be specified while adding the infobase to the cluster.</td></tr><tr title="Версия 8.3.3" class="tag_10 tag_6"><td><a name="e9db313d-71c2-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>The server cluster administration utility (<span class="interface">rac</span>) from the previous platform versions (8.3.1 and 8.3.2) cannot be connected to the administration server (<span class="interface">ras</span>) of the current platform version.
The server cluster administration utility (<span class="interface">rac</span>) from the current platform version cannot be connected to the administration server (<span class="interface">ras</span>) of the previous platform versions (8.3.1 and 8.3.2).</td><td>The server cluster administration utility (<span class="interface">rac</span>) could be connected to the administration server (<span class="interface">ras</span>) of any platform version.</td><td>The server cluster administration utility (<span class="interface">rac</span>) and the administration server (<span class="interface">ras</span>) that have incompatible versions cannot interact with each other.</td></tr><tr title="Версия 8.3.3" class="tag_78 tag_15"><td><a name="b1aa6011-3eb3-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>You can get a file mask that describes all files for the operating system where 1C:Enterprise runs. The following methods are implemented: <span class="term">GetAllFilesMask()</span>, <span class="term">GetClientAllFilesMask()</span>, and <span class="term">GetServerAllFilesMask()</span>.</td><td>This feature was not provided.</td><td>You can write a source code that processes files and does not depend on the operating system where 1C:Enterprise runs.</td></tr><tr title="Версия 8.3.3" class="tag_78 tag_15"><td><a name="23f78db4-4f35-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>You can get a file path separator for the operating system where 1C:Enterprise runs. The following methods are implemented: <span class="term">GetPathSeparator()</span>, <span class="term">GetClientPathSeparator()</span>, and <span class="term">GetServerPathSeparator()</span>.</td><td>This feature was not provided.</td><td>You can write a source code that processes files and does not depend on the operating system where 1C:Enterprise runs.</td></tr><tr title="Версия 8.3.3" class="compat tag_41 tag_1"><td><a name="b0bfd8ad-42a8-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 41); return false;">ZIP archive operations</a>.<br></td><td>The behavior of the <span class="term">ZipFileWriter</span> object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in a source directory:<ul><li>If a file name does not contain wildcard characters (<span class="interface">?</span> or <span class="interface">*</span>), the file is added to the archive.</li><li>If a file name contains the wildcard characters (<span class="interface">?</span> or <span class="interface">*</span>), an exception is generated.</li></ul><p>The behavior of the <span class="term">ZipFileReader</span> object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in the directory containing the archive file, the archive is opened in the read-only mode.
This change is not implemented in 8.3.2 compatibility mode.</p></td><td>During the creation of an archive using the <span class="term">ZipFileWriter</span> object, if the user under whose account the system was running did not have rights for viewing the list of files in the source directory, the files were not added to the archive and the resulting archive did not contain expected data.
The archive could not be opened using the <span class="term">ZipFileReader</span> object if the user under whose account the system was running did not have rights for viewing the contents of the directory containing the archive file.</td><td>The behavior of <span class="term">ZipFileWriter</span> and <span class="term">ZipFileReader</span> objects became more logical. Decreased chance of creating archive files with incorrect data.</td></tr><tr title="Версия 8.3.3" class="compat tag_67 tag_1"><td><a name="c56862ed-42af-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>The compatibility mode with 1C:Enterprise versions 8.3.2 and earlier is implemented for the configuration repository. If the compatibility mode is disabled:<ul><li>New configuration repository database structure is used.</li><li>The optimized method for interaction with configuration repository server is used.</li></ul><p>If the compatibility mode is disabled, only 1C:Enterprise version 8.3.3 or later can be used to access the repository.
The command line option <span class="term">ConfigurationRepositoryClearCache</span> is implemented in Designer. It is intended for clearing the local configuration cache.
The option to stop the execution of repository operations by pressing <span class="interface">Ctrl+Break</span> is implemented (this does not depend on repository compatibility mode).</p></td><td>A different configuration repository database structure was used. Some repository operations were performed inefficiently.
The Designer command line option <span class="term">ConfigurationRepositoryClearCache</span> was not available. Pressing <span class="interface">Ctrl+Break</span> did not stop the execution of repository operations.</td><td>Improved performance when accessing a configuration repository server.</td></tr><tr title="Версия 8.3.3" class="tag_23"><td><a name="8b298533-436b-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>The <span class="term">Filter</span> property of the parameter structure that is passed to the formal parameter of the <span class="term">GetChoiceData()</span> method or the <span class="term">ChoiceDataGetProcessing</span> handler can contain elements with values of <span class="term">ValueList</span> and <span class="term">Array</span> types. The system applies the <span class="interface">In </span><span class="interface">list</span> comparison type to such values (it is the same comparison type that is used with <span class="term">FixedArray</span> values).</td><td>The <span class="term">Filter</span> property of the parameter structure that is passed to the formal parameter of the <span class="term">GetChoiceData()</span> method or the <span class="term">ChoiceDataGetProcessing</span> handler could not contain elements with values of <span class="term">ValueList</span> and <span class="term">Array</span> types.</td><td>Extended filtering options when retrieving selection data. Removed unnecessary data conversions.</td></tr><tr title="Версия 8.3.3" class="compat tag_120 tag_1"><td><a name="94c5b7e5-48fa-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 120); return false;">Background and scheduled jobs</a>.<br></td><td>Background and scheduled jobs can now run in the file mode without using the <span class="term">ProcessJobs()</span> global context method. The <span class="term">ProcessJobs()</span> method does not perform any actions. Background and scheduled jobs are executed in one of the client applications connected to the infobase. The behavior of background and scheduled jobs has some specifics (see the full list in the documentation):<ul><li>All scheduled jobs are executed in a dedicated client application (by default, it is the first session started).</li><li>A background job started by a session is executed by the client application that started it.</li><li>Within a client application, a single background job is performed at a time (this includes scheduled jobs).</li></ul><p>For specifying the client application that will execute scheduled jobs, the <span class="term">AllowExecuteScheduledJobs</span> command-line option is implemented for the client application. The <span class="interface">Background jobs</span> check box, which is located in the Autoattach dialog box in Designer, affects the attachment to background jobs both at server and at client.</p><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>The only way to run background and scheduled jobs in the file mode involved using the <span class="term">ProcessJobs()</span> global context method.<p>The <span class="interface">Background jobs</span> check box, which is located in the Autoattach dialog box in Designer, only affected attachment to background jobs at server.</p></td><td>Reduced developer efforts during implementation of background and scheduled job execution in the file mode.</td></tr><tr title="Версия 8.3.3" class="compat tag_23 tag_58 tag_1"><td><a name="f79ed94b-491b-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>In order to successfully read or write separated constants using the <span class="term">Constants</span> method of the global context, values of all shared separators that split the constant must be specified. Otherwise an exception is generated.
This change is not implemented in 8.3.2 compatibility mode.</td><td>Reading or writing separated constants using the <span class="term">Constants</span> method of the global context was performed successfully even when values of all combined separators that split the constant were not specified.</td><td>The feature is uniform with other similar platform features.</td></tr><tr title="Версия 8.3.3" class="tag_15"><td><a name="3f6ba89d-4922-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The <span class="interface">config_system</span> configuration utility for Linux is removed from the distribution kit.
The search for MS Core Fonts required by the platform is performed automatically in the following directories:<ul><li><span class="interface">/usr/share/fonts/truetype/msttfcorefonts</span></li><li><span class="interface">/usr/share/fonts/msttfcorefonts</span></li><li><span class="interface">$HOME/.fonts</span></li></ul><p>The system automatically searches for required dynamic libraries when functions from these libraries are used.
If the required font or dynamic library is not found, an error message is displayed.
The operating system setup instructions for Linux are provided in the documentation.</p></td><td>The <span class="interface">config_system</span> configuration utility for Linux was included in the distribution kit. If required fonts or dynamic libraries were missing, this was not detected directly and could lead to various errors or unexpected behavior. The operating system setup instructions for running 1C:Enterprise on Linux were not provided in the documentation.</td><td>Simplified operating system for running 1C:Enterprise on Linux. Improved issue diagnostics.</td></tr><tr title="Версия 8.3.3" class="compat tag_110 tag_45 tag_42 tag_82 tag_1"><td><a name="1d64700f-49b5-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Access rights for autogenerated period fields (<span class="term">YearPeriod</span>, <span class="term">HalfYearPeriod</span>, <span class="term">QuarterPeriod</span>, <span class="term">MonthPeriod</span>, <span class="term">TenDaysPeriod</span>, <span class="term">DayPeriod</span>, <span class="term">HourPeriod</span>, and <span class="term">SecondPeriod</span>) in virtual tables of accumulation and accounting registers are obtained from the corresponding access rights of the standard <span class="term">Period</span> attribute.<p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>Access rights for autogenerated period fields in virtual tables of accumulation and accounting registers depended on the state of the <span class="interface">Set rights for attributes and tabular sections by default</span> check box. If the property was set to True, the user was granted the right.</td><td>Access right management is more consistent.</td></tr><tr title="Версия 8.3.3" class="tag_171"><td><a name="5e12a7bc-49b8-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 171); return false;">Development methodology</a>.<br></td><td>The documentation includes a section with recommendations for developing cross-platform applied solutions.</td><td>The documentation did not include recommendations for developing cross-platform applied solutions.</td><td>Recommendations for creating the cross-platform applied solutions at minimal costs are available.</td></tr><tr title="Версия 8.3.3" class="compat tag_52 tag_1"><td><a name="9867c985-49be-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>Managed transaction locks can be set by object attributes. For specifying attributes whose values are taken into account when setting transaction locks, the <span class="term">DataLockFields</span> property is implemented for the following configuration objects:<ul><li>Catalogs</li><li>Documents</li><li>Charts of characteristic types</li><li>Charts of calculation types</li><li>Business processes</li><li>Tasks</li><li>Charts of accounts</li><li>Exchange plans</li></ul><p>While objects are being written or deleted, they will be temporarily locked by all attributes specified in the <span class="term">DataLockFields</span> property and the <span class="term">Ref</span> field. For objects being written, attribute values available at the beginning of the writing process are used. For objects being deleted, current attribute values are used.</p><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>Managed locks for the following objects could be set only by the standard attribute <span class="term">Ref</span>: catalog, document, chart of characteristic types, charts of calculation types, business process, task, chart of accounts, and exchange plan.</td><td>Extended managed lock functionality. When you need to perform a coordinated action on a set of objects filtered by a specific attribute and at the same time prohibit the creation of new objects that match the filter, you have the option to set a lock by the attribute, rather than lock the entire set of objects of the given type. </td></tr><tr title="Версия 8.3.3" class="compat tag_52 tag_1"><td><a name="86939261-5bca-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>Using the <span class="term">DataLock</span> object outside of a transaction or in the automatic data lock control mode raises an exception.<p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>Using the <span class="term">DataLock</span> object outside of a transaction or in the automatic data lock control mode did not raise an exception and did not lead to any locks.</td><td>Situations when the system seemed to work properly but actually did not perform any actions are eliminated.</td></tr><tr title="Версия 8.3.3" class="tag_70 tag_10"><td><a name="1329a1e5-49da-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can specify whether the latest 1C:Enterprise updates are installed automatically. This is configured using the following new parameters:<ul><li>The <span class="term">AppAutoInstallLastVersion </span>command-line option of the non-interactive startup utility.</li><li>The <span class="term">AppAutoInstallLastVersion </span>parameter in the <span class="interface">1CEStart.cfg</span> and <span class="interface">1CESCmng.cfg</span> configuration files. </li></ul><p>When the client application version does not match the 1C:Enterprise server version, or when a specific 1C:Enterprise version is required to access an infobase, the new version is always installed unless the required version is already present at the client computer. The <span class="interface">Install new application versions automatically</span> check box is added to the infobase startup settings dialog box.</p></td><td>The non-interactive startup utility installed the latest 1C:Enterprise version, except the following scenarios:<ul><li>In the startup utility configuration dialog box, a specific 1C:Enterprise version is selected for all infobases. </li><li>A specific version of the client application or interactive startup utility is started. </li></ul></td><td>In the non-interactive startup utility, you have the option to disable the search and installation of the latest 1C:Enterprise version in the event when the required version is already installed at the client computer, but later versions are available and not yet installed. You still have the option to install any 1C:Enterprise version that you need.</td></tr><tr title="Версия 8.3.3" class="compat tag_20 tag_1"><td><a name="b8a81803-49df-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>During the database configuration update, the check for matches between the names of common pictures and the names of pictures from the picture library is performed. If matches are found, the message informing that the names are not unique is displayed and the database configuration is not updated.
This change is not implemented in 8.3.2 compatibility mode.</td><td>During the configuration update, the check for matches between the names of common pictures and the names of pictures from the picture library was not performed.</td><td>The following scenario is no longer possible: when a common picture name matches a picture name from the picture library, in 1C:Enterprise mode the picture from the library is displayed instead of the common picture.</td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="91328deb-4a8a-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The <span class="term">Close()</span> method called on an additional form closes this form. If this form is active, the default form is made active, otherwise no additional actions are performed.
The <span class="term">IsOpen()</span> method called on an additional form that is open returns <span class="term">True</span>. If the user switched to another additional or default form after opening the additional form, the <span class="term">IsOpen()</span> method still returns <span class="term">True.</span></td><td>If the <span class="term">Close()</span> method was called on an additional form, an error was generated and the form was not closed.
The <span class="term">IsOpen()</span> method called on an additional form that was open returned <span class="term">False</span>.</td><td>The system behaves as expected.</td></tr><tr title="Версия 8.3.3" class="compat tag_56 tag_1"><td><a name="2204d65b-4a93-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>During the generation of the configuration data model, for all properties of the configuration data model that have more than one type in their type descriptions, the <span class="interface">C</span><span class="interface">an be empty </span>property (the <span class="term">nillable</span> attribute of the XSD schema) is set to <span class="term">True</span>, otherwise the property value is not set.<p>If you specify the<span class="interface"> Any ref </span>type for an attribute (such as a resource or dimension) in Designer, the type is converted into one of the following in the configuration data model:</p><ul><li>The <span class="term">{http://v8.1c.ru/8.1/data/enterprise}AnyRef</span> type if the configuration includes multiple metadata objects that form the <span class="interface">Any ref</span> type.</li><li>The type that corresponds to reference data type if the configuration includes a single metadata object that forms the <span class="interface">Any ref </span>type.</li></ul><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td>During the generation of the configuration data model, for all properties of the configuration data model that have more than one type in their type descriptions, the value of the <span class="interface">C</span><span class="interface">an be empty </span>property (the <span class="term">nillable</span> attribute of the XSD schema) was never set.<p>If you specified the <span class="interface">Any ref</span> type for an attribute (such as a resource or dimension) in Designer, it was always converted to the <span class="term">{http://v8.1c.ru/8.1/data/enterprise}AnyRef</span> type in the configuration data model.</p></td><td>The XML data model generation for the <span class="interface">Any ref</span> type is uniform with other types.</td></tr><tr title="Версия 8.3.3" class="compat tag_21 tag_1"><td><a name="419fa03d-4b56-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>Full-text search indexes include the number of 1C:Enterprise version that was used to create them. If the full-text search index is created in version 8.3.3 or later while the compatibility mode is disabled, and then the infobase is accessed using version 8.3.2 or earlier, the search by presentations of configuration objects is not performed.</td><td>Full-text search indexes did not include the number of 1C:Enterprise version that was used to create them.</td><td>Reverse compatibility of full-text search indexes is implemented. The full-text search indexes are now compatible with earlier 1C:Enterprise versions that have different index format.</td></tr><tr title="Версия 8.3.3" class="tag_155 tag_172"><td><a name="94dbd816-4e79-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 155); return false;">Web services</a>.<br><a href="#" onclick="onTagClick(this, 172); return false;">Web links</a>.<br></td><td>You can specify proxy server parameters in constructors of the <span class="term">WSProxy</span> and <span class="term">WSDefinitions</span> objects and in the <span class="term">CreateWSProxy()</span> method.<p>The former constructor and method syntax is supported for compatibility purposes.</p></td><td>Proxy server parameters could not be specified when <span class="term">WSProxy</span> or <span class="term">WSDefinitions</span> objects were created or when the <span class="term">CreateWSProxy</span><span class="term">()</span> method was called. The proxy server settings could be specified only by editing the <span class="interface">inetcfg.xml</span> configuration file.</td><td>Extended web service support functionality: the proxy server settings can be specified in the configuration settings rather than by editing the configuration file.</td></tr><tr title="Версия 8.3.3" class="compat tag_104 tag_1"><td><a name="3a6e9e2a-4f64-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>If the privileged get mode is set for a functional option, getting the functional option value in the safe mode does not require checking the access rights.
This change is not implemented in 8.3.2 compatibility mode.</td><td>If the privileged get mode was set for a functional option, getting the functional option value in the safe mode included checking the access rights. </td><td>Eliminated the issues related to accessing functional options in the safe mode. The data provided by a functional option that has privileged get mode set is considered safe enough and can be retrieved in the safe mode.</td></tr><tr title="Версия 8.3.3" class="tag_51"><td><a name="71198b0c-5010-11e2-bb40-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>If an object being tested cannot perform the required action, an exception is raised (except methods that search for objects, which never raise this kind of exception).</td><td>It was impossible to detect situations when objects being tested could not perform the required actions. </td><td>Better error detection during automated testing.</td></tr><tr title="Версия 8.3.3" class="tag_51"><td><a name="aa68c41c-5bf3-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 51); return false;">Automated testing</a>.<br></td><td>Methods that perform actions on objects being tested do not wait for action completion. Methods that previously returned the execution results now raise exceptions when the actions cannot be performed.</td><td>Methods that performed actions on objects being tested waited for action completion. In some cases such methods returned result codes.</td><td>Better error detection during automated testing.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_1"><td><a name="548952ee-5ef2-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For managed form fields, the <span class="term">DropListButton</span> property is implemented. It describes whether the button that opens the drop-down list is present. Depending on the type of the attribute linked to the text box, the list can contain the following data:<ul><li>Choice list - from the choice list property of the text box.</li><li>Quick choice list - for the quick choice property of the configuration object.</li><li>Choice values – values matching the text entered by the user.</li><li>Choice history - for reference fields and enumeration fields. Note that the history is not available for fields that contain configuration objects with the quick choice option enabled.</li></ul><p>During the text input in a text box, the platform displays unique items from all these lists (if they are available for the text box).
For managed form fields, the <span class="term">ChoiceButtonRepresentation</span> property is implemented. It describes whether the button that opens the choice form is present in the field.
The <span class="term">DropListButton</span> property of managed form fields is no longer available; it is left for compatibility purposes. The <span class="term">StartListChoice</span> event of text box objects is never called.
This change is not implemented in 8.3.2 compatibility mode.</p></td><td>The <span class="term">DropListButton</span> property was available for managed form fields. When a user started selecting an item from the list, the the <span class="term">StartListChoice</span> event was generated. Developers could not control whether the choice form could be opened from the choice list.</td><td>The choice list is designed to allow users to select values quickly, without opening the choice form, whenever possible. For that, the choice list contains data that helps users to select a value for a text box:<ul><li>History of choices in the fields of the given type (with the given parameters)</li><li>Choice values</li><li>Quick choice list, and so on</li></ul></td></tr><tr title="Версия 8.3.3" class="tag_28"><td><a name="1721726f-704a-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>In the web client for iPad, only the <span class="interface">Forms in tabs</span> mode without modal windows and the <span class="interface">Taxi</span> interface are supported. The <span class="term">webclientmode</span> command-line parameter is no longer supported. Standard gestures for zooming in and out are now supported.
Form items with content that can be scrolled have scroll bars.</td><td>In the web client for iPad, modal windows were supported with some limitations, and the <span class="interface">Forms in tabs</span> mode was not supported. The <span class="term">webclientmode</span> command-line parameter was supported. Standard gestures for zooming in and out were not supported. Form items never had scroll bars.</td><td>Configuration tuning is no longer required to run applications on iPad (provided that you switch to the mode that does not use modal windows). In earlier versions of the platform, the developer had to remove a part of functionality to make an application compatible with iPad because modal calls were supported with limitations.</td></tr><tr title="Версия 8.3.3" class="compat tag_115 tag_86 tag_1"><td><a name="7c32df17-7101-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>Enhanced window blocking technology introduces innovative approach to window modality. Blocking windows are used instead of modal windows, while modal windows are supported for compatibility purposes.
It is recommended that you replace all modal windows with blocking windows in your applied solutions, and use new platform methods that do not create modal windows.
A call of a modal form is broken down into one or more separate calls: the first call opens a blocking form instead of a modal one and the the other one contains a callback procedure that is called by the platform when a form operation is complete (it includes getting the return value).
Applied solutions designed for iPad must support the blocking windows technology.
The <span class="term">ModalityUseMode</span> configuration property is implemented, it defines the modal window usage mode. In the extended configuration check, the search for methods related to modal windows is implemented. You can also perform this check from the command line by using the <span class="term">CheckUseModality</span> option of the <span class="term">ExtendedModulesCheck</span> command-line parameter.
The <span class="term">NotifyDescription</span> object is implemented, it passes the callback procedure description to platform methods that open blocking windows. The global context method <span class="term">ExecuteNotifyProcessing()</span> is implemented.
For the <span class="term">FormWindowOpeningMode</span> system enumeration, the <span class="term">LockWholeInterface</span> value is implemented.
For managed forms, command interface commands, and common modules, the <span class="term">ThisObject</span> property is implemented. This property is not supported in version 8.3.2 compatibility mode.
The global context method <span class="term">OpenForm()</span> is modified.
The following global context methods are implemented: <span class="term">ShowQueryBox()</span>, <span class="term">ShowValue()</span>, <span class="term">ShowMessageBox()</span>, <span class="term">ShowInputDate()</span>, <span class="term">ShowInputValue()</span>, <span class="term">ShowInputString()</span>, <span class="term">ShowInputNumber()</span>, <span class="term">BeginInstallAddIn()</span>, <span class="term">BeginInstallFileSystemExtension()</span>, <span class="term">BeginInstallCryptoExtension()</span>, and <span class="term">BeginPutFile()</span>.
For objects <span class="term">StandardPeriodEditDialog</span>, <span class="term">FormatStringWizard</span>, <span class="term">FontChooseDialog</span>, <span class="term">ColorChooseDialog</span>, and <span class="term">ScheduledJobDialog</span> the <span class="term">Show()</span> method is implemented. For the <span class="term">DataCompositionDetailsProcess</span> object, the <span class="term">ShowChooseAction()</span> method is implemented.
For the <span class="term">ValueList</span> object, the methods <span class="term">ShowCheckItems()</span> and <span class="term">ShowChooseItem()</span> are implemented.
For the <span class="term">ManagedForm</span> object, the <span class="term">Open()</span> method is modified, and the methods <span class="term">ShowChooseFromMenu()</span> and <span class="term">ShowChooseFromList()</span> are implemented.
For the <span class="term">ManagedForm</span> object, the <span class="term">OnCloseNotifyDescription</span> property is implemented.
The <span class="term">ThisForm</span> property of the <span class="term">ManagedForm</span> object is removed but supported for compatibility purposes.
The system enumeration value <span class="term">PostingModeUse.Ask</span> is supported for managed forms only in version 8.3.2 compatibility mode.</td><td>In the web client on iPad, the modal window support was limited, while modal windows were widely used in applied solutions and in the system part of the interfaces.</td><td>The web client meets the modern web technology standards. Removed limitations on modal window usage in the web client on iPad.
Configuration modification is required for applied solutions intended to run in the web client on iPad.</td></tr><tr title="Версия 8.3.3" class="tag_17"><td><a name="d0b36fdd-71d9-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>The resolution of the event time output to the technological log is increased to 1 microsecond. The count of microseconds in technological log event time has six digits.
The <span class="term">DurationUs</span> property is implemented. It contains the event duration measured in microseconds. For compatibility purposes, filtering by <span class="term">Duration</span> properties is supported.</td><td>The resolution of the event time output to the technological log was equal to 100 microseconds. The count of microseconds in the technological log had four digits.
Only the <span class="term">Duration</span> property was available in the technological log. It contained the event duration measured in hundreds of microseconds.</td><td>Decreased chance of the time counter overflow that occurred when the count of technological log events exceeded 10 000 events per second. One second can now contain up to 1 000 000 events of the technological log.
It is recommended that you use the <span class="term">DurationUs</span> property instead of the <span class="term">Duration</span> property.</td></tr><tr title="Версия 8.3.3" class="tag_28 tag_29"><td><a name="b760b07d-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>The following browsers are no longer supported:<ul><li>Microsoft Internet Explorer version 7.0;</li><li>Safari for Windows;</li><li>Mozilla Firefox version 16 and earlier for Windows and Linux.</li></ul></td><td>The following browsers were supported:<ul><li>Microsoft Internet Explorer version 7.0;</li><li>Safari for Windows;</li><li>Mozilla Firefox version 16 and earlier for Windows and Linux.</li></ul></td><td>Improved web client stability because rarely used browsers with errors and non-standard behavior are no longer supported.</td></tr><tr title="Версия 8.3.3" class="tag_15"><td><a name="b760b07e-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The platform supports <span class="term">XBase</span> objects on 64-bit Linux operating systems</td><td>The platform did not support <span class="term">XBase</span> objects on 64-bit Linux operating systems</td><td>Operations with <span class="interface">.dbf</span> files are now available on all supported architectures, except the mobile platform.</td></tr><tr title="Версия 8.3.3" class="tag_43"><td><a name="b760b07f-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 43); return false;">Dynamic lists</a>.<br></td><td>The <span class="term">DataVersion</span> field is removed from the list of available fields of dynamic list settings.</td><td>The <span class="term">DataVersion</span> field was included in the list of available fields of dynamic list settings.</td><td>The field that was erroneously added to the list of available fields of dynamic list settings is now removed from the list.</td></tr><tr title="Версия 8.3.3" class="tag_110"><td><a name="b760b082-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 110); return false;">Access rights</a>.<br></td><td>Managed forms only display data retrieved using "." (dot) if the user has access rights for all parts of the full path to the data.
If they do not have the rights, the item linked to this data is not displayed on the form.</td><td>If a user did not have access rights for all parts of the full path to data retrieved using "." (dot), the item linked to the data was displayed in the form, but it did not contain any data.</td><td>When accessing data using "." (dot), the form item linked to the data is not displayed on the form if the user does not have access rights for all parts of the full path to the data.</td></tr><tr title="Версия 8.3.3" class="tag_10"><td><a name="4f6ce7a3-becf-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>In the Java API for server administration, the value of the <span class="term">RuleType</span> property of the <span class="term">AssignmentRuleInfo</span> object matches the value of the <span class="term">RuleType</span> property of the <span class="term">IAssignmentRule</span> object in the server cluster administration tools that use COM connection.</td><td>The values of the <span class="term">RuleType</span> properties differed in the Java API for server administration and in the server administration tools that used COM connection.</td><td>The server cluster administration tools are unified.</td></tr><tr title="Версия 8.3.3" class="tag_37"><td><a name="24df460f-c444-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>The OpenID pass-through authentication protocol implementation is revised. The implementation complies with the Direct Identity version 2.0 mode of the OpenID protocol.
The format of the OpenID provider address in the <span class="interface">default.vrd</span> file is modified (the <span class="term">url</span> attribute of the <span class="term">rely</span> item): <span class="interface">httрs://&lt;address of the OpenID provider infobase&gt;/e1cib/oid2op</span>. The default authentication lifetime is 24 hours. The maximum authentication lifetime is 168 hours.
The protocol for interaction between the relying party and the OpenID provider is modified.
In the authentication dialog box, you can disable storing authentication data.
For the web client, a dialog box for entering the user name and password at the OpenID provider side is implemented.</td><td>The protocol implementation did not fully comply with the Direct Identity version 2.0 mode of the OpenID authentication protocol. The OpenID provider address in the <span class="interface">default.vrd</span> file was as follows: <span class="interface">httрs://&lt;address of the OpenID provider infobase&gt;/e1cib/oida</span>. The default authentication lifetime was 1 week. The maximum authentication lifetime was not limited. In the web client, there was no dialog box for entering the user name and password at the OpenID provider side. </td><td>The OpenID pass-through authentication protocol complies with the specification.</td></tr><tr title="Версия 8.3.3" class="tag_11 tag_28"><td><a name="b8ad7789-2a75-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The add-in technology now supports Mozilla Firefox browser version 22.0 and later. You can use add-in adapters for Mozilla Firefox 22.0 in the later versions of the web browser without recompiling the adapters.<p>For add-ins intended for use with all supported Mozilla Firefox versions, you have to add several add-in versions to the archive:</p><ul><li>For Mozilla Firefox version 18.0 or earlier</li><li>For Mozilla Firefox versions 19.0 to 21.0</li><li>For Mozilla Firefox version 22.0 or later</li></ul><p>It is recommended that you specify only the minimum version of the web browser in the add-in manifest file.</p><p>Documentation on creating add-ins is updated (<a href="http://1c-dn.com/library/add_in_creation_technology/" target="_blank">read more</a>). Examples are added, new versions of adapters for web browsers.</p><p>Adapters for Mozilla Firefox versions that are no longer supported by the developer (versions 3.6, 4.0, and 5.0) are removed.</p></td><td>The add-in technology did not support Mozilla Firefox browser version 22.0 or later.</td><td>The add-in technology now supports new versions of Mozilla Firefox browser (version 22.0 or later).</td></tr><tr title="Версия 8.3.3" class="tag_115 tag_21"><td><a name="e6aa040c-4b41-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 21); return false;">Full-text search</a>.<br></td><td>When a choice list is generated for the "input by string" feature (for reference configuration objects), the following options are available:<ul><li>Full-text search</li><li>Search by substring or by the beginning of the string</li><li>Instant or background search</li></ul><p>You can specify each of these options in Designer, in the configuration object properties.
The full-text search is performed only among the configuration object attributes that are selected in the "input by string" options of the configuration object. If a filter is applied during the input by string, the filter is converted (whenever possible) to a full-text search query in order to increase the search performance. </p><p>For external data source tables, you can only select the search modes (by substring or by beginning of the string, and instant or background).
In the file mode, the background search can be performed only when any other background or scheduled job is not being executed.
For the <span class="term">AutoComplete</span> and <span class="term">TextEditEnd</span> event handlers, the formal option <span class="term">Parameters</span> is implemented. It contains settings for getting choice data and allows you to manage this process by changing the properties of the structure that is passed in this parameter.</p></td><td>The following options were not available in the "input by string" feature:<ul><li>Full-text search</li><li>Search by substring or by the beginning of the string</li><li>Instant or background search</li></ul><p>The full-text search and search by substring were available in <span class="term">ChoiceDataGetProcessing</span> handlers.</p></td><td>New standard options for the "input by string" feature in text boxes:<ul><li>Full-text search</li><li>Search by substring (as an alternative to the search by the beginning of the string)</li><li>Background search (the search is running while the user is typing the search string)</li></ul></td></tr></table><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4288e49b-1835-11e2-b237-e61f135f174b">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.3" class="compat tag_0 tag_1"><td><a name="bb57dca5-2296-11e2-977c-e61f135f174b"></a>The name of calculating register recalculation manager type is changed.
This change is not implemented in version 8.3.2 compatibility mode.</td><td><span class="term">CalculationRegisterRecalcs</span><span class="term">.&lt;Calculation register name</span><span class="term">&gt;</span>
</td><td><span class="term">RecalculationManager</span><span class="term">.&lt;</span><span class="term">Calculation register name</span><span class="term">&gt;</span>
</td></tr><tr title="Версия 8.3.3" class="compat tag_0 tag_1"><td><a name="3ca8140d-324f-11e2-977c-e61f135f174b"></a>English names of the following script objects are changed:<ul><li>External data source table record (<span class="term">ExternalDataSourceTableRecord</span>);</li><li>External data source record set (<span class="term">ExternalDataSourceTableRecordSet</span>).</li></ul><p>This change is not implemented in 8.3.2 compatibility mode.</p></td><td><ul><li><span class="term">ExternalDataSourceRecord;</span></li><li><span class="term">ExternalDataSourceRecordSet</span>.</li></ul><p></p></td><td><ul><li><span class="term">ExternalDataSourceTableRecord;</span></li><li><span class="term">ExternalDataSourceTableRecordSet</span>.</li></ul><p></p></td></tr><tr title="Версия 8.3.3" class="tag_0"><td><a name="26594439-4f5c-11e2-bb40-e61f135f174b"></a>For turnovers accumulation register managers and for accounting register managers, the methods for setting and getting the totals period are renamed. For compatibility purposes, the previous names are supported.</td><td><ul><li><span class="term">GetTotalsPeriod()</span></li><li><span class="term">SetTotalsPeriod()</span></li></ul></td><td><ul><li><span class="term">GetMaxTotalsPeriod()</span></li><li><span class="term">SetMaxTotalsPeriod()</span></li></ul></td></tr><tr title="Версия 8.3.3" class="tag_0"><td><a name="1721726c-704a-11e2-adcc-e61f135f174b"></a>For objects that describe form elements being tested, the name of the property that contains the element title is changed.<p>
</p></td><td><ul><li><span class="term">Title</span></li></ul></td><td><ul><li><span class="term">TitleText</span></li></ul></td></tr><tr title="Версия 8.3.3" class="tag_0"><td><a name="17217274-704a-11e2-adcc-e61f135f174b"></a><p>The names of the <span class="term">UsualGroupRepresentation</span> system enumeration items are changed. For compatibility purposes, the previous names are supported.</p></td><td><ul><li><span class="term">Line</span></li><li><span class="term">Margin</span></li><li><span class="term">GroupBox</span></li></ul></td><td><ul><li><span class="term">WeakSeparation</span></li><li><span class="term">NormalSeparation</span></li><li><span class="term">StrongSeparation</span></li></ul></td></tr><tr title="Версия 8.3.3" class="tag_0"><td><a name="09181363-7128-11e2-adcc-e61f135f174b"></a>The names of the methods for getting and setting the client application window caption are changed. For compatibility purposes, the previous names are supported.<p>
</p></td><td><ul><li><span class="term">GetApplicationCaption</span></li><li><span class="term">SetApplicationCaption</span></li></ul></td><td><ul><li><span class="term">GetClientApplicationCaption</span></li><li><span class="term">SetClientApplicationCaption</span></li></ul></td></tr><tr title="Версия 8.3.3" class="tag_0"><td><a name="09181364-7128-11e2-adcc-e61f135f174b"></a>The name of the configuration property that describes the desktop command interface is changed.<p>
</p></td><td><ul><li><span class="term">DesktopCommandInterface</span></li></ul></td><td><ul><li><span class="term">MainSectionCommandInterface</span></li></ul></td></tr><tr title="Версия 8.3.3" class="tag_0"><td><a name="d0b36fe0-71d9-11e2-adcc-e61f135f174b"></a>The name of configuration property that describes the desktop workspace (the starting page) is changed.</td><td><ul><li><span class="term">DesktopWorkingArea</span></li></ul></td><td><ul><li><span class="term">StartPageWorkingArea</span></li></ul></td></tr><tr title="Версия 8.3.3" class="compat tag_0 tag_1"><td><a name="8421ae53-9b6d-11e2-adcc-e61f135f174b"></a>The names of settings that store start page (desktop) parameters.
In version 8.3.2 compatibility mode, use the old names. When the compatibility mode is changed, the saved settings keys are changed as well.</td><td><ul><li><span class="term">Common</span><span class="term">/DesktopSettings</span></li><li><span class="term">Desktop/NavigationPanel/CommandInterfaceSettings</span></li><li><span class="term">Desktop/ActionsPanel/CommandInterfaceSettings</span>
</li></ul></td><td><ul><li><span class="term">Common</span><span class="term">/</span><span class="term">StartPageSettings</span></li><li><span class="term">MainSection</span><span class="term">/</span><span class="term">NavigationPanel</span><span class="term">/</span><span class="term">CommandInterfaceSettings</span></li><li><span class="term">MainSection</span><span class="term">/</span><span class="term">ActionsPanel</span><span class="term">/</span><span class="term">CommandInterfaceSettings</span>.</li></ul></td></tr><tr title="Версия 8.3.3" class="tag_0"><td><a name="8421ae54-9b6d-11e2-adcc-e61f135f174b"></a>The name of the type that describes the object containing start page (desktop) settings is changed. For compatibility purposes, the previous name is supported. </td><td><ul><li><span class="term">DesktopSettings</span></li></ul></td><td><ul><li><span class="term">StartPageSettings</span></li></ul></td></tr><tr title="Версия 8.3.3" class="tag_0"><td><a name="20673241-bc60-11e2-adcc-e61f135f174b"></a>The Russian name of the <span class="term">TestedFormField</span> object method, which ends the editing of the current area, is changed.</td><td><ul><li><span class="term">ЗавершитьРедактированиеТекущейОбласти()</span></li></ul></td><td><ul><li><span class="term">ЗакончитьРедактированиеТекущейОбласти()</span></li></ul></td></tr></table><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="fcbb6956-8af0-11e2-adcc-e61f135f174b">Mobile platform</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="30%">After</th><th width="30%">Before</th><th width="20%">Result of changes</th></tr></thead><tr title="Версия 8.3.3" class="tag_29"><td><a name="b760b08b-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>For iOs-based devices, the iOS version 4.x is not supported. The minimum iOS version is 5.1.<p>For Android-based devices, the minimum RAM size is 256 MB.</p></td><td>iOS version 4.x was supported.<p>Android-based devices required 100 MB of RAM to run 1C:Enterprise.</p></td><td>System requirements for the mobile platform are revised.</td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="b760b080-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In the mobile application, the extended tooltop can be used, except the <span class="term">Balloon</span> option.</td><td>Extended tooltips were not available in mobile applications.</td><td>On the mobile platform, you can create tooltips for form elements using a variety of tooltip design options.</td></tr><tr title="Версия 8.3.3" class="tag_36"><td><a name="b760b085-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>Geolocation functions and multimedia tools (photos, audio- and videorecording) provided by mobile devices are available in mobile applications.<p>The following geolocation functions are implemented: <span class="term">GeographicCoordinates</span>, <span class="term">LocationData</span>, <span class="term">LocationProviderInformation</span>, <span class="term">LocationTools</span>, <span class="term">AddressData</span>. The <span class="term">LocationTools</span> global context property is implemented. Global context methods <span class="term">GetAddressByLocation</span><span class="term">()</span>, <span class="term">GetLocationByAddress</span><span class="term">()</span>, and <span class="term">ShowOnMap</span><span class="term">()</span> are implemented. The <span class="term">GeographicalSchemaCoordinates</span> type is renamed to <span class="term">GeographicCoordinatesp</span>; it is used in geolocation functions. The <span class="term">GeographicalSchemaCoordinates</span> type name is supported for compatibility purposes.</p><p>The <span class="term">MultimediaData</span> and <span class="term">MultimediaTools</span> objects are implemented to support processing multimedia features. The <span class="term">MultimediaTools</span> global context property is implemented.</p></td><td>These features were not provided.</td><td>Geolocation and multimedia functions of mobile device perating systems are now available in the mobile platform. You can add features for defining the current location, making photos of incoming items, and so on.</td></tr><tr title="Версия 8.3.3" class="tag_20"><td><a name="b760b086-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>The configuration check verifies whether the conifiguration language code meets the ISO standard. It is recommended that you use ISO-compliant language codes.</td><td>The language codes were not checked for compliance with ISO standard.</td><td>Reduced chance of incorrect mobile platform language selection based on the mobile device language.</td></tr><tr title="Версия 8.3.3" class="tag_69"><td><a name="b760b087-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Common modules that reuse returned values are now supported</td><td>This feature was not provided.</td><td>On the mobile platform, you can optimize getting the same data multiple times during a single session or a single server call.</td></tr><tr title="Версия 8.3.3" class="tag_95"><td><a name="b760b088-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 95); return false;">Predefined data</a>.<br></td><td>While a mobile application is being updated, metadata objects are compared by their internal identifiers.
When a mobile application is updated to version 8.3.3, the corresponding restructuring is performed. </td><td>While a mobile application was being updated, metadata objects were compared by their names.</td><td>You can rename metadata objects while preserving the object data.</td></tr><tr title="Версия 8.3.3" class="tag_64"><td><a name="b760b089-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>The mobile platform picture format is replaced by the format that supports several screen resolutions of mobile devices.</td><td>All mobile platform pictures had the same resolution.</td><td>The sizes of system pictures displayed on mobile device screens depend on the screen resolutions.</td></tr><tr title="Версия 8.3.3" class="tag_173"><td><a name="b760b08a-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 173); return false;">Backups</a>.<br></td><td>When an infobase is created on iOS-based devices, the directory containing the application data is marked as excluded from the backup. When the infobase data is modified (object form extension data and register data is recorded), the directory with application data is marked for backup and the backup is initiated using the system tools.</td><td>On iOS-based devices, the infobase directory was marked for backup since it was created.</td><td>The application behavior meets the requirements of the Apple company to user data backup.</td></tr><tr title="Версия 8.3.3" class="tag_26"><td><a name="b760b08c-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>On the mobile platform, resolved issues with displaying spreadsheet documents that have a large number of rows and columns.</td><td>In some cases displaying a spreadsheet document with a large number of rows and columns on the mobile platform led to an unexpected shutdown.</td><td>Improved mobile platform stability when processing large spreadsheet documents.</td></tr><tr title="Версия 8.3.3" class="tag_37"><td><a name="b760b08d-9a99-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For the mobile platform, the HTML-document field is implemented. The HTML-document field has the following specifics:<ul><li>The<b> </b><span class="term">Document</span> and <span class="term">Output</span> properties are not supported.</li><li>The <span class="term">OnClick</span> event is fired only during the attempt to switch to a new page. At this time, all properties of the <span class="term">EventData</span> parameter except <span class="term">Href</span> contain the <span class="term">UNDEFINED</span> value. The <span class="term">Href</span> property contains the address of the new page.</li></ul></td><td>The HTML-document field was not supported on the mobile platform.</td><td>In mobile applications, displaying HTML pages in forms is implemented. For example, you can create a manual for your configuration.</td></tr><tr title="Версия 8.3.3" class="tag_96"><td><a name="8421ae50-9b6d-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 96); return false;">Interface</a>.<br></td><td>On mobile devices with Android OS, you can change the order of items in the list of applications.</td><td>On mobile devices with Android OS, changing the order of items in the list of applications was not available.</td><td>Improved usability of the list of applications. User can arrange applications in any order.</td></tr><tr title="Версия 8.3.3" class="tag_25"><td><a name="8421ae55-9b6d-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Processing data composition system details on the mobile platform is implemented (this includes opening values and remote processing of the details). For mobile platform, the <span class="term">DataCompositionDetailsID</span> object is implemented.</td><td>On the mobile platform, reports that contained data composition system details could not be opened.</td><td>On the mobile platform, reports can be generated using the data composition system. Report that contains details can be opened on the mobile platform.</td></tr><tr title="Версия 8.3.3" class="tag_174"><td><a name="2fa966f6-9e07-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 174); return false;">Mobile application development</a>.<br></td><td>In the <span class="interface">Mobile application creation wizard</span> data processor, you can specify a key for Google Maps.
You can also specify a logo for screen resolution 950×1136 (iPhone 5 screen) in this data processor.</td><td>These features were not provided.</td><td>You can use the <span class="interface">Mobile application creation wizard</span> data processor for creating mobile applications that utilize new mobile platform features (geocoding support). Support of iOS-based devices was improved as well.</td></tr><tr title="Версия 8.3.3" class="tag_37"><td><a name="514aa822-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>For the objects <span class="term">HTTPConnection</span>, <span class="term">WSProxy</span>, <span class="term">WSDefinitions</span>, and <span class="term">InternetMailProfile,</span> and for the <span class="term">CreateWSProxy()</span> method, the option to set a timeout for interaction with a network resource is implemented.
User names and passwords that are passed to <span class="term">WSProxy</span>, <span class="term">WSDefinitions</span>, and <span class="term">HTTPConnection</span>
objects can contain special characters, except ":".
You can encode (the <span class="term">EncodeString()</span> method) and decode (the <span class="term">DecodeString()</span> method) custom text strings for using them in URLs. Encoding is performed in compliance with the RFC 1738 standard (<a href="http://www.ietf.org/rfc/rfc1738.txt" target="_blank">http://www.ietf.org/rfc/rfc1738.txt</a>).
You can process HTTP request headers and return codes, as well as get and set request bodies as strings or binary data. The <span class="term">HTTPRequest</span> and <span class="term">HTTPResponse</span> objects are implemented.<p>This functionality is similar to the PC-based platform functionality.
</p></td><td>This feature was not provided on the mobile platform.</td><td>On the mobile plaform, the following features are available:<ul><li>Setting timeouts for interaction with network resources</li><li>Using characters that do not belong to the ASCII character set in user names and passwords </li><li>Generating URLs and getting values from them according to the RFC 1738 standard (<a href="http://www.ietf.org/rfc/rfc1738.txt" target="_blank">http://www.ietf.org/rfc/rfc1738.txt</a>) when custom text is added to a URL</li><li>Generating HTTP requests, processing responses, and interacting with REST services from 1C:Enterprise script</li></ul></td></tr><tr title="Версия 8.3.3" class="tag_69"><td><a name="514aa823-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The <span class="term">CurrentUniversalDateInMilliseconds()</span> function is implemented. It gets the number of milliseconds that passed since January 1, year 0001, 0:00:00 UTC. <p>The attempt to assign a value to a fixed structure item raises an exception.
In value tables, serialization of index descriptions is implemented. The index contents are not serialized but restored during deserialization.
The hash function value can be calculated based on <b>MD5</b> and <b>CRC32</b> algorithms using the <span class="term">DataHashing</span> object.
This functionality is similar to the PC-based platform functionality.</p></td><td>This feature was not provided on the mobile platform.</td><td>On the mobile platform, you can do the following:<ul><li>Measure time intervals more precisely. For example, this can be handy for getting the duration of a specific action.</li><li>Use fixed structures in a similar way to other fixed collections.</li><li>Restore the value table state in more detail during its deserialization.</li><li>Quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools.</li></ul></td></tr><tr title="Версия 8.3.3" class="tag_115"><td><a name="514aa824-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>When specifying values of managed form fields or tables, you can specify data stored in a specific row of a form attribute that is a table (but not a dynamic list).
Data belonging to dynamic lists that are currently not displayed on a managed form is not read during the operations that involve the managed form.
For attributes of <span class="term">String</span> type that have fixed length and are located in managed form tables, table boxes, or spreadsheet documents, the appearance of the mark that indicates that the field must be filled is modified.
The following style fonts are implemented: <span class="term">SmallTextFont</span>, <span class="term">LargeTextFont</span>, and <span class="term">ExtraLargeTextFont</span>. For the <span class="term">Font</span> type, the <span class="term">Scale</span> property is implemented. It defines increase or decrease of the font relative to the initial size.
For groups of "usual group" or "page" type, you can set the background color of form group extensions using the <span class="term">BackColor</span> property.
The <span class="term">URLProcessing</span> handler is implemented for the <span class="term">Label</span> form field, <span class="term">Decoration </span>form field of <span class="term">Label</span> type, and managed form. The handler is called when a user clicks a formatted string with a hyperlink in a field.
Extended appearance customization options for form fields of label type and decorations of label type.
In usual groups with limited width, the size of managed form buttons can vary depending on the width, which is similar to the behavior of other form items in a group with limited width.
This functionality is similar to the PC-based platform functionality.</td><td>This feature was not provided on the mobile platform.</td><td>On the mobile platform, you can do the following:<ul><li>Edit data stored in specific rows of form table data in separate fields.</li><li>Get fast access to managed forms with dynamic lists located on different pages.</li><li>Ensure that the behavior of the mark that indicates that the field must be filled is the same for all attribute types.</li><li>Specify font size in a form relative to the form base font, without using absolute font size values.</li><li>Improve form usability by highlighting group colors.</li><li>Create a handler for each hyperlink represented as a formatted string.</li><li>Use more appearance customization options in managed forms.</li></ul><p>When the size of a usual group is limited, the algorithm used for resizing group items is the same for all item types.</p></td></tr><tr title="Версия 8.3.3" class="tag_23"><td><a name="514aa825-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>User presentations are implemented for database objects of the following types: <span class="term">Catalog</span>, <span class="term">Document</span>, and <span class="term">Exchang</span><span class="term">ePlan</span>.
In document journals, the attribute containing the document number has fixed length if all documents included in the journal have the number field of <span class="term">String</span> type with fixed length. Otherwise, the journal attribute has variable length.
A value obtained from an unfilled table attribute, value tree, or tabular section is equal to the default value of the column attribute type, with the type qualifier taken into account.
This functionality is similar to the PC-based platform functionality.</td><td>This feature was not provided on the mobile platform.</td><td>On the mobile platform, you can do the following:<ul><li>Get nonstandard data presentations in various scenarios.</li><li>Get document numbers in a uniform way, regardless of the method used to obtain the document numbers: either from the document itself or from the document journal. </li><li>Generate default values in the same way as they are generated on the PC-based platform.</li></ul></td></tr><tr title="Версия 8.3.3" class="tag_86"><td><a name="514aa826-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>In the information register record form, if the <span class="term">OnlyInActions</span> property of the <span class="term">Copy</span> command has the <span class="term">Auto</span> value, the system behavior is changed. This value now means that the command is located in the <span class="interface">More</span> (or <span class="term">All actions</span>) menu only.<p>This functionality is similar to the PC-based platform functionality.</p></td><td>This feature was not provided on the mobile platform.</td><td>On the mobile platform, you can specify the same default location for the <span class="interface">Copy</span> command in information register records set forms and in the item forms.</td></tr><tr title="Версия 8.3.3" class="tag_63"><td><a name="514aa827-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>New types of charts are implemented: <ul><li>Funnel</li><li>3D funnel</li><li>Normalized funnel</li><li>3D normalized funnel</li></ul><p>The antialiasing mode is implemented for charts.</p><p>You can connect series of charts to each other.</p><p>The semitransparency mode is implemented for charts. </p><p>The <span class="term">Indicator</span> property is implemented for the tape graph chart.</p><p>This functionality is similar to the PC-based platform functionality.
</p></td><td>This feature was not provided on the mobile platform.</td><td>Extended chart features on the mobile platform.</td></tr><tr title="Версия 8.3.3" class="tag_16"><td><a name="514aa828-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>For periodic information registers, the totals for getting first and last slices are implemented.<p>This functionality is similar to the PC-based platform functionality.</p></td><td>This feature was not provided on the mobile platform.</td><td>On the mobile platform, you can get first and last slices, which represent data as of the last (current) moment in time, much faster.</td></tr><tr title="Версия 8.3.3" class="tag_26"><td><a name="514aa829-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>If a fixed area is larger than the displayed area, the spreadsheet document does not use the fixation.<p>The algorithm for horisontal cell placement in different rows is modified.</p><p>This functionality is similar to the PC-based platform functionality.
</p></td><td>This feature was not provided on the mobile platform.</td><td>On the mobile platform you can:<ul><li>Improve usability of reports that contain areas with left or top fixation.</li><li>Improve usability of spreadsheet documents.</li></ul></td></tr><tr title="Версия 8.3.3" class="tag_56"><td><a name="514aa82a-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>If a message to a user contains characters incompatible with XML format (in the thick or thin client), the error <span class="interface">XML text contains invalid characters in X position</span> is generated.<p>This functionality is similar to the PC-based platform functionality.
</p></td><td>This feature was not provided on the mobile platform.</td><td>The processing of characters that are incompatible with XML format on the mobile platform is uniform with processing them on the PC-based platform.</td></tr><tr title="Версия 8.3.3" class="tag_64"><td><a name="514aa82b-a592-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Formatted strings are available (the <span class="term">FormattedString</span> type).<p>You can use a formatted string as:</p><ul><li>Data for the "label field" form items</li><li>Title for form items of decoration type</li><li><span class="term">MessageText</span> parameter of the <span class="term">DoMessageBox</span><span class="term">()</span> method</li><li><span class="term">QueryText</span> parameter of the <span class="term">DoQueryBox</span><span class="term">()</span> method</li></ul><p>
</p></td><td>This feature was not provided on the mobile platform.</td><td>On the mobile platform, the text presentation capabilities are improved.</td></tr><tr title="Версия 8.3.3" class="tag_56"><td><a name="fc13ebc5-a73b-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>During the import of XSD schema, if the target namespace definition is missing in the schema, a diagnostic message is displayed.</td><td>During the import of XSD schema, when any problems occurred while loading the XSD schema, a diagnostic message was not displayed.</td><td>Improved diagnostics during XSD schema import.</td></tr><tr title="Версия 8.3.3" class="tag_115 tag_86 tag_36"><td><a name="62d069c7-acda-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br><a href="#" onclick="onTagClick(this, 36); return false;">Common objects</a>.<br></td><td>You can specify the <span class="term">Arbitrary</span> type for a subordinate attribute of a managed form attribute (for example, a value table column or a value tree column).
For managed forms, the <span class="term">URL</span> and <span class="term">AutoURL</span> properties are implemented. You can use the <span class="term">URL</span> property to get a link to the main form of the object.
For the <span class="term">GetForm()</span>, <span class="term">OpenForm()</span>, and <span class="term">OpenFormModal()</span> methods, the <span class="term">URL</span> parameter is implemented. Its value is assigned to the <span class="term">URL</span> property of a form when the form is obtained or opened.
Navigation links to lists are implemented. For a form whose main attribute is a dynamic list with a main table specified, the navigation link points to the list of the object specified as the main table. Following the link opens the main form of the list.
You can use navigation links to global command interface commands.
The format of navigation links to navigation points generated by standard commands is modified.
Changes made to a table of totals storage settings for accumulation registers are applied within a transaction.
Values of the <span class="term">ReadOnly</span> and <span class="term">Protection </span>properties are preserved when a spreadsheet document is passed between the client and the server.
For the <span class="term">NumberInWords()</span> global context method, the <span class="term">AU</span> formatting option is implemented.<p>The <span class="term">TextReader</span> and <span class="term">TextWriter</span> objects are implemented.
This functionality is similar to the PC-based platform functionality.</p></td><td>This feature was not provided on the mobile platform.</td><td>Some mobile platform features are now uniform with PC-based platform.</td></tr><tr title="Версия 8.3.3" class="tag_144"><td><a name="f5b4ca12-da60-11e2-adcc-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 144); return false;">Mobile application</a>.<br></td><td>The mobile platform supports all of the interface languages that are supported in the PC-based platform. The mobile platform delivery that supports only English and Russian interface languages is also available.<p>The content of the mobile platform distribution kit is modified.</p></td><td>The mobile platform supported English and Russian interface languages only.</td><td>The system part of the mobile platform interface supports more languages than before.</td></tr><tr title="Версия 8.3.3" class="tag_20"><td><a name="84a96464-3186-11e3-9afe-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>If the <span class="interface">Use purposes </span>configuration property is set to <span class="interface">Mobile device </span>only, other configuration settings are changed automatically:<ul><li>The <span class="interface">Modality usage mode</span> property is set to <span class="interface">Use</span>.</li><li>The <span class="interface">Interface compatibility mode</span> is set to <span class="interface">Version 8.2</span>.</li></ul></td><td>If the <span class="interface">Use purposes </span>configuration property was set to <span class="interface">Mobile device </span>only, other configuration properties were not changed automatically.</td><td>For configurations being developed for mobile platform only, eliminated the chance to save configuration property values that are incompatible with mobile platform limitations.</td></tr></table><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="e55bc2bb-c767-11e2-adcc-e61f135f174b">Transition from the version 8.2 to the version 8.3.3</a></h2><ul><li title="Версия 8.3.3" class="tag_0"><a name="e55bc2bd-c767-11e2-adcc-e61f135f174b"></a>Conversion of configurations, infobases, external data processors, and external reports is not required during the upgrade from the version 8.2 to version 8.3.3.</li><li title="Версия 8.3.3" class="tag_0"><a name="e55bc2be-c767-11e2-adcc-e61f135f174b"></a>To use certain features of version 8.3.3 you have to disable the compatibility mode. The structure of certain database objects is modified when disabling or enabling the compatibility mode. Note that to be able to work with infobases created using 1C:Enterprise version 8.2 you have to set the compatibility mode to the <span class="interface">Version 8.2.16</span>. <p>In order to use certain optimization improvements, you have to restructure data related to the optimization areas. To restructure data, you can use the <span class="interface">Verify and repair </span>mode, or perform forced restructuring of the required objects.</p></li><li title="Версия 8.3.3" class="tag_0"><a name="e55bc2c0-c767-11e2-adcc-e61f135f174b"></a>Simultaneous operating of 1C:Enterprise 8.3.3 and earlier 1C:Enterprise versions with a single file infobase is not supported. In this case a diagnostic error message is displayed.</li><li title="Версия 8.3.3" class="tag_0"><a name="e55bc2bc-c767-11e2-adcc-e61f135f174b"></a>It is recommended that you revise the list of infobases. Infobases that are present in the list when version 8.3.3 is installed in most cases have version 8.2 or 8.1 (because it is the default version, which is set automatically when an infobase is created or added to the list). Therefore, in order to open an infobase in 8.3.3 (using the program that starts 1C:Enterprise), you have to specify the required version in the list of infobase startup settings, or specify the version directly in the infobase settings.</li><li title="Версия 8.3.3" class="tag_0"><a name="e55bc2bf-c767-11e2-adcc-e61f135f174b"></a>At the first start of server cluster version 8.3.3 on the computer that has previous versions of ther server cluster installed, the content of the cluster register file (<span class="interface">1CV8Reg.lst</span>) is converted to a new format. The register of the server cluster 8.3.3 is stored in the file <span class="interface">1CV8Clst.lst,</span> in the same directory as the cluster register of the previous versions. There is no data synchronization between cluster registers of different versions after the first start of server cluster 8.3.3. <p>To perform the conversion of the cluster register from version 8.2 to version 8.3 once more, stop the server cluster 8.3, delete the server cluster 8.3 register (the <span class="interface">1CV8Clst.lst</span> file), and then start the server cluster 8.3.3.</p></li><li title="Версия 8.3.3" class="tag_0"><a name="e55bc2c1-c767-11e2-adcc-e61f135f174b"></a>To increase the performance of the configuration repository in a scenario when a repository server is used, disable the compatibility mode of the configuration repository. To access the configuration repository using earlier 1C:Enterprise versions, enable the compatibility mode of the configuration repository. The conversion process can take significant time.</li><li title="Версия 8.3.3" class="tag_0"><a name="e55bc2c2-c767-11e2-adcc-e61f135f174b"></a>Changed the full-text search index format. For efficient full-text search when using input by string, it is recommended that you clear and update the full-text search index during the transition to 1C:Enterprise version 8.3.3. It is also recommended that you clear and then update the full-text search index during the transition to earlier platform versions.</li><li title="Версия 8.3.3" class="tag_0"><a name="e55bc2c3-c767-11e2-adcc-e61f135f174b"></a>For infobases that use the OpenID authentication, you have to change the publishing settings in the <span class="interface">default.vrd</span> file.</li></ul><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4288e49c-1835-11e2-b237-e61f135f174b">Transition from the previous version to version 8.3.3</a></h2><ul><li title="Версия 8.3.3" class="tag_0"><a name="4288e49d-1835-11e2-b237-e61f135f174b"></a>Conversion of configurations, infobases, external data processors, and external reports is not required during the transition from the previous version to the version 8.3.3.
</li><li title="Версия 8.3.3" class="tag_0"><a name="6841617d-389c-11e2-977c-e61f135f174b"></a>Some features that are added in version 8.3.3 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li><li title="Версия 8.3.3" class="tag_0"><a name="427ec7ce-185a-11e2-b237-e61f135f174b"></a>Simultaneous operating of 1C:Enterprise 8.3.3 and earlier 1C:Enterprise versions with a single file infobase is not supported. In this case a diagnostic error message is displayed.</li><li title="Версия 8.3.3" class="tag_0"><a name="188e7b92-42db-11e2-977c-e61f135f174b"></a>To increase the performance of the configuration repository in a scenario when a repository server is used, disable the compatibility mode of the configuration repository. To access the configuration repository using earlier 1C:Enterprise versions, enable the compatibility mode of the configuration repository. The conversion process can take significant time.</li><li title="Версия 8.3.3" class="tag_0"><a name="ce24468e-4b55-11e2-977c-e61f135f174b"></a>Changed the full-text search index format. For efficient full-text search when using input by string, it is recommended that you clear and update the full-text search index during the transition to 1C:Enterprise version 8.3.3. It is also recommended that you clear and then update the full-text search index during the transition to earlier platform versions.</li><li title="Версия 8.3.3" class="tag_0"><a name="24df4610-c444-11e2-adcc-e61f135f174b"></a>For infobases that use the OpenID authentication, you have to change the publishing settings in the <span class="interface">default.vrd</span> file.</li></ul><p><a href="#4288e495-1835-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h1><a name="e729b97c-1831-11e2-b237-e61f135f174b">Version 8.3.2</a></h1><p title="Версия 8.3.2" class="tag_0"><a name="e4701c69-b51d-11e1-b815-e61f135f174b"></a>Version 8.3.2 includes known bug fixes and functionality modifications.</p><hr></hr><ul><li><a href="#e4701c62-b51d-11e1-b815-e61f135f174b">New functions and changes</a></li><li><a href="#e4701c63-b51d-11e1-b815-e61f135f174b">New functions and changes in the 1C:Enterprise mode</a></li><li><a href="#e4701c64-b51d-11e1-b815-e61f135f174b">Optimization</a></li><li><a href="#e4701c65-b51d-11e1-b815-e61f135f174b">Changes altering the system behavior</a></li><li><a href="#e4701c66-b51d-11e1-b815-e61f135f174b">Changes that require changes to the configuration and administrative settings</a></li><li><a href="#e4701c68-b51d-11e1-b815-e61f135f174b">Transition from the previous version to the version 8.3.2</a></li></ul><h2><a name="e4701c62-b51d-11e1-b815-e61f135f174b">New functions and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of changes</th></tr></thead><tr title="Версия 8.3.2" class="compat tag_2 tag_1"><td><a name="19d50449-f356-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.3.1</span> is added to the list of available values of the <span class="interface">Compatibility mode</span> property.</td><td>Compatibility modes were available for the following platform versions: 8.1, 8.2.13, and 8.2.16.</td><td>In version 8.3.2 you can run configurations created in version 8.3.1 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.2 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.1 for working with the infobase even after the transition to version 8.3.2. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).</td></tr><tr title="Версия 8.3.2" class="tag_20"><td><a name="19d50447-f356-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Automated configuration testing is implemented for managed applications. The testing is written in 1C:Enterprise script (using the appropriate script objects); it emulates a sequence of interactive actions and checks the results of their execution.<p>Automated testing is supported for thin, thick, and web clients, both in file and client/server modes.</p><p>The test does not require making any changes in the configuration being tested.</p><p>Implemented the option of recording interactive user actions in a managed application for later use in a 1C:Enterprise script-based scenario, which reproduces the actions (<a href="http://its.1c.ru/db/metod81#content:5014:1" target="_blank">http://its.1c.ru/db/metod81#content:5014:1</a>).</p></td><td>This feature was not provided.</td><td>Better development quality can be achieved due to automated testing of the applied solution interface.</td></tr><tr title="Версия 8.3.2" class="tag_20 tag_23"><td><a name="1dcccca2-f732-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Implemented XDTO serialization for pivot charts. Templates of spreadsheet documents that contain pivot charts can be dumpled to XML files.
</td><td>This feature was not provided.</td><td>All configuration objects can be dumped to files.
</td></tr><tr title="Версия 8.3.2" class="tag_144"><td><a name="facd7a19-fe76-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 144); return false;">Mobile application</a>.<br></td><td>Mobile application development is supported, with target operating systems iOS and Android. Applications can run on mobile devices in the offline mode; permanent Internet connection is not required. Application data exchange through the Internet can be implemented using standard 1C:Enterprise tools. The development is performed in Designer; the managed application development model is used. The subset of functionality used for PC application development is supported.<p>The resulting applications can run both on PC and mobile devices.</p></td><td>This feature was not provided. <p>Mobile application development was only supported in the mobile extension for handheld devices (and only for Microsoft Windows Mobile and Microsoft Windows CE operating systems).</p></td><td>You can develop applications for devices with iOS and Android operating systems using 1C:Enterprise platform tools. Data exchange between mobile applications and PC applications is available.</td></tr></table><p><a href="#e729b97c-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="e4701c63-b51d-11e1-b815-e61f135f174b">New functions and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of changes</th></tr></thead><tr title="Версия 8.3.2" class="tag_14"><td><a name="be29a14f-dd52-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>If an error that leads to system shutdown occurs, the error text is displayed in the technical support information window.</td><td>In some cases the error that led to system shutdown was not displayed in the technical support information window.</td><td>Improved usability of information for technical support.
</td></tr></table><p><a href="#e729b97c-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="e4701c64-b51d-11e1-b815-e61f135f174b">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of changes</th></tr></thead><tr title="Версия 8.3.2" class="tag_23"><td><a name="be29a150-dd52-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Reduced verification and repair time for document journals.</td><td>For large journals the "Verify and Repair" operation might take significant time.</td><td>Reduced time of the "Verify and Repair" operation for document journals.
</td></tr><tr title="Версия 8.3.2" class="tag_20"><td><a name="86cc1695-dd66-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Optimised memory usage when comparing configurations and updating modified configurations.</td><td>Comparison and merging of large configurations might cause issues related to high memory usage.</td><td>Comparison and merging of large configurations no longer requires customized OS settings.</td></tr></table><p><a href="#e729b97c-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="e4701c65-b51d-11e1-b815-e61f135f174b">Changes altering the system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of changes</th></tr></thead><tr title="Версия 8.3.2" class="compat tag_86 tag_1"><td><a name="19d5044a-f356-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>In the information register record form the system behavior has been changed in the case when the <span class="term">OnlyInAllActions</span> property of the <span class="term">Copy</span> command is set to <span class="term">Auto</span>. This value now means that the command is only present in the <span class="interface">All actions </span>menu. This change is not implemented in 8.3.1 compatibility mode.</td><td>The <span class="term">Auto</span> value of the <span class="term">OnlyInAllActions</span> property of the <span class="term">Copy</span> command meant that the command was present both in the command bar and in the <span class="interface">All actions</span> menu.</td><td>The behavior of the <span class="interface">Copy </span>command in the information register record form is unified with its behavior in forms of other objects.</td></tr><tr title="Версия 8.3.2" class="tag_149"><td><a name="19d5044b-f356-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 149); return false;">Window management</a>.<br></td><td>Relative positions of the user notification window and the window showing server calls are changed.<p>The default position of the user notification window is the bottom right corner of the workspace area.</p><p>The default position of the window showing server calls is the bottom left corner of the workspace area.</p></td><td>On Windows operating system, default window positions depended on the taskbar position. On Linux operating system, default window positions were not defined.</td><td>Unified default positions for the user notification window and the window showing server calls in different operating systems. Eliminated indeterminate behavior on Linux operating system.</td></tr><tr title="Версия 8.3.2" class="tag_28"><td><a name="6b5979cd-f677-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>When a pop-up window is blocked by the pop-up blocker in Google Chrome web browser, the browser displays a related setup instruction in a new tab.</td><td>The browser setup instruction was displayed in a new browser window (not in a new tab)</td><td>Better usability of web browser setup.</td></tr><tr title="Версия 8.3.2" class="compat tag_23 tag_1"><td><a name="e73f356b-f69b-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>A value obtained from an empty table of values attribute, a value tree, or a tabular section matches the default value of the column attribute type (the type qualifier is taken into account).<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td>A value obtained from an empty table of values attribute, a value tree, or a tabular section matched the default value of the column attribute type, but the type qualifier was not taken into account.</td><td>The default value generation is uniform throughout the system.</td></tr><tr title="Версия 8.3.2" class="tag_14 tag_19 tag_29 tag_67"><td><a name="e73f356c-f69b-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>The mechanism of shared work with infobase files and configuration repository files is revamped. Shared work with infobases and configuration repositories is supported for both Windows and Linux users. For the files <span class="interface">1Cv8.1CD</span>, <span class="interface">1Cv8tmp.1CD</span>, <span class="interface">1Cv8.1CL</span>, <span class="interface">1Cv8tmp.1CL</span>, and for some other files the system creates auxiliary files that have the same names with <span class="interface">.cfl</span> extension added (for example, <span class="interface">1Cv8.1CD.cfl</span>). These files have zero size and are never deleted on closing client applications.<p>Shared work with a file infobase is only possible if all client applications have the same version number. </p><p>The number of simultaneous connections to a file infobase is limited to 1024.</p></td><td>The mechanism of shared work with the file infobase and the configuration repository did not take into account some pecularities of Linux file system.</td><td>Shared work with the file infobase and the configuration repository is available to both Windows and Linux users. Issues related to multiuser work with file infobases and configuration repositories on Linux operating system are eliminated.</td></tr><tr title="Версия 8.3.2" class="tag_64"><td><a name="e73f356d-f69b-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>When you create a formatted string in Designer (in the dialog for editing a formatted string), you can use style elements (font face and color). The formatted string stores references to style elements that were used during its creation. Converting style elements to actual fonts and colors (dereferencing) is performed when the string is displayed.</td><td>The dialog for editing a formatted string did not have options for specifying style elements. <p>Formatted strings that were created using 1C:Enterprise script and included style elements actually contained explicit font and color values (not the references).</p></td><td>Improved usability of formatted string creation. You can simultaneously change the formatting of all text fragments that have the same style element applied to them.</td></tr><tr title="Версия 8.3.2" class="compat tag_37 tag_1"><td><a name="1dcccca3-f732-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>If you use the <span class="term">InternetMail </span>object with a mail server where secured StartTLS connection is set up to use the same ports as unsecured connection, the StartTLS connection is established.<p>This change is not implemented in version 8.2.16 compatibility mode. </p></td><td>If you used the <span class="term">InternetMail </span>object with a mail server where secured StartTLS connection was set up to use the same ports as unsecured connection, the StartTLS connection was not established.</td><td>You can establish a secured StartTLS connection to a mail server.</td></tr><tr title="Версия 8.3.2" class="compat tag_26 tag_1"><td><a name="1dcccca4-f732-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When the <span class="term">Join</span><span class="term">()</span> method of a spreadsheet document is called, the properties <span class="term">StayWithNext</span>, <span class="term">PageTop</span>, and <span class="term">PageBottom</span> of a spreadsheet document cells area are only copied when joining is performed for the area located beyond the right border of the resulting document.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td>When the <span class="term">Join</span><span class="term">()</span> method of a spreadsheet document was called, properies of a spreadsheet document cells area were always copied.</td><td>The <span class="term">Join</span><span class="term">()</span> method handles page breaks during the output to a spreadsheet document.</td></tr><tr title="Версия 8.3.2" class="tag_6"><td><a name="30d41e30-fb65-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Removing a server cluster or a working server from the cluster console requires a confirmation.</td><td>Removing a server cluster or a working server from the cluster console did not require a confirmation.</td><td>The chance of accidentally removing a server cluster or a working server from the cluster console is decreased.</td></tr><tr title="Версия 8.3.2" class="tag_10"><td><a name="6ff31dc9-f8b5-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The <span class="term">URL</span> parameter is added to the <span class="term">CheckInfoBases </span>method of the <span class="term">WebCommonInfoBases </span>internet service. It allows "redirection" of infobase list requests to another internet service (provided that the other service has the same method descriptions). The other internet service can have different authentication settings.</td><td>Internet service "redirection" was not available. All web service calls used the same authentication.</td><td>When retrieving the list of infobases through internet services, you have the option to use multiple services with different authentication requirements. This allows implementing scenarios of the following type: the check for infobase list changes does not require authentication, but retrieving the list requires authentication.</td></tr><tr title="Версия 8.3.2" class="tag_23 tag_16"><td><a name="f7792aed-2326-11e2-977c-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>Attributes, common attributes (that are not separators), and resources are not read implicitly when record sets are written to information registers.<p>Rights to read attributes, common attributes (that are not separators), and resources are not required when writing a recordset to an information register.</p></td><td>Rights to read attributes, common attributes (that are not separators), and resources were required when writing a recordset to an information register.</td><td>Access right restrictions for read operations are not checked when writing a record set to an information register.</td></tr></table><p><a href="#e729b97c-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="e4701c66-b51d-11e1-b815-e61f135f174b">Changes that require changes to the configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of changes</th></tr></thead><tr title="Версия 8.3.2" class="compat tag_64 tag_1"><td><a name="19d50448-f356-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>If a message to a user contains characters incompatible with XML format (in thick or thin client), the error <span class="interface">XML text contains invalid characters in X position</span> is generated.<p>This change is not implemented in version 8.3.1 compatibility mode. </p></td><td>If a message to a user contained characters incompatible with XML format, the thick and thin clients did not display any error message.</td><td>Uniform system behavior for handling characters incompatible with XML format.</td></tr><tr title="Версия 8.3.2" class="compat tag_23 tag_1"><td><a name="e73f356e-f69b-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>If you explicitly specify the <span class="term">Encoding</span> property of the <span class="term">InternetMailAttachment</span> object, the outgoing email message is generated with explicitly specified attachment encoding.<p>
</p><p>This change is not implemented in version 8.2.16 compatibility mode. </p></td><td>The <span class="term">Encoding</span> property of the <span class="term">InternetMailAttachment</span> object was ignored during the generation of outgoing email message.</td><td>Explicitly specified attachment encoding ensures that the emal client displays the attachment name and content correctly whenever email message encoding is different from the attachment encoding.</td></tr><tr title="Версия 8.3.2" class="compat tag_26 tag_1"><td><a name="6b5979cb-f677-11e1-97ad-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The algorithm for calculating horizontal cell positions is changed. If total width of several adjacent cells is identical for different rows, such blocks of adjacent cells have equal width in all rows and therefore have common vertical borders.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td>If total width of several adjacent cells was identical for different rows, the cells might have different width in different rows, and therefore might not have common vertical borders.</td><td>Improved usability of spreadsheet documents.</td></tr></table><p><a href="#e729b97c-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="e4701c68-b51d-11e1-b815-e61f135f174b">Transition from the previous version to the version 8.3.2</a></h2><ul><li title="Версия 8.3.2" class="tag_0"><a name="e4701c6a-b51d-11e1-b815-e61f135f174b"></a>Conversion of configurations, infobases, external data processors, and external reports is not required during the transition from the previous version to the version 8.3.2.</li><li title="Версия 8.3.2" class="tag_0"><a name="2650de83-06d4-11e2-97ad-e61f135f174b"></a>Some features that are added in version 8.3.2 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
</li></ul><p><a href="#e729b97c-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h1><a name="e729b97b-1831-11e2-b237-e61f135f174b">Version 8.3.1</a></h1><p title="Версия 8.3.1" class="tag_0"><a name="97e1245b-086c-11e2-97ad-e61f135f174b"></a>Version 8.3.1 does not include changes introduced in version 8.2.17.</p><p title="Версия 8.3.1" class="tag_0"><a name="4cc794a8-7d56-11e1-b5d1-e61f135f174b"></a>Version 8.3.1 includes known bug fixes and functionality modifications.</p><p title="Версия 8.3.1" class="tag_0"><a name="95b24f67-a0d0-11e1-991e-e41f136d174a"></a>
<p>Improved the list of new and updated features:</p><ul><li>Keywords and interface texts are color-coded (it is the same formatting that is used in the documentation).</li><li>Sections describing behavior in the compatibility mode have color background.</li><li>The list structure is updated, providing more details and better usability (only for version 8.3.1 or later).</li></ul></p><hr></hr><ul><li><a href="#4cc794a1-7d56-11e1-b5d1-e61f135f174b">New functions and changes</a></li><li><a href="#4cc794a2-7d56-11e1-b5d1-e61f135f174b">New functions and changes in the 1C:Enterprise mode</a></li><li><a href="#4cc794a3-7d56-11e1-b5d1-e61f135f174b">Optimization</a></li><li><a href="#4cc794a4-7d56-11e1-b5d1-e61f135f174b">Changes altering the system behavior</a></li><li><a href="#4cc794a5-7d56-11e1-b5d1-e61f135f174b">Changes that require changes to the configuration and administrative settings</a></li><li><a href="#4cc794a6-7d56-11e1-b5d1-e61f135f174b">Renamed objects</a></li><li><a href="#4cc794a7-7d56-11e1-b5d1-e61f135f174b">Upgrade from the previous version to version 8.3.1</a></li></ul><h2><a name="4cc794a1-7d56-11e1-b5d1-e61f135f174b">New functions and changes</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of changes</th></tr></thead><tr title="Версия 8.3.1" class="compat tag_2 tag_1"><td><a name="d0b682cd-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 2); return false;">Configuration properties</a>.<br></td><td><span class="interface">Version 8.2.16</span> is added to the list of available values of the <span class="interface">Compatibility mode</span> property.</td><td>Compatibility modes were available for the following platform versions: 8.1 and 8.2.13.</td><td>1C:Enterprise provides compatibility of configurations developed using version 8.3.1 or later with previous platform versions.</td></tr><tr title="Версия 8.3.1" class="tag_135 tag_136"><td><a name="9439c9c6-87a0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 135); return false;">Designer</a>.<br><a href="#" onclick="onTagClick(this, 136); return false;">Cross-platform architecture</a>.<br></td><td>The client application for Linux operating system is available. It includes thin client, thick client, and Designer. It supports file and client/server operation modes. Thin client can connect to infobases using a web browser. Limitations of the client application for Linux are listed in the documentation.<p>Installation of multiple 1C:Enterprise versions is not supported.</p><p>Shortcuts for noninteractive startup application, thin client, and thick client are added to the application menu of Linux desktop environment. They are located in the <span class="interface">Finance</span> subsection of the <span class="interface">Office</span> section.</p></td><td>Only the 1C:Enterprise server and the web client were available for Linux operating system.</td><td>You can develop applied solutions and run client applications on Linux operating system.</td></tr><tr title="Версия 8.3.1" class="tag_175"><td><a name="d0b682e5-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 175); return false;">Thin client access over the Internet</a>.<br></td><td>The thin client is now HTTPS-enabled, thanks to client certificate support. The following client certificate storage options are supported: file, Windows certificate store, and NSS certificate store.<p>The following command line options for specifying certificate parameters are implemented: <span class="term">HttpsCert</span>, <span class="term">HttpsCA</span> and <span class="term">HttpsNSS</span>.</p><p>Client applications for Linux operating system do not support Windows certificate store, and <span class="term">HttpsCert</span>, and <span class="term">HttpsCA</span> command line options.</p></td><td>The thin client was not HTTP-enabled, and client certificates were not supported.</td><td>The thin client is HTTP-enabled, and client certificates are supported.</td></tr><tr title="Версия 8.3.1" class="tag_172"><td><a name="d0b682cf-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 172); return false;">Web links</a>.<br></td><td>Web services can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).</td><td>Web services could not operate using HTTPS with client certificates.</td><td>Web services are operational in cases when the server side requires a client certificate to use HTTPS.</td></tr><tr title="Версия 8.3.1" class="tag_37"><td><a name="d0b682d0-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>HTTP and FTP connections can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).</td><td>HTTP and FTP connections could not operate using HTTPS with client certificates.</td><td>HTTP and FTP connections are operational in cases when the server side requires a client certificate to use HTTPS.</td></tr><tr title="Версия 8.3.1" class="tag_69"><td><a name="e92cc508-7752-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>You can calculate the value of hash function by <b>MD5</b> and <b>CRC32</b> algorithms using the <span class="term">DataHashing</span> object.</td><td>Calculating the hash function required the use of third-party (add-ins, etc.) tools. </td><td>You can quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools.</td></tr><tr title="Версия 8.3.1" class="tag_62 tag_58"><td><a name="e4aaa638-7e21-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>A common attribute can include an external data source. Connection parameters for such external data sources are stored by separator values. If a separator is not used in a session, the separator is treated as an independent value for storing connection parameters. Data located in tables of external data sources is not separated by separator values.</td><td>Common attributes could not include external data sources.</td><td>You can specify connection parameters for each data area in the infobase. This provides you with the option to access either different infobases with the same structure, or a single infobase with different connection parameters.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="d0b682d3-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>You can specify data located in a specific row of a form attribute that has table structure (except dynamic lists) as a value of a managed form field or table.</td><td>This feature was not provided.</td><td>You can implement such interface features as displaying report settings in separate form fields.</td></tr><tr title="Версия 8.3.1" class="tag_62"><td><a name="d0b682d5-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>Operating system authentication is available when working with external data sources. The <span class="term">SessionOSAuthenticationChange</span> access right is implemented. It allows or denies changing the operating system authentication setting both in user settings and in current session parameters.</td><td>This feature was not provided.</td><td>You can establish connection to external data sources if the only authentication method available is operating system authentication.</td></tr><tr title="Версия 8.3.1" class="compat tag_23 tag_64 tag_1"><td><a name="d0b682e0-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>User presentations for data base objects of the following types: <span class="term">Catalog</span>, <span class="term">Document</span>, <span class="term">ChartOfAccounts</span>, <span class="term">ChartOfCalculationTypes</span>, <span class="term">ChartOfCharacteristicTypes</span>, <span class="term">BusinessProcess</span>, <span class="term">Task</span>, <span class="term">ExchangePlan</span>, <span class="term">Table</span>. Implemented the <span class="term">PresentationFieldsGetProcessing</span> and <span class="term">PresentationGetProcessing</span> event handlers for object manager modules of these types. <p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td>Modification of database objects using script tools was not allowed.</td><td>Custom presentations for database objects. The option to obtain presentations for external data source tables when the field that provides the presentation is not specified. The option to obtain presentations of objects that include localized data.</td></tr><tr title="Версия 8.3.1" class="tag_62 tag_69"><td><a name="d0b682dd-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>You can search for references to objects of external data source tables using the <span class="term">FindByRef()</span> global context method or <span class="interface">Find references to object</span> standard function. The search is performed both in infobase tables and in external data source tables.</td><td>Searching for references to objects of external data sources tables using the <span class="term">FindByRef()</span> global context method or <span class="interface">Find references to object</span> standard function was not available.</td><td>You can search for references to objects of external data source tables.</td></tr><tr title="Версия 8.3.1" class="tag_62"><td><a name="d0b682de-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>The <span class="term">AllRefsType()</span> method is implemented for the <span class="term">ExternalDataSourceTablesManager</span> object.</td><td>This feature was not provided.</td><td>Implementation of missing features for working with external data sources.</td></tr><tr title="Версия 8.3.1" class="tag_62"><td><a name="d0b682df-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>The <span class="term">OpenValue()</span> global context method allows opening the following value types: <span class="term">InformationRegisterRecordKey</span> and <span class="term">ExternalDataSourceTableRecordKey</span>.</td><td>The <span class="term">OpenValue()</span> global context method did not allow opening the following value type: <span class="term">InformationRegisterRecordKey</span> and <span class="term">ExternalDataSourceTableRecordKey</span>.</td><td>Implementation of missing features for working with information registers and external data sources.</td></tr><tr title="Версия 8.3.1" class="tag_142 tag_6"><td><a name="4ca4acdf-789a-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 142); return false;">Database configuration updates</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Background database configuration update is implemented. The update is supported in client/server mode only. It is available when the data structure is modified. The update does not require long-lasting exclusive access to the infobase. The exclusive access is required at the final stage of the background update for a short period of time. <p>The database configuration update service is implemented for a server cluster. A system background job that performs the background database configuration update is implemented. </p><p>The <span class="term">GetDataBaseConfigurationUpdate()</span> global context method and the <span class="term">DataBaseConfigurationUpdate</span> object are implemented.</p><p>For the <span class="term">/UpdateDBCfg</span> Designer batch mode command line option, the following parameters are implemented: <span class="term">-Dynamic</span>, <span class="term">-BackgroundStart</span>, <span class="term">-BackgroundCancel</span>, <span class="term">-BackgroundFinish</span>, <span class="term">-BackgroundSuspend</span>,and <span class="term">-BackgroundResume</span>.</p><p>The following events are implemented in the event log: <span class="term">_$InfoBase$</span><span class="term">_.DBConfigBackgroundUpdateStart</span><span class="term">, </span><span class="term">_$InfoBase$_.DBConfigBackgroundUpdateFinish</span><span class="term">, </span><span class="term">_$InfoBase$_.DBConfigBackgroundUpdateCancel</span><span class="term">, </span><span class="term">_$InfoBase$_.DBConfigBackgroundUpdateSuspend</span><span class="term">, and </span><span class="term">_$InfoBase$_.DBConfigBackgroundUpdateResume</span><span class="term">.</span></p></td><td>An update of database configuration with modified data structure was possible only in the exclusive mode.</td><td>The update of database configuration with significant changes in its data structure does not cause long application downtime for end users.<p>You have the option to perform dynamic infobase configuration update in Designer batch mode. The option is available for both background and regular updates.</p></td></tr><tr title="Версия 8.3.1" class="tag_69 tag_78 tag_28"><td><a name="f9466837-83a4-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 78); return false;">File operations</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>The <span class="term">TempFilesDir</span><span class="term">()</span> method is implemented for the web client. The method is available when the file system extension is installed.<p>The <span class="term">UserDataWorkDir</span><span class="term">()</span> method is implemented. It provides access to the user directory created by the system. The method is available for thin, thick, and web clients. In the web client the method is available when the file system extension is installed. </p><p>The <span class="term">DocumentsDir</span><span class="term">() </span>method is implemented. It provides access to the default document directory of the operating system. The method is available for thin, thick and web clients. In the web client the method is available when the file system extension is installed. </p></td><td>Standard catalogs (user data directory and document directory) were inaccessible for standard tools. In the thick and thin clients the access could be implemented using third-party tools, which reduced 1C:Enterprise portability between operating systems and client applications types.</td><td>Access to certain standard directories on the client computer, which allows storing user file data in designed locations without using third-party tools.</td></tr><tr title="Версия 8.3.1" class="tag_64"><td><a name="d0b682ce-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Formatted strings are available (<span class="term">FormattedString</span> type). You can use formatted strings as:<ul><li>data for the form elements of <span class="interface">L</span><span class="interface">abel</span> type;</li><li>title for the <span class="interface">Decoration</span> form element;</li><li><span class="term">MessageText</span> parameter of the <span class="term">DoMessageBox</span><span class="term">()</span> method</li><li><span class="term">QueryText</span> parameter of the <span class="term">DoQueryBox</span><span class="term">()</span> method.</li></ul></td><td>Displaying text that included various formatting styles was only available for HTML documents and formatted documents.</td><td>Improved text presentation capabilities and usability.</td></tr><tr title="Версия 8.3.1" class="tag_69 tag_115"><td><a name="7171261a-8470-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The <span class="term">URLProcessing</span> handler is implemented for the form field <span class="term">Label</span>, form field <span class="term">Decoration</span> of <span class="term">Label</span> type, and managed form. <p>The handler is called if the following conditions are met: there is a formatted string in any of the specified form fields, it contains a hyperlink, and the <span class="term">Hyperlink </span>property of the form element is set to <span class="term">False</span>.</p></td><td>Implementing presentation of an entire form element as a hyperlink was allowed, but including multiple hyperlinks in a single field was not allowed.</td><td>The option to handle each hyperlink contained in a formatted string separately.</td></tr><tr title="Версия 8.3.1" class="tag_86"><td><a name="71712611-8470-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>You can use navigation links to commands of the global command interface. Using a link executes the command.<p>Support of navigation links to commands is implemented for the <span class="term">GotoURL</span><span class="term">GotoURL</span><span class="term">()</span> global context method.</p></td><td>This feature was not provided.</td><td>Using a link can execute a command, and this feature can be used in the script.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="71712614-8470-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>The <span class="term">URL </span>property is implemented for managed forms. It is used for obtaining a link to the default object form.<p>The <span class="term">AutoURL</span> property is implemented for the managed form. The <span class="term">GetURL</span><span class="term">()</span> method of the <span class="term">ClientApplicationWindow</span> objects returns a value of the <span class="term">URL</span> property (if the <span class="term">AutoURL </span>property is set to <span class="term">False</span>) or the standard link to the default form.</p><p> </p></td><td>This feature was not provided.</td><td>You can specify the value of the navigation link obtained from the client application window.</td></tr><tr title="Версия 8.3.1" class="tag_69 tag_58 tag_23"><td><a name="8331a825-853e-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Document journals can be included in contents of common attributes, which are not used as separators. For compatibility purposes, in infobases created in 1C:Enterprise version 8.2, the value of the <span class="term">Use </span>property of the the common attribute content element is set to <span class="interface">Do not use</span> for document journals. </td><td>Common attributes could not be displayed in document journals.</td><td>Common attributes can be displayed in document journals.</td></tr><tr title="Версия 8.3.1" class="tag_64 tag_115"><td><a name="8331a826-853e-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Implemented the following style fonts: <span class="term">SmallTextFont</span>, <span class="term">Large</span><span class="term">TextFont</span>, <span class="term">ExtraLargeTextFont</span>.<p>For the <span class="term">Font</span> type the <span class="term">Scale</span> property is implemented. It specifies increase or decrease of the font size relatively to the original size.</p></td><td>The only method of specifying font size in a managed form was setting absolute font size.</td><td>You can specify the size of the form font relatively to the base font of the form, without using absolute font size values.</td></tr><tr title="Версия 8.3.1" class="tag_6 tag_69"><td><a name="8331a829-853e-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>The <span class="term">SafeCallMemoryLimit</span> property is implemented for the <span class="term">IWorkingProcessInfo</span> object. It specifies the amount of memory (in bytes) that the application can use during a single server call. The <span class="term">SafeWorkingProcessesMemoryLimit</span> property for the <span class="term">IWorkingServerInfo</span> object is implemented. It specifies maximum amount of memory (in bytes) available for all running processes on a given working server.</td><td>No tools for limiting memory usage were available. It might cause problems in some situations - for example, when users customized reports that selected large amounts of data.</td><td>Server stability improved. If a specific session consumes a large amount of memory, it does not cause emergency shutdown of the entire server cluster. Instead, the client application that causes the memory consumption is shut down.</td></tr><tr title="Версия 8.3.1" class="tag_6 tag_69"><td><a name="8331a82a-853e-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>While a working process is executing a script in the client/server infobase mode, the stack is monitored to prevent it from overflowing.</td><td>Infinite recursion might lead to emergency shutdown of the working process of the server cluster.</td><td>Stability of server cluster operation improved.</td></tr><tr title="Версия 8.3.1" class="tag_6 tag_69"><td><a name="375290e2-8551-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>For the <span class="term">ISessionInfo</span> and<span class="term"> IInfoBaseConnectionInfo</span> objects the following properties are implemented:<ul><li><span class="term">MemoryCurrent</span> - size of memory (in bytes), used from the beginning of the current call;</li><li><span class="term">MemoryLast5Min</span> - size of memory (in bytes), used by calls during the last 5 minutes;</li><li><span class="term">MemoryAll</span> - size of memory (in bytes), used by calls since the beginning of the session;</li><li><span class="term">InBytesCurrent</span> - number of bytes read from the disk since the start of the current call;</li><li><span class="term">InBytesLast5Min</span> - number of bytes read by the session from the disk during the last 5 minutes;</li><li><span class="term">InBytesAll</span> - number of bytes read from the disk by the session since the beginning of the session;</li><li><span class="term">OutBytesCurrent</span> - number of bytes written to the disk by the session since the beginning of the current call;</li><li><span class="term">OutBytesLast5Min</span> - number of bytes written to the disk by the session for the last 5 minutes;</li><li><span class="term">OutBytesAll</span> - number of bytes written to the disk by the session since the beginning of the session.</li></ul><p>Similar properties are implemented in the cluster console for the list of sessions, list of connections, and connection properties dialog.</p></td><td>This feature was not provided.</td><td>Monitoring tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.</td></tr><tr title="Версия 8.3.1" class="tag_17 tag_6"><td><a name="9108828f-856d-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Extended the list of properties for the <span class="term">&lt;call&gt;</span> event of the technological log when the event is generated for the <span class="interface">rphost</span> process (the <span class="term">process</span> property is set to <span class="term">rphost</span>), and also when the <span class="interface">rphost</span> process performs a call to virtual system resources. The following properties are added:<ul><li><span class="term">Report</span> - metadata object name of the report being executed;</li><li><span class="term">Method </span>- name of the called method;</li><li><span class="term">SessionID</span> - session number;</li><li><span class="term">Memory</span> - size of memory (in bytes) that was occupied and not released during the call;</li><li><span class="term">MemoryPeak</span> - size of memory (in bytes) that was occupied and not released during the call. The peak value;</li><li><span class="term">InBytes </span>- number of bytes read from the disk during the call;</li><li><span class="term">OutBytes</span> - number of bytes written to the disk during the call;</li><li><span class="term">Context</span> - event context.</li></ul></td><td>The listed properties were absent from the <span class="term">&lt;call&gt;</span> event.</td><td>Technological log tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.</td></tr><tr title="Версия 8.3.1" class="tag_58 tag_69"><td><a name="ebc5a550-8853-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>You can delete data from a specific data area or from the entire infobase. The following data can be deleted:<ul><li>Applied object data</li><li>Settings storage data</li><li>History</li><li>List of users</li><li>Time zone settings</li></ul><p>The <span class="term">Administration</span><span class="interface"> </span>right is required for deletion. The deletion can be performed:</p><ul><li>using the <span class="term">/EraseData</span> command line option of the Designer batch mode</li><li>using the <span class="term">EraseInfoBaseData</span><span class="term">() </span>global context method</li></ul><p>The<span class="term"> _$InfoBase$_.EraseData </span>event is implemented in the event log.</p></td><td>It was impossible to delete a specific data area.</td><td>You can delete a data area that is no longer needed (for example, data belonging to a subscriber that stopped using the system).</td></tr><tr title="Версия 8.3.1" class="tag_6 tag_116"><td><a name="b013c21d-89df-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>The licensing service is implemented for the server cluster. The license search algorithm is modified.</td><td>The licensing service was not present.</td><td>You have the option to bind a software license to a specific computer, which is intended for running the licensing service only and will not be subject to hardware changes.</td></tr><tr title="Версия 8.3.1" class="tag_20"><td><a name="51be1ba5-8ebe-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Dumping configurations to files and loading configurations from files is implemented. <p>Most objects are dumped to .xml files. Modules are dumped to the text files. Pictures are dumped to files in their original format, help information is dumped to <span class="interface">.html</span> files. Vendor configurations are dumped to configuration files (<span class="interface">.cf</span>). Ordinary forms and interfaces are dumped to binary files.</p><p><span class="interface">Dump configuration to files</span> and <span class="interface">Load configuration from files</span> commands are added to the <span class="interface">Configuration </span>menu. <span class="interface">Dump configuration files</span> and <span class="interface">Load configuration files</span> commands are removed from the <span class="interface">Configuration </span>menu, but you can restore them using the main menu settings dialog.</p><p>The <span class="term">DumpConfigToFiles</span> and <span class="term">LoadConfigFromFiles</span> command line options are implemented.</p></td><td>Limited set of data was dumped and loaded: modules, help information, templates, rights, and pictures. Other configuration data was not dumped.<p><span class="interface">Dump configuration files</span> and <span class="interface">Load configuration files</span> commands from the <span class="interface">Configuration </span>menu were used for dumping and loading data.</p></td><td>You can analyze and modify configurations using third-party tools.</td></tr><tr title="Версия 8.3.1" class="tag_64 tag_115"><td><a name="f324a4d4-8f5b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>You can specify the background color for form group extensions of regular groups and pages using the <span class="term">BackColor</span> property. If the background color of a group is different from <span class="interface">Auto</span> and the group is displayed as a <span class="interface">Group box</span>, the group box (including the title) is filled with the specified background color.</td><td>The option to specify background color for form groups was not provided.</td><td>The color highlighting of groups improves visibility of form elements and the overall usability of forms.</td></tr><tr title="Версия 8.3.1" class="tag_58"><td><a name="f324a4d6-8f5b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br></td><td>New global context methods for managing the safe mode of data separation are available in 1C:Enterprise script: <span class="term">SetDataSeparationSafeMode</span><span class="term"> </span>and <span class="term">DataSeparationSafeMode</span>. They duplicate the functionality of the <span class="term">safe</span> attribute in the <span class="term">zone</span> tag of the <span class="interface">default.vrd</span> file.</td><td>Switching to the safe mode of data separation was only available by editing the file <span class="interface">default.vrd </span>and only if the web server connection to the infobase (the HTTP protocol) was used.</td><td>The new methods enable safe execution of code fragments called from sessions that do not use separator values (but are intended to run in specific data areas, without any way to change the area accidentally).</td></tr><tr title="Версия 8.3.1" class="tag_39 tag_176"><td><a name="c7577798-90f8-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br><a href="#" onclick="onTagClick(this, 176); return false;">OpenID authentication</a>.<br></td><td>In case of successful or unsuccessful OpenID authentication the <span class="interface">Session.Authentication</span> or <span class="interface">Session. </span><span class="interface">Authentication</span><span class="interface"> error</span> events are generated in the event log.</td><td>OpenID authentication events were not written to the event log.</td><td>You can obtain information about OpenID authentication events from the event log.</td></tr><tr title="Версия 8.3.1" class="tag_39 tag_176"><td><a name="c7577799-90f8-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br><a href="#" onclick="onTagClick(this, 176); return false;">OpenID authentication</a>.<br></td><td>For infobases that are OpenID providers the <span class="interface">OpenIDProvider.PositiveAssertion</span> event is implemented. It is generated in case of a positive response to the authentication request. If the response to the authentication request is negative, the <span class="interface">OpenIDProvider.NegativeAssertion</span> event is generated in the event log of the infobase.</td><td>This feature was not provided.</td><td>Improved tools for administration of OpenID providers.</td></tr><tr title="Версия 8.3.1" class="tag_20"><td><a name="e5ba99a6-853b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>You can view the values of the form element properties <span class="term">Font</span>, <span class="term">TitleFont</span>, <span class="term">FooterFont</span> and <span class="term">ChoiceList</span> in a separate window when editing of these properties is disabled.</td><td>These properties could not be viewed if the object was not locked in the repository or was supported.</td><td>If an item is not locked in the configuration repository or is supported, you can view its font style and choice list without disabling support and without locking the object in the repository.</td></tr><tr title="Версия 8.3.1" class="tag_6"><td><a name="13a6296d-94ec-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>When logon to or logout from an infobase that requires a client license is performed, the platform can notify an external application using web service methods. In response to logon notification, the external application can allow or deny the start of the session. This option is only available in client/server infobase mode. For specifying web service parameters, the following properties are implemented:<ul><li><span class="interface">External session manager</span> property of the infobase in the cluster console</li><li><span class="term">ExternalSessionManagerConnectionString</span> property of the <span class="term">IInfoBaseInfo</span> object.</li></ul><p>If a web service for external session management is unavailable, the system behavior is determined using the following properties:</p><ul><li><span class="interface">Required usage of external session manager</span> property of the infobase in the cluster;</li><li><span class="term">ExternalSessionManagerRequired </span>property of the <span class="term">IInfoBaseInfo</span> object.</li></ul><p>The external session manager service is implemented on the server.</p><p>Parameters of invoked web services are listed in the documentation.</p></td><td>The only option to limit the number of simultaneous sessions was appropriate modification of the applied solution. A platform mechanism for performing this task was not available.</td><td>A platform mechanism for monitoring the number of simultaneously used licenses for various applied solutions, which does not require modification of these applied solutions.</td></tr><tr title="Версия 8.3.1" class="tag_28 tag_11"><td><a name="13a6296f-94ec-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 11); return false;">Add-ins</a>.<br></td><td>You can use add-ins in Google Chrome and Safari web browsers (for operating systems of Windows family and Mac OS X). The Mac OS value is implemented for the <span class="term">PlatformType</span> system enumeration. A file system extension is available for these browsers on operating systems of Windows family and Mac OS X. A cryptographic extension is available for these browsers on operating systems of Windows family only.</td><td>Add-ins, file system extension, and cryptographic extension were not supported for Google Chrome and Safari web browsers.</td><td>A file system extension and cryptographic extension (for operating systems of Windows family only) are available for Google Chrome and Safari web browsers. Add-ins can be created for all supported web browsers.</td></tr><tr title="Версия 8.3.1" class="tag_79"><td><a name="13a62971-94ec-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 79); return false;">Pictures</a>.<br></td><td>Processing pictures from the script with help of the new <span class="term">PictureProcessor </span>object. The following options are available:<ul><li>Selecting a significant picture part</li><li>Rotating a picture</li></ul></td><td>This feature was not provided.</td><td>A way to process pictures before placing them in a spreadsheet document. Usage examples:<ul><li>Select a seal from a photo</li><li>Rotate a picture by a specified angle to align a signature</li></ul></td></tr><tr title="Версия 8.3.1" class="tag_63"><td><a name="d0b682d2-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The managed form editor allows interactive setup for the following attribute types: <span class="term">Chart</span>, <span class="term">GanttChart</span>, <span class="term">Dendrogram</span>, <span class="term">SpreadsheetDocument</span>, <span class="term">GraphicalSchema</span>, and <span class="term">GeographicalSchema</span>. You can open the interactive setup dialog box from the property panel of the attribute.</td><td>Only the following ways to set up the <span class="term">Chart</span>, <span class="term">GanttChart</span>, <span class="term">Dendrogram</span>, <span class="term">SpreadsheetDocument</span>, <span class="term">GraphicalSchema</span>, and <span class="term">GeographicalSchema </span>objects were available: through 1C:Enterprise script, or by putting a set up object to a template and then putting the object from the template to a form element at form creation.</td><td>This feature facilitates development.</td></tr><tr title="Версия 8.3.1" class="tag_64"><td><a name="d0b682d4-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>New parameter <span class="term">AU </span>for the global context method <span class="term">NumberInWords</span><span class="term">()</span>. It is only used in the English locale (<span class="term">en</span>, <span class="term">en_XX</span>). It defines the number notation, classic or compact.<p>In the classic notation "and" is always used between the word "hundred" (or "thousand" or "million") and the word representing the last two decimal digits. For example, 150 is "one hundred and fifty", while 100 is "one hundred" and 50 is "fifty". In the compact notation "and" is omitted.</p></td><td>The compact notation was always used for converting numbers to English words.</td><td>Correct number-to-word conversion according to the common practice rule in European countries.</td></tr><tr title="Версия 8.3.1" class="tag_114"><td><a name="d0b682d6-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 114); return false;">Charts of characteristic types</a>.<br></td><td>You can use the <span class="term">ALLOWED</span> keyword when retrieving a list of characteristics, provided that the list was defined using one of the following: the <span class="term">CHARACTERISTICS</span> keyword of the query language or the dialog box for specifying object characteristics. If you retrieve the list of characteristics using a query, you have the option to use the <span class="term">ALLOWED</span> keyword there.</td><td>The <span class="term">ALLOWED</span> keyword was not used when retrieving lists of characteristics.</td><td>Data access restrictions are implemented for tables that store property lists (for example, charts of characteristic types).</td></tr><tr title="Версия 8.3.1" class="tag_25"><td><a name="d0b682d7-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Fields from data sets that are not connected can be displayed in details. For <span class="term">DataCompositionTemplateRecords</span><span class="term">DataCompositionTemplateRecords </span>and <span class="term">DataCompositionTemplateTableRecords</span> objects, the <span class="term">DataSets </span>properties are implemented. The property value is an array containing names of data sets whose details are displayed.<p>The <span class="term">DataSet</span> property of <span class="term">DataCompositionTemplateRecords</span> and <span class="term">DataCompositionTemplateTableRecords</span> objects is deprecated. It is recommended that you do not use this property, although it is supported for compatibility purposes. Calling the <span class="term">DataSet</span> property throws an exception if the <span class="term">DataSets </span>property contains an array with more than one item.</p></td><td>It was impossible to display fields from data sets that were not connected.<p>The <span class="term">DataSet</span> property of <span class="term">DataCompositionTemplateRecords</span> and <span class="term">DataCompositionTemplateTableRecords</span><span class="term"> </span>contained the name of the dataset whose details were displayed.</p></td><td>You can create complex analytic reports.</td></tr><tr title="Версия 8.3.1" class="tag_62"><td><a name="d0b682dc-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>The <span class="term">FormGetProcessing</span> event is implemented in the manager module of external data source table.</td><td>This feature was not provided.</td><td>The default form of the external data source can be redefined when the external data source is opened or obtained.</td></tr><tr title="Версия 8.3.1" class="tag_62"><td><a name="55463267-77f0-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>Hierarchical lists can be organized for object data of external data sources. The <span class="term">ParentField</span> and <span class="term">UnfilledParentValue</span> attributes are implemented for the <span class="term">Table</span> metadata object. Hierarchical object tables can be used in the data composition system, queries, and dynamic lists.</td><td>This feature was not provided.</td><td>You can work with hierarchical data in external data sources.</td></tr><tr title="Версия 8.3.1" class="tag_62 tag_45 tag_25"><td><a name="55463268-77f0-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>You can use temporary tables when working with external data sources. Temporary tables are created directly in the database of the external data source. The following syntax is used for calling temporary tables:<span class="term">ExternalDataSource</span><span class="term">.&lt;E</span><span class="term">xternal data source name</span><span class="term">&gt;.TempTable</span><span class="term">.&lt;Temp </span><span class="term">table name</span><span class="term">&gt;</span>.</td><td>This feature was not provided.</td><td>You can create complex reports based on external data source tables.</td></tr><tr title="Версия 8.3.1" class="tag_114 tag_25"><td><a name="0cddc074-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 114); return false;">Charts of characteristic types</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When creating object characteristics using the <span class="interface">Additional characteristics of metadata object</span> dialog, if the list of characteristics is not obtained from the chart of characteristic types, the characteristic value type is defined by the attribute type specified in the <span class="interface">Value field</span> attribute of this dialog. If this attribute is not specified, the characteristic value type is <span class="term">Boolean</span>. <p>When object characteristics are specified using the <span class="term">CHARACTERISTICS</span> query language extension of the data composition system, if the <span class="term">TYPE </span>property is not specified, the characteristic type is defined by the value type obtained in the <span class="term">CHARACTERISTICVALUES </span>property. If the <span class="term">CHARACTERISTICVALUES </span>property is not specified, the characteristic value type is <span class="term">Boolean</span>.</p></td><td>When object characteristics were specified using the <span class="interface">Additional characteristics of metadata object</span> dialog or the <span class="term">CHARACTERISTICS</span> query language extension, if the list of characteristics was not obtained from the chart of characteristic types, the characteristic value type was <span class="term">Boolean</span>.<p>
</p></td><td>You can store characteristic types in catalogs, and you can modify characteristic types using a complex type of the attribute that stores the characteristic value (e.g., type of information register resource).</td></tr><tr title="Версия 8.3.1" class="tag_69"><td><a name="0cddc077-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Serialization of value table index descriptions is implemented. The index content is not serialized, but restored during deserialization.</td><td>Value table indexes were lost during serialization/deserialization.</td><td>More complete restoration of value table state during deserialization.</td></tr><tr title="Версия 8.3.1" class="tag_63"><td><a name="fc15b2e1-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>New types of charts are implemented:<ul><li>Funnel</li><li>3D funnel</li><li>Normalized funnel</li><li>3D normalized funnel</li></ul><p>The following properties are implemented for the <span class="term">Chart</span> object: <span class="term">FunnelNeckHeight</span>, <span class="term">FunnelNeckWidth</span>, and <span class="term">FunnelSpace</span>. These properties are applicable for the new charts types only.</p></td><td>This feature was not provided.</td><td>New chart functionality.</td></tr><tr title="Версия 8.3.1" class="tag_63"><td><a name="fc15b2e2-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>Antialiasing mode is implemented for charts. <span class="term">SplineMode</span> and <span class="term">SplineStrain</span> properties are implemented for the <span class="term">Chart</span> object. These properties are applicable to the following chart types: line, stacked line, area, stacked area, normalized area, ceil graph, tape graph, waterfall, funnel, and 3D funnel, and also for the following chart types, which have the <span class="term">Indicator</span> flag set for the series: column, 3D column, bar, 3D bar, stacked column, 3D stacked column, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.</td><td>This feature was not provided.</td><td>New chart functionality.</td></tr><tr title="Версия 8.3.1" class="tag_63"><td><a name="fc15b2e3-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>You can connect series of charts with each other. For the <span class="term">Chart</span> object the following properties are implemented: <span class="term">ValuesBySeriesConnection</span>, <span class="term">ValuesBySeriesConnectionLines</span>, and <span class="term">ValuesBySeriesConnectionColor</span>. These properties are applicable to the following chart types: stacked column, 3D stacked column, stacked bar, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.</td><td>This feature was not provided.</td><td>New chart functionality.</td></tr><tr title="Версия 8.3.1" class="tag_63"><td><a name="fc15b2e4-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The semitransparency mode is implemented for charts. <span class="term">SemitransparencyMode</span> and <span class="term">SemitransparencyPercent</span> properties are implemented for the <span class="term">Chart</span> object. These properties are applicable to the following chart types: area, bar graph, pyramid graph, ceil graph, tape graph, waterfall, funnel, 3D funnel, and 3D normalized funnel.</td><td>This feature was not provided.</td><td>New chart functionality.</td></tr><tr title="Версия 8.3.1" class="tag_63 tag_25"><td><a name="fc15b2e6-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>For the objects <span class="term">DataCompositionOutputParameterValues</span>, <span class="term">DataCompositionGroupOutputParameterValues</span>, <span class="term">DataCompositionChartOutputParameterValues</span>, and <span class="term">DataCompositionAreaTemplateChartAppearance</span> the following properties are implemented: <span class="term">ChartType</span><span class="term">.</span><span class="term">ValuesBySeriesConnection</span>, <span class="term">ChartType</span><span class="term">.</span><span class="term">ValuesBySeriesConnectionLines</span>, <span class="term">ChartType</span><span class="term">.</span><span class="term">ValuesBySeriesConnectionColor</span>, <span class="term">ChartType</span><span class="term">.</span><span class="term">SplineMode</span><span class="term">, </span><span class="term">ChartType</span><span class="term">.</span><span class="term">SplineStrain</span>, and <span class="term">ChartType</span><span class="term">.</span><span class="term">SemitransparencyMode</span>. These properties are used for setting data composition template parameters.</td><td>This feature was not provided.</td><td>New chart management options in the data composition system.</td></tr><tr title="Версия 8.3.1" class="tag_25"><td><a name="d0b682d8-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the data composition system expression language the following aggregate functions are implemented: <span class="term">Every</span><span class="term">()</span>, <span class="term">Any</span><span class="term">()</span>, <span class="term">Stddev_Pop</span><span class="term">()</span>, <span class="term">Stddev_Samp</span><span class="term">()</span>, <span class="term">Var_Samp</span><span class="term">()</span>, <span class="term">Var_Pop</span><span class="term">()</span>, <span class="term">Covar_Pop</span><span class="term">()</span>, <span class="term">Covar_Samp</span><span class="term">()</span>, <span class="term">Corr</span><span class="term">()</span>, <span class="term">Regr_Slope</span><span class="term">()</span>, <span class="term">Regr_Intercept</span><span class="term">()</span>, <span class="term">Regr_Count</span><span class="term">()</span>, <span class="term">Regr_R2</span><span class="term">()</span>, <span class="term">Regr_AvgX</span><span class="term">()</span>, <span class="term">Regr_AvgY</span><span class="term">()</span><span class="term">, </span><span class="term">Regr_SXX</span><span class="term">()</span>, <span class="term">Regr_</span><span class="term">SYY()</span>, and <span class="term">Regr_</span><span class="term">SXY()</span>.</td><td>These aggregate functions were not provided in the data composition system expression language.</td><td>The new functions facilitate creation of complex analytic reports.</td></tr><tr title="Версия 8.3.1" class="tag_25"><td><a name="d0b682d9-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>In the data composition system expression language the following functions are implemented: <span class="term">ACos()</span>, <span class="term">ASin()</span>, <span class="term">ATan()</span>, <span class="term">Sin()</span>, <span class="term">Cos()</span>, <span class="term">Tan()</span>, <span class="term">Exp()</span>, <span class="term">Log()</span>, <span class="term">Log10()</span>, <span class="term">Pow()</span>, <span class="term">Sqrt()</span>, <span class="term">Round</span><span class="term">()</span>, <span class="term">Int</span><span class="term">()</span>, <span class="term">ValueType</span><span class="term">()</span>, and <span class="term">Type()</span>.</td><td>These functions were not provided in the data composition system expression language.</td><td>The new functions facilitate creation of complex analytic reports.</td></tr><tr title="Версия 8.3.1" class="tag_25"><td><a name="d0b682da-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New aggregate function <span class="term">Rank()</span> in the data composition system expression language. The function returns a sequence number of the current record in the current grouping, provided that all records of the current grouping are sorted in the specified order.</td><td>This aggregate function was not provided in the data composition system expression language.</td><td>The new functions facilitate creation of complex analytic reports.</td></tr><tr title="Версия 8.3.1" class="tag_25"><td><a name="d0b682db-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>New aggregate function <span class="term">ClassificationABC</span><span class="term">()</span> in the data composition system expression language. The function returns the class number: 1 – class "А", 2 – class "B", 3 – class "C".</td><td>This aggregate function was not provided in the data composition system expression language.</td><td>The new function facilitates creation of complex analytic reports.</td></tr><tr title="Версия 8.3.1" class="tag_26"><td><a name="a513e904-78b2-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>The <span class="interface">Merge</span> command is added to the shortcut menu of a spreadsheet document. It is also accessible through a keyboard shortcut <span class="interface">Ctrl+M</span>. <p>
</p><p>
</p></td><td>Merging cells of a spreadsheet document was only available by using the menu command <span class="interface">Table</span> <span class="interface">- </span><span class="interface">Merge</span> or clicking the corresponding toolbar button.</td><td>Improved usability of spreadsheet documents containing a large number of merged cells.</td></tr><tr title="Версия 8.3.1" class="tag_63"><td><a name="fc15b2e5-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 63); return false;">Charts</a>.<br></td><td>The <span class="term">Indicator</span> property is supported for the tape graph chart: when antialiasing is disabled, the series with the <span class="term">Indicator</span> property set are displayed semitransparently on the entire chart area, overlapping other series.</td><td>This feature was not provided.</td><td>New chart functionality.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="d0b682ea-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>You can specify the <span class="term">Arbitrary</span> type for a subordinated attribute of a managed form attribute (e.g., column of a value table, column of a value tree, etc.).</td><td>It was impossible to store some data types (such as a references to external data source tables) in subordinated attributes of managed form attributes.</td><td>You can store references to external data source tables in subordinated attributes of managed form attributes.</td></tr><tr title="Версия 8.3.1" class="tag_64"><td><a name="d0b682eb-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>You can manage duplex printing of spreadsheet documents, graphical schemas (using script and interactively), and text documents (interactively only). System enumerations <span class="term">DuplexPrintingType</span> and <span class="term">PagePlacementAlternation</span> are implemented.</td><td>This functionality was only available from a printer driver.</td><td>You can explicitly specify the duplex printing option in some use cases.</td></tr><tr title="Версия 8.3.1" class="tag_20 tag_151"><td><a name="f324a4d8-8f5b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br><a href="#" onclick="onTagClick(this, 151); return false;">Web client and web service publishing tools</a>.<br></td><td>In the dialog for publishing to the web server you can edit all tags present in the <span class="interface">default.vrd</span> file. You can edit custom <span class="interface">default.vrd</span> files in this dialog. The <span class="interface">descriptor</span> parameter of the <span class="interface">webinst</span> utility allows you to perform publishing by template. The generated <span class="interface">default.vrd</span> file is used as a template.</td><td>A limited set of tags present in the <span class="interface">default.vrd</span> file was available for editing in the dialog for publishing to the web server. The option to publish by template was unavailable in the <span class="interface">webinst</span> utility, which limited the capabilities of automatic publication. E.g., publishing of web services using the utility was impossible. </td><td>You can edit all tags of the <span class="interface">default.vrd</span> file interactively, and you can create templates for the future automatic publication. Using templates allows publishing web services using the command line utility.</td></tr><tr title="Версия 8.3.1" class="tag_70"><td><a name="f324a4da-8f5b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 70); return false;">Client application installation</a>.<br></td><td>You can set up the update of thin client distribution kit and downloading the list of common infobases using an HTTP connection or a web service.<p>If versions of client and server applications do not match, the thin client is downloaded and installed automatically.</p><p>The following parameters of the <span class="interface">1ces</span><span class="interface">tart.cfg</span> file are implemented :</p><ul><li><span class="term">InternetService</span> - address of the web service for updating of the thin client distribution kit and the list of common infobases,</li><li><span class="term">WebCommonInfoBases</span> - address of the web service for downloading the list of common infobases,</li><li><span class="term">WebDistributiveLocation</span> - address of the web service for updating the thin client distribution kit.</li></ul><p>You can specify a link to the thin client distribution kit in the following configuration files:</p><ul><li>In the <span class="interface">default.vrd</span> file using the <span class="term">pubdst</span> attribute;</li><li>In the <span class="interface">conf.cfg</span> file using the <span class="term">PublishDistributiveLocation</span> parameter.</li></ul></td><td>Automatic update of the thin client and downloading of list of common infobases were only available in a local network.</td><td>You can update the thin client distribution kit and download the list of common infobases without creating common directories. This allows you to obtain an up-to-date version of the distribution kit and the current list of infobases from a remote network.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="a513e902-78b2-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>DBA rights are not required for creating infobases in Oracle Database. The following actions cannot be performed without DBA rights:<ul><li>creating a database (data schema)</li><li>deleting a data base (data schema) using the cluster management console</li></ul></td><td>DBA rights were required for creating infobases in Oracle Database.</td><td>Increased security of DBMS operations. New scenario of creating an infobase without DBA rights, provided the database (data schema) already exists.</td></tr><tr title="Версия 8.3.1" class="tag_37 tag_69"><td><a name="95b24f63-a0d0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Encoding of text strings is implemented (the global context method <span class="term">EncodeString()</span>). It simplifies the following operations:<ul><li>Converting a text string to a format that allows using it as a part of a URL</li><li>Converting a URL string to a <a href="http://www.faqs.org/rfcs/rfc1738.html" target="_blank">RFC 1738</a>-compliant format</li></ul><p>Decoding of text strings is implemented (method <span class="term">DecodeString()</span>).</p><p>
</p></td><td>This feature was not available.</td><td>Easier generation of URLs containing non-English characters.</td></tr><tr title="Версия 8.3.1" class="tag_10"><td><a name="b3f9eb74-baab-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>You can create a self-extracting archive (SFX archive) of a client application and upload it to a web site. You can include the client application distribution kit and the <span class="interface">1CEStart.cfg</span> configuration file, which is used for installing the client application, into the archive. The created executable file is only intended to run on Windows operating systems. <p>The self-extracting archive is generated using the <span class="interface">1CEClientSetupMake.exe</span> utility, which is distributed via ITS (<a href="http://its.1c.ru/db/metod81#content:4914:1" target="_blank">http://its.1c.ru/db/metod81#content:4914:1</a>).</p></td><td>This feature was not provided.</td><td>Simplified installation of client applications on the client computer for infobase access over the Internet (instead of using the web client).</td></tr></table><p><a href="#e729b97b-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4cc794a2-7d56-11e1-b5d1-e61f135f174b">New functions and changes in the 1C:Enterprise mode</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of change</th></tr></thead><tr title="Версия 8.3.1" class="tag_12"><td><a name="d0b682ec-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br></td><td>The search for references to external data source tables is available for the standard function <span class="interface">Find references to object</span>, which operates in the managed mode.</td><td>It was impossible to find references to objects of external data sources tables using the standard function <span class="interface">Find references to object</span>.</td><td>You can search for references to external data source objects using a standard function.</td></tr><tr title="Версия 8.3.1" class="tag_26"><td><a name="0cddc072-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In a spreadsheet document that is in the read-only mode, you can expand and collapse groups not only using a mouse, but also using keyboard shortcuts and the shortcut menu of the spreadsheet document.</td><td>In a spreadsheet document that was in the read-only mode, expanding and collapsing groups could only be performed using a mouse.</td><td>Improved usability of spreadsheet documents.</td></tr><tr title="Версия 8.3.1" class="tag_66"><td><a name="71712619-8470-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 66); return false;">Navigation links</a>.<br></td><td>In the <span class="interface">In tabs</span> form opening mode when a form is opened by clicking a navigation panel command and the navigation link is requested, if the managed form property <span class="term">AutoUrl</span> is set to <span class="term">True</span>, the form returns a link to the object displayed by the form. Otherwise, it returns the value of the <span class="term">Url </span>property of the managed form.</td><td>In the <span class="interface">In tabs</span> form opening mode forms opened by clicking navigation panel commands returned links to navigation points.</td><td>You can open a list form in a separate window using the shortcut menu of the tab title.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="9439c9c7-87a0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If the <span class="term">EditMode</span> property of a managed form table cell is set to <span class="term">Directly</span>, pressing the <span class="interface">Enter</span> key in this cell moves the cursor to the next editable cell in this row. If the cell is last in a row, the cursor is moved to the first editable cell of the next row. If there is no next row and the managed form table has the <span class="interface">Autoinput new row</span> property set to <span class="term">True</span>, a new row is added.</td><td>In the row editing mode pressing the <span class="interface">Enter</span> key finished editing the table cell and did not move the cursor to the next cell.</td><td>Pressing the <span class="interface">Enter</span> key is handled in the same way in the new row input mode and in the row editing mode. This simplifies working with the platform and enhances editing table data using the keyboard.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="56a0e41b-b6d1-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>While editing a cell of a managed form table with <span class="term">EditMode</span> property set to <span class="term">Directly</span>:<ul><li>Pressing the <span class="interface">Ins</span> key adds a new row;</li><li>Pressing <span class="interface">PgUp</span> or <span class="interface">PgDn</span> moves one table page up or down;</li><li>Pressing <span class="interface">Ctrl+Home</span> or <span class="interface">Ctrl+End</span> moves to the first or to the last table row.</li></ul></td><td>These features were not provided.</td><td>Improved usability of managed form tables.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="56a0e41a-b6d1-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed forms, in automatic table row adding mode, you can delete rows by pressing <span class="interface">Alt+Shift+Del</span>. A row is deleted in the following cases: <ul><li>The row does not contain any data, and you click in any area outside the new row.</li><li>The row does not contain any data, and you move to another row using the keyboard.</li></ul><p>You can use this keyboard shortcut even while you are editing a table row.</p></td><td>This feature was not provided.</td><td>Improved usability of managed form tables.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="9439c9c8-87a0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If you press the <span class="interface">Down Arrow</span> key while the cursor is in the last row of a managed form table, a new row is added. If you press the <span class="interface">Up Arrow</span> key while the cursor is in a new row and the new row is still empty, this row is deleted. If you move the cursor from top to bottom by holding down the <span class="interface">Down Arrow</span> key, the cursor will stop at the last row of the managed form table. To add a new row, release the <span class="interface">Down Arrow</span> key and press it again.</td><td>Pressing the <span class="interface">Down Arrow</span> key did not create a new row. Pressing the <span class="interface">Up Arrow</span> key did not undo the creation of a new row.</td><td>Improved usability of managed form tables.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="f324a4d5-8f5b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For attributes of <span class="term">String</span> type that have fixed length, the automatic marking of incomplete attributes is modified. The change affects attributes located in managed form tables, table boxes or spreadsheet documents. The check whether the attribute is performed using the <span class="term">ValueIsFilled</span><span class="term">()</span> method, so the value of <span class="term">String </span>type is considered incomplete if it does not contain any any characters except spaces.</td><td>An attribute was considered incomplete only if it contained a blank string.</td><td>Unified the behavior of marking of incomplete attributes.</td></tr><tr title="Версия 8.3.1" class="tag_28"><td><a name="d0b682e6-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>When the web client is started in a web browser that is not in the list of supported ones, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per week.</td><td>The check for supported web browsers was not performed.</td><td>The user receives a warning if they use an unsupported web browser or an unsupported version of a supported browser.</td></tr><tr title="Версия 8.3.1" class="tag_28"><td><a name="d0b682e7-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>When the web client is started in a web browser whose version is not supported, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month.</td><td>The check for supported browser versions was not performed.</td><td>The user receives a warning when they use an unsupported web browser or an unsupported version of a supported browser. It is recommended that they change their browser version when they receive the warning.</td></tr><tr title="Версия 8.3.1" class="tag_28"><td><a name="d0b682e8-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>When the web client is started in Microsoft Internet Explorer version later than those available during the platform development, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month.</td><td>The check for supported Microsoft Internet Explorer versions was not performed.</td><td>The user is notified if their Microsoft Internet Explorer version was not tested for compatibility with 1C:Enterprise.</td></tr><tr title="Версия 8.3.1" class="tag_17"><td><a name="d0b682e9-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>You can write information about working with external data sources <p>to the technological log. For this purpose, the <span class="term">&lt;EDS&gt; </span>event is added to the configuration file of the technological log.</p></td><td>Working with external data sources was not reflected in the system technological log.</td><td>A tool for analyzing problems that might occur while working with external data sources.</td></tr><tr title="Версия 8.3.1" class="tag_17"><td><a name="c0f88563-b91a-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 17); return false;">Technological log</a>.<br></td><td>You can have all operations that affect server cluster functioning (for example, operations performed during data replication between cluster services) written to the technological log. For this purpose, the <span class="term">&lt;CLSTR&gt;</span> event is added to the technological log configuration file.</td><td>Events that were generated during the execution of operations that affected server cluster functioning were not reflected in the technological log.</td><td>A tool for analyzing server cluster issues.</td></tr><tr title="Версия 8.3.1" class="tag_6 tag_10"><td><a name="b83b549b-aed8-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>Cross-platform administration server (<span class="interface">RAS</span>) is implemented for administering the server cluster. The application can run both as a standalone application and a service (daemon). The administration server is installed with 1C:Enterprise server.<p>The cross-platform command line utility (<span class="interface">RAC</span>) is implemented for the administrator server. The utility is installed with 1C:Enterprise server. Administration utility version and administration server version may differ. The utility provides the same administration functionality as program cluster administration tools (the <span class="term">V82.ComConnector</span> COM object), </p><p>except operating system authentication of the administrator in infobases, clusters, or working servers. The utility does not support this feature.</p><p>An interface for working with the administration server using Java is also implemented. The interface is distributed via ITS (together with its description and usage example) (<a href="http://its.1c.ru/db/metod81#content:4985:1" target="_blank">http://its.1c.ru/db/metod81#content:4985:1</a>).</p></td><td>Tools for 1C:Enterprise server cluster administration were only available for Windows operating system as a cluster administration console and as <span class="term">V82.ComConnector</span> COM object. Linux tools for server cluster administration were not provided.</td><td>You can administer 1C:Enterprise server cluster using the command line in various operating systems (Windows and Linux), and also from Java programs.</td></tr></table><p><a href="#e729b97b-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4cc794a3-7d56-11e1-b5d1-e61f135f174b">Optimization</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of changes</th></tr></thead><tr title="Версия 8.3.1" class="tag_19"><td><a name="e4aaa639-7e21-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Optimized performance of Oracle DBMS queries that include complex conditions for data access restrictions.</td><td>Insufficient performance of queries that include complex conditions for data access restrictions.</td><td>Improved performance of operations with data access restrictions in Oracle Database.</td></tr><tr title="Версия 8.3.1" class="tag_23"><td><a name="d0b682ee-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Working with memory is optimized for some mechanisms.</td><td>Insufficient performance in certain scenarios.</td><td>Improved overall system performance in some scenarios.</td></tr><tr title="Версия 8.3.1" class="tag_45"><td><a name="d0b682f0-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>When executing a query, for all <span class="term">IN HIERARCHY</span> conditions with the same parameter value a single temporary table per batch query is generated.</td><td>When executing a query, for <span class="term">IN HIERARCHY</span> conditions with the same parameter value several temporary tables were generated.</td><td>Improved the performance of queries containing the same parameter values in several <span class="term">IN HIERARCHY </span>operations.</td></tr><tr title="Версия 8.3.1" class="tag_45"><td><a name="d0b682f1-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>When executing a query, for all <span class="term">IN</span> conditions with the same list of values a single temporary table per batch query (for storing the list) is used.</td><td>When executing a query, for <span class="term">IN</span> conditions with the same list of values several temporary tables were generated, one for each condition.</td><td>Improved the performance of queries containing the same list of values in several <span class="term">IN</span> operations.</td></tr><tr title="Версия 8.3.1" class="tag_45"><td><a name="fc15b2dd-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Improved performance of queries that include the <span class="term">IN HIERARCHY</span> expression. Improved performance of queries that include performing data composition system operations on external data sources by using the <span class="interface">IN GROUP</span> and <span class="interface">IN GROUP</span> <span class="interface">FROM THE LIST</span> expressions.</td><td>Insufficient performance of query and report selections in some cases when hierarchy conditions were used.</td><td>Improved performance of query and report selections in some cases when hierarchy conditions are used.</td></tr><tr title="Версия 8.3.1" class="tag_6 tag_14"><td><a name="fdbf84e5-7970-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br></td><td>The amount of memory consumed by server working processes is significantly reduced. Reduced client application startup time. The effect is especially noticeable on configurations having large volumes of metadata.</td><td>Inefficient use of memory on configurations having large volumes of metadata.</td><td>Memory requirements for servers with configurations having large volumes of metadata are reduced.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="a513e901-78b2-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>For PostgreSQL and Oracle Database, optimized recording register records with update of account register totals. The optimization is achieved by introducing a new index. The performance increase takes effect after restructuring accounting registers and disabling the compatibility mode.</td><td>The data structure did not allow using the existing indexes at their full potential, which led to insufficient system efficiency.</td><td>Improved performance of operations with accounting registers in PostgreSQL and Oracle Database DBMS.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="a513e8fd-78b2-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Improved performance of requests to main tables when Oracle Database is used.</td><td>Response time for some DBMS requests was sub-optimal.</td><td>Improved performance of database requests. This includes a significant increase in the speed of configuration updates that require infobase structure updates.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="f9466833-83a4-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Optimized some accounting register-related DBMS requests. In particular, optimized requests that include filters by account.</td><td>Inefficient usage of DBMS capabilities.</td><td>Improved performance for "heavy" accounting register requests (such as, when creating accounting reports or performing month-end closing).</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="f9466835-83a4-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Optimized operations with temporary tables in Microsoft SQL Server, as well as operations with objects that use temporary tables: accumulation registers, accounting registers, sequences, and so on.</td><td>Insufficient performance in case of heavy usage of temporary tables.</td><td>Improved performance in case of heavy usage of temporary tables in Microsoft SQL Server.</td></tr><tr title="Версия 8.3.1" class="tag_28"><td><a name="7171261c-8470-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Faster start of the web client on slow connections.</td><td>A large amount of service information was obtained during the start of the web client.</td><td>Faster start of the web client on slow connections.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="ebc5a551-8853-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Improved performance of operations with Microsoft SQL Server DBMS in the following cases:<ul><li>reading and writing data;</li><li>loading infobase from the <span class="interface">*.dt</span> file (if the recovery mode is set to <span class="interface">Simple</span> or <span class="interface">Bulk-logged</span>);</li><li>infobase restructuring (if the recovery mode is set to <span class="interface">Simple</span> or <span class="interface">Bulk-logged</span>).</li></ul><p>
</p></td><td>Inefficient usage of DBMS capabilities.</td><td>Improved performance of operations with infobases that use Microsoft SQL Server DBMS.</td></tr><tr title="Версия 8.3.1" class="tag_82"><td><a name="d83203f0-8913-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Improved performance of accounting register operations in the following cases:<ul><li>writing record sets with up to ten records and with several hundred records;</li><li>obtaining totals for a given time;</li><li>generating reports that use the accounting register.</li></ul><p>The performance increase takes effect after infobase restructuring.</p></td><td>Insufficient performance of accounting register operations in certain use cases.</td><td>Improved performance of operations with accounting registers containing a large amount of data.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="b3a28d2f-950a-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The performance of operations with PostgreSQL is improved by changing the index structure. The optimization applies both to new infobases and to existing ones (after restructuring their databases).</td><td>Cluster indexes were not used in PostgreSQL operations; regular indexes were created instead.</td><td>Faster execution of PostgreSQL operations.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="3ac57140-95f5-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>You can use separate table spaces for indexes (the <span class="term">v81c_index</span> space) and for data (the <span class="term">v81c_data</span> space) in PostgreSQL.<p>Table spaces are not created automatically; a database administrator creates them. If no additional table spaces are created, the default table space (<span class="term">pg_default</span>) is used.</p></td><td>Using a single table space might decrease the performance (due to storage medium overload or performance limitations).</td><td>Balancing system performance by recording table spaces to multiple storage media in PostgreSQL.</td></tr><tr title="Версия 8.3.1" class="tag_28"><td><a name="d0b682ed-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br></td><td>Faster opening of the following forms in the web client:<ul><li>Forms located on the main window tabs</li><li>Forms that block windows of their owner forms</li></ul></td><td>Delays when opening forms in the web client.</td><td>Faster form opening, which improves user experience.</td></tr><tr title="Версия 8.3.1" class="tag_45"><td><a name="d0b682ef-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Improved performance retrieving a selection by group (with a large number of records) from a result of a query containing a <span class="term">TOTALS </span>clause.</td><td>Insufficient performance when retrieving a selection by group from a result of a query that contains totals.</td><td>Improved performance when processing results of queries that contain totals.</td></tr><tr title="Версия 8.3.1" class="tag_6"><td><a name="4ca4acde-789a-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Improved server performance and scalability when processing reference data types.</td><td>Insufficient server performance when processing reference data types.</td><td>Improved server performance when processing reference data types.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="4ca4acdd-789a-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Temporary tables containing data of unrestricted length are temporary in IBM DB2 version 8.7 and later.</td><td>For data of unrestricted length, permanent tables were created and then deleted after use.</td><td>System tables cannot get locked. Improved user experience in case when a large number of users are working simultaneously.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="1fc35c20-9b4f-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Certain operations with IBM DB2 are optimized.</td><td>Insufficient usage of IBM DB2 capabilities.</td><td>Faster execution of IBM DB2 operations.</td></tr><tr title="Версия 8.3.1" class="tag_19 tag_82"><td><a name="1fc35c21-9b4f-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br></td><td>Faster processing of accounting register data during database configuration update in the client/server infobase mode.</td><td>Insufficient performance when reconfiguring accounting registers.</td><td>Faster processing of accounting register data during their reconfiguration.</td></tr><tr title="Версия 8.3.1" class="tag_16"><td><a name="13a6296c-94ec-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 16); return false;">Information registers</a>.<br></td><td>Totals are implemented for periodic information registers. They are intended for retrieving first and last slices, provided that the following conditions are met:<ul><li>using totals is allowed (in metadata);</li><li>using totals is enabled (in the 1C:Enterprise mode);</li><li>slice retrieval conditions do not include date;</li><li>slice retrieval conditions only include dimensions and separators;</li><li>data access restrictions for the register only include dimensions and separators.</li></ul><p>Properties <span class="term">EnableTotalsSliceFirst</span> and <span class="term">EnableTotalsSliceLast</span> are implemented for information registers. </p><p>Methods <span class="term">RecalcTotals()</span>, <span class="term">SetTotalsUsing()</span>, and <span class="term">GetTotalsUsing()</span> are implemented for information register managers.</p><p>Access right <span class="term">TotalsControl</span> is implemented for information registers. The <span class="interface">Verify and Repair</span> action in Designer includes recalculation of first and last slices if the <span class="interface">Recalculating totals</span> option is enabled in the <span class="interface">Verifications and modes</span> list and using totals is enabled for the register.</p></td><td>Each slice retrieval resulted in execution of a query to the main register table, with calculation of resource values.</td><td>Faster retrieval of first and last slices for the first and the last (current) moments of time.</td></tr><tr title="Версия 8.3.1" class="compat tag_20 tag_1"><td><a name="4d2c527f-b123-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 20); return false;">Development tools</a>.<br></td><td>Optimized memory usage in the following cases: <ul><li>operations with configurations that are on support</li><li>loading and dumping the <span class="interface">1cv8.dt</span> file</li></ul><p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>In some cases working with configurations that are supported by vendor configurations of large size was impossible.</td><td>Reduced RAM usage when working with vendor configurations of large size.</td></tr></table><p><a href="#e729b97b-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4cc794a4-7d56-11e1-b5d1-e61f135f174b">Changes altering the system behavior</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of change</th></tr></thead><tr title="Версия 8.3.1" class="compat tag_19 tag_1"><td><a name="e4aaa63a-7e21-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>If a database query contains more than 400 levels of expression nesting, an exception occurs but the system is not shut down. This change is not implemented in 8.2.16 compatibility mode.</td><td>If a database query contained more than 400 levels of expression nesting, the system performed emergency shutdown.</td><td>The system stability increased, preventing shutdowns when executing complex queries.</td></tr><tr title="Версия 8.3.1" class="compat tag_177 tag_104 tag_1"><td><a name="d0b682f3-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 177); return false;">Attribute fill checks</a>.<br><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br></td><td>Attributes disabled by a functional option are not included in the list of checked attributes of the <span class="term">FillCheckProcessingAtServer</span><span class="term">()</span><span class="term"> </span>handler.<p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>When generating the list of checked attributes, functional options were not considered.</td><td>Application developers do not need to programmatically exclude attributes disabled by functional options from the check.</td></tr><tr title="Версия 8.3.1" class="compat tag_45 tag_1"><td><a name="d0b682f4-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If there is a list of totals with a grand total in the query result, unloading the query result using the <span class="term">Unload</span> method (<span class="term">QueryResultIteration.ByGroups</span>) of the <span class="term">QueryResult</span> object results in a tree with a single node with the grand total, while nodes for groupings located in the query after the grand total become the tree elements.<p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>If there was a list of totals with a grand total in the query result, unloading of the query result using the <span class="term">Unload</span> method (<span class="term">QueryResultIteration.ByGroups</span>) of the <span class="term">QueryResult</span> object created a tree with several nodes of the same level: the grand total and groupings located in the query after the grand total.</td><td>The query behavior provides more comfortable work with totals when unloading the result to a tree.</td></tr><tr title="Версия 8.3.1" class="compat tag_25 tag_1"><td><a name="0cddc075-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When a data composition result is exported to a collection of values, columns containing calculated fields will have value types specified in the calculated fields. If the calculated field value type is not specified, the value type for the corresponding column is determined automatically based on the calculated field expression.<p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>When a data composition result was exported to a collection of values, the value types for columns that contained calculated fields were always determined automatically based on the calculated field expressions. </td><td>You can specify the calculated field type explicitly in cases when automatic type definition is difficult or impossible.</td></tr><tr title="Версия 8.3.1" class="tag_178"><td><a name="fc15b2e0-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 178); return false;">Client/server interaction</a>.<br></td><td>When the server version is changed, sessions running at the time when the server manager is started are not deleted automatically. When a client application that uses a web server is shut down due to the client/server version difference exception, an attempt to delete the session at the server is made.</td><td>When the server version was changed, the message <span class="interface">Session is missing or deleted</span> was generated. Furthermore, users did not receive messages that clearly described the problem</td><td>When the platform version is changed at the server, users receive messages stating that the client application version and the server version differ (instead of the messages stating that the session is missing or deleted).</td></tr><tr title="Версия 8.3.1" class="tag_67"><td><a name="0cddc07f-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>Working with configuration repository is only possible if the repository version matches the Designer version.</td><td>The check whether the repository version matches Designer version was not performed.</td><td>Prevention of compatibility problems when the configuration repository server and Designer have different versions.</td></tr><tr title="Версия 8.3.1" class="tag_67"><td><a name="0cddc080-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 67); return false;">Configuration repositories</a>.<br></td><td>When Designer operates in batch mode, if the location of the infobase that is bound to the repository is changed, the infobase is rebound to the repository and no warnings are displayed. When the location check is performed for the infobase bound to the repository, the name of computer from which the connection to the infobase in established is ignored for client/server infobases and for file infobases located on network drives.</td><td>In batch mode, a warning about the infobase location change was displayed and user response was expected. When the location check was performed for the infobase bound to the repository, the name of computer from which the connection to the infobase was established was taken into account for client/server infobases and file infobases located on network drives.</td><td>In batch mode, an attempt to access a copy of an infobase bound to the repository from the repository user account that is used for accessing the original infobase will lead to disconnecting the original infobase from the repository. A warning about the infobase location change is not displayed for client/server infobases and for file infobases located on network drives if the connections differ only by the name of computer from which the connection is established. </td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="a513e900-78b2-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The following clustered indexes are created when using IBM DB2 DBMS:<ul><li>for object tables - primary key (reference);</li><li>for tables of totals between accounts - by period;</li><li>for information registers - <span class="term">Dimensions</span>, <span class="term">Dimensions+Period</span>, <span class="term">Recorder+Number</span>, <span class="term">Dimensions+Period</span><span class="term">+Recorder</span><span class="term">+Number</span>, and <span class="term">Dimensions+Period</span> (depending on register type).</li></ul></td><td>When using IBM DB2 DBMS the following indexes were created:<ul><li>for object tables - index by the primary key was not clustered;</li><li>for tables of totals between accounts - no clustered index;</li><li>for information registers - clustered indexes were used only in the following cases: <span class="term">Record</span><span class="term">er</span>, <span class="term">Dimensions</span>, <span class="term">Dimensions+Period </span>(depending on register type).</li></ul></td><td>Unified approach to the implementation of object indexes in various DBMS.</td></tr><tr title="Версия 8.3.1" class="compat tag_179 tag_1"><td><a name="30cc7ae4-83ce-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 179); return false;">Export to Microsoft Excel</a>.<br></td><td>When a spreadsheet document is exported to Microsoft Excel 97 or Microsoft Excel 2007 format, cells of the spreadsheet document that are left-aligned are exported together with their general formatting. This change is not implemented in 8.2.16 compatibility mode.</td><td>When a spreadsheet document was exported to Microsoft Excel 97 or Microsoft Excel 2007, cell values were converted to numbers in the following cases:<ul><li>a number is recognized in the string content, and there is no text data after the number;</li><li>a number is recognized in the string content, and text data is following it, but the cell is right- or center-aligned.</li></ul></td><td>If a cell of a spreadsheet document contains a numeric value, which is intended to be used as text, and the value is left-aligned (e.g., the cell contains a product code or article), when the spreadsheet document is exported to Microsoft Excel format, the cell value is not converted to a number. This simplifies the use of the converted document (including editing and comparison).</td></tr><tr title="Версия 8.3.1" class="tag_69 tag_115"><td><a name="71712616-8470-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>For methods <span class="term">GetForm()</span>, <span class="term">OpenForm()</span>, and <span class="term">OpenFormModal()</span> the <span class="term">URL</span> parameter is implemented. Its value is assigned to the <span class="term">URL</span> property of received or opened forms, unless the parameter value is <span class="term">Undefined</span>. Furthermore, the <span class="term">AutoURL</span> property of received or opened forms is set to <span class="term">False</span>. For the <span class="term">CommandExecuteParameters</span> object the <span class="term">URL</span> property is implemented. The property usage example is added to the command module example.</td><td>This feature was not provided.</td><td>You can specify a navigation link for a form that is being opened. The navigation link can be used later in the interactive mode (e.g., stored in the history).</td></tr><tr title="Версия 8.3.1" class="tag_24"><td><a name="8331a824-853e-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 24); return false;">Infobase users</a>.<br></td><td>When you press <span class="interface">Shift+Del</span> in the list of infobase users, a warning is displayed.</td><td>Pressing <span class="interface">Shift+Del </span>in the list of infobase users deleted a user without a warning.</td><td>Prevention of accidental deletion of infobase users.</td></tr><tr title="Версия 8.3.1" class="tag_116"><td><a name="b013c21e-89df-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>If an application license is not found during the start of the application, the differences between the current hardware settings and hardware settings at the moment when the license was obtained are written to the license search log. This information is only written for software licenses.</td><td>Information on differences in hardware settings was not listed in the license search log.</td><td>Simplified diagnostics of software license problems when the license is not issued due to hardware settings differences.</td></tr><tr title="Версия 8.3.1" class="compat tag_19 tag_52 tag_1"><td><a name="b013c21f-89df-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>In version 8.2.16 compatibility mode, if you use Microsoft SQL Server version 2005 or later and the configuration uses managed lock mode, row versioning is enabled. The transaction isolation level is <span class="term">READ_COMMITED_SNAPSHOT</span>. Consistent read is used for reading data outside of transactions.</td><td>Microsoft SQL Server 2005 or later had a lock mode enabled. The transaction isolation level was <span class="term">READ_COMMITED</span>. "Dirty" read was used for reading data outside of transactions.</td><td>The following improvements are available:<ul><li>Reduced number of locks and deadlocks while executing transaction queries.</li><li>Eliminated errors in the execution of out-of-transaction queries involving frequently modified applied objects.</li><li>Consistent results for reports generated outside of transactions.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_115 tag_25 tag_1"><td><a name="f324a4db-8f5b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>You can implement quick choice user settings as a set of form fields in a separate group. You can manage location and other parameters of this group. The <span class="interface">User settings group</span> property is implemented for managed form extension for reports. You can create user settings items using the <span class="term">CreateUserSettingsFormElements()</span> method of managed form extension for reports. Before settings elements are created, all existing elements are deleted from the group. Forms that are created automatically (report and user settings forms) include dedicated groups with elements used for editing settings. The <span class="term">OnUpdateUserSettingSetAtServer</span> event is implemented for managed report form extension. The event is called in the following cases:<ul><li>when the report form is created;</li><li>after the report variant is loaded;</li><li>after the report variant is changed;</li><li>after user modification of settings.</li></ul><p>Presentation of automatically generated report forms is changed: report variant presentation moved to report title; the variant selection button moved to report command bar, etc. This change is not implemented in 8.2.16 compatibility mode.</p></td><td>Quick choice user settings were edited in a special table located in the form. The form for editing user settings contained a table for editing all user settings.<p>There was a field with current report presentation and a button for selecting report variant in the report form.</p></td><td>Improved report settings usability - they are displayed similarly to other form elements because standard form elements (text box, check box, etc.) are used instead of tables for editing settings.</td></tr><tr title="Версия 8.3.1" class="tag_39"><td><a name="5798fce7-903a-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>When event log is being read, events are not filtered by current separator value if the separator is conditionally disabled in the current session.</td><td>When event log was being read, records were filtered by value of a conditionally disabled separator.</td><td>Eliminated the differences between event log functioning in infobases without separators and infobases with conditionally disabled separators.</td></tr><tr title="Версия 8.3.1" class="compat tag_19 tag_1"><td><a name="b3a28d2d-950a-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>Internal implementation of several query executions for PostgreSQL, IBM DB2, and Oracle Database is modified. This change is not implemented in 8.2.16 compatibility mode.</td><td>The implementation took advantage of DBMS specifics to a lesser extent.</td><td>Improved the internal implementation of query executions for specific DBMS.</td></tr><tr title="Версия 8.3.1" class="compat tag_86 tag_1"><td><a name="71712612-8470-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>Navigation links to lists are implemented. A navigation link request to a form whose main attribute is a dynamic list with the main table specified returns a navigation link to the list of the object specified as the main table. This link opens the default list form. Support of navigation links to lists is implemented for the <span class="term">GotoURLGotoURL()</span> global context method. This change is not implemented in 8.2.16 compatibility mode.</td><td>Navigation links to lists were not provided.</td><td>Users can store links to lists in history and favorites.</td></tr><tr title="Версия 8.3.1" class="tag_180"><td><a name="d0b682f2-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 180); return false;">Configuration comparison reports</a>.<br></td><td>The configuration comparison report no longer includes added and removed objects whose access rights exactly match their default access rights.<p>
</p></td><td>Added and removed objects whose access rights exactly matched their default access rights were included in the report.</td><td>The report no longer displays redundant information that does not help in merging data.</td></tr><tr title="Версия 8.3.1" class="tag_158"><td><a name="e92cc507-7752-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 158); return false;">Third-party software</a>.<br></td><td>Migrated from OpenSSL 1.0.1 to OpenSSL 1.0.0g.</td><td>OpenSSL version 1.0.1 was used.</td><td>An HTTP server query error is no longer displayed when the thin client is started.</td></tr><tr title="Версия 8.3.1" class="tag_23"><td><a name="0cddc069-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>Value length for <span class="interface">Description l</span><span class="interface">ength</span> and <span class="interface">Order leng</span><span class="interface">th</span> properties of <span class="interface">Chart of a</span><span class="interface">ccounts </span>objects is limited by 628 characters. The current value length is only checked when an attempt to change it is made.</td><td>Value length for <span class="interface">Description l</span><span class="interface">ength</span> and <span class="interface">Order leng</span><span class="interface">th</span> properties of <span class="interface">Chart of a</span><span class="interface">ccounts </span>objects was not limited.<p></p></td><td>Increased platform stability. Prevention of infobase corruption (in the file mode). Prevention of performance losses.</td></tr><tr title="Версия 8.3.1" class="compat tag_45 tag_1"><td><a name="d0b682f5-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>If a script generated by the query wizard includes result processing, the name of the variable where the result is stored is <span class="term">QueryResult</span>.<p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>In certain cases (for example, when a query was created with the option to display the processed result in a report), a naming conflict occurred between variable names created by the wizard and attribute names of the report form whose module contained this code. As a result, the generated code did not work properly.</td><td>Eliminated naming conflicts between variable names created by the query wizard and report form attribute names (for queries that include result processing).</td></tr><tr title="Версия 8.3.1" class="compat tag_25 tag_1"><td><a name="55463269-77f0-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>A query field used in a union operation becomes unavailable to filters if it has the <span class="term">NULL</span> value in all parts of the union. This change is not implemented in 8.2.16 compatibility mode.</td><td>If a query field used in a union operation had the <span class="term">NULL</span> value in all parts of the union, filters were applied at the data set level of data composition template, not inside the query.</td><td>When the <span class="term">UNION</span> or <span class="term">UNION ALL</span> expression is used in a query that retrieves a data set of the data composition system (with automatic filling of available settings), if a filter is applied to a field attribute, the filter is only applied to the parts of the union where the given attribute exists. When a filter is applied to a field, it is only applied to the parts where the field expression is not equal to <span class="term">NULL</span>. </td></tr><tr title="Версия 8.3.1" class="tag_39"><td><a name="0cddc071-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br></td><td>The <span class="interface">*.elf</span> extension is removed from the <span class="interface">Files of type </span>list in the open file dialog box in the thick client and Designer. Opening event logs in the <span class="interface">*.elf</span> format is still supported. To open an <span class="interface">.elf</span> file, select the <span class="interface">Event log (*.lgf)</span> file type and then enter the file name, including the <span class="interface">elf </span>extension.</td><td>The list of file extensions in the open file dialog box in the thick client and Designer included both <span class="interface">*.lgf</span> and <span class="interface">*.elf</span> extensions.</td><td>Removed obsolete user interface options.</td></tr><tr title="Версия 8.3.1" class="compat tag_39 tag_64 tag_1"><td><a name="0cddc076-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 39); return false;">Event log</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Events related to canceled transactions are displayed in gray in the ordinary form of the event log (in the same way as they are displayed in the managed form of the event log). This change is not implemented in 8.1 compatibility mode.</td><td>Events related to canceled transactions were displayed in black in the ordinary form of the event log.</td><td>Unification of display of ordinary and managed forms of the event log.</td></tr><tr title="Версия 8.3.1" class="tag_12 tag_64"><td><a name="0cddc07a-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 12); return false;">Standard functions</a>.<br><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br></td><td>Object presentation in standard functions <span class="interface">Find references to object</span> and <span class="interface">Delete marked</span><span class="interface"> objects</span> is modified. Names of metadata objects types are removed from object presentations.</td><td>In standard functions <span class="interface">Find references to object</span> and <span class="interface">Delete marked</span><span class="interface"> objects</span> object presentation contained the name of metadata object type.</td><td>System-standard object presentation is introduced.</td></tr><tr title="Версия 8.3.1" class="tag_42 tag_82 tag_58 tag_6"><td><a name="91088294-856d-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>Changes in the table of storage settings for accumulation and accounting register totals are performed within a transaction. While tables are being modified, managed data locks are applied to the corresponding lock namespace.<p>A cache for storing totals storage settings for working processes is implemented.</p></td><td>Changes in the tables of storage settings for accumulation and accounting register totals were performed outside a transaction. Each retrieval of totals storage settings was performed using a database query.</td><td>Elimination of conflicts that might occur during the modification of totals storage settings tables from multiple simultaneous sessions that have identical data separator values.<p>Reducing the number of database queries and improving parallel processing for sessions that use separators.</p></td></tr><tr title="Версия 8.3.1" class="tag_58 tag_82 tag_42"><td><a name="91088295-856d-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 58); return false;">Common attributes / Data separation</a>.<br><a href="#" onclick="onTagClick(this, 82); return false;">Accounting registers</a>.<br><a href="#" onclick="onTagClick(this, 42); return false;">Accumulation registers</a>.<br></td><td>If separators are deleted or separator types are modified, during the next update of database configuration records in the tables of totals storage settings for accounting and accumulation registers are merged according to the new sets of separators.</td><td>If separators were deleted or separator types were modified, the following situations might occur:<ul><li>Inserting records with identical values in a table of totals storage settings.</li><li>Database update errors due to attempts to insert records with identical values.</li></ul></td><td>Improved reliability of operations during database configuration updates caused by deleting separators or modifying separator types.</td></tr><tr title="Версия 8.3.1" class="compat tag_181 tag_1"><td><a name="0cddc07c-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 181); return false;">Text operations</a>.<br></td><td>Implemented recording a byte order mark (<span class="interface">BOM</span>) to the beginning of files generated by the <span class="term">TextWriter</span> object if the following conditions are met: the file to be recorded does not yet exist, the <span class="term">FinishWriter</span> constructor parameter is set to <span class="term">True</span>, and the text encoding is set to UTF-8.<p>This change is not implemented in the compatibility with 8.2.16 mode.</p></td><td>A byte order mark (<span class="interface">BOM</span>) was not added to the beginning of files generated by the <span class="term">TextWriter</span> object if the following conditions were met: the file to be recorded does not yet exist, the <span class="term">FinishWriter</span> constructor parameter is set to <span class="term">True</span>, and the text encoding is set to UTF-8.</td><td>A byte order mark (<span class="interface">BOM</span>) ensures unique identification of text encoding used in a file.</td></tr><tr title="Версия 8.3.1" class="tag_56"><td><a name="fc15b2df-78cd-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 56); return false;">XML and XDTO support</a>.<br></td><td>During the import of XSD schema, if definition is missing from the target namespace schema, a diagnostic message is displayed.</td><td>During the import of XSD schema, if any loading problems occurred, a diagnostic message was not displayed.</td><td>Improved diagnostics during XSD schema import.</td></tr><tr title="Версия 8.3.1" class="tag_19"><td><a name="9439c9cb-87a0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>The documentation describes the specifics of working with the following DBMS: Oracle Database and PostgreSQL.</td><td>The documentation did not contain enough details about the specifics of working with the following DBMS: Oracle Database and PostgreSQL.</td><td>Documentation is expanded to clarify DBMS usage specifics during configuration development.</td></tr><tr title="Версия 8.3.1" class="tag_26"><td><a name="a513e903-78b2-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>While you are changing the selection area in a spreadsheet document, if the selection area contains rows with different formatting, the platform switches to the row selection mode. Then, if the platform previously was in cell selection mode and after another selection change all selected rows have the same formatting, the platform switches back to the cell selection mode.</td><td>The only ways to select rows with different formatting were using headers of spreadsheet document rows or the <span class="interface">Alt+Shift+Arrows </span>key combination. </td><td>Simplified copying of data from spreadsheet documents with different row formatting.</td></tr><tr title="Версия 8.3.1" class="tag_28 tag_26"><td><a name="95b24f64-a0d0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Users can edit spreadsheet documents in the web client. The <span class="interface">Table</span> main menu is modified in the web client. Clipboard is implemented for spreadsheet documents in Google Chrome web browser. The clipboard is available within a single browser instance working with a single infobase.</td><td>This feature was not provided (except editing cells with values, changing the display mode of groupings, freezing rows and columns, and changing column width).</td><td>Users can edit spreadsheet documents after they are generated in the web client.</td></tr><tr title="Версия 8.3.1" class="tag_14 tag_28 tag_135 tag_26"><td><a name="907077e0-a8cf-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 14); return false;">Client application</a>.<br><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 135); return false;">Designer</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>In the <span class="interface">Table</span> menu of thin client, web client, thick client, and Designer, the <span class="interface">Cells</span> submenu is implemented. It includes some of the commands that were previously located in the <span class="interface">Table</span> menu, and some new commands.</td><td>The <span class="interface">Cells</span> submenu was not available in the <span class="interface">Table</span> menu of thin client, web client, thick client, and Designer.</td><td>Improved usability of spreadsheet documents. Menu items intended for working with spreadsheet document cells are grouped into a single submenu.</td></tr><tr title="Версия 8.3.1" class="tag_182"><td><a name="9962fe01-afa6-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 182); return false;">Dynamic update</a>.<br></td><td>Improved reliability of dynamic update in various situations.</td><td>In certain situations dynamic update worked improperly.</td><td>Improved reliability of dynamic update operations.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="ef8ac4f1-c4cb-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>If a width limit is set for a regular group in a managed form, the size of buttons within the group is adjusted (similar to adjusting the size of other elements included in the group).</td><td>A width limit set for a regular group might not affect the size of buttons within the group.</td><td>Unified the algorithm of adjusting element sizes when a width limit is set for a regular group.</td></tr><tr title="Версия 8.3.1" class="tag_64 tag_115"><td><a name="8331a827-853e-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 64); return false;">Data display</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Tooltips of managed form items can have one of the following types: displayed directly in the text box, displayed near the form item, and opened clicking a button (in a pop-up window). If a tooltip is not specified for a form item, the command bar button linked to this item also does not have a tooltip.<p>You can use the <span class="term">InputHint</span> property, which contains tooltip text, to display a tooltip directly in the text box. This type of tooltip is unavailable for text boxes that display data of <span class="term">Number</span> and <span class="term">Date</span> types.</p><p>To manage the display of tooltips and their appearance, the <span class="term">ExtendedTooltip</span> and <span class="term">TooltipDisplay</span> properties are implemented for the following form controls: field, table, group, button, and decoration of <span class="term">Text</span> type.</p></td><td>Tooltips were only available in pop-up windows of form items. If a tooltip was not specified for a form item, its title was used as a tooltip for the command bar button linked to this item.</td><td>You can manage tooltip formatting and tooltip positions.</td></tr></table><p><a href="#e729b97b-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4cc794a5-7d56-11e1-b5d1-e61f135f174b">Changes that require changes to the configuration and administrative settings</a></h2><table cols="4"><thead><tr><th width="20%">Functionality</th><th width="26%">After</th><th width="26%">Before</th><th width="26%">Result of change</th></tr></thead><tr title="Версия 8.3.1" class="tag_183"><td><a name="285a2e38-a64b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 183); return false;">1C:Enterprise software system</a>.<br></td><td>1C:Enterprise version is changed to <b>8.3</b>.<p>Installation directories are changed:</p><ul><li>For Windows: <span class="interface">C:\Program Files\1cv8</span>;</li><li>For Linux: <span class="interface">/opt/1С/v8.3</span>.</li></ul><p>Names of installation files are changed:</p><ul><li>For Windows: <span class="interface">1CEnterprise 8*.msi</span>;</li><li>For Linux: <span class="interface">1С_Enterprise83*</span>.</li></ul><p>Names of COM objects are changed: <span class="term">V83.Application</span>, <span class="term">V83.ComConnector</span>.</p><p>The server service name is :</p><ul><li>For Windows: <span class="interface">1C:Enterprise 8.3</span><span class="interface"> Server Agent</span>;</li><li>For Linux: <span class="interface">srv1cv83</span>.</li></ul><p>The default name of the user on whose behalf the server service starts is <span class="interface">usr1cv8</span>.</p><p>Default template directory is changed: <span class="interface">%APPDATA%\1C\1Cv8\tmplts</span>.</p><p>Add-in installation directory is changed: <span class="interface">%APPDATA%\1C\1Cv8\ExCompT</span>.</p></td><td>1C:Enterprise version was 8.2.<p>Installation directories had the following names:</p><ul><li>For Windows: <span class="interface">C:\Program Files\1cv82</span>;</li><li>For Linux: <span class="interface">/opt/1С/v8.2</span>.</li></ul><p>Installation files had the following names:</p><ul><li>For Windows: <span class="interface">1CEnterprise 8.2</span><span class="interface">*.msi</span>;</li><li>For Linux: <span class="interface">1С_Enterprise82</span><span class="interface">*</span>.</li></ul><p>COM objects had the following names: : <span class="term">V82</span><span class="term">.Application</span>, <span class="term">V82</span><span class="term">.ComConnector</span>.</p><p>The server service had the following name:</p><ul><li>For Windows: <span class="interface">1C:Enterprise 8.2</span><span class="interface"> Server Agent</span>;</li><li>For Linux: <span class="interface">srv1cv82</span>.</li></ul><p>The default name of the user on whose behalf the server service started was <span class="interface">usr1cv82</span>.</p><p>Default template directory was <span class="interface">%APPDATA%\1C\1Cv82\tmplts</span>.</p><p>Add-ins installation directory was <span class="interface">%APPDATA%\1C\1Cv82\ExCompT</span>.</p></td><td>Due to the version number change, names and identifiers that include the version number are changed.</td></tr><tr title="Версия 8.3.1" class="compat tag_23 tag_1"><td><a name="e92cc50b-7752-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 23); return false;">Applied objects</a>.<br></td><td>In a document journal the attribute containing the document number is generated with fixed length if all documents included in the journal have a number field of <span class="term">String</span> type of fixed length. Otherwise, the journal field will have variable length. This change is not implemented in 8.2.16 compatibility mode.</td><td>In a document journal the attribute containing the number of documents was always generated with fixed length.</td><td>The document number is retrieved in a uniform way, which does not depend on the retrieval method (from the document itself or from the document journal).</td></tr><tr title="Версия 8.3.1" class="compat tag_26 tag_1"><td><a name="d0b682f9-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>When any of the spreadsheet document methods <span class="term">Show()</span>, <span class="term">Print()</span>, <span class="term">Hide(</span><span class="term">)</span>, and <span class="term">Write()</span> is called at server or in an external connection with the <span class="term">SpreadsheetDocumentFileType</span> parameter set to <span class="term">XLS95</span>, an exception occurs. This change is not implemented in 8.2.16 compatibility mode.</td><td>When the method was called at server or in an external connection, this did not lead to an error, but the method did not perform any actions either.</td><td>Simplified detection of configuration errors related to specifying incorrect file type when working with a spreadsheet document at server or in an external connection.</td></tr><tr title="Версия 8.3.1" class="compat tag_45 tag_1"><td><a name="d0b682fa-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 45); return false;">Queries</a>.<br></td><td>Specifying type qualifiers in the <span class="term">Type()</span> function of the query language is not allowed. This change is not implemented in 8.2.16 compatibility mode.</td><td>Specifying type qualifiers for the Type() function was allowed, but it did not affect the returned values.</td><td>Implemented a check that eliminates the chance to misuse the query language syntax.</td></tr><tr title="Версия 8.3.1" class="compat tag_26 tag_1"><td><a name="d0b682fb-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Print scaling of a spreadsheet document does not affect its margin size. This change is not implemented in 8.2.16 compatibility mode.</td><td>Print scaling of a spreadsheet document affected its margin size.</td><td>Independent management of margin size and print scaling.</td></tr><tr title="Версия 8.3.1" class="compat tag_25 tag_1"><td><a name="a513e905-78b2-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>When data composition result is put into a collection of values, fields belonging to different groups and referencing to the same data composition field are put in the same collection column. This change is not implemented in 8.2.16 compatibility mode.</td><td>When data composition result was put into a collection of values, fields belonging to different groups and referencing to the same data composition field were put in different collection columns.</td><td>Output of the result to a collection is performed in the same way as output of the result to a spreadsheet document.</td></tr><tr title="Версия 8.3.1" class="compat tag_86 tag_69 tag_1"><td><a name="71712618-8470-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>Format of navigation links to navigation points generated by standard command is modified to the following: <span class="term">e1cib/navigationpoint/Purchases</span><span class="term">/Catalog</span><span class="term">.Products</span><span class="term">.OpenList </span>(example link). The former navigation link format is also supported.<p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>Navigation links to navigation points generated by standard commands had the following format: <span class="term">e1cib/navigationpoint/Purchases</span><span class="term">/Catalog</span><span class="term">.Products</span><span class="term">.Command</span><span class="term">.OpenList </span>(example link).</td><td>Unified usage of metadata names.</td></tr><tr title="Версия 8.3.1" class="compat tag_19 tag_62 tag_1"><td><a name="add3c1db-8494-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br><a href="#" onclick="onTagClick(this, 62); return false;">External data sources</a>.<br></td><td>If the <span class="interface">Name in the data source property</span> of an external data source field contains a value enclosed in single straight quotation marks, when a DBMS query is generated, this value is not enclosed in double straight quotation marks. Otherwise, if the field value contains special characters, it is enclosed in double straight quotation marks. This change is not implemented in 8.2.16 compatibility mode.</td><td>If the <span class="interface">Name in the data source property</span> of an external data source field contained special characters (including single straight quotation marks), the value was enclosed in double straight quotation marks.</td><td>Compatibility with DMBS that use different field description syntaxes in their query and database fields (for example, MySQL).</td></tr><tr title="Версия 8.3.1" class="tag_116"><td><a name="9439c9ca-87a0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>The search for available licenses covers all folders where they might be located.</td><td>The search for available licenses only covered <span class="interface">*.lic</span> files stored in the first folder of the list and skipped any other folders where the license files might be located, regardless of whether the license was found in the first folder.</td><td>Increased flexibility of the licensing mechanism. Elimination of problems that occured when the license files were located in multiple folders (for example, the first folder that was searched contained a server license, while another folder contained a multiuser license).</td></tr><tr title="Версия 8.3.1" class="compat tag_115 tag_1"><td><a name="e92cc505-7752-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>In managed forms, the platform does not read data from hidden dynamic lists. When a form is opened, the value of the <span class="term">CurrentRow</span> attribute of the managed form table connected to the dynamic list is <span class="term">Undefined</span>. The <span class="term">CurrentRow</span> attribute value is changed at the moment when the table is displayed to the user. This change is not implemented in 8.2.16 compatibility mode.</td><td>In managed forms, the platform read data from all dynamic lists, whether they were displayed on the form or not.</td><td>Reduced time for opening forms that contain multiple pages with dynamic lists.</td></tr><tr title="Версия 8.3.1" class="compat tag_104 tag_115 tag_1"><td><a name="411eaeb4-95af-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Behavior of the following form elements related to functional options is modified:<ul><li>Form attributes of reference type are disabled if configuration objects that determine their type are disabled by functional options. Form attributes of complex type are disabled if functional options disable all types that form the complex type.</li><li>Form attributes of <span class="term">&lt;Type&gt;Object</span> type (e.g., the main attribute of the form) are disabled if configuration objects that determine their type are disabled by functional options.</li><li>Form tables are disabled if they display data belonging to attributes disabled by functional options.</li><li>Types are not included in type selection dialogs (e.g., in text boxes connected with attributes of complex types) if configuration objects that determine these types are disabled by a functional option. Information on types disabled by functional options is cached at the client and is cleared in 20 minutes or when the <span class="term">RefreshInterface()</span> method is called.</li></ul><p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>Attributes and form elements had the following behavior:<ul><li>Form attributes of reference type were not disabled when configuration objects that determined their type were disabled by functional options.</li><li>Form attributes of <span class="term">&lt;</span><span class="term">Type&gt;Object</span> type were not disabled if configuration objects that determined their type were disabled by functional options.</li><li>Form tables were not disabled if they displayed data belonging to attributes disabled by functional options.</li><li>Type selection dialogs contained all types, including those disabled by functional options.</li></ul></td><td>Increased effect of default functional option values on the data composition system. Unification of functional option effect on various application elements. <p>
</p></td></tr><tr title="Версия 8.3.1" class="compat tag_104 tag_25 tag_1"><td><a name="411eaeb5-95af-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br></td><td>Functional option effect on the data composition system is modified:<ul><li>A data composition system field becomes unavailable if it is connected to attributes whose types are disabled by functional options.</li><li>A query table and attributes of this table become unavailable if a functional option disables the configuration object forming this table.</li></ul><p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>The data composition system did not disable fields or query tables connected to data whose type was disabled by functional options.</td><td>Increased automatic effect of functional options on the data composition system. Unification of functional option effect on various application elements.</td></tr><tr title="Версия 8.3.1" class="compat tag_104 tag_86 tag_1"><td><a name="411eaeb6-95af-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 104); return false;">Functional options</a>.<br><a href="#" onclick="onTagClick(this, 86); return false;">Command interface</a>.<br></td><td>Commands of the command interface become unavailable in the following cases:<ul><li>An attribute, which is a command parameter, is disabled by a functional option.</li><li>A command parameter type is disabled by a functional option. If the command parameter has complex type, the command becomes unavailable if all of the parameter types are disabled.</li></ul><p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>The command availability was not changed if the availability of the attribute, which was used as a parameter for the command, was changed, or when the command parameter type was disabled by a functional option.</td><td>Increased effect of functional options on the data composition system. Unification of functional option effect on various application elements.</td></tr><tr title="Версия 8.3.1" class="tag_25 tag_26"><td><a name="3ac5713f-95f5-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 25); return false;">Data composition system</a>.<br><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>You can fix rows and columns of a spreadsheet document using the <span class="term">FixedLeft</span> and <span class="term">FixedTop</span> output parameters. If the fixed area exceeds the displayed area, the fixing is automatically turned off.</td><td>The data composition system always used fixing of rows and columns in reports. In spreadsheet documents the fixed area might be larger than the displayed area.</td><td>Improved usability of row and column fixing in reports. Users can disable fixing in reports when they find it inconvenient. Fixing is disabled automatically when it does not allow scrolling of the spreadsheet document.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="d0b682fd-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>It is recommended that you use methods <span class="term">SetObjectAndFormConformity</span><span class="term">()</span> and <span class="term">GetObjectAndFormConformity</span><span class="term">()</span>.<p>Methods <span class="term">SetObjectAndFormAttributeConformity</span><span class="term">()</span> and <span class="term">GetObjectAndFormAttributeConformity</span><span class="term">()</span> are declared deprecated, they are only supported for compatibility purposes.</p></td><td>Methods <span class="term">SetObjectAndFormAttributeConformity</span><span class="term">()</span> and <span class="term">GetObjectAndFormAttributeConformity</span><span class="term">()</span> were not declared deprecated.</td><td>New methods with enhanced functionality are implemented, while the old ones that provide similar functionality are declared deprecated.</td></tr><tr title="Версия 8.3.1" class="compat tag_184 tag_1"><td><a name="d0b682f6-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 184); return false;">Lock manager</a>.<br></td><td>When using the <span class="term">Range</span> object constructor, an exception is thrown if the left range boundary is greater than the right one. This change is not implemented in 8.2.16 compatibility mode.</td><td>Using the <span class="term">Range</span> object constructor was allowed when the left boundary of the range was greater than the right one.</td><td>Elimination of unpredictable behavior of the managed locks manager. Elimination of developer errors.</td></tr><tr title="Версия 8.3.1" class="compat tag_52 tag_1"><td><a name="0cddc068-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 52); return false;">Managed locks</a>.<br></td><td>When a managed lock is set in the file mode of the infobase, types are validated for the values located in the DataSource attribute of the DataLockItem object. This change is not implemented in 8.2.16 compatibility mode.</td><td>Validation of the value types was not performed in the file mode.</td><td>Unified behavior in the file and client/server modes. Easier detections of errors in the applied solution.</td></tr><tr title="Версия 8.3.1" class="compat tag_69 tag_1"><td><a name="d0b682f7-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 69); return false;">1C:Enterprise script</a>.<br></td><td>An attempt to assign a value to an item of a fixed structure causes an exception. This change is not implemented in 8.2.16 compatibility mode.</td><td>An attempt to assign a value to an item of a fixed structure did not cause an exception, and the value was not assigned.</td><td>Behavior of fixed structures is similar to behavior of other fixed collections.</td></tr><tr title="Версия 8.3.1" class="tag_28 tag_29"><td><a name="d0b682f8-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Mozilla Firefox versions 3.0 and 3.5 are no longer supported.</td><td>Mozilla Firefox versions 3.0 and 3.5 were supported.</td><td>Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported.</td></tr><tr title="Версия 8.3.1" class="tag_28 tag_29"><td><a name="e92cc509-7752-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 28); return false;">Web client</a>.<br><a href="#" onclick="onTagClick(this, 29); return false;">System requirements</a>.<br></td><td>Microsoft Internet Explorer version 6.0 is no longer supported. The warning that was displayed when the web client was started in Microsoft Internet Explorer 6.0 is changed to the warning about unsupported web browser.</td><td>Microsoft Internet Explorer version 6.0 was supported.</td><td>Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported.</td></tr><tr title="Версия 8.3.1" class="compat tag_26 tag_1"><td><a name="d0b682fc-7266-11e1-baae-e0cb4ed5ef3d"></a><a href="#" onclick="onTagClick(this, 26); return false;">Spreadsheet documents</a>.<br></td><td>Whenever a spreadsheet document is transferred between the client and the server, the values of its <span class="term">ReadOnly</span> and <span class="term">Protection </span>properties are preserved.<p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>Whenever a spreadsheet document was transferred between the client and the server, the values of its <span class="term">ReadOnly</span> and <span class="term">Protection </span>properties were set to <span class="term">F</span><span class="term">alse</span>.</td><td>Whenever a spreadsheet document is transferred between the client and the server, its properties are preserved in a uniform way.</td></tr><tr title="Версия 8.3.1" class="tag_111"><td><a name="0cddc079-77f5-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 111); return false;">Formatted documents</a>.<br></td><td>Formatted document object model is extended. The document text consists of paragraphs of various types, which are included in the paragraph collection. A paragraph consists of items included in the formatted document item collection. Functionalities for paragraph and item management are implemented.<p>Methods <span class="term">GetItems</span><span class="term">() </span>and <span class="term">GenerateItems()</span> return the array of formatted document items located between the specified bookmarks. Method <span class="term">FindText</span><span class="term">()</span> returns the formatted document area (<span class="term">FormattedDocumentRange </span>object) that contains the specified text.</p><p>The <span class="term">ItemType</span> parameter type in methods <span class="term">Add</span><span class="term">()</span> and <span class="term">Insert</span><span class="term">()</span> of the <span class="term">FormattedDocument </span>object was changed.</p><p>Methods <span class="term">Add</span><span class="term">()</span> and <span class="term">Insert</span><span class="term">()</span> of the <span class="term">FormattedDocument</span> object return the added/inserted item.</p><p>You can add a picture by specifying its URL (in text format).</p><p>It is recommended that you do not add or insert pictures using binary data, this options is present for compatibility purposes only. It is recommended that you use the <span class="term">Picture</span> object for inserting pictures.</p><p>
</p><p>
</p></td><td>Formatted document text was not represented as an object model.</td><td>You can implement various text processing algorithms that are based on standard formatting elements (paragraphs, lists, and so on). Automated text generation is now simpler.</td></tr><tr title="Версия 8.3.1" class="compat tag_97 tag_1"><td><a name="a513e8ff-78b2-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 97); return false;">Data access restrictions</a>.<br></td><td>If the <span class="term">Update </span>right of an object includes data access restrictions with conditions that apply to tabular section attributes, writing the object after it was modified is only allowed if tabular section data before and after the modification match the data access restrictions.<p>Requests from data access restrictions to tabular sections increase the processing time.</p><p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>If the <span class="term">Update </span>right of an object included data access restrictions with conditions that applied to tabular section attributes, then whenever tabular section attributes were modified, their compliance with the data access restrictions was not be verified.</td><td>Data access restrictions apply to object data and object tabular section data in a uniform way.</td></tr><tr title="Версия 8.3.1" class="compat tag_19 tag_1"><td><a name="92e7ce45-7973-11e1-b5d1-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 19); return false;">DBMS operations</a>.<br></td><td>For complex Oracle Database queries of certain type, DBMS request generation rules are modified. Cases that led to DBMS errors are eliminated. A slowdown in DBMS request execution can occur if there are many join operations. It is recommended that you do not use queries with a large number of join operations. This change is not implemented in 8.2.16 compatibility mode.</td><td>When executing complex Oracle Database queries of certain type, DBMS errors might occur in some cases.</td><td>Improved stability when using Oracle Database.</td></tr><tr title="Версия 8.3.1" class="tag_37"><td><a name="95b24f61-a0d0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>You can use secure versions of SMTP and POP3.<p>The following properties are implemented for the <span class="term">InternetMailProfile</span> object: <span class="term">SMTPUseSSL</span>, <span class="term">POP3UseSSL</span>, <span class="term">IMAPSecureAuthenticationOnly</span>, <span class="term">SMTPSecureAuthenticationOnly</span>, and <span class="term">POP3SecureAuthenticationOnly</span>.</p><p>POP3 supports the <span class="term">GetMessageCount</span><span class="term">()</span> method of the <span class="term">InternetMail</span> object.</p><p>It is recommended that you do not use <span class="term">SMTPAuthentication</span> and <span class="term">POP3Authentication</span> properties of the<span class="term">InternetMailProfile</span> object, as well as <span class="term">SMTPAuthenticationMode</span> and <span class="term">POP3AuthenticationMode</span> enumerations. <span class="term">SMTPAuthentication</span> and <span class="term">POP3Authentication</span> properties, as well as <span class="term">SMTPAuthenticationMode</span> and <span class="term">POP3</span><span class="term">AuthenticationMode </span>enumerations are supported for compatibility. It is recommended that you use <span class="term">SMTPSecureAuthenticationOnly</span> and <span class="term">POP3SecureAuthenticationOnly</span> properties of the <span class="term">InternetMailProfile</span> object.</p></td><td>The <span class="term">InternetMail</span> object did not supportsecure versions of SMTP and POP3.</td><td>You can use secure versions of SMTP and POP3.</td></tr><tr title="Версия 8.3.1" class="compat tag_37 tag_1"><td><a name="95b24f62-a0d0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 37); return false;">Internet-enabled functionality</a>.<br></td><td>Default values are changed for <span class="term">InternetMailProfile </span>object properties that store port numbers:<ul><li>The default <span class="term">SMTPPort</span> value is 0, which means port 25 for nonsecure connections and port 465 for secure connections.</li><li>The default <span class="term">POP3Port </span>value is 0, which means port 110 for nonsecure connections and port 995 for secure connections.</li><li>The default <span class="term">IMAPPort </span>value is 0, which means port 143 for nonsecure connections and port 993 for secure connections.</li></ul><p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>The <span class="term">InternetMailProfile </span>object properties that store port numbers had the following default values:<ul><li><span class="term">SMTPPort</span> - 25.</li><li><span class="term">POP3Port </span>- 110.</li><li><span class="term">IMAPPort </span>- 143.</li></ul></td><td>Simplified port setup for the <span class="term">InternetMailProfile </span>object. In most cases the default port values suffice.</td></tr><tr title="Версия 8.3.1" class="tag_115"><td><a name="95b24f66-a0d0-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 115); return false;">Managed forms</a>.<br></td><td>Changed the behavior of the drop-down list in form fields that contain reference data types, enumerations, or system enumerations. Changed the look and behavior of the drop-down list. The system storage settings now store the history of previously selected values (the <span class="term">ChoiceHistory </span>setting).<p>If user-generated lists, using a value of the <span class="term">FormattedString </span>type as a value presentation is allowed.</p><p>This change is not implemented in 8.2.16 compatibility mode.</p></td><td>The drop-down list had a different look and behavior. The choice list did not appear in the drop-down list.</td><td>Better usability of fields, which display data of reference types, enumerations, or system enumerations.</td></tr><tr title="Версия 8.3.1" class="tag_15"><td><a name="668a8fc5-a562-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 15); return false;">Linux</a>.<br></td><td>The configuration utility for Linux is named <span class="interface">config_system</span>.</td><td>The configuration utility for Linux was named <span class="interface">config_server</span>.</td><td>The new utility name provides a better description of its purpose because it performs the environment check not only at the server side, but also at the client application side.</td></tr><tr title="Версия 8.3.1" class="tag_124"><td><a name="285a2e3b-a64b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 124); return false;">Administration</a>.<br></td><td>The <span class="interface">location.cfg</span> configuration file stores the list of directories where 1C:Enterprise searches for system data.<p>During the installation of version 8.3, the search for data (user profiles, configuration files, software license files, etc.) belonging to version 8.2 is performed in directories available to the current user. If directories with data belonging to version 8.2 are found, then <span class="interface">location.cfg</span> files are generated in the directories intended for storing data in version 8.3. These files contain links to directories with data from version 8.2. Therefore, installing the new version does not require transferring all data and settings from version 8.2 directories to version 8.3 directories.</p></td><td>This feature was not provided.</td><td>After installing version 8.3, you can use a single list of settings for version 8.2.16 and version 8.3.</td></tr><tr title="Версия 8.3.1" class="tag_116"><td><a name="285a2e39-a64b-11e1-991e-e41f136d174a"></a><a href="#" onclick="onTagClick(this, 116); return false;">Software licensing</a>.<br></td><td>If the software license is activated "for all users" or using 1C:Enterprise server, the following directory is used for storing software licenses:<ul><li>on Windows: <span class="interface">%ALLUSERSPROFILE%\Application </span><span class="interface">Data\1C\licenses</span> (<span class="interface">%ALLUSERSPROFILE%\</span><span class="interface">1C\licenses</span> - for Windows Vista and later);</li><li>on Linux: <span class="interface">/var/1C/licenses</span>.</li></ul><p>The directory is created during 1C:Enterprise installation.</p><p>Rights for accessing the created directory are granted depending on the operating system being used:</p><ul><li>On Windows, read and write rights are granted to the user under whose account the server service runs. If the service is not installed, the rights for accessing the directory are not changed.</li><li>On Linux, the user group <span class="interface">grp1cv8</span> is created. All users under whose names the server daemon runs must be included into this group. The following rights are set for the created directory: owner - <span class="interface">root</span>, rights - read and write; owner group - <span class="interface">grp1cv8</span>, rights - read and write; other users are granted the read only right.</li></ul><p>Only users with administrative rights can obtain a client license "for all users".</p></td><td>The following directory was used for storing the software license files:<ul><li>on Windows: <span class="interface">%ALLUSERSPROFILE%\Application Data\1C\1Cv82\Conf</span> (<span class="interface">%ALLUSERSPROFILE%\1C\1Cv82\Conf</span> for Windows Vista and later);</li><li>on Linux: <span class="interface">~/.1cv82/conf</span>.</li></ul><p>On Windows, the directory was used when the software license was activated "for all users", and on Linux - when the software license was activated using 1C:Enterprise server.</p></td><td>Administration of software license files is made easier. 1C:Enteprise versions 8.2.16 and 8.3 can use the same set of licenses when their software licenses are activated "for all users" or using 1C:Enterprise server.</td></tr><tr title="Версия 8.3.1" class="compat tag_6 tag_10 tag_1"><td><a name="b83b549d-aed8-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br><a href="#" onclick="onTagClick(this, 10); return false;">Administration tools</a>.<br></td><td>The server cluster administration scheme is modified. The management of cluster processes and function distribution between these processes are performed automatically, and therefore the option to manage them manually is removed. You can affect the automatic distribution process by creating service cluster assignment rules or working server connection rules. The server cluster is functional until at least one working server marked as central server is running. The server cluster availability is defined by the <span class="interface">Fault tolerance level</span> parameter (the maximum number of working servers that can become unavailable without service interruption). <p>In the cluster console, the server cluster is displayed by its name (the <span class="interface">Cluster name</span> property), not by its port. </p><p>The software tools for administering server cluster version 8.3 are not compatible with the software tools for administering server cluster version 8.2.</p><p>The <span class="term">SessionFaultToleranceLevel</span> property is implemented for the <span class="term">IClusterInfo</span> object.</p><p>For the <span class="term">IWorkingServerInfo</span> object the following properties are implemented: <span class="term">MainServer</span>, <span class="term">ClusterMainPort</span>, <span class="term">DedicatedManagers</span>, <span class="term">InfoBasesPerWorkingProcessLimit</span>, <span class="term">ConnectionsPerWorkingProcessLimit</span>, and <span class="term">WorkingProcessMemoryLimit</span>.</p><p>The <span class="term">IAssignmentRule</span> object is implemented, it allows to manage the functionality of working servers.</p><p>The list of required functionality assignments is available via the <span class="term">IServerAgentConnection</span> object and the cluster console.</p><p>For the <span class="term">IServerAgentConnection</span> object the following methods are implemented: <span class="term">RegAssignmentRule</span><span class="term">()</span>, <span class="term">UnregAssignmentRule()</span>, <span class="term">GetAssignmentRules()</span>, <span class="term">CreateAssignmentRule()</span>, and <span class="term">ApplyAssignmentRules()</span>.</p><p>The properties of <span class="term">IWorkingProcessInfo</span>, <span class="term">IClusterManagerInfo</span>, and <span class="term">IClusterServiceInfo</span> objects are read-only.</p><p>For the <span class="term">IServerAgentConnection</span> object the following methods are removed: <span class="term">CreateWorkingProcessInfo()</span>, <span class="term">RegWorkingProcess()</span>, <span class="term">UnregWorkingProcess()</span>, <span class="term">StartWorkingProcess()</span>, <span class="term">StopWorkingProcess()</span>, <span class="term">SetWorkingProcessUsage()</span>, <span class="term">SetClusterMultiProcess()</span>, <span class="term">SetWorkingProcessCapacity()</span>, <span class="term">SetClusterDescription()</span>, <span class="term">CreateClusterManagerInfo()</span>, <span class="term">RegClusterManager()</span>, <span class="term">UnregClusterManager()</span>, <span class="term">RegClusterService()</span>, <span class="term">UnregClusterService()</span>, <span class="term">CreateStandbyClusterItem()</span>, <span class="term">RegStandbyCluster()</span>, <span class="term">UnregStandbyCluster()</span>, and <span class="term">GetStandbyClusterList()</span>.</p><p>The <span class="term">IStandbyClusterItem</span> object is deleted.</p><p>The <span class="term">SyncPort</span> property is deleted for the following objects: <span class="term">IWorkingProcessInfo</span>, <span class="term">IClusterManagerInfo</span>, <span class="term">IWorkingServerInfo</span>, and <span class="term">IClusterInfo</span>.</p></td><td>Management of cluster processes and function distribution between these processes could only be performed manually. The server cluster was displayed in the cluster console as a port number. The fault tolerance level could not be set.</td><td>Working processes are managed automatically, so that the load distribution in the server cluster is improved. At the same time, an administrator can specify working servers where certain cluster services or connections will be executed (using rules). For example, they can move the license management service to a separate working server with minimal configuration changes, or execute certain background jobs at the working server that is running Windows operating system.</td></tr><tr title="Версия 8.3.1" class="tag_6"><td><a name="b3f9eb72-baab-11e1-b815-e61f135f174b"></a><a href="#" onclick="onTagClick(this, 6); return false;">Server clusters</a>.<br></td><td>On Linux operating system, a server is not automatically started after it is installed. </td><td>On Linux operating system, servers were automatically started after they were installed.</td><td>A server is not started in the environment that is not fully configured. To configure the environment, you have to run the <span class="interface">config_system</span> utility first, and then you can start the server.</td></tr></table><p><a href="#e729b97b-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4cc794a6-7d56-11e1-b5d1-e61f135f174b">Renamed objects</a></h2><table cols="3"><thead><tr><th width="25%">Object</th><th width="37%">The old name</th><th width="37%">The new name</th></tr></thead><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05a5-7749-11e1-b5d1-e61f135f174b"></a>Column groups in the user settings table of the data composition system are renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">&lt;Table </span><span class="term">name</span><span class="term">&gt;ColumnGroup</span>;</li><li><span class="term">&lt;</span><span class="term">Table </span><span class="term">name</span><span class="term">&gt;</span><span class="term">ColumnGroup1</span>.</li></ul><p></p></td><td><ul><li><span class="term">&lt;</span><span class="term">Table </span><span class="term">name</span><span class="term">&gt;</span><span class="term">ColumnGroupSettings</span>;</li><li><span class="term">&lt;</span><span class="term">Table </span><span class="term">name</span><span class="term">&gt;</span><span class="term">ColumnGroupValues</span>.</li></ul><p></p></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05a7-7749-11e1-b5d1-e61f135f174b"></a>Column groups in the data parameters table of the data composition system are renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span><span class="term">1</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span><span class="term">2</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span><span class="term">3</span>.</li></ul></td><td><ul><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupParameterAndPeriodValue</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupParameter</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupPeriodValue</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupParameterValue</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05a8-7749-11e1-b5d1-e61f135f174b"></a>A column group in the available fields table of the data composition system is renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">&lt;Table </span><span class="term">name</span><span class="term">&gt;ColumnGroup</span>.</li></ul></td><td><ul><li><span class="term">&lt;Table </span><span class="term">name</span><span class="term">&gt;</span><span class="term">ColumnGroupAvailableField</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05a9-7749-11e1-b5d1-e61f135f174b"></a>Column groups in the group fields table of the data composition system are renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span><span class="term">1</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span><span class="term">2</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span><span class="term">3</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span><span class="term">4</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span><span class="term">5</span>.</li></ul></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupGroupField</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupFieldAndType</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupPeriod</span><span class="term">;</span></li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupField</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupBeginOfPeriod</span><span class="term">;</span></li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupEndOfPeriod</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05aa-7749-11e1-b5d1-e61f135f174b"></a>Column groups in the selected fields table of the data composition system are renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p><p> </p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">1</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">3</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">2</span>.</li></ul></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupSelectedField</span><span class="term">;</span></li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupHeaderAndPlacement</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupHeader</span>;</li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupField</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05ab-7749-11e1-b5d1-e61f135f174b"></a>Column groups in the filter table of the data composition system are renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p><p> </p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">2</span>;</li><li><span class="term">&lt;</span><span class="term">Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">3</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">4</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">1</span>.</li></ul></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupFilter</span><span class="term">;</span></li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupMainFilterItems</span><span class="term">;</span></li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupLeftValue</span><span class="term">;</span></li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupRightValue</span><span class="term">;</span></li><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupApplication</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05ad-7749-11e1-b5d1-e61f135f174b"></a>A column group in the order table of the data composition system is renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p><p> </p><p></p></td><td><ul><li><span class="term">&lt;Table </span><span class="term">name</span><span class="term">&gt;ColumnGroup</span><span class="term">.</span></li></ul></td><td><ul><li><span class="term">&lt;Table </span><span class="term">name</span><span class="term">&gt;</span><span class="term">ColumnGroupField.</span></li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05ae-7749-11e1-b5d1-e61f135f174b"></a>Column groups in the output parameters table of the data composition system are renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p><p> </p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">1</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">2</span>;</li><li><span class="term">&lt;Table name&gt;</span><span class="term">ColumnGroup</span><span class="term">3</span>.</li></ul></td><td><ul><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupParameterAndPeriodValue</span><span class="term">;</span></li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupParameter</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupParameterValue</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupParameter</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05af-7749-11e1-b5d1-e61f135f174b"></a>A column group in the user field case variants table of the data composition system is renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>.</li></ul></td><td><ul><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupValue</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05b0-7749-11e1-b5d1-e61f135f174b"></a>A column group in the appearance fields table of the data composition system is renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>.</li></ul></td><td><ul><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupField</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05b1-7749-11e1-b5d1-e61f135f174b"></a>A column group in the gauge chart quality bands table of the data composition system is renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>.</li></ul></td><td><ul><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupBackColor</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05b2-7749-11e1-b5d1-e61f135f174b"></a>Column groups in the filter conditions table of the data composition system are renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">&lt;Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup</span>;</li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroup1</span>.</li></ul></td><td><ul><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupValueAndPeriod</span><span class="term">;</span></li><li><span class="term">&lt;</span><span class="term">Table name</span><span class="term">&gt;</span><span class="term">ColumnGroupPeriod</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="compat tag_0 tag_1"><td><a name="ebcb05b3-7749-11e1-b5d1-e61f135f174b"></a>Column groups in the report variant form elements of the data composition system are renamed.<p>This change is not implemented in version 8.2.16 compatibility mode.</p></td><td><ul><li><span class="term">GoToReportSelectedFields</span><span class="term">1</span>;</li><li><span class="term">GoToReportFilter</span><span class="term">1</span>;</li><li><span class="term">GoToReportOrder</span><span class="term">1</span>;</li><li><span class="term">GoToReportConditionalAppearance</span><span class="term">1</span>;</li><li><span class="term">GoToReportOutputParameters</span><span class="term">1</span>.</li></ul></td><td><ul><li><span class="term">GoToReportSelectedFields</span><span class="term">FromInaccessibleSelectedFields</span>;</li><li><span class="term">GoToReportFilterFrom</span><span class="term">InaccessibleFilter</span><span class="term">;</span></li><li><span class="term">GoToReportOrderFrom</span><span class="term">InaccessibleOrder</span><span class="term">;</span></li><li><span class="term">GoToReportConditionalAppearanceFromInaccessibleConditionalAppearance</span><span class="term">;</span></li><li><span class="term">GoToReportOutputParametersFrom</span><span class="term">InaccessibleOutputParameters</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="tag_0"><td><a name="0cddc06b-77f5-11e1-b5d1-e61f135f174b"></a>Russian presentation for the <span class="term">ReportSettings</span> command of the report form is changed.</td><td><ul><li><span class="interface">Настройка</span><span class="interface"> ...</span>.</li></ul></td><td><ul><li><span class="interface">Настройки ...</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="tag_0"><td><a name="0cddc06c-77f5-11e1-b5d1-e61f135f174b"></a>English and Russian presentations for the <span class="term">LoadReportSettings</span><span class="term"> </span>command of the report form are changed.</td><td><ul><li><span class="interface">Select setting</span><span class="interface"> ...</span><span class="interface">.</span></li><li><span class="interface">Выбрать настройку ...</span></li></ul></td><td><ul><li><span class="interface">Select settings</span><span class="interface"> ...</span><span class="interface">.</span></li><li><span class="interface">Выбрать настройки ...</span></li></ul></td></tr><tr title="Версия 8.3.1" class="tag_0"><td><a name="0cddc06d-77f5-11e1-b5d1-e61f135f174b"></a>English and Russian presentations for the <span class="term">SaveReportSettings</span><b> </b>command of the report form are changed.</td><td><ul><li><span class="interface">Save setting </span><span class="interface">...</span></li><li><span class="interface">Сохранить настройку ...</span></li></ul></td><td><ul><li><span class="interface">Save settings </span><span class="interface">...</span></li><li><span class="interface">Сохранить настройки ...</span></li></ul></td></tr><tr title="Версия 8.3.1" class="tag_0"><td><a name="0cddc06e-77f5-11e1-b5d1-e61f135f174b"></a>Presentation of the <span class="term">StandardSettings</span> command in the report variant form is modified.</td><td><ul><li><span class="interface">Standard setting</span>.</li></ul></td><td><ul><li><span class="interface">Standard settings</span>.</li></ul></td></tr><tr title="Версия 8.3.1" class="tag_0"><td><a name="0cddc06f-77f5-11e1-b5d1-e61f135f174b"></a>Field containing name of saved settings in the <span class="interface">Save settings</span> dialog is changed.</td><td><ul><li><span class="interface">Name of saved setting</span>.</li></ul></td><td><ul><li><span class="interface">Name of saved settings</span><span class="interface">.</span></li></ul></td></tr></table><p><a href="#e729b97b-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><h2><a name="4cc794a7-7d56-11e1-b5d1-e61f135f174b">Upgrade from the previous version to version 8.3.1</a></h2><ul><li title="Версия 8.3.1" class="tag_0"><a name="4cc794a9-7d56-11e1-b5d1-e61f135f174b"></a>Conversion of configurations, infobases, external data processors, and external reports is not required during the upgrade from the previous version to version 8.3.1.</li><li title="Версия 8.3.1" class="tag_0"><a name="3ac57141-95f5-11e1-991e-e41f136d174a"></a>To use certain features of version 8.3.1 you have to disable the compatibility mode. The structure of certain objects is modified when disabling or enabling the compatibility mode. Note that to be able to work with infobases created using previous 1C:Enterprise versions you have to enable the compatibility mode. In order to use certain optimization improvements, you have to restructure data related to the optimization areas. To restructure data, you can use the <span class="interface">Verify and repair </span>mode, or perform forced object restructuring.</li><li title="Версия 8.3.1" class="tag_0"><a name="285a2e3c-a64b-11e1-991e-e41f136d174a"></a>It is recommended that you revise the list of infobases. Infobases that are present in the list when version 8.3 is installed in most cases have version 8.2 or 8.1 (because it is the default version, which is set automatically when an infobase is created or added to the list). Therefore, in order to open an infobase in 8.3, you have to specify the required version in the list of infobase startup settings, or specify the version directly in the infobase settings.</li><li title="Версия 8.3.1" class="tag_0"><a name="9962fe02-afa6-11e1-b815-e61f135f174b"></a>At the first start of server cluster version 8.3.1 on the computer hat has previous versions of ther server cluster installed, the content of the cluster register file(<span class="interface">1CV8Reg.lst</span>) is converted to a new format. The register of the server cluster 8.3.1 is stored in the file <span class="interface">1CV8Clst.lst,</span> in the same directory as the cluster register of the previous versions. There is no data synchronization between cluster registers of different versions after the first start of server cluster 8.3.1. <p>To perforrm the conversion of the cluster register from version 8.2. to version 8.3 once more, stop the server cluster 8.3, delete the server cluster 8.3 register (the <span class="interface">1CV8Clst.lst</span> file), and then start the server cluster 8.3.</p></li></ul><p><a href="#e729b97b-1831-11e2-b237-e61f135f174b"><small>Table of contents</small></a></p><script>
document.body.ondblclick = function(e)
{
e = e || window.event; var target = e.target || e.srcElement;
if (target.nodeName.toUpperCase() === 'A') return true;
var link = findClosestLink(target);
if (link) { prompt("Reference to", document.URL.split('#')[0] + '#' + link); }
}
function findClosestLink(target)
{
var parent = target;
while (parent) {
var anchor = getAnchorChildren(parent);
if (anchor) return anchor.name;
parent = parent.parentNode; }
return null;
}
function getAnchorChildren(parent)
{
var anchorsList = parent.getElementsByTagName('A');
if (anchorsList && anchorsList.length > 0) {
for (var i = 0; i < anchorsList.length; i++) {
if (!anchorsList[i].href) return anchorsList[i]; } }
return null;
}
document.oncopy = CopyRight;
function CopyRight(e) {
var element_body = document.getElementsByTagName('body')[0];
var link = findClosestLink(e.target);
var selection = window.getSelection();
var divnew = document.createElement('div');
divnew.style.position = 'absolute';
divnew.style.left = '-99999px';
element_body.appendChild(divnew);
for (var i = 0; i < selection.rangeCount; i++)
divnew.appendChild(selection.getRangeAt(i).cloneContents());
if (link) {
var sourceDiv = document.createElement('div');
sourceDiv.innerHTML = "<br/>Source: <a href='" + document.URL.split('#')[0] + '#' + link + "'>" + document.URL.split('#')[0] + '#' + link + "</a>";
divnew.appendChild(sourceDiv);
}
selection.selectAllChildren(divnew);
window.setTimeout(function () {
element_body.removeChild(divnew);
}, 0);
}
var curTag = 0;
function getElementsByClassName(className)
{
if(document.getElementsByClassName)
return document.getElementsByClassName(className);
else
{
var selector = '.' + className;
if(document.querySelectorAll)
return document.querySelectorAll(selector);
else
{
var stylesheet = document.styleSheets[0] || document.createStyleSheet();
stylesheet.addRule(selector, 'tm:p');
var nodes = [];
var length = document.all.length;
for(var i = 0; i < length; i++)
{
var node = document.all[i];
if(node.currentStyle.tm)
nodes.push(node);
}
stylesheet.removeRule(stylesheet.rules.length - 1);
return nodes;
}
}
}
function onTagClick(el, id)
{
if (curTag == id) {
id=0;
}
for (var i = 0; i <= 184; i++) {
var rows = getElementsByClassName('tag_' + i);
for (var j = 0, l = rows.length; j < l; j++)
if (id == 0)
rows[j].style.display = '';
else
rows[j].style.display = 'none';
}
if (id > 0) {
var rows = getElementsByClassName('tag_' + id);
for (var j = 0, l = rows.length; j < l; j++)
rows[j].style.display = '';
}
var tagsDiv = document.getElementById('tags');
var tags = tagsDiv.getElementsByTagName('A');
for (var i = 0, l = tags.length; i < l; i++)
tags[i].className = '';
document.getElementById('action_' + id).className = 'tagSelected';
document.getElementById('func_list').setAttribute('open', 'open');
el.scrollIntoView(true);
curTag = id;
return false;
}</script></body></html>