SailPoint Identity Services Search Subscription Notification Email Template Bug

Hello. I am having trouble with the following default email template:

It seems like in particular the “## ## Exclusion of detailed results” section is not rendering as expected. My test subscription has set “Add a detailed summary of results to the report” toggled on. I attempt to copy and paste the entire default template section into the email template “Body” → “Source Code” section. If I don’t manually remove “## Exclusion of detailed results” from the template, it seems like everything after that point just fails to render. Once I remove it, I see no detailed preview report being generated anyways on “Send Test” selection in the Search Subscription flow. However, when an actual subscription email is generated via the schedule, I see a barebones “Preview cell” table that has no relevant data rendering:

Am I mistaken in that this section of the template should work OOB, or am I missing that I need to make manual updates to get the preview results logic to work? It would be very nice if the “Send Test” button also honored the “Add a detailed summary” config option, which it appears to not at the moment; it would also be nice if the “Send Test” button displayed an error if the email failed to render as well, because I commonly ran into having buggy template issues where that Subscription “Send Test” button would still display as if the email sent properly.

1 Like

I am also now noticing that “Send Test” button seems to wrongfully display that a search query returns no results. This is despite running the query in the UI clearly returning results. Again, this is with the default email template in place except for the “## ## Exclusion of detailed results” as noted in original post. The relevant bit from the default template would appear to be this: #if (!${searchResults.isEmpty()}). I was not seeing this issue with other test queries. This is very frustrating to test.

We are also seeing an issue with this template. We updated the email body to reflect the default Search Subscription Notification Email Template but the subscription emails would not send at all.

Hi Elizabeth, I ended up opening a support ticket. I think we might have figured out what was going on for us, which I’ve included here in case it might help you:
“”"
I did find the previous report of a Saved search subscription not sending emails. the issue here has to do with how the search query is being saved. Please take a look at the information below to see if this process solves the issue for you:

===============================================

Saved search:

{ "id": "bef6468c-5d3f-4c7d-9f4d-91def4e4ce91", "name": "Failed Aggregations last 2 hours", "description": null, "owner": { "type": "IDENTITY", "id": "2c9180877dfe669c017e0c950c133ace" }, "ownerId": "2c9180877dfe669c017e0c950c133ace", "public": false, "created": "2022-10-18T20:23:01.764Z", "modified": "2022-10-18T20:23:01.787Z", "indices": [ "identities", <------ problem "*" ], "columns": { "identity": [ { "field": "displayName", "header": "Display Name" }, { "field": "firstName", "header": "First Name" }, { "field": "lastName", "header": "Last Name" }, { "field": "email", "header": "Work Email" }, { "field": "created", "header": "Created" }, { "field": "attributes.cloudLifecycleState", "header": "Lifecycle State" } ] }, "query": "type:source_management AND status:FAILED AND created:[now-2h TO now]", "fields": null, "orderBy": null, "sort": null, "filters": null }

In this case, when they saved the search, it was indexed on “identities”. That query won’t return any identities. So it’s always empty.

I’m guessing they saved the query when the results were empty. In that case it defaults to indexing on “Identities”. They can edit the “indices” attribute with the API,

https://developer.sailpoint.com/idn/api/v3/saved-search-update

But probably easier to recreate the search. Before saving, set the filter to “Events”.

===============================================

“”"

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.