Case: Generic contact / answer form(s)

[lvbachmann]

What needs to be solved?

Today, many app owners (and other government bodies) have no secure alternative to e-mail when contacting them. And messages sent through DPI and DPV generally don't contain any way of giving an answer.

How do you want it solved?

One (or two) generic forms owned by Digdir, that use eFormidling to send data to the relevant app owner (or other government body). These generally contain a title, message, attachment(s) and for answers; a case-ID.

Alternative solutions

Making a template for the relevant form(s), and let the different app owners make forms as they need them.

Additional context

The eFormidling based solution needs some functionality in the interface between Altinn and eFormidling to be completed before this issue should be solved.

[nkylstad]

@FinnurO is this still relevant?

[lvbachmann]

Note that this case rests on an assumption that the government bodies involved want the messages created to be received by their archive systems. User research should probably be done to prove (or disprove) this assumption before starting any work.

[FinnurO]

Yes; still relevant. Prefered solution is based on eFormidling integration, but other endpoints should be possible.

[nkylstad]

@FinnurO do we have a concrete case for this, or is this something that we just think would be useful? Nothing has happened with this issue in the past 2 years, and if we do not have a concrete case I think we should close it.

[lvbachmann]

@nkylstad I remember registering this issue after a talk with Aud Inger Sviggum at Digdir. It was more of a business opportunity than a concrete case from any service owner, and that is likely to still be the case. You could perhaps check with Aud Inger if we have had any concrete interest in this case the last couple of years that indicate it's a viable opportunity? CC: @FinnurO

[nkylstad]

Thanks @lvbachmann! Will check with Aud Inger if this is still something worth pursuing. In any case I'm not sure that this issue belongs in the altinn-studio repo, since we now use this repo only for the altinn-studio tools themselves. I will create a label for this type of issues for now so I can exclude them from my searches 😊