# What’s New In Version: 56.02.01

<h2 align="center">Resolutions</h2>

### Verifone Configuration Client <a href="#bookmark60" id="bookmark60"></a>

1. The Security Log Servers Configuration was displaying an internal error when trying to add or update a log server IP in Verifone Configuration Client. This was corrected.
2. The DNS values displayed in Verifone Configuration Client were determined by the sequence of elements in the incoming XML rather than their unique IDs. As a result, DNS3 was populating on DNS1. If there were no DNS entries configured on DNS1 and DNS2, the remaining values shifted upward and appeared in the wrong fields. This issue was limited to the information viewed in Verifone Configuration Client. The XML payload had the correct IDs. This was corrected by binding each DNS to their respective configuration IDs.

### EPS System <a href="#bookmark61" id="bookmark61"></a>

The user had to perform multiple day closes to apply the network tables. This was corrected and now only one day close has to be performed to apply the tables.

### POS System <a href="#bookmark62" id="bookmark62"></a>

1. Verifone serial printers (RP-300/310/320/330 and TM-88) without white labeling firmware were displaying “Receipt Printer Unavailable” or “Receipt Printer Unsupported” alarm messages. This was corrected and now the messages no longer display.
2. After configuring Security Log Servers in Configuration Client, the POS started to lock up on the “Sales Functions Initializing” screen. This was corrected.
3. In Verifone Configuration Client > Managed Modules, when scanner and printer device types were changed from serial to USB and the POS was rebooted to engage the device, the printer module “Printer Type” changed to “VFIPrinter.submodule.” This was corrected and now it displays correctly.
4. The following charity donation expected prompt messages were not displayed on the POS screen:

* Charity In Progress
* Please acknowledge the charity prompt on the PIN pad or POS

  This was corrected and now the prompt messages will display after entering values from the keyboard.

5. POS was locking up on the “Sales Functions initializing” message when navigating through different screens. A system reboot was required to recover. This was corrected and now the user can navigate through the POS screens as expected.

### Dispensers <a href="#bookmark63" id="bookmark63"></a>

There was a possible intermittent issue with dispensers not allowing a preset due to pump stopped. This was corrected by making an internal update to improve handling.

### Loyalty <a href="#bookmark64" id="bookmark64"></a>

When the user selected loyalty outside and payment inside, loyalty was prompted again inside. The loyalty information was not retained for the postpay sale. This was corrected and now the loyalty ticket references are retained for settling the postpay fuel transaction.

<h2 id="bookmark65" align="center">FEP Specific Changes</h2>

### Phillips 66 FEP <a href="#bookmark66" id="bookmark66"></a>

#### Resolution <a href="#bookmark67" id="bookmark67"></a>

The Network Configuration for Phillips 66 was not preserved after an auto upgrade from 56.00.00 to 56.02.01. This was corrected and now it is preserved.

### Rapid Connect FEP <a href="#bookmark68" id="bookmark68"></a>

#### Resolutions <a href="#bookmark69" id="bookmark69"></a>

1. Site was processing on TID 002, but reporting totals on TID 001. The original MID and TID were not being reset to null after Close Daily. This was corrected and now the original MID and TID are reset to null after response received for the host totals.
2. Changes have been made to comply with the latest Datawire protocol.

### Shell FEP <a href="#bookmark70" id="bookmark70"></a>

#### Resolution <a href="#bookmark71" id="bookmark71"></a>

When the POS-to-EPS cable was disconnected during fueling and then reconnected more than three minutes after fueling was completed, the EPS failed to send the Card Financial Advice CSR message. This was corrected and now it sends the Card Financial Advice CSR message.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/commander-release-notes/verifone-commander-release-56.03.00/whats-new-in-version-56.02.01.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.