Why does DateLastWorked become mandatory when the ExitDate attribute is populated? Is it a bug?

Hello,
I noticed that whenever the ExitDate field is populated on One Identity Manager, the DateLastWorked field becomes mandatory. I noticed because when trying to put a blank Exit Date and a blank Date Last Worked on an Identity that had both attributed populated, both the Angular Web Portal and the back-end tools (Manager and Object Browser) did not allow me to save the changes.

On the documentation I found nothing about this and in the Designer there is no configuration/script that makes the DateLastWorked field mandatory. By checking the DateLastWorked attribute on the Person table via Object Browser, I saw that the MinLen value for the DateLastWorked is 0 when the Exit Date is empty but when the Exit Date is populated, the MinLen value for the DateLastWorked becomes 1.


Is it a bug? How is it possible to disable this?

Kind Regards

Parents
  • To add to Barry's answer, DateLastWorked is crucial to the Identity lifecycle automation in Identity Manager and is normally set to the ExitDate (by a value template). However, you can still override the value manually. You did that by setting it to a blank date and the customer prevented you from creating invalid data.

Reply
  • To add to Barry's answer, DateLastWorked is crucial to the Identity lifecycle automation in Identity Manager and is normally set to the ExitDate (by a value template). However, you can still override the value manually. You did that by setting it to a blank date and the customer prevented you from creating invalid data.

Children
No Data