Can You Add Non-Searchable Attributes Using Source Maps in SailPoint?

When delving into the intricacies of SailPoint, one common query that comes up is about source maps and whether you can add non-searchable attributes. You might be thinking—what's the big deal with non-searchable attributes? Well, let me tell you, this is where the magic happens!

So, the short answer to your burning question is yes, indeed! You can add non-searchable attributes through source maps in SailPoint—and here’s the kicker—they’re stored in a CLOB format, not in an indexed column. Isn’t that fascinating? You might wonder why CLOB (Character Large Object) is preferred for these attributes. Before we dive deeper, let’s step back for a moment and understand the broader picture!

What’s the Deal with Source Maps?

Source maps in SailPoint are like the undercurrents of a river; you might not see them at the surface, but they play a crucial role beneath. They’re used primarily for mapping and synchronizing identity data from your diverse data sources. Imagine juggling multiple balls in the air; that's how managing identity data often feels! Including non-searchable attributes helps to enrich your identity profiles without burdening the performance of your system.

Why Use Non-Searchable Attributes?

You might be wondering—aren’t we supposed to be all about efficiency and performance? Absolutely! But remember, not every piece of data in your identity system needs to be searchable. Some data is simply supplementary or contextual. Think of it as the garnish on a well-plated dish. It adds flavor but doesn’t always need to be the main ingredient. And that’s where CLOBs shine: they allow you to store large data blocks efficiently.

For example, say you've got lengthy descriptions, notes, or compliance-related information. These can be critical for certain applications or processes, yet don’t require exhaustive search capabilities. CLOB storage offers a lightweight alternative, ensuring that your regular queries remain quick and responsive without encumbering your indexed columns.

Performance Benefits: Less Overhead

Now, while we’re talking about efficiency, let’s not forget the performance angle! When you include a lot of attributes in your identity management system, indexing all of them can slow things down—like trying to run a marathon in a pair of high heels. Ouch, right? By using CLOBs for these non-searchable attributes, you avoid that performance overhead. Your typical search queries won’t be slowed by irrelevant data, leading to snappier results and a smoother user experience.

Practical Applications of CLOBs in SailPoint

Imagine a real-world scenario: a compliance department may need to keep lengthy reports on each user for audit purposes, but they don’t need to search for these reports routinely. Storing this data in a CLOB allows it to reside comfortably within the user’s profile whenever needed, while keeping the primary database lean and efficient.

Wrapping Up

In summary, yes, SailPoint does allow customization via non-searchable attributes through the use of source maps, stored cleverly in CLOB format. This means you can enhance your identities with rich data while keeping search performance intact. So, the next time you're wading through your identity governance strategies, remember the importance of CLOBs—you’ll thank yourself later!

Have you used non-searchable attributes in your SailPoint journey? What was your experience like? Let’s chat in the comments!