Skip to content

BSL229 — Ordinary application support

← All rules

Summary

Ordinary application support

Identifiers

Field Value
Rule code BSL229
Compatible alias OrdinaryAppSupport
Severity WARNING
Enabled by default Yes
Implemented Yes
Tags compatibility, ui

Behavior

  • The public identifier BSL229 and alias OrdinaryAppSupport are stable.
  • The rule reports the cases documented on this page.
  • Suppressions and project configuration are applied before publication.
  • The rule requires neither an external analyzer nor network access.

Configuration and suppression

BSL### is the primary stable identifier. The compatible alias is accepted in select, ignore, and compatible block suppression comments.

[tool.onec-hbk-bsl]
select = ["BSL229"]
ignore = ["OrdinaryAppSupport"]

All three suppression families support both a current line and a range. When an opening comment follows code, it affects only that line. Use any one form:

  • noqa:
Value = "example";  // noqa: BSL229
  • bsl-disable:
Value = "example";  // bsl-disable: BSL229
  • compatible BSLLS form:
Value = "example";  // BSLLS:OrdinaryAppSupport-off

When the same opening comment is on a line by itself, it starts a range. Close it with the matching marker from the same family:

// noqa: BSL229
// code without this diagnostic
// noqa-enable: BSL229

// bsl-disable: BSL229
// code without this diagnostic
// bsl-enable: BSL229

// BSLLS:OrdinaryAppSupport-off
// code without this diagnostic
// BSLLS:OrdinaryAppSupport-on

To disable the rule until the end of the file, omit the closing noqa-enable, bsl-enable, or BSLLS:…-on marker.

Opening and closing markers must belong to the same family.

Description

To maintain backward compatibility with various proprietary and third-party solutions, external data processes and reports developed on previous versions of the 1C: Enterprise platform 8.0 and 8.1, the configuration should also support launching in ordinary application (thick client) and external connection modes for administrators (users with full rights).

For this it is recommended:

  • The configuration property "Use managed forms in a ordinary application" is set to True.
  • Set the property "Use ordinary forms in managed mode" to False.
  • Adhere to the general scheme for setting the attributes of common modules, and conduct the development itself in the Designer in edit mode for both launch modes - managed and ordinary applications (Service menu - Options - General tab).

When developing in EDT, properties are set through the Designer.

The refusal to support the launch of configuration in the ordinary application and external connection modes for administrators is possible only in certain justified cases.

Examples

Sources