and more in a single search tool across platforms. Read the announcement here. |
05/30/2023 09:06 PM
I have an update form using which HR can process an immediate exit for any user in the company. The enddate that HR can select can be any value, (past, present or future). However, when the form is submitted and a request number is generated, I need CP59 of the user to be updated with now() [current UTC timestamp] to capture when the immediate exit was submitted for the user. When I configure the default value as ${new Date()} and type as Date, nothing is getting stored on CP59 of the user. I have a dynamic attribute defined and mapped to CP59 and have selected the option to hide on create and hide on update for the dymanic attribute (name is termTimestamp).
05/30/2023 10:25 PM
@krecpond can you try to use 'Single Select from SQL query' instead and see if that helps?
select DATE_FORMAT(NOW(), '%Y-%m-%d %H:%i:%s') AS ID
05/31/2023 06:41 AM
Below is a screenshot of the termTimestamp DA configuration in the Identity Lifecycle under Global Configurations.
The logs show that there is no such property
Any suggestions on how to resolve this error?
05/31/2023 10:56 PM - edited 05/31/2023 11:09 PM
@krecpond here is what you can do, as the end date is an attribute that will be updated by HR, you can make the below changes to the enddate and the termTimestamp DAs to set a parent child mapping with your config
For enddate:
for termTimestamp:
So when the HR updates the enddate and submits the request, it updates the cp59 value with current date in UTC