BB2-3524: Contract ID and formatting updates#83
Merged
jimmyfagan merged 2 commits intofeature/c4dicfrom Nov 19, 2024
Merged
Conversation
loganbertram
approved these changes
Nov 19, 2024
loganbertram
left a comment
There was a problem hiding this comment.
Looks like expected, matches the linked screenshot. Everything seems to be in order
This file contains hidden or 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
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.
JIRA Ticket:
BB2-3524
What Does This PR Do?
What Should Reviewers Watch For?
Nothing in particular, just check that the changes make sense and render properly.
Validation
Validated by running the sample client against my local server from the feature/c4dic web-server branch.

I see the below card when running with BBUser10000 (I think that was the user anyway):