IdM Rockstar
Adam Callen
Search Archives
"One of the top Identity Management Strategists in the market today!"
Welcome to my Identity Management blog with focus on proven implementation stratigies, best practices, product selection, and where I open my expertse to You!
Fortune 100, Higher Education, Government... I've done it all. I'm 7 feet tall, live in NYC, tattooed, and love a challenge! Here's what I've learned...
0
ERROR [PeopleSoftAction] Not satisfied the filter condition
If you’re receiving this error in your logs when running a PeopleSoft recon, here’s the problem (so lame…):
In the Oracle Xellerate Connector Pack – Version: 9.0.4.1, some test data was incorrectly left in the Connector Pack 9.0.4.1 release for the PeopleSoft User Management and PeopleSoft Employee Reconciliation connectors! This test data causes a custom filter to be applied to the Change Based Reconciliation which will reject most (or all) incoming reconciliation events (awesome…). This issue is only with the Change based reconciliation of PeopleSoft User Management and PeopleSoft Employee Reconciliation connectors of Connector Pack 9.0.4.1.
Workaround
To resolve this problem, edit the file “configureReconciliation.properties” in the PeopleSoftApp war file. The following lines you should be replaced:
#Filter attributes
Lastname=Test
DeptId=100
Postal=108
Operator=or
with
#Filter attributes
Lastname=
DeptId=
Postal=
Operator=
After replacement, you must reconstruct and re-deploy the war file using the standard procedures for your specific application server. This change will remove the filter entirely, and allow all data to flow through change based reconciliation.
Back to top