This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
So, Maximo 7.6.0.3, workflow to approve a PR.
The workflow didn't have an AUTOACCEPT person so I created one, and associated it to a user with very high PR limits.
I setup the escalation for the AUTOACCEPT task on WFASSIGNMENT, no problem.
My workflow assigns a PR to a person with zero dollar limits on a PR. This person may or may not have PR limits greater than zero, so I want to avoid moving people into a security group just for this.
The zero-limit person accepts the "Approve" task, and I route it to an autoaccept, thinking the escalation will pick up the assignment and the positive line out of the task can hold an action "PR APPR".
Well, Maximo doesn't like that. I'm getting this beauty: "Maximo BMXAA0042E - A change status action was invoked on business object WFASSIGNMENT. However, this object does not have a status field, and therefore cannot have a status assigned to it. Look at the log files to determine which process is invoking the status"
I could probably write another escalation to change status if the workflow has an active AUTOACCEPT assignment, but that seems torturous to me.
Is Maximo working correctly? I always thought AUTOACCEPT could be used to change a status.
-C
Would this be helpful?
http://www-01.ibm.com/support/docview.wss?uid=swg21618017 http://www-01.ibm.com/support/docview.wss?uid=swg21618017
Travis Herron
Travis, that would defeat the purpose of restricting status changes to end users. But thanks.
I found the weirdness, and it's spooky like Halloween: the PR APPR action was added to the escalation, and not by any human as far as I can tell. Maybe a leftover from a former escalation is all I can think, but I removed it and magic happened as designed.
Case closed, thanks all for reading.
-C