New Features: Object state change detection, and more ...
|
|
|
|
|
CARE Technologies is pleased to announce the new versions of the OLIVANOVA Products:
|
|
| Common Features for all products |
Object state change detection: Nowadays, it is necessary that users could interact with the information system in concurrency. To allow this concurrency interaction, State Verification feature has been introduced in OLIVANOVA applications. By means of this new feature, the Analyst can specify attributes and/or roles that must be controlled before a service is executed. When a user, in the final application tries to execute the service, then those specified attributes and roles are checked to ensure that their value has not been modified by another user in the period between the query (to retrieve the values) and the execution of the service.
|
|
| OLIVANOVA Modeler - Version 7.4.5.0.4.0 |
Find & Replace: The number of characters that can be introduced in the combo boxes when using the “Find and replace” facility has been increased.
|
|
| OLIVANOVA STAR Client - Version 3.1.0 |
New option in Business Logic Transformation Engine Transactional C#.Net 2.0 (BLT_TRCS2) profile:
- Autonumerics set by the DB: Determines whether the value for the autonumeric ID of a class will be calculated by the RDBMS
|
New option in User Interface Transformation Engine Web ASP.Net 2.0 (UIT_ASP2) profile:
- Default Theme: Default theme of the application. Its options are ‘Metal’, ‘Dianium’ and ‘inNOVAtion’.
|
Changes in User Interface Transformation Engine Java Server Faces (UIT_JSF) profile’s options:
- JNDI Server: The option ‘Business Logic Application Server’ now is named as ‘JNDI Server’.
- Default Theme: Options ‘Desert’ and ‘Metal’ had been substituted by ‘Dianium’ and ‘inNOVAtion’.
|
|
| OLIVANOVA COMPARATOR - Version 3.0.4.0 |
Compares the new property of the State verification, showing all the information about their modifications
|
|
| OLIVANOVA Multilanguage – Fixed Text to be updated – 5.12 |
The XML file holding the Transformation Engines fixed texts has been updated.
- Some new texts have been added to the User Interface Transformation Engine (UIT) profile.
- A new text has been added to the Business Logic Transformation Engine (BLT) profile.
|
|
| OLIVANOVA Documentation Manager – 3.5.4.0 |
The information about the state verification of an object has been included in the Service Interaction Unit section of the Full Model Documentation.
|
|
| OLIVANOVA User Interface Desktop C# .NET 2.0 Transformation Engine – v.3.2.4.0 |
Increase the maximum length in password type inbound arguments.
|
|
| OLIVANOVA User Interface Web ASP.NET 2.0 Transformation Engine – v.3.1.4.0 |
Increase the maximum length in password type inbound arguments.
|
|
| OLIVANOVA User Interface Web JSF Transformation Engine – v.3.1.4.0 |
Increase the maximum length in password type inbound arguments.
|
|
| OLIVANOVA Business Logic Transactional C# .NET 2.0 Transformation Engine – v 2.7.4.0 |
Have autonumeric ID fields calculated by the RDBMS, instead of the C# code. Classes with its own ID function comprising just one autonumeric attribute which is not requested upon creation and not having any other autonumeric attribute can rely on the RDBMS to determine the value of said attribute upon creation, thus alleviating locks when massively creating instances of said class.
NOTE: This feature is available for all certified RDBMS: SQL Server, Oracle, DB2 and MySQL.
The maximum length allowed for agent passwords has been increased to 30.
In case this length is not enough or is too large, the code has been changed to make easier the change of this value, using constants defined in just one file
The access modifier for filter variables members in navigational filter classes has been changed from private to public fields, so they become accessible from the rest of the code.
The information loading of a related legacy view has been delayed from the moment of loading the local class to the moment in which legacy view information is needed.
If a local class is related with a legacy view, when retrieving the information of the local instance there was a query to the legacy system to retrieve the information of each related legacy view. If this information is not needed, the connections can overload the system unnecessarily. The feature has been implemented just to avoid this overload.
The error message from the legacy system is now returned instead of the generic message of error in Legacy Views.
When an error occurs in a legacy system, the server always returned the same message (Error occurred while attempting to communicate with legacy system). Instead of returning this message is more useful for the user to show the error occurred in the legacy system.
|
|
| OLIVANOVA Business Logic Transactional EJB2 Architecture Java Platform Transformation Engine – v 5.0.4.0 |
Have autonumeric ID fields calculated by the RDBMS, instead of the C# code. Classes with its own ID function comprising just one autonumeric attribute which is not requested upon creation and not having any other autonumeric attribute can rely on the RDBMS to determine the value of said attribute upon creation, thus alleviating locks when massively creating instances of said class.
NOTE: This feature was already available for DB2 and now it is available for SQL Server, Oracle, and MySQL.
The maximum length allowed for agent passwords has been increased to 30.
|
