ISC Saved Search displays wrong indices and wrong columns

Feedback Bugs
,
1

Hi all, :slight_smile:

I used the following as json body for creating a saved search, using this documentation: create-saved-search | SailPoint Developer Community

{
  "name": "Angelo test saved search",
  "description": "test",
  "indices": [
    "accessprofiles",
    "roles"
  ],
  "columns": {
    "role": [
      {
        "field": "name",
        "header": "Name"
      }
    ],
    "accessprofile": [
      {
        "field": "name",
        "header": "Name"
      }
    ]
  },
  "query": "name:Angelo",
  "fields": null,
  "orderBy": null,
  "sort": [
    "name"
  ],
  "filters": null
}

I then logged into the UI, went to search, selected the newly created saved search, and did not just see roles and accessprofiles, but also identities and entitlements, even though I did not specify those in my saved search indices. To me this is bug #1.

Also I saw one column name appearing under the access profiles, which makes sense as I configured that in the JSON. However, if I then click on the roles tab, I do see more columns, even though I also configured the columns for roles in the JSON. To me this is bug #2.

As a result, our end users complain that they have to reselect the columns each time, even though the saved search has this configuration stored.

We also observed that our end users go to the UI, write down a query, select the indices through the filter icon, then go to each tab and select the desired columns. After doing all of this, they save the search through the UI. However, they then notice that the indices are wrong as well (containing a * and only one additional index in the JSON) and that the columns are not stored properly in the saved search JSON as well. To me this is bug #3.

Kind regards,
Angelo

1 Like
2

Update from SailPoint Support

1 Like
3

May I ask when you have created the support ticket? The original post is from end of August, two and a half months ago.

4

I created the Support ticket on the same day I created this topic in this forum, on the 29th of August, which is 75 days ago.

Please see screenshots below.

image
image907Ă—164 13.9 KB

how_reporting_bugs_to_sailpoint_support_sometimes_look_like
how_reporting_bugs_to_sailpoint_support_sometimes_look_like832Ă—2793 231 KB

1 Like
5

75 days, not bad at all to get an answer.

So if the ticket is getting closed, how will SailPoint :sailpoint: inform us when the issue is resolved/improved? Will they update this post?

6

I got another update from SailPoint Support:

In general, I notice different behaviors from SailPoint Support.

  1. They keep the ticket open until the bug is resolved, then they inform me and I test and let them know. SailPoint Support is (unfortunately) not adding information in this forum, so I then have to close the loop by pasting the information here and letting others know that the bug is fixed. This process of SailPoint keeping the support ticket open until the bug is fixed does not happen often, but I do prefer this the most. Perhaps this is only done if it is clear that the bug is going to be fixed quite quickly?
  2. They create an internal ticket, share the number with me and close the support ticket with the instructions to follow up with our Customer Success Manager (CSM) from SailPoint for closure. Unfortunately, our previous and also our current CSM have informed us that since I report so many bugs, it takes them too much time to keep tracking all these internal tickets, so they only look at items tagged P1 or P2. I can still incidentally ask the CSM to check for P3 or P4 issues, but then I have to proactively reach out and I will not be informed the moment the bug is resolved. This happens the most often.

In this case, it will be different as I also did not get an internal ticket. I think SailPoint is not really going to fix the bug. To me, it sounds more like a “We understand the toilet in the train is broken, but in around half a year from now we plan to use a new train which should not have this issue” type of thing. Therefore, I think we will get informed of the indirect fix of this issue by SailPoint making an announcement in this forum in around half a year from now with a statement like:

:bangbang: SailPoint® is excited to announce that …

1 Like