Miscellaneous Notes and Bug Fixes for USoft 11.0.BETA2
Bug fixes
The identification number in front of each item title is a Jira Issue ID. Jira is the information system that USoft uses internally. If you use these numbers in your communications with USoft, the support desk will know what you are referring to.
An identification number(s) at the end of an item title (if any) is a Jira Support ID. This is the number that was used in communication about the support call that gave rise to the note or the bug fix.
BENCHMARK
USD-5954
When USoft Benchmark was connected to a Version Control repository, running Synchronize could result in a "no rights on job" error.
This has been fixed.
DEFINER
USD-5074
The performance of the process to initially connect to a version control repository has been improved.
USD-5297
Note: This issue is about changes to generated domains and tables. If you are already using any of these domains or tables, then this is no problem. They can be used without problems.
- Previously, USoft generated a T_EVENT table by default. Now, this only happens if you set the STARTUP_EVENT Rules Service Parameter to True.
- Previously, USoft generated domains with names starting with TWI_.... . These have been replaced by the USoft 11 template domains. This also applies to domains used for columns in the generated tables TABLE_SEQUENCE_NUMBERS, T_APP_TIME, and T_EVENT.
- Previously, USoft used a generated domain called TW_YESNO for generated subtype indicator columns. These columns now use the BOOLEAN template domain.
- Previously, USoft used the TWI_CHAR_30_UP domain as a fallback for Logical View columns for which it could not determine a specific domain. Now, it uses the SHORT_TEXT template domain in this situation.
USD-5470
When connecting or synchronizing in Version Control, there was no progress indicator during the import of paintings.
This has been fixed.
USD-5962
Version Control: if a checkable object (such as a Logical View or a SQL Task) was deleted in the version control repository, during Synchronize it could re-appear on the file system.
This has been fixed.
USD-6004
In Windows Designer and Web Designer, if a class which was not an entity did not have any properties but did have one or more inserted controls, the class would not be noticed by the Version Control system and would not be exported to file.
This has been fixed.
USD-6079
When a database repository was under version control and Synchronize ran into an error, the error sometimes popped up multiple times and subsequent objects were not loaded.
The error now appears only once and an attempt is made to load subsequent objects.
USD-5506
The EAR diagram functionality introduced in USoft 11 Beta 1 for Business Objects (BO) is now also available at Repository Definition (REP).
At the BO level, the EAR diagram only displays tables connected to the BO via Data Contents.
At the REP level, by definition, the EAR diagram displays all tables known to Definer.
Intended behaviour is that you create a single Repository Definition for your repository.
USD-5558
The Teamwork, Object Shopping, Import Off The Shelf option gave problems in Beta 1 because the models had not yet been upgraded to 11.
This has been fixed.
USD-5598
The table creation process has been improved. Wherever possible, an ALTER TABLE statement is now used rather than the older strategy of renaming a table to OLD_<table_name>, creating a new table, and transferring data from the old to the new table.
Also, the renaming of tables and columns is now tracked and performed automatically.
USD-5743
Creating a self-referential relationship in an EAR diagram could raise Error: Lookup and Related Window Titles cannot be the same.
This has been fixed.
USD-5773
If you created a subtype box in an EAR diagram and you created a non-key column in the subtype box, saving the diagram resulted in an error because the non-key subtype column was written to Definer with Key = 1.
This has been fixed.
USD-5844
In an EAR diagram, changing the direction of a subtype relation line (arrow) resulted in an error.
This has been fixed.
USD-5845
Dropping a subtype relationship line (arrow) from an EAR diagram resulted in an error.
This has been fixed.
USD-5912
It is now possible to filter out items in a tree view by using a search key. All tree views in USoft Definer now contain this search filter. All USoft tree views now contain a new method FilterTree() which can be used to filter entries in a tree view.
USD-5965
If you renamed the role name of an existing relationship in an EAR diagram (by overwriting the text by the relation line), when you saved the diagram, 2 relationships remained in Definer: one with the old name and one with the new name.
This has been fixed. 1 relationship remains, with the old role name replaced by the new role name.
USD-5978
It is now possible to rename Tables and Columns directly from an EAR diagram.
In an EAR diagram, to rename a table, use the Table Name setting in the property sheet for the table.
In an EAR diagram, to rename a column, use the Column Name setting in the property sheet for the column.
USD-6017
Saving an EAR diagram in USoft Definer on Oracle could lead to error "Unexpected end-of-file while parsing Name".
This has been fixed.
USD-6080
In EAR diagrams, the positioning on the canvas of table boxes for tables created in the diagrammer was not remembered on first re-open of the diagram.
This has been fixed.
USD-6081
Pressing the 'print' button could result in a crash.
This has been fixed.
USD-6083 (US-1338)
Certain incorrect SQL statements could lead to a crash.
This has been fixed.
USD-6091
Extension Properties were not written correctly to the VersionControl repository and were not read during Connect or Synchronize.
This has been fixed.
MISCELLANEOUS
USD-3962
RDMI:Automation Servers were deprecated in version 10. They have now been removed from the product.
If you are on version 10 and still have components of type RDMI Automation Servers, you are advised to change them into DotNet components before upgrading to 11.
RULES ENGINE
USD-6094
$$GUID$$ was no recognized by the parser.
This has been fixed.
USD-6103
When running against SqlServer via ODBC, the ordering of data in select statements using order by position, could lead to unexpected results if the outlist contained one or more LOB columns.
This has been fixed.
SERVICE FRAMEWORK
USD-6075 (US-1337)
If Service Definer was connected to a version-controlled repository, special characters (for example smart quotes) would not be read correctly during Synchronize.
This has been fixed.
WEB DESIGNER
USD-5925
You can now achieve instant validation of values supplied by a web page user in an input control by setting special Web Designer properties.
For example, you can validate that the value a user types in a text box contains alphabetic characters only, or does not exceed some maximum length.
Instant validation gives feedback by applying user-friendly colours, icons and positioning in the web page. In some cases, feedback is more immediate than when you define the validation rule(s) (only) at domain level in USoft Definer.
For details, see documentation on these Web Designer properties:
- Validation Rules - Validation Moment
- Validation Feedback
USD-5390
In USoft 10, there are additions to various common and global prototypes, including the Object prototype. These additions contain functions such as 'map' which may cause name clashes if other, third-party software also tries to make such changes to the same prototype.
This has been fixed: for accessing USoft functions on the prototypes, use a '.usoft' prefix to the function, e.g. object.usoft.map() for: object.map().
USD-6057
When a repository was under version control, page and window properties such as 'description', 'state', and 'read-only' were not written to the VC repository if no other changes were made.
This has been fixed.
USD-6073
In a version-controlled repository, certain changes made to a page or window in Web Designer or Windows Designer were not written to the version-controlled repository on the file system. This applied if the changes were not saved by means of the Save button but by pressing the close 'X' and then replying 'Save' in response to the question what to do with the changes.
This has been fixed.