High-Level Overview of Bugs and Enhancements Now Available in Swift
Release: 1.23.0
The descriptions below are now available in Swift as April 2025.
🐞 Bug Fixes: Three (3)
-
- Shipping > Monthly Nominations: One (1)
- Loading > Customer Authorizations: One (1)
- Loading > Carrier Authorizations: One (1)
📣 Customer-Requested & Usability Enhancements: Three (3)
-
- General: One (1)
- Loading > Customer Authorization: Two (2)
📣 NEXT RELEASE: NO MORE 'EMPTY CACHE AND HARD RELOAD!' 📣
This is the last release you will need Empty Cache & Hard Reload. This final refresh will upgrade you to enjoy this milestone with us! After Swift Version 1.23.0, users no longer have to manually 'Empty Cache and Hard Reload.'
What does this mean?
- Going forward after the 1.23.0 release, when a new version of Swift is available, users will see a pop-up notifying them.
- One click is required: click the Upgrade Now.
- Your active screen will refresh.
Things to Note
- The pop-up will show on any screen within Swift; users do not have to be on the Home screen. This will occur if the user is in Swift as a Swift release is pushed to your environment.
- Persistent filters will hold; users will not lose saved filters upon refresh.
- A screen refresh is the user's visual notification that a Swift version upgrade or product release happened.
- If a user hits Close (to opt out of the upgrade), the pop-up will return in five minutes. Go ahead and upgrade.
- Suppose a user leaves their session or logs out. In that case, the next login will automatically apply the updated Swift version without the user having to select Upgrade Now.
THREE BUG FIXES
Shipping > Monthly Nominations
One Bug Fix
A user can now successfully accept their open, Awarded nomination; it no longer automatically goes to the Rejected tab within Swift Monthly Nominations. When a user edits, approves, and saves their Awarded nomination, the submission stays on the Accepted tab.
Loading > Carrier Authorizations
One Bug Fix
Users can now successfully proceed past Step Three in the Create + New Authorization workflow. Previously, the Continue button remained grey, and users cannot move forward.
-
- This was the step where users restricted specific carriers being set up and their ability to load associated with this Authorization.
- This was the step where users restricted specific carriers being set up and their ability to load associated with this Authorization.
Loading > Customer Authorizations
One Bug Fix
Users can now successfully create and submit a semi-monthly Customer Authorization without errors. This is for creating or editing a Product-Specific Authorization to be Semi-Monthly.
Now in Swift! Three Enhancements
General
One Enhancement
The Swift version automatically refreshes the user's browsing session. Users no longer have to manually Empty the Cache and hard Refresh. See the orange section above for details.
Loading > Customer Authorizations (Two Enhancements)
ONE
When a user tries to reactivate an inactive Authorization with a leading 0 in the ID, the Authorization fails to become inactive, and the user receives a generalized error pop-up message.- A user can create a new Customer ID with a zero but cannot reactivate it if that ID moves to an Inactive status.
The enhancement? Swift is working toward better error messaging detail feedback and insight for users within Swift.
- Within the Customer Authorization screens, users will now see an Error message pop up communicating the behavior causing the error. Previously, the user was only provided with a vague error message with no details.
TWO
Customer Authorizations will now only allow and display active ONEOK Refined Terminal locations in the Authorization.
- Previously, the search filters were incorrect if a Customer Authorization had an inactive location point.
- If an Authorization has an inactive terminal, the Customer Authorization remains active, but the inactive terminal is removed.