@tdipisa by they way.
I noticed that the documentation for the pages
https://mapstore.geosolutionsgroup.com/mapstore/docs/api/plugins#pages.RulesManager

Disappeared on dev

https://dev-mapstore.geosolutionsgroup.com/mapstore/docs/api/plugins#pages.RulesManager

Trying to apply tthe same config, I have this result

While I see on dev it works well:

So we have to update the doc properly to explain how to setup rule-manager.

The new correct config, copied from dev instance, is this:

"rulesmanager": [
      "Redirect",
      {
        "name": "BrandNavbar",
        "cfg": {
          "containerPosition": "header"
        }
      },
      "Home",
      "ManagerMenu",
      "Login",
      "Language",
      "RulesDataGrid",
      "Notifications",
      {
        "name": "RulesEditor",
        "cfg": {
          "containerPosition": "columns",
          "disableDetails": true
        }
      }
    ],

If documented somewhere, it should be linked in rules-manager plugin.
I'd document also how to obtain the ID of the geoserver instance, that is now not clarified.

I had to create an instance by sending the following post request

curl --location 'http://localhost:8080/geofence/rest/instances' \
--header 'Content-Type: application/json' \
' \
--data '{
  "name": "GeoServer",
  "description": "",
  "baseURL": "http://localhost:8080/geoserver",
  "username": "admin",
  "password": "geoserver"
}'

It returns the ID of the instance in plain text (e.g. 7)

You can get the current configured instaces with this call:

curl --location 'http://localhost:8080/geofence/rest/instances' \
--header 'Accept: application/xml' \
'

The ID should be used in configrued geoServerInstance in localConfig.json

@offtherailz

@tdipisa by they way.
I noticed that the documentation for the pages
https://mapstore.geosolutionsgroup.com/mapstore/docs/api/plugins#pages.RulesManager

Disappeared on dev

https://dev-mapstore.geosolutionsgroup.com/mapstore/docs/api/plugins#pages.RulesManager

thank you for informing about that. I think we have to check why and restore, then. Please take care of this as part of this PR @mahmoudadel54, if possible.

@offtherailz

• yeah, the 1st issue is a bug not related to the work in this issue [I fixed it]
• for the ipAddressAny parameter do not have any effect. you should use this link https://tehnoblog.org/ip-tools/ip-address-in-cidr-range/ which I added into the PR description above to validate your filter
• for the crashing in ipAddressAny filter please give me clear steps to reproduce as I have tried many time but can't reproduce it
• for the date filter by writing date manually --> I will fix it

• I noticed this bug, not sure it is related to the PR, but on dev is not reroducible.

MapStore.mp4

StandardRouter.jsx:88 TypeError: Cannot read properties of null (reading 'scrollTop')
    at DataGrid.eval [as scrollListener] (DataGrid.jsx:29:35)
    at RulesGrid.eval [as componentDidUpdate] (RulesGrid.jsx:46:19)

• The ipAddressAny parameter do not have any effect. I'd expect it to filter by precise IP (range) vs if the rule is applied. Verify if it makes sense, or if it doesn't show it checked and disable. The same looks to be

MapStore.1.mp4

• See the video above (for ipAddressAny, I had a crash while recording .

StandardRouter.jsx:88 TypeError: Cannot read properties of undefined (reading 'id')
    at eval (react-data-grid-addons.js:9672:39)
    at Array.filter (<anonymous>)
    at CustomDragLayer.isDraggedRowSelected (react-data-grid-addons.js:9671:30)
    at CustomDragLayer.getDraggedRows (react-data-grid-addons.js:9690:29)
    at CustomDragLayer.renderDraggedRows (react-data-grid-addons.js:9702:20)
    at CustomDragLayer.render (react-data-grid-addons.js:9745:31)
    at finishClassComponent (react-dom.development.js:18407:31)
    at updateClassComponent (react-dom.development.js:18360:24)
    at beginWork$1 (react-dom.development.js:20108:16)
    at HTMLUnknownElement.callCallback (react-dom.development.js:362:14)

• Another crash while playing on date filter.

MapStore.2.mp4

StandardRouter.jsx:88 TypeError: Cannot destructure 'state.filters' as it is undefined.
    at rulesmanager (rulesmanager.js:161:15)
    at combination (combineReducers.js:126:29)
    at reduce (StateUtils.js:256:14)
    at standardRootReducerFunc (defaultOptions.js:79:8)
    at rootReducer (StandardStore.js:90:12)

@tdipisa @offtherailz after the changes and clean up of JSDoc (#10814) that includes the automated script to list plugins now only plugins will checked and go in the plugins doc. The RulesManager is a page and not a plugin so afterward I moved it in the framework doc (#10877) so in the new doc for this page is here https://dev-mapstore.geosolutionsgroup.com/mapstore/docs/api/framework#pages.RulesManager. If we want to move it again inside the plugins doc we need to improve a bit the jsDocUtils.js to include pages automatically inside the plugins documentation

So @mahmoudadel54 for the moment linking (with a relative path) the plugin to the page doc is enough. Something like: "This Plugin requires the configuration of the rules-manager page (link) to be activated. "

@etj we need you to double check the above and address it.

I will perform more test at the end of this week, anyway the "any" boolean does not work the way you think:

• If you don't set a filter for a given field, no "WHERE" clause will be added on such field
• When you do set a filter on a field, there will be a WHERE clause with field=value
• When you set a filter on a field, setting the fieldAny=true, there will be the WHERE clause field=value OR field is null, in order to retrieve also rules which impose no constraints on such field.

@etj I was reading the actual tooltips for the checkbox to deduce functionality. In fact I think that while for the other rules this can be the same, in this case setting the velue Any to true has not the same meaning (because of range nature of these fields).
Maybe we have to change the tooltip, hide the checkboxes for these fields, or properly implement the functionality on BE.
@tdipisa let's check this point asap.

@offtherailz pls report

• the list of rules you have in the db
• the filtering you are requesting
• what geofence returns

Ok, a mix of unclear behavior, not clear API pre-existing bugs generated the misundestanding.
Here I explain tha main points.

Api behavior

For any field/flagAny ( associated to the checkbox in inverse logic) The API has this behaviour:

1. Value is missing
   1. flag not present -> no filtering
   2. flagAny=false -> no filtering
   3. flagAny=true -> All the rules that has null in the given field
2. Value is present
   1. flag not present -> search all fields that match the rules (including nulls)
   2. flagAny=false -> all rules that match only because of the specific field (excluding nulls)
   3. flagAny=true -> earch all fields that match the rules (including nulls) as (2.i)

MapStore bug

The client has a pre-existing bug that, initially do not send the flag, then when checked sends the flag to false (inverted logic) and then when unchecked sends the flag to true. There is no way to reset the flag.

Instead, the checkbox should send only the flag to reproduce the conditions:

• With no value, the flag should not be send (actually it happens only on startup, after check/uncheck the value is always sent)
• When value is set:
  • When checked, the flag should be send with value false
  • When unchecked the flag should be sent with value true.
• In order to better clarify the behavior and avoid future misunderstanding, I'd also modify the tooltips as indicated at the end of this comment

This has to be fixed, maybe in a dedicated issue/PR.

Expected functionality

As a user I'd expect the functionality to search by content or by match. Checking by "all the rules thah match but not because of null" is hard to understand for a user, but it is what is offered by the current API.

We can not change or enhance GeoFence, so I'd at least better indicate the filtering condition.

The current tooltip tells to check to "filter by selected value" that is a little generic.

I'd suggest the following tooltips:

• When checked (flagAny=false) → "Currently showing only rules that match the provided value. Uncheck to also include rules where the field value is missing."

• When unchecked (flagAny=true) → "Currently including all rules that match, even if different from the given value. Check to filter only by this field value."

@offtherailz and @etj thank you so much for clarifying the above.

@mahmoudadel54 we need you now to provide:

• The fix to the filter check logic
• The tooltip improvement

see above for more details.

@ElenaGallo, could you please test this on DEV ? Thank you
Ideally we should test:

• Standalone new version (nightly)
• Embedded new version (nightly)
• Standalone old version (I suppose this tool needs to work with current and old versions of geoserver/geofence too)
• Embedded old version (I suppose this tool needs to work with current and old versions of geoserver/geofence too)

Actually on dev we can test only embedded old version.
During dev we tested the Standalone new version.

Let's check if the functionalitries break something (e.g. adding an ip rule or a date rule, trying to filter by ip or by date).
Try to save edit and filter also by other fields (e.g. user or layer), to verify the functionalities are preserved.

@mahmoudadel54 @tdipisa The Date functionality works, but the Date filter is not clear to me.
If I enter the interval >2025-11-18 & <2025-11-19 in the rule, when I filter for the date 2025-11-18 in the filter box, the rule with >2025-11-18 & <2025-11-19 does not appear in the list.
In this case, shouldn’t the date 2025-11-18 be included?

@mahmoudadel54 @tdipisa The Date functionality works, but the Date filter is not clear to me. If I enter the interval >2025-11-18 & <2025-11-19 in the rule, when I filter for the date 2025-11-18 in the filter box, the rule with >2025-11-18 & <2025-11-19 does not appear in the list. In this case, shouldn’t the date 2025-11-18 be included?

The docs here: https://docs.geoserver.org/latest/en/user/extensions/geofence-server/rest.html#filter-parameters
mentioned:

So I think the filtered date you entered not included.
@tdipisa can confirm if it is right or not.

@mahmoudadel54 exactly. @ElenaGallo only single date value is allowed in the filter. Please check and let me know asap if we can mark the issue as Accepted.