Passing parameters to PaCE policies

  • Release version: Australia
  • Updated March 12, 2026
  • 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 Passing parameters to PaCE policies

    This content outlines how parameters can be passed to PaCE policies in ServiceNow for validating updates to objects, including tables and document IDs. It details the types of parameters available for use during policy authoring in both low-code and JavaScript environments.

    Show full answer Show less

    Key Features

    • API Variables: Previously known as Caller Inputs, these are passed to the PaCE API during invocation. Only one immutable API Variable, SnapshotId, is predefined for each policy. If not specified during API calls, the policy will not execute.
    • Config Parameters: Known as Mapped Inputs, these are used when mapping policies to specific objects. Mandatory inputs must be specified to execute the policy; otherwise, it remains inactive. They allow customization of limits for different scenarios, such as expense limits for various employee groups.
    • Record References: These define queries to extract data from ServiceNow tables, facilitating the configuration of policy logic based on the retrieved data. Aggregate functions can also be performed on these queries.
    • Data Collectors: This function collects input process data from ServiceNow or external sources for policy logic decisions. Data collectors can be managed through the policy builder and accessed in JavaScript using the dataCollectors object.

    Key Outcomes

    By utilizing these parameter types, ServiceNow customers can enhance their PaCE policies to validate data effectively, enforce limits based on specific criteria, and make informed decisions through the integration of external data sources. This flexibility allows for tailored policy execution aligned with organizational needs.

    Parameters can be passed to a PaCE policy to validate updates to an object (tables and document IDs). These variables apply to authoring in both low-code or JavaScript. Policy versions include three types of parameter inputs: API Variables, Config Parameters, and Record References.

    API Variables

    Previously known as Caller Inputs, the API Variables is passed to the PaCE API at the time of invocation by a developer. The API Variable is a variable that enables you to pass the value to the policy whenever the policy is invoked. Specify a value for this API Variable when calling the API, otherwise the policy is not executed and no decision is reached. In the code editor, the variable name is apiVars.

    For each PaCE policy, there is only one pre-defined API Variable called SnapshotId. This API Variable is Immutable and cannot be modified or deleted. You cannot define any additional API Variables for a policy.

    Config Parameters

    Previously known as Mapped Inputs, the Config Parameters can be passed when mapping policies to an object (tables and document IDs). When you define a Config Parameter, you are creating a parameter that enables you to pass values to the policy whenever the policy is mapped. If you define mandatory inputs, you must specify values for these inputs when mapping the policy. If the inputs you define are not mandatory, the policy is not executed (the status is set to inactive) and no decision is reached. In the code editor, the variable name is configParams.

    For example, for a travel expenses policy you can add variables to define the limits of different types of expenses. The limits are specified when mapping the policy, and set the limits on the expense when the policy is invoked on this object. The breakfast expense limit for one group of employees could be $25, and for a different group of employees the limit could be $50. Each time the policy is invoked, the expenses are validated by the policy according to the limits specified in the mapping.

    Record References

    Record references define queries to extract data from any ServiceNow® tables and use the data to configure the policy logic. This feature enables you to retrieve additional data that may be required while defining the policy. You can define a query to perform aggregate functions for a record reference. In the code editor, the variable name is recordRefs.

    Data Collectors

    The data collectors function collects input process data from ServiceNow or an external data source to provide an output. The output can be used in the policy logic to make a decision. You can define and manage data collectors by creating, editing, updating, and activating them to your policy builder.

    Data collectors can be accessed by using the dataCollectors object in JavaScript.
    Note:
    Auto-completion lists all possible outputs and data collectors that are available to use.

    While editing a policy in low-code, an output of the configured data collectors is available under the drop-down menu.