As technical users, we have lots of opinions. Some of them are even good! If you have feature requests/suggestions that you’ve posted on the Ideas portal (ideas.sailpoint.com), share them here to get some added visibility and maybe some additional upvotes from your fellow developers.
here are some of mine to get the ball rolling -
-
implement pagination headers in API responses - include “link” headers in API responses for more standardized pagination, rather than just parameter- or query-based pagination.
-
add Duration to aggregation event metadata - include the duration of an Aggregation in the event’s metadata for easier reporting and better visibility into Aggs running longer than they should be.
-
allow Workflow HTTP requests to originate from a specified VA cluster - let us set up our HTTP requests to come from inside the house so we can build workflows that call internal servers that aren’t exposed to the outside world.
-
Workflow Action: execute Powershell script on IQService host - add a new Workflow action to allow us to call a Powershell script (or a single Powershell command) on our IQService host.
-
preserve Workflow test input between tests - retain what we provide as our test input for a Workflow (at least within the same session) so we don’t have to constantly paste it back in every time we run a test.
1 Like
Great idea @sup3rmark
-
Improve Auditing for Source Changes - I’ve discussed this in a topic in the Developer Community before, but in some circumstances, it’s extremely difficult if not impossible to find out what was changed on a source configuration. In some cases, like schema changes, the audit event will spell that out in the details, but others, like changing an accounts query for a JDBC source, do not show the details of what changed. This requires a lot of work on the customer end to document changes, and even go as far as building their own version history feature because the tool only sort of does that in Configuration Hub. I can’t even complete this DIY version history task right now due to a bug in the source modified event that I discussed here.
-
Dynamic Page Titles in HTML -The tag in the section of the HTML on all pages defaults to your org name, which is very annoying when you have multiple tabs open at the same time.
-
SDS Support for Snowflake Tenants in Azure - Currently, secure data share is only available for Snowflake customers who have their tenant deployed in AWS. My request is to make that available for customers who have Snowflake in Azure.
-
Add Risk Level Field to SOD Policy - Currently, the SOD Policy form does not allow an admin to define a risk level for the SOD policy
-
New Certification Type - Entitlement Properties/Metadata - Part of our entitlement lifecycle is to ensure that the entitlement is still valid and up-to-date. No such feature exists in IDN, and it would be very useful. I saw IIQ-I-1229 created in the IIQ section, so decided to create a similar one for IDN.
-
ServiceNow Catalog Integration - Add Filter for sys_user table - Currently, the catalog integration pulls all users from the sys_user table without any filters that can be set from the Setup screen (system properties). This results in user accounts being pulled from tables that extend sys_user, including these in my instance
-
ServiceNow Catalog Integration - Approval Definitions with Search - Allows for more flexible approval flows in ServiceNow
2 Likes
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.