- Revenera Community
- :
- FlexNet Operations
- :
- FlexNet Operations Forum
- :
- FNO Web Services - emailEntitlement - Result:FAILURE
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
FNO Web Services - emailEntitlement - Result:FAILURE
Hello,
The issue
I am trying to trigger the Entitlement Email via web services API
The call is to : /v3/ManageDeviceService/emailEntitlement
The response is always Status:FAILURE and there is nevermore details on the failure.
I've tried every variation of the parameters that I could think of and always the result is the same.
No Sent email shows up in the web portal. No email arrives at the destination mailbox.
The template for Entitlement and Entitlement Certificate are active and send indicator is true.
I can trigger the email via the web interface.
Questions
Is there any way to get the API to return more information as to why it has failed?
Can someone provide an example of a successful call?
Thanks,
Doug Melvin
Additional info
Some examples of the SOAP request made are pasted below.
The values for UniqueID, EntitlementID and the Email address are all correct.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="urn:v3.webservices.operations.flexnet.com">
<SOAP-ENV:Body>
<ns1:emailEntitlementRequest>
<ns1:entitlementIdentifier>
<ns1:primaryKeys>
<ns1:entitlementId>c38f-c7dc-1eb4-402f-9a11-10d8-e040-c407</ns1:entitlementId>
</ns1:primaryKeys>
</ns1:entitlementIdentifier>
</ns1:emailEntitlementRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="urn:v3.webservices.operations.flexnet.com">
<SOAP-ENV:Body>
<ns1:emailEntitlementRequest>
<ns1:entitlementIdentifier>
<ns1:uniqueId>HID-7874268</ns1:uniqueId>
<ns1:primaryKeys>
<ns1:entitlementId>c38f-c7dc-1eb4-402f-9a11-10d8-e040-c407</ns1:entitlementId>
</ns1:primaryKeys>
</ns1:entitlementIdentifier>
</ns1:emailEntitlementRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="urn:v3.webservices.operations.flexnet.com">
<SOAP-ENV:Body>
<ns1:emailEntitlementRequest>
<ns1:entitlementIdentifier>
<ns1:uniqueId>HID-7874268</ns1:uniqueId>
<ns1:primaryKeys>
<ns1:entitlementId>c38f-c7dc-1eb4-402f-9a11-10d8-e040-c407</ns1:entitlementId>
</ns1:primaryKeys>
</ns1:entitlementIdentifier>
<ns1:ignoreExistingEmailList>false</ns1:ignoreExistingEmailList>
<ns1:validateEmailAddresses>false</ns1:validateEmailAddresses>
<ns1:locale>en-US</ns1:locale>
</ns1:emailEntitlementRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="urn:v3.webservices.operations.flexnet.com">
<SOAP-ENV:Body>
<ns1:emailEntitlementRequest>
<ns1:entitlementIdentifier>
<ns1:uniqueId>HID-7874268</ns1:uniqueId>
<ns1:primaryKeys>
<ns1:entitlementId>c38f-c7dc-1eb4-402f-9a11-10d8-e040-c407</ns1:entitlementId>
</ns1:primaryKeys>
</ns1:entitlementIdentifier>
<ns1:ignoreExistingEmailList>true</ns1:ignoreExistingEmailList>
<ns1:validateEmailAddresses>false</ns1:validateEmailAddresses>
<ns1:emailIdList>
<ns1:emailId>dougmelvin+Dec04@gmail.com</ns1:emailId>
</ns1:emailIdList>
<ns1:locale>en-US</ns1:locale>
</ns1:emailEntitlementRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @DougMelvin ,
I'm not sure if it is a typo but you mentioned you are sending the request to /v3/ManageDeviceService/emailEntitlement. The emailEntitlement web service is in the EntitlementOrderService wsdl. The endpoint to which you should be sending is /v3/EntitlementOrderService
https://{yourFNOsite}.flexnetoperations.com/flexnet/services/v3/EntitlementOrderService
Example of a working call attached. Also note that the most current version of the EntitlementOrderService is V4 (The example provided works with V4 as well).
Best regards,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hello @jberthold ,
Yes that was a mis-paste - the endpoint that I am accessing is /v3/EntitlementOrderService/
Thank you for the example. I'll see what I can do with it to fix my call.
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hello @jberthold ,
From your example it seems that my call is correct. Unless I am getting the wrong type of EntitlmentID.
Is this meant to be the EntitlementID or the UniqueID of the entitlement?
Is there any way to get the system to tell me why it won't send the email?
Thanks,
Doug Melvin
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @DougMelvin ,
I used the entitlementID. Are you sending both the uniqueID and entitlementID? I think you'd want to only use one or the other. I'm not aware of any way to get more information back on why your web service call is failing.