Breadcrumbs

Off-Guideline Deal Agent (Configuration)

The Off-Guideline Deal Agent identifies quotes that fall outside approved pricing guidelines and tracks their outcomes (e.g., revenue, status, margins). It provides visibility into violations of floor, target, or stretch price rules to support guideline compliance analysis.

Create Agent

  1. Go to Pricefx Agents > Agents.

  2. Click Create New Agent.

  3. In the Create New Agent menu:

    1. Enter the Agent Name.

    2. Enter a Label for the Agent (optional).

    3. In the Type field, select Flex Agent.

  4. Click Create.

Definition

Agent Type

In the Select your agent field, select Off-Guideline Deal Agent.

Scope Definition

This section defines which quotes are included in the analysis.

Quote Type – The user must first select the Quote Type. This selection determines the available configuration options.
Quote status to include – A multi-select dropdown used to filter quotes by status. Possible options include:

  • DRAFT

  • OFFER

  • DEAL

  • REVOKED

  • SUPERSEDED

  • INVALIDATED

  • LOST

  • PARTIALDEAL

Review Period – Defines the time window for evaluating quotes. Options include:

  • Last 24 Months

  • Last 12 Months

  • Last 6 Months

  • Last 3 Months

  • Custom static range

Select Customers to monitor – An optional filter to restrict the analysis to specific Customer Groups.
Currency – The currency in which values are displayed for this agent. When the Source is a Data Source (DS), the default is USD. When the Source is a Datamart (DM), the default is the Datamart's base currency. Changing this setting does not convert existing values.
Additional Filters – An InputMatrix that allows filters on Quote header-level inputs or outputs (e.g., Country == 'USA').
Available fields depend on the selected Quote Type.

Field Mapping

This step determines which Quote line-item fields the Agent will use in its analysis.

Quantity – Map to the line item's quantity field.
Invoice Price – Map to the line item's final selling price field.
Boundary Price – Map to the floor or boundary price to be compared against the Invoice Price.

Grouping

Controls how results are aggregated (Optional).

Group By (Customer fields) – Select one or more fields from the Customer Datamart (e.g., customerCategory, region).
Group By (Product fields) – Select one or more fields from the Product Datamart (e.g., productFamily, brand).

If no grouping is defined, the Agent groups results by the parent Quote.

Threshold

This section defines when a group is flagged as problematic.

Threshold – The user may choose either:

  • % of cases – Flags the group if the percentage of line items below the boundary exceeds a threshold (e.g., >10%).

  • % of revenue – Flags the group if revenue from off-guideline items exceeds a defined percentage of total group revenue.

Performance & Technical

Percentage amount – The proportion of line items within the group where the Invoice Price is below the Boundary Price, shown as a percentage.
Limit amount of quotes for preview – Standard performance setting for the live preview.
Customer field mapping – Allows configuration of the Customer ID source on the quote header if it is not stored in the standard customerId field.

Schedule

Configure the preferred start date and frequency for Agent execution.

Start Date – The first execution date.
Period – Defines the period type.

  • Day

  • Month

  • Year

Interval – The number of repetitions within the selected period. Valid characters: 0–9. An interval of 0 indicates a one-time execution.

Action Definition

This step defines actions which will be created by the Agent once the alert conditions are met so that the specified user can address the detected problem or opportunity. The Agent creates Actions on the row level in the Detected Insights (i.e., if there are 5 rows in the identified data, 5 actions will be created).

The Pricefx Agents 1.4 release introduces changes to the way Actions are created from Detected Items in Datamart Tables. Actions can now be grouped and limited to the most impactful items, while unused Detected Items are automatically cleaned up.

  • Group Actions by – Detected Items are grouped based on the fields defined in this configuration option. The Group Actions by setting controls how Detected Items are aggregated into a single Action. The list of available fields is derived from the fields defined in the Group By configuration option in the Definition step.

  • Keep Top Actions – Only Detected Items with the highest potential impact, based on the first impact defined in the Impact Definition are considered. There is a system-enforced maximum limit of 500 Actions. If the configured value exceeds this limit, it is automatically reset to 500. The default limit is 20 Actions.
    info A value of 0 indicates that there is no functional limit; however, the system limit of 500 Actions still applies.

  1. Click the Add Action button.

  2. Enter a Summary to identify the Action.

  3. Add a Description with details of the action for the user.

  4. (Optional) Select the Due Date. The due date will be relative to the date when the action is created (now in the menu options means the day when the action will be triggered).

  5. In Assign To select to whom to assign the Action (a single 'fallback' assignee). If no one in “Assign to per Dimension” is set or no user is found based on the mapping defined there, then this fallback assignee is set for the Action.

  6. In Assign to per Dimension, you can select users to whom the Action will be assigned based on the value of any dimension of the selected series from the Definition. Mapping to users is set for the values of the selected dimensions.
    info The fields available for the Assign to per Dimension option are now limited to the dimensions selected in the Group Actions by configuration option. If no grouping field is selected, the assignment behavior remains unchanged.

  7. (Optional) Select the Action Plan and the specific Action Group to which this Action will be connected. Action Plans allow you to group Actions created by a Agent together by their nature. Action Groups are wrappers for Actions under one Action Plan.

  8. (Optional) Add a Dashboard that will be displayed in the Action detail. You can select any dashboard but only Sales Insights and Customer Insights dashboards are fully supported. Other dashboards can be used with limitations, for example, some inputs will not be recognized and values will have to be entered manually by the user. Dashboards will only work properly if their data source is the same as the data source of the Agent.
    Embedded dashboard's context (Product / Customer filters) is defined by the dimensions in the Detected Insights table. Only those dimensions which are synchronized with Customer Master of Product Master will be applied to the dashboard's filters. They will be mapped to existing fields in Product / Customer Master tables and applied as default filters.

  9. Click Continue.

Impact Calculation

Define specific metrics to calculate the expected impact of actions. Use total absolute values only, as these metrics will be aggregated.

Summary

Review the full configuration of the Agent. If everything is correct, click Submit for Approval. Once approved, the Agent becomes active and begins monitoring your data according to the defined schedule.