We have one requirement to set the leaver notice date on the basis of leaver’s date (another identity attribute which is calculated further from another transform), actually if leaver date has 31.12.9999 ( dummy date to define no planned exit) then this transform evaluate value to null but if leaver date has another valid date other than 31.12.9999 then it should set current date with this transform and to ensure that the value of current date should not get changed on the daily basis of identity refresh. do we have anything in transform to support such implementation.
if leaver date has 31.12.9999 then notice date will be null
if leaver date has some valid date other than 31.12.9999 then it should set current date and once it set it doesn’t change on daily basis.
Also the current Date will get now operation which will not same value tomorrow. This will change value tomorrow. Lets say Leaver Notice condition met today will set but tomorrow again it will change the value to tomorrow’s date. I have tried below transform to implement the logic but I am sure the value would change in future once this transform would evaluated
@iamnithesh@lampard08 Experts seeking your help on this, could you please suggest if this can be done via transforms or we need to implement rule only to solve this requirement.
IF the attribute already has a value (it’s not null or empty), KEEP that existing value.
ELSE IF the leaver conditions are met (Leaver Date is valid), SET it to now.
ELSE, set it to null.
Attribute Name: Ensure leaverNoticeDate (in the existingValue section) matches the exact Technical Name of the identity attribute you are currently creating/editing.
Hi Rahul, Will it be changed on daily basis let suppose if my leaver date has some other date 31.12.9999 my notice date would be changed to current date as per the transform 2026-03-23 will it be 2026-03-24 tomorrow 2026-03-25 and so on. if yes then it should not be updated on daily basis
@LearningStar As per Rahul’s logic, it should not change. Because in his transform, it is mentioned that if existing value is not equal to null then it retains the existing value and the existing value is calculated from LeaverNoticeDate identity attribute. Did you try it?
Hey, I don’t have access to any tenant right now, its still in discovery phase, and one thing if this transform can retain the previous value then I think it should be good
there could be an other way of doing this. where are you getting this date from? from transform i see you are getting an account attribute from successfactors. does success factors also send this end date? if so you can consider using that date directly successfactors. the above transform works but in case of rehire or similar, i assume your date needs to reflect what you are getting from source.
Hi @lampard08 we are getting this from terminated date which is also coming via another transform on the basis of two attributes (last working day , end date) whichever is available we are using it on leaver date, and further this leaver date we are using to derived the notice date. this is the entire flow.
Hi @rahulb635 This transform would result in appending the current date as per the current implementation , do we have any way to restrict it from appending the current date if it set once.
I m still stuck on this transform would appreciate your help if you guys can suggest what is wrong here as I tried so many combinations but none of them is working, filter condition is the main issue what I understood from transform.