question Re: Making an attachment mandatory in a catalog task in Developer forum

Making an attachment mandatory in a catalog task

gnunez — Thu, 02 Mar 2017 18:13:10 GMT

Hello all,

So in a catalog item I created there are attachments that need to be mandatory based on the catalog tasks in the workflow. In the request the first catalog client script works correctly, but the other ones I created for the catalog tasks don't show and instead shows the initial attachment. It basically asks to attach the same attachment over and over again.

Does anyone know how I can make it mandatory only on specific catalog tasks. I already tried checkmarking "Apples on Catalog Tasks" and that didn't work.

This is what I have for the one that does work but keeps showing repeatedly:

Thanks in advance!!

Re: Making an attachment mandatory in a catalog task

AnotherNOWDev — Thu, 02 Mar 2017 18:18:00 GMT

Hello Grace,

This is a pretty good post about it, maybe it can be what you're looking for.

How to Make Service Catalog Attachments Mandatory in ServiceNow | SN Commander

Hope it's useful

Re: Making an attachment mandatory in a catalog task

nayanawadhiya1 — Thu, 02 Mar 2017 18:28:29 GMT

Hey Grace,

Try this -

var sys_id = gel('sys_uniqueValue').value;
var attachment = new GlideRecord('sys_attachment');
attachment.addQuery('table_name','sc_task');
attachment.addQuery('table_sys_id',sys_id);
attachment.query();
if (!attachment.next()) {
alert ('Attach an attachment.');
}

Re: Making an attachment mandatory in a catalog task

gnunez — Thu, 02 Mar 2017 19:13:46 GMT

Nayan,

Do I need to replace some of the values to my own? If so which ones?

Thanks!

Re: Making an attachment mandatory in a catalog task

nayanawadhiya1 — Thu, 02 Mar 2017 19:16:46 GMT

no need to change anything!!!

Re: Making an attachment mandatory in a catalog task

gnunez — Thu, 02 Mar 2017 19:31:57 GMT

It didn't work. Do you think its because I'm not specifying a value? Since I'm trying to trigger it in a catalog task it needs something to tell it when right?

Also, for "Type" I took off the onSubmit and put None instead, don't know if that makes a difference.

Thanks,

Grace

Re: Making an attachment mandatory in a catalog task

nayanawadhiya1 — Thu, 02 Mar 2017 19:42:41 GMT

write "return false;" after alert(); And Client script should "onSubmit" Client script

Re: Making an attachment mandatory in a catalog task

gnunez — Thu, 02 Mar 2017 19:52:46 GMT

It says syntax is OK but there is an error saying invalid return. I also added onSubmit

Here is what it looks like:

Re: Making an attachment mandatory in a catalog task

nayanawadhiya1 — Thu, 02 Mar 2017 19:57:15 GMT

you haven't write the code in between function -

function onSubmit(){

//here paste the code

}

Re: Making an attachment mandatory in a catalog task

gnunez — Thu, 02 Mar 2017 20:04:00 GMT

I noticed that right after I had replied. I added it and tested and still doesn't ask for an attachment.

Re: Making an attachment mandatory in a catalog task

nayanawadhiya1 — Thu, 02 Mar 2017 20:12:19 GMT

Have you check ed applies on catalog tasks??

0r share your full client script screenshot

Re: Making an attachment mandatory in a catalog task

rafael_merces2 — Thu, 02 Mar 2017 20:34:27 GMT

Instead of:

attachment.addQuery('table_sys_id','sys_id');

could you please try with:

attachment.addQuery('table_sys_id',sys_id);

Also, please check this thread: Catalog service making Mandatory Attachment both application and SP

Re: Making an attachment mandatory in a catalog task

gnunez — Thu, 02 Mar 2017 21:36:56 GMT

Yes I checked mark that.

Here is the full screenshot:

Re: Making an attachment mandatory in a catalog task

gnunez — Thu, 02 Mar 2017 21:37:45 GMT

Hi Rafael,

I tried it and it didn't make a difference. Should I be including a script in the catalog task as well?

Thanks,

Grace

Re: Making an attachment mandatory in a catalog task

Vladi1 — Thu, 02 Mar 2017 22:51:25 GMT

we use following script

function onSubmit() {

try { //Works in non-portal ui

var attachments = document.getElementById('header_attachment_list_label');

if (attachments.style.visibility == 'hidden' || attachments.style.display == 'none' ) {

alert("Please be sure to attach all required documentation prior to submitting your request");

return false;

}

} catch(e) {

if ((this.document.getElementsByClassName('get-attachment').length == 0)) {

alert('Please add the required attachment before submitting this request.');

return false;

}

Re: Making an attachment mandatory in a catalog task

gnunez — Fri, 03 Mar 2017 00:27:41 GMT

Hi Vladimir,

Thank you but I tried it and it didn't make the attachment mandatory.

-Grace

Re: Making an attachment mandatory in a catalog task

shloke04 — Fri, 03 Mar 2017 05:11:10 GMT

Hi Grace,

An update on my existing post, you can use Glide Aggregate on Server side which is a Best Practice for better System Performance rather than using Glide Record on Client Side. Write an Before Insert/Update Business Rule on Catalog Task Table as below:

Condition: You can specify the Catalog Item for which you want to configure this validation by dot walking as mentioned below:

Select "Show Related Fields" option from the filter condition first and then dot walking as "Request Item-->Requested Item fields"

Post which you can select the field as "item" is "Your Item Name" as shown below:

Script:

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

var att = new GlideAggregate('sys_attachment');

att.addAggregate('COUNT');

att.addQuery('table_name', current.getTableName());

att.addQuery('table_sys_id', current.sys_id);

att.query();

var count = 0;

if (att.next()) {

count = att.getAggregate('COUNT');

if (count<1) {

gs.addInfoMessage("Please attach Attachment");

current.setAbortAction(true);

}

})(current, previous);

Hope this helps.Mark the answer as correct/helpful based on impact.

Regards,

Shloke

Re: Making an attachment mandatory in a catalog task

gnunez — Mon, 06 Mar 2017 18:15:00 GMT

This worked, thank you!

Re: Making an attachment mandatory in a catalog task

manibaig — Wed, 15 Jan 2020 23:54:30 GMT

This is fine but even though it doesn't let the user insert a record without attachment. It still occupies the next number sequence on the table. for example in your example SCTASK000 number is taken even though record was rejected

Re: Making an attachment mandatory in a catalog task

John H1 — Tue, 14 Sep 2021 16:15:18 GMT

I'm getting an invalid update error .... Match not found, reset to original