For out of the box content this issue is resolved in vRealize Automation 7.3 vRealize Orchestrator plugin, vRealize Automation 7.3 is available at
VMware Downloads.
To resolve this issue for custom content and API calls you should adjust your API query or workflow to specify the paging information to overcome the limitation of 100 entries per call. The below gives examples on what the customization may look like depending on your use case and environment:
- When using the REST API, specify the paging information by appending the following to the end of your API call:
?page=<page>&limit=<limit>
For Example:
When calling for catalogItems, this will look like:
https://<vrva_url>/catalog-service/api/consumer/resources?page=1&limit=<some_number_less_than_100>
For more information on the vRA REST API and its functionality please refer to the documentation's vRealize Automation 7.2 Developer Resources Guide .
- When using a vRealize Orchestrator workflow, include host and pagination details for the vCAC plugin:
For example:
var myvCACCAFEOdataQuery = new vCACCAFEOdataQuery();
var myFilter = vCACCAFEFilterParam.substringOf("name" , "'" + nameFilter + "'");
myvCACCAFEOdataQuery.addFilter([myFilter]);
var myvCACCAFEPageOdataRequest = new vCACCAFEPageOdataRequest(page , pageLimit , myvCACCAFEOdataQuery);
var items = host.createCatalogClient().getCatalogConsumerCatalogItemService().getCatalogItems(myvCACCAFEPageOdataRequest);
System.log(items);