![]() |
VOOZH | about |
OutSystems is a low-code platform which provides the tools for companies to developer, deploy, and manage omnichannel enterprise applications. When paired with CData Connect AI, you get instant, cloud-to-cloud access to Paylocity data for business applications. This article shows how to create a virtual database for Paylocity in Connect AI and build a simple app from Paylocity data in OutSystems.
The CData Connect AI provides a pure cloud-to-cloud interface for Paylocity, allowing you to build reports from live Paylocity data in OutSystems β without replicating the data to a natively supported database. As you create applications to work with data, OutSystems generates SQL queries to gather data. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to Paylocity, leveraging server-side processing to quickly return the requested Paylocity data.
Connectivity to Paylocity from OutSystems is made possible through CData Connect AI. To work with Paylocity data from OutSystems, we start by creating and configuring a Paylocity connection.
Set the following to establish a connection to Paylocity:
This property is required for executing Insert and Update statements, and it is not required if the feature is disabled.
Paylocity will decrypt the AES key using RSA decryption.
It is an optional property if the IV value not provided, The driver will generate a key internally.
You must use OAuth to authenticate with Paylocity. OAuth requires the authenticating user to interact with Paylocity using the browser. For more information, refer to the OAuth section in the Help documentation.
The Pay Entry API is completely separate from the rest of the Paylocity API. It uses a separate Client ID and Secret, and must be explicitly requested from Paylocity for access to be granted for an account. The Pay Entry API allows you to automatically submit payroll information for individual employees, and little else. Due to the extremely limited nature of what is offered by the Pay Entry API, we have elected not to give it a separate schema, but it may be enabled via the UsePayEntryAPI connection property.
Please be aware that when setting UsePayEntryAPI to true, you may only use the CreatePayEntryImportBatch & MergePayEntryImportBatchgtable stored procedures, the
InputTimeEntry table, and the OAuth stored procedures. Attempts to use other features of the product will result in an error. You must also store your OAuthAccessToken
separately, which often means setting a different OAuthSettingsLocation when using this connection property.
π Configuring a connection (Salesforce is shown)
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the connection configured and a PAT generated, you are ready to connect to Paylocity data from OutSystems.
The steps below outline connecting to CData Connect AI from OutSystems to create a new Paylocity database connection.
Once you create the database connection for Paylocity, you can create an extension that maps the tables or views to OutSystems entities. If you have not already done so, create an Application in Service Studio.
At this point, you can access and work with Paylocity data just like you would with the standard OutSystems entities.
With Connect AI and OutSystems, you can easily build Paylocity-connected applications. Request a free trial of Connect AI and start working with Paylocity data in OutSystems today.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial