--- title: "What's New in DMS" canonical: "https://docs.rubiconwater.com/space/DMS/2071790213/What's%20New%20in%20DMS" format: markdown --- > Macro (toc) # NF 2026.1.2 ## Reordering in a Ration Period - A grace period can be configured during which Irrigators can reorder after cancelling an order during a ration period to allow irrigators to correct mistakes made when cancelling orders. Following that, a restriction period can be configured during which they will not be able to reorder. - A restriction period can be configured to prevent irrigators from immediately reordering on the same outlet after cancelling an order scheduled for a future rationing period so they do not block future capacity Irrigators will be alerted of any restrictions and when the restriction periods end. > ℹ️ **Note** > ℹ️ > ℹ️ See [Configuring restrictions on re-ordering during a ration period](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2053439583/Configuring+the+System+for+Rationing#Configuring-Restrictions-on-Reordering-during-a-Ration-Period) for more details. Contact Rubicon Support if you need to configure these features. # NF 2026.1 ## Rationing with Delivery Shares - A new system parameter, **Standby water period hours**, defines a period starting from the current time during which irrigators can order water without being constrained by their *Delivery Share*. The order must begin and end within the standby period and you must currently be in a ration period. - Planners can now group delivery share across service points, enabling the use of the total delivery share entitlement of the service points when ordering. - Irrigators can now place orders using the total delivery share volume across grouped service points. - Irrigators can now view the delivery share for their outlet when placing an order. # NF 2025.2 - If you are [https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2294972417](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2294972417) then if you place an order that overlaps a change in daylight savings the system will automatically adjust the duration of the order if necessary so that the start and finish times that you have entered are correct. - The feature to automatically reject suggested orders can be enabled by setting the value of the **Available order actions when order changed by DMS** parameter to AUTO_REJECT. - If the **Maximum flow items per order **parameter is set to 1 (the default is 50), the option to add flows will not appear in the user interface. Changes to the flow must be applied to the whole order. # NF 2025.1.2 - When scheduling the Running Sheet you can use the **Is the System Using Planning** parameter to contol what dates are used for the report. - If the parameter is set to *Yes*, the report can only be run for plan dates - If the parameter is set to *No*, the report will default to the latest finalised plan date if possible but you can modify the date if necessary. - For irrigators ordering with IVR or CustomerConnect, if you have specified a **Default Start Time** that will be defaulted in for the irrigator but it won’t be enforced unless you ALSO set the **Enforce Start Time** attribute to *Yes*. The **Order Duration Interval** will now only control the order duration and won’t affect the start time. - You can specify whether you want order notifications sent to all the operators for an outlet (this is the default), or just to the irrigator who placed the order. Set the **Lodged Party Only** attribute on the Customer Communication Type object to *Yes* to restrict notifications to the operator who lodged the order. # NF 2025.1.1 - You can add push notifications as a delivery method in the [Comm Types module](https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2018672641) (DMS) and as an Action Type in the [Alarm Actions module](https://rubiconwater.atlassian.net/wiki/spaces/ANC/pages/1989968507) in SCADAConnect Forms. These notifications will be available in NetworkConnect and SiteConnect. - The DMS Preset Service, the TCC Service, and the Presets from Orders functionality can all now be configured to consider only confirmed orders. - You can now [add a note](https://rubiconwater.atlassian.net/wiki/spaces/BNC/pages/1990361098) when creating a Billing adjustment. The note will be displayed on the Refund Listing Report. - When an outlet is transferred to a new property any previous link between the authorisation and a delivery share are removed. # NF2024.2.2 - Notes can now be displayed on reaches in the network and planning schematic. Right-click on the reach and select **Notes** to view or add notes. - A new configuration option is available to automatically expire "DMS update" audit messages. When enabled, the message will no longer appear in the Planner's message inbox avoiding the need for acknowledgement. The messages can still be found by using the find message option. Contact Rubicon Support if you need to enable this feature. - In the Metadata Audit Log, in the ‘Change Info’ column TAG_WRITE is displayed as ‘Site Name : Tag Description. ## Rationing - Orders not modified within a rationing plan are subject to the same rules as orders that were modified by rationing. - You can enable or disable changing or cancelling orders within a ration period. See [Enabling or Disabling Order Changes](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2053439583/Configuring+the+System+for+Rationing#Enabling-or-Disabling-Order-Changes). - You can force an outlet to apply a restricted rate even if the restriction period itself is set to *Exclude* mode. See [https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2051900084/Configuring+the+Rationing+Tool#Configuring-the-Ration-Restriction-Percentage-for-Outlet-Groups](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2051900084/Configuring+the+Rationing+Tool#Configuring-the-Ration-Restriction-Percentage-for-Outlet-Groups) for details. ## Configuring NeuroFlo Apps - You can now give users the option to modify the default start time for orders. If you have configured the **Default Start Time for Order** attribute, a start time will automatically be defaulted in for an order. However the start time will not be enforced unless you have also set the new **Enforce Start Time** attribute to *Yes*. See [https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2631172097](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2631172097) for details. - You can now control whether meter readings entered in CustomerConnect are referred to a Planner if they exceed the user’s allocation. - Use the **Refer meter readings to planner when allocation exceeded** parameter to control whether over-allocation readings are referred to the Planner. - Use the **Bypass Meter Variance Checks **attribute to control whether readings that are out of the expected range are referred to the Planner. This means that you can disable variance checks for unplanned outlets but still refer readings that exceed allocation. See [https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2002026613](https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2002026613) for details. - If a user logs into DMS as a Planner and selects a Planning Area they will also have Planner access to that area in NetworkConnect and SiteConnect and will be able to see any relevant sites and customer messages until they log out of their session in DMS. See [https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/2659287156](https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/2659287156) for details. # NF 2024.2.1
NF 2024.2.1 - You can automatically populate the *Username* field from another field on the Party when a new party is created either manually or automatically. The field to use is specified in the **IVR/WEB login userid** **column** parameter. This may be useful if you are configuring login credentials for applications that require a *Username* value for logging in (for example, CustomerConnect). See [https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2454257674](https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2454257674). - You can now use the Notice Period attribute on the **Order End No Recurring Alerts **comm type to control when these alerts are sent. See [https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2018672809](https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2018672809). - There is a new attribute **Ration Restriction Percentage** that can be applied to outlets in an [Outlet Group](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/edit-v2/2051900084#Outlet-Grouping). When this is configured for outlets, the default participation mode of those outlets during a restriction plan will be *Restrict* even if the overall mode for the plan is *Exclude*. You can manually adjust orders to use either *Restrict* or *Exclude* mode in an *Exclude* plan. ### Changes Related to SiteConnect, NetworkConnect, CustomerConnect, and MeterConnect > ℹ️ **Note** > ℹ️ > ℹ️ These changes are included here because there are associated changes in DMS or because they require configuration in DMS. - You can now lock specific users out of CustomerConnect by using the DMS **System Lockout** feature on the *Customer Applications *authentication group. See [Lock or Disable a User Account](https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/1983610944/Preventing+a+Party+from+Logging+In#Lock-or-disable-a-user-account). - Messages sent from CustomerConnect are now received in the DMS messages inbox by the planner who is actively planning the area/group that contains the irrigator’s outlet. - Water Authorities can restrict the ability of customers to change their own contact details by adding or removing the *Manage Own Customer Details* function from the customers' role in Security Manager. See [https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/2471493732](https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/2471493732).
# NF 2024.1.2
What's new in NF 2024.1.2 - A new parameter - **Meter reading mandatory for Metered SP **-** **has been** **added to specify whether meter readings for past orders are required before transferring outlets. This defaults to *Yes*. - If a customer takes water that they have not ordered during a stored water restriction period, their stored water usage will not be calculated correctly. This discrepancy can be corrected by using the [Order Reconcilation ](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2313814037)module which creates orders to account for the missing usage and allocates it as stored water usage. - Users can now access the Customer Entitlements Report from the Irrigator Portal in mobile view. ### Changes Related to SiteConnect, NetworkConnect, CustomerConnect, and MeterConnect > ℹ️ **Note** > ℹ️ > ℹ️ These changes are included here because there are associated changes in DMS or because they require configuration in DMS. - Data for orders placed using SiteConnect, NetworkConnect, and CustomerConnect are now included in the Order Stats report. - There are two new parameters to control the default reason types that can be specified when entering readings in SiteConnect and MeterConnect: - *Default Estimated Meter Reading Reason Type* - this also sets the default for normal readings. - *Default Meter Reading Adjustment Reason Type*. - Messages sent from DMS as both voice and text can now be received as text messages in CustomerConnect. - Order Duration Intervals (formerly Order Privileges) can now be specified in minutes. This change only affects orders lodged in the NeuroFlo next generation apps where order duration can be entered in minutes. If you have already set up order duration intervals you do not need to change them. The values you have configured will continue to work as they did before. > ℹ️ **Note** > ℹ️ > ℹ️ If you are creating new order duration intervals in minutes please consider the [Order Duration Side Effects](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/edit-v2/2295070721#Order-Duration-Interval-Side-Effects).
# NF 2024.1.1
What's new in NF 2024.1.1 **Messages** - The DMS Messages inbox will now pop up automatically whenever you receive a new message. - Planners can now reply to customer messages using SMS. Select SMS as the sending option in the New Message screen. **Orders** - You can now use the **Disable Emergency Stop of TCC Partial Orders** parameter to prevent irrigators from emergency-stopping an outlet with TCC mode set to Partial. This will apply to the Irrigator Portal and to CustomerConnect. - By default, the Order list is now sorted by start time. **Parties** - If a customer is an owner or operator of more than one property you can now generate all of their water statements at once. Choose the statements you want to generate in the **Generate Water Statements** option in the Parties module. See [Run a Water Usage Report for a Party.](https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/1983054010/View+Customer+Balances+and+Water+Usage#Run-a-Water-Usage-Report-for-a-Party) - You can now [un-retire](https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/1983610885/Retiring+a+Party#Unretiring-a-Party) a retired party in the Parties module. **Other** - Automatically read meter readings that differ from the expected reading by more than the configured tolerance limit will now be listed with the reason “Auto out of variance” in the Meter Reading History module. - You can now configure the default change interval used to generate the [Running Sheet report](https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/1986888436) by setting the **Default change interval** parameter. This defaults to six hours which is the previous built-in default.
# NF 2023.1.3 > ℹ️ The V_MESSAGE_DATA_TAG view will no longer exist. > ℹ️ > ℹ️ - ScadaWeb auditing will no longer work, auditing data will be available via SiteConnect and NetworkConnect on the [https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/1914765847](https://rubiconwater.atlassian.net/wiki/spaces/NC/pages/1914765847) page. > ℹ️ - All custom reports that use this view will no longer work and must be recreated. > ℹ️ - Data will not be available in the auditlog table.
What's new in NF 2023.1.3 - In the [https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/2014806017](https://rubiconwater.atlassian.net/wiki/spaces/RptNC/pages/2014806017) the regulators are now listed in alphabetical/numerical order. - A new attribute, **Site Operating Alarm - Flow Above/Below Tolerance**, is available that allows the Flow Above/Below tolerance to be configured at a site level. See [https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2002026641](https://rubiconwater.atlassian.net/wiki/spaces/CFGNC/pages/2002026641) for more details. - Notes attached to orders in CustomerConnect will be available as messages in the Orders module.
# NF 2023.1.2
What's new in NF 2023.1.2 - In CustomerConnect, irrigators can now [Enter Meter Readings](https://rubiconwater.atlassian.net/wiki/spaces/CC/pages/2071724068). Access to this is controlled in DMS. See [https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/2071887896](https://rubiconwater.atlassian.net/wiki/spaces/UMNC/pages/2071887896). - A new parameter **Enable Shared Selection** is available to enable selection of the correct ABA when reading the meter at a shared outlet. Note that this is not enabled by default. - You can now create [Maintenance Schedules ](https://rubiconwater.atlassian.net/wiki/spaces/NWNC/pages/2000978886)that begin and end in the past. - When using the Exclude [https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2051899994](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2051899994) for restrictions, the way that the number of “since last restricted” days is calculated has been changed to give priority to outlets with more restricted days in a row. # Rationing with Ration Periods See [What’s New in Rationing with Ration Periods](https://rubiconwater.atlassian.net/wiki/spaces/PNC/pages/2052489273).