Uploaded image for project: 'Domain Models'
  1. Domain Models
  2. DMOD-160

Design and implement Users, Auth and Permission business-logic module

    XMLWordPrintable

Details

    Description

      As described in LIBAPP-12 and STRIPES-183 even a simple UI screen to edit/create users requires a non-trivial series of calls to multiple backend modules (in this example: mod-auth, login, perms). This indicates that we need a server-side business-logic module that understand the relationships between the modules and exposes simple endpoints (like edit user) that perform various operations (and error handling) behind the scenes. Thus alleviating the UI from the complex business logic.

      Step 1.

      • Design a set of operations and schemas for the new business-logic module. Re-use existing schema by creating compound object where possible.

      Step 2

      • Implement and expose endpoints required by the UI: create and update User, migrate the UI client (component) over to the new endpoints

      TestRail: Results

        Attachments

          Issue Links

            blocks

            New Feature - New feature requests FOLIO-506 include users-bl in the bb

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests STRIPES-227 Re-wire User edit and view screens to the BL module

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            duplicates

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LIBAPP-163 Manage patron groups association on the user screen

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            New Feature - New feature requests DMOD-197 Update item status as part of creating or updating a loan

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Umbrella - FOLIO-463 Discuss and design platform support for building/deploying business-logic modules

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Umbrella - FOLIO-490 Convention for paths of storage and business logic resources

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests DMOD-198 Include item information in loans

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests DMOD-202 perform a join users-patron groups in the users BL

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests DMOD-208 reimplement how user's permissions are retrieved to the UI/client

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. STRIPES-244 ui-users: use stripes-connect to post new users's credentials and permissions

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. UIU-304 Rewrite the Users module to use stripes-connect throughout

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                kurt Kurt Nordstrom
                jakub Jakub Skoczen
                Heikki Levanto, Hongwei Ji, Jakub Skoczen, Kurt Nordstrom, Matt Connolly, Mike Taylor, Niels Erik Gilvad Nielsen, Wayne Schneider
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 weeks, 1 hour, 30 minutes
                    2w 1h 30m

                    TestRail: Runs

                      TestRail: Cases