Invoke PaCE activity
Enable the Policy as Code Engine (PaCE) activity in Playbooks to develop playbook processes.
Roles and availability
These activities are available as part of the application that is automatically bundled with PaCE. Users with the admin, pd_admin, pd_author, or pd_content_author can add these activities to a playbook.
Inputs
Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see Dot-walking examples.
| Name | Type | Description |
|---|---|---|
| Label | String | Title to display as activity and playbook card. |
| Description | String | Information to display about activity usage or outcome. |
| Run condition | Condition Builder | Conditions that must be met to run an activity. You can use data from prior activities to build conditions. |
| When to start | Choice | Select a start rule for when your activity should start running:
|
| Start with delay | True/False | Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the Start with delay input properties. |
| Service | String | The calling service that is invoking the PaCE API. |
| Category | String | The category type. |
| Policy tag | String | Tag name of the policy. |
| Document Ids | Array.Object | Name of document IDs. |
| Data | JSON | The policy-specific data that includes all possible caller inputs. |
| Options | Object | Options of the policy. |
Outputs
The outputs are configurable in Flow Designer and are set by the Automation plan.
| Label | Type |
|---|---|
| Root execution id | Sys ID (GUID) |
| Don't Treat as Error | True/False |
| Response | JSON |
| Action Status | String |