Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Components
Assignee
Tim KlemmTim KlemmReporter
Tim KlemmTim KlemmPriority
MajorFix versions
Pull Request URL
Details
Details
Components
Assignee
Tim Klemm
Tim KlemmReporter
Tim Klemm
Tim KlemmPriority
Fix versions
Pull Request URL
Created November 15, 2018 at 2:20 AM
Updated December 5, 2018 at 3:17 PM
Resolved December 5, 2018 at 3:17 PM
The custom request transform is required to populate data fields not available to certain users, and to enforce legal requirements to prevent certain values from being set by users not authorized to do so.
Logging needs to log the values actually applied in the request, not blanks for values users could not provide and not invalid values supplied by users who could, but shouldn't have, supplied them. The log agent needs access to the transformed request to include the correct values in the log update request.
The transformed request currently exists as a local variable in the handleFinalRequest. This method will, for DESDL requests only, simulate an additional response dataset that includes the request data. The log agent will need to be changed to recognize this dataset when it is present, and make the contained data available for logging.