Quantcast
Channel: Forum Microsoft Identity Manager
Viewing all articles
Browse latest Browse all 4767

FIM portal MPR triggered only when Employee EndDate was changed at least 1 year behind

$
0
0

Hello All,

Thank you in Advance.

Issue: MPR was not triggered unless the Employee End date was changed to at least 1 year behind

MPR: DisableUserOnEndDate

Transition Set: Employee Type isPayroll, UserStatus is Active,  Employee End Date prior to today

Workflow: [//Target/UserStatus]-> String "Disabled"

FIM portal date format: (GMT+10:00) Canberra, Melbourne, Sydney

What the MPR does? Disable account after the account expired, set the user account status to Disabled

Issue: MPR was not triggered unless end date was set at least 1 year behind.

Scenario tested:

EmployeeEnd Date             |              MPR Triggered?

05/02/2016                                        not Triggered

05/03/2015                                        not Triggered

05/02/2015                                        Triggered

05/03/2015                                        Triggered

The set seems to be working as it should, when account expired the expired accounts became part of the set immediately, but for some reason the set failed to trigger the workflow until the accountExpired over 1 year. Any idea? Thank you.

Cheers,

Adi



Viewing all articles
Browse latest Browse all 4767

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>