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 3 Next »

PageUp Overview

For requirements and specifications, see https://uconn.atlassian.net/l/c/X3MvZ3ZC. This is a high level view of PageUp, the job boards, and all integrations involved.

 

PageUp Daily File Import Integrations from KFS, ID System, and CoreCT

The Control-M PageUp jobs (PRD_RPM_BATCH) run at 6:45am every day except Sunday.  These jobs send files to PageUp to update the available pick lists and users.  Users not included in the daily import file will be deactivated.  The User file is created by the Systems-Identity team which we then transfer with a Control-M job.  The other files are sent from either KFS or from Core-CT broker data.  More details on these files are available on Confluence.

 

To view integration files, import settings, and PageUp importer job: System Settings > Integrations.

 

  1. Import Log (files into PageUp). 

  • Here you will see view files that are ready to be imported and files that have been imported.

  • Any files with a status of "Unarchived" have not been ingested by PageUp yet.

  • Any files with a status of "Archived" have been ingested and processed into PageUp.

 

  1. Import Configuration

  • Here you will find the schedule that runs each morning.  The schedule runs at 6,7, & 8 am to process the files that are unarchived in the Import Log.

  • If you need to re-run this schedule at any time, click the "Add to queue" icon under UCONN Imports.  The schedule will queue in kick-off automatically.

  • You can check to confirm that the files have been processed by going back under Import Log.  If the files have moved out of unarchived, then they have been processed by the Import Configuration schedule.

 

  • If at any time you need to re-run the Control-M jobs to resend the files to PageUp, you can do so by running the web services that are triggered by the Control-M job. 

    • An example for this would be to open the Control-M job PRD_RPM_ACCOUNT_TO_PAGEUP1 , copy the URL https://api.rpm.uconn.edu/createAccountFileJob.html and paste the url into your browser window (hit enter).  Accessing the URL will trigger the process that sends the account file to PageUp.  You would do this for each of the Control-M jobs if needed.

 

 

PageUp Job Boards and Integrations

PageUp integrates with 4 different job boards to receive external applicant/application data.  These are (in order of most used) AJO, MathJobs, Police, and Fire.  The integration uses web services to call each site and pull the data.  Data is pulled from all sites via a XML format.  PDFs are provided from the sites that are then stored in PageUp. 

 

Sunday-Friday, there are Control-M jobs that run at 6:45am that take applicants and applications from all sites and sends the data to PageUp.  Before the data is sent to PageUp, it is stored in the aeweb database (Service: "aewebp_srv.uits.uconn.edu").   You may need access to this database if HR has questions on the applicants/applications that have been sent on specific days.  The tables you would use would be JOB_BOARD_APPLICANT and/or PAGEUP_APPLICATION.

 

AJO website (credentials are needed prior to signing in for AJO/Math): https://academicjobsonline.org/ajo

MathJobs: https://www.mathjobs.org/jobs

Dr Yu is the contact for if there are any issues with AJO and MathJobs: yu@math.duke.edu

Police/Fire: There is no portal to log into, for any Admin purpose.  Chris Anton is/was the contact at Websolutions if there are any issues (chris@websolutions).

 

Job Board and other import Files

Control-M Job Names

Police/Fire: PRD_RPM_POLICE_APP_TO_PAGEUP2

AJO: PRD_RPM_AJO_TO_PAGEUP2

MathJobs: PRD_RPM_JAM_TO_PAGEUP2

 

Files imported into PageUp:

  • KFS Files From KFS CA_ACCOUNT_T table

    • Accounts-5-page-up.txt

    • Accounts-3-page-up.txt

    • Accounts-6-page-up.txt

    • Cost-centers-pageup-up.txt

    • Accounts-4-pageup-up.txt

    • Accounts-2-page-up.txt

    • Accounts-1-page-up.txt

  • Users-page-up.txt data is from OpenLDAP, ID System/CoreCT.  Control-M job picks up file from glue server and sends file to PageUp

  • Primary-team-page-up.txt

  • Org Structure From CoreCT UC_CURRENT_TREE table (changed to a table recently from the view that decommissioned)

    • Business-unit-3-page-up.txt

    • Business-unit-2-page-up.txt

    • Business-unit-1-page-up.txt

    • Jointdept2.txt

    • Work_department_non_academic.txt

    • Jointdept1.txt

  • Sites-page-up.txt From CoreCT PS_LOCATION_TBL

 

Integrations Control-M jobs run and call the API for each site.  Process runs to get the XML and send the applicants/applications to PageUp.

  • AJO

  • MathJobs

  • Police/Firefighter App

 

AJO Info

  • Most used Navigation Menu items for ITS:

    • Jobs

      • Selecting a specific job under "Jobs" is recommended prior to using Help or List.  Doing so will filter the data onto a specific job selected.  If you navigate to Help > Data Export prior to selecting a job, you will get all data for all jobs that are still active.

    • Help > Data Export

    • List

 

 

  • When on the AJO site, clicking the "Step by Step" icon in the upper right corner gives a very detailed explanation of the entire portal. 

  • The integration data from AJO can be found under Help > Data Exports.  Here you can find real time XML data that is available for export.  Any data available under Data Export is available when the AJO integration runs.  If the data is not here, it will not be available to the Control-M process in order to be picked up. 

  • The integration from AJO/Math to PageUp is dependent on the PageUp Job ID, which is populated into the XML <Tag> field in AJO/Math.  Without this ID, the integration would not know what jobs in PageUp the AJO/Math applications belong to. HR is responsible for populating this ID into AJO when a new job is created.  Jobs are manually created in PageUp first, then in AJO followed by populating the PageUp Job ID into AJO.

  • Do NOT make any changes under Admin > Config.  The HTML and Mappings on this page are used in the integrations to get specific field values and send them to PageUp using the PageUp data dictionary.  Keep in mind, HR also has the same permission to make changes on this page.  They should know not to make certain changes here to break the integrations. 

 

PageUp specific Info

  • In order to troubleshoot any issues, you will need SuperUser access.  Having this level of access gives you the permission to view AJO/Math and Police/Fire information.  Since PageUp does not have the ability to easily identify if an applicant/application is AJO/Math or Police/Fire, you will need this elevated permission to search for specific Job IDs or names as needed. 

 

An Example for making sure all applications for a specific job made it into PageUp

  1. Pull up 496477 in AJO by navigating to Jobs and clicking on the hyperlink. 

  2. Click the List navigation menu hyperlink. 

  3. Here you will see all applicants that have applied to this job.

  4. Log into PageUp. 

  5. Under Quick search, type 496477 and hit Enter. 

  6. Click the job specific to 496477.

  7. Click View applications.

  8. Here you can see (as of 10:28am on 2022-06-23) there are 10 records.  If you look at the list in AJO; there are also 10 records.  Keep in mind, the AJO number could be higher depending on how many applicants have applied since the job last ran.  The remaining records will be transferred once the job runs the next morning.

 

An Example (leading from above) on how to confirm the applicant data sent in the integrations is from AJO

  1. Click on View application for a specific applicant from the search above.

  2. Notice there is no hint that this applicant/application integrated from AJO.  This is a limitation of PageUp.

  3. Click on History

  4. Here you can confirm the integration originated in AJO.  Looking at the list, you can see a document was created named "AJO-xxxx.pdf".  A PDF is sent for each application from AJO/Math. 

  5. Click on the View hyperlink for the PDF.

  6. Here you can see the AcademicJobsOnline (AJO) applicant info, along with any received materials (Documents: cover letter, CV, teaching statement, references).  AJO includes this all as 1 PDF which is then sent through the integrations to the application in PageUp.  The datestamp in the upper-right of the PDF is the date the PDF was created in the integration.  There is also a stamp in the header of all pages after page 1.  this includes the applicant ID and timestamp of when the documents were uploaded into PageUp.

    1. Application data in PageUp CANNOT be updated through the integration.  This is a limitation of the PageUp API.

    2. The only UPDATEs that are allowed through the PageUp API is for PDFs.  When a PDF is updated through the integration, there is no history of it.  The date/time stamp will also not change.  Only the current PDF will be removed from PageUp and the new PDF from AJO will replace it. 

  7. If for some reason an application needs to be re-imported into PageUp, HR will need to delete out the Application.  ITS can then re-run the integration going back to when the person applied.

 

PageUp integration web services

The following is the AJO web service that will pick up all applicants as of the parameter executeFromDate=yyyy-mm-dd.  If you needed to resend an applicant that applied on 2022-06-10, you would update the date in executeFromDate=yyyy-mm-dd to 2022-06-10. 

  • DO NOT run this web service more than once at any given time, as running it more than once will make the first execution error. 

  • DO NOT set the date to any historical date that will cause stress on the AJO server without first contacting Dr Yu.  In example, setting this to 2019-06-23 while the current date is 2022-06-23 could potentially cause major issues for the servers at Duke. 

  • Redacted URL for purposes of malintent on Confluence.  If you need the URL to call, reference the Control-M job. 

 

More information regarding the details of PageUp and integrations are available on Confluence pages.

  • No labels