How to Review Deployed Agents

How to Review Deployed Agents

After the deployment of an Agent, it is advisable to open its configuration and verify that all the automatically created settings meet your requirements.

  1. Go to Pricefx Agents > Agents in the module menu.

    image-20250723-085153.png
  2. On the Agents list page, open an Agent by clicking its name or label.

  3. Review the Agent’s steps.

The following sections describe the items in the individual steps that you should pay attention to.

Definition

This step sets the scope of the data for the Agent.

  1. Review (or set):

    • Group By
      Evaluate whether the level of granularity is appropriate. You may also consider including additional fields such as Customer or Product attributes, that could facilitate better analysis of the outputs, depending on the specific context.

    • Measures
      Review the Measures to ensure they are aligned with the expected business objective.

    • Dimension Filter, Generic Filter and Aggregation Filter
      Use the Dimension Filter, Generic Filter, and Aggregation Filter to adjust the scope, ensuring that only the relevant Customers and/or Products are filtered accordingly.

  2. Click Apply Settings to display data preview.

  3. If you are happy with the results, click Continue.

You may also consider adjusting the time range using the Generic Filter, especially for the Agents, which analysis depends on trends and variations.

agentDefinitionGenericFilterScopeAdjusment.png
  • When defining measures, make sure that the name that you give them is not identical with a field in the Datamart.

  • When joining data series, verify that in the Join Series definition none of the selected dimensions contains rows with null values. A database Join will not join two rows that have null value in the same field because null != null. For more details see https://pricefx.atlassian.net/wiki/spaces/ACC/pages/6421905697.

Detection Rules

This step sets the alert conditions for the Agent and its schedule. Actions will be triggered during the next Agent run when the set conditions are met.

  1. Select a series and define conditions. You can preview the data that meet the condition by clicking Preview Rules.

  2. Set up a schedule for running the Agent.

  3. Click Continue.

Refine the Detection Rules based on the specific business context and the number of cases identified.

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.

    GroupActionsByReference.png
  • 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.
    A value of 0 indicates that there is no functional limit; however, the system limit of 500 Actions still applies.

    keepTopActionsReference.png

Ranking Based on Impact

When Actions are limited, the system retains the Actions with the highest impact, allowing users to focus on the most critical issues first. The resulting Actions are stored in the Actions Datamart Table. Detected Items that do not result in an Action being created are removed.

  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.
    The fields available for the Assign to per Dimension option are now limited to the dimensions selected in the Group Action 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.

  • Adjust the Action's Summary and Description, as these will be used in the email messages sent to the assigned users.

  • Review the Impact Calculation, particularly the Realization Rate (%), in accordance with the specific business objective.

Action Task

Action Task let you define follow‑up operations that users can trigger directly from Actions created by an Agent, for example, creating quotes or updating Simple Live Price Grids from selected detected items. You can configure available follow‑up types and how Agent dimensions (such as customer, product, dependency level, and recommended price) are mapped into the downstream objects, while the Action UI then shows result tables so users can see which quotes were created or which Live Price Grid items were updated from each Action. For more information see Action Task.

Summary

Review the setup of the Agent, here you can see all the set parameters in one place. For more information about the Summary step see Summary Step.

If you are happy with the setup, click Submit for Approval. Once the Agent is approved, it becomes active and starts monitoring your data based on the schedule.

Review the final results in the Summary step. Summary step also provides the Expected Impact portlet. For more information see the Expected Impact By Agent and Total Expected Impact.

Schedule

It is good practice to set the Start Date in the Schedules to a past date, ensuring that the calculation actions begin immediately.

agentsSummarySchedules.png
Agents Schedules

 

Notes

  • After the approval/activation this step displays the results of the Agent: detected insights, actions and action plans for each run.

  • Note that an active Agent is read-only and you cannot make any edits. You can, however change or add schedules – go to 3 Dots menu > Schedules.

    Under this menu, you will find also other useful options, enabling you to review the Agent’s tables, attachments or execution history.

  • If you need to edit an Agent that is already approved and active, the only option is to go to the Agents list page, select the Agent and Duplicate it. Once done, the previous Agent can be deleted from the same page. The new duplicated Agent will be in the Draft status and can be edited.

Follow-up

Once the Agent is set up it is run regularly as per its defined schedule. When the alert condition is met, action will be created for the defined users. They will be notified by email and in the Notification center and they will see the assigned Actions on the Actions page.

  • The Agent does not automatically re-create the same kind of Actions every time it is run:

    • The same kind of Actions that have been created previously and are still open (or rejected, blocked, postponed) are not re-created.

    • Actions that have been marked as done are re-created if more time has elapsed from their original due date than the set schedule period. For example, if the original due date of an action is April 30 and the Period in the Schedule section is set for 1 month, Actions will start to be re-created after May 30.

  • Previously postponed Actions are reopened if the due date is in the past.

See Also