Use Cases - UC-01 Categories

• User must be logged
• User must have ROLE_ADMINISTRATIVE

1. User request to obtain a category by primary key.
2. System returns category detailed model.
3. User updates general category information. User can updates I18n fields for the defined languages, add new languages or remove an existent one.
4. System receives request and save it to storage. CATEGORY_KEY AND VISIBILITY field will be ignored.
5. System may offer the option to update the products associated to category (@see UC-01f CategoryManagement-updateCategoryProducts)

System will raise and exception if primarey key does not exist.

• User must be logged
• User must have ROLE_ADMINISTRATIVE

1. User request to remove a category by primary key.
2. System will check for associated products and warn the user about:
   
   1. Number of products that belongs to that category that will be orphan.
   2. Double check to remove that category
3. User accepts to remove the category.
4. System updates all the products to remove the category.
5. System removes category.

1. System may offer the option to move the products to another category (@see UC-01f CategoryManagement-updateCategoryProducts)

System will raise and exception if primary key does not exist.

• User must be logged
• User must have ROLE_PRODUCT_MANAGER

1. User request to change category visibility of category by primary key
2. System will check the number of products that belongs to that category that are visible:
   1. If visible = 0: Warn about that situation to the user
3. System updates category.
4. System may offer the option to update the products visibility (@see UC-02b ProductManagement-updateProduct)

System will raise and exception if primary key does not exist.

• User must be logged
• User could have ANY ROLE

1. User request for a list of categories.
2. System will query database using provided parameters. If product details are requested then it will be included in response.Product and category i18N fields must be returned in all the configured languages.

None

• User must be logged
• User must have ROLE_ADMINISTRATIVE

1. User request for a category-products update.
2. System will return a detailed category with the current associated products and a list of the rest of available products.
3. User may add/remove products from the list
4. System will receive a list of the new products that will belong to this category: 
   1. Products removed maybe updated removing the category from them.
   2. Products added to the list must be associated now to the current Category.
5. System will check the number of products that belongs now to that category that are visible:
   1. If visible = 0: Warn about that situation to the user.

None