Document report and appearance inspection
This commit is contained in:
@@ -83,6 +83,28 @@ overlay, it then removes only receipt-recorded rows after hash precondition
|
||||
checks. A successful result proves SQL readback and cleanup only; it does not
|
||||
prove Configurator visibility, acceptance, or activation.
|
||||
|
||||
## Report And Appearance Inspection
|
||||
|
||||
`report.inspect` is the read-only entry point for a report component graph.
|
||||
It accepts a public report name and returns only independently confirmed
|
||||
modules, forms, templates and SCD components. A form called
|
||||
`ОсновнаяСхемаКомпоновкиДанных` remains a form; it is never promoted to an SCD
|
||||
from its name or a guessed `.0` stream.
|
||||
|
||||
```json
|
||||
{"method":"report.inspect","payload":{"base_id":"upo_test","report":"ФинансовыйРезультат"}}
|
||||
```
|
||||
|
||||
`appearance.inspect` is a separate read-only reader for a base
|
||||
`CommonTemplate` whose `.0` carrier is confirmed as `AppearanceTemplate` XML.
|
||||
It returns raw XML-backed `item(parameter, value)` rules and an XML tag
|
||||
outline. It has no write operation, and an extension template returns explicit
|
||||
`unsupported` until an extension carrier route is proven.
|
||||
|
||||
```json
|
||||
{"method":"appearance.inspect","payload":{"base_id":"upo_test","template":"ОформлениеОтчетовБежевый"}}
|
||||
```
|
||||
|
||||
## User Identity And Access Terminology
|
||||
|
||||
An unqualified user request means an **infobase user**: the platform identity
|
||||
|
||||
Reference in New Issue
Block a user