Use Cases - UC-03 Versions

• User must be logged
• User must have ROLE_PRODUCT_MANAGER

1. User request to add a product
2. System returns version creation form.
3. User add general version information. I18N fields (release notes and links) will be provided for the prefered_language.
4. UI offers to define new languages: One option it's to copy current texts to a new language or fill the empty fields.
5. PubishDate and UploadDate will not be editable and will be empty when it's created.
6. System receives request and save it to storage. 
7. System may offer the option to add artifacts to the product(@see UC-04e ArtifactManagement-uploadArtifact)

• User must be logged
• User must have ROLE_ADMINISTRATIVE_USER
• User may require ROLE_PRODUCT_MANAGER

1. User request to obtain a product by primary key.
2. System returns product detailed model.
3. User updates general product 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. PRODUCT_KEY AND VISIBILITY field will be ignored.
5. Licensed product field may only be editable by productManagers. By default keeps unchanged.

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

• User must be logged
• User must have ROLE_ADMINISTRATIVE_USER

1. User request to remove a product by primary key.
2. System will warn about the loose of data (versions and storage).
3. User accepts to remove the product.

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 product visibility by primary key
2. System will check the number of versions that are published:
   1. If visible = 0: Warn about that situation to the user
3. System updates product.

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