You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the notification api to send emails to customer service. In the form users have filed an email were they can be reached. These emails now fail and we need to rewrite emails to name.lastname att organization dott org. And customer service needs to rewrite back to [email protected].
Adding some background: The rationale for introducing the validation is that in Altinn3, all content is user-defined, wheras in Altinn2 this is a "managed process". As far as we could see, there were no use of links/emails (in line with the content guidelines; https://altinn.github.io/docs/utviklingsguider/varsling/#hva-skal-et-varsel-ikke-inneholde). Thus we enabled a hard enforcement of this. In retrospec we should have done more analysis of new/current Altinn3-usage, and also published/versioned the feature as a breaking change.
Description
We are using the notification api to send emails to customer service. In the form users have filed an email were they can be reached. These emails now fail and we need to rewrite emails to name.lastname att organization dott org. And customer service needs to rewrite back to [email protected].
Additional Information
This worked in June-24 and was used in application kyv/tilgangsoknad-pilot , now digdir/tilgangssoknad . https://altinn.slack.com/archives/C02EJ9HKQA3/p1726485543751009
The text was updated successfully, but these errors were encountered: