About Client
The client is a 70 year old furniture manufacturer based out of Wadena, Minnesota, USA. It mainly deals into affordable luxury outdoor patio furniture offered in 30 collections. These include tables, chairs, chaises, loveseats, sofas, ottomans bar and balcony stools/chairs stools made up of durable aluminum, steel, and cast frame. The client is serving various industries such as restaurants, hotels, resorts, hospitals etc.
It offers outdoor patio furniture products to furniture retailers across North America. The company’s sales improved when it patented the Bottemiller’s swivel rocker mechanism in 1956, as this mechanism made the client popular among American households. Today it is on is on a journey to build its future on consumer and contract needs, innovative new products and global opportunities.
The Challenge
The client has multiple Windows applications for internal purposes such as for various categories of the furniture and fabrics. These applications are designed for offering customized products to the customers. The challenges faced by the client are:
- The applications are desktop based and cannot be accessed from anywhere, therefore creating a delay in attending to the requirements and customization of the products
- As these are multiple applications for various functions, there is no single platform to access all of them at one place. The employees have to login separately on all of them to fetch the details.
- Windows applications do not look appealing or user friendly.
- The client wanted only the authorized users to access the new web based applications
- The products were to be better categorized with the addition of Zebra printer that would print the tickets with barcode correctly and attach those with the products for identification.
The Solution
01.
Developers at Programmers.io became a trustworthy IT partner of the client and suggested Angular for front-end development and Java as the backend technology
02.
Web based applications need to have robust security. Therefore, our team used existing database i.e. DB2 and Oauth 2.0 to provide the access token authorization to the users.
03.
The client wanted the application to have Single Sign-On functionality for all the applications so, our team used the Oauth server for the same.
04.
Our team added the feature of authorization based access to the application leveraging the facilities provided by Oauth server and Java APIs.
05.
The development team also added the functionality in which the JAVA API could create dynamic tickets with barcode and that could be printed using the Zebra printer. These tickets are created to be attached with a specific product in order to categorize them properly.
