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 may require ROLE_PRODUCT_MANAGER

1. User request to obtain a product version by primary key to be modified
2. If version is published system warns user about this fact and recomends to create a new version. System offers the option to force update.
3. System returns product version model.
4. User updates version information. User can updates I18n fields for the defined languages, add new languages or remove an existent one.
5. System receives request and save it to storage.  field will be ignored.
6. PubishDate and UploadDate will not be editable.
7. User may add/remove new artifacts to the current version  
8. (@see UC-04e ArtifactManagement-uploadArtifact and UC-04f ArtifactManagement-removeArtifact)
9. If new artifacts are modified UploadDate must be updated. PublishDate may remain 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 version by primary key.
2. System will warn about the loose of data (versions and storage).
3. User accepts to remove the version.
4. System removes associated artifacts (@see UC-04f ArtifactManagement-removeArtifact). Once delete, it removes the version itself.

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

• User must be logged
• User must have ROLE_ADMINISTRATIVE_USER

1. User request to publish a version. User may update:
   1. Tag values
   2. PublishDate - (Date must be prefilled with current timestamp)
2. System checks that version has not been published yet.
3. System updates tags and publication date.
4. System will notify customers about that new release @see UC-XXa CustomerNotifications -  sendEmail

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

System will raise and exception if current version has just been published