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 9 Current »

GENERAL LEAP APPLICATION NOTES (also see Confluence under Enterprise Financial Systems > HCL LEAP Applications)


USDP Status Report System

  • Status Report form pulls data from other forms (Vendor, Project, Certified Company).
  • Utilities form is used by USDP (Veronica Cook) to upload list of Certified Companies.  List is uploaded via a CSV file format.
  • Each Vendor is individually created under the Vendor form using affiliate NetIDs.  Veronica Cook has a process where she requests affiliate NetIDs for the vendors.
  • Once a Vendor exists, Projects can then be created with the assigned vendor alias NetID.
  • the PDF creation is done using JS which calls app.getSharedData().FillPdf() to api.finance.uconn.edu.  The service fills the PDF, archives the PDF on the server, and returns it back to the user.


University Expense Card Request

  • Consists of two workflows for Employee Travel Cards and Student Travel Cards.  Each process utilizes the same form but with different workflow. 
  • Flags are used to determine which workflow to route the form through.
  • Certain elements on the form will change depending on the flag set.  Examples of this include:

           -The title will be UNIVERSITY TRAVEL CARD for employees and STUDENT TRAVEL CARD for students.

           -Specific sections/fields will show or be required

           -fields are populated with specific values as required by the BOA (Bank Of America) upload template

  • Students do not create Student Travel Card forms by launching the form.  The student forms are initially created by a Control-M job that runs each day.  The students are notified via LEAP email that a form is pending for them to complete.  There is a Concur file that the Control-M job picks up which then creates forms for each record in the file.  More specific details are on Confluence.
  • Once forms are approved out of the Expense Card Admin stage, a record is created under the Report table.  Each record is created in a specific format so that the Bank Of America (BOA) import template can be populated directly from the Export out of the LEAP dashboard.  Specific instructions were created at the time for Business Services to Export the data (available on Confluence).
  • This application contains its own department delegate approval, as delegates are not typically allowed for Travel Cards with the exception of the President's Office. 
  • As the President will not approve forms, specific code was included where the President's NetID is included to replace the President of UConn with their specific delegate approver.  This will need to be changed whenever the President is replaced.


Enterprise Financials System Access Request

  • When adding users into roles, make sure to also add them into the System Review form as well (KFS Admin, Reporting, etc.).
  • This application contains workflow for access requests with these applications: Asset Panda, HuskyBuy, KFDM, SADM, KFS.
  • Unlike the University Expense Card application that uses the same form for 2 workflows, this application uses 2 different forms; 1 for each workflow.  1 form for Asset Panda, HuskyBuy, KFS, KFDM, a 2nd form for SADM.
  • Application contains department delegate approvers for each department under Delegate Admin form.
  • Once the department head approves either KFS or SADM form, the LEAP service is called to create a form in the Systems Review application below.
  • If Asset Panda is selected and the department head approves, the asset team receives a link to the form.  Dave Ferreira's group does not need to approve or review the form.  The user is notified at a later point from Asset Panda that their access is all set. 
  • The SADM form contains specific functionality that allows dynamic assignment of reviewers dependent on the options selected on the form for each data steward.  If all 4 options are chosen on the form for each data steward area, then all 4 groups will need 1 person to approve.  If only 1 data steward area is selected, then only 1 area needs to review the form.


Enterprise Financials System Access Request - System Review

  • Direct form creation by an employee is turned off with this application with .unauthorizedAccessWarning() on the Event onNew.
  • Forms are only created in this application through the LEAP API from Enterprise Financials System Access Request and Concur Role Access Request. 
  • There are two forms used depending on if the form is KFS related (including Concur) or SADM.  All KFS forms first go to the KFS team for review.  Forms are assigned as needed to KFDM and other ad hoc approval. 



Employee-Spousal Tuition Waiver

  • This application contains workflow for employee tuition waivers, spousal tuition waivers, and flexible schedule requests.  As of now, the flexible schedule request is fully operational; although forms are only created through the LEAP API when a ETW or STW form is submitted.  Direct submissions for a flexible schedule are turned off with a function.
  • There is a good amount of logic in this application that triggers off of listeners stored in the Events.  If you make any changes or enhancements, I would highly recommend searching all events for the IDs that would be affected along with checking Rules and Services.
  • There is a diagram on the Confluence page that gives you an idea of all the listeners that are connected.  If there is a service triggered, chances are there is a listener stored under Events for it.


Dependent Tuition Waiver

  • DO NOT upgrade prod2 with prod1 nitro without first updating the URLs to remove the dev extension.  Doing so will make the LEAP production application post to the DTW DEV database.  I have a specific process to update the URLs without going 1-by-1 in the LEAP application.
  • The users do not use the LEAP dashboard for this application.  The Main Menu (F_MainMenu1) form is their dashboard. 
  • Take all other precautions as with ETW for listeners.  We did not use the LEAP API to POST to the external DBs.  GETs are used with JS to get around the LEAP issues with POST.  In other areas, a GET was used in order to post through to the aeweb API in order to get around the LEAP limitation.
  • When updating HR users, update HR group 2 with group 1 users so that both groups match (for both UCHC and UConn).


  • No labels