# November 5, 2024 — Rule engine, filter and metric improvements

New in the **Rules** engine:

- New variable `$card_bin`, representing the card issuer, and new function `count($user_profiles, [period])`, which returns the number of different cards used by the same user. See the [documentation](/en/transactional/expression-syntax/) for more details.
- Simulate rule execution: open any version of a rule, click the arrow next to the **Edit** button, and choose **Simulate**. You can run the simulation from real payment data or fill in the variables freely.
- Improvements to validating nonexistent lists when creating rules. The platform now prevents deleting lists that are being used by active rules.

Updates to the **Explore** screen:

- We improved the usability of filters to make it easier to identify the active fields in each search. We will soon replicate the same reorganization across other screens of the platform.
- We fixed an intermittent issue where the Explore screen showed no results in queries with large data volumes.

Other improvements:

- New **Metrics**: **Total amount by merchant and status**, **Average duration (ms)**, **Average duration (ms) by connector ID**, and **Average duration (ms) by connector ID, card network and issuer**.
- You can now send card data in the update (`PATCH`) of the [payments API](/en/api/methods/patch_payments_id/), if this data was not sent at creation (`POST`). This reduces the negative impact on the quality of later risk analyses when card data cannot be obtained at creation time.