[ENGA3-1173]: Updated the secure form database key to the correct one. #373
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
danfowler
reviewed
May 3, 2023
danfowler
approved these changes
May 8, 2023
ajzkk
approved these changes
May 8, 2023
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.
1. Objective
Fix the issue of secure form notification not turning off.
Jira Ticket: (#1173)[https://opn-ooo.atlassian.net/browse/ENGA3-1173]
2. Description of change
Updated the key where secure form status is saved from
embedded_form_enabledtosecure_form_enabled.3. Quality assurance
Specify where and how you tested this and what further testing it might need.
🔧 Environments: