Kbase P80071: Dynamics 2.1A Service Pack 2 release notes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/11/2004 |
|
Status: Verified
GOAL:
Dynamics 2.1A Service Pack 2 release notes
GOAL:
Release notes for Dynamics 2.1A02
FIX:
RELEASE NOTES AND INSTALLATION INSTRUCTIONS
for Windows NT 32 Intel PROGRESS Dynamics (TM) Service Pack 2.1A02
** Please make sure you shut down any instances of PROGRESS and Dynamics
that you have running before installing this Service Pack. If you do
not, you may receive messages indicating that some files could not be
copied on top of other files (because they are locked\in use by
another process).
SYSTEM INFORMATION:
Platform: Windows NT 32 Intel
Serial Code(s): 146 (CD-ROM)
Service Pack Version: 2.1A02
SOFTWARE NOTES:
===============
Progress Dynamics New Features
------------------------------
1. Extending Object Classes
Currently customers who customize the Dynamics class structure need
to reapply their class customizations with each Dynamics release
because the upgrade process resets the class structure to the
standard Dynamics structure. With this release, the class structure
and class customization procedure has been changed to eliminate the
requirement to reapply class customizations in future releases.
The new support for class customization is documented in the Extending
Object Classes in Progress Dynamics available on PSDN. Once class
customizations have been applied according to the directions in that
whitepaper, they will be preserved across future versions of Dynamics.
2. Print Preview to XML or HTML
The Print Preview tool on the browse toolbar now additionally supports
viewing the Print Preview in XML and HTML. XML and HTML previews will
be displayed in the user´s default browser.
Print preview also continues to support viewing with version 8 of
Crystal. Due to packaging changes in later versions of Crystal, the
print preview is not currently integrated with Crystal version 9 and
later. The print preview to XML can be used to generate xml data for
later versions of Crystal.
Configuring the format for print preview:
The print preview format is set for a session. There are two session
properties that can be configured for each of the applicable
session-types in order to select the format of the print preview.
These properties should be set by using the Session Type Control from
the Dynamics Administration Tool. The properties are:
a. The "print_preview_preference" property sets the format for print
preview to use. The value of this property can be "Crystal", "XML"
or "HTML". The default print_preview_preference is XML, and it
will also revert to XML if Crystal is selected but cannot be found.
b. The "print_preview_stylesheet" identifies the style sheet to use
for the XML and HTML options. The value of this property is the
style sheet pathname. Default style sheets are provided for XML
and HTML in the following paths:
- XML style sheet - src\dynamics\af\rep\xmlreport.xsl
- HTML style sheet - src\dynamics\af\rep\htmlreport.css
If you set Crystal as the preview preference, you should still specify
the XML style sheet in case Crystal cannot be found and the preview
defaults to XML.
Please note that for Dynamics Web the only available option is HTML,
and the associated stylesheet is relative to the web-server path
("..\dhtml\webreport.css").
3. Dataset Import\Export Tool performance improvements (Bug Number
20020923-042)
Several changes have been made to the dataset import and export APIs to
improve performance. Amongst the changes are pooling of objects and the
reduction in the amount of XML that has to be read and written. Most of
the performance benefit i.s seen without any special action being taken.
Reducing the amount of XML to be written involved changing the behavior
of the API so that full dataset headers are not written into the XML file
as this information is not used. To realize the full performance benefit
associated with the reduction in size of the XML file, it is necessary
for users to re-dump all their ADOs. Removing the header information from
the ADO reduces Source Code Managed dataset sizes significantly and means
that less data is both read from and written to the ADO file. Obviously,
removing the header information from the ADOs requires re-dumping them.
===========================================================================
Progress Dynamics Release Notes
-------------------------------
1. Session must be restarted after changing security settings (Bug Number
00011505-000)
If security settings are changed in a Dynamics session, the session
must be restarted before those settings are available for the client
session.
2. Global field translations do not work for dynamic viewers (Bug Number
00012570-000)
3. Clearing the repository object cache before instantiating all pages
causes problems (Bug Number 00013087-000)
Clearing the repository object cache prior to instantiating secondary
pages of a container causes problems. If the objects on secondary pages
have not yet been instantiated, the rendering engine attempts to
retrieve the objects from the cache and fails with errors. In addition
the client session may hang.
4. Table-IO links are not created as pass-through links with dynamic
frames (Bug Number 00013667-000)
Table-IO links are not created as pass-through links with dynamic
frames. This results in errors when a records is being updated (add,
copy, cancel, save etc).
5. Dynamics uses ry\clc install directory if "client_cache_directory" is
not defined (Bug Number 00013796-000)
If the "client_cache_directory" is not defined, Dynamics will
automatically pick up what has been previously dumped into the ry\clc
path in the Dynamics installation directory. The users should be
careful about this situation if they are developing multiple
applications with tables with same names.
6. If auto_dump_entity_cache is set to NO, entity cache is still used
(Bug Number 00013797-000)
If the development session and the runtime session point to the same
location for the entity cache, even if the auto_dump_entity_cache is set
to NO in the development session, if there is an entity cache then it
will pick-up the entity cache. The auto_dump_entity_cache is for
dumping the cache not for indicating if the cache should be used (if
found).
7. Window size profile data is saved against the container name only (Bug
Number 00013798-000)
Dynamics currently saves window size profile data against the container
name only. Different run attributes result in separate menu entries;
currently all containers with the same name and different run attributes
share one set of profile data so that the saved size used is the size of
the last one closed.
8. Appserver hit for each SDO calculated field. (Bug Number 00013827-000)
An SDO that is started with OpenOnInit false will have an Appserver hits
for each calculated field. This can be avoided by setting the SDO´s
SchemaLocation attribute to ´DLP´. This directs the SDO to retrieve its
field definitions from the Data Logic Procedure, so this has to be
deployed on the client and need to be recompiled to get changes.
9. Super procedures running STATELESS (Bug Number 00013882-000)
When retrieving. an object using the getInstanceProperties() API, unless
the value of the SuperProcedureMode attribute is explicitly set against
an object, the class value of ´Stateless´ will be returned, even though
the default behavior is ´Stateful´. This differs from the way that the
prepareInstance() API handles the SuperProcedureMode attribute and can
result in inconsistent behavior when starting an object using
constructObject or manually starting an object.
10. Object Generator fails to create dynamic SDOs with deep joins (Bug
Number 00013912-000)
The Object Generator fails to create dynamic SDOs if a deep join is
selected. This is because the SDO include file is not created because of
error 560.
11. fullocreat.p is obsolete (Bug Number 00013974-000)
fullocreat.p is obselete in Dynamics post Dynamics version 1.1. This file
contains the Dynamics Version 1.1 Object Generator business logic. It was
replaced in the Dynamics 2.x family and is now obsolete.
12. Class cache fields must be generated with American or European numeric
formats (Bug Number 00013975-000)
The generateClassCache() API in the repository manager does not cater for
all numeric formats correctly - it only handles AMERICAN and EUROPEAN
formats. When generating class cache files, the client session should
use one of these. The API that does the runtime reading of these files
can handle any numeric format.
13. Browse column labels come from database schema with static objects (Bug
Number 20030404-030)
Browsers running in static windows linked to a static SDO on an AppServer
will not get the column-label from the Repository´s EntityField, but from
the database schema. This problem also applies to any static browser.
14. The client cache viewer returns errors on startup and doesn´t show any
data.(Bug Number 20031106-086)
15. Folder pages are initialized in alphabetic order of contained GA target
viewers. (Bug Number: 20031201-006)
Tab folder pages of a dynamic container initialize in alphabetic order of
contained Group Assign target linked viewers (i.e. the GA source page is
initialized last).
16. GroupAssign target viewer does not blank lookups when no record is
available (Bug Number 20031203-032)
A GroupAssign-target viewer does not blank Lookups when no record is
available, the last displayed values remains on the screen.
17. Help cannot be mapped to dynamic lookups and dynamic combos (Bug Number
20040204-002)
Context help cannot be mapped to dynamic lookup and dynamic combo objects.
18. MigrateEntityFieldstoDataFields should run only once (Bug Number
20040206-001)
The migration program MigrateEntityFieldstoDataFields.p is designed to be
run once only; it should only be run when upgrading to Dynamics version
2.0A02 and should not be run subsequently or be re-run.
19. Static Object Deployment missing some files for thin client mode (Bug
Number 20040212-019)
The following files are not included in the static object deployment for
thin client, which may cause problems for the "Security Control" window
from the Admin menu. In order to prevent these problems, simply copy the
files below from the gui directory into your deployment package directory,
making sure the directory structure is kept.
af\obj2\grpusrsupr.r
af\obj2\usrgrpviwvsupr.r
af\obj2\grpcomsupr.r
af\obj2\gsmussupr1.r
af\obj2\secacselbvsupr.r
af\obj2\sectpviewvsupr.r
af\obj2\secfiltervsupr.r
af\obj2\gscsclogcp_cl.r
af\obj2\gsmtologcp_cl.r
af\obj2\gsmsslogcp_cl.r
af\obj2\gsmfflogcp_cl.r
af\obj2\gsmlglogcp_cl.r
af\obj2\gsm.ralogcp_cl.r
20. ObjectBands defined with a RunAttribute are always added to object (Bug
Number 20040212-034)
ObjectBands are not filtered properly on RunAttribute. The Bands will
show up on the first launch of a container also when RunAttribute is not
specified.
21. BlankWidget for DynLookup causes an Appserver hit (Bug Number
20040217-041)
Calling BlankWidget in a DynLookup causes an Appserver hit as the Lookup
class currently assumes that blank is a valid key value.
22. Appserver hits on initialization of viewer for lookup and combo when data
source OpenOnInit is false (Bug Number 20040217-042)
The viewer causes Appserver hits on initialization to retrieve lookup and
combo information even when OpenOnInit is set to false in the viewer´s
data-source.
23. Data container context may exceeds 32K limit (Bug Number 20040407-006)
An Appserver-aware Container may sometimes fail to complete an Appserver
request with the error ´** Replace/Concat may not result in data > 32000
bytes´. This can happen when the container has a large number (usually 10 or
more) of dynamic SmartDataObject instances. The number of SDOs that would
cause this issue depends on the application. Using Dynamic SDOs will reach the
32k limit faster. Dynamic Treeview containers with structured data nodes could
reach this limit as nodes are being expanded within a branch.
24. Treeview private API modifications (Bug Number 20040113-032)
Resolution of issues with submenus failing to display in treeview menus
required several changes to private APIs. Private APIs should not be used by
Dynamics applications because they are subject to change. The modifications
to the APIs include the following:
1) A parameter was added to the internal procedure, extractMenuItems, in
ry/app/rytreemenp.p. The new parameter carries the value of the current menu
level being processed so that multi-level menus can be processed recursively.
2) The internal procedure, stripMNUDetails, has been removed from
adm/tvcontnr.p as it had no value and cannot operate on the current recursive
structure of returned menu details.
===========================================================================
Progress Dynamics - SCM Integration
-----------------------------------
1. Cannot reopen object after modifying with auto check out (Bug Number
00013053-000)
When an object that was checked in is opened with auto check out, then
modified and saved again, the object remains marked as ´Checked In´, and
subsequent attempts to open the object produce the following error:
"** "00060001" was not found. (293)"
A workaround is to select Workspace = None, then reselect the development
workspace. The object will show the correct status of ´Checked Out´.
2. adecomm\tt-brws.i not found compile errors (Bug Number 00013859-000)
Compilation of rysdfcombv.w or rysdflkupv.w may result in the following
error: "** "adecomm\tt-brws.i" was not found. (293)"
This happens because the adecomm\tt-brws.i include file is distributed
in a procedure library (src\adecomm.pl) and it is not used when compiling
programs.
To prevent this compilation error, extract the file tt-brws.i
(path: adecomm\) from the RTB Partner-Site Full Package rtb_100000.zip
into the OpenEdge-Install>\src directory.
3. SCM Install and Setup documentation misleading (Bug Number 20040204-028)
The. PSDN document "Progress Dynamics Version 2.1 Source Code Management:
Roundtable TSMS Installation and Setup" contains screenshots showing path
and PROPATH names that are confusing for customers. References to the
installed Dynamics path should use the default installation path, without
any modifications that suggests a particular release of the product.
For the 2.xx branch that would be: "C:\Program File\Progress Dynamics"
For the OpenEdge 10.xx branch that would be: "C:\Progress\OpenEdge"
4. SCM Install and Setup documentation missing deployment instructions (Bug
Number 20040204-030)
The PSDN document "Progress Dynamics Version 2.1 Source Code Management:
Roundtable TSMS Installation and Setup" does not contain instructions for
deploying Dynamics Products and Modules, new Object Types (Classes) or SCM
Xref records between Roundtable workspaces. The Roundtable integration
code does not manage these 3 types of data. When an application is
deployed from a workspace or imported into another workspace, they have to
be exported and imported manually in order for the application to be
complete and to function properly. The three types of data are deployed
in the datasets GSCPR, GSCOT and GSCSM.
5. SCM Install and Setup documentation missing directory from workspace
paths (Bug Number 20040205-007)
The PSDN document "Progress Dynamics Version 2.1 Source Code Management:
Roundtable TSMS Installation and Setup" needs to have the directory
src\wrappers added in all places where it specifies workspace paths.
The include files in src\wrappers are needed in order for some of the
Dynamics code to compile.
The workspace path would look like:
-
- \src\dynamics
- \src\dynamics\af\sup2
- \
- \src\dynamics\scm
- \src\dynamics\scm\custom\rtb
- \src\dynamics\scm\custom
- \src
- \src\wrappers
6. SCM Install and Setup documentation pre-assign workspace files are in
the wrong order (Bug Number 20040205-008)
The PSDN document "Progress Dynamics Version 2.1 Source Code Management:
Roundtable TSMS Installation and Setup" section 3.4 describes how to
update workspaces with newer releases of Dynamics. A part of this process
is to pre-assign some files to the workspace that is being updated before
doing a complete import from the source workspace.
Page 81 has a list of the files that need to be pre-assigned. The list
contains include files and procedure files. The list currently does not
show the files in the correct order. The include files should be shown at
the top of the list to ensure that there are no compilation errors when
the procedures are assigned.
===========================================================================
ISSUES ADDRESSED IN THIS SERVICE PACK:
Issue # Component Description
------------ ---------- -------------------------------------------------------
20040209-022 DEPLOYMT There is a problem with DynLookups on the Web when
using a database that had prior migration issues and
the dynLookup´s "fieldname" attribute was not being
populated. Lookups are left in an ´undefined´ state.
00013884-000 DEPLOYMT DCU Error 76 loading RYCAT.ADO
20040220-002 GUIRENDR The containedProperties function in a Dynamics TreeView
is called many times when selecting a node.
20040219-019 GUIRENDR Exceeding 32K character limit when runnin.g a Treeview
container with data-driven nodes (SDO) over a
stateless Appserver
20040219-005 GUIRENDR Selecting a Treeview node may cause ´OpenQuery´ to be
called more than once.
20040210-007 GUIRENDR Error message about invalid use of ADD/SET-BUFFERs when
running a SBO with SDOs that have joins on an
AppServer.
20040203-002 GUIRENDR When using the static SDV with the translated labels
for the dynlookup, the fill-in widget of the dynlookup
is much wider than the original non-translated version
therefore distorting the screen layout.
20040129-026 GUIRENDR Mandatory field errors are not trapped properly after
the data object code was changed to be dynamic.
20040128-022 GUIRENDR Adm property records are not deleted for toolbars when
the Dynamics container is closed.
20040123-009 GUIRENDR It is not possible to change the font of a dynamic
browser column.
20040121-019 GUIRENDR Static SDOs have the DestroyStateless property set to
FALSE by default. This is not supported for SDOs in
static containers. It causes the SDOs to remain alive
until the AppServer broker is restarted.
20040119-003 GUIRENDR dynCombos with parent fields looses information when
another container with dynCombos with parent fields are
opened. The problem is typically seen when trying to
select items in the first created combo as the
list-items is empty and the screen-value becomes blank.
20040113-032 GUIRENDR When using treeview nodes to represent menus using the
structured menu node type, only the top level and its
submenus are represented. Further submenus are not
rendered.
20031210-008 GUIRENDR ttAction already exists message when running toolbars
where toolbarcustom has been customized to add actions.
20031205-012 GUIRENDR When AutoSort is FALSE, text nodes are sorted on
gsm_node.node_obj rather than on their code/label.
20031113-007 GUIRENDR Screen values of smartBrowse columns that contain
prepended spaces are trimmed when the record is
highlighted showing the visible character data to the
far left of the browse cell.
20031020-049 GUIRENDR FindRowWhere will always retrieve data from the server
for SDOs that have a joined query even if the requested
record already exists on the client and doesn´t need to
be retrieved.
20030925-031 GUIRENDR Editor widgets on dynamics viewers are not sensitive
upon initialization when the toolbar linked to the
viewer with a tableio link is set to update
TableioType.
20030723-022 GUIRENDR It is not possible to set focus in TAB, LEAVE event
procedure on a dynamic viewer, due to the fact there is
no way to interrupt the current event.
20030630-006 GUIRENDR The container´s viewObject sets window-state to
window-normal for minimized windows, making it
impossible to minimize windows before super in
initializeObject override.
20030415-015 GUIRENDR This issue is specific to SmartFilters containing
. field(s) with a masked format, e.g. "(999)999-9999".
After entering the first character into the SmartFilter
field, the cursor jumps to the last position in the
field.
20030115-010 GUIRENDR SmartDataField fill-in is resized when placed in a
SmartDataViewer.
00013903-000 GUIRENDR When the foreign key value(s) of a record visualized as
a treeview node are changed, the node does not reappear
in its correct tree branch position corresponding to
the new values.
00013872-000 GUIRENDR adm2/combo.p does not compile due to a wrongly
referenced include
00013085-000 GUIRENDR Empty RowObject records are left in the SDO on failed
create making them visible in browser and viewer on
local connections.
20040129-002 PROSPY Pro*Spy Plus returns ENTRY errors when loading logs
with carriage returns in parameters.
20040302-026 SERVICES If you have 2 Static SDFs on the same viewer that have
the same original label and both are translated, the
first pass at translating them fails.
20040219-018 SERVICES The getLabelHandle function is not found for translated
SmartDataFields.
20030825-040 SERVICES Folder object shows scrollbars if more then 1 row of
tabs is used.
20021104-003 SERVICES Changes containing accented characters are discarded on
saving.
20020509-013 SERVICES The items and of a dynamic combo cannot be
translated.
00013916-000 SERVICES Entity Cache files are dumped by default if the
auto_dump_entity_cache session parameter is not
specified.
00013673-000 SERVICES The ADMProps table is not being deleted on the
AppServer for data containers causing a memory leak.
20040331-014 TOOLS If a dataField object contained any attribute in the
repository with a null value, the dynamic property
sheet launched from the DataField Maintenance screen
would not properly display all attributes for the
object. Instead they would display only the initial
values for all attributes.
20040210-010 TOOLS The first time the AppBuilder is selected in a
Roundtable, it takes a very long time to initialize.
20040209-033 TOOLS When using the security control from the Administration
menu to assign security to actions, the key field is
being assigned the unknown value causing orphan
security records in the repository.
20040209-026 TOOLS When trying to add a menu to window with a SmartPanel
an error message is shown that says that menu cannot be
added because the Window has a SmartToolbar with a
menu.
20040202-039 TOOLS The "Print Preview to XML/HTML" feature provides an
alternative to the current Print Preview that only does
an "Export to Crystal" (CR8). It allows you to specify
in the session type whether you want the default to be
Crystal, XML or HTML. For HTML/XML it will open a Web
Browser to display the results.
20040119-025 TOOLS Error 247 occurs when generating the DataLogic
Procedure with more than one extent field in the SDO.
20040119-007 TOOLS The dynamic property sheet no longer shows buttons for
properties that need to be modified using a dialog
screen.
20031230-001 TOOLS The order in which rectangles are displayed is not
maintained correctly for files built in early releases
of version 8. This has the effect of incorrectly
hiding overlayed rectangles.
20031217-006 TOOLS Reopening and saving an SDV that was made against an
SBO renames the data field from "sdo.field" to
"table.field". As a result, the viewer no longer works
with various errors such as error 560 when trying to
add a record.
20031212-001 TOOLS Error 3567 occurs when saving a static viewer that has
a SDO field represented by an editor widget.
20030829-029 TOOLS If a section editor is open when a message area is
added or removed in a window, clicking the "List"
button in the section editor will hang the session.
20030827-030 TOOLS If a read-only file was opened in the Procedure Editor
and modified, and then the user closed the window
without saving the file, a message was displayed
indicating that the file was read-only and could not be
saved. However, the procedure editor continued to close
the file thus losing all changes.
20030721-031 TOOLS The focus does not go back to the correct parent window
when exiting from a Filter window.
20030616-030 TOOLS Shortcuts (Alt+key) for Tab Folder labels do not work.
20030528-005 TOOLS Dynamic viewers were not having their minimum height
and minimum width set correctly. The system was
automatically adding 1 character for the minimum width
and 1 character for the minimum height at run time.
In addition, at design time, the system was also
adding an extra character for the width and the height.
So when you resized the viewer to its minimum size and
saved it, the extra character re-appeared when it was
reopened.
00013706-000 TOOLS The bottom toolbar on most framework tools, like the
Product Control and Language Control looks darker than
the top toolbar at runtime.
20040209-018 WEBRENDR Event hooks like onClick, onBlur do not get output to
the DynLookup element on the Web. Also the
_lookup hook never gets called on return from
Lookup.
20040119-001 WEBRENDR Toolbars set to be vertical remain horizontal on web
rendering.
20030818-004 WEBRENDR URL mapping (/scripts/cgiip.exe?WService=wsdynamics1/)
is provided as an alternative to (*.icf) extenstion
mapping.
00013968-000 WEBRENDR Deleting a record in an SBO-based container on web
gives an error and the record is not deleted.
00013793-000 WEBRENDR Dynamic Lookups with nested queries do not work on the
web.
00013790-000 WEBRENDR Dynamic lookups do not work on local fields on the web.
00013432-000 WEBRENDR The SBO Commit button does not work the way it should
. on the Web. If an SBO has multiple SDOs it will only
control one of them correctly.
===========================================================================.
.