Advertisement
Closed defect summary
Names fix duplicates produces an empty error
nl
message.
Symptom—This happens when the newly edited Name
matches another Name (when Names are set to be
unique), or when an invalid name is detected (such
as an @ in a FOS port name.
When editing names, edit device tree name and
nl
collapse item, the edited name gets moved to a new
cell.
Symptom—Could accidentally assign a name to the
wrong device, if they collapse the tree before selecting
another cell or pressing return.
Duplicated Names dialog help does not launch.
Symptom—Cannot open help from this dialog to get
details on its functionality.
Event policy help does not launch; invalid ID -- DCFM
Enterprise.
Symptom—Help will not launch for this dialog.
Event policy Count implemented incorrect; it cannot
start with '1'.
Symptom—The valid range for a count is 2–999.
Currently values cannot start with a 1 which makes
10–19 and 100–199 invalid values.
Getting login failure for a remote client through a
firewall that has the required ports open as per FS.
Symptom—Getting login failure for a remote client
through a firewall that has the following ports open
as per FS:
80, 24600-24606, 24607-24613 (enabled
or disabled) 1527 (enabled or disabled),
2638 (enabled or disabled), and 20
(enabled or disabled)
Master log online help documents wrong location for
log events.
Symptom—Misinformed about the location of events.
On-Line Help "Windows systems" refers to applications
we do not support for migration.
Symptom—Help is incorrect.
Online Help post-installation requirements refers to
EFCM locations and files.
Symptom—Help is incorrect.
20
Solution
Fixed in DCFM 10.1.0
Workaround—Find the Name in the product tree and
fix it there, or allow the application to fix it for you
Fixed in DCFM 10.1.0
Workaround—Always press return after typing the
name into a cell.
Fixed in DCFM 10.1.0
Workaround—Open Help form the title bar and
navigate to the Names help section.
Fixed in DCFM 10.1.0
Workaround—Open help from the main toolbar and
navigate to the correct section.
Fixed in DCFM 10.1.0
Workaround—Use 2–9, 20–99, 200–999 for the
count.
Fixed in DCFM 10.1.0
Fixed in DCFM 10.1.0
Workaround—The older events are written to
install directoryjboss\server\dcm\
databackup in a folder named events.
Fixed in DCFM 10.1.0
Fixed in DCFM 10.1.0
Advertisement
