Class with many parameters, beyond the Builder pattern
<h2>Context</h2>

<p>Suppose you have a component with a great many options to modify its behavior. Think a table of data with some sorting, filtering, paging, etc. The options could then be <code>isFilterable</code>, <code>isSortable</code>, <code>defaultSortingKey</code>, etc etc. Of course there will be a <em>parameter object</em> to encapsulate all of these, let's call it <code>TableConfiguration</code>. Of course we don't want to have a huge constructor, or a set of telescopic constructors, so we use a <em>builder</em>, <code>TableConfigurationBuilder</code>. The example usage could be:</p>

<pre><code>TableConfiguration config = new TableConfigurationBuilder().sortable().filterable().build();   
</code></pre>

<p>So far so good, a ton of SO questions deals with this already.</p>

<h2>Moving forward</h2>

<p>There is now a ton of <code>Tables</code> and each of them uses its own <code>TableConfiguration</code>. However, not all of the "configuration space" is used uniformly: let's say most of the tables is filterable, and most of those are paginated. Let's say, there are only 20 different combinations of configuration options that make sense and are actually used. In line with the DRY principle, these 20 combinations live in methods like these:</p>

<pre><code>public TableConfiguration createFilterable() {
  return new TableConfigurationBuilder().filterable().build();
}

public TableConfiguration createFilterableSortable() {
  return new TableConfigurationBuilder().filterable().sortable().build();
}
</code></pre>

<h2>Question</h2>

<p>How to manage these 20 methods, so that developers adding new tables can easily find the configuration combination they need, or add a new one if it does not exist yet?</p>

<p>All of the above I use already, and it works reasonably well if I have an existing table to copy-paste ("it's exactly like Customers"). However, every time something out of the ordinary is required, it's hard to figure out:</p>

<ul>
<li>Is there a method doing exactly what I want? (problem A)</li>
<li>If not, which one is the closest one to start from? (problem B)</li>
</ul>

<p>I tried to give the methods some very descriptive names to express what configuration options are being built in inside, but it does not scale really well...</p>

<h1>Edit</h1>

<p>While thinking about the great answers below, one more thing occurred to me:
Bonus points for grouping tables with the same configuration in a type-safe way. In other words, while looking at a table, it should be possible to find all its "twins" by something like <em>go to definition</em> and <em>find all references</em>.</p>