An update to WebPay is approaching soon, and we wanted to make sure you have the information you need to best prepare:
Following a review of accessibility across the site, improvements have been made to allow users that require a screen reader or keyboard only to better navigate through the site.
A new ‘skip to content’ link has been added to allow keyboard only users to press TAB once and ENTER to skip all navigation links and go straight to the main content on the page. (Figure 1)
Note: This will only display when pressing TAB once when the page is initially loaded.
Help icons and text have been added across the site to aid a user’s understanding of what is required. (Figure 2)
The traveller’s title (Mr, Mrs etc) is no longer mandatory when creating/amending a Deployment.(Figure 3)
A user with applicable access levels can now mark Supplier Reference and Payment Restrictions as mandatory fields per Card Pool in the Administration section. These new options join the previously available fields in the Manage Mandatory Data section of a Card Pool. (Figure 4)
Once ticked, the fields will be required to be populated when a user attempts to create/amend a deployment for that Card Pool. (Figure 5)
It is now possible to search for a deployment based on the Platform it was created on.
A dropdown list shows possible options to search by on the Deployment Search page. (Figure 6)
Note: Only Shared Platforms will display this new search option. Agency owned Platforms will not show this new search field
Previously, when using a multi-type Card Pool, it has not been possible to restrict certain spend types. A Card Pool can now be restricted to only allow Accommodation and Rail deployments to be created.
Multi-type Card Pools will still allow deployments across all use types if required.
A new option in the Communications Hub allows a user to resend a Notification or Payment Message.
Next to each record, a send button is present which asks for a confirmation before resending the selected communication. (Figure 7)
Note. The communication sent will be as per the current deployment state where applicable. If the informality has changed on the original notification, this cannot be reissued.
Links to sections of the website can now be found in a menu drop down list in the navigation bar, where before they were present in the top navigation bar. (Figure 8)
When populating the Supplier Name textbox whilst creating a new deployment, a list of suggested previously used suppliers populates as part of the auto-complete feature. (Figure 9)
This auto-complete functionality has now been enhanced to also fill in a supplier’s address details upon being selected (Figure 10).
Historically when creating a Ground Transportation Deployment, the first line of the Pick-Up and Drop-Off Location has been captured. This has been improved to now capture the full address of both Locations if a user so desires. (Figure 11)
The full address fields are optional, and the original Pick-up Location and Drop-off Location fields will remain mandatory. (Figure 12)
Custom data fields (CDF) have been enhanced to dynamically display during a deployment dependant on the values selected by the deployer. The aim of this enhancement is to improve the quality and accuracy of the data collected in the CDFs, It will also give the ability to control which CDFs are displayed during a deployment as not all CDFs are relevant to every deployer, therefore reducing any confusion and time taken to complete a deployment.
Dynamic CDFs can only be configured for control type drop down list, if an item selected in the list is linked to a CDF, that CDF then becomes visible on the deployment page for the user to complete, until then the CDF will be hidden and not required to be completed. An example of this could be that you may present a CDF called ‘Region’ with following select options ‘North, North West, South’ and upon selecting the option ‘North West’ a CDF called ‘North West Offices’ becomes visible with the options ‘Manchester, Liverpool and Warrington’ and upon selecting ‘Manchester’ the CDF called ‘Line Managers’ becomes visible.
CDFs are still created in the Card Pool Administration section as before, however they can now be amended directly on the table and clicking the save button (Figure 13).
To set up Dynamic CDFs there is a new section in the navigation. In this section users will be able to see all CDFs which are eligible to have a Dynamic links created for them and a preview of the current CDF setup. (Figure 14)
To begin set up, select a value in the relevant drop down e.g. in the ‘Region’ CDF select ‘North West’. This will bring up red arrow button indicating that we can now select which controls to show if this option is selected from the Drop Down (Figure 15).
Using the previous example when selecting ‘North West’ the ‘North West Offices’ CDF needs to display, so I need to check the ‘North West Offices’ CDF in the available CDF table and click save (Figure 16).
Now that the NW Offices CDF is dynamically linked to ‘Region – North West’ it has disappeared in the Preview and upon selecting North West in the Region CDF it will show (Figure 17). Users still have the ability to then link ‘North West Offices’ to other CDFs e.g. ‘NW Line Manager’. Once the CDFs have been configured they will display exactly as per the preview when creating/amending a deployment.
Download the WebPay v2.13 Release Notes by clicking the link at the end of this article.
Download a guide on WebPay CDF Hierarchy Creation at the end of this article.