Thanks Nicolas,
Fortunately in my case I could get rid of the FK and deleteWorkeffort then worked like a charm. But I thnought about that this weelend and I see more
the problem lying in the remove-related Minilang feature, see my comment in the Jira
Jacques
Le 23/01/2017 à 11:55, Nicolas
Please answer in the Jira :)
I made a more generic proposition about remove-related there
Jacques
Le 23/01/2017 à 14:31, Rishi Solanki a écrit :
Agree on all points shared by Scott, Paul and Nicolas. Also valid concern
raised in this thread by Jacques. Thanks!
As described by Nicolas, that
Le 23/01/2017 à 11:10, Paul Foxworthy a écrit :
Hi Jacques and Scott,
On 23 January 2017 at 09:08, Scott Gray
wrote:
I can't think of any *good* reasons to remove a WorkEffort record.
Hear, hear. In general, OFBiz expires an entity by setting the thruDate.
Agree on all points shared by Scott, Paul and Nicolas. Also valid concern
raised in this thread by Jacques. Thanks!
As described by Nicolas, that work_effort is complex entity and we should
consider the functional context for it, if we wnat to delete a work_effort.
Still I think, until business
Thanks for your comments, though in OFBIZ-9185 would have been better ;)
I answered there, please do so
Thanks
Jacques
Le 23/01/2017 à 11:55, Nicolas Malin a écrit :
WorkEffort is a complexe entity as much technical aspect as functional cover :)
On the Jacques's case, the workEffort is used
WorkEffort is a complexe entity as much technical aspect as functional
cover :)
On the Jacques's case, the workEffort is used to follow jobSandox
activity after user command and in logical delete all older workEffort
to minimize the history (like jenkins with his scheduler).
After your
Hi Jacques and Scott,
On 23 January 2017 at 09:08, Scott Gray
wrote:
> I can't think of any *good* reasons to remove a WorkEffort record.
Hear, hear. In general, OFBiz expires an entity by setting the thruDate.
What's so special about WorkEffort?
Cheers
Paul