Hi Andreia,
I sometimes face a situation, where I want to access the data via SQL and the values are not yet written / available for different reasons.
In these cases I move those "read" actions from the path to the OnEntry and everything works fine.
I'm not sure whether this would apply in this case though. The technical field would be set via a form rule and if you use the for each operator in the automation then you should be able to access the actual value. If it is set to true you could set a automation local parameter and decide whether to send a mail or not using this parameter after the for each operator.
The WFHistoryElements shouldn't use a count but should compare the HDT_DETID column of the previous version. In the worst case an old row get's deleted and a new one get's added which would result in the same count.
Best regards,
Daniel
Hi Daniel,
I was reading all the messages again and I saw I didn't wrote correctly what I want to achieve.
The idea is to alert another user that a new row was added. I'm not interested in getting the row information on the email, just check if there's a new line to inform the user that he/she needs to go in the instance.
I've trying to check the options under the history tables, I think the count for example will simply what I actually need but I'm not sure on how to create a condition where you compare new version with last version for that instance.
Did you implemented something like that in your developments?
Thank you