Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SCL-2804 DatasetModelGenerator now excludes Virtual Column's from cBufferFieldMapping

Description:

The DatasetModelGenerator now properly excludes virtual columns from the buffer-field mapping list.

SCL-2821 Improved handling of "{" character in dynamic query strings passed to DataAccess classes

Description:

Previously we've been masking the "{" character in dynamic queries strings received via the JSDO generic service with "~{". We're now providing the ability to replace this (and potentially other characters for every possible method of passing a query string to a Data Access class.
We have now implemented the interface Consultingwerk.OERA.IQueryStringFilter for services supporting manipulation of the query string for Data Access classes. Our default implementation the Consultingwerk.OERA.EscapeCurlyBracesFilter now generally escapes the "{" with "~{" in all query strings passed to the Data Access class.

SCL-2822 Displaying menu structure code in menu security assignment

Description:

To support the maintenance of the menu authorization in large menu structures, we're now also displaying the menu structure code in the menu authorization maintenance.

Improvement

SCL-2774 Improved performance Viewer Master designer

Description:

We have significantly improved the performance of the Viewer Master Designer (SmartFramework repository) when opening and saving designs.

SCL-2791 List of Business Entity Web Handler now includes "copy to clipboard" functionality in html output

Description:

The /web/BusinessServices/... web handler now adds a copy to clipboard link to the name of a Business Entity or Task.

SCL-2794 RestServerSessionActivator won't store context for SESSION-ID "0" anymore

Description:

When the PASOE spring hybrid realm authentication is used with basic authentication, the client-principal SESSION-ID property returns "0". This is expected. As every request to the backend made using basic authentication, we're no longer storing and restoring the session context from the context store in the SmartDB for SESSION-ID = "0".

SCL-2807 Implemented endpoint for fetching Validation Instance Property Descriptors

Description:

To support the implementation of the browser based business entity designer, we've implemented an Endpoint in the BusinessEntityDesignerBusinessTask which returns the property descriptors for the validation objects supported by the tool.

SCL-2809 Added additional fields to the user grids in the group maintenance

Description:

To simplify the assignment of users to group in the group maintenance we have added additional fields to the grids there
- user full name
- user email

SCL-2810 Improved error message when seeking for a non existing object type in object type maintenance

Description:

We've improved the error message when seeking for a non existing object type in the object type maintenance. We're now showing a qualified error message instead of a generic "record not available".

SCL-2816 SmartBusinessEntityAdapter/SmartDataBrowser should scroll to top before/during RetrieveData

Description:

We've resolved a minor inconvenience. Previously when opening a SmartBusinessEntityAdapter query with batching and after scrolling down a few pages, calling RetrieveData again the Business Entity Adapter might have fetched the second batch just after requesting the initial batch.
Our investigation has shown that this was due to the Grid not repositioning to the to of the list in time and thus requesting the second batch (off end).
We've resolved this by scrolling to the top of the grid before/during RetrieveData.

SCL-2818 Implemented limit to the number of BY phrases used in PrepareQueryInReverseOrder

Description:

As the ABL does not support dynamic query strings with more than 16 BY phrases, we're not limiting the number of BY phrases added to the Query String in the QueryHelper:PrepareQueryInReverseOrder method.

SCL-2823 Implement ability to Skip rows sequentially in Data Access classes

Description:

The combination of row number based batching (Skip argument in FetchDataRequest) and BEFORE-ROW-FILL call backs may result in multiple batches containing the same database records.
When the first batch skipped 10 rows using BEFORE-ROW-FILL/RETURN NO-APPLY and the second batch is requested using Skip 50, result records 50 - 60 would overlap with the first batch as the Skip is just applied to the database query and is not taking the programmatically skipped rows into account.
We've implemented the ability to influence this behavior in a Data Access class. First the FetchDataAccessRequest class now provides a new attribute SkipRowsSequentually which changes the behavior of the Skip attribute of the FetchDataRequest. In Data Access classes using the BEFORE-ROW-FILL callback in combination with RETURN NO-APPLY to skip rows (row level security) developers can enable the extended batching behavior using this code:

Code Block
languageabl
     METHOD PUBLIC OVERRIDE VOID FetchData (poFetchDataRequest AS IFetchDataRequest):

        DEFINE VARIABLE oRequest AS FetchDataAccessRequest NO-UNDO.

        oRequest = NEW FetchDataAccessRequest (poFetchDataRequest) .
        oRequest:SkipRowsSequentually = TRUE .

        SUPER:FetchData (oRequest) .

    END METHOD.


Developers have to further separate the BEFORE-ROW-FILL callback method. We need to call into this method from within the Data Access class directly and be able to assert the result. As the ABL does not allow to assert if a method returned using

Code Block
languageabl

RETURN NO-APPLY . 


we have to split this method like this:
The actual BEFORE-ROW-FILL callback

Code Block
languageabl

    METHOD PUBLIC VOID eCustomerBeforeRowFill (DATASET dsCustomer):

        IF THIS-OBJECT:eCustomerBeforeRowFill () THEN
            RETURN NO-APPLY .

    END METHOD .


and the actual implementation of the decision which rows to skip (due to row-level security etc.):

Code Block
languageabl

    METHOD PROTECTED LOGICAL eCustomerBeforeRowFill ():

        IF Customer.CustNum MODULO 2 = 0 THEN
            RETURN TRUE .

    END METHOD .


It's important to provide those signatures exactly. The actual BEFORE-ROW-FILL callback is a PUBLIC method with the dataset as an INPUT PARAMETER. The method which decides which records should be skipped must be called <temp-table buffername>BeforeRowFill, may be PROTECTED or PUBLIC, returns LOGICAL (true: skip row, false or ?: accept row) and takes no parameter.

SCL-2824 Implemented logging about SmartFramework Rendering Performance

Description:

Based on the "Rendering" custom log entry type, we are now logging
- runtime for retrieving repository data
- runtime for rendering individual components
- runtime for retrieving data of various SmartBusinessEntityAdapter instances

New Feature

SCL-2541 Mass-Assignment utility for Security Assignment

Description:

We've implemented a new tool which allows Administrators to assign the authorization for a user or group for all security items of a given security realm to either restricted or unrestricted or to remove the existing security assignment records altogether.
This utility can be launched form the SmartFramework menu under "Authentication and Authorization".

SCL-2803 Equals() override for TableModel

Description:

When used as a Entites (DDD), TableModels should define Equality based on primary unique key values (the identity or records). To facilitate this we have implemented a default override of Equals(), implementing comparison of the primary unique key values (when present).

SCL-2805 Business Entity Designer now indicates private/protected columns

Description:

The Business Entity Designer now indicates PRIVATE and PROTECTED columns on the design canvas using the usual - and # characters after the field name.

SCL-2808 Ensuring PASOE Startup does not execute System.Environment:NewLine

Description:

A customer has reported issues with the use of .NET on PASOE in the form of crashes during the AppServer startup. Those issues are most likely OpenEdge core issues.
To support working around those issues we've however ensured that the Consultingwerk.Environment class invoked during the AppServer startup does not invoke the .NET System.Environment class anymore.