Release/1.7.0 #184
Merged
Release/1.7.0 #184
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OS-80: Fixed LFI issue with report generating.
OTC-530: Moving district is now blocked if local pricelists present.
OP-735: fixed 'restoring claim' functionality
OTC-523: correction of displaying report 'ClaimOverview with detail'
…and Premium models
…Premium interface layer
…, Insuree, Policy and Premium
OTC-616: Add new columns related to the source of the entries in all the enrolment related tables
OP-786 Added claim related tables to claims export
OP-796: Changed .net framework to version 4.8.
OTC-661: EO Substitution looks like mandatory
OTC-655: Fixed culture not found error
OTC-655: Change approach to culture not found error in report export
OTC-672: Fixed Contribution Distribution report
Hide the report mode option and set the value 1 in the Commission Overview Report
OTC-673: Overview of Commission does not require Previous report input anymore.
Finish feature/OS-80
Designing issue of the report (the width of the column is increased)
OP-937: Phone extract SQL bug fixed.
OTC-733: Create user with English language throws an exception
OTC-733: Create user with English language throws an exception
hirensoni913
approved these changes
Nov 16, 2022
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 3700516 | Generic High Entropy Secret | 8825357 | IMIS_BL/EscapeBL.vb | View secret |
| 3700516 | Generic High Entropy Secret | 8825357 | IMIS_BL/EscapeBL.vb | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.