Maximo Open Forum

Hello Everyone,

I have a new requirement to create a Cron job to close the completed SR in Maximo.
So I created an Action with change status and value as closed in SR and then I attached the action to Escalation with the condition as (status='completed' and ticketid='234'). When I trigger the Escalation, I am getting error as "BMXAA4295E - Could not change ticket 234 status to CLOSED. BMXAA4190E - Status CLOSED is not in the value list."

When I checked there is No global data restriction present on object 'SR' or attributes related to 'SR'. Also there is No condition attached on Security group for SR Application.

But there is a domain condition attached to SRSTATUS (Expression =  :&APPNAME&='SR'). I tried to remove the domain condition (Expression =  :&APPNAME&='SR') and trigger the Escalation. The escalation ran successfully without any error and change the status of SR record '234' to Closed. 
So I tried to give the domain condition as 

Expression =  :&APPNAME&='SR' or :&APPNAME&='ESCALATION' or :&APPNAME&='CRONTASK''. But again its throwing the error. 
"BMXAA4295E - Could not change ticket 1234 status to CLOSED. BMXAA4190E - Status CLOSED is not in the value list."


Can anyone help on this, why are we getting error when there is domain condition on Application name (Expression =  :&APPNAME&='SR).

Thanks in Advance.

Can anyone please help on this

When you have background processes like escalations or cron tasks, the app name will not be set. You create these in the escalation/cron task application but the set is not opened in that context. If your condition was an automation script condition you could check for interactive but it's not possible in our expression builder today.

I guess my question is what is the purpose of the condition? Phrased another way, when is a scenario that a user is changing the status but the app isn't SR? If we add a null/empty string check to support escalations/cron tasks it will also enable support for other scenarios (like SOAP or REST integrations) which means out of box I can't think of something we'd be blocking it on. The only thing I can think of is that you have a cloned application where you are trying to hide the status. But if that's not the case, the correct answer may be to remove the condition.

HI Ishwarya,

did you try something like this Expression =  :&APPNAME&='SR' or :&USERID&='MAXADMIN'

where the maxadmin is the user who will be used by the system to run the escalation.