Automation of new users

I am creating my first new flow that will automate our users into S3 and Landmark, but having troubles with getting data back for the initial Landmark query. I'm expecting 2 records; when I pull by one specific member number, I correctly get 1 of the 2 records. However, when I use adjusted hire date (either hard coded or using a variable), I get every record in the system;30 records at a time.

I confirmed the records existed in the database:

1 select employee, adjustedstartdate
2 from employee
3 where trunc(adjustedstartdate) = to_date('15-JUN-2017','DD-MON-YYYY')

EMPLOYEE ADJUSTEDS
---------- ---------
260 15-JUN-17
13950 15-JUN-17

_dataArea="ltmtest" & _module="hr" & _objectName="Employee" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="EmpRequestedTimeOffByPlanRel" & _setName="" & _asOfDate="" & _effectiveDate="" & HROrganization="1" & Employee="" & AdjustedStartDate="<!SystemDate>"

The variable <!SystemDate> is initialized to pfDate(todayAGS(),'yyyymmdd') and is correctly being returned in the log as 20170615.

Any advice would be greatly appreciated.

Thanks,

Mindy Stevens

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

Legacy Contributor

We use Employee_CreateStamp.TimeStamp . We run our flows nightly to get those that were added that day.

jreese

JimY, how do you handle rehires? Our current process, using S3 as the primary source, removes their security rights when they term.

Legacy Contributor

Instead of basing your update on a scheduled query, have you thought of allowed PA action codes of NEWHIRE (or similar functions from PA52) to trigger the process. Thus, you could expand the same functionality to REHIRE (or similar action codes).

jreese

That is what we do now but in both Mindy and Jim's examples they are using Landmark as the source and not Lawson.

Mindy Stevens

As a applications developer, I’m used to being able to code anything I want in any format. I’m trying to maximize my use of the standard PF features, but not sure if I’m missing something or it’s just limitations of IPD.

My first process after Start = LandmarkTransaction (to select those new hire employees with create dates of today). As you suggested, I am using Employee_CreateStamp.TimeStamp in my transaction builder (thanks for the tip!), but how do I set it to truncate the time in the initial transaction to limit my where clause to just the records from today YYYYMMDD?

Legacy Contributor

In the Start node we set a variable to todays date using the following.

dmeDate.substr(6,4)+dmeDate.substr(0,2)+dmeDate.substr(3,2)

Mindy Stevens

Hi Jim,

I have my current date set to YYYYMMDD in the Start Node pfDate(todayAGS(),'yyyymmdd');. The issue is that the Employee_CreateStamp.TimeStamp needs to be truncated to YYYYMMDD as well; but there doesn't appear to be an option to substring the field in the "Value" field of the Landmark transaction.

So, right now, my transaction node isn't finding the records because currentDate variable of 20170619 does not equal Employee_CreateStamp.TimeStamp data of 2017061905023680.

Mindy

Copyright © 2025 Infor. All rights reserved.