Roman_Bessnow | 2020-12-21 23:27:18 UTC | #1
Hi. I am running the Pure Cloud Faxing via API and have a question to ask.
As I send a fax from my Genesys outbound fax line to my Genesys Inbound Fax line I get multiple unique IDs from my sent event. As the Fax arrives to my Inbound Fax line, I have multiple unique IDs from the received fax event from my FaxDocumentEntityListing object. What I am looking for would be identification that would join the sending and receiving into one narrative. I do not want to OCR the send ID from the received PDF file. I am looking for a back-end solution. It looks like the default inbound filename "fax.pdf" and the default name "Fax from tel:+xxxxxxxx Do you know where it is being configured and might it be set dynamically? Are any other options on a table?
anon59476161 | 2020-12-21 13:10:26 UTC | #2
Hello,
The inbound filename and the name of the document cannot be configured or customized currently. Instead, the conversation Id can be used to link the outbound and inbound faxes (assuming sent and received within the same org).
The id field returned in the response of the /api/v2/conversations/faxes API is the conversation ID. When the inbound fax is saved as a document in the receiver's workspace, the conversation ID is added as an attribute to the document however it is not part of the /api/v2/fax/documents API's response.
A user who has access to the conversation ID and the received document can locate the received document by sending the conversation ID as a filter to /api/v2/contentmanagement/query POST API.
Example payload: { "filters": [ { "name": "conversationId", "operator": "EQUALS", "type": "STRING", "values": [ "5721df98-c392-402e-839e-ee5a36966d6c" ] } ], "pageNumber": 1, "pageSize": 10 }
Roman_Bessnow | 2020-12-21 16:03:46 UTC | #3
Jananee, thanks you very much, that was exactly what I was looking for.
Roman_Bessnow | 2020-12-22 18:04:49 UTC | #4
Jananee, I think I need your help. The same org and the same user. I pulled the same user faxes with GetFaxDocumentsbyBatch and I am passing the V2.Model.FaxDocument.Id. The objective is to get the ConversationID that was submitted during the sending, one that should be stored as the attribute to the sent document. I do have the ConversationID in my DB, stored during my sending the fax. So, now I have a collection of sent faxes with their ConversationIDs and a collection of received faxes and I need to find the relation between them. I am using the logic you proposed but I always get Result.Results.Total=0 and Result.FacetInfo.Attributes.Count = 0. Did I misunderstood you or I do anything wrong?
public async Task<QueryResults> GetDocConversationID2(string docID) { //cook filter ContentFilterItem filter = new ContentFilterItem(); filter.Name = "conversationId"; // should be 8e9f2095-d780-47ae-bbba-8e71f444f498 filter._Operator = ContentFilterItem.OperatorEnum.Equals; filter.Type = ContentFilterItem.TypeEnum.String; filter.Values = new List<string> { docID };
List<ContentFilterItem> FiltersList = new List<ContentFilterItem> { filter };
// get sent ConversationID by Inbound FaxDocument.Id return await contentManagementApi.PostContentmanagementQueryAsync(new QueryRequest { Filters = FiltersList }); }
anon59476161 | 2021-01-05 12:51:38 UTC | #5
The association is actually the other way around. The conversationId is stored as an attribute of the received fax document, not the sent document and it is also different from the sent/received fax's document Id.
- Send fax using the /api/v2/conversations/faxes API. Save the id in the response as conversationId.
- Send the conversationId (not fax Id as in your example) as a filter to /api/v2/contentmanagement/query POST API.
- The response will have the received fax document. Extract the document Id from the response.
- Use /api/v2/fax/documents/{documentId} API to get more details about the received fax document.
Hope this helps.
Roman_Bessnow | 2021-01-06 01:37:34 UTC | #6
Jananee, thank you very much. Will certainly try it.
system | 2021-02-06 01:37:35 UTC | #7
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 9511