Architectural artifacts

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 1 Minute Lesedauer

    • Architectural artifacts are created to describe a system, solution, or state of an enterprise. The goal of architectural artifacts in Enterprise Architecture is to enable Enterprise Architects to create and manage artifacts in their organization.

    Wichtig:

    Starting with the Xanadu release, the legacy architectural artifact module has been deprecated from Enterprise Architecture (formerly Application Portfolio Management). However, if you’re an existing user of Enterprise Architecture (formerly Application Portfolio Management), you can still use the legacy architectural artifact module. If you’re a new activation user, the legacy architectural artifact module isn’t available.

    You can leverage the same features by using the Enterprise Architecture Workspace. To learn more, see Exploring architectural artifacts.

    Sometimes you may rely on external sources to keep and maintain many of your enterprise architecture elements such as diagrams, reports, and other visualizations. However, it is hard to associate these artifacts to the ServiceNow objects such as business applications or business capabilities.
    Hinweis:
    You need the sn_apm.apm_user role to view or create architectural artifacts.
    As an Enterprise Architect, use the Architectural Artifacts module to perform the following tasks:
    • Review and approve architectural artifacts.
    • Keep track of artifacts versions.
    • Relate architectural artifacts to categories that are configured to match the needs of the organization.
    • Associate your architectural artifacts to your organization's business capabilities and business applications.

    The Architectural Artifacts feature extends the functionality of the ServiceNow® Document Management plugin (com.snc.platform_document_management) and can create a relationship with ServiceNow® objects: Business Applications and Business Capabilities.