1
0
-1

I'm in the process of converting an existing legacy core API delivery service to a newer fluent API delivery service but I'm running into issues with the functionality supported by the Fluent API in regards to the Transaction (Txn) object.

In the TM Core API for a Submission object, there are a few methods that I don't see with an equivalent available for the Fluent API Transaction (Txn) Object. Submission has #getMaxDeliveryAttempts, #getDeliveryProcessAttempts and #setSaveChallengeAnwser but I don't see them available for transaction (Txn). 

Do support for these properties just need to be added to Txn and TxnUpdater?

Thanks,

Blake

    CommentAdd your comment...

    1 answer

    1.  
      2
      1
      0

      Hi Blake,

      The maxDeliveryAttempts and deliveryProcessAttempts should be handled using the DeliveryResultBuilder class.

      With regard to the saveChallengeAnswerm, are you creating new Tasks or updating existing transactions.  If you are doing the latter we can add support for this to the TxnUpdater class.

      regards Malcolm

      1. Blake Hunter

        Hi Malcom,

         

        With the saveChallengeAnswer we are updating existing transactions.

        I need to be able to persist the maxDeliveryAttempts and deliveryProcessAttempts across multiple service calls so that a service can compare the two counts. The DeliveryResultBuilder gives me a new DeliveryResult object that can contain these counts but they do not persist per transaction across service calls. In the previous 4.3 Core API we had access to these properties from the submission object. To convert some existing services the use these properties we would need to have the Transaction (Txn) class support maxDeliveryAttempts and deliveryProcessAttempts like the previous Submission class.

        Can we make a request to have these two properties added to Txn and TxnUpdater?

        Thanks,

        Blake

      CommentAdd your comment...