User documentation for Interact

This version does not contain any major changes that indicate that this will be launched as a new main version, but due to major changes in Flow that also affect Interact, we choose to launch both products as new main versions.

Changes in version 2.32

Submitted dialogue, sorting by status - it was discovered that if you sorted by status "Payment failed" or "Payment successful with unknown error", under Submitted dialogue, you where only presented hits within the first 50 forms. It did not search through all submissions for the selected dialogue. This has now been fixed and it now shows 50 possible hits for the selected filter. If there are more than 50 hits, you will also have a choice to show the next 50. (SBF-2099)

Counters and NetAxept - previously a spot was counted when the submitter clicked Pay inside NetAxept's pages. We have now changed this so that the spot is counted at the time the submitter clicks the "Pay now" button in the dialogue. The spot will be vacated if the submitter presses "Cancel" on the payment page at NetAxept, or if the payment attempt fails. A timeout solution has also been added for reservations related to payments that are never completed, e.g. if the submitter closes the browser while on NetAxept's payment pages. The place will be vacated after 30 minutes. NOTE ! If two submitters press "Pay" in Interact at the same time, there is still a risk of overbooking. (SBF-2100)

Rich text editor field - we experienced problems with rich text editor fields where mandatory validation was always triggered. The submitter was not allowed to proceed until he clicked on "Summary" step and then "Next". This has now been corrected, and the mandatory rich text field validates as it should. (SBF-2090)

Signing files during the build process - the previous version of Interact only signed the main application, while now the main application and all dependencies are signed. (SBF-2097)

Changes that are relevant to customers outside Norway

MitID - it has now been opened up for the submitter to log in with MitID in Interact. The submitter can choose between NemAdgang, NemID and MitID when Interact sends the submitter to for login. We use CPR and Pid to connect new ID from MitID with older users, so that submitters can find their previously submitted and started dialogues under «My Forms».

MitID settings are added to the KMD tab. Start by choosing the environment MitID is to be used for (Prod, Internal or Lab), then add Client id and Client secret (1). Click Advanced (2) to add more settings. Here you add the rest of the MitID settings (3) and click Update (4) to save. (SBF-2073, SBF-2031)

Add MitID on the KMD tab

Eboks signing - if the dialogue is to be signed, and the dialogue is created with MitID as the authentication method, then you must activate signing by going to the "Dispatch" (1) tab. Press (+) (2), select «Signing» (3), then OK. Check «Activate signing» (4). The field "Identity" (5) must have a mapping to a field in the dialogue where CPR is filled in. You can choose to change the language and nationality to something other than the default values set to "da" and "DK". (SBF-2073, SBF-2031)

Add signing from the Dispatch tab

Map birth number from dialogue to signing

Dynamic dispatch - from version 2.28.5 to 2.30.4 the XML structure was changed. This has now been changed back to its original structure. (SBF-2074)

OIDC authentication for OData integration - today's OData integration has been extended to support authentication with OIDC (1) in addition to username / password. Different OIDC authentications can be defined under the Authentication tab and the KMD tab, and authentications from both locations can be selected for OData (2). (SBB-1992)

An image showing how to enable OIDC authentication, OData integration

Synchronize OData with Azure Authentication - in Interact you can now update the OData definition in Interact by clicking a button in Dynamic dispatch. If you have access, the data should be updated and you will be notified that everything is ok. If you do not have access, you will be notified that the data could not be updated and that your user does not have access. (SBF-2040)

Postal code module - we have previously experienced Norwegian hits on Danish postal codes. This mostly happened if the selected number did not match Danish postal codes, but also sporadically if the Danish code was actually correct. This has now been corrected. If the Danish postal code does not exist, you will now see «unknown postal code», and the field will open up so you can write the city. (SBF-2079)