7/25/2019 Updates to Form
- Update Account Holder Type to be read-only and default to Individual
- Remove Expense Type field
- Update Comments field required on Update requests
- Spend Limit ($USD) re-labeled to Monthly Cycle Spend Limit on New requests
- Update requests: label is changed to 'New Monthly Cycle Spend Limit'
- Update requests: enable this field to be editable
- New requests: set this field dependent on standard/frequent and mark as read-only
- Monthly Cycle Spend Limit is less than 5,000 for Standard and less than 10,000 for Frequent
- Value is set dependent on Card Limit
- Single Transaction Limit is always 4999 and read-only
- Update Cycle Limit to Transactions Per a Cycle
- 'New Transactions Per a Cycle' for Updates
- Made Card Limit *required
- Update requests: changes to 'New Card Limit'
- Add Daily Transaction Limit field and set as always 20. read-only.
- Add Default Level 1 Hierarchy field and set as always 10385. read-only, hidden.
- Add Agent Number field and set as always 5402. read-only, hidden.
- Remove Country/Building from address information.
- Update verbiages to remove T-Card and replace with Travel Card
- Update alerts upon form submission for verbiage 'Your card request has been submitted'
- Update Card Limit to be editable in Supervisor and Department Head review stages
- Added in ability to attach documents to form (for SABA certificate).
- Added in functionality to check if User has completed SABA training. (where to store list of NetIDs is TBD)
- if not, User is alerted of link to sign up for training (need exact link)
8/8/2019
-Updated form title to: 'UNIVERSITY TRAVEL CARD'
-Updated various grammar items
-Removed edit button for access approval updating
-Updated Transactions Per Cycle to be read-only when submitting. Can still be updated by Card Admin.
-Monthly Cycle Spend Limit updated to 5,000 (from 4,999) for Standard and 10,000 (from 9,999) for Frequent
-Attachment for SABA certificate is required.
-Updated contact information for Help to huskybuysupport@uconn.edu and updated wording
-Dialog box will show with each new form for SABA certificate training and reminder to attach certificate to form.
- future functionality is to call SABA API for checking to see if user completed training. If not, user cannot complete form and is provided with a link to sign up and complete training. Certificate will not be needed or required with API. (*TBD*)
- current functionality includes a reminder to complete training and to also attach certificate to form.
-dialog box will appear for Affiliate users(Primary Affiliation = Univ Affiliated Employee) or users with no Org information. Access to form is denied and User is provided with an explanation with contact info for questions.
-hid other fields not required on form submission
9/3/2019
- Attached is an update version of the email language. Please let me know if you have any questions.
- The MCC group should say: TCARD for the name with an action of Include
- The link to SABA is still pending as it is not published for production yet – but if you need a place holder, this is the link to the UAT version.
https://uconnsb-storrs.sabacloud.com/Saba/Web_spf/NA1TNB0103/common/leclassview/dowbt000000000011762
- Updated email language: T Card Request Application Email Notifications.docx
9/16/2019
-In Card Admin stage - comment should only be required on a Deny
-Remove Read access for Users in department head, supervisor, and card admin review
-Update link in report Submit creation email to be link from production
-Update name in Travel Card Holder Agreement to be refreshed with each stage
-Added an extra blank space after 'Agent Number' in the Export Data Report to align with validation workbook
-Updated SABA Training link to Live URL and updated display text to 'Travel Card Training Link' https://uconnsb-storrs.sabacloud.com/Saba/Web_spf/NA1TNB0103/common/leclassview/dowbt000000000011762
10/01/2019
-Updated Agent Number to 5581
10/11/2019
Updated Mobile phone field to update if it does not match Business Phone field
Add in Transferred? Field to determine if record has been transmitted to Report yet, or not.
11/15/2019
Added MCC Group 2(Value: TCARD1) and MCC Group 2 Action (VALUE: Include) fields to form.
Added 'Spend Limit' and 'Single Amount Limit' string fields to the form. These fields are sent to the report instead of the currency fields that are visible to the requester on the form.
01/27/2020
-Updated form to not validate NetID field under User Information. Instead, fields will be cleared out upon completion of service call if NetID does not exist in LDAP.
-updated redirect URL for when Users do not have supervisors. URL on Procurement site was changed.
-added a new check for supervisor vs department head. Since delegates could potentially be used, new code has been added to check for if the designee is the same as the supervisor.
//onItemChange of designee table
var reviewerNetId = [];
var table = BO.F_DesigneeTable;
for (var i = 0; i < table.getLength(); i++) {
reviewerNetId.push(get(table.get(i),"F_DesigneeNetId").getValue());
}
BO.F_supervisornetidcheck.setValue(reviewerNetId.join(", "));
//code is placed onItemChange of new field for Designee NetIds
value = BO.F_supervisornetidcheck.getValue()
SupervisorNetId = BO.F_SupervisorNetId.getValue()
if (value.indexOf(SupervisorNetId) !== -1) {
BO.F_SupervisorException.setValue(true)
}
else { BO.F_SupervisorException.setValue(false)
}
04/13/2020
Updated Attestation
Updated initiator to have read access in Delegate maintenance stage (for ajax calls in case delegates are used).
05/26/2020
Added new form for giving departments the ability to see who has requested access to Travel Cards.
08/17/2020
Updated Department Lookup query to include new service. Service will return requests directly under the Org # entered and also requests that report up to the entered org directly or indirectly.
10/05/2020
Added SABA training link to email sent to new user.
Hid Report section on DBC Initiate stage.
10/09/2020
Updated legal language for DBC and Travel Card agreement.
Field Mapping and requirements
FEB Field Label | FEB Field ID | Notes | Read only? | Required? | Conditional Show/Hide | Pre-populated? | Source | |||
ACCOUNT TYPE | Account Holder Type | Required. Must select either Individual (person’s name) or Department (i.e. project, vendor or department name). If Department is selected, proceed to column G (Employee ID). | Account Holder Type | F_AccountHolderType | If 'Department' is selected, set DOB, card last name, home address as not required. Set card first name as department name and set last name as optional and blank current form is set to individual and read-only. Left in department if needed for the future. | yes | yes | yes | dropdown values | |
APPLICANT INFORMATION | Applicant Full First Name | Required for Individual applicant. Legal First Name of the cardholder. Note: The combination of Applicant First Name + Applicant Middle Initial + Applicant Last Name cannot exceed 25 characters. | First Name | F_UserFirstName | yes | Yes | LDAP | |||
Applicant MI | Optional for individual applicant. Middle Initial of the cardholder 1 character Max | |||||||||
Applicant Last Name | Required for Individual applicant. Legal Last Name of the cardholder. | Last Name | F_UserLastName | read only | yes | Yes | LDAP | |||
Date of Birth | Required for Individual applicant. Actual date of birth. Can be entered in the following formats: - MM/DD/YYYY (12/01/1980) - M-D-YYYY (1-1-1981) | Date of Birth | F_birthdate | yes; if individual | New Request | No | ||||
Employee ID | Optional. Employee ID for the cardholder. May be required for third party file feeds Max. 20 characters alpha/numeric. | Employee ID | F_EmployeeId | read only | Yes | Travel Web API | ||||
ACCOUNT SECURITY | Access Code 1 | Required. Four digits: Must be Numeric. Must be unique to the account. Cannot be the same as Access Code 2. Used for cardholder authentication when calling Customer Service. | Access Code 1 | F_AccessCode1 | last 4 digits of employee id | read only | Yes | Employee ID | ||
Access Code 2 | Required. Four characters: Any alpha/numeric combination. Must be unique to the account. Cannot be the same as Access Code 1. Used for cardholder authentication when calling Customer Service. | Access Code 2 | F_AccessCode2 | random 4 digit number (JS) onNew (this field is hidden) | read only | Yes | Random 4 digit number | |||
NAME AS IT WILL APPEAR ON CARD | First Name on Card | Required. First Name for cardholder. For Department cards, enter the entire name to be displayed here, example: "Marketing Department". Note: Combination of First Name on Card + Middle Initial on Card + Last Name on Card cannot exceed 21 characters. | First Name to be printed on card | F_FirstNameOnCard | populated from web service first name. If first+last name greater than 21 characters then invalidate fields and alert user. If for Department, first name on card is populated with Department and last name is blank and optional. | yes | New Request | Yes | first name, Department if request type of Department | |
MI on Card | Optional for Individual applicant. Not applicable for Department applicant. Middle Initial 1 character Max | |||||||||
Last Name on Card | Required for Individual applicant. Last name of the cardholder Not applicable for Department applicant. | Last Name to be Printed on Card | F_LastNameOnCard | populated from web service first name. If first+last name greater than 21 characters then invalidate fields and alert user | read only | yes; if individual | New Request | Yes | Last Name, blank if request type of Department | |
Second Line to Appear on Card | Optional. Second line to be embossed below the name on the card. Max. 21 characters. | |||||||||
ACCOUNT CONTACT INFORMATION | Business Email Address | Required. Business email address of the cardholder. Must enter at least one ‘@’ symbol and at least one ‘.’ in the email address. For Department Card, provide the business email address of the authorized user. No spaces are allowed. Max. 60 characters. | F_UserEmailAddress | yes | Yes | LDAP | ||||
Business Phone Number | Required. Business phone number for the cardholder. For Department Card, provide the business number of the authorized user. Enter 10 digit number, no spaces, slashes, etc., are necessary. The field will be formatted automatically. | Work Phone Number | F_UserPhoneNumber | yes | Yes | Travel web API | ||||
Mobile Phone Number | Required. Mobile phone number for the cardholder. If no mobile number exists, enter home or business phone number. For Department Card, provide the mobile number of the authorized user. No punctuation. Enter 10 digit number, no spaces, slashes, etc., are necessary. The field will be formatted automatically. | Mobile Phone Number | F_MobilePhone | Populated from Business Phone Number | yes | Yes | Business Phone Number | |||
ACCOUNT MAILING ADDRESS | Mailing Street Address 1 | Required. First address line for the cardholder. Address for statement delivery. Max. 36 characters. | Department | F_UserOrganization | Populated with Department Name | yes | New Request | Yes | Department Name | |
Mailing Street Address 2 | Optional. Second address line for address provided. Max. 36 characters. | Mailing Street 2 (work address 1 + 2) | F_MailingStreet2 | //F_WorkStreetAddress + F_WorkStreetAddress2 will check to see if address 1 + 2 combined exceeds 36 characters | New Request | Yes | work street address 1 + 2 | |||
Mailing City | Required. City for the Mailing Address provided. Letters, numbers, periods, and spaces are allowed. Max 24 characters. | City | F_WorkCity | yes | New Request | Yes | Travel web API | |||
Mailing State | Required. State for the Mailing Address provided. Only the 50 states of US, DC, or Military Codes AA, AE, & AP are allowed. Must be 2 character state abbreviation | State | F_WorkStateProvince | yes | New Request | Yes | Travel web API | |||
Mailing ZIP Code | Required. Zip code for Mailing Address provided. Enter 5 or 9 digit zip code. Example: 60612, or 601300024 | Zip/Postal Code | F_WorkZipPostal | special characters will be auto removed if entered. Field limit is 5-9 max characters. | yes | New Request | Yes | Travel web API | ||
HOME ADDRESS | Home Street Address 1 | Required for Individual applicant. Home Address for the Physical address is required (no P.O. box). Max. 36 characters. | Home Address Line 1 | F_HomeAddress1 | yes;individual | New Request | No | |||
Home Street Address 2 | Optional for individual applicant. Second address line for Home address provided. Max. 36 characters. | Home Address Line 2 | F_HomeAddress2 | New Request | No | |||||
Home City | Required for Individual applicants. City for Home Address provided. Letters, numbers, periods, and spaces are allowed. Max 24 characters | City | F_HomeCity | yes;individual | New Request | No | ||||
Home State | Required for individual applicants. 2 digit State for the Home Address provided. Only the 50 states of US, DC, or PR (Puerto Rico) are allowed. | State/Province | F_HomeState | no more than 2 alpha characters | yes;individual | New Request | No | |||
Home Zip Code | Required for Individual applicants. Zip Code for Home Address provided. Enter 5 or 9 digit zip code. Example: 60612 or 606121076 | Zip/Postal Code | F_HomeZip | special characters will be auto removed if entered. Field limit is 5-9 max characters. | yes;individual | New Request | No | |||
CARD CONTROLS | Spend Limit | Required. A spend limit per cycle must be provided for the cardholder for the cycle. No punctuation. The field will be formatted automatically. Max is $9,999,999 | Monthly Cycle Spend Limit | F_SpendLimit | limit to less than or equal to 5,000 for standard; less than or equal to 10,000 for frequent | yes | -Dependant on Card Limit selection (standard/frequent) -re-labeled if Update request | Yes | ||
Cycle Transaction Limit | Optional. Use this field to restrict the number of times the card account can be used per cycle. Max 8 digits. | Transactions Per a Cycle | F_CycleLimitNumber | limit to less than or equal to 100 for standard; limit to less than or equal to 200 for frequent | -Dependant on Card Limit selection (standard/frequent) -re-labeled if Update request | Yes | ||||
Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction. No punctuation. The field will be formatted automatically. Max is $9,999,999 | Single Transaction Limit ($USD) | F_TransactionLimit | limit to less than 5000. static value | Yes | Yes | ||||
Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent in a day. No punctuation. The field will be formatted automatically. Max is $9,999,999 | blank | ||||||||
Daily Transaction Limit | Optional. Use this field to restrict the number of times the card account can be used per day. Max 8 digits. | Daily Transaction Limit | F_DailyTransactionLimit | static value of 20 | Yes | Yes | ||||
Cash Advance Limit | Optional. Use this field to restrict the cash limit per cycle. Required if MCC Group 1 is used for Cash. No decimals. Field will be formatted automatically. Max. cash limit is $2,500 | blank | ||||||||
HIERARCHY | Default Level 1 Hierarchy | Required. Enter the bank provided value at the time of set-up. Default is to use the company Level 1 Hierarchy. Enter a 5 digit number. | Default Level 1 Hierarchy | F_Defaultlevel1Hierarchy | static value of 10385 | Yes | Yes | |||
Level 2 Hierarchy | Optional. Enter the bank provided value at the time of set-up. Enter a 5 digit number. | |||||||||
Level 3 Hierarchy | Optional. Enter the bank provided value at the time of set-up. Enter a 5 digit number. | |||||||||
Level 4 Hierarchy | Optional. Enter the bank provided value at the time of set-up. Enter a 5 digit number. | |||||||||
Level 5 Hierarchy | Optional. Enter the bank provided value at the time of set-up. Enter a 5 digit number. | |||||||||
Level 6 Hierarchy | Optional. Enter the bank provided value at the time of set-up. Enter a 5 digit number. | |||||||||
MCC GROUP NAME 1 | MCC Group Name 1 | Required. Enter the name of the Merchant Category Code Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. For Cash access: use this field to enter the name of the Merchant Category Code Group controlling cash access. | MCC Group Name 1 | F_mccGroupName1 | TCARD | yes | Yes | |||
MCC Group 1 Action | Required. Select from the drop down: Include or Exclude. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include For Cash access: select Include. | MCC Group 1 Action | F_mccGroup1Action | Include | yes | Yes | ||||
MCC GROUP 1 SPEND AND TRANSACTION LIMITS | MCC Group 1 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. If MCC Group Name 1 is for cash, this amount cannot exceed the value of Cash Advance Limit. No punctuation. Field will be formatted automatically. Max is $9,999,999 | ||||||||
MCC Group 1 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. For Cash access, not applicable. Max is 7 digits | |||||||||
MCC Group 1 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. No punctuation. Field will be formatted automatically. For Cash access, not applicable. Max is $9,999,999 | |||||||||
MCC Group 1 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. No punctuation. Field will be formatted automatically. For Cash access, not applicable. Max is $9,999,999 | |||||||||
MCC Group 1 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. For Cash access, not applicable. Max is 7 digits | |||||||||
MCC GROUP 2 | MCC Group Name 2 | Optional. Enter the name of the Merchant Category Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. Required If MCC Group 1 has "Cash" access | MCC Group Name 2 | F_mccGroupName2 | TCARD1 | yes | yes | |||
MCC Group 2 Action | Optional. If MCC Group Name 2 is selected, this field is Required. Select from the drop down: Exclude or Include. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include | MCC Group 2 Action | F_mccGroup2Action | Include | yes | yes | ||||
MCC GROUP 2 SPEND AND TRANSACTION LIMITS | MCC Group 2 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. Max is 7 digits | ||||||||
MCC Group 2 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. Max is 7 digits | |||||||||
MCC Group 2 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. Max is 7 digits | |||||||||
MCC Group 2 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. Max is 7 digits | |||||||||
MCC Group 2 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. Max is 7 digits | |||||||||
MCC GROUP 3 | MCC Group Name 3 | Optional. Enter the name of the Merchant Category Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. | ||||||||
MCC Group 3 Action | Optional. If MCC Group Name 3 is selected, this field is Required. Select from the drop down: Exclude or Include. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include | |||||||||
MCC GROUP 3 SPEND AND TRANSACTION LIMITS | MCC Group 3 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. Max is 7 digits | ||||||||
MCC Group 3 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. Max is 7 digits | |||||||||
MCC Group 3 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. Max is 7 digits | |||||||||
MCC Group 3 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. Max is 7 digits | |||||||||
MCC Group 3 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. Max is 7 digits | |||||||||
MCC GROUP 4 | MCC Group Name 4 | Optional. Enter the name of the Merchant Category Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. | ||||||||
MCC Group 4 Action | Optional. If MCC Group Name 4 is selected, this field is Required. Select from the drop down: Exclude or Include. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include | |||||||||
MCC GROUP 4 SPEND AND TRANSACTION LIMITS | MCC Group 4 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. Max is 7 digits | ||||||||
MCC Group 4 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. Max is 7 digits | |||||||||
MCC Group 4 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. Max is 7 digits | |||||||||
MCC Group 4 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. Max is 7 digits | |||||||||
MCC Group 4 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. Max is 7 digits | |||||||||
MCC GROUP 5 | MCC Group Name 5 | Optional. Enter the name of the Merchant Category Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. | ||||||||
MCC Group 5 Action | Optional. If MCC Group Name 5 is selected, this field is Required. Select from the drop down: Exclude or Include. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include | |||||||||
MCC GROUP 5 SPEND AND TRANSACTION LIMITS | MCC Group 5 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. Max is 7 digits | ||||||||
MCC Group 5 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. Max is 7 digits | |||||||||
MCC Group 5 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. Max is 7 digits | |||||||||
MCC Group 5 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. Max is 7 digits | |||||||||
MCC Group 5 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. Max is 7 digits | |||||||||
MCC GROUP 6 | MCC Group Name 6 | Optional. Enter the name of the Merchant Category Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. | ||||||||
MCC Group 6 Action | Optional. If MCC Group Name 6 is selected, this field is Required. Select from the drop down: Exclude or Include. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include | |||||||||
MCC GROUP 6 SPEND AND TRANSACTION LIMITS | MCC Group 6 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. Max is 7 digits | ||||||||
MCC Group 6 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. Max is 7 digits | |||||||||
MCC Group 6 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. Max is 7 digits | |||||||||
MCC Group 6 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. Max is 7 digits | |||||||||
MCC Group 6 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. Max is 7 digits | |||||||||
MCC GROUP 7 | MCC Group Name 7 | Optional. Enter the name of the Merchant Category Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. | ||||||||
MCC Group 7 Action | Optional. If MCC Group Name 7 is selected, this field is Required. Select from the drop down: Exclude or Include. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include | |||||||||
MCC GROUP 7 SPEND AND TRANSACTION LIMITS | MCC Group 7 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. Max is 7 digits | ||||||||
MCC Group 7 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. Max is 7 digits | |||||||||
MCC Group 7 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. Max is 7 digits | |||||||||
MCC Group 7 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. Max is 7 digits | |||||||||
MCC Group 7 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. Max is 7 digits | |||||||||
MCC GROUP 8 | MCC Group Name 8 | Optional. Enter the name of the Merchant Category Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. | ||||||||
MCC Group 8 Action | Optional. If MCC Group Name 8 is selected, this field is Required. Select from the drop down: Exclude or Include. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include | |||||||||
MCC GROUP 8 SPEND AND TRANSACTION LIMITS | MCC Group 8 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. Max is 7 digits | ||||||||
MCC Group 8 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. Max is 7 digits | |||||||||
MCC Group 8 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. Max is 7 digits | |||||||||
MCC Group 8 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. Max is 7 digits | |||||||||
MCC Group 8 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. Max is 7 digits | |||||||||
MCC GROUP 9 | MCC Group Name 9 | Optional. Enter the name of the Merchant Category Group chosen for the cardholder. This is obtained from the MCC Group Worksheet. Max 10 alphanumeric characters. | ||||||||
MCC Group 9 Action | Optional. If MCC Group Name 9 is selected, this field is Required. Select from the drop down: Exclude or Include. This is obtained from the MCC Group Worksheet and relates to the MCC Group Name entered for the cardholder. Default: Include | |||||||||
MCC GROUP 9 SPEND AND TRANSACTION LIMITS | MCC Group 9 Cycle Spend Limit | Optional. Use this field to restrict the amount that can be spent per cycle for the MCC Group. Max is 7 digits | ||||||||
MCC Group 9 Cycle Transaction Limit | Optional. Use this field to restrict the number of transactions per cycle for the MCC Group. Max is 7 digits | |||||||||
MCC Group 9 Single Amount Limit | Optional. Use this field to restrict the amount that can be spent on a single transaction for the MCC Group. Max is 7 digits | |||||||||
MCC Group 9 Daily Amount Limit | Optional. Use this field to restrict the amount that can be spent per day for the MCC Group. Max is 7 digits | |||||||||
MCC Group 9 Daily Transaction Limit | Optional. Use this field to restrict the number of transactions per day for the MCC Group. Max is 7 digits | |||||||||
Card Design | Agent Number | Required. 4 digit Agent Number that defines the card design to be used. Default: Company Info Agent Number (from Company Info tab). Enter 4 digit Agent Number if different from Company Info default. | Agent Number | F_AgentNumber | static value of 5581 | Yes | Yes | |||
Alternate Mailing Address | Card Delivery Site ID Number | Optional. 5 digit Site ID given to you by JPMC which will determine the alternate address where replacement cards are mailed. | ||||||||
ACCOUNT PARAMETERS | Executive Card | Optional. Use this field to request an Executive Card by entering "Y". A fee may apply. Default: N Executive: Y | Executive Card | F_ExecCard | static value of N | |||||
Declining Balance | Optional. Approval required. Default: N Declining Balance: Y | Declining Balance | F_DecBalance | static value of N | ||||||
Declining Bal Effective Begin Date | Optional. Declining Balance use only. Can be entered in the following formats: - MM/DD/YYYY (12/01/2017) - M-D-YYYY (1-1-2018) | |||||||||
Declining Bal Effective End Date | Optional. Declining Balance use only. Can be entered in the following formats: - MM/DD/YYYY (12/31/2017) - M-D-YYYY (1-31-2018) | |||||||||
ACCOUNTING CODE | Accounting Code | Optional. General Ledger string associated with the cardholder. Max. 75 characters, dashes and spaces allowed. |
-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
Questions:
-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