Closed khanrn closed 6 months ago
Not sure this needs to be linked to the recipient. Might be enough to link it to the order?
Not sure this needs to be linked to the recipient. Might be enough to link it to the order?
I was thinking the same. If the application owner want to create notifications for multiple resources they would need to create multiple order, but I don't think this will be an issue.
Closing issue as it is not relevant. resourceId has been added to NotificationOrder model
Description
When a notification order is getting generated it may affiliated with a service. In other word the notification to person identified by national identity number with service affiliation should posses an
resourceId
.Consideration
This issue is closely related to #436.
Tasks
API
resourceId
property to external recipient model,RecipientExt
resourceId
property should benullable
as this is optional, because is could be with or without service affiliation.resourceId
to relevant mapper methods inOrderMapper.cs
NotificationSummaryMappers
Core
Recipient.cs
resourceId
property asnullable
EmailRecipient.cs
resourceId
property asnullable
SmsRecipient.cs
resourceId
property asnullable