Coflyr · Backend model field catalog

WorkTemplate

Maintenance.WorkTemplates.

23 mapped fields6 field groupsGenerated 2026-10-06
Model class
coflyr.features.engineering.workrepositories.models.WorkTemplate
Source
Features/Engineering/WorkRepositories/Models/WorkTemplate.cs
Table
Maintenance.WorkTemplates
Review
Dropped · HTML proposal; backend/DB pending

Every mapped scalar field appears once. Types and nullability come from the current EF model snapshot. Navigation properties and unmapped DTO fields are outside this page. Purpose text is inferred from names and should be checked against the feature workflow.

← All model classes · AMOS Workpackage example

NextRevisionNumber and ProjectNumber are marked Dropped in the review. Both fields remain visible here; backend/database adoption is pending.

Dropped as a separate header: all fields are merged into the single WorkTemplateMaster. EngineeringOrder joins it as a template type; add Task, Modification and Troubleshooting. All original field rows remain visible for review. NextRevisionNumber and ProjectNumber remain Dropped. Backend/database adoption pending.

Identity and naming

5 fields
#FieldEF typeStorageBusiness purposeReview
1IdGuidRequiredStable identifier for this record.Reviewed
2NextRevisionNumberintRequiredRecords next revision number for this work template.Dropped
Removal pending complete review
3ProjectNumberstringNullableRecords project number for this work template.Dropped
Removal pending complete review
4TemplateNumberstringRequiredRecords template number for this work template.Reviewed
5TitlestringRequiredRecords title for this work template.Reviewed

Relationships and references

4 fields
#FieldEF typeStorageBusiness purposeReview
1AtaIdGuid?NullableSelects the related ata record.Reviewed
2CustomerBusinessPartnerIdGuid?NullableSelects the related customer business partner record.Reviewed
3PartIdGuid?NullableSelects the related part record.Reviewed
4ShopFacilityIdGuid?NullableDrop ShopFacilityId from the common WorkTemplateMaster proposal as requested. Backend/database adoption remains deferred until complete project review.Dropped
Removal pending complete review

Status and controls

4 fields
#FieldEF typeStorageBusiness purposeReview
1AppliesToRotablesOnlyboolRequiredIndicates whether applies to rotables only applies to this work template.Dropped
Removal pending complete review
2IncludeAlternatePartsboolRequiredIndicates whether the component-maintenance template is intended to apply to alternate parts. Example: apply the template to pump P100 and its approved alternate P101. Current test-assignment returns the flag; automatic alternate-part expansion and applicability validation are not implemented by that endpoint. Reviewed in the HTML proposal; backend/database adoption pending complete review.Reviewed
3IsActiveboolRequiredIndicates whether active applies to this work template.Dropped
Removal pending complete review
4RequiredConditionCodestringNullableRecords required condition code for this work template.Reviewed

Descriptions and details

3 fields
#FieldEF typeStorageBusiness purposeReview
1OrderReasonCodestringNullableReplace OrderReasonCode text with reviewed OrderReason (MaintenanceOrderReason?) enum. Explicitly map legacy reason codes and preserve unmapped/historical values during deferred backend/database adoption.Dropped
Removal pending complete review
2TemplateDescriptionstringNullableRecords template description for this work template.Reviewed
3TemplateTextstringNullableRecords template text for this work template.Reviewed

Audit and revision

3 fields
#FieldEF typeStorageBusiness purposeReview
1ActiveRevisionIdGuid?NullableSelects the related active revision record.Dropped
Removal pending complete review
2SystemAuditIdGuid?NullableLinks to system audit history when this model stores the reference.—
3UpdateIdGuid?NullableLinks to the preceding revision or update record.Reviewed

Other fields

4 fields
#FieldEF typeStorageBusiness purposeReview
1PositionCodestringNullableDrop PositionCode text and replace it with LocationReferenceId (LocationReference lookup), ConfigurationMasterId (ConfigurationMaster lookup) and ConfigurationId (Configuration lookup), all nullable UUIDs. Resolve legacy codes explicitly in the correct context and preserve unresolved/historical values during deferred adoption.Dropped
Removal pending complete review
2PriorityCodestringNullableReviewed nullable maintenance planning priority. Replace free-text PriorityCode with the existing ComponentWorkpackagePriority enum already used by WorkorderMaster: VeryUrgent = 1, Urgent = 2, Normal = 3, NotUrgent = 4, NiceToHave = 5. Reuse these project values rather than introduce a second priority enum. Null means priority not specified; do not silently default to Normal. These are project enum values; AMOS uses a configurable priority table and may contain other legacy codes, including M (Mandatory). Explicitly map legacy codes and preserve unmapped text and historical priorities for review. Priority does not replace a governing compliance requirement or mandatory-compliance classification. Enum conversion and backend/database adoption pending complete review.Reviewed
3RequirementTypeCodestringNullableDrop RequirementTypeCode from the WorkTemplateMaster proposal. Use the linked Requirements record through RequirementId and its RequirementTypeDefinitionId lookup to display the governing requirement type. Reconcile legacy free-text codes with authoritative requirement-type definitions during later adoption. Backend/database changes remain deferred until complete project review.Dropped
Removal pending complete review
4TemplateTypeintRequiredRecords template type for this work template.Reviewed