The main difference between Flatfile Portal 2.0 and Flatfile Portal 3.0 is that Portal 3.0 runs server-side while Portal 2.0 runs in the browser, client-side. All major differences between Portal 2.0 and 3.0 begin with the server-side implementation of Portal 3.0.
Running on servers allows Portal 3.0 to implement some advanced features, such as interruption protection that allows users to close and resume matching sessions. Portal 3.0 is also not limited by your local hardware, allowing faster data processing and painless data onboarding. And because of its server-side implementation, Portal 3.0 is also capable of securely saving your history of matching decisions, something not possible with Portal 2.0’s browser-based application, and improve its matching suggestions using your historical decisions.
Because Portal 3.0 is the newest iteration of our product, there are some features that are not yet available. However, we are planning on implementing the following features soon:
- XML File uploads
- TXT File uploads
- I18N - translation of Flatfile across different locales
- Dynamic Schemas - System Managers can create a dynamic template structure in Flatfile when their data model is customizable by a Data Owner
- Manually inputting data instead of importing a file
- Programmatically creating new fields