Require attachment for catalog item in Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-31-2016 10:04 AM
We are preparing to make Service Portal live and going through our service catalog items to make sure everything works ok. One challenge we have is being able to require an attachment before submission. We want to do this always for some forms and conditionally on others. We were using one solution that relied on the DOM but we know that functionality is restricted in the Service Portal. I have seen some solutions but I wanted something simpler that required fewer modifications of OOB code or widgets and would be flexible and easy to reuse. What I came up with is not a perfect solution but it works for now.
We have a global UI Script with reusable functions for catalog items. It prevents having to maintain functions in multiple places and makes them available for all catalog items. Lets name this global UI Script GlobalCatalogItemFunctions. This script needs to be included in your Service Portal via the Theme. Go to Service Portal > Portals and select your portal. Then click the reference icon next to the Theme field to go to its record. There is a related list called JS Includes. Create a new one (Source: UI Script) and set the UI Script to GlobalCatalogItemFunctions. You can set the display name to that as well. Save. The functions in the UI Script will now be available for use in Catalog client scripts. This is the function I am using for getting the attachment count:
UI Script: GlobalCatalogItemFunctions
function getSCAttachmentCount() {
var length;
try {
length = angular.element("#sc_cat_item").scope().attachments.length;
} catch(e) {
length = -1;
}
return length;
}
This is an onSubmit script I am using for a catalog item:
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('You must attach the completed form before submitting this request.');
return false;
}
} catch(e) { //For Service Portal
var count = getSCAttachmentCount();
if(count <= 0) {
alert('You must attach the completed form before submitting this request.');
return false;
}
}
}
Notice in the onSubmit script I used a try/catch block and the first part works in the full UI but not in the Service Portal. In the portal, the document.getElementById... part will not work, but our catch statement performs the method that will work in the portal by calling the getSCAttachmentCount() function which is in our included ui script. That function accesses the angular scope of the catalog item which has an array of the attachments. We just want the count so we use the length attribute. There's no guarantee this will work in the future but for now it will get the job done. It would be nice if there were a function to get attachment information out-of-the-box.
For reference:
Is it possible to require a user to add an attachment before submitting a catalog item?
Catalog service making Mandatory Attachment both application and SP
Service Portal UI Script or Reusable functions in Client Scripts
- Labels:
-
Service Catalog
- 49,066 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2018 01:49 PM
Can confirm it worked for me too. This is one enhancement I think should be requested to SN for future versions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2018 03:57 AM
Hi All,
We have a requirement to make attachment mandate in HR Service Portal. Can we include the above for HR service Portal as well. Please confirm.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2018 04:06 AM
Yes, it works in the HR Service Portal. That's where I first set it up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2018 03:48 AM
Hi.. Is there any changes need to be done if we had to work this on HR service Portal or same code would work in HR Service Portal. Please suggest.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-05-2018 12:57 AM
For future reference:
I struggled a bit to make this work in my instance, but found out that the UI type on the Client script was the issue. This will not work if the UI Type is set to Desktop, but will work if it is set to All.