Page Comparison

...

SCL-2839 Fixed error in RestEntitiesWebHandler when resource URI references field actually not returned by the request itself

Description:

In this request http://localhost:8820/web/Entities/Customers/1/Orders/36/OrderLines/1 the customer number is not returned by the OrderLine table.

@RestAddress (type="record", address="/Customers/~{CustNum}/Orders/~{OrderNum}/OrderLines/~{LineNum}", tables="eOrderLine,eItem", id="LineNum",
              fields="*", canRead="true", canUpdate="true", canDelete="true").

However it's provided by the request URL and can be used to build the record URL for the response.
However the following error is raised:

{
  "title": "A runtime error has occurred (Progress.Lang.SysError)",
  "error": "Progress.Lang.SysError",
  "messages": [
    {
      "message": "BUFFER-FIELD CustNum was not found in buffer eOrderLine. (7351)",
      "messageNum": 7351
    },
    {
      "message": "Lead attributes in a chained-attribute expression (a:b:c) must be type HANDLE or a user-defined type and valid (not UNKNOWN). (10068)",
      "messageNum": 10068
    },
    {
      "message": "Error attempting to push run time parameters onto the stack. (984)",
      "messageNum": 984
    },
    {
      "message": "Error attempting to push run time parameters onto the stack. (984)",
      "messageNum": 984
    }
  ],
  "callStack": "ResourceUri Consultingwerk.OERA.RestResource.RestEntitiesWebHandler at line 3669  (c:\\work_stream\\SmartComponentLibrary\\Develop121\\ABL\\Consultingwerk\\OERA\\RestResource\\RestEntitiesWebHandler.r)\nBuildRecordResponse Consultingwerk.OERA.RestResource.RestEntitiesWebHandler at line 1118  (c:\\work_stream\\SmartComponentLibrary\\Develop121\\ABL\\Consultingwerk\\OERA\\RestResource\\RestEntitiesWebHandler.r)\nHandleGet Consultingwerk.OERA.RestResource.RestEntitiesWebHandler at line 1913  (c:\\work_stream\\SmartComponentLibrary\\Develop121\\ABL\\Consultingwerk\\OERA\\RestResource\\RestEntitiesWebHandler.r)\nHandleRequest OpenEdge.Web.WebHandler at line 61  (OpenEdge/Web/WebHandler.r)\nHandleRequest OpenEdge.Web.InternalWebRouter at line 113  (OpenEdge/Web/InternalWebRouter.r)"
}

We have fixed this issue.

SCL-2840 Resolved issue caused by race condition when creating a new session.

Description:

Customer was reporting occasional errors like this when web clients were logging into the system:
Osiv reported that during performance testing they encountered the following error:

An Progress.Lang.SysError has occurred:
Error reading XML from a MEMPTR or LONGCHAR. (13036)
READ-XML encountered an error while parsing the XML Document: FATAL ERROR: file 'MEMPTR', line '1', column '1', message 'invalid document structure'. (13064)
RestoreSessionContext Akioma.Swat.OERA.Context.SwatContextDatasetStore at line 602 (Akioma/Swat/OERA/Context/SwatContextDatasetStore.r)
ActivateSmartServerSession Akioma.Swat.System.SwatServerSessionActivator at line 805 (Akioma/Swat/System/SwatServerSessionActivator.r)
ActivateServerSession Akioma.Swat.System.SwatServerSessionActivator at line 553 (Akioma/Swat/System/SwatServerSessionActivator.r)
OnActivated Consultingwerk.OERA.ServiceInterface at line 4447 (Consultingwerk/OERA/ServiceInterface.r)
Activate Consultingwerk.OERA.ServiceInterface at line 597 (Consultingwerk/OERA/ServiceInterface.r)
GetData Consultingwerk.OERA.JsdoGenericService.Service at line 1045 (Consultingwerk/OERA/JsdoGenericService/Service.r)
HandleGet Consultingwerk.OERA.JsdoGenericService.WebHandler.ResourceWebHandler at line 754 (Consultingwerk/OERA/JsdoGenericService/WebHandler/ResourceWebHandler.r)
HandleRequest OpenEdge.Web.WebHandler at line 61 (OpenEdge/Web/WebHandler.r)
HandleRequest OpenEdge.Web.InternalWebRouter at line 113 (OpenEdge/Web/InternalWebRouter.r)

Analysis has shown that this issue might have occurred when multiple requests from the same client session have been issued while the session context store was yet to be initialized and thus the LONGCHAR / CLOB with the serialized context dataset was empty.
We have added a new configuration setting (.restapplicationsettings) RereadSmartContextStoreOnInitialization which allows to control the number of attempts to read the SmartContextStore when the SessionID is already valid, but no data is stored for the Context Dataset yet. We'll use a 1/10 of a second break between re-read attempts. The ThrowWhenStoredContextIsNotAvailable setting (logical) allows to control if we're throwing an exception when the context record contains no valid context dataset of if we re-create the context dataset.

SCL-2843 Resolved an issue where the users password couldn't be changed for user with no company assigned

Description:

We have resolved an issue preventing users that were not defined against a specific login company from changing the user password stored in the SmartUser table.

Improvement

SCL-2829 MetaViewer/MetaFrame Angular rendering now optionally supports absolute positioning

Description:

The MetaViewer and MetaFrame repository rendering to Angular (JSON) now supports both responsive (default) and absolute positioning of controls.
The behavior is based on the LayoutStyle property of the viewer and can be set to either Pixel or Responsive.

SCL-2830 MetaViewer/MetaFrame now supporting for rendering of images on Angular buttons

Description:

We've implemented rendering support for images on buttons in Angular Viewers.

SCL-2837 Added run button to Repository Object Master maintenance

Description:

We have added a Run button to the Repository Object Master maintenance Form. This buttons clears the repository cache and launches the currently opened form.

SCL-2841 Improved error message raised when creating a repository object under a duplicate name

Description:

We have implemented a more meaningful error message when creating an Object Master under a duplicate name.

SCL-2845 Improved fault tolerance of Repository Service on inconsistent repository data

Description:

We have improved the robustness of the Repository Service when retrieving repository data. First we no longer require the SmartModule of the SmartObjectMaster record to be available. The module is not needed for rendering purposes. Secondly when for whatever reasons the cache records for the Attribute Temp-Tables contains an invalid temp-table handle, we will re-create the temp-table instead of failing.

SCL-2849 SessionHelper:DLC now includes check for WINDOW-SYSTEM MS-WIN95

Description:

When determing the DLC or PROMSGS value we have been relying on the WINDOW-SYSTEM value of MS-WINXP. We've extended that to include MS-WIN95 as well.

SCL-2850 Implemented a way to disable NotifyIconWaitStateManager in GuiClientStartupManager

Description:

We have added a new static property to the Consultingwerk.Framework.GuiClientStartupManager class.

     /**
     * Purpose: Gets and sets if a Notify Icon WaitStateManager instance should be
     *          used and initialized
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY UseNotifyIconWaitStateManager AS LOGICAL NO-UNDO INITIAL TRUE
    GET.
    SET.

This property can be set thorough the JSON configuration file and allows to control if an instance of the NotifyIconWaitStateManager will be instantiated or not.

SCL-2853 Added overload to BufferHelper:FindDatabaseBuffer which accepts additional key values

Description:

We've implemented a new overload to the FindDatabaseBuffer method which accepts a list of values which complete or override the key values form the provided temp-table buffer. This method is useful when the Business Entity temp-table's do not contain fields like the client key but those need to be provided when fetching the database buffer.

    /**
     * Purpose: Finds the database record for a linked (ProDataset data-source) record
     *          in a ProDataset.
     * Notes:   Uses the PUK or first UK of the database record with the field values
     *          of the ProDataset buffer, based on the provided field mapping. This variant of the
     *          method also allows to pass a ListNameValuePair with values which override or complete
     *          values (missing) from the temp-table, e.g. when the client-key of a database table is
     *          not part of the temp-tables
     * @param phBuffer The database buffer to locate
     * @param phDatasetBuffer The dataset (before or after) buffer
     * @param pcFieldMapping The field mapping between database and temp-table (ATTACH-DATA-SOURCE method)
     * @param poMissingValues List of Name value pairs with missing values
     * @param poLockMode The LockModeEnum value controlling the record lock-mode
     */
    METHOD PUBLIC STATIC VOID FindDatabaseBuffer (phBuffer AS HANDLE,
                                                  phDatasetBuffer AS HANDLE,
                                                  pcFieldMapping AS CHARACTER,
                                                  poMissingValues AS ListNameValuePair,
                                                  poLockMode AS LockModeEnum):

...

SCL-2826 Implemented on demand rendering of SmartViewerControl

Description:

SmartFramework Repository based SmartViewerControls (MetaViewer) now support lazy or on demand rendering. The controls on the viewer will now only be rendered when the user is switching to the tab folder page that contains the viewer. Lazy loading can be turned off using the LazyLoading repository attribute of the viewer instance or master.
Viewers on page 0 are by default not lazy loaded.
Lazy loading will significantly speed up the launch time of forms containing a larger number of viewers on various tab pages.