ores.reporting.configuration

Table of Contents

The name is ours; the detail lives with the component named by owning_component. A report binds a configuration through report_configuration, so several reports share one configuration without copying it, and the kind of configuration it is comes from configuration_type by foreign key rather than from a text code.

1. Flags

2. Columns

2.1. id

Surrogate key for the configuration.

2.2. party_id

The party that owns the document this row belongs to. Set from the session that writes the document, and enforced by row level security, so a party sees only its own configuration. 

ctx.generate_uuid()

2.3. name

The name of the configuration. It is ours, not ORE's, and it is what a report refers to.

2.4. configuration_type_code

The kind of configuration this is.

2.5. owning_component

The component that owns the detail of this configuration, for example analytics or refdata. Reporting references it rather than copying it.

3. SQL

3.1. Flags

4. Foreign keys

4.1. configuration_type_code

5. Insert trigger

5.1. Validations

column validation_function

6. C++

6.1. Flags

6.2. Repository

6.3. Domain includes

#include <string>

6.4. Entity includes

#include <string>

6.5. Conventions

6.6. Table display

column header
name Name
configuration_type_code Kind
owning_component Owner
modified_by Modified By
version Version

6.7. Presentation

6.7.1. Detail fields

field label type is_key is_required placeholder
name Name line_edit true true Enter name
configuration_type_code Kind line_edit   true Enter configuration type code
owning_component Owner line_edit   true Enter owning component

6.7.2. Columns

enum_name field header type width
Name name Name string 220
ConfigurationType configuration_type_code Kind string 180
OwningComponent owning_component Owner string 140
Version version Version int 80
ModifiedBy modified_by Modified By string 120

6.8. Custom repository methods

7. See also

Emacs 29.3 (Org mode 9.6.15)