Frequently asked questions
- Date of issue
- 5/3/2023 - Until further notice
This is a compilation of frequently asked questions and answers in regard to stakeholder testing. If you do not find an answer to your question, please contact the project by filling in the contact form in the Enter portal.
1 STAKEHOLDER TESTING
1.1 Is it absolutely necessary to start testing in the given schedule?
No, but we recommend that you should start testing what you can test as soon as possible. You can start testing even if your implementation is not quite ready yet. Early testing allows the testing organisation to use their observations to enhance development. In addition, the project can make changes before rollout on the basis of observations reported during testing, provided that the observations are reported in the given schedule.
1.2 Where can I find the exact addresses of the APIs of the testing environment?
API addresses for use in the testing of data reporting are available on the Stakeholder testing page.
1.3 How can I report errors detected during testing?
You can report observations and errors through the Enter portal. Fill in the observation form in Enter. The form will guide you to give the information we need to resolve the matter.
1.4 Will the project notify testers of errors that have already been detected?
Yes. When a new version of the testing environment is released, a delivery report will be published. The delivery report contains a list of known defects. In addition, the project can give information about defects or errors under Information bulletins in Enter.
1.5 We will test in two parts: system supplier A tests the reporting of data on some products, and system supplier B tests the reporting of data on other products. Should the tests be carried out simultaneously?
Simultaneous testing is not required. It is recommended, however, that stakeholders should do the testing in the schedule provided by the project, so that any errors detected during testing could be addressed before rollout.
1.6 Can we ask you to remove the test data we submit to the testing environment, in full or in part?
The test data submitted to the testing environment cannot be removed, and you should take this into account in your testing plans. The data generated in the testing environment when data reporting is tested will be used later when the requesting of data will be tested.
1.7 How can we check the data we have submitted during testing?
The processing response contains information about the status of the submitted batch. The data submitter requests a processing response separately for each batch, indicating the batch reference. More information is available in Reporting data on loan contracts – API description.
Data reported on an individual loan can be checked through the API for checking loan data. The loan number must be indicated in the request, so you can check the data on only one loan at a time. More information is available in Checking loan data – API description.
1.8 Is testing mandatory?
Testing is not mandatory. By testing, however, the stakeholder can make sure that it has the technical capability to report data to the register and request data from the register as laid down in law. Comprehensive testing enables smooth rollout for all the parties involved.
1.9 When will you release the final technical specifications and API descriptions?
Up-to-date API descriptions are available under Documentation on the Positive credit register’s website. In the case of a development project, it is practically impossible to publish ‘final’ documentation, but the documents published on the website are up to date. Changes may still be made to the documents, for example due to observations reported by stakeholders.
1.10 Will the Suomi.fi data exchange layer be available for testing at some point?
The project has inquired whether stakeholders would like to use the Suomi.fi data exchange layer. It seems that hardly anyone is interested, and so we have postponed the development of the data exchange layer. This means that it will not be available for testing on 2 May 2023.
2 SIGNING UP FOR TESTING
2.1 When multiple operators test together or in a concentrated manner, how do they sign up for testing?
It is not necessary for each operator to sign up separately if the technical contact person and the testing contact person are the same for all the operators. In that case, only one operator needs to sign up. If an operator signing up for testing intends to test on behalf of multiple organisations, the organisations should be specified in the testing start notification.
If the operators have different technical contact persons and different testing contact persons, then it is advisable for each operator to sign up separately.
When signing up, you should also state if you need several artificial Business IDs and test certificates for testing. You can state the number of Business IDs and testing certificates in the start notification. You can also order additional certificates after signing up by filling in the contact form in Enter.
2.2 Who can submit a testing start notification?
Stakeholders sign up for testing in the Enter portal. Only the master user registered for the portal can fill in a testing start notification. Read more about how to select a master user in different situations in section 3 below (Enter portal).
2.3 During signing up, the testing contact person and technical contact person must be specified. Can the same persons act as contact persons for various stakeholders?
One and the same person can act on behalf of only one organisation in Enter. When a person is added as a user to Enter, they can log in with their email address only to the portal view of the organisation for which they were added first. The email address acts as the user ID in the portal, so the same email address cannot be used more than once.
However, if a stakeholder wants a person already acting on behalf of another organisation in Enter to act as its contact person, the person's details can be reported in the additional information field of the form. The organisation’s contact persons must be specified in the testing start notification. In the above case, the master user can assign themselves as the contact person and submit the details of the actual contact persons in the additional information field.
3 ENTER PORTAL
3.1 Our testing is carried out at group level, so one operator tests on behalf of several companies. Who should register as the master user in Enter?
You can select the master user yourself from the testing organisation or a group company, for example. Keep in mind that the master user can view all the organisation’s tickets in Enter. The master user will also process the users’ personal data. The personal data saved in the portal includes the user’s first name, last name, email address and telephone number.
3.2 We have two different system suppliers testing on our behalf. Who should register as the master user for the Enter portal, we (the stakeholder) or one of the system suppliers?
You can agree on who will register in Enter, i.e. who will act as your organisation's master user. We recommend that only one person should register as the master user. The master user then adds other persons who perform testing to the portal as basic users of the same organisation.
Example: The stakeholder's representative acts as the master user. When registering for Enter, the master user enters the stakeholder organisation’s details, i.e. the Business ID and the organisation's name, in the same form as they are in the Business Information System. The master user can add both system suppliers’ testers as basic users to Enter. The stakeholder's representative, i.e. the master user, can see all the tickets submitted by the system suppliers’ testers. The basic users cannot see one another's tickets.
3.3 I have been added as a user to the Enter portal but I have not received an email with a link to set a password. What should I do?
Check that the message is not in your junk mail.
If you received the first email asking you to confirm the user ID, you should then have received an email with a link to set a password. If you did not receive the latter message, the problem may be that you have entered an invalid user ID.
In Enter, your email address acts as your user ID. If you entered something else as your user ID, the message about setting a password will not reach you. Start again: click the link contained in the first email. When you are prompted for a user ID, enter the same email address that is saved in your user information in the portal.
3.4 Can all the users added to the portal see all the tickets and information contained in them? Can the view be filtered? What if we do not want a system supplier to have access to information on products in another system, for example?
The master user sees the tickets of all the organisation’s users added to the portal and can also comment on the tickets. The master user will also process the personal data of all the users added to the portal (name, email address, telephone number). Basic users see only their own tickets in the portal. It is not possible to filter or edit the master user's or the basic user's view.
If necessary, the stakeholder and the system supplier can register for the portal separately, in which case the master users can view and comment on only their own organisation's tickets. In this case, it must be taken into account that a person cannot be added as a user for multiple organisations with the same email address. This applies to both master users and basic users.
3.5 Who receives email notifications from the portal?
Email notifications are sent to the user who has filled in the form in the Enter portal. The Enter portal will send you an email notification when
we have received your ticket
we need additional information to process your ticket
we have resolved your ticket.
You can follow the processing of your own tickets at My tickets on the Enter portal's home page.
3.6 Does the Enter portal show frequently asked questions about testing, and general error situations?
This page with Frequently Asked Questions is linked to Enter's home page, and the page is updated as needed. When a new version of the testing environment is released, a delivery report will be published. The delivery report will be available on the register’s website. The delivery report contains a list of known defects. In addition, the project can give information about defects or errors under Information bulletins in Enter.
3.7 What are the portal languages?
Finnish, Swedish and English. The master user selects a default language for themselves when registering. The master user adds other users with the Adding new users form, specifying a default portal language for each user.
The users themselves can also change the language in Enter.
4 TESTING CERTIFICATE
4.1 Can we get several testing certificates? We are developing a software solution to deliver data to the register, and we want to simulate the functioning of our own system with more than one certificate.
Yes, you can request more than one certificate either in the testing start notification (free text field) or separately by filling in the contact form in the Enter portal. You can request
a) additional artificial Business IDs and certificates connected to them
b) additional certificates for a single artificial Business ID.
Please specify in the request whether you want the certificates to be connected to a single artificial Business ID or to different Business IDs.
4.2 We are developing a centralised data-reporting solution for multiple banks (e.g. in a group of banks). How should we act with the testing certificate?
In the production stage, each lender with the reporting obligation must have a separate certificate. The certificate is used to identify the data source, and the data is saved in the register in line with the certificate. If one operator submits data to the register on behalf of several lenders in a centralised manner, each of these lenders must have a separate certificate.
In the course of testing, you yourself can specify the lenders for which you will be testing actively (and requesting certificates). You can request additional testing certificates by filling in the contact form in the Enter portal.
4.3 If more than one party is testing the reporting of data to the register on behalf of one and the same stakeholder, can they use the same certificate or should each party retrieve a testing certificate of their own?
Operators participating in testing can test on the stakeholder's behalf by using the same artificial Business ID and testing certificate as long as the data submitted to the register is from the same lender. The testing certificate can be copied to the systems in which it will be used. The stakeholder can also request additional testing certificates. Based on the request, certificates can be ordered either for one Business ID or for various Business IDs. You can request additional testing certificates by filling in the contact form in the Enter portal.
4.4 Can we retrieve certificates by using the tool we normally use to retrieve certificates?
You should check this with the tool supplier or in the documentation provided. The information about the Tax Administration's and the Incomes Register's certificate service needed in the integration is found in the instructions on the testing certificate and the interface description of the certificate service.
In addition, a ZIP package including a schema description of PKI and a WSDL description is provided: Technical interface of the interface service – ZIP – For application developers
4.5 The organisation’s technical contact person retrieves the certificate. Because of this, the technical contact person’s telephone number is needed. Does the number have to be Finnish?
No. The technical contact person’s telephone number can also be a foreign number. The telephone number must be given in the international format, including a country prefix, and it must be possible to send text messages to it.