Public Release r2.2 (Fall25 M4)#55
Conversation
| **Customer Insights v0.2.0 is the first public release version for v0.2.0 of the Customer Insights API.** | ||
| - **This version contains changes compared to v0.2.0:** | ||
| - Addition of `404 - IDENTIFIER_NOT_FOUND` | ||
| - Removal of `401 - AUTHENTICATION_REQUIRED` | ||
| - New pattern for `x-correlator` | ||
| - Addition of a new section `# Additional CAMARA error responses` in `info.description` field | ||
| - Addition of Algorithm Model Definiton documentation |
There was a problem hiding this comment.
Please group these into
Added
Changed
Fixed
Removed
There was a problem hiding this comment.
I prefer removing those Lines 35 - 39 as already mentioned below (so avoiding unnecessary duplication)
Added
404 - IDENTIFIER_NOT_FOUNDerror in Release Candidate API - Alignment with Transversal WGs #43- New section
# Additional CAMARA error responsesininfo.descriptionfield in Release Candidate API - Alignment with Transversal WGs #43 - Addition of Algorithm Model Definiton documentation in Algorithm Model Definition #29 and Algorithm Model Sources and Examplification #40
- New tests
@retrieve_scoring_400.02_invalid_x-correlatorand@retrieve_scoring_C02.02_phone_number_not_foundin Gherkin.featurefile in Testing Enhancements for RC API #44 - Added missing tests related to
idDocumentin Update customer-insights-retrieveScoring.feature #50
Changed
phoneNumberfield referenced to a schema for testing matching in Release Candidate API - Alignment with Transversal WGs #43- New pattern for
x-correlatorand model aligment with Commonalities in Release Candidate API - Alignment with Transversal WGs #43 - Test
@retrieve_scoring_404.01refactor and generic aligments (including x-correlator Background set-up update) in Gherkin.featurefile in Testing Enhancements for RC API #44 and API aligment with Transversal WGs Public Releases Fall25 #54 - Rename CUSTOMER_INSIGHTS.IDENTIFIERS_MISMATCH code in Rename CUSTOMER_INSIGHTS.IDENTIFIERS_MISMATCH code #51
- Error schema model alignment with Commonalities in API aligment with Transversal WGs Public Releases Fall25 #54
Fixed
- N/A
Removed
401 - AUTHENTICATION_REQUIREDerror in Release Candidate API - Alignment with Transversal WGs #43
Kevsy
left a comment
There was a problem hiding this comment.
for the customer-insights.yaml info.description, I suggest to change L4:
Provides a risk index based on the individual's profile owned by a Telco Operator.
to
This API allows the API consumer to retrieve a risk index based on the individual's profile owned by a Telco Operator.
(I think 'Provides' may give the wrong impression that this is a subscription service)
|
PS @PedroDiez will you also be doing the ErrorInfo alignment within Fall'25? |
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
|
Covered within commit updates_after_1st_RM_review:
|
There was a problem hiding this comment.
Approved on behalf of Release Management 👏
Next steps for the team:
- PR merged (by API repository codeowner)
- Release created within GitHub (by API repository codeowner)
- Release Tracker updated (with creation date of the release and the release tag link)
|
Merging PR and proceeding with Release tag generation |
|
API Release tracker updated: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/111706246/customer-insights+v0.2.0 |
What type of PR is this?
What this PR does / why we need it:
PR for Public Release r2.2 Generation for Customer Insights API
Which issue(s) this PR fixes:
Fixes #33
Special notes for reviewers:
To be reviewed after #51 merge
Changelog input
Additional documentation
This section can be blank.