.png%3Falt%3Dmedia%26token%3D8174d25a-bbf3-43b6-9e21-3b022d5cd5ec)
.png%3Falt%3Dmedia%26token%3D8174d25a-bbf3-43b6-9e21-3b022d5cd5ec)
6. Put Live
Up to now, Atfinity has carefully kept track of every configuration change we have done so far. Now it's time to put them live which means that Atfinity will implement all our changes. After that, we will be able to start our account opening process.
Atfinity provides a list of changes done to the configuration. There we can find everything we have done, from creating the ontologies 'Contract' and 'Person', to creating the document as well as writing the rule's condition.
It could have happened that we forgot something during configuring, like adding a newly created rule to a process. This does not cause any error, but it might not be what we have intended. Therefore, Atfinity will warn about it. If we wish, we can ignore the warnings and still put live.
However, if we have done a mistake that would lead to a fatal error, Atfinity lets us know with an error message. As long as the error is not taken care of, we won't be able to put live. If we have followed this guide painstakingly, there shouldn't be any errors or warnings and we can continue to the next step.
When everything is in order and all possible errors are taken care of, we can put the configuration live.
It is good practise to ensure that changes made to the configuration behave the way they were intended to. Let's go to the Dashboard where we can start a new case.
This is how our process should behave:
- When we open the new case, what we should see is an instance of a 'Contract' as well as the 'Account Type' information that needs to be provided. Clicking on it should open a dropdown from which we can select 'Individual Account'.
- As soon as 'Individual Account' is selected, a lot of things happen at once. First, the rule we created becomes active and ensures that there is a person who's account holder. That's because the information about the account type is now 'individual' which was the rule's condition in order to evaluate to true. Second, the document condition evaluates to true as well because now both a contract and a person are part of the case. This leads to all the remaining information we created being asked.
- We then should be able to enter a first and last name as text and select a date of birth.
- Approving or declining a case should also be possible. Doing either one should close the case.
If you have done the exercises throughout the guide and have, e.g. created an additional rule that warns when the account holder is underage, you should test its behaviour too. When you enter yesterdays date as a date of birth, there should be a warning. Similarly important, if you then change the date of birth to a date from the last century, the warning should disappear again.
Last modified 1yr ago