Page Comparison

Important Info

Whenever a new person is assigned as President for UConn, the President's NetID needs updating under event onItemChange of F_supervisornetidcheck.  Currently this is set to ram10007.  This is so that any employees directly reporting to the president will always go to the president's delegate for supervisor review.

Screenshot of NetID:

Image Added

To update the delegate for the President's Office use the Administration Tab within the Responses section of the app.

Diagram Overview

Instructions for Business Services: 

Field Mapping and requirements:

Business Requirements:

Only the User in need of a card can initiate and submit the form

Supervisor needs to approve

Department head needs to approve

Card Admin Group needs to approve

Data needs to be able to be exported (this is possible in a module called View Responses)

Specific fields needed (as provided in PPT)

Supervisor information should auto return via web service

User must 'I agree' to agreement

-After the Card Admin Group approves and the form is in the Final stage, what action is needed? – A report needs to be sent to Nancy/Elise with the requested card information in the JPMC format.  There should be a step for “sent for processing” and then Nancy/Elise will flip it to “Completed” after they upload said report.

-Who should be in the Card Admin Group? – Nancy Patrylak and Elise Fiorentino

Specific Logic/Rules in form:

• Web Service (LDAP) is used to return initial employee information (netid, name, email, org, phone number)
• Web service logic (new web service built specifically for this), inputs Employee NetID to RPM table to return Employee info from Core(not LDAP) and supervisor netid,name,email.
  • If employee does not have a supervisor, look up next level Org and return approver for that Org
  • If no supervisor exists, form will return an error to contact card admin administration

-If supervisor and department head are the same, only 1 approval is required from that person

-Certain fields will appear depending on if the request is new or an update(see conditional requirements below)

-Form will story a history of all stage actions taken (user submits form, supervisor approves, dep. Head approves, card admin approves)

-form currently gives the option to change department and department head for the 'Department' reviewer.  Some users may not be assigned to a department but may have a supervisor (affiliates/students). – Can we talk about this?

-if Department head is the User submitting the form, the department head approver will route to the next level org and pull in the next level Department head

Updates to the form since inception

7/25/2019 Updates to Form

...

if (value.indexOf(SupervisorNetId) !== -1) {
BO.F_SupervisorException.setValue(true)
}
else { BO.F_SupervisorException.setValue(false)
}

04/13/2020 

Updated Attestation

27 Apr 2020 

...

Updated legal language for DBC and Travel Card agreement.

Field Mapping and requirements

...

-What is needed as a Card agreement/data access agreement that the User has to agree to? (I have a generic 1 liner here currently) – The cardholder agreement is attached here.  We were going to have people print, sign, and attach but if we can put all of this information into the attestation and get a electronic signature, that is fine as well.

-What is needed in the 'report'? (the form has the ability to return all data in a spreadsheet, just not in a specific format out of the box) – Attached is the format that is required by JPMC.  We will get you a version with date filled in soon as there are some columns that will need to be hard coded with the same information for each applicant (and this data isn’t on the application)

-Fields?

• What fields should the user be able to modify? – Please see the table below – we updated it.

Business Requirements:

Only the User in need of a card can initiate and submit the form

Supervisor needs to approve

Department head needs to approve

Card Admin Group needs to approve

Data needs to be able to be exported (this is possible in a module called View Responses)

Specific fields needed (as provided in PPT)

Supervisor information should auto return via web service

User must 'I agree' to agreement

Logic/Rules in form:

• Web Service (LDAP) is used to return initial employee information (netid, name, email, org, phone number)
• Web service logic (new web service built specifically for this), inputs Employee NetID to RPM table to return Employee info from Core(not LDAP) and supervisor netid,name,email.
  • If employee does not have a supervisor, look up next level Org and return approver for that Org
  • If no supervisor exists, form will return an error to contact card admin administration

-If supervisor and department head are the same, only 1 approval is required from that person

-Certain fields will appear depending on if the request is new or an update(see conditional requirements below)

-Form will story a history of all stage actions taken (user submits form, supervisor approves, dep. Head approves, card admin approves)

-form currently gives the option to change department and department head for the 'Department' reviewer.  Some users may not be assigned to a department but may have a supervisor (affiliates/students). – Can we talk about this?

-if Department head is the User submitting the form, the department head approver will route to the next level org and pull in the next level Department head