I have followed the instructions in this eB wiki:
eB Customization :- Set the “Date Effective” to current date of the system and make it Hard coded.
However, from the document audit history I can see that the date effective is added, but then removed again (see attached). There is no other behaviour set on the template that might be doing this, could something else be causing the date to be overwritten after the extended behaviour sets it?
I have tested this behaviour on our side using custom document creation wizard from Thameslink menu and got same results as you when OnTemplateInstantiated event was used, but when I used OnObjectChanged value was saved. As in screenshot below you can see that custom wizard removed it, but removal was counted as Object Change so automation kicked in again and added value back in.
Below is my configuration of automation I've used.
When event to trigger automation OnObjectChanged is used it's a must to use where clause as in screenshot above, otherwise Date Effective will be update every time when change is done on Object.
Try to create identical automation on your side and see will that work for you.
Answer Verified By: Catherine Marklove