Here you will find everything about "Integrable".
- Product design to customer requirements
- Excel import & export (offline data)
- Connection to backend systems
- Application interface for application data
Modern software solutions are often a combination of specialized individual components. In contrast to the monolithic "all-rounders" of the past, specialized systems are focused on their area of responsibility and are combined into complete solutions using service-oriented architecture (SOA).
The focus of AFS is on structured data capture. Online dialogs can be optimally implemented with AFS. AFS has interfaces to all surrounding systems relevant to data capture.
The checking and business logic of specialist applications can also be easily integrated into AFS forms. The integration of online dialog and downstream specialist system eliminates the duplication of code.
AFS forms can also be integrated into existing content management systems (CMS) and portals.
Product design in line with customer requirements
AFS is continuously developed according to customer requirements. New AFS versions are regularly made available as part of all-in maintenance.
aforms2web coordinates the design and financing of product enhancements across customers and countries. The AFS user groups that take place twice a year in Switzerland and Austria are key to this. Our customers meet here to discuss joint plans, projects and successes. This results in development synergies from which all AFS clients benefit.
Excel import & export (offline data)
Each AFS form can be assigned a freely configurable Excel template. This makes it possible to export recorded form data to Excel, edit the data offline and load it back into the form. The Excel comment function is used for simple mapping of the form fields in the Excel template.
Connection to backend systems
Backend system -> AFS
AFS forms can be filled with data from backend systems. Different technologies are available for the connection:
- SQL: Direct query of relational databases with SQL statements (e.g. for value lists)
- LDAP and Active Directory: Direct query of directory services (e.g. for user rights and organizational structures)
- aforms inbox: Direct query of the aforms inbox (e.g. for accessing sent application data)
- Webservice (SOAP/REST): Direct use of web services (e.g. for calling business logic in the backend system)
The queried backend information can be assigned to AFS fields using mapping tables.
AFS -> backend system
The application data recorded in AFS can be written to backend systems. Various technologies are available for the connection:
- SQL: Writing directly to relational databases with SQL statements (e.g. direct connection form -> backend system
- aforms inbox: Saving applications in the aforms inbox
- aforms inbox: Writing status information and metadata (e.g. for processing processes)
- . e.g. for transaction processing)
- Webservice (SOAP/REST): Direct use of web services (e.g. for writing application data to backend systems)
In many administrative procedures, it is possible to calculate costs and fees directly. E-payment enables payment to be made directly as part of the application process. This means that particularly citizen-friendly e-government services can be offered.
AFS supports the connection of well-known e-payment providers such as BillingOnline, QPay, PayUnity-Flex, Payrexx and SaferPay. This ensures that the application is only submitted after payment has been confirmed.
More about "Integrable"
The AFS application interface is divided into the following functions:
Optional transformation of an input file in the specific format of the third-party application using XSL into the AFS application format before further processing.
Write over the application data transferred from the input XML with optionally specified values (list of field references and values)
Check the input file according to the configured validation and dynamics of the online form (simulation of the input).
Optional acceptance of the application and confirmation by applying the confirmation of receipt
Optionally return the signed request as
- XML (EApplication)
- HTML file with embedded XML data
- PDF print form
to the third-party application including confirmation of receipt