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.
Hi, I'm new to 7.5. Currently in version 5.2 and testing 7.5 functionality in a development environment.
In version 5.2 we have a simple work request process that automatically enters requests into a work order workflow and populates associated fields with data entered into the request. 7.5 appears to be a little different. I created a brief SR workflow and used an interaction node to create a work order from the SR. The Targetstartdate that was entered into the SR does not carry over to the associated work order that is created, although the work order does reference the SR#
Confused by what is happening here. Am I approaching this incorrectly. We are a small site and just want to be able allow users to enter a work request that will move into a work order workflow that moves through an approval process based on criteria entered into the SR. Thanks for any clues/direction anyone can provide!!!
I can't remember if the SR to WO crossover domain is out of the box, if so
you need to add target start to it. If not, you need to create a crossover
domain to pull values from SR to WO.
Kevin Wertz
Grifols Therapeutics
Clayton NC
On Tue, Aug 20, 2013 at 6:05 PM, glenholtsea <holtaudio@gmail.com> wrote:
> **
>
>
> Hi, I'm new to 7.5. Currently in version 5.2 and testing 7.5 functionality
> in a development environment.
> In version 5.2 we have a simple work request process that automatically
> enters requests into a work order workflow and populates associated fields
> with data entered into the request. 7.5 appears to be a little different. I
> created a brief SR workflow and used an interaction node to create a work
> order from the SR. The Targetstartdate that was entered into the SR does
> not carry over to the associated work order that is created, although the
> work order does reference the SR#
>
> Confused by what is happening here. Am I approaching this incorrectly. We
> are a small site and just want to be able allow users to enter a work
> request that will move into a work order workflow that moves through an
> approval process based on criteria entered into the SR. Thanks for any
> clues/direction anyone can provide!!!
>
>
>
Thanks much. The consensus I'm getting is to create the crossover.
I was used to work request in version 5.2 being in the same table so didn't have to consider that.
--- In MAXIMO@yahoogroups.com, Kevin Wertz <wertzee@...> wrote:
>
> I can't remember if the SR to WO crossover domain is out of the box, if so
> you need to add target start to it. If not, you need to create a crossover
> domain to pull values from SR to WO.
>
> Kevin Wertz
> Grifols Therapeutics
> Clayton NC
>
>
> On Tue, Aug 20, 2013 at 6:05 PM, glenholtsea <holtaudio@...> wrote:
>
> > **
> >
> >
> > Hi, I'm new to 7.5. Currently in version 5.2 and testing 7.5 functionality
> > in a development environment.
> > In version 5.2 we have a simple work request process that automatically
> > enters requests into a work order workflow and populates associated fields
> > with data entered into the request. 7.5 appears to be a little different. I
> > created a brief SR workflow and used an interaction node to create a work
> > order from the SR. The Targetstartdate that was entered into the SR does
> > not carry over to the associated work order that is created, although the
> > work order does reference the SR#
> >
> > Confused by what is happening here. Am I approaching this incorrectly. We
> > are a small site and just want to be able allow users to enter a work
> > request that will move into a work order workflow that moves through an
> > approval process based on criteria entered into the SR. Thanks for any
> > clues/direction anyone can provide!!!
> >
> >
> >
>
>
>
>