/**
     * Array of web crawling configuration IDs to process.
     * If null, all available web configurations will be crawled (when no other config IDs are specified).
     */
    protected String[] webConfigIds;

    /**
     * Array of file system crawling configuration IDs to process.
     * If null, all available file configurations will be crawled (when no other config IDs are specified).
     */

But I'll show you how to improve that next. 🤓

## Custom Operation IDs and Better Method Names { #custom-operation-ids-and-better-method-names }

You can **modify** the way these operation IDs are **generated** to make them simpler and have **simpler method names** in the clients.

 *   -n, --name name               : Name for the crawling session
 *   -w, --webConfigIds ids        : Comma-separated web config IDs
 *   -f, --fileConfigIds ids       : Comma-separated file config IDs
 *   -d, --dataConfigIds ids       : Comma-separated data config IDs
 *   -p, --properties path         : Properties file path
 *   -e, --expires days            : Expires for documents (in days)

            }

            // Compute Resource Group IDs with Resource Domain ID to get SIDs
            this.resourceGroupSids = new SID[resourceGroups.length];
            for (int i = 0; i < resourceGroups.length; i++) {
                this.resourceGroupSids[i] = new SID(resourceDomainId, resourceGroups[i].getId());
            }

            // Compute User IDs with Domain ID to get User SIDs

    }

    /**
     * Retrieves web crawling configurations filtered by a list of IDs.
     * If the ID list is null, returns all available configurations.
     *
     * @param idList the list of configuration IDs to retrieve, or null for all configurations
     * @return a list of WebConfig objects with the specified IDs
     */
    public List<WebConfig> getWebConfigListByIds(final List<String> idList) {

     */
    protected Function<Map<String, Object>, Long> requestHandler = params -> {
        final FessConfig fessConfig = ComponentUtil.getFessConfig();
        final String[] ids = idFinder.apply(params);
        if (ids.length == 0) {
            return 0L;
        }
        final SearchEngineClient client = ComponentUtil.getSearchEngineClient();
        if (bulkRequestBuilder == null) {

                    return cookie.getValue();
                }
            }
        }
        return null;
    }

    /**
     * Stores the document IDs associated with a search query for tracking purposes.
     * This method caches the document IDs returned for a specific query to enable click tracking and analytics.
     *
     * @param queryId the unique identifier for the search query

    }

    /**
     * Retrieves a list of session IDs with their document counts from the search engine.
     * Uses aggregation to get session segments and their corresponding document counts.
     *
     * @param searchEngineClient the search engine client to perform the query
     * @return a list of maps containing session IDs and their document counts
     */

Pero te mostraré cómo mejorar eso a continuación. 🤓

## Operation IDs Personalizados y Mejores Nombres de Métodos

Puedes **modificar** la forma en que estos operation IDs son **generados** para hacerlos más simples y tener **nombres de métodos más simples** en los clientes.

 *
 * <p>
 * The class uses a static {@code idCount} to generate unique IDs for each access result.
 * The {@code idCountLock} object is used to synchronize access to the {@code idCount} variable,
 * ensuring that IDs are generated in a thread-safe manner.
 * </p>
 *
 * <p>
 * The class also provides methods to get the count of access results for a given session,