on Dec 22, 2016In the workflow, I updated the Change Request Table with the value of last working day in Delay_Date column, expectation is to have a delay until it equals the fulfillment date. But still the workflow is getting through with the fulfillment phase.
Question is apart from Change Request Table, do we need to update the delay date in any other tables?
As far as I know, this is not the only place where this information is stored.
Probably it's stored also is WP tables as well.
Consider using Delay node (with SQL Delay configured) instead of modifying internal tables.
What use case are you trying to solve by this approach?
There are multiple scenarios for termination. Among which, one scenario is to trigger the change request based on the last working day(read as dd-Mon-yy).
I tried with rules (Attribute change and termination rule), but its not triggering the change request.
Even I tried SQL delay with the below query.
select LastWorkingDay from pv_users where USER_ID = '${access_request_cri_meu_userId}'
Here I created the user attribute "LastWorkingDay" with data type string, due to which, its not working as expected?
The sql query should return a date value as mentioned...
You can change the query to convert that string to date like below if you know the format will be like 'DD-MON-YY'.. Note that the column should hold the date value by the time delay node executes...
select to_date(LastWorkingDay, 'DD-MON-YY') from pv_users where user_id = '${access_request_cri_meu_userId}'
The sql query should return a date value as mentioned...
You can change the query to convert that string to date like below if you know the format will be like 'DD-MON-YY'.. Note that the column should hold the date value by the time delay node executes...
select to_date(LastWorkingDay, 'DD-MON-YY') from pv_users where user_id = '${access_request_cri_meu_userId}'