How does the Standard builder operate from custom queries?

For a Standard builder diagram template that works from custom queries, a query is expected to be configured for each schematic feature class associated with it. Another query can also be specified on the diagram template itself to provide the list of the diagrams the Standard builder is supposed to build. In that case, the queries specified on the schematic feature classes are generally configured to allow filtering data related to each diagram. When the builder is expected to build only a schematic diagram, no query needs to be specified on the diagram template.

All those configured queries can operate from any type of database. They are automatically executed at diagram generation to retrieve the set of records in the database tables from which the builder must implement the schematic features expected in the generated diagram.

When generating a Standard builder diagram entirely based on custom queries, the builder populates the schematic feature classes—that is, it creates the schematic features expected in the diagram as follows:

1. For each schematic feature class associated with the diagram template for which the custom queries are configured to be launched at diagram building—that is, queries with the Query on Generate/Update evaluation mode—it executes the custom query.

   For each record returned by the query, it creates a schematic feature in memory, evaluates its attributes, and initializes its topology and geometry.

2. If schematic rules are specified for the related diagram template, they are executed on all the schematic features built in memory.
3. If there are schematic feature classes associated with the diagram template for which the custom queries are configured to be launched at diagram loading—that is, queries with the Query on Start Editing evaluation mode—it executes the custom query configured on each schematic feature class.

   For each record returned by the query, it creates a schematic feature in memory, evaluates its attributes, and initializes its topology and geometry.

4. If there is a default schematic layout algorithm configured for the diagram template, the algorithm is executed and the geometry for all the in-memory schematic features is updated accordingly.
5. All the schematic features in memory since the generation process started are saved in the schematic feature classes in the schematic dataset.
6. All the created schematic features are queried from the schematic feature classes, and the diagram is displayed.

Then, at any time and for its lifetime—that is, until it is deleted from the schematic dataset—the diagram can be

• Reopened
• Edited, laid out, and saved
• Updated so its content continues to correspond with the database from which the diagram has been built—that is, updated so each change that may have impacted the records in that database is reported on the associated schematic features