Developer Programs
Fintech Integration Network (FIN)
Jack Henry's Integration Program for Fintechs.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
Developer Account
Create a developer acccount to access resources that help you integrate with Jack Henry.
Learn
Shared Responsibility
Learn about shared roles and responsibilities of customers and Jack Henry in open banking.
Developer Use Cases
Find a use case that fits your development needs.
Developer Video Gallery
Watch the latest demos, webinars, and more.
Developer Conference
Connect with industry leaders, gain insights from expert speakers, and explore our latest innovations.
Docs
Admin API
Create solutions for an institution's back office support tools.
Authentication Framework
Map customer identities to your existing system IDs.
Consumer API
Access financial data for user accounts, transactions, and more.
Data Hub
Get deeper access to financial institution data.
Enterprise Event System
Respond to events in real-time using this powerful pub/sub-based solution.
jXchange - REST API
Translate business information between Jack Henry and 3rd-party apps using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and 3rd-party apps using a SOAP-based API.
Operational Data Integration (ODI)
Get customized queries for bulk data needs.
Payments
Embed check deposits, ACH, bill pay, cards, and real-time payments.
Plugin Framework
Embed the best of the fintech world directly into your user's dashboard.
SymXchange
Query Symitar core member accounts, post transactions, run PowerOn scripts, and more.
Xperience
Modern UI that provides consistent visual integration across Jack Henry products.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.

Migrating from PrimeNG v17 to v19

Technical Info > Third-Party Support > Migrating from PrimeNG v17 to v19

Starting with version 18, PrimeNG’s UI component library includes a number of large breaking changes. PrimeNG v19 is the latest version that fully embraces modern Web APIs and eliminates legacy technical debt. A significant update in v18/19 is the new styled mode implementation, which replaces the previous SASS-based approach with a design token architecture utilizing CSS variables.

Component names have been updated for clarity, such as Datepicker replacing Calendar and Select replacing Dropdown. Consistency in naming conventions has been improved across components, ensuring uniformity in CSS class names.

Below is a basic list of steps to take to upgrade your application to use the latest v19 of PrimeNG’s component library. This is not an exhaustive list. Additional information on breaking changes and version updates can be found on the PrimeNG website.

angular.json

  • Remove primeng.min.css from styles array

tsconfig.json

  • Change moduleResolution from node to bundler

package.json

  • Update primeng to 19.1.0

  • Add @primeng/themes: 19.0.5

app.module.ts

  • Convert CalendarModule to DatePickerModule

  • Convert DropdownModule to SelectModule

  • Add import { providePrimeNG } from ‘primeng/config’;

  • Add import { RuiTheme } from ‘@jkhy/responsive-ui-prime-ng’;

  • In the providers section, add

Add the PrimeNG Theme Provider
providePrimeNG({
    theme: {
        preset: RuiTheme,
        options: { darkModeSelector: false }
    }
}),

All markup files

  • Convert <p-calendar> elements to <p-datepicker> elements

  • Convert <p-dropdown> elements to <p-select> elements

Support options
Have questions on this topic?
Join the Responsive UI team in Microsoft Teams to connect with the community.
See something in this page that needs to change?
Send us feedback on this page.
Did this page help you?
Last updated Thu Jul 31 2025