--- title: "Tag a Policy Status field from a routing policy" slug: "tag-a-policy-status-field-from-a-routing-policy" description: "Set fields on a record's related Policy Status record from a routing policy's record-tagging stage, so you can report on routing outcomes in Salesforce. Require" tags: ["Routing Policies", "Policy Status", "record tagging", "routing reporting"] status: "update" updated: 2026-10-29T17:06:45Z published: 2026-10-29T17:06:45Z canonical: "support.fullcast.com/tag-a-policy-status-field-from-a-routing-policy" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fullcast.com/llms.txt > Use this file to discover all available pages before exploring further. # Tag a Policy Status field from a routing policy When a routing rule assigns a record, it can also "tag" that record by writing a value to one of its fields. As of Managed Package 2.208, a routing rule can tag fields on the record's related **Policy Status** record too, not just the routed record (like the Account or Lead). This gives you a dedicated place to capture routing details, so you can report on how records were distributed without adding new fields to your core objects. > [!NOTE] > Note > > The Policy Status record is Fullcast's log of how a policy ran against a record. If you're new to it, read [Understand the Policy Status page in Salesforce](/v1/docs/understand-the-policy-status-page-in-salesforce) first. ## Before you begin - Available for **Salesforce package version 2.208 or later**. Existing record tagging keeps working exactly as before on earlier versions, so nothing breaks if you haven't upgraded yet. - Ensure that **Overwrite policy status is turned off** (`false`). When overwrite is on, Fullcast replaces the Policy Status record on each run, so there isn't a stable record to tag. Turning it off keeps a Policy Status record per routing event. See how this setting behaves in [Understand the Policy Status page in Salesforce](/v1/docs/understand-the-policy-status-page-in-salesforce). ## How it works Record tagging lives in the [**Default users & record tagging**](/plan-and-pay/docs/routing-policy-stages#routing-policy-stages) stage of a routing policy. You pick a field, pick a value, and when the rule runs, Fullcast writes that value to the field. Before 2.208, the **Field** dropdown only listed fields on the routed record. Now it also lists editable fields from the related Policy Status record. Every option is labeled with its object name, so it's always clear which record gets updated: - `Account.Industry` writes to the routed Account. - `Policy Status.Status` writes to the related Policy Status record. When the rule runs, Fullcast updates the field on whichever record the option points to. ## Tag a Policy Status field 1. Open the routing policy you want to edit and go to **Default users & record tagging**. 2. In the **Field** dropdown, choose the field you want to set. Each field is labeled with its object name, so look for the `Policy Status.` prefix to tag the Policy Status record. 3. In the **Value** selector, choose the value to write. 4. Save the policy. When the rule runs, Fullcast writes your chosen value to that field on the matching Policy Status record. Tags on the routed record work the same as before, so one rule can tag both records at once. **Example:** A rule sends inbound EMEA leads to the EMEA SDR team. You add a tag that sets the Policy Status field **Routing Path** to `EMEA SDR Round Robin`. RevOps can now build a Salesforce report of every lead that rule handled, without adding a new field to the Lead. ## How to use it - **Report on routing outcomes.** Stamp which rule or path handled a record on its Policy Status record, then report on distribution in Salesforce. - **Keep your core records clean.** Store routing-only details on Policy Status instead of adding more fields to the Account or Lead. - **Do both at once.** A single rule can tag the routed record and its Policy Status record together. ## Limitations - **Policy Status is the only related record you can tag.** Other related objects aren't supported. - **Only editable fields appear in the dropdown.** Formula and auto-number fields aren't listed. - **Fullcast supports tagging Text and Lookup fields.** Other field types may appear in the dropdown but aren't officially supported.