Share all details related to your problem, including any error messages you may have received.
Hi and Hello,
I have problem with time machine because is not working. I add configuration. Change date for future. Change enddate on identity. Start task refresh.(on identity, I check boxes inside). Nothing happend. Status was not change, trigger not start, and I know it work without time mashine.
I also have only one server and I use rapid setup.
Any hints? I think maybe I can not use time machine with rapid setup?
@ashutosh08 Hi, like I said I have only one server. Identity date I not change, I only change date in time machine for future to have enddate before to start leaver.
@ashutosh08
Yes, I have trigger on change attribute. Which is starting workflow. Everything works when I wait for correct date. Identity is terminate. I want to use timeMachine to not manipulate date on cube, only on date in IIQ.
As per my understanding if there is any process which will update identity like workflow or task then you need to check why it is not considering changed future date.
But automatically just by date change in Time Machine you will not get identity attribute changed.
@ashutosh08 No. Everything works on workflow and trigger when I do not use time machine. I know that time machine will not terminate user. I want use this tool for tests. If I am correct in iiq you can not use time machine for rapid setup (leaver).
I need this info that somebody use time machine with rapid setup and how it works.
You can only trigger events that are supposed to run on future date using timeMachine. But you have to make sure your attribute is changed in order to trigger this future date events.
Attribute changes will not automatically take place until there is some process to pick new date and update identity attribute.
If date on cube (enddate) passed Trigger and than workflow start, change status and other staff. It only works when I wait to correct date or it works when I do some manually changes on debug. I want to use timeMachine for test, without debug change on attribute.
I also think this is not possible with rapid setup.
You can use some custom tasks to read the current date and then update the identity date once you have changed the time via timeMachine and in this way your workflow will trigger without you manually changing the time via debug.
@AdamVentum I spent some time investigating where RapidSetup gets current date and unfortunately I found Date now = new Date();
this mean RapidSetup will ignore timeMachine.
Why would someone do that at Sailpoint btw?
Warning, marketing here !!! Such test case could be easily handled by ITF
Didn’t notice that @kjakubiak already mentioned that above already.
!!! Such test case could be easily handled by ITF