Import/Export Schema Assets
Archy supports Excel bulk import and import to generate and update enterprise-class schema assets, and can synchronize with external business modeling tools, data asset catalogs, and reuse existing schema assets. This page explains the usage scenarios for template import rules and external integrations. For creating and editing single objects, see Manage Schema Assets.
Import Business Objects
- Click More Actions → Download Template in the Business Object Model area to download the import template locally.
- Fill in the coding, name, directory, definition, and responsibility information of the business object by template.
- Click [Import Business Objects] to upload the completed Excel.
- The system is updated according to the business object encoding: the existing object of the encoding is updated, and the newly encoded object is added.
- After the import is complete, check the new quantity, hierarchical path, and Chinese display results.
The application system is imported in the same way as the business object, see Manage application domains and application systems.
| Inspection | Description |
|---|---|
| Encoding Uniqueness | Updating by encoding means duplicate encodings will overwrite each other and must be checked before importing |
| Template Version | Older templates may be missing new columns with the current version of the downloaded template |
| Hierarchy Path | Directory and parent objects must already exist, otherwise the hierarchy is misplaced |
| Change baseline | Export stock assets before import as a basis for backtracking |
It is recommended to import a small amount of data in the test catalog first, and then import the formal scope after confirming that it is correct; after importing, run repeated checks and supplement the necessary approvals, see Management Architecture Asset Lifecycle.
Export Business Objects
Click [→Export Business Objects with More Actions] to export all business objects in the directory to local. The export file can be used for change review, object inventory before external tool mapping, and baseline retention before deletion or scrapping.
Illustration of the integration of Archy with external tools: Architectural assets can flow in both directions to business modeling tools and data asset catalogs, and import and export are data preparation means before synchronization.
Sync with business modeling tools
Archy can integrate with domestic and foreign business modeling tools (such as Aris, digital twins) for two-way synchronization, and integrate the modeling results of the information planning stage into the architecture management and control process.
| Integration Objects | Orientation | Typical Scenarios |
|---|---|---|
| Business modeling tools such as Aris | Two-way synchronization | When there is an enterprise-level process and data model, it is imported into Archy under control, and the architecture change is written back to the modeling tool |
| Twin Modeling Tools | Two-way Synchronization | Aligning Project-Level Modeling Outcomes with Enterprise-Level Architecture Assets |
| Data Asset Catalog | One-way or per-configuration synchronization | Post-release funding asset catalog display and retrieval of schema assets |
Before synchronization, the main data source, field mapping, conflict handling and synchronization direction of the object should be clearly defined. Do not use two systems as the maintenance master of the same object at the same time.
Post-sync check
After each bulk sync or import:
- Randomly check that the object hierarchy, encoding, status, and relationships are as expected.
- Verify in the Data Distribution View that there are no empty or abnormal relationships due to the added objects.
- Keep synchronization logs and export files for issue tracking and backtracking.
When hierarchical confusion or encoding conflicts are found, export the current results to locate the source of the difference, and then decide whether to correct the template re-import or fall back to the pre-synchronization baseline.