question Re: If short description is same as current short description,then user must not be able to save inc in CSM forum

If short description is same as current short description,then user must not be able to save inciden

Shubham_verma — Thu, 08 Feb 2024 09:14:52 GMT

When user tries to enter short description on incident form,if short description is same as recently entered short description,then user must not be able to submit incident.How can we achieve this?

Re: If short description is same as current short description,then user must not be able to save inc

shyamkumar VK — Thu, 08 Feb 2024 09:18:54 GMT

@Shubham_verma ,

1. Design BR on Before Insert on Incident Table and use this Below Script

function onBefore(current, previous) { var gr = new GlideRecord('incident'); gr.addQuery('short_description', current.short_description); gr.query(); while(gr.next()) gs.addInfoMessage('Incident exists With same short description please select different SD'); //change as you need current.setAbortAction(true); //aborts the record } }

Regards,

Shyamkumar

Re: If short description is same as current short description,then user must not be able to save inc

Shubham_verma — Thu, 08 Feb 2024 09:29:47 GMT

I opened a existing incident,tried to update short description with same name as well as different name .In both cases incident is getting updated.?

Re: If short description is same as current short description,then user must not be able to save inc

Priyanka_786 — Thu, 08 Feb 2024 09:35:54 GMT

@shyamkumar VK :- You need to select update checkbox in your BR so that it will work for update as well if you want to restrict for update.

Kindly mark helpful/accepted if it helps you.

Regards,

Priyanka Salunke

Re: If short description is same as current short description,then user must not be able to save inc

Shubham_verma — Thu, 08 Feb 2024 09:38:30 GMT

Have selected update checkbox in BR,still existing incident is updating .

Re: If short description is same as current short description,then user must not be able to save inc

_Gaurav — Thu, 08 Feb 2024 09:40:36 GMT

Hi @Shubham_verma

Try this

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

var grIncident = new GlideRecord('incident');

grIncident.addQuery("short_description",current.short_description);

grIncident.query();

if (grIncident.next()) {

current.setAbortAction(true);

}

})(current, previous);

Make sure you have not applied any condition on when to run section

Please mark help if this resolves your query
Thanks!

Re: If short description is same as current short description,then user must not be able to save inc

Shubham_verma — Thu, 08 Feb 2024 09:49:05 GMT

After using this script,When I am updating short description with different name its not working,If I use same short description value which was written earlier,then incident is getting saved.

If short desc value is same as earlier then it should not get saved.

Re: If short description is same as current short description,then user must not be able to save inc

shyamkumar VK — Thu, 08 Feb 2024 09:51:01 GMT

@Shubham_verma , How did you perform Testing ?

So when you create an INC giving Short description as XYZ and if this SD already Exists it aborts the Submission

if you want the same for Update as well enable update Operation as well

add gs.log to check if BR is triggering or not

Regards,

Shyamkumar

Re: If short description is same as current short description,then user must not be able to save inc

_Gaurav — Thu, 08 Feb 2024 10:02:44 GMT

@Shubham_verma
The script will take the SD value that you're entering, with all the incidents present in the system, if the SD matches with any other incident's SD, then it will not allow you to save the incident, however, if no SD matches then it will allow you to save the incident.

Re: If short description is same as current short description,then user must not be able to save inc

Shubham_verma — Thu, 08 Feb 2024 10:37:49 GMT

The code you provided is working fine when creating a new incident & update incident but,

when I open a existing incident & SD is XYZ .When I again write XYZ in SD its getting saved.I wanted to abort if I write same SD as written earlier on existing incident.It should not get saved.

Re: If short description is same as current short description,then user must not be able to save inc

Shubham_verma — Thu, 08 Feb 2024 10:39:01 GMT

The code you provided is working fine when creating a new incident & update incident but,

when I open a existing incident & SD is XYZ .When I again write XYZ in SD its getting saved.I wanted to abort if I write same SD as written earlier on existing incident.It should not get saved..

Re: If short description is same as current short description,then user must not be able to save inc

shyamkumar VK — Thu, 08 Feb 2024 10:52:32 GMT

@Shubham_verma , when you update XYZ to XYZ , there wont be any difference right Shubam

Technically when you update from XYZ to YZA and then when you update YZA to XYZ in next update it throughs error

Regards,

Shyamkumar

Re: If short description is same as current short description,then user must not be able to save inc

_Gaurav — Thu, 08 Feb 2024 10:55:26 GMT

@Shubham_verma
There is no sense in writing BR in this case as BR will work only when the record is updated.

See if your incident's SD is XYZ and you're clearing it out and writing again XYZ as the SD then the BR will not run.