How to create problem record with assess state?

kiran115
Tera Contributor

Whenever a problem record is created by an incident or directly by the problem module, The stages should start from an assess state instead of a new state. How to configure that requirement? 

3 REPLIES 3

Pankaj kr
Kilo Sage

Hi kiran,

 

You can write on before insert BR on problem table and mark the state as assess. This way you can fix this issue.

 

Thanks,

 

Pankaj kumar

Community Alums
Not applicable

Hi @kiran115 , 

I tried your problem in my PDI and it works for me, pleas check below solution 

Create before BR and add below code 

(function executeRule(current, previous /*null when async*/) {

	// Add your code here
	gs.log("Change Probelm state");
	current.setValue('state', 102);
	current.setWorkflow(false);

})(current, previous);

SarthakKashyap_0-1717004069931.png

 

Please mark my answer correct and helpful if this works for you

Thanks and Regards 
Sarthak

 

Robbie
Kilo Patron
Kilo Patron

Hi @kiran115,

 

A couple of things you need to be aware of before implementing this based on your organisations vs OOB (Out Of Box) configurations.

First, typically when moving to the state of 'Asses' the Problem needs to be assigned. Is there a default group or user (or logic) these should be assigned to?

Next, there are some plugins available around Problem state mapping so make sure these are considered.

 

If the above are considered, you can edit the UI Action (the 'Create Problem' button) which allows you to create the Problem form an incident.

See the below screen shot which for demo purposes updates as you've required, however you do need to consider the assignment for this state.

From the Navigation menu, type 'UI Actions' under 'System UI'.

Search for and select the 'Create Problem' and update as follows - note the lines highlighted - 15 through 17.

 

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.

 

Thanks, Robbie

 

Screenshot 2024-05-29 at 12.37.15.png