Re: Does the deleteWorkEffort really always works?

2017-01-23 Thread Jacques Le Roux
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

Re: Does the deleteWorkEffort really always works?

2017-01-23 Thread Jacques Le Roux
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

Re: Does the deleteWorkEffort really always works?

2017-01-23 Thread Jacques Le Roux
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.

Re: Does the deleteWorkEffort really always works?

2017-01-23 Thread Rishi Solanki
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

Re: Does the deleteWorkEffort really always works?

2017-01-23 Thread Jacques Le Roux
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

Re: Does the deleteWorkEffort really always works?

2017-01-23 Thread Nicolas Malin
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

Re: Does the deleteWorkEffort really always works?

2017-01-23 Thread Paul Foxworthy
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

Re: Does the deleteWorkEffort really always works?

2017-01-22 Thread Scott Gray
What comments are you looking for? It either works or it doesn't. A couple of things to consider: - Is there really a good reason to delete a WorkEffort record when changing its status should be sufficient? - Maybe it doesn't work now because the data model has changed since it was introduced? -

Re: Does the deleteWorkEffort really always works?

2017-01-22 Thread Jacques Le Roux
I created https://issues.apache.org/jira/browse/OFBIZ-9185 please comment Thanks Jacques Le 19/01/2017 à 21:35, Jacques Le Roux a écrit : Hi, I looked closely and I do not understand how the deleteWorkEffort service can work. Especially when a Workeffort has an established relationship

Does the deleteWorkEffort really always works?

2017-01-19 Thread Jacques Le Roux
Hi, I looked closely and I do not understand how the deleteWorkEffort service can work. Especially when a Workeffort has an established relationship with a RuntimeData. If someone has some clues I'm interested! Also CustRequestWorkEffort is missing in deleteWorkEffort, please confirm if you