SFS - How to request additional access for testing in SFDEV

Guidelines for requesting test access to pages in SFDEV for test accounts or functional staff completing testing.


The following steps must have been completed prior to requesting test access:

For temporary test access (Access to be tested for functionality, but not being assigned to an existing SFS role at this time)
  1. Security Task JIRA has been created, linked to a development JIRA, assigned to 'Team: SFS Security'. If available, please provide Business Purpose for requested test access.
For permanent access (Known changes made to existing SFS roles)
  1. Development System Change JIRA has been created, with a completed Change Request Form attached, and approval from UWSA noted on the JIRA.
  2. Security System Change JIRA has been created, linked to the development JIRA, with a completed Change Request Form attached, and approval from UWSA noted on the JIRA.


For test Page Access:
In order to add requested page access, the following information should be provided on the Security System Change or Task JIRA:
  1. Information for each page is required:
  • Menu
  • Component
  • Page
  • Requested Authorized Action (available authorized actions are page dependent, but a full list can be found here: https://kb.wisc.edu/erp-security/internal/page.php?id=64164)
  • Existing or test users to add access to. For details on requesting test accounts please see: [Link for document 66336 is unavailable at this time]
    1. Required information from above added to Security System Change or Task JIRA and assigned to 'Team: SFS Security'.
    2. SFS Security will review request and send back if any information is missing.
    3. If the requested access is temporary, SFS Security will create a test role to be assigned to users or test accounts. 
    4. If the requested access is being added to an existing SFS role, SFS security will implement approved changes in SFDEV, and note changes made on the Security JIRA.
    5. Security JIRA will be assigned back to developer for validation, and will include test account information if requested.
    6. If any additional security changes are needed, add an additional comment to the JIRA with information required above, and assign back to 'Team: SFS Security'.

    Keywords:SFS, SFDEV, Shared Financial System, developers, access, request, JIRA, UWSA, support, functional, test   Doc ID:66332
    Owner:Peter V.Group:ERP Security
    Created:2016-08-22 13:59 CSTUpdated:2016-08-22 14:26 CST
    Sites:ERP Security
    Feedback:  0   0