SOAP and REST Web Services Issues Resolved

The following issues related to FlexNet Operations Web Services were addressed in the 2025 R1 release.

Updating Line Item Quantity with EntitlementOrderService v7 No Longer Failing

(Case 02872466, SWM-21506)

Attempting to update the total quantity (numberOfCopies parameter) of a line item using the createSimpleEntitlement operation with an opType of CREATE_OR_UPDATE no longer results in a stack overflow error. This issue previously occurred for the EntitlementOrderService SOAP web service, version 7.

GetProductCategories Now Returning Product Line Attributes

(Cases 01964245, 02502505; SWM-21024)

In the ProductPackagingService web service, the getProductCategories operation now returns the product line attributes if the product is associated with a product line.

Sample Request

1
2
3
4
5
6
7
8
9
10
11
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:v3.webservices.operations.flexnet.com">
   <soapenv:Header/>
   <soapenv:Body>
      <urn:getProductCategoriesRequest>
         <!--Optional:-->
         <urn:pageNumber>1</urn:pageNumber>
         <urn:batchSize>10</urn:batchSize>
         <urn:returnContainedObjects>true</urn:returnContainedObjects>
      </urn:getProductCategoriesRequest>
   </soapenv:Body>
</soapenv:Envelope>

Sample Response

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <soapenv:Body>
    <getProductCategoriesResponse xmlns="urn:v3.webservices.operations.flexnet.com">
      <statusInfo>
        <status>SUCCESS</status>
      </statusInfo>
      <responseData>
        <productCategory>
          <name>ALL</name>
          <description>ALL</description>
        </productCategory>
        <productCategory>
          <name>ProductLine</name>
          <description>ProductLine</description>
          <categoryAttributes>
            <categoryAttribute>
              <attributeName>ProductLineAttribute1</attributeName>
              <isRequired>true</isRequired>
              <dataType>BOOLEAN</dataType>
            </categoryAttribute>
            <categoryAttribute>
              <attributeName>ProductLineAttribute2</attributeName>
              <isRequired>true</isRequired>
              <dataType>TEXT</dataType>
              <maxLength>128</maxLength>
            </categoryAttribute>
          </categoryAttributes>
        </productCategory>
        <productCategory>
          <name>Uncategorized Products</name>
          <description>Uncategorized Products</description>
        </productCategory>
      </responseData>
    </getProductCategoriesResponse>
  </soapenv:Body>
</soapenv:Envelope> 

Resolved Issue With Recording CREATE Events

(SWM-21703)

Previously, when an entitlement was created using the SOAP web service request createSimpleEntitlement and autoDeploy was set to true, the CREATE event type was not listed on the Search Transactions: Results page for entitlements.

This issue no longer occurs and all event types are displayed on the Search Transactions: Results page.

SOAP Operation getLicenseModelIdentifiers Now Returning License Model

(Case 02880643, SWM-21742)

The getLicenseModelIdentifiers operation of the ProductPackagingService web service now returns the license model as expected. Previously, it returned a null value even if the license model existed in FlexNet Operations.

getEntitlementsQuery and getEntitlementCount Operations Strictly Adhering to expirationDate Parameter

(Case 02905739, SWM-23097)

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 2025 R1 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>

Activation ID Updates Using EntitlementOrderService Web Service Only Allowed in Draft State

(Case 02180694, SWM-22403)

Previously, the updateEntitlementLineItem method in the EntitlementOrderService allowed producers to change the activation ID of an entitlement in a deployed state. This behavior was inconsistent with the Producer Portal UI which did not allow such a change.

Starting in 2025 R1, the activation ID of an entitlement can only be changed if the line item is in a draft state, and this behavior is consistent with the Producer Portal UI.