Skip to content

Drawing production MVP requirements #8534

@pmconne

Description

@pmconne

Is your feature request related to a problem? Please describe.

@Josh-Schifter's drawing production team has minimum requirements for their initial release.

Describe the solution you'd like

They need to create a field in a sheet template and see that field be updated when the template is copied from a catalog iModel to create a new BisCore.Sheet in the design iModel.

Tasks

  • Implement ITextAnnotation.onCloned
    • Remap element Ids in JSON when copying a field from one iModel to another
    • Copy or create ElementDrivesTextAnnotation relationships between iModels
    • Copy default text style or remap based on name
  • Make element cloning async #8615 and cloning a text style imports font
  • Enhance display-test-app for testing and API validation
    • Key-ins
      • Save TextDecoration's current annotation as a TextAnnotation2d element, possibly replacing the annotation on an existing element.
      • Populate TextDecoration's current annotation from an existing element.
      • Add a FieldRun to TextDecoration
    • Add an environment variable to specify allowed channels for editing
  • Support all of the property types in Title Block properties #8490
    • Formatting
      • DateTime
      • String
      • Scale not for MVP
    • Field definition+evaluation
      • Element properties
      • ECView properties
      • Project properties
      • SheetReference properties (placeholder fields?)
  • Font cache invalidation
  • Validate complete workflow for copying a sheet template from catalog iModel to design iModel
    • Transformer does not support ElementDrivesElement relationships?
      • In general, we would need to remap these relationship after all elements are imported. For the purposes of fields required for MVP, that probably won't be necessary.
    • When are SheetReferences created (fields in title block may point to their properties)
  • Detect when a drawing may need to be regenerated
  • Blanking fill draws behind other elements #8101

Josh suggested testing with sheet number (CodeValue for SheetReference) to start since that one's already implemented, but see question above about when sheet references actually get created in the workflow.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions