SOAP and REST Web Services Issues Resolved
The following issues related to FlexNet Operations SOAP and REST web services were addressed in the 2021 R1 release.
| • | Appropriate Error Now Produced When Transferred Counts Exceed Available Counts |
| • | Feature Replacement for Deployed Products Now Working Properly |
| • | Part Number Associated with Product Now Properly Handled During Product Entitlement |
| • | Milliseconds Separator No Longer Included in Returned Usage Data |
| • | Last Modified Time for Line Items Now Reported Accurately |
| • | “getActivatableItemsQuery” Web Service Results Now Show Correct Number of Copies for Line Items |
| • | Incorrect Entitlement Data No Longer Extracted After Entitlement Updates |
| • | Counts Now Consistent for “searchEntitilement...” Web Services |
| • | EntitlementOrderService Issue Resolved |
| • | Data Extracts Now Properly Encoded |
Appropriate Error Now Produced When Transferred Counts Exceed Available Counts
Previously, the transferLineItem method in the EntitlementOrderService SOAP web service erroneously permitted the transfer of line item counts from one entitlement to another when the requested transfer count was greater than the number of licenses available in the source entitlement.
Now, the transferLineItem method throws an appropriate error when users attempt to transfer line item counts that exceed the number of licenses available in the source entitlement. (The transfer succeeds, however, when the transfer count is less than or equal to the available license count.)
Feature Replacement for Deployed Products Now Working Properly
The REPLACE operation for individual features in the updateProduct SOAP web service now properly replaces a given feature in a deployed project (as long as the editing of deployed products is allowed).
Part Number Associated with Product Now Properly Handled During Product Entitlement
Previously, if the part number for a product that was being entitled was not included during the creation of an entitlement through the EntitlementOrderService SOAP web service, the part number associated with the product was still shown in the End-User Portal. This has been fixed. Now, if the part number for a product being entitled is not included in the web service request, the part number associated with the entitled product is no longer assigned by default.
Milliseconds Separator No Longer Included in Returned Usage Data
In the data returned for the Usage data extract REST API, the timestamps for Transaction Time and Received Time were showing a period (.) as a milliseconds separator even though a milliseconds value was not intended to be included in either timestamp.
2020-08-18T02:09:28.-0700
The unnecessary period could cause parsing issues and has now been removed.
Last Modified Time for Line Items Now Reported Accurately
The lastModifiedDateTime attribute for an entitlement line item now gets updated internally with every checkout or return of a license. As a result, this value (in UTC format) is now accurately reported in the lastModifiedDateTime field in the response for the getActivatableItemsQuery SOAP web service.
“getActivatableItemsQuery” Web Service Results Now Show Correct Number of Copies for Line Items
Previously, in the response for the getActivatableItemsQuery SOAP web service, information for given entitlement line items could occasionally show out-of-date values for the number of remaining and fulfilled line-item copies. This issue is now resolved.
Incorrect Entitlement Data No Longer Extracted After Entitlement Updates
Previously, the Entitlement data extract could show incorrect information if the expiration date or any other entitlement field had been updated using either the SOAP web service method updateEntitlementLineItemRequest or an import job for update entitlement. This issue has been resolved so that the extract now presents correct data.
Counts Now Consistent for “searchEntitilement...” Web Services
Web Service calls to searchEntitlementRequest and searchEntitlementLineItemPropertiesRequest were returning different available count totals for the same activation ID. This issue has been resolved so that the counts are consistent.
EntitlementOrderService Issue Resolved
The error generated when you attempted to update or create entitlements concurrently using EntitlementOrderService methods has been resolved.
Data Extracts Now Properly Encoded
Previously, extracts were not being properly UTF-8 encoded. The extracts are now properly formatted in UTF-8.