# What's New In Release: 55.02.00

<h2 align="center">New Features and Enhancements</h2>

### Verifone EVPAY Upgrade <a href="#verifone_evpay_upgrade" id="verifone_evpay_upgrade"></a>

M400 PINpads connected on the Verifone Commander system loaded with EVPAY 2.03.03 r04 or higher will automatically upgrade to EVPAY 2.04.02 R1 upon installation of the 55.02.00 release. (For the Fiserv (Buypass) Lab only and HPS Lab Only distributions will be upgraded to the EVPAY 2.06.00 version). Also, the Shell FEP will not automatically upgrade to any EVPAY version.

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

#### Menu Enhancements

1. Menu chains and order menus no longer require cashier or customer selection when an expanded menu with only one PLU is set as the first menu. The expanded menu PLU is automatically added to the cart and the next menu is presented.
2. A limit was added to the multi-select menu functionality to restrict the number of allowed PLU selections. The current functionality for the menu allows customers to select all PLUs within the multi-select menu. The limit will allow users to set a configured limit within the multi-select menu configuration. The limit field will only allow values up to 96 to be entered and will default to zero.

#### Lottery Purchases with Credit

{% hint style="info" %}
Lottery Purchases with Credit is not supported in the Chevron distribution. It will be supported in the Chevron Release 56.00.00 version.
{% endhint %}

A Lottery purchase is now allowed with the Credit MOP code. In Verifone Configuration Client > Payment Management, there is an additional field with a check box called “Allow Lottery Purchase.” It is disabled by default for Credit, EBT Cashback, and Store Value Card MOPs.

### Verifone C-Site Management <a href="#bookmark159" id="bookmark159"></a>

#### Synchronized Configurations

1. Verifone Commander DCR Configuration will now be synchronized with Verifone C-Site Management.
2. Verifone Commander users can now send their current primary payment configuration to the cloud when their site is onboarded so that the cloud data is synchronized with the site data.

#### Verifone Commander E and EF Variant

The Verifone Commander E and EF Variant has been added to the Site Asset Data in C-Site Management.

### Verifone C18 Self Checkout

#### Caloric Values

Caloric values may be displayed on the Verifone Self-Checkout. The caloric values are entered into the PLU configuration, and the option to enable displaying caloric values is within Verifone Configuration Client > Store Operations > Self-Checkout > Global Configuration.

#### Screen and Display Enhancements

1. Verifone C18 Self Checkout is now supported in Portrait mode. Simply rotate the screen into portrait mode from the self-checkout login screen to change the orientation. The screen will automatically adjust to scale into portrait mode. The rotation can happen anytime.
2. The Verifone C18 Self-Checkout has been enhanced to provide more customization options for site-specific branding, promotions, and advertisements. The welcome screen now supports a full screen image/GIF, and an optional banner can be added to the self-checkout home screen. To add a full screen image/GIF or a banner login to Configuration Client > Self-Checkout Configuration > Global Configuration.  Also, to improve user awareness of uploading image files and GIF files with potential security risks, a warning message prompt was added to the Browse functionality of Configuration Client's Image Upload. The prompt asks the users to accept the warning message before uploading files. This prompt appears when changing existing images and uploading new images using the add functionality.
3. Verifone Configuration Client was enhanced to support uploading a Banner file to Verifone Self Checkout Global Configuration. The banner file will apply to both Portrait and Landscape modes on the Verifone Self Checkout application.&#x20;
4. The Verifone Configuration Client Global Configuration Welcome Screen settings were updated to allow a Portrait Mode image for full screen.

#### Self Checkout Monitoring

The cashier can now view transaction details for the Verifone C18 Self Checkout using the Self Checkout Monitoring option available in POS Mode.

#### Tower Light Kit

Support has been added for those who have purchased a Banner Tower Light kit (Model TL50P1UQP) for the Verifone C18 Self Checkout. The Banner Tower Light is a pole with a light on top that is mounted next to the Verifone C18 Self Checkout. The Banner Tower Light informs the cashier and customer the different statuses of the Verifone C18 Self Checkout. The Banner Tower Light is a plug and play device. There are no configuration settings in Verifone Configuration Client. The different color lights indicate:

* Green - Ready for use
* White - In use
* Off - Not available for use
* Flashing Red - Customer needs assistance or requires age verification
* Blue - Cashier is logged in and using CSR functions
* Flashing Yellow (Briefly displayed) - Transaction is suspended. These colors are also displayed on the base C18 Light Ring.

### Verifone Vista

#### Refresh Configuration and Fuel Grade Prompting

* The Vista Refresh Configuration has been enhanced to send additional details about Departments and PLUs.
* Vista has been enhanced to remove the fuel grade prompt requirement for prepays.

### Dispenser Card Readers <a href="#bookmark162" id="bookmark162"></a>

#### DCR Payment Screens

1. The default DCR Payment screen, except for Chevron and Shell, has been revised to eliminate options such as “Pay Here with Debit” and “Pay Here with Credit” etc., specifically for an EMV-capable DCR. Customers are no longer required to explicitly choose between Debit or Credit for EMV card transactions.
2. The Manual Loyalty ID soft key (or Cancel key press) behavior has been modified to act similarly to the Reward soft key on the DCR. The customer can select “Pay Inside” after loyalty if post-pay is allowed.

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

#### Multiple Loyalty IDs

Multiple loyalty IDs can now be processed by a single loyalty host inside and outside.

#### Prompting

The following two check boxes have been added to the Loyalty Configuration in Verifone Configuration Client to disable loyalty prompting at the terminal:

* Prompt on inside transactions
* Prompt on outside transactions

By default, these check boxes are enabled.

### Mobile Payment <a href="#mobile_payment" id="mobile_payment"></a>

#### Using Credit as a Single Method of Payment

{% hint style="info" %}
This feature is only supported with Conexxus 2.0 Mobile (It is not supported for Conexxus 1.0).
{% endhint %}

The cashier no longer needs to ask the customer how they are paying for the item(s) when they are using a mobile payment application. The cashier is only required to press the Credit MOP key on the POS.

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

#### Software Installation Enhancements

1. The following improvements have been made to the Auto Upgrade process:

* The OS will not be upgraded if not needed, therefore reducing downtime.
* The history of Auto Upgrades will be retained on the system for troubleshooting purposes.
* Optimized backup and restore technique when there is no database schema changed, therefore further reducing downtime.

2. A feature was created to automatically back up the store's data so that it can be restored if there was a need for a reload. This will improve store uptime, reduce technician time on site, and reduce the reliance on technicians to create manual backups with the SMS Import Export tool.

#### System Enhancements

1. As a security enhancement, the Verifone Commander will no longer support TLS CBC cipher suites. Please see the Bulletin “TLS Cipher Suites -- Release 55.02" for more information.
2. By optimizing certain aspects of memory usage, improvements were made to the Verifone Commander performance.
3. Verifone EVPAY software is now bundled with the Verifone Commander distribution and will be installed on Verifone Engage devices. Currently, Verifone ViperPAY software is bundled with the Verifone Commander distribution.
4. The Verifone Commander no longer sends T-Logs with timing data to C-Site Management.
5. Improvements were added to the POS Pairing feature to assist with Helpdesk troubleshooting efforts.

#### TruAge Mobile QR Code IDs

1. The Online Age Verification feature has been enhanced to support the TruAge Mobile QR Code IDs. This is a digital ID that customers can sign up to use in place of their physical ID. If TruAge needs to confirm the Mobile QR Code ID, the cashier may be prompted to scan the physical ID that the customer signed up with. It is normally needed when a customer is activating their digital ID for the first time at a store.
2. Cashier will not be able to sell age restricted items to a customer that has a TruAge mobile QR code token if it is invalid. The response message is “Could not resolve the token” and the response code is ‘400’.

#### USB Scanners

USB scanners are now supported on the Verifone C18 Self Checkout and POS. The primary and secondary USB and also serial scanners are now configured in Verifone Configuration Client > Tools > Managed Modules. Currently, only the Zebra USB scanner is supported.

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

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

1. Verifone Configuration Client was allowing duplicate tank names in Fuel Configuration > Fuel Tanks tab. It was possible for the wrong tank to be assigned in the Fuel Products Configuration. This was corrected and now an error will display when a duplicate tank name is entered.
2. When a menu or PLU is added to a category in Self Checkout > Category Configuration, the description automatically fills the display name field. However, the auto fill only added\
   8-characters. This field allows 16-characters. This was corrected.
3. When apostrophes, slashes, or double quotes were used in a category name, the information was missing from the category configuration. This was corrected and double quotes and slashes cannot be used in the name, but apostrophes are allowed.
4. After performing an export of logs from the Verifone Commander, all of the department information was missing from the Verifone C-Site Management and Configuration Client. This was corrected.
5. &#x20;If a user deletes the display name of a PLU on the menu configuration screen, and saves with the display name field left empty, “null” displays in the name field on the POS or Verifone Self Checkout. This was corrected and the display name field will remain empty on the POS or Verifone Self Checkout if the user leaves the field blank.

### Verifone C-Site Management <a href="#verifone_c-site_management" id="verifone_c-site_management"></a>

When a loyalty program such as PCATS01 was disabled and then re-enabled in Verifone Configuration Client, the cards were not added to the Verifone Cloud. This was corrected.

### Verifone C18 Self Checkout <a href="#bookmark169" id="bookmark169"></a>

1. Verifone Self Checkout Global Configurations were not getting restored after an auto upgrade if Theme Color was not configured under Verifone Self Checkout Global Configuration. This was corrected.
2. On Verifone Self Checkout and using the order menu function, if Help was pressed and the “Cashier will be with you shortly” message was dismissed, “Pick x Items” message disappeared. If the menu order screen was reengaged by selecting an item, the message will reappeared. This was corrected.
3. During a Verifone Self Checkout fuel prepay and the default price level was set to Credit and then the customer paid with cash MOP, an incorrect price level was given. This was corrected.
4. Black rectangle appears in top right of the Verifone C18 Self Checkout screen when switching from portrait to landscape orientation. This was corrected.
5. Restricted items in an Order menu were not prompting for ID Verification on C18 Self Checkout and the sale was able to be completed without an ID check. This was corrected and now an ID must be entered before proceeding.

### Dispenser Card Readers <a href="#bookmark170" id="bookmark170"></a>

1. Occasionally, after inserting a chip card, the Gilbarco DCRs went to a black screen and then rebooted. This was corrected.
2. Wayne DCR prompts and messages were incorrectly recorded in the log file. This was corrected.

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

1. When a loyalty transaction was declined and then retried with a different MOP and approved, the receipt was printed with the previous declined transaction details along with approved transaction details. This was corrected.
2. The POS was displaying approved when transaction failed. The PIN pad displayed a decline message. This was corrected and now a credit failure prompt will be displayed on the cashier screen.
3. During a Visa Fleet with Host Based Restriction transaction, the PIN pad displayed approved and then it was stuck at processing please wait and no message to the cashier on the POS. This was corrected and now the appropriate restriction message will be displayed to the customer.
4. DCR prompt displayed “Enter Data” instead of “Enter Purchase/PO Number” for a fleet card transaction. This was corrected.
5. The PIN pad was getting stuck on the “Please Remove Card” prompt screen for contact cards and “Please wait” for contactless cards. When the MOP function key was selected on the POS, the sale continued. This was corrected and now “Waiting For Cashier” message will be displayed.
6. A transaction was declined after Fallback and then a card swipe attempt. This was corrected and now the transaction will be approved in this scenario.
7. When Bar Code Scanning was selected for the second loyalty prompt, the DCR did not prompt for the Bar Code and continued to the fueling stage. This was corrected.
8. Fleet card transactions were not declined when the Cancel hard key was pressed on the PIN pad or DCR. A transaction canceled message displayed, but it continued to the next prompt. This was corrected and now the transaction stops immediately.
9. The PDL Download process was not completing even if the FTP server did not respond. Since the process was still active, it was preventing a new PDL download to start. The site was unable to download a new PDL. This was corrected by adding a time out after a specified time.
10. There were extra buffers created when a batch close was performed. This had the potential to occasionally cause an out of memory issue that resulted in transactions failing when trying to run transactions on the POS. Rebooting the Verifone Commander temporarily fixed the issue. This was corrected and the extra buffers will no longer be created during a batch close.
11. When there was a fuel prepay with loyalty alternate ID in a Verifone Commander E configuration and then paid with a VISA card, the PIN pad was stuck on “Processing Please Wait” message and the POS workstation displayed the “EPS Not Responding” message. This was corrected.

### FoodService <a href="#foodservice" id="foodservice"></a>

The FoodService menu navigation buttons in Verifone C18 Self Checkout portrait mode at the bottom of the screen were overlapping receipt view area. This was corrected and now the button label text will be truncated with an ellipsis (three dots) if needed.&#x20;

### InComm FEP <a href="#incomm_fep" id="incomm_fep"></a>

Certain site-branded mag-stripe InComm cards were failing to activate or recharge with “Declined” message on the PIN pad and “E16 ISO Format Error” message on the POS. This was corrected.&#x20;

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

1. In a loyalty transaction, there was a second Get Rewards Request that should have been transmitted with two loyalty IDs, but only contained one. This was corrected.
2. The dispenser was rolling back the price even though the customer selected ‘No’ at the loyalty prompt in a multiple prepay fuel rewards transaction. This was corrected and now multiple prepay fuel rewards handling will validate and apply each rewards individually.
3. When a loyalty card was used first and then a hybrid card was used as payment at the DCR, loyalty was not applied to the hybrid card. This was corrected and now loyalty will be applied to both cards.
4. With “Authorization on Total” enabled, prepay transaction initiated on the POS, Total key pressed, “Reward Customer Y/N?” displayed on the PIN pad, ‘Yes’ was selected, loyalty card swiped, loyalty code options displayed, and then the first reward key was swiped without selecting any options, this caused other loyalty FEPs to be displayed without the header “Swipe next Loyalty” and no continue key for the customer to go ahead with the payment option. It was also occurring outside at the DCR. This was corrected.
5. After entering multiple loyalty cards followed by inserting an EMV card, the DCR displayed the “Card Not Allowed Now, Use Reward Card To Apply Rewards” message and then the transaction was declined. This was corrected.
6. Hybrid loyalty cards were not being finalized with the host. The receipt prints “Thanks for Shopping with us Enjoy Your Rewards come back soon” and “Discount From”, but the details were missing. This was corrected and now the finalize reward request is sent for the Hybrid cards.
7. The Total Loyalty discount which contains multiple discount displayed only the first PPG discount. Also, the Loyalty Report was only reporting the first PPG discount in a multiple discount transaction. This was corrected and now all discounts will be displayed and reported.
8. The space was missing between the colon and card number in the receipt for a loyalty card. This was corrected and a space was added.

&#x20;

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

1. Occasionally, the Auto Upgrade failed at “Comm Check Stage-1”. This was corrected and now the Auto Upgrade is successful.
2. In the 55.00.00 release, the PLU values for import/export were changed to allow only true or false values. When a back office partner sent PLU data to the Verifone Commander with configuration values set to yes or no instead of true or false, it would cause the import to fail. This was corrected and now the system can handle the back office PLU parameter values set to yes or no along with the existing true or false values.
3. POS Help > Home page was not loading when navigating from About > Home and Support > Home. This was corrected.
4. When a DVR was used on a Verifone C18 in POS mode, the data was overlaying correctly on the video stream. However, when the terminal was switched over to Self Checkout mode, the overlay stopped. This was corrected.
5. When the car wash menu was selected on the POS, a “Period Close in Progress” pop-up message displayed. This was corrected.
6. &#x20;The user was unable to use the keyboard after an age restriction prompt. After an age restriction prompt was completed, the keyboard was not unlocked and still only allowed numbers and the enter key to be pressed until another function was performed via the touchscreen. This was corrected.
7. An error occurred when sending T-Logs from the Verifone Commander to C-Site Management. This had the potential to cause an out of memory issue that resulted in logging to stop on the Verifone Commander. This was corrected.

### Reports

Taxes were not displaying in the Tax Reports when the tax name size was more than 10 characters and included a special character. This was corrected and the tax name will be truncated in the report if it has more then 10 characters.

### Sales <a href="#bookmark177" id="bookmark177"></a>

1. When logging into the POS, it was getting stuck on the “Sales Functions Initializing” screen. This was corrected.
2. When pressing the close (X) button in an order menu or menu chain, the user was brought to the cancel confirmation screen. On this screen, there was a back button. When the back button was pressed, it did not take the user back to the previous screen, but forward one screen. This was corrected.&#x20;

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

### Chase FEP <a href="#chase_fep" id="chase_fep"></a>

### Enhancement <a href="#chase_fep" id="chase_fep"></a>

**EMV EBT cards as Fallback**

Support was added to process EMV EBT cards as Fallback to Mag-stripe.

### Chevron FEP <a href="#chevron_fep" id="chevron_fep"></a>

#### Enhancement <a href="#chevron_fep" id="chevron_fep"></a>

**DigiCert Certificates**

Fingerprint certificates were removed from the POS so that the EPS can obtain DigiCert certificates from the Truststore Server of the EDGE box.

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

1. The EPS was sending the original amount instead of partial approved amount in reversal request. This was causing a batch out of Balance issue. This was corrected.
2. The “Acct/Card” label was not printed on the receipt for a refund transaction. This was corrected.
3. When attempting to change and save any value at Verifone Configuration Client > Payment Controller > EPS Configuration > Chevron Configuration, it displayed “Processing” and then it reverted back to its original saved value. This was corrected and now it will save the changed value.
4. When performing a sale or prepay transaction with a Gift Card, the customer copy receipt printed as expected, but the “Merchant Copy” label was missing from the receipt. This was corrected.
5. The loyalty prompt after payment on the Gilbarco FlexPay 2 and 4 DCR was attempting to add the word “Reward” after the program name that was resulting in the text being displayed as “CHEVRON AND SAFEWAY REYES/NO” instead of “CHEVRON AND SAFEWAY REWARD YES/NO”. This was corrected.

### HPS FEP <a href="#bookmark184" id="bookmark184"></a>

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

1. When the expiry date was entered for an EBT transaction, the default ‘0000’ value was sent to the host instead. It was declined with response code 107. This was corrected and now the EBT transaction will be successful.
2. &#x20;The configuration message was not being sent to the host after an auto upgrade. This was corrected and now it will be sent automatically after 90 minutes.

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

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

1. When a batch close was performed and the FEP resent all completions, the Request to Balance (RTB) was not including user and EMV data in WEX EMV transactions. The batch was not closing and causing chargebacks. This was corrected.
2. The transaction date and time was not matching the dates and times in the preauthorization, completion and data collect messages of SVS fueling transactions. This was corrected.
3. The preauthorization was not matching the WEX card number provided in the completion message. This resulted in a transaction posting to a terminated card. Also, Fallback transactions were not displaying an odometer for the preauthorization and the Driver and Vehicle number was not matching between preauthorization and completion messages. These were corrected.
4. When split tender was used with multiple cards inside on the POS, only one card printed on the completion receipt. This was corrected.
5. After a fresh install of software, the system is asking to Close Day in order to apply the EMV PDL. This was corrected and now the EMV PDL will be applied without closing the day on fresh installs.

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

#### Enhancements <a href="#bookmark189" id="bookmark189"></a>

**EMV EBT cards as Fallback**

Support was added to process EMV EBT cards as Fallback to Mag-stripe.

**ExxonMobil DCR Logo**

Sites can now choose between an Exxon or Mobil DCR logo. The logo selection is available exclusively on Gilbarco M7 and Wayne iX Pay 1 and iX Pay 2 DCRs.

**Fleet Card Certification and Support**

{% hint style="info" %}
Fleet cards are currently certified for M400, P400, Bennett, Gilbarco, Invenco, and Wayne devices (See the DCR firmware section for minimum versions).
{% endhint %}

Card support has been added to the Buypass (Fiserv) distribution for EMV WEX and Visa Fleet 2.0 and host-based restrictions, EMV Fuelman cards, EMV contactless refund transactions, EMV contactless support for JCB, formerly known as Japan Credit Bureau, and China Union Pay (CUP), and Visa Fleet 2.0 support for non-capable and non-certified devices.

**Sunoco DCR Color Logo**

Color logo support has been added for Sunoco on Gilbarco M7 and Wayne iX Pay1 and iX Pay 2 DCRs. Support will not be available for other DCRs such as Gilbarco M5, Wayne Anthem, Bennett, and Invenco.

**Sunoco LAN Configuration**

The LAN Configuration settings have been customized for the Brand selection “Sunoco” in the Buypass distribution. Fiserv and Sunoco Incomm device specific routes have been added to the Local Area Network (LAN) Configuration.

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

1. When the Host Based Discount download was sent, it started the FBSeq as ‘0001’ instead of ‘0000’. This was corrected and now the first packet will be sent with ‘0000’\</FBSeq>.
2. After TAVE registration, the Update Settings or Advance DDK was not sent to EPS, but after a DCR Driver Initialization, the commands were sent successfully. This was corrected and now the Update Settings and Advance DDK commands are now sent.
3. For Marathon, after the DCT configuration download, the system was creating multiple duplicate entries for the Universal MasterCard Fleet card in the card table. This was corrected.
4. A signature line was being printed on the bottom of the receipt for Fallback transactions in the ExxonMobil and Sunoco brand selections. Also, the signature line was not being printed for small credit transactions. This was corrected and a validation was added to print the signature line only when needed.
5. Manual entry of PCI cards were matching with different Card Type Indicator (CTI) that had manual entry flag as ‘M’ and prompting for cash advance. This was corrected.
6. ValueLink gift cards with 16-digits and 19-digits were failing unrestricted refund transactions. This was corrected.
7. The socket connection used for the network was dropped and there was no recovery process for certain scenarios. It caused transactions not to complete with the host. This was corrected and now the system will reconnect if dropped.
8. A customer was able to get an approval for a cash advance on a commercial fleet card without a fuel prepay. The site allowed cash without sales. This was corrected and now a fuel sale is required before the cash advance.

### VAPS FEP <a href="#bookmark191" id="bookmark191"></a>

#### Enhancement <a href="#bookmark192" id="bookmark192"></a>

**Network Reports**

The text “Contact Network Provider” has been added to the Batch Detail Report, Network Report and Exception Report for batches that are in a stuck state.

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

1. When split tender was used with multiple cards inside on the POS, only one card printed on the completion receipt. This was corrected.
2. The transaction date and time was not matching the dates and times in the preauthorization, completion and data collect messages of SVS fueling transactions. This was corrected.
3. The preauthorization was not matching the WEX card number provided in the completion message. This resulted in a transaction posting to a terminated card. Also, Fallback transactions were not displaying an odometer for the preauthorization and the Driver and Vehicle number was not matching between preauthorization and completion messages. These were corrected.
4. After a fresh install of software, the system is asking to Close Day in order to apply the EMV PDL. This was corrected and now the EMV PDL will be applied without closing the day on fresh installs.

### Verifone EPS FEP <a href="#bookmark194" id="bookmark194"></a>

#### Enhancement <a href="#bookmark194" id="bookmark194"></a>

**Merchandise and Fuel Prepays**

Merchandise is now allowed with a fuel prepay transaction. The product check has been removed when processing the fuel prepay for card preauthorization when using the Payware FEP.


---

# 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-55.02.08/whats-new-in-release-55.02.00.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.
