In a previous blog post, we explored how we can quickly develop the application structure for a Secret Santa app using Intrexx that would allow people to create an event, set a budget/location and add participants.
It’s almost the holiday season, and you probably know what that means: gifts, gifts, and more gifts! Of course, no winter holiday would be complete without the Secret Santa tradition. But now you’re facing a conundrum: should you create a group chat, start drawing names, and try your best not to leave anyone out? Or… should you use an online application instead? The latter certainly sounds much more convenient! But what if you could take it a step further and develop your very own Secret Santa application to use year after year?
When creating applications using Intrexx, you will likely need to store and read values specific to that particular user's session. The most important aspect of session values is that they can be accessed from any page of your Intrexx portal.
Advanced customization often requires developers to explore the Expert tab of elements in Intrexx, a low-code platform for building business applications. Two key components within this tab are Attributes and Settings, which offer crucial control over how elements behave and interact within the application.
There are many applicable real-life scenarios where the destination page must sometimes be different upon the click of a button. Imagine the same button being clicked to determine what the destination page should be on its own. How to do this Intrexx?
Intrexx is a robust platform designed for easily creating and managing web applications. A key feature of Intrexx is its intuitive user interface, which leverages icons to enhance user interaction and experience. The built-in icons in Intrexx cover a wide range of functions and actions, providing users with immediate visual recognition and understanding of various tasks and options within the application.
Have you ever encountered an issue in Intrexx where most of your backend logic relies on event listeners, such as record insertion, updating, or deleting?
It's a valid approach, but sometimes you may find yourself restricted to calling backend processes via Generic Actions triggered with an AJAX call. In such cases, you might wonder how to send data to those event listeners without duplicating all the functionality in a single Groovy Script Action.