Paf 160 #133
Open
Paf 160 #133
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
Comment on lines
+9
to
+11
| eform.Attachements.push({url: fieldValue}); | ||
| } else if (fieldName === 'tbwhoaddperson') { | ||
| eform.AdditionalPeople = fieldValue; |
There was a problem hiding this comment.
basically both lines should be eform.Thing = fieldValue;
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.
What?
Mapped and added additional people to the json data that is sent to SQS
Why?
The user is allowed to add unto six additional people to the allegation
How?
Mapped added HOF person field names to IMS field names and added to the json data
Testing?
Tested locally by sending the PAF form allegation to branch SQS and viewing the sent allegation in the Verint IMS PRP1 UI. Similar testing will also be done in branch and UAT.