2024: MultiValue Adapts to Change

<< back Page 7 of 8 next >>

Malcolm Carrol, Director, BlueFinity

The possibilities that AI now offers the MultiValue market in respect to interaction with customers and in-house personnel are continuously evolving. This serves to highlight the ever-growing need for a more modern user interface to work as an integral part of legacy MultiValue systems.

BlueFinity has been incorporating elements of AI into Evoke-built apps for some time now. The flexibility of the low-code development platform has allowed us to provide customers with routes to establish learning mechanisms into their apps to meet specific business requirements. To supplement this, we make customizable APIs available to customers so that third-party facilities such as chatbots and ChatGPT may be included.

Apps built using Evoke that “learn” include these examples: a medical practice app that learns the different medications prescribed by senior doctors for different conditions/illnesses and offers these as options to junior doctors when they are treating a specific condition/illness and a retail shopping app that identifies people who purchase car accessories and then suggests they consider, or offers a special deal on, antifreeze as the weather gets colder.

The security risk with AI must be monitored, but we have found that the option of multiple levels of security within Evoke is more than sufficient. Similarly, our optimized use of the cloud also remains a constant.

Within the MultiValue sector, a growing number of companies are recognizing the need for modernization. However, the sector is seeing a dwindling resource pool of MultiValue talent, and many have seen changes in their personnel. This tends to bring with it an unavoidable shortfall in the awareness of their internal MultiValue environment/systems.

BlueFinity’s new enhanced support service, through which we can provide general help, guidance, and advice relating to a client’s own MultiValue systems, goes some way in addressing this for our customers, but it is still an issue. Most significantly, we have found that the introduction of modern Microsoft-based systems integrated with legacy MV systems also eases the burden on specific MV personnel for new development.

<< back Page 7 of 8 next >>