Maximo List Archive

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.



Workflow - Update Worktype in WO

From: Ian Turner (2016-04-08 11:39)

We have a very simple workflow that is causing us no end of trouble. In
Service Request we have set up a workflow to apply the SR owner, apply SLA
and create a work order. This works fine but the final step we want to make
is to set the work type in the work order. We have an action to do this but
when we try to add it to the workflow it fails. Putting the action in an
interaction works but we need to click the route workflow icon twice to get
it to run to the end. We've tried many different options, one of which will
update then work type but fails to bring across the target start and
completion times as well as the owner which are normally populated by the
crossover. I possibly have given you all little to work with but perhaps
someone out there has come across a similar problem?


From: InComm Solutions Inc. (2016-04-11 13:06)

Can you tell why the action is failing? That’s what I would have done, myself ...


Shannon

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Friday, April 8, 2016 12:40 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Workflow - Update Worktype in WO


We have a very simple workflow that is causing us no end of trouble. In
Service Request we have set up a workflow to apply the SR owner, apply SLA
and create a work order. This works fine but the final step we want to make
is to set the work type in the work order. We have an action to do this but
when we try to add it to the workflow it fails. Putting the action in an
interaction works but we need to click the route workflow icon twice to get
it to run to the end. We've tried many different options, one of which will
update then work type but fails to bring across the target start and
completion times as well as the owner which are normally populated by the
crossover. I possibly have given you all little to work with but perhaps
someone out there has come across a similar problem?


From: clowlong (2016-04-12 07:43)

We use the priority in the service request to change the workorder worktype.
Like priority 4 is a EM and priority 5 is SF for safety...ect.
The workflow of the service request has a wait node - looking for the workorder to complete and then notify the originator of the work completed.
Had some trouble with the worktype -
I have the workorder workflow go right into a sub-process worktype flow first thing.
This changes the worktype and simple thing one at a time.
if priority 1 do this..
if priority 2..and so on
so ..:wopriority = '4'
action - on workorder, set value, 'EM', attribute Worktype.

I can not do interactions on the workorder flow if the request comes from someone that does not have access to the workorder.