Overview of Configurations

Info

Sam Im (Deactivated) and Mary Jo Kochendorfer (Deactivated) are holistically reviewing the current status of configuration. We will review if there is currently and admin screen, bulk upload (via the reference seed tool), sequencing of the configuration. Please reach out if you'd like to support or with any feedback to help us understand how the current configurations work and deciding how we want to improve or define the "to be" state. FYI Wesley Brown and Sebastian Brudziński

To populate the spreadsheet please use the following instructions for each column :

Column A: Table - Sam Im (Deactivated) Pulled a list of tables from reference data(done), requisitions, stock management, fulfillment, auth, cce
Column B: Component/Service - which service the table is within.
Column C: Relevant for Configuration - Determine if each table is relevant for user configuration. Some tables are not populated nor configured by the user. Rather it is a populated and used within OpenLMIS to support the workflows and transactions.
Column D: Where the configuration happens - Some tables are configured within a grouping, like Orderables, because it makes more logical sense to users. We want to identify those groupings or abstractions so that we understand how each table that needs user configuration is being accounted for.
Column E: Is the table and attributes included in the Configuration Guide? - To determine where are gaps are within the configuration guide.
Column F: View Admin screen - Identify if the table viewable through an admin screen. This means a user can see, through the UI, the information in that table.
Column G: Edit Admin screen - Identify if the table is editable through an admin screen. This means a user can edit the data in the table directly through the UI, NOT uploading an csv/excel or file.
Column H: Ref Seed Tool - Identify if the table can be populated via an csv upload. This means a user can upload a csv of data to set the configuration for the table but CANNOT download the current data in the system. UPLOAD only. The new upload overrides the current data in the system
Column I: UI Batch upload Screen - Identify if the table is editable through a batch upload admin screen. This means a user can first download the current data in the table into a csv and then update the file, and re upload the data into the table. This overrides the current data.
Column J: Sequence for setup and configuration for the first time - we want to identify the order of configuration to ensure we are clearly communicating what must happen first and what is dependent on what. There may be lineitems which should happen simultaneously with other lineitems. Sam Im (Deactivated) to advise on how we should address this.

Notes for filling out the spreadsheet:

To fill out the status on the Reference Seed Tool, we will need input from Ben Leibert and Sebastian Brudziński on what is currently working or broken
For sequence, there was an initial attempt done here: Configuringthesystemthroughrequisitions. Not sure the best approach to filling out the order.

Source: https://docs.google.com/spreadsheets/d/1m6q1zYSval3RLrfT9LRA6DSmV1RMoNjBcBM4GdUkJms/edit?usp=sharing