Configure product code attribute

Description

As an implementer, I want to decide to display the product code attribute on the requisition form so that I can mirror our current requisition form and potentially decrease the amount of information on the forms (or increase the accuracy by including the product code since product names may be similar).

The product code serves as the unique identifier for each product/commodity that can be requested and fulfilled by storeroom managers.

Products/commodities are associated with facilities and programs so that only the relevant products/commodities are displayed on the form.

Acceptance Criteria
Verify that:

  • users can rename the product code label if desired

  • the source of the product code attribute is the reference data

  • the product code data validations are upheld (it needs to be unique)

  • it is not required to be displayed on the requisition form

  • if selected to be displayed, it should be first ( or does it need to come first or can it be reordered? Or does it not really matter?)

Attachments

2

QAlity Plus - Test Management

Checklists

Activity

Paulina Borowa 
July 13, 2016 at 6:45 AM

All works
Checked for this test cases:
-Create Program.
-Create Requisition Template.
-Change requisitionTemplateColumn label values.
-Change requisitionTemplateColumn source values.
For more details please see report below.

Paweł Lal 
July 11, 2016 at 10:14 AM

Anna Czyrko test should only include adding and editing column with new parameter (source). Other functionality can be tested only with integration tests for now (and it's okay, because we don't have UI to test it). Same with OLMIS-811.
Sample requests are provided in the link above.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Original estimate

Time tracking

2d 2h 55m logged20m remaining

Components

Sprint

Fix versions

Priority

Time Assistant

Created July 6, 2016 at 8:19 PM
Updated August 29, 2016 at 12:01 PM
Resolved July 13, 2016 at 6:45 AM