• Created by Unknown User (leslie.obourn), last modified on Oct 20, 2022

UVA-452 - Getting issue details... STATUS


  1. 10/20
    1. Dashboard
    2. J's testing results
  2.  10/18
    1. Get everyone logged in 
      1. Litao to send direct link
    2. Ask someone to do a test
  3. 10/5 Meeting:
    1. App Review
    2. Testing & Deployment timeline
    3. 10/5-14 - Complete Development (in UVA3)
      1. In Progress: BP: Matt to own in partnership with J (for KT)
      2. In Progress: Extend: Litao
        1. Will add to the new dashboard
        2. Pages are set - but need bp to smoke test.
    4. 10/17-21: Begin Unit Test in UVA3
      1. Include: the distribution
      2. Unit Test Kick-off
        1. Dennis to send Sec Admin group users to Matt to set up.
        2. Matt to notify J when sec group is ready.
        3. J to test more scenarios.
        4. Thursday: Review the new dashboard
      3. 2x 90 minute session 
        1. Send ACN avail to Teresa and Vanessa
        2. Vanessa to schedule weekly checkins
    5. 10/24 - Litao & Matt Migrate & Validation to Sandbox
      1. Wed 10/26: 60 minute validation session
    6. 10/27-28 - Migrate to Prod
    7. 10/31: Go-Live Session (sFTP & new Dashboard)
  4. 9/21 Meeting
    1. Litao to walkthrough current progress
    2. Identify timeline

  5. 9/12 Meeting:

    • Decided to go with a new app
      • HCM
        • Roles to be provided
      • FIN
        • Accounting Journal
        • Internal Service Provider (ISP)
        • Customer Invoice
        • Supplier Invoice
        • 1099 Adjustment files
        • FDM Worktags files
        • Banking and Settlement
        • Miscellaneous Payee/Payment
          • Subform
            • Folder (Inbound/ Outbound)
            • Prod/Non Prod
      • Manager approval
      • Lorie Approval - HCM
      • Aarati approval - FIN
      • System admin (same as SIS) for dispositioning
        • Note: no automation right now, but perhaps it can it be like SIS
  6.  Options
    1. Requirements
      1. Approval Requirements:
        1. IT group approves sFTP requests
        2. No routing based on sFTP directory 
      2. Requester enters the sFTP directory - not a validated field.  We could have an Extend drop down (requires ongoing maintenance)
    2. New App
      1. This seems cleanest - because sFTP access is an additional system (it's not WD)
      2. Additional information needed - sFTP Directory needs to be specified (Teresa said they know what sFTP directory they need)
      3. Con: HCM and FIN roles require sFTP access - so it could be a better user experience to combine it.
      4. Could we have the HCM/FIN app launch the sFTP app?
        1. If there is a role that requires sFTP in the grid then when you click OK on one of the HCM/FIN pages it kicks off another BP for the sFTP request.
        2. On the page - if role = sfTP - call the end-point to launch a bp in parallel
        3. Or - could add a Todo and if the role requires sFTP could route a message to the initiator's inbox to inform them to begin an sFTP request.
    3. Add to Part 1 of HCM and FIN App
      1. We don't think this option will work
      2. If we had a selection in part 1 - would need to give Sec Admins the ability to edit (they don't have it now)
      3. Part 1 is a questionnaire that currently doesn't have edits/updates - and isn't part of the dispositioning process (Part 1 is not visible on the questionnaire).
      4. Currently approvals do not see the Part 1/questionnaire - that would need to change for HCM/FIN apps if we use this option and decide we want to use approval steps for dispositioning.
        1. other dispositioning options: new page
    4. New role with subforms in HCM and FIN App
      1. Require a new user-based security group
      2. Extend code update in the App to add a subform
      3. Extend code update for flow
      4. Pro: similar to SIS App
      5. Con: configuration is in the code (instead of ABO) - more maintenance
  • No labels