A9 Document management made easy
We have also set the highest and most modern standards for the handling of documents in Albatros and for document output as paper or PDF prints. Albatros 9 should be able to be used independently of third-party products (such as Microsoft Office), but at the same time be able to read, process and output the standard file formats such as “.docx” (MS Word) or “.pdf” (Acrobat Reader etc.).
At the same time, documents in A9 document management or in CRM should be saved, archived and retrieved as often as required in the original for each customer or per action. This applies to e-mails in the same way as for SMS, but also for all types of form letters, contract documents and invoice documents. This creates a complete history for each customer, sustainable communication with the customer and member, but also an increasingly paperless office that can be accessed and viewed from anywhere thanks to the browser-based application at Albatros 9.
This functionality is made possible by the technical integration of the development tools from Tibco (Jasper) and ASPOSE (Aspose.PDf and Aspose.Words) into the Albatros 9 software.
Very smart and ergonomically designed, these tools can be easily and quickly integrated into the backend functionality for software developers. The desired functionality is then created at the push of a button, external documents can be read into Albatros for further processing, and documents generated from Albatros (such as start lists, winner lists, statistics) can be converted into the standard formats (e.g. MS WORD or PDF) when they are output will. With these conversion solutions from ASPOSE, an enormous leap in functionality was achieved in the shortest possible time within the software project.
A9 project manager Steven Bukenberger: “At first, our developers were skeptical whether an“ out of the box ”solution like Aspose was the right way to make our new software application fit for the requirements regarding document input and output . There was also considerable concern as to whether the inclusion of such a tool would in the end create more programming problems and require more compromises than what was ultimately supposed to save time and resources. However, we decided to test implement ASPOSE, which was made very easy for us thanks to the very helpful ASPOSE team. In particular, the good integration instructions, as well as the possibility of a test phase lasting several months, made this possible and led to a successful collaboration, in which we were able to concentrate on implementing our customer requirements and not on basic technical solutions. Ultimately, the integration into our source code was completely easy to implement for my development team. My developers are very satisfied with the Aspose tools and their handling and we already have other tools from the Aspose portfolio in the evaluation. We are all happy that we chose this way of integration with ASPOSE. ”
Further information:
