PaCE policy version states

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of PaCE Policy Version States

    PaCE policy versions in ServiceNow can exist in four states—Draft, Current, Archived, and Ready—each defining how a policy version is managed, used, and numbered. Understanding these states helps you effectively manage policy lifecycle, versioning, and deployment within your environment.

    Show full answer Show less

    Policy Version States

    • Draft: Initial state when creating a new policy version. Drafts can be saved for future editing but cannot be executed until published.
    • Current: The active published version used for policy execution. Only one Current version can exist per policy. Publishing a draft to Current triggers verification of mapping inputs to ensure proper execution.
    • Archived: Previous Current versions become Archived when a new version is published. Archived versions retain their version number and can be republished if needed.
    • Ready: States assigned to optional policies included in application content packs. These are read-only; to modify, you must create a copy.

    Policy Version Numbering

    Each version has three identifiers:

    • Version Name: For Drafts, named as Draft-V{Revision number} (e.g., Draft-V0.1). For Current or Archived, named as V{Version} (e.g., V1.0).
    • Version Number: Assigned only upon publishing. Starts at 1.0 for the first Current version and increments by 1.0 for each new Current version (e.g., 2.0, 3.0). Drafts do not have a version number.
    • Revision Number: Tracks incremental changes within a version. New empty drafts start at 0.1 and increment by 0.1 for each draft (0.2, 0.3, etc.). Drafts created from a published version inherit that version number with an added decimal (e.g., 2.1 from version 2.0).

    Practical Implications for ServiceNow Customers

    • Manage policy lifecycle by progressing versions from Draft to Current, ensuring only one active version is in use.
    • Verify mapping inputs when publishing to avoid execution errors.
    • Leverage Archived versions to maintain history or revert if necessary.
    • Use Ready policies as templates and create copies for customization.
    • Understand version and revision numbering to track changes and deployment status clearly.

    A PaCE policy version can be in one of four states: Draft, Current, Archived, and Now-Content. The policy version state also defines the version numbering.

    Only one policy version in each policy can be Current at any one time. There is no limit to the number of Draft or Archived policy versions.

    Table 1. Policy version states
    State Description
    Draft When a version is created, its initial state is Draft. The new Draft version can be saved as a Draft for later use, or published to become the Current version. The draft versions cannot be used until they are published.
    Current Draft versions can be published to Current, which means the former draft version becomes the default published version used for policy execution.
    Note:
    When publishing the version, if mapping exists, verification is performed to confirm that all required inputs for mapping inputs were provided. If you update the mapping inputs, you must update the inputs in the Mapping screen. If you updated caller inputs, you must update the PaCE API call to ensure that the policy is executed.
    Archived A published Current version becomes Archived when a different version is published. Only Current versions can be Archived. If necessary, you can also republish an Archived version.
    Note:
    When a version is published, it becomes the Current version irrespective of its previous states.
    Ready The Ready state is assigned to optional policies available when an application content pack is installed. These policies cannot be modified. If you want to modify a policy, create a copy and make the required changes.

    Policy version numbering

    There are three identifiers for each version: Version name, Version, and Revision number. These identifiers are shown as three separate columns in the Versions tab.
    Identifier Description
    Version name

    For Draft versions, the version name uses Draft-V{Revision number}.

    For Current (published) or Archived versions, V{Version} is used for the name.
    Version The Version number is assigned only when you publish a version. The number is automatically created according to the existing version number. For the first Current (published) version, the number is 1.0 and for subsequent current versions, the number increases by +1.0. For example, 2.0, 3.0, 4.0, and so on.

    Current versions that have been Archived retain the original version number.

    Draft versions are not assigned a version number.
    Revision number The Revision number is derived from the version that it was created from. If an empty new policy is created, the initial draft version is assigned 0.1. Each subsequent draft version is assigned 0.2, 0.3, 0.4, and so on.

    If the version was created from a published (Current or Archived) version, it inherits the Version number. For example, you can create a draft version from the Current (published) version 2.0. The draft version is assigned the revision number 2.1.

    The following image illustrates the different states and their version numbering.

    Policy version numbering.

    As shown in the preceding image, the first draft policy version created was automatically assigned the Revision number 0.1. Each subsequent draft is assigned V0.2, V0.3, and so on. Draft version 0.2 (as indicated in the Revision number column) was published and became the Current version, with the Version name of V1.0.

    A draft version of this Current version was created, with the Revision number 1.1. That draft was published to become the Current version and was assigned the Revision number 1.1. The previously Current version is now Archived, but retains the Revision number 0.2.