[ECOMMERCE-497] Expose Category Key in request reponse for Category ID so user can render dynamic category pages Created: 14/Feb/22  Updated: 18/Oct/22  Resolved: 21/Mar/22

Status: Closed
Project: E-commerce
Component/s: None
Affects Version/s: 1.2.6, 1.3.1
Fix Version/s: 1.3.2

Type: Story Priority: High
Reporter: Dominik Maslanka Assignee: Andrei Ichimescu
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon ECOMMERCE-491 Migrate commercetools to commercetool... Closed
documentation
to be documented by ECOMMERCE-509 DOC: Add newly exposed category key t... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Epic Link: AuthorX Maintenance
Sprint: AuthorX 4, AuthorX 5
Story Points: 3

 Description   

User Story: As User I would like to render dynamic Category pages by calling it by the Category Key instead of only CategoryID so that I can get my pages from the commerceTools 

 

Background: our Client's Avon  users is facing a difficulties with rendering  dynamic category pages. Currently our framework offers to call it directly via below params:
private final Id id;
private final String name;
private final String description;
private final Integer position;
private final Integer level;
private final String parentId;
private final String path;
 

 

Requirement: We need to somehow expose Category Key without interrupting our framework structure (so the solution won't be one customer oriented). Would be great to try reach as lowest amount of request as possible for the customer. 

 

Acceptance Criteria:

 

Given: User has integrated CustomerTools with Magnolia Commerce Connector Pack 
When: He request for all Categories or Category by single ID 
Then: He receives Category Key in response

 

outcome: He can filter the categories by the key provided in the response
and 
Then: He can render the (filtered) categories


Generated at Mon Feb 12 01:44:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.