ONE NETWORK ENTERPRISES
LN 15.0.1 Release Notes
for the
Logistics Network
This document is strictly for Logistics Network Users
Version 1.0
January 13, 2016
Revision History
Version
Release Date
Author
Comments
1.0
1/13/2016
Gary Hahn
Version 1.0 for 15.0.1 Release Notes
Copyright Notice
© 2015 by One Network Enterprises, Inc. All rights reserved.
Printed in the United States of America, 2015.
No part of this document may be reproduced, stored in a retrieval system, or transmitted, in any form or
by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written
permission of One Network Enterprises.
Table of Contents
1 Introduction........................................................................................ 2
2 Bug Fixes ............................................................................................ 3
2.1 Common Network Bug Fixes
3
2.2 Customer-Specific Bug Fixes
17
3 Browser Support ................................................................................. 18
1
LN 15.0.1 Release Notes - Confidential
Version 1.0
1 Introduction
This document contains the release notes for the LN 15.0.1 Patch Release for One Network’s Logistics
Network.
These are the bug fixes that are common for the entire Logistics Network. A JIRA Issue Number is listed
next to each bug fix as a cross reference. Common bug fixes as well as customer-specific bug fixes are
identified in JIRA with the Fix Version of 15.0.1.
If more details are needed on any of the items in this document, please contact the NOC at
[email protected].
2
LN 15.0.1 Release Notes - Confidential
Version 1.0
2 Bug Fixes
2.1 Common Network Bug Fixes
The following is a list of the common bug fixes made as part of the LN 15.0.1 Patch Release:
1) LN-14873
3
The UI is not taking into account the time zone of the Event Date of the
Tracking Event
Problem -
The user was adding a Tracking Event, and in the Event Date field, the user
manually changed the time zone and saved the event. The time on the event did not
show the updated time based on this changed time zone.
Cause –
On the Tracking Event screen, the Event Date field defaults to the current
date/time and displays this date/time in the user's profile time zone. The UI screen
allowed the user to modify the time zone of the event date but when saving, it
reverted and saved it back in the user’s time zone.
Resolution –
A dropdown list will be added in the UI screen for create a tracking event and will
allow the user to select the time zone of the event date. See the screen shot below
for the new time zone dropdown list field. Note - the default time zone displayed will
be the time zone configured in the user’s profile.
LN 15.0.1 Release Notes - Confidential
Version 1.0
2) LN-15254
3)
4)
4
Equipment Number update not showing at the Shipment Level
Problem -
An EDI 214 Tracking Event message was sent to update a Shipment’s Equipment
Number. The update was done at the Movement Level but not at the Shipment Level
as shown on the Shipment Details screen under the Tracking tab.
Cause –
When processing the EDI 214 message sent at the Movement Level, the Equipment
Number provided in the EDI only updated the Movement Level.
Resolution -
Changed the implementation of the EDI 214 processing so when the Equipment
Number is provided for a Movement Level, it will update the Equipment Number for
all the associated Shipments.
LN-16288
PO Date changes are not changing on the Awaiting page
Problem -
The user was changing the Pickup/Delivery dates for Shipments using the Modify
Pickup-Delivery Dates action. The date changes were being changed in the
system when looking at the Shipment Details screen, but these dates were not
being shown on the Awaiting screen.
Cause –
The Planned Dates were getting set on the Shipment which can be viewed by going
to the Shipment Details screen and going to the Schedule tab. Once the Planned
Dates were set on a Shipment, those were the dates that were shown on the
Shipment Summary screen such as the Awaiting screen. The Planned Dates were
getting set when manually consolidating Shipments together on a Movement or when
changing the stop date on the Load Builder screen. Note – Planned Dates were not
getting set when using the Modify Pickup-Delivery Dates action.
Resolution -
The Planned Dates for shipments and movements will not be set under this scenario
to prevent this date display issue on the Shipment Summary screen.
LN-18554
Invoice Lines Summary - Duplicate Movement Numbers and Pro Numbers
Problem -
On the Invoice Lines summary report exported to Excel, it showed a list of duplicate
Movement Numbers and Pro Numbers – duplicates were listed on the invoice line on
the report separated by a comma
Cause –
The Invoice Lines exported summary report contained duplicate Movement Numbers,
Shipment Numbers and PO Numbers in the corresponding column when the invoice
contained multiple lines that were referenced to the same Movement, Shipment and
PO Number.
Resolution –
The Invoice Lines exported summary report will show unique Movement, Shipment
and PO numbers in each invoice and not duplicate values.
LN 15.0.1 Release Notes - Confidential
Version 1.0
5)
6)
7)
8)
5
LN-19015
Problem with the Tender Plan Not Determined Alert
Problem -
User subscribed to the ‘Tender Plan Not Determined’ Shipment Event alert and was
having a problem where they were receiving duplicate alert records in the Alert
Inbox and was displaying alerts for the previous day instead of the current day.
Cause –
The ‘Tender Plan Not Determined’ alert was not being generated on time according
to the threshold value configured on the alert and also duplicate alerts were
incorrectly generated for the same Shipment.
Resolution -
Fixed so the ‘Tender Plan Not Determined’ alert will be generated according to the
threshold value configured on the alert and no duplicate alerts will be generated for
the same Shipment.
LN-19045
The Datawarehouse data field descriptions are not populating any longer
Problem -
User was not seeing the data field descriptions in the datawarehouse specifically for
new tables.
Cause -
Table related column descriptions were not being updated.
Resolution –
This will be fixed as part of 15.0.1 by using a migration script to add descriptions for
the columns in the main datawarehouse tables.
LN-19596
Copy Shipment function is copying equipment info over to new shipment
Problem -
The Equipment Number was being copied to the new shipment as seen on the
Shipment Details screen under the Header tab when the Copy Shipment action
was used. Copy Shipment is an action available on the Shipment Summary
screen at the Shipment Level.
Cause -
The Equipment Number was incorrectly copied to the new Shipment when using the
Copy Shipment action.
Resolution -
Fixed so the Equipment Number will not be copied over to the new Shipment when
using the Copy Shipment action.
LN-19722
Receiving an error when trying to create a Standing Block
Problem –
User was trying to add a recurring Standing Block and was receiving an error about a
conflict but the UI showed no conflict on the day listed.
Cause -
Users accidentally created duplicate, overlapping standing blocks in the system – this
happened because the UI allowed the user to click on the Save button on the Add
Standing Block popup window multiple times when creating a Standing Block.
Resolution -
One Network will clean up and remove the duplicate Standing Blocks in the system
and will also fix the UI to not allow the user to click on the Save button multiple
times before the completion of the first ‘save’ operation when creating or updating a
Standing Block.
LN 15.0.1 Release Notes - Confidential
Version 1.0
9)
LN-19817
Not seeing the Carrier listed in the History of the Shipment again
Problem -
User was not seeing the Carrier listed on the Shipment’s History screen but was
being displayed on the Shipment Summary screen and on the Appointment
Reservation screen.
Cause -
The Carrier was not being listed on the Shipment’s History screen when an offnetwork carrier was specified when scheduling an appointment on a Non-controlled
Shipment.
Resolution -
The logic of populating the Carrier field has been fixed so that the off-network carrier
will show properly on the Shipment’s History screen.
10) LN-19839
Problem -
On the Shipment Summary screen on the State/Status column, it showed
‘Confirmed/Appointment Cancelled’ even though an appointment existed and whose
confirmation number and link was shown under the Delivery column.
Cause -
There was a problem with the code when the user used the ‘Add More’ function on
the Appointment Reservation screen for a Non-controlled Shipment and then
cancelled the appointment. If the user cancelled the appointment and then used the
‘Add More’ function and added the Non-controlled Shipment to another Noncontrolled Shipment and scheduled an appointment or added the Non-controlled
Shipment to another Non-controlled Shipment's existing appointment, the Shipment
Summary screen status showed as ‘Appointment Cancelled’ for the Non-controlled
Shipment.
Resolution -
The logic to update the Shipment status in the described scenario has been fixed and
the Shipment Summary screen will show the correct status which is appointment
scheduled instead of appointment cancelled.
11) LN-19947
6
Shipment stated Appointment Cancelled yet there is an appointment
scheduled
Global Search Box drop down is displaying names incorrectly in Spanish
Problem -
User who had his profile set for Spanish was using the Global Search field and the
drop down list was not displaying the choices correctly in Spanish but everything was
listed as #NAME.
Cause -
The option names for the Global Search field were not internationalized in the
Spanish language bundle messages which are used by the system.
Resolution -
The Global Search field will show Spanish characters instead of #NAME or instead of
English characters when the user’s profile has ‘espanol’ set as the Locale.
LN 15.0.1 Release Notes - Confidential
Version 1.0
12) LN-20100
Problem -
Movements were not rating for rates that had an expiration date on the same day of
the Shipment’s Ship/Delivery Date
Cause -
The Contract End Date was using a time of 12:00:00 AM so the rate was not being
applied when the Ship Date fell on the same date as the end date of the contract
because the system treated the ship date as not within the contract effective date
range.
Resolution -
The Contract End Date will use the time of 11:59:59 PM instead of the time of the
start of the day so that the rate can be properly calculated when the Ship Date falls
on the same date of the Contract End Date.
13) LN-20120
Carriers did not have all the Events in their Alert Subscription drop down
Problem -
When creating an Alert Subscription, Carriers did not have all the same drop-down
options under the Event field under the Alert Filter section as compared to the
Hub.
Cause -
The list of Events for a ‘Shipment Event Alert’ and ‘Movement Event Alert’ Alert Type
available for the Hub/Shipper under Alert Subscription was always different from that
for a Carrier. This was done because what is applicable is different between the Hub
and the Carrier.
Resolution -
Adding Events of ‘Refused by Consignee’, ‘Ready for Pickup’ and ‘Ready for Delivery’
for Carriers for their Shipment Event Alert and Movement Event Alert types.
14) LN-20178
7
Movements not rating with a certain Shipment Ship Date
Supplier Facility showing incorrect address on Shipments
Problem -
On the Shipment Summary screen for the Supplier, on some Shipments, the address
under the Shipper column was not the same address as specified by the Hub when
they created the Partner Site.
Cause -
The Partner Site for a Supplier is created by the Hub/Shipper. When this Partner Site
created, that same site is added under the Supplier Partner company. The Supplier
is able to view and update the site address of the original site. When the Supplier
updated the original site’s address, the updated address did not propagate to the
corresponding Partner Site and therefore, resulted in a different address being
displayed on Shipments using those Partner Sites. On the Shipment Summary
screen and Shipment Details screen, the Partner Site address information is pulled
from the Site under the Supplier Partner Company.
Resolution -
Added logic to prevent the Supplier from updating the Site when it is created by the
Hub/Shipper via the creation of a corresponding Partner Site.
LN 15.0.1 Release Notes - Confidential
Version 1.0
15) LN-20179
Problem -
Under the Message section of the Alert emails received by the user, the time was
being displayed in Eastern Time and not the time specified by the time zone under
the user’s profile.
Cause -
For the ‘Delivered’, ‘Confirmed’, and ‘Accept’ alert Events for the Shipment Event
Alert type and Movement Event Alert type, the date’s time was not formatted
according to the time zone configured in the user profile:
Resolution -
Fixed the Delivered, Confirmed, and Accept alerts for Shipment Event and Movement
Event Alert type to display the time according to the time zone specified on the
user’s profile.
16) LN-20274
For Base Rate function Download CSV for Upload, uploading is not working
Problem -
On the Base Rate Details screen with a rate with Step Rates, when using the
Download CSV For Upload button and then updating that file and uploading it
with the Tools -> Upload -> Base Rate function, the user received a ‘null’ error
message.
Cause -
There was a bug in the logic where the upload failed when the uploaded Base Rate
record contained the Step Min Rate value for a Step Rate but not a Step Max Rate
value.
Resolution -
Base Rate upload has been fixed to allow uploading of records which contain only the
Step Min Rate value for a Step Rate. Upload will also work if only the Step Max Rate
value for a Step rate is provided as well as if both the Mon and Max Rate values are
provided.
17) LN-20553
8
Alerts are not being sent in the time zone of the user. The times in the
alerts are in EDT and not that of the user preference.
Outbound Invoice File for Air Equipment type vs others
Problem -
User created a custom Equipment Type and on the outbound integration file for the
Freight Invoice, it listed the name of the Enterprise before the name of the
Equipment Type. When using standard Equipment Types, it was fine and did not
show the Enterprise name.
Cause -
When using a custom Equipment Type, the system was adding a prefix on the
Equipment Type in the outbound invoice integration message with the Enterprise
name.
Resolution -
The prefix of the Enterprise name for custom Equipment Types has been removed in
the outbound Freight Invoice Notification message.
LN 15.0.1 Release Notes - Confidential
Version 1.0
18) LN-20555
Problem -
On the Shipment Summary screen, the user was confused with the status
displayed under the State/Status column showing ‘No Carrier Commitments
available’ and what it indicated and how the system generated that status.
Cause -
This was due to a bug that occurred whenever the user tried to accept a Tender
having an invalid Carrier Commitment Tier. The system would cancel the Tender Plan
and due to this bug, the Shipment status would change to ‘No Carrier commitment
available’.
Resolution –
The logic has been fixed so in the case of an invalid Carrier Commitment scenario,
the Shipment State/Status will show as ‘Awaiting/Cancelled by Shipper’.
19) LN-20644
Problem with the Duplicate Line function
Problem -
On the Shipment Details screen on the Content tab, when adding a new
Shipment Line or deleting an existing Shipment Line, the No of Packages field at
the Shipment Header is not re-computing. This field computes correctly when the
Shipment and lines are first created - but they are not re-computing when Shipment
Lines are added or deleted and then a Save operation is done on the Shipment. Note
– this was not a problem related to the Duplicate Line functionality.
Cause -
There was a bug in the logic of adding/deleting a Shipment Line where the ‘No of
Packages’ value was not being propagated to the Shipment header level on the
Content tab.
Resolution -
Fixed the issue so the ‘No of Packages’ value will propagate to the Shipment header
level.
20) LN-20750
9
Confusion over a status "No Carrier Commitments available" being
displayed in the Status column
Invoices in For Review with No Holds
Problem -
User wanted to set the Currency UOM field on the Carrier’s Invoicing Policy
screen to blank to support multiple currencies, but the system would not save this
value as a blank.
Cause -
The system was not supporting saving a blank value in the Currency UOM field on
the Carrier’s Invoicing Policy screen.
Resolution -
The system will allow the Currency UOM field on the Carrier Invoicing Policy screen
to be blank and to be saved as blank. When the Currency UOM field is blank, a
hold will be created if the amounts on the Invoice and Movement violate the
Invoicing Policy tolerances as long as the currency on the Movement Cost matches
the currency on the Invoice.
LN 15.0.1 Release Notes - Confidential
Version 1.0
21) LN-20926
10
No Tendered Notification for Spot Tender
Problem -
User was expecting the Carrier to receive an alert when the Hub accepted or rejected
a Carrier’s Spot Tender Cost on the Shipment Tender Plan screen – the cost is
submitted by the Carrier using the Conditionally Accept action.
Cause -
There was no alert available for Carriers to subscribe to in order to receive an alert
when the Hub/Shipper accepted or rejected a Spot Tender.
Resolution –
Carrier can create an alert subscription for a Shipment Event Alert Alert Type for
Event = Accept or Reject and check the flag named ‘Spot Bid’. An alert will then
be generated accordingly when the Hub/Shipper accepts or rejects the Carrier’s Spot
Tender Cost. See the example screenshot below:
LN 15.0.1 Release Notes - Confidential
Version 1.0
22) LN-20994
Carrier was not able to see the Accesorials on an Invoice
Problem -
Carrier user received a permission error when trying to view the Accessorial Detail
screen from the Invoice Creation. Hub expected the Carrier to be able to view it but
not to be able to perform any updates.
Cause -
Carrier user could view the list of Accessorials but they did not have permission to
view the details of Accessorials created by the Hub/Shipper.
Resolution -
In the list report of Accessorials viewed when creating an Invoice Line, the screen
will show the Description ad Type of the Accessorial. See the screenshot below.
Note: the Carrier user will not be able to click on the hyperlink to open a screen to
view the details of the Accessorial.
11
LN 15.0.1 Release Notes - Confidential
Version 1.0
23) LN-21061
Problem -
User created a Movement with two Shipments and saved the Movement to the
Confirmed state. The Movement Tracking screen showed an entry for Type =
Confirmed. User added a Received tracking event to one of the Shipments and then
cancelled or removed the other Shipment from the Movement. The Movement’s state
showed as Delivered on the Shipment Summary screen but the Movement
Tracking screen did not update and show an entry for Delivered.
Cause -
There was a bug in the logic where the Movement Tracking screen did not reflect
the state change when a Shipment was removed from the Movement.
Resolution -
When a Movement contains multiple Shipments and when a Shipment is removed
from the Movement, the Movement Tracking screen will reflect any necessary
state change and show the corresponding event. For example, if a Movement
contains two Shipments and one of them is in the In-transit state and the other is in
the Delivered state, removing the In-transit Shipment will change the state of the
Movement to Delivered and the Movement Tracking screen will now reflect the
Delivered event.
24) LN-21247
Unable to remove Equipment Number from Shipment header
Problem -
User tried to delete the Equipment Number displayed in the Equipment No field on
the Shipment Details screen under the Header tab – after deleting and
performing a Save operation, the Equipment Number was displayed again.
Cause -
The UI Shipment Details screen did not remove the Equipment Number when the
user removed it while updating the Shipment.
Resolution -
The UI Shipment Details screen logic has been fixed to properly remove the
Equipment Number when removed during a shipment update.
25) LN-21355
12
Movement Tracking screen not showing tracking update information
correctly
EDI 997 message issue
Problem -
User was not able to process the EDI 997 Failure message EDI 997 message (EDI
997 is a Functional Acknowledgement message) due to the count in the
SE01 segment. Note – an EDI 997 Success or Failure message is sent in regards to
ONE processing an EDI 210 message (EDI is an Invoice message).
Cause -
When a 210 EDI file contained a mix of good and bad records in terms of syntax
errors when missing the element of B.LX.L102 and L103 in the segment of B.LX.L1,
the EDI 997 response generated was missing the AK1 segment which caused the
issue with the count in the SE01 segment.
Resolution -
This has been fixed so the EDI 997 generated for an EDI 210 will contain the AK1
segment and regardless of any syntax errors received in the EDI 210.
LN 15.0.1 Release Notes - Confidential
Version 1.0
26) LN-21423
Problem -
On the Create Live Delivery Appointment screen, a Vendor user was able to go
to the Shipments tab and modify the date in the Target Delivery Date field and
then return to the Reservation tab and see appointment times that were outside of
the Hub-defined Auto Date Tolerance.
Cause -
The Vendor was able to modify the Target Delivery Date on the Shipments tab on
the Appointment Reservation screen and when the system then showed
appointment times based on that date, the system did not show any type of error
about the appointment time being outside of date tolerance.
Resolution -
On the Scheduling Policies screen when selecting the Enterprise name at the top
of the tree in the Explorer window, under the Basic Policies tab, there is a flag
named ‘Allow Trading partners to change Target Appointment Date’. When
this flag is unchecked, Vendor users will not be allowed to change the Target
Delivery Date on the Shipments tab on the Appointment Reservation screen.
Vendor users will be allowed to change the Target Delivery Date when this flag is
checked.
27) LN-21460
Unable to create alert for a Delivered Movement when one of the Event
Type entries is "inactive" even it has another one active
Problem -
On the Tracking Event Policies screen available by navigating to Transportation > Policies -> Tracking Event Polices, if an Event Type has entries for different Target
Groups, when one event was set to inactive, the Event Type was not available under
the Event drop down list on the Alert Subscriptions screen.
Cause -
In the Tracking Event Policies screen, if an event is configured twice for Target
Groups of ‘All’ and ‘My Organization’, and when the ‘My Organization’ configuration is
set to be inactive, the logic to determine what Event Type is available only
considered this inactive setting and made the Event Type not available for Alert
Subscriptions.
Resolution -
Event Types will be available for Alert Subscriptions to users when there is one
configuration in the Tracking Event Policies screen set to active for the applicable
Target Group for the user.
28) LN-21482
13
Scheduling Issue With Date Ranges
Outstanding Order Quantity not adding correctly
Problem -
On the Search Order Summary screen displayed when navigating to Order Mgmt > Search Order and performing an order search, the value displayed under the
Outstanding Quantity column did not add up to the quantity amount left on the
Order based on the Shipments created against the Order.
Cause -
A race condition occurred when multiple users selected the checkbox by the Order
and selected the Create Shipment action at the same time. Because of this race
condition, the updated value for the Outstanding Quantity on the Order was
overridden by one of the users.
Resolution -
The way the system updates the Outstanding Quantity for an Order when using the
Create Shipment action from an Order has been changed to avoid the race
condition when multiple users create shipments from the same order using this
action.
LN 15.0.1 Release Notes - Confidential
Version 1.0
29) LN-21576
Problem -
On the Scheduling Policies screen displayed when selecting a Dock Door Group
under the Explorer window, on the Basic Policies tab, there is a policy named
Restrict Candidate Search When Available. Selecting the checkbox for this
policy did not do anything on the Appointment Reservation screen.
Cause -
The Restrict Candidate Search When Available policy was an old policy and no
longer had any logic associated with it.
Resolution -
Removed the Restrict Candidate Search When Available policy from the
Scheduling Policies screen for a Dock Door Group.
30) LN-21666
Update the Carrier on the Awaiting Report to match the first Carrier with
Capacity
Problem -
On the Awaiting screen under the Carrier column, the first Carrier listed on the
Tender Plan is displayed under the Carrier column even if that Carrier has no
remaining capacity when utilizing the Carrier Commitment functionality.
Cause -
When the Ranking Types of a Tender Plan are ‘Least Cost’ or ‘Carrier Priority’, the
Carrier list was not getting sorted according to any “capacity warning or no
commitment available”.
Resolution –
If the Tender Plan is using “Least Cost” or “Carrier Priority” as the Ranking Type, the
Carrier list will be sorted according to “capacity warnings” on the tender. For
example, a Carrier which has the “No commitment or capacity available” warning will
be in the last position on Tender Plan. Please note that this sorting strategy won’t
apply to Tender Plans where the strategy is Rotational Allocation.
31) LN-21679
14
The Restrict Candidate Search When Available policy does not do anything
EDI 204 problem
Problem -
User reported a problem with the EDI 204 message they received and stated there
were too many characters being sent in the N301 field/segment.
Cause -
In the logic of generating the EDI 204 message, One Network did not limit the
number of characters in the N3 element and took the full length of the full address of
the site including the site name.
Resolution -
When the full address of the site exceeds the length of 55 characters, it will be
truncated to 55 characters when populated in the N3 element in the generation of
the EDI 204 message.
LN 15.0.1 Release Notes - Confidential
Version 1.0
32) LN-21710
Problem -
User was updating the dates for a Shipment using the Modify Dates PickupDelivery action and on the popup under the Reason Code column, only some of
the available reason codes were displayed.
Cause -
There was a bug in the logic to retrieve the list of reason codes for the Modify
Pickup-Delivery Dates popup window that caused some reason codes to not be
displayed.
Resolution -
This has been fixed so all reason codes listed under Shipment Change Reason
Codes which are configured under Tools -> Dynamic Enumerations will be displayed
on the Modify Pickup-Delivery Dates popup window.
33) LN-21852
Receiving system error when clicking into the costs or shipments
Problem -
User received an error when clicking the Cost hyperlink to view the Cost Details
screen on a specific Shipment as well as when clicking the Shipment Number
hyperlink on a specific Shipment to view the Shipment Details screen on the
Shipment Summary screen.
Cause -
There was a bug in the logic of getting the Shipment details and an error occurred
when the user did not have defined a default Shipment Template or the default
Shipment Template did not have the Ship From address/site field populated.
Resolution -
Issue has been fixed so user should not have a problem accessing the Shipment
Details screen for a Shipment even if they do not have a default Shipment Template
or a default Shipment Template without the Ship From address/site populated.
34) LN-22209
Favorites drop down is not in alphabetical order but viewing selections
under Manage Favorites is
Problem -
When selecting the Favorites icon on the top left of the main screen (i.e. Star icon),
the list of Favorites is not displayed in alphabetical order.
Cause -
The system did not enforce and list the Favorites in alphabetical order.
Resolution -
This has been fixed so the Favorites will be listed in alphabetical order.
35) LN-22595
15
Reason Codes Missing in Modify Pickup-Delivery Dates Field
Name change of Ent Role Types won't save
Problem -
User wanted to change the name of an Ent Role Type and navigated to
Administration -> Ent Role Types and selected the name link for one of the Ent Role
Types in the Explorer window and on the Ent Role Type screen under the Info tab,
the user changed the name under the Name field and performed a Save operation
but the change did not take effect.
Cause -
There was a bug in the logic to change the name of an Ent Role Type that made the
name change update unsuccessful.
Resolution -
This has been fixed so the user will be able to change the name of an Ent Role Type
via the UI.
LN 15.0.1 Release Notes - Confidential
Version 1.0
36) LN-22686
16
Problem creating a Standing Block
Problem -
User was creating a Standing Block and received an error message about a conflict
with an existing block on a specified day but that conflict block did not show in the
UI.
Cause -
There was a bug in the logic of finding the conflicting appointments with the newly
added standing block. It did not take the correct adjustment on daylight savings
time. For example, if there was an appointment on 1/1/15 from 10:30 AM to 11:30
AM and the user tried to create a Standing Block on 1/1/15 from 9:00 AM to 10:00
AM, the creation of the Standing Block failed because the time of the existing
appointment was wrongly adjusted to 9:30 AM to 10:30 AM and therefore was being
treated as a conflict.
Resolution -
The bug in the logic of finding conflicting appointment has been fixed to adjust the
time correctly according to daylight saving time conversion. Standing Blocks should
be created successfully in the scenario described above.
LN 15.0.1 Release Notes - Confidential
Version 1.0
2.2 Customer-Specific Bug Fixes
The following is the list of JIRA Issue Numbers for the customer-specific bug fixes included in the LN
15.0.1 Patch Release:
17

LN-16986

LN-20857
LN 15.0.1 Release Notes - Confidential
Version 1.0
3 Browser Support
For each software release, One Network recommends a specific version of Internet Explorer (IE) to use
with the system. Using the recommended version of IE helps maximize the performance of the system
by taking advantage of the continued improvements available in the latest releases of IE. One Network
supports the recommended IE version and up to two previous versions of IE depending on if they are still
supported by Microsoft.
For the 15.0.1 Release, we are strongly recommending for users to use IE version 11. We will still
support IE 10 and IE 9, but system performance will be degraded as compared to IE 11.
18
LN 15.0.1 Release Notes - Confidential
Version 1.0