Future Dated Transactions

Is there a way within IPA to find futured dated transactions? Currently our HRIS team maintains a spreadsheet of future dated ChangeRelationshipToOrganization actions where an Employee's Relationship status is going from active to Term Pending. Once that action has processed on the effective date, then they can submit another ChangeRelationshipToOrganization action to change the Relationship from Term Pending to Termed.

Ideally, it would be nice for the ability to submit multiple future dated ChangeRelationshiptToOrganization transactions on an employee, one to go from Active to Term Pending and another to go from Term Pending to Termed. The reason we cannot go directly from Active to Termed, is we have to allow a 30 day grace period to ensure the Employee has been issued their final Paycheck for things like Paying out their PTO bank.

The end goal is to eliminate the manual process of tracking the futured dated transactions on a spreadsheet. I opened an incident with Support on how we can find futured dated transactions within HR Talent and/or IPA and I was directed to contact our CSM to have Manage Services get involved. I feel like there should be a way to identify these specific future dated transactions within the system.

I appreciate any insight people may have.

Thank you

Don

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

Legacy Contributor

Hi Don,

To handle future-dated records, we created a Replication Set that was configured to contain "Future Effective Entries". That setting is in a Drop Down choice for the Business Class you are replicating.

In general, our process is to use Replication Sets to create Documents, and then an ION Data Flow uploads that data into the Data Lake. Our IPA flows query the Data Lake.

Thanks,

David

cleverly

Within LPL there is syntax to find when a record "has future changes" (see the FullFieldName definition on page 13 of the current LPL guide).

I'm not certain whether IPA's Landmark node would accept the syntax (it might; I've never tried), but even if it doesn't, you could use Config Console to define a User Condition that used it:

—and then your LM Transaction Node in IPA could query it.

Similarly, config console user fields can use "for each audit log records" to get access to both past changes and future pending ones.

Here is an example of a derived field that would build up an HTML-formatted change log snippet that would list the actions and when they occurred and would bold (and highlight with asterisks) those that are future (cf. pages 20 and 21 in the LPL guide):

[Other things to note: if you needed to make a custom relation from one business class to another, and wanted to limit it to records that were future dated, the syntax is listed on page 43. Probably not relevant to your immediate situation, but if you ever implement your own user business classes and need special handling when future changes become effective, it's worth reading about the difference between Commit Rules and Audit Entry Rules on page 55.]

jreese

We have the same setup here except we wait for 21 days to change from Term Pending to Term Final. What we do is run a flow daily that looks for any employee that is in a Term Pending status with a Termination Date that is more than 21 days ago and create the action request to change their status to Term Final. HR only has to enter the initial term action.

don-kintzle

Thanks everyone for the responses. Keep the suggestions coming as I'm sure I could use them for other future uses. JReese, I believe your approach should work for our needs, I think I was just trying to make it more complicated than it needed to be.

Copyright © 2025 Infor. All rights reserved.