Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Current »


Form Features Include:

  • 6 Main stages:
    • Form Submission
    • Org Review
    • Confidentiality Signing
    • (checked in - read only)
    • Data Steward Review (checked out for review)
    • Reporting Admin Review
  • 5 new access groups for the data stewards:
    • Student Record
      1. Stacy Storrs

      2. Brian Rockwood

    • Student Financials

      1. Kelly Shedd

      2. Tanya Osuba

    • Admissions

      1. Julie Decandia

      2. Dawn Jones

    • Grad Student Review

      1. Lisa Pane

      2. Julie Decandia

    • Reviewers Group (dynamic open group)
  • The users in the groups are granted access dynamically to each form depending on system access selected by the form initiator
    • ie:  Selecting Student Records on the form will add the Student Records data stewards to the Reviewers Group.  Selecting CRSE (this is a separate environment with more global access) will add ALL data stewards to the Reviewers Group. 
  • 3 new stages:
    • Confidentiality Agreement
    • Read-Only (to check out the form for editing)
    • Update (to update the form once it is checked out.  Form will be checked back into the Read-Only stage if further review is required)
  • Confidentiality Agreement stage
    • If the initiator of the form is not the User requesting access, the form will route to a new stage where the User has to log in and sign the form.  The form will then route to the data stewards for approval. 
  • A Check-in/Check-out process
    • Data Stewards will check-out the form in order to edit and approve.  After the Org Manager approves the form, the form goes into a Read-Only stage (ST_Read).  When a Data Steward clicks the check-out button, it sends it to a new stage (ST_Update).  Once in the Update stage, the form is locked for review by the current Data Steward.  The form will only unlock if the Data Steward approves or if a certain time limit window is reached (I have this currently set to 1 hour).  There is also a way for an Admin user to have the ability to submit the form even if it’s open by another user( I currently have this disabled). 
  • Form History for the entire form
    • History is tracked from form start to end by the stage action buttons.  Each stage has different fields which are stored into the history. 
  • Automatic tracking of the number of system options selected for access and the number of data stewards that need to approve.  Once all stewards approve, the form will auto route to the End stage (which will transmit to the System Review App once that is set up). 
    • approval is tracked by the number of data options selected.  once 1 approval is left, JS will trigger the final stage action button to transmit to Reporting Admin Review.

Current SADM Request process (requirements):

https://datawarehouse.uconn.edu/ubis-data-warehouse-access-process/


RTM/Use Cases/Test Cases:



SADM Flow Simple.vsdx

SADM Flow.v3.vsdx


Changes


08/14/2019

-Removed Organizational Reviewer comment box as required


06/04/2019

-Added in description boxes for each Data Source (student records, student financials..)

-Added in Review Data Source Selections to be dynamically dependent on Data Source selected on form submission

-(System Review) Hid extra information if form is to be assigned for review

-Updated for spelling/grammar (undergraduate, graduate, Data Mart(two words))

-Added in Affiliate Department

-Made Reporting Role editable in Update/check-out stage


1/27/2020

-Updated form to not valid NetID field under User Information.  Instead, fields will be cleared out upon completion of service call if NetID does not exist in LDAP.






  • No labels