fix: Create/update entity send log columns. #612
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug report
Currently the columns, used for the log record, are being sent to the server from the client, these columns should be omitted as they should be handled by the server only.
Steps to reproduce
Currently the columns, used for the log record, are being sent to the server from the client, these columns should be omitted as they should be handled by the server only.
System Admin
menu.Issue Report
window.New Record
and fill fields.Screenshot or Gif
After this PR:
Before this PR:
Expected behavior
These columns should always remain read-only for both log entry and editing, as they are in the smart browser results and window.
As for the smart browser and query criteria reports/processes and forms, they can be editable (if defined in the application dictionary) since they do not modify record data from the client but are used for queries.
Other relevant information
Additional context
the evaluation of obligatory nature is omitted and the t fields are placed as read-only are placed where applicable.