topic Re: Information in workflow records cannot be trusted. in Alfresco Archive

Information in workflow records cannot be trusted.

lyles — Sat, 28 Apr 2012 20:10:50 GMT

It looks like there are a few problems with Alfresco workflows that result in missing or incorrect information recorded in the details of a workflow. The problems occur in Alfresco 4.0.d. and can all be easily reproduced with the out-of-box review and approve workflows. I haven’t tested in any other

Re: Information in workflow records cannot be trusted.

mrogers — Sun, 29 Apr 2012 09:41:00 GMT

Please raise the other two issues otherwise they will not even be considered.

Also a wont-fix does not mean it will never be fixed. The issue is now with project management to consider. I suggest you add some comments with your concern. And my reading of the issue is that it is mainly dealing with who can work on the issue rather than who is in the workflow history.

Re: Information in workflow records cannot be trusted.

lyles — Sun, 29 Apr 2012 20:07:41 GMT

I've added my comment to the related JIRA and raised two new ones:

https://issues.alfresco.com/jira/browse/ALF-13901
https://issues.alfresco.com/jira/browse/ALF-13902

Still looking for advice on how to modify the code myself.
The "Claim" button for pooled tasks assigns the task to the current user. That code and resulting behaviour needs to be duplicated for the accept and reject buttons. But I don't know where to look to find that code.

Re: Information in workflow records cannot be trusted.

lyles — Sat, 05 May 2012 16:34:43 GMT

Could someone look at the two JIRAs that I submitted and explain what happened.

They were both quickly marked as "Fixed", as well as another related JIRA that hadn't seen any activity since February.
I'm new to the process of submitting bug reports for Alfresco and I don't understand what occurred to make them "Fixed".

Re: Information in workflow records cannot be trusted.

mrogers — Sat, 05 May 2012 21:27:23 GMT

The code was fixed! Isn't that clear?

Next step is for QA to validate the fix.

These fixes should be in the Enterprise 4.0.2 service pack.
And the next community release. The one I checked is already on HEAD as well so will be in the "nightly build".