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.



Re: [MAXIMO List] ESCALATIONS

From: Shannon Sutton (2012-07-19 15:59)

I am in 7.5 but i believe escalations setup is the same.. If you could list out all the steps that you have completed it would also help trace down other issues or send some screen shots directly to my email.. Don't worry about the ignorance.. I believe we all learn by error, google and yahoo groups :)
Shannon Sutton
Cell: 571-970-7965
On Jul 19, 2012, at 6:39 PM, zeroxpectations@yahoo.com wrote:
> Thanks for the response, Shannon. I'll definitely give ur suggestions a try. I am new to this part of Maximo so please excuse my ignorance. Thanks and I'll let you know my results!
>
> On Jul 19, 2012, at 5:27 PM, Shannon Sutton <ssutton@emcor.net> wrote:
>
> > You date range is causing it not to yield any data.. using a '7/18/12' is
> > setting time to 7/1/18 00:01:00. I prefer to use a between or you could use
> > a (statusdate >= getdate()-1), but try your query from the where clause in
> > workorder tracking to make sure it yields the correct data before applying
> > to an escalation..
> >
> >
> > Also as long as the Repeat check box is not checked under escalation point
> > it should not repeat data that matches the query..
> >
> >
> >
> > Shannon Sutton
> > CMMS Specialist
> > EAM/IBM-Tivoli Maximo
> > EMCOR Government Services
> > Office: 571-403-8940
> > Cell: 571-970-7965
> >
> >
> >
> >
> > From: Zeroxpectations <zeroxpectations@yahoo.com>
> > To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> > Date: 07/19/2012 05:09 PM
> > Subject: [MAXIMO List] ESCALATIONS
> > Sent by: MAXIMO@yahoogroups.com
> >
> >
> >
> >
> >
> >
> > Need a little help from you Maximo Pros out there. I am starting to mess
> > with escalations and am running into a problem. I am trying to set up an
> > automatic notification when a Work Order has been cancelled and send it to
> > the originator. Currently I set my escalation up like this: STATUS =
> > 'CAN' and STATUSDATE >= '7/18/12'
> > The schedule is set to 15 minutes for testing purposes, but this formula
> > isn't yielding any notifications. Also, looking at this a bit more I am
> > thinking that if this did work it would not get me what I want because, for
> > example, if a work order is cancelled today and the system runs the
> > escalation and notifies me then when it runs again it will notify me of the
> > same Work Order cancellation.....this could be a problem as time goes on.
> > Perhaps I am trying to use the wrong app for what I am trying to
> > accomplish?
> >
> > Anyways, although this is a very simple process for some of you out
> > there any guidance you can provide would be much appreciated. Even if that
> > included links to literature on the topic. Thanks.
> >
> > Maximo v6.2.6
> > SQL 2002 Server
> >
> >
> >
> >
> >
> >
> > This message is for the named person's use only. It may contain confidential,
> > proprietary or legally privileged information. No confidentiality or privilege
> > is waived or lost by any mistransmission. If you receive this message in error,
> > please immediately delete it and all copies of it from your system, destroy any
> > hard copies of it and notify the sender. You must not, directly or indirectly,
> > use, disclose, distribute, print, or copy any part of this message if you are
> > not the intended recipient.
> >
> >
> >
>
>
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.


From: zeroxpectations (2012-07-19 20:41)

Ha! If I can't get it to work using ur previous suggestions I just might take you up on ur offer! Thanks
On Jul 19, 2012, at 6:59 PM, Shannon Sutton <ssutton@emcor.net> wrote:
> I am in 7.5 but i believe escalations setup is the same.. If you could list out all the steps that you have completed it would also help trace down other issues or send some screen shots directly to my email.. Don't worry about the ignorance.. I believe we all learn by error, google and yahoo groups :)
>
> Shannon Sutton
> Cell: 571-970-7965
>
> On Jul 19, 2012, at 6:39 PM, zeroxpectations@yahoo.com wrote:
>
> > Thanks for the response, Shannon. I'll definitely give ur suggestions a try. I am new to this part of Maximo so please excuse my ignorance. Thanks and I'll let you know my results!
> >
> > On Jul 19, 2012, at 5:27 PM, Shannon Sutton <ssutton@emcor.net> wrote:
> >
> > > You date range is causing it not to yield any data.. using a '7/18/12' is
> > > setting time to 7/1/18 00:01:00. I prefer to use a between or you could use
> > > a (statusdate >= getdate()-1), but try your query from the where clause in
> > > workorder tracking to make sure it yields the correct data before applying
> > > to an escalation..
> > >
> > >
> > > Also as long as the Repeat check box is not checked under escalation point
> > > it should not repeat data that matches the query..
> > >
> > >
> > >
> > > Shannon Sutton
> > > CMMS Specialist
> > > EAM/IBM-Tivoli Maximo
> > > EMCOR Government Services
> > > Office: 571-403-8940
> > > Cell: 571-970-7965
> > >
> > >
> > >
> > >
> > > From: Zeroxpectations <zeroxpectations@yahoo.com>
> > > To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> > > Date: 07/19/2012 05:09 PM
> > > Subject: [MAXIMO List] ESCALATIONS
> > > Sent by: MAXIMO@yahoogroups.com
> > >
> > >
> > >
> > >
> > >
> > >
> > > Need a little help from you Maximo Pros out there. I am starting to mess
> > > with escalations and am running into a problem. I am trying to set up an
> > > automatic notification when a Work Order has been cancelled and send it to
> > > the originator. Currently I set my escalation up like this: STATUS =
> > > 'CAN' and STATUSDATE >= '7/18/12'
> > > The schedule is set to 15 minutes for testing purposes, but this formula
> > > isn't yielding any notifications. Also, looking at this a bit more I am
> > > thinking that if this did work it would not get me what I want because, for
> > > example, if a work order is cancelled today and the system runs the
> > > escalation and notifies me then when it runs again it will notify me of the
> > > same Work Order cancellation.....this could be a problem as time goes on.
> > > Perhaps I am trying to use the wrong app for what I am trying to
> > > accomplish?
> > >
> > > Anyways, although this is a very simple process for some of you out
> > > there any guidance you can provide would be much appreciated. Even if that
> > > included links to literature on the topic. Thanks.
> > >
> > > Maximo v6.2.6
> > > SQL 2002 Server
> > >
> > >
> > >
> > >
> > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> >
> >
> >
> >
>
> This message is for the named person's use only. It may contain confidential,
> proprietary or legally privileged information. No confidentiality or privilege
> is waived or lost by any mistransmission. If you receive this message in error,
> please immediately delete it and all copies of it from your system, destroy any
> hard copies of it and notify the sender. You must not, directly or indirectly,
> use, disclose, distribute, print, or copy any part of this message if you are
> not the intended recipient.
>
>
>
>
>
>
>
>
>
>
>


From: Ian Wright (2012-07-20 08:58)

You don’t need a date, just

status = ‘CAN’

Escalation point elapsed time interval = statusdate uncheck the repeat flag

Check with the e-mail administrators that your mxserver is trusted or do a communication to yourself from the workorder and see if you get it

Rgds Ian

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of zeroxpectations@yahoo.com
Sent: 20 July 2012 01:42
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] ESCALATIONS



Ha! If I can't get it to work using ur previous suggestions I just might take you up on ur offer! Thanks

On Jul 19, 2012, at 6:59 PM, Shannon Sutton <ssutton@emcor.net<mailto:ssutton%40emcor.net>> wrote:

> I am in 7.5 but i believe escalations setup is the same.. If you could list out all the steps that you have completed it would also help trace down other issues or send some screen shots directly to my email.. Don't worry about the ignorance.. I believe we all learn by error, google and yahoo groups :)
>
> Shannon Sutton
> Cell: 571-970-7965
>
> On Jul 19, 2012, at 6:39 PM, zeroxpectations@yahoo.com<mailto:zeroxpectations%40yahoo.com> wrote:
>
> > Thanks for the response, Shannon. I'll definitely give ur suggestions a try. I am new to this part of Maximo so please excuse my ignorance. Thanks and I'll let you know my results!
> >
> > On Jul 19, 2012, at 5:27 PM, Shannon Sutton <ssutton@emcor.net<mailto:ssutton%40emcor.net>> wrote:
> >
> > > You date range is causing it not to yield any data.. using a '7/18/12' is
> > > setting time to 7/1/18 00:01:00. I prefer to use a between or you could use
> > > a (statusdate >= getdate()-1), but try your query from the where clause in
> > > workorder tracking to make sure it yields the correct data before applying
> > > to an escalation..
> > >
> > >
> > > Also as long as the Repeat check box is not checked under escalation point
> > > it should not repeat data that matches the query..
> > >
> > >
> > >
> > > Shannon Sutton
> > > CMMS Specialist
> > > EAM/IBM-Tivoli Maximo
> > > EMCOR Government Services
> > > Office: 571-403-8940
> > > Cell: 571-970-7965
> > >
> > >
> > >
> > >
> > > From: Zeroxpectations <zeroxpectations@yahoo.com<mailto:zeroxpectations%40yahoo.com>>
> > > To: "MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>" <MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>>
> > > Date: 07/19/2012 05:09 PM
> > > Subject: [MAXIMO List] ESCALATIONS
> > > Sent by: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> > >
> > >
> > >
> > >
> > >
> > >
> > > Need a little help from you Maximo Pros out there. I am starting to mess
> > > with escalations and am running into a problem. I am trying to set up an
> > > automatic notification when a Work Order has been cancelled and send it to
> > > the originator. Currently I set my escalation up like this: STATUS =
> > > 'CAN' and STATUSDATE >= '7/18/12'
> > > The schedule is set to 15 minutes for testing purposes, but this formula
> > > isn't yielding any notifications. Also, looking at this a bit more I am
> > > thinking that if this did work it would not get me what I want because, for
> > > example, if a work order is cancelled today and the system runs the
> > > escalation and notifies me then when it runs again it will notify me of the
> > > same Work Order cancellation.....this could be a problem as time goes on.
> > > Perhaps I am trying to use the wrong app for what I am trying to
> > > accomplish?
> > >
> > > Anyways, although this is a very simple process for some of you out
> > > there any guidance you can provide would be much appreciated. Even if that
> > > included links to literature on the topic. Thanks.
> > >
> > > Maximo v6.2.6
> > > SQL 2002 Server
> > >
> > >
> > >
> > >
> > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> >
> >
> >
> >
>
> This message is for the named person's use only. It may contain confidential,
> proprietary or legally privileged information. No confidentiality or privilege
> is waived or lost by any mistransmission. If you receive this message in error,
> please immediately delete it and all copies of it from your system, destroy any
> hard copies of it and notify the sender. You must not, directly or indirectly,
> use, disclose, distribute, print, or copy any part of this message if you are
> not the intended recipient.
>
>
>
>
>
>
>
>
>
>
>





GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.

**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
**************************************************************************************************************


From: john_gould14 (2012-07-20 11:31)

I actually have this setup to provide notifications throughout the status changes that a work order goes through. It should be relatively straight forward and as others have suggested - I don't think you need to key in on dates at all because when the escalation runs it will stop after the criteria have been met. Here is what I have for my 'canceled' notification. For what it's worth - I am on 7.5.0.0
First - you need to create a communication template. One really nice thing that we do is utilize variables within the HTML text to pull information from the work order and put it in the body of the email. One really nice field to pull over is WOSTATUS2.memo - this is the memo box you see when you change status of a work order. We use this to type in why we are canceling the request - basically it's one stop shopping for informing the user what is going on - very effective.
In the template itself make sure that it applies to WORKORDER and is accessible from ALL. Your 'to' field should equal a role that you want to have established as the recipient - think of this as a variable that you want to apply to the template that regardless of the situation will pull this role based information. In our case, we created a custom field to pull user email addresses when work orders are submitted - I'm not going to explain all of this but we have a web interface for people to submit work orders that is not directly through Maximo but done through the MIF.
This role was defined by utilizing the newly created database field that we wanted to pull for use in this role scenario.
Lastly - and an important one to check as well - make sure the communication template itself is ACTIVE.
On to the escalation -
Applies to - WORKORDER
Status - Active (you might want to check if your escalation is active first if it doesn't appear to be running)
Condition - status = 'CAN' and (email field) is not null (we did this because we wanted to make sure that the escalation is only going to run in a particular case - when our custom email field is not null)
Escalation Point - just add a new row - no need to add data
Under the notification tab - select your communication template
You should be good to go here. Next as a double check - make sure your in the CRON task for escalations that this escalation is active. The CRON task for escalations is also a good place to check the history of your escalation to make sure that things are running as designed.
Hope this helps!
--- In MAXIMO@yahoogroups.com, Ian Wright <ian.wright@...> wrote:
>
> You don’t need a date, just
>
> status = ‘CAN’
>
> Escalation point elapsed time interval = statusdate uncheck the repeat flag
>
> Check with the e-mail administrators that your mxserver is trusted or do a communication to yourself from the workorder and see if you get it
>
> Rgds Ian
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of zeroxpectations@...
> Sent: 20 July 2012 01:42
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] ESCALATIONS
>
>
>
> Ha! If I can't get it to work using ur previous suggestions I just might take you up on ur offer! Thanks
>
> On Jul 19, 2012, at 6:59 PM, Shannon Sutton <ssutton@...<mailto:ssutton%40emcor.net>> wrote:
>
> > I am in 7.5 but i believe escalations setup is the same.. If you could list out all the steps that you have completed it would also help trace down other issues or send some screen shots directly to my email.. Don't worry about the ignorance.. I believe we all learn by error, google and yahoo groups :)
> >
> > Shannon Sutton
> > Cell: 571-970-7965
> >
> > On Jul 19, 2012, at 6:39 PM, zeroxpectations@...<mailto:zeroxpectations%40yahoo.com> wrote:
> >
> > > Thanks for the response, Shannon. I'll definitely give ur suggestions a try. I am new to this part of Maximo so please excuse my ignorance. Thanks and I'll let you know my results!
> > >
> > > On Jul 19, 2012, at 5:27 PM, Shannon Sutton <ssutton@...<mailto:ssutton%40emcor.net>> wrote:
> > >
> > > > You date range is causing it not to yield any data.. using a '7/18/12' is
> > > > setting time to 7/1/18 00:01:00. I prefer to use a between or you could use
> > > > a (statusdate >= getdate()-1), but try your query from the where clause in
> > > > workorder tracking to make sure it yields the correct data before applying
> > > > to an escalation..
> > > >
> > > >
> > > > Also as long as the Repeat check box is not checked under escalation point
> > > > it should not repeat data that matches the query..
> > > >
> > > >
> > > >
> > > > Shannon Sutton
> > > > CMMS Specialist
> > > > EAM/IBM-Tivoli Maximo
> > > > EMCOR Government Services
> > > > Office: 571-403-8940
> > > > Cell: 571-970-7965
> > > >
> > > >
> > > >
> > > >
> > > > From: Zeroxpectations <zeroxpectations@...<mailto:zeroxpectations%40yahoo.com>>
> > > > To: "MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>" <MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>>
> > > > Date: 07/19/2012 05:09 PM
> > > > Subject: [MAXIMO List] ESCALATIONS
> > > > Sent by: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Need a little help from you Maximo Pros out there. I am starting to mess
> > > > with escalations and am running into a problem. I am trying to set up an
> > > > automatic notification when a Work Order has been cancelled and send it to
> > > > the originator. Currently I set my escalation up like this: STATUS =
> > > > 'CAN' and STATUSDATE >= '7/18/12'
> > > > The schedule is set to 15 minutes for testing purposes, but this formula
> > > > isn't yielding any notifications. Also, looking at this a bit more I am
> > > > thinking that if this did work it would not get me what I want because, for
> > > > example, if a work order is cancelled today and the system runs the
> > > > escalation and notifies me then when it runs again it will notify me of the
> > > > same Work Order cancellation.....this could be a problem as time goes on.
> > > > Perhaps I am trying to use the wrong app for what I am trying to
> > > > accomplish?
> > > >
> > > > Anyways, although this is a very simple process for some of you out
> > > > there any guidance you can provide would be much appreciated. Even if that
> > > > included links to literature on the topic. Thanks.
> > > >
> > > > Maximo v6.2.6
> > > > SQL 2002 Server
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > This message is for the named person's use only. It may contain confidential,
> > > > proprietary or legally privileged information. No confidentiality or privilege
> > > > is waived or lost by any mistransmission. If you receive this message in error,
> > > > please immediately delete it and all copies of it from your system, destroy any
> > > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > > use, disclose, distribute, print, or copy any part of this message if you are
> > > > not the intended recipient.
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> > This message is for the named person's use only. It may contain confidential,
> > proprietary or legally privileged information. No confidentiality or privilege
> > is waived or lost by any mistransmission. If you receive this message in error,
> > please immediately delete it and all copies of it from your system, destroy any
> > hard copies of it and notify the sender. You must not, directly or indirectly,
> > use, disclose, distribute, print, or copy any part of this message if you are
> > not the intended recipient.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
> GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
>
> **************************************************************************************************************
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
> **************************************************************************************************************
>
>
>
>
>


From: Travis Herron (2012-07-20 14:21)

I'll add that you DO want to keep your restriction for work orders cancelled after "today." If you do not, the first time you run the escalation, it will send out emails for every work order ever cancelled. You might have cancelled Bob's work order 10 years ago and he'll get this cancellation notice now. You don't want that.
And if you ever remove that restriction, it will at the next run go back and check all those work orders that it hasn't performed the escalation on. In other words, you'll want it there, and don't ever remove it.
If you were doing this in a Workflow, you wouldn't need to restrict the date. As an Escalation, you'll want to.
Others are correct in saying it will not repeatedly send it unless you check the "repeat?" box on the Escalation Point.
Travis Herron
--- In MAXIMO@yahoogroups.com, "john_gould14" <john_gould14@...> wrote:
>
> I actually have this setup to provide notifications throughout the status changes that a work order goes through. It should be relatively straight forward and as others have suggested - I don't think you need to key in on dates at all because when the escalation runs it will stop after the criteria have been met. Here is what I have for my 'canceled' notification. For what it's worth - I am on 7.5.0.0
>
> First - you need to create a communication template. One really nice thing that we do is utilize variables within the HTML text to pull information from the work order and put it in the body of the email. One really nice field to pull over is WOSTATUS2.memo - this is the memo box you see when you change status of a work order. We use this to type in why we are canceling the request - basically it's one stop shopping for informing the user what is going on - very effective.
>
> In the template itself make sure that it applies to WORKORDER and is accessible from ALL. Your 'to' field should equal a role that you want to have established as the recipient - think of this as a variable that you want to apply to the template that regardless of the situation will pull this role based information. In our case, we created a custom field to pull user email addresses when work orders are submitted - I'm not going to explain all of this but we have a web interface for people to submit work orders that is not directly through Maximo but done through the MIF.
>
> This role was defined by utilizing the newly created database field that we wanted to pull for use in this role scenario.
>
> Lastly - and an important one to check as well - make sure the communication template itself is ACTIVE.
>
> On to the escalation -
>
> Applies to - WORKORDER
> Status - Active (you might want to check if your escalation is active first if it doesn't appear to be running)
> Condition - status = 'CAN' and (email field) is not null (we did this because we wanted to make sure that the escalation is only going to run in a particular case - when our custom email field is not null)
> Escalation Point - just add a new row - no need to add data
> Under the notification tab - select your communication template
>
> You should be good to go here. Next as a double check - make sure your in the CRON task for escalations that this escalation is active. The CRON task for escalations is also a good place to check the history of your escalation to make sure that things are running as designed.
>
> Hope this helps!
>
>
> --- In MAXIMO@yahoogroups.com, Ian Wright <ian.wright@> wrote:
> >
> > You don’t need a date, just
> >
> > status = ‘CAN’
> >
> > Escalation point elapsed time interval = statusdate uncheck the repeat flag
> >
> > Check with the e-mail administrators that your mxserver is trusted or do a communication to yourself from the workorder and see if you get it
> >
> > Rgds Ian
> >
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of zeroxpectations@
> > Sent: 20 July 2012 01:42
> > To: MAXIMO@yahoogroups.com
> > Subject: Re: [MAXIMO List] ESCALATIONS
> >
> >
> >
> > Ha! If I can't get it to work using ur previous suggestions I just might take you up on ur offer! Thanks
> >
> > On Jul 19, 2012, at 6:59 PM, Shannon Sutton <ssutton@<mailto:ssutton%40emcor.net>> wrote:
> >
> > > I am in 7.5 but i believe escalations setup is the same.. If you could list out all the steps that you have completed it would also help trace down other issues or send some screen shots directly to my email.. Don't worry about the ignorance.. I believe we all learn by error, google and yahoo groups :)
> > >
> > > Shannon Sutton
> > > Cell: 571-970-7965
> > >
> > > On Jul 19, 2012, at 6:39 PM, zeroxpectations@<mailto:zeroxpectations%40yahoo.com> wrote:
> > >
> > > > Thanks for the response, Shannon. I'll definitely give ur suggestions a try. I am new to this part of Maximo so please excuse my ignorance. Thanks and I'll let you know my results!
> > > >
> > > > On Jul 19, 2012, at 5:27 PM, Shannon Sutton <ssutton@<mailto:ssutton%40emcor.net>> wrote:
> > > >
> > > > > You date range is causing it not to yield any data.. using a '7/18/12' is
> > > > > setting time to 7/1/18 00:01:00. I prefer to use a between or you could use
> > > > > a (statusdate >= getdate()-1), but try your query from the where clause in
> > > > > workorder tracking to make sure it yields the correct data before applying
> > > > > to an escalation..
> > > > >
> > > > >
> > > > > Also as long as the Repeat check box is not checked under escalation point
> > > > > it should not repeat data that matches the query..
> > > > >
> > > > >
> > > > >
> > > > > Shannon Sutton
> > > > > CMMS Specialist
> > > > > EAM/IBM-Tivoli Maximo
> > > > > EMCOR Government Services
> > > > > Office: 571-403-8940
> > > > > Cell: 571-970-7965
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: Zeroxpectations <zeroxpectations@<mailto:zeroxpectations%40yahoo.com>>
> > > > > To: "MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>" <MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>>
> > > > > Date: 07/19/2012 05:09 PM
> > > > > Subject: [MAXIMO List] ESCALATIONS
> > > > > Sent by: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Need a little help from you Maximo Pros out there. I am starting to mess
> > > > > with escalations and am running into a problem. I am trying to set up an
> > > > > automatic notification when a Work Order has been cancelled and send it to
> > > > > the originator. Currently I set my escalation up like this: STATUS =
> > > > > 'CAN' and STATUSDATE >= '7/18/12'
> > > > > The schedule is set to 15 minutes for testing purposes, but this formula
> > > > > isn't yielding any notifications. Also, looking at this a bit more I am
> > > > > thinking that if this did work it would not get me what I want because, for
> > > > > example, if a work order is cancelled today and the system runs the
> > > > > escalation and notifies me then when it runs again it will notify me of the
> > > > > same Work Order cancellation.....this could be a problem as time goes on.
> > > > > Perhaps I am trying to use the wrong app for what I am trying to
> > > > > accomplish?
> > > > >
> > > > > Anyways, although this is a very simple process for some of you out
> > > > > there any guidance you can provide would be much appreciated. Even if that
> > > > > included links to literature on the topic. Thanks.
> > > > >
> > > > > Maximo v6.2.6
> > > > > SQL 2002 Server
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > This message is for the named person's use only. It may contain confidential,
> > > > > proprietary or legally privileged information. No confidentiality or privilege
> > > > > is waived or lost by any mistransmission. If you receive this message in error,
> > > > > please immediately delete it and all copies of it from your system, destroy any
> > > > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > > > use, disclose, distribute, print, or copy any part of this message if you are
> > > > > not the intended recipient.
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
> >
> > **************************************************************************************************************
> > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
> > If you have received this email in error please notify the system manager.
> > This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
> > **************************************************************************************************************
> >
> >
> >
> >
> >
>


From: Chris Brandon (2012-07-20 07:34)

What Travis said ... been there, done that...  not a good thing and you can't really stop it once it starts!

________________________________
From: Travis Herron <therron@pcci.edu>
To: MAXIMO@yahoogroups.com
Sent: Friday, July 20, 2012 9:21 AM
Subject: [MAXIMO List] Re: ESCALATIONS


 

I'll add that you DO want to keep your restriction for work orders cancelled after "today." If you do not, the first time you run the escalation, it will send out emails for every work order ever cancelled. You might have cancelled Bob's work order 10 years ago and he'll get this cancellation notice now. You don't want that.
And if you ever remove that restriction, it will at the next run go back and check all those work orders that it hasn't performed the escalation on. In other words, you'll want it there, and don't ever remove it.
If you were doing this in a Workflow, you wouldn't need to restrict the date. As an Escalation, you'll want to.
Others are correct in saying it will not repeatedly send it unless you check the "repeat?" box on the Escalation Point.
Travis Herron
--- In mailto:MAXIMO%40yahoogroups.com, "john_gould14" <john_gould14@...> wrote:
>
> I actually have this setup to provide notifications throughout the status changes that a work order goes through. It should be relatively straight forward and as others have suggested - I don't think you need to key in on dates at all because when the escalation runs it will stop after the criteria have been met. Here is what I have for my 'canceled' notification. For what it's worth - I am on 7.5.0.0
>
> First - you need to create a communication template. One really nice thing that we do is utilize variables within the HTML text to pull information from the work order and put it in the body of the email. One really nice field to pull over is WOSTATUS2.memo - this is the memo box you see when you change status of a work order. We use this to type in why we are canceling the request - basically it's one stop shopping for informing the user what is going on - very effective.
>
> In the template itself make sure that it applies to WORKORDER and is accessible from ALL. Your 'to' field should equal a role that you want to have established as the recipient - think of this as a variable that you want to apply to the template that regardless of the situation will pull this role based information. In our case, we created a custom field to pull user email addresses when work orders are submitted - I'm not going to explain all of this but we have a web interface for people to submit work orders that is not directly through Maximo but done through the MIF.
>
> This role was defined by utilizing the newly created database field that we wanted to pull for use in this role scenario.
>
> Lastly - and an important one to check as well - make sure the communication template itself is ACTIVE.
>
> On to the escalation -
>
> Applies to - WORKORDER
> Status - Active (you might want to check if your escalation is active first if it doesn't appear to be running)
> Condition - status = 'CAN' and (email field) is not null (we did this because we wanted to make sure that the escalation is only going to run in a particular case - when our custom email field is not null)
> Escalation Point - just add a new row - no need to add data
> Under the notification tab - select your communication template
>
> You should be good to go here. Next as a double check - make sure your in the CRON task for escalations that this escalation is active. The CRON task for escalations is also a good place to check the history of your escalation to make sure that things are running as designed.
>
> Hope this helps!
>
>
> --- In mailto:MAXIMO%40yahoogroups.com, Ian Wright <ian.wright@> wrote:
> >
> > You don’t need a date, just
> >
> > status = ‘CAN’
> >
> > Escalation point elapsed time interval = statusdate uncheck the repeat flag
> >
> > Check with the e-mail administrators that your mxserver is trusted or do a communication to yourself from the workorder and see if you get it
> >
> > Rgds Ian
> >
> > From: mailto:MAXIMO%40yahoogroups.com [mailto:mailto:MAXIMO%40yahoogroups.com] On Behalf Of zeroxpectations@
> > Sent: 20 July 2012 01:42
> > To: mailto:MAXIMO%40yahoogroups.com
> > Subject: Re: [MAXIMO List] ESCALATIONS
> >
> >
> >
> > Ha! If I can't get it to work using ur previous suggestions I just might take you up on ur offer! Thanks
> >
> > On Jul 19, 2012, at 6:59 PM, Shannon Sutton <ssutton@<mailto:ssutton%40emcor.net>> wrote:
> >
> > > I am in 7.5 but i believe escalations setup is the same.. If you could list out all the steps that you have completed it would also help trace down other issues or send some screen shots directly to my email.. Don't worry about the ignorance.. I believe we all learn by error, google and yahoo groups :)
> > >
> > > Shannon Sutton
> > > Cell: 571-970-7965
> > >
> > > On Jul 19, 2012, at 6:39 PM, zeroxpectations@<mailto:zeroxpectations%40yahoo.com> wrote:
> > >
> > > > Thanks for the response, Shannon. I'll definitely give ur suggestions a try. I am new to this part of Maximo so please excuse my ignorance. Thanks and I'll let you know my results!
> > > >
> > > > On Jul 19, 2012, at 5:27 PM, Shannon Sutton <ssutton@<mailto:ssutton%40emcor.net>> wrote:
> > > >
> > > > > You date range is causing it not to yield any data.. using a '7/18/12' is
> > > > > setting time to 7/1/18 00:01:00. I prefer to use a between or you could use
> > > > > a (statusdate >= getdate()-1), but try your query from the where clause in
> > > > > workorder tracking to make sure it yields the correct data before applying
> > > > > to an escalation..
> > > > >
> > > > >
> > > > > Also as long as the Repeat check box is not checked under escalation point
> > > > > it should not repeat data that matches the query..
> > > > >
> > > > >
> > > > >
> > > > > Shannon Sutton
> > > > > CMMS Specialist
> > > > > EAM/IBM-Tivoli Maximo
> > > > > EMCOR Government Services
> > > > > Office: 571-403-8940
> > > > > Cell: 571-970-7965
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: Zeroxpectations <zeroxpectations@<mailto:zeroxpectations%40yahoo.com>>
> > > > > To: "mailto:MAXIMO%40yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>" <mailto:MAXIMO%40yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>>
> > > > > Date: 07/19/2012 05:09 PM
> > > > > Subject: [MAXIMO List] ESCALATIONS
> > > > > Sent by: mailto:MAXIMO%40yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Need a little help from you Maximo Pros out there. I am starting to mess
> > > > > with escalations and am running into a problem. I am trying to set up an
> > > > > automatic notification when a Work Order has been cancelled and send it to
> > > > > the originator. Currently I set my escalation up like this: STATUS =
> > > > > 'CAN' and STATUSDATE >= '7/18/12'
> > > > > The schedule is set to 15 minutes for testing purposes, but this formula
> > > > > isn't yielding any notifications. Also, looking at this a bit more I am
> > > > > thinking that if this did work it would not get me what I want because, for
> > > > > example, if a work order is cancelled today and the system runs the
> > > > > escalation and notifies me then when it runs again it will notify me of the
> > > > > same Work Order cancellation.....this could be a problem as time goes on.
> > > > > Perhaps I am trying to use the wrong app for what I am trying to
> > > > > accomplish?
> > > > >
> > > > > Anyways, although this is a very simple process for some of you out
> > > > > there any guidance you can provide would be much appreciated. Even if that
> > > > > included links to literature on the topic. Thanks.
> > > > >
> > > > > Maximo v6.2.6
> > > > > SQL 2002 Server
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > This message is for the named person's use only. It may contain confidential,
> > > > > proprietary or legally privileged information. No confidentiality or privilege
> > > > > is waived or lost by any mistransmission. If you receive this message in error,
> > > > > please immediately delete it and all copies of it from your system, destroy any
> > > > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > > > use, disclose, distribute, print, or copy any part of this message if you are
> > > > > not the intended recipient.
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
> >
> > **************************************************************************************************************
> > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
> > If you have received this email in error please notify the system manager.
> > This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
> > **************************************************************************************************************
> >
> >
> >
> >
> >
>



From: zeroxpectations (2012-07-20 21:57)

LMAO thanks for the advice. I was wondering about this very thing!
Thanks to all who have offered their knowledge. You're the reason this forum is so great!
On Jul 20, 2012, at 10:34 AM, Chris Brandon <cbrandon63@yahoo.com> wrote:
> What Travis said ... been there, done that... not a good thing and you can't really stop it once it starts!
>
> ________________________________
> From: Travis Herron <therron@pcci.edu>
> To: MAXIMO@yahoogroups.com
> Sent: Friday, July 20, 2012 9:21 AM
> Subject: [MAXIMO List] Re: ESCALATIONS
>
>
>
>
> I'll add that you DO want to keep your restriction for work orders cancelled after "today." If you do not, the first time you run the escalation, it will send out emails for every work order ever cancelled. You might have cancelled Bob's work order 10 years ago and he'll get this cancellation notice now. You don't want that.
>
> And if you ever remove that restriction, it will at the next run go back and check all those work orders that it hasn't performed the escalation on. In other words, you'll want it there, and don't ever remove it.
>
> If you were doing this in a Workflow, you wouldn't need to restrict the date. As an Escalation, you'll want to.
>
> Others are correct in saying it will not repeatedly send it unless you check the "repeat?" box on the Escalation Point.
>
> Travis Herron
>
> --- In mailto:MAXIMO%40yahoogroups.com, "john_gould14" <john_gould14@...> wrote:
> >
> > I actually have this setup to provide notifications throughout the status changes that a work order goes through. It should be relatively straight forward and as others have suggested - I don't think you need to key in on dates at all because when the escalation runs it will stop after the criteria have been met. Here is what I have for my 'canceled' notification. For what it's worth - I am on 7.5.0.0
> >
> > First - you need to create a communication template. One really nice thing that we do is utilize variables within the HTML text to pull information from the work order and put it in the body of the email. One really nice field to pull over is WOSTATUS2.memo - this is the memo box you see when you change status of a work order. We use this to type in why we are canceling the request - basically it's one stop shopping for informing the user what is going on - very effective.
> >
> > In the template itself make sure that it applies to WORKORDER and is accessible from ALL. Your 'to' field should equal a role that you want to have established as the recipient - think of this as a variable that you want to apply to the template that regardless of the situation will pull this role based information. In our case, we created a custom field to pull user email addresses when work orders are submitted - I'm not going to explain all of this but we have a web interface for people to submit work orders that is not directly through Maximo but done through the MIF.
> >
> > This role was defined by utilizing the newly created database field that we wanted to pull for use in this role scenario.
> >
> > Lastly - and an important one to check as well - make sure the communication template itself is ACTIVE.
> >
> > On to the escalation -
> >
> > Applies to - WORKORDER
> > Status - Active (you might want to check if your escalation is active first if it doesn't appear to be running)
> > Condition - status = 'CAN' and (email field) is not null (we did this because we wanted to make sure that the escalation is only going to run in a particular case - when our custom email field is not null)
> > Escalation Point - just add a new row - no need to add data
> > Under the notification tab - select your communication template
> >
> > You should be good to go here. Next as a double check - make sure your in the CRON task for escalations that this escalation is active. The CRON task for escalations is also a good place to check the history of your escalation to make sure that things are running as designed.
> >
> > Hope this helps!
> >
> >
> > --- In mailto:MAXIMO%40yahoogroups.com, Ian Wright <ian.wright@> wrote:
> > >
> > > You don’t need a date, just
> > >
> > > status = ‘CAN’
> > >
> > > Escalation point elapsed time interval = statusdate uncheck the repeat flag
> > >
> > > Check with the e-mail administrators that your mxserver is trusted or do a communication to yourself from the workorder and see if you get it
> > >
> > > Rgds Ian
> > >
> > > From: mailto:MAXIMO%40yahoogroups.com [mailto:mailto:MAXIMO%40yahoogroups.com] On Behalf Of zeroxpectations@
> > > Sent: 20 July 2012 01:42
> > > To: mailto:MAXIMO%40yahoogroups.com
> > > Subject: Re: [MAXIMO List] ESCALATIONS
> > >
> > >
> > >
> > > Ha! If I can't get it to work using ur previous suggestions I just might take you up on ur offer! Thanks
> > >
> > > On Jul 19, 2012, at 6:59 PM, Shannon Sutton <ssutton@<mailto:ssutton%40emcor.net>> wrote:
> > >
> > > > I am in 7.5 but i believe escalations setup is the same.. If you could list out all the steps that you have completed it would also help trace down other issues or send some screen shots directly to my email.. Don't worry about the ignorance.. I believe we all learn by error, google and yahoo groups :)
> > > >
> > > > Shannon Sutton
> > > > Cell: 571-970-7965
> > > >
> > > > On Jul 19, 2012, at 6:39 PM, zeroxpectations@<mailto:zeroxpectations%40yahoo.com> wrote:
> > > >
> > > > > Thanks for the response, Shannon. I'll definitely give ur suggestions a try. I am new to this part of Maximo so please excuse my ignorance. Thanks and I'll let you know my results!
> > > > >
> > > > > On Jul 19, 2012, at 5:27 PM, Shannon Sutton <ssutton@<mailto:ssutton%40emcor.net>> wrote:
> > > > >
> > > > > > You date range is causing it not to yield any data.. using a '7/18/12' is
> > > > > > setting time to 7/1/18 00:01:00. I prefer to use a between or you could use
> > > > > > a (statusdate >= getdate()-1), but try your query from the where clause in
> > > > > > workorder tracking to make sure it yields the correct data before applying
> > > > > > to an escalation..
> > > > > >
> > > > > >
> > > > > > Also as long as the Repeat check box is not checked under escalation point
> > > > > > it should not repeat data that matches the query..
> > > > > >
> > > > > >
> > > > > >
> > > > > > Shannon Sutton
> > > > > > CMMS Specialist
> > > > > > EAM/IBM-Tivoli Maximo
> > > > > > EMCOR Government Services
> > > > > > Office: 571-403-8940
> > > > > > Cell: 571-970-7965
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: Zeroxpectations <zeroxpectations@<mailto:zeroxpectations%40yahoo.com>>
> > > > > > To: "mailto:MAXIMO%40yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>" <mailto:MAXIMO%40yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>>
> > > > > > Date: 07/19/2012 05:09 PM
> > > > > > Subject: [MAXIMO List] ESCALATIONS
> > > > > > Sent by: mailto:MAXIMO%40yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Need a little help from you Maximo Pros out there. I am starting to mess
> > > > > > with escalations and am running into a problem. I am trying to set up an
> > > > > > automatic notification when a Work Order has been cancelled and send it to
> > > > > > the originator. Currently I set my escalation up like this: STATUS =
> > > > > > 'CAN' and STATUSDATE >= '7/18/12'
> > > > > > The schedule is set to 15 minutes for testing purposes, but this formula
> > > > > > isn't yielding any notifications. Also, looking at this a bit more I am
> > > > > > thinking that if this did work it would not get me what I want because, for
> > > > > > example, if a work order is cancelled today and the system runs the
> > > > > > escalation and notifies me then when it runs again it will notify me of the
> > > > > > same Work Order cancellation.....this could be a problem as time goes on.
> > > > > > Perhaps I am trying to use the wrong app for what I am trying to
> > > > > > accomplish?
> > > > > >
> > > > > > Anyways, although this is a very simple process for some of you out
> > > > > > there any guidance you can provide would be much appreciated. Even if that
> > > > > > included links to literature on the topic. Thanks.
> > > > > >
> > > > > > Maximo v6.2.6
> > > > > > SQL 2002 Server
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > This message is for the named person's use only. It may contain confidential,
> > > > > > proprietary or legally privileged information. No confidentiality or privilege
> > > > > > is waived or lost by any mistransmission. If you receive this message in error,
> > > > > > please immediately delete it and all copies of it from your system, destroy any
> > > > > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > > > > use, disclose, distribute, print, or copy any part of this message if you are
> > > > > > not the intended recipient.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > This message is for the named person's use only. It may contain confidential,
> > > > proprietary or legally privileged information. No confidentiality or privilege
> > > > is waived or lost by any mistransmission. If you receive this message in error,
> > > > please immediately delete it and all copies of it from your system, destroy any
> > > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > > use, disclose, distribute, print, or copy any part of this message if you are
> > > > not the intended recipient.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
> > >
> > > **************************************************************************************************************
> > > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
> > > If you have received this email in error please notify the system manager.
> > > This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
> > > **************************************************************************************************************
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
>


From: Shannon Rotz (2012-07-20 20:14)

Me too … one of those “oops” moments …



Shannon

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Chris Brandon
Sent: July-20-12 8:35 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: ESCALATIONS


What Travis said ... been there, done that... not a good thing and you can't really stop it once it starts!
________________________________
From: Travis Herron <therron@pcci.edu <mailto:therron%40pcci.edu> >
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Sent: Friday, July 20, 2012 9:21 AM
Subject: [MAXIMO List] Re: ESCALATIONS

I'll add that you DO want to keep your restriction for work orders cancelled after "today." If you do not, the first time you run the escalation, it will send out emails for every work order ever cancelled. You might have cancelled Bob's work order 10 years ago and he'll get this cancellation notice now. You don't want that.
And if you ever remove that restriction, it will at the next run go back and check all those work orders that it hasn't performed the escalation on. In other words, you'll want it there, and don't ever remove it.
If you were doing this in a Workflow, you wouldn't need to restrict the date. As an Escalation, you'll want to.
Others are correct in saying it will not repeatedly send it unless you check the "repeat?" box on the Escalation Point.
Travis Herron
--- In mailto:MAXIMO%40yahoogroups.com, "john_gould14" <john_gould14@...> wrote:
>
> I actually have this setup to provide notifications throughout the status changes that a work order goes through. It should be relatively straight forward and as others have suggested - I don't think you need to key in on dates at all because when the escalation runs it will stop after the criteria have been met. Here is what I have for my 'canceled' notification. For what it's worth - I am on 7.5.0.0
>
> First - you need to create a communication template. One really nice thing that we do is utilize variables within the HTML text to pull information from the work order and put it in the body of the email. One really nice field to pull over is WOSTATUS2.memo - this is the memo box you see when you change status of a work order. We use this to type in why we are canceling the request - basically it's one stop shopping for informing the user what is going on - very effective.
>
> In the template itself make sure that it applies to WORKORDER and is accessible from ALL. Your 'to' field should equal a role that you want to have established as the recipient - think of this as a variable that you want to apply to the template that regardless of the situation will pull this role based information. In our case, we created a custom field to pull user email addresses when work orders are submitted - I'm not going to explain all of this but we have a web interface for people to submit work orders that is not directly through Maximo but done through the MIF.
>
> This role was defined by utilizing the newly created database field that we wanted to pull for use in this role scenario.
>
> Lastly - and an important one to check as well - make sure the communication template itself is ACTIVE.
>
> On to the escalation -
>
> Applies to - WORKORDER
> Status - Active (you might want to check if your escalation is active first if it doesn't appear to be running)
> Condition - status = 'CAN' and (email field) is not null (we did this because we wanted to make sure that the escalation is only going to run in a particular case - when our custom email field is not null)
> Escalation Point - just add a new row - no need to add data
> Under the notification tab - select your communication template
>
> You should be good to go here. Next as a double check - make sure your in the CRON task for escalations that this escalation is active. The CRON task for escalations is also a good place to check the history of your escalation to make sure that things are running as designed.
>
> Hope this helps!
>
>
> --- In mailto:MAXIMO%40yahoogroups.com, Ian Wright <ian.wright@> wrote:
> >
> > You don’t need a date, just
> >
> > status = ‘CAN’
> >
> > Escalation point elapsed time interval = statusdate uncheck the repeat flag
> >
> > Check with the e-mail administrators that your mxserver is trusted or do a communication to yourself from the workorder and see if you get it
> >
> > Rgds Ian
> >
> > From: mailto:MAXIMO%40yahoogroups.com [mailto:mailto:MAXIMO%40yahoogroups.com] On Behalf Of zeroxpectations@
> > Sent: 20 July 2012 01:42
> > To: mailto:MAXIMO%40yahoogroups.com
> > Subject: Re: [MAXIMO List] ESCALATIONS
> >
> >
> >
> > Ha! If I can't get it to work using ur previous suggestions I just might take you up on ur offer! Thanks
> >
> > On Jul 19, 2012, at 6:59 PM, Shannon Sutton <ssutton@ <mailto:ssutton@%3cmailto:ssutton%40emcor.net> <mailto:ssutton%40emcor.net>> wrote:
> >
> > > I am in 7.5 but i believe escalations setup is the same.. If you could list out all the steps that you have completed it would also help trace down other issues or send some screen shots directly to my email.. Don't worry about the ignorance.. I believe we all learn by error, google and yahoo groups :)
> > >
> > > Shannon Sutton
> > > Cell: 571-970-7965
> > >
> > > On Jul 19, 2012, at 6:39 PM, zeroxpectations@ <mailto:zeroxpectations@%3cmailto:zeroxpectations%40yahoo.com> <mailto:zeroxpectations%40yahoo.com> wrote:
> > >
> > > > Thanks for the response, Shannon. I'll definitely give ur suggestions a try. I am new to this part of Maximo so please excuse my ignorance. Thanks and I'll let you know my results!
> > > >
> > > > On Jul 19, 2012, at 5:27 PM, Shannon Sutton <ssutton@ <mailto:ssutton@%3cmailto:ssutton%40emcor.net> <mailto:ssutton%40emcor.net>> wrote:
> > > >
> > > > > You date range is causing it not to yield any data.. using a '7/18/12' is
> > > > > setting time to 7/1/18 00:01:00. I prefer to use a between or you could use
> > > > > a (statusdate >= getdate()-1), but try your query from the where clause in
> > > > > workorder tracking to make sure it yields the correct data before applying
> > > > > to an escalation..
> > > > >
> > > > >
> > > > > Also as long as the Repeat check box is not checked under escalation point
> > > > > it should not repeat data that matches the query..
> > > > >
> > > > >
> > > > >
> > > > > Shannon Sutton
> > > > > CMMS Specialist
> > > > > EAM/IBM-Tivoli Maximo
> > > > > EMCOR Government Services
> > > > > Office: 571-403-8940
> > > > > Cell: 571-970-7965
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: Zeroxpectations <zeroxpectations@ <mailto:zeroxpectations@%3cmailto:zeroxpectations%40yahoo.com> <mailto:zeroxpectations%40yahoo.com>>
> > > > > To: "mailto:MAXIMO%40yahoogroups.com <mailto:MAXIMO%40yahoogroups.com%3cmailto:MAXIMO%40yahoogroups.com%3e> <mailto:MAXIMO%40yahoogroups.com>" <mailto:MAXIMO%40yahoogroups.com <mailto:MAXIMO%40yahoogroups.com%3cmailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com>>
> > > > > Date: 07/19/2012 05:09 PM
> > > > > Subject: [MAXIMO List] ESCALATIONS
> > > > > Sent by: mailto:MAXIMO%40yahoogroups.com <mailto:MAXIMO%40yahoogroups.com%3cmailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Need a little help from you Maximo Pros out there. I am starting to mess
> > > > > with escalations and am running into a problem. I am trying to set up an
> > > > > automatic notification when a Work Order has been cancelled and send it to
> > > > > the originator. Currently I set my escalation up like this: STATUS =
> > > > > 'CAN' and STATUSDATE >= '7/18/12'
> > > > > The schedule is set to 15 minutes for testing purposes, but this formula
> > > > > isn't yielding any notifications. Also, looking at this a bit more I am
> > > > > thinking that if this did work it would not get me what I want because, for
> > > > > example, if a work order is cancelled today and the system runs the
> > > > > escalation and notifies me then when it runs again it will notify me of the
> > > > > same Work Order cancellation.....this could be a problem as time goes on.
> > > > > Perhaps I am trying to use the wrong app for what I am trying to
> > > > > accomplish?
> > > > >
> > > > > Anyways, although this is a very simple process for some of you out
> > > > > there any guidance you can provide would be much appreciated. Even if that
> > > > > included links to literature on the topic. Thanks.
> > > > >
> > > > > Maximo v6.2.6
> > > > > SQL 2002 Server
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > This message is for the named person's use only. It may contain confidential,
> > > > > proprietary or legally privileged information. No confidentiality or privilege
> > > > > is waived or lost by any mistransmission. If you receive this message in error,
> > > > > please immediately delete it and all copies of it from your system, destroy any
> > > > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > > > use, disclose, distribute, print, or copy any part of this message if you are
> > > > > not the intended recipient.
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
> >
> > **************************************************************************************************************
> > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
> > If you have received this email in error please notify the system manager.
> > This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
> > **************************************************************************************************************
> >
> >
> >
> >
> >
>