Consume-before-date of non-persistable objects

1
I have been trying to find this in the documentation, but I am not finding an anwers for this, so I hope to get this here. If I have a non-persistable object in my domain, with a relation to administration.account at what time does this object goes "poef"? or to reverse the question which action/circumstance drops the object and the association ?
asked
2 answers
0

AFAIK only when your session is 'ended' (logout, inactivity etc)

answered
0

The issue stays the same, on login you need to fill the non-persistant entity with data, since it will be empty on log-in. So the 'Outstandig issues' need to be persistant, since this has data that need to be commited. the workload objects COULD be non-persistant if created on the spot, but personally I'd make those persistant too in case of logging / reporting.

Maybe I'm not sure how your app is functioning though. Which entity is non-persistant in your example?

answered