Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1544

Pivot Vendor App into Organizations App

    XMLWordPrintable

    Details

    • Template:
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      XL < 15 days
    • Confidence factor:
      Medium
    • Estimation Notes and Assumptions:
      See comments
    • Development Team:
      Thunderjet
    • Calculated Total Rank:
      100
    • Rank: Chalmers (Impl Aut 2019):
      R1
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: hbz (TBD):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Leipzig (ERM Aut 2019):
      R1
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      Overview: The FOLIO system requires the ability to keep track of organizations, some of which are generic/non-vendor and others (vendors) which have more details specified.

      Background: Whether an organization is considered a "vendor" has been identified as the main distinction here. In order to increase the flexibility of Vendors such that they can be used effectively by modules other than orders to represent both vendor and non-vendor organizations . This feature aims to convert what we call a "Vendor" into an "Organization" that can take on the role of "Vendor".

      Requirements:

      • An organization with the "Vendor" flag enabled must be able to perform all the functions of the current Vendor
      • Update the labels in APIs, Schemas, and other Documentation accordingly

      UI Stories needed:

      • When assigning an org to an order, limit to organizations that have function: can be assigned to orders (may have implication for organization lookup widget)
      • When assigning an org to an invoice, limit to organizations that have function: can be assigned to invoice (may have implication for organization lookup widget)
      • When assigning an org to an agreement, limit to organizations that have function: can be assigned to agreements (may have implication for organization lookup widget)
      • When assigning an org to a license, limit to organizations that have function: can be assigned to license (may have implication for organization lookup widget)
      • When assigning an org to an eUsage record, limit to organizations that have function: can be assigned to eUsage (may have implication for organization lookup widget)
      • Question: Any other record types that need organizations assigned to them?
      • Change the vendor lookup plugin to organizations lookup plugin (do we need to add some sort of understanding of function or role? should only suggest organizations that can be assigned to that particular type of record)
      • Clean up documentation (see MODVEND-89)
      • Get rid of as many trivial bugs as we can (see small stories and bugs in UXPROD-1603)
        [no additional fields needed in Agreements or Interfaces in the short term]

      Additional information to be provided as analysis continues.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                dennisbridges Dennis Bridges
                Reporter:
                dennisbridges Dennis Bridges
                Back End Estimator:
                Craig McNally Craig McNally
                Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases