Real-life Project Example

Let's dive into Fenorri to walk you through creating a simple project using no-code methods. Imagine this: we're embarking on a journey to streamline a business process within an organization through digitalization. Think of it as upgrading from manual tasks or Excel operations to modern, efficient systems.

⭐️ Here's the game plan: our goal is to facilitate the input of new customer orders for fresh clients, generate sleek PDF invoices, dispatch them to customers, give Alice a heads-up about new orders, and make sure John knows about the latest invoices.

🔧 First things first, we need to nail down the essential data we'll be working with. That means setting up four data input forms: one for product details, another for customer information, one more for order specifics, and finally, a form for invoice particulars. Be meticulous about managing product details as master data, as they are entered only once but are employed in several customer orders.

⭐️ In our product form, we'll cover fields such as product ID (automatically generated), name, description, and price. Once the product form is set up, we'll fill it with a range of product details to ensure they're ready for action when we fire up the app.

🚀 In our customer form, we're going to include fields for the customer's first and last names, address, email, and phone number.

💥 Likewise, in the order form, we'll want to have fields for the order ID (automatically generated), date, customer ID, product ID, quantity, and price.

🌟 To ensure the Product field displays values from the Master Data Form, we simply added a Select element and linked it to the right data source.

⭐️ Finally, in the invoice form, we'll include fields for the invoice number (automatically generated), customer ID, product ID, quantity, date, total VAT (or sales tax), and total price.

To create PDF invoices, we'll design a template in Word and insert data tags within curly braces {}. After uploading this template to the Fenorri no-code editor, linking these data tags to elements within the business app will fill in the document automatically when it's executed.

Feel free to include as many data tags as required within a single document. It's recommended to use unique keywords for each tag to keep things organized. These data tags can be customized and placed within tables for better presentation. Moreover, you have the flexibility to dynamically incorporate a user's signature, create barcodes or QR codes, and even generate text using AI before inserting it into a data tag.

Now, let's jump right in and begin constructing our business app using the no-code development platform editor. But before we get started, it's important to establish a well-structured plan to execute the process systematically. This involves outlining the sequential steps and logical flow of actions required to achieve our objectives. Planning ahead allows us to maintain clarity and efficiency in our approach, ultimately leading to a more effective implementation.
Here's a proposed sequence for the business logic:

START
CREATE a new customer order	Collect customer details and generate a unique customer number.
CREATE a new order	Associate the customer number with product details, including quantity and sale price.
READ the product data	Retrieve product information to calculate the product price.
CALCULATE the total order price	Sum up the prices of all products in the order.
CALCULATE VAT	Calculate the value-added tax (VAT) based on the total order price.
CALCULATE the total invoice price	Add VAT to the total order price.
UPDATE the total order price	Reflect the calculated total order price on the order form.
CREATE a new invoice	Compile customer and product details, including quantity, sale price, VAT, and total price, then generate a unique invoice number.
GENERATE a new invoice in PDF format.	Use the no-code app to populate dynamic data into the Word template and then save it as a PDF.
SEND an email	Express gratitude to the customer for their order and attach the PDF invoice.
NOTIFY Alice	Inform Alice of the newly received customer order.
NOTIFY John	Notify John about the newly generated invoice.
END

⭐️ Think of each action as a building block within the Fenorri no-code editor. These blocks are like pieces of a puzzle that fit together to form a comprehensive diagram, illustrating the workflow.

🔧 In Fenorri, these blocks are highly interactive and can be seamlessly connected to form a cohesive flowchart. Each block represents a specific action or task outlined in our business logic plan.

🚀 Now, let's dive into the no-code editor and arrange these blocks within a diagram. We'll customize each block to match the desired action, ensuring they align perfectly with our business logic.

💥 When it comes to form blocks, selecting the right form is key. And if we need to populate form fields with data from other blocks, it's just a matter of linking those fields together. It's as straightforward as connecting the dots!

Now, it's time to set up the Order block, which operates just like any other form within Fenorri's intuitive interface. We'll effortlessly link the customer ID from the previous block to the corresponding field in this one, ensuring seamless data flow.

🌟 For now, we'll keep the price field hidden; we'll calculate and unveil it in the next step of our process. This step-by-step approach ensures that we're building our workflow logically and efficiently.

🔧 Now, let's fetch the price of the selected product. It's quite straightforward since when a user chooses a product, its price is already stored in the dataset associated with that particular product. Therefore, once we identify which product the user selected, setting up the Data Access step to retrieve the relevant dataset is a breeze.

⭐️ Selecting the right product is a breeze with a simple filter application. Just click on the field, and then configure the filter to match your preferences. In this case, we're simply opting to choose the Product ID that aligns with the Product ID from the Order block.

🚀 With both the quantity and product data in hand (including the price info), we're set to introduce a Calculate block, named 'Calculate Price'. This block will perform a straightforward task: multiplying the quantity by the price to furnish us with the total.

🔧 Now, onto configuring the next Calculate block, which we'll dub 'VAT'. Initially, we'll set it at a fixed rate of 25%. However, in practical situations, this value would usually originate from elsewhere. Ideally, you'd manage your VAT rate centrally through a VAT master data form, ensuring it's automatically applied across all your applications.

🚀 Moving forward, we need one last Calculate block to determine the total for this order. This step is quite straightforward: we'll simply sum up the result from the first Calculate block with the result from the second Calculate block.

💥 Now, let's handle the update for the order total, a step we couldn't calculate during order creation. We'll use a Data Access block for this, labelling it 'Update Order'. Setting it to 'Write' mode, we'll draw data from the previous block as the source. Then, with a simple click on the 'Price' field, we'll select the value from the 'Total' block.

🌟 Now, let's proceed to generate an invoice. Unlike a form block, this one functions as a data access block. Its role is to generate a new record, requiring us to input the details manually. First, we need to ensure the data access block is set to 'Write' mode and that we've selected the correct data source – in this instance, it's the 'Invoice' data source.

🚀 In this block, all the fields are concealed, and we must connect each field to a value from the preceding blocks. For example, the Order ID field should be linked to the Order block's Order ID field (along with Quantity, Product ID, and Date). The Customer ID field should be connected to the Customer block's Customer ID field. VAT and Total Price must be linked to their corresponding Calculate blocks. There's no requirement to pre-set the Invoice ID because it will be generated automatically.

🔧 Now that we've gathered all the necessary data, it's time to craft a PDF invoice. We'll do this using the Document block. Here, we'll upload our Word invoice template, saved with a .docx extension, which includes all our data tags. It's essential to adhere to best practices by ensuring that your data tag names are distinct to prevent any potential confusion.

💥 Remember that if a data tag field is empty or missing data during runtime, the system will automatically eliminate the data tag, causing the space to be left blank.

In the last step, we'll go through each data tag, connecting it to the corresponding data from the preceding blocks, and ensuring that the formatting is accurate (like using Euros for currency formatting in this instance).

⭐️ To initiate email sending, we'll need to establish a connection with an email provider like Gmail, Microsoft Graph, or IMAP. Once connected, we can customize the message content, data tags, recipient addresses, and subject lines. Simply set the 'To' field to reference the 'email' field in the 'Customer' block. For a personalized touch, we can include the customer's First Name field. If we prefer the user to review the email before sending, we can opt for 'Show email and allow editing it during execution'. Otherwise, the email will be dispatched automatically.

🌟 Now, let's configure two Notification blocks – one for Alice and one for John. For Alice, we want to ensure she receives notifications on both the web and mobile interfaces.

💥 It's pretty simple: we just write the message we want to show up in the notification and choose the user who should receive it.

🔧 Lastly, we'll configure access permissions for the business app, granting specific users, departments, groups, or projects the required access.

🚀 Once the app is published, we can run it and observe how the screens flow. While running the app, a new invoice will be created and sent to the customer, with Alice and John receiving their notifications.

🌟️ After launching our first no-code app, it's crucial to test its real-world performance by engaging users and gathering feedback. This helps us understand how well the app meets user needs and improves daily tasks. User feedback is essential for identifying areas to simplify, refine the interface, and address any issues that emerge during testing, ensuring we enhance the app effectively.

Real-life Project Example

Exploring Fenorri's No-Code Development Platform Marvels and Magic!