SOAP and REST Web Services Issues Resolved in 2024.11

The following issue related to FlexNet Operations Web Services was addressed in the 2024.11 release.

getEntitlementsQuery and getEntitlementCount Operations Strictly Adhering to expirationDate Parameter

In previous releases, the search parameter expirationDate in the getEntitlementsQuery and getEntitlementCount operations of the EntitlementOrderService web service also returned entitlements containing line items where the expiration was specified as a duration, and where such line items had not yet been activated.

In the 2024.11 release, such searches using expirationDate return only entitlements that strictly match the specified expiration dates.

If none of the line items in an entitlement meet the criteria for expirationDate or have an empty expiration date, then such entitlements will not be returned.

Examples

When <urn:expirationDate> is passed in the request, at least one of the line items for an entitlement must strictly match the search type for that entitlement to be returned in the response.

expirationDate with searchType ON

The following search criteria return only entitlements that have at least one line item with the expiration date 2024-01-30.

<urn:expirationDate>

<urn:value>2024-01-30</urn:value>

<urn:searchType>ON</urn:searchType>

</urn:expirationDate>

expirationDate with searchType AFTER

The following search criteria return only entitlements that have at least one line item with the expiration date later than 2024-01-30.

<urn:expirationDate>

<urn:value>2024-01-30</urn:value>

<urn:searchType>AFTER</urn:searchType>

</urn:expirationDate>