[CFAMX-14734] CloudLink - Build "Acknowledgment" mechanism for when a CFA Message is pushed on to the sales queue - HotSchedules JIRA

Details

Type: Story
Status: Closed (View Workflow)
Resolution: Done
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
- Cloudlink

Sprint:
2021.R5 CloudLink Sprint 2
SCRUM Team:
Globogym Purple Cobras
Story Points:
3
Work Type Classification:
Sustaining

Description

Inside the CFA Message Processor, we:

Pull a message from tbCFAMessage
Convert it to a Transaction
Then Send it to the Sales Queue

Desired Output: After that, we need to mark the record in tbCFAMessage as done (IsDue=0). The same messages are currently getting picked up each time because we're not setting the IsDue flag to 0.

The MessageExportService does something very similar, see "MessageExportService.cs": "MsmqDelivery"

externalMessage = new ExternalMessage();
                foreach (var export in exports)
                {
                    externalMessage.UserInfo = export.MessageId;
                    externalMessage.PolledDate = export.CreatedAt;
                    externalMessage.MessageSource = export.MessageSource;
                    externalMessage.MessageTypeDescription = export.MessageTypeCode;
                    externalMessage.UnCompressedData = export.ExportData;

                    var message = new Message(externalMessage, _messageFormatter)
                    {
                        Label = externalMessage.MessageSource + ":" + externalMessage.MessageTypeDescription + ":" + externalMessage.UserInfo,
                        Priority = MessagePriority.Normal,
                        Recoverable = true,
                        AttachSenderId = true
                    };

                    messageQueue.Send(message, MessageQueueTransactionType.None);

                    deliveredFiles.Add(new AcknowledgeMessageExportDelivery.Entry(export));

                    _metrics.IncDeliverySuccess();
                }

See how the MessageExportQueueRepository-> AcknowledgeMessageExportDelivery method handles this