Friday 16 February 2024

Mendix online training hyderabad - Mendix training institute in hyderabad

What is Mendix?

Mendix is a low-code application development platform. Let's break down what that means:

Contact: +919059868766


  • Application Development: Creating software like web apps, mobile apps, and internal business tools.

  • Low-Code: Instead of writing extensive lines of traditional code, you use visual models and drag-and-drop elements to build applications. This makes development much faster and easier.

Think of it like building with blocks:

  • Traditional coding: Similar to building a house by laying bricks one by one.

  • Mendix (low-code): Like building a house using prefabricated blocks or even whole rooms.

Mendix Online Training in India

Why use Mendix?

  • Speed: Create working applications incredibly quickly compared to traditional development.

  • Collaboration: Mendix makes it easy for business experts and developers to work together on the same project, which ensures applications truly meet the needs of the users.

  • Flexibility: Applications built on Mendix can easily be expanded, updated, and connected to other systems.

  • Cloud-Ready: Mendix allows for both cloud deployment and on-premises solutions, providing scaling and security that modern businesses need.

What can you build with Mendix?

Pretty much anything! Here are some examples:

  • Customer Portals: Where customers can track orders, submit requests, view information

  • Workflow Automation Apps: For streamlining business processes, such as onboarding or approvals

  • Mobile Apps for Field Workers: Helping workers collect data, access information, or perform tasks while on the go

  • Modernizing Legacy Systems: Replacing outdated software with newer, more flexible solutions

Mendix online training Course Content

Mendix – Introduction

1. What is Mendix?

  • Explain Mendix as a low-code application development platform

  • Emphasize visual modeling instead of extensive traditional coding.

  • Key benefits:

  • Speed of development

  • Enhanced collaboration

  • Agility and flexibility

  • Real-world use case examples (customer portals, workflow automation, etc.)

2. Understanding Traditional Web Applications

  • Basic components: Frontend (what the user sees), backend (database, logic), communication between them.

  • Development approach: Programming languages (HTML, CSS, JavaScript, backend languages like Java or Python), frameworks.

  • Challenges: Development time, technical expertise required, limited collaboration.

3. Getting Started with Mendix

  • Creating your Mendix Account: Explain using a corporate account (if applicable), single sign-on options.

  • Mendix Studio vs. Studio Pro: Briefly touch on the difference between the free, browser-based modeler and the more advanced desktop IDE.

4. Mendix Academy: Your Learning Hub

  • Explore available courses: Introduction, beginner paths, focused specializations

  • Structured learning paths: Tutorials and resources from Beginner to Expert

  • The value of certification: Explain Rapid Developer, Advanced, and Expert Certifications, and their benefits

5. Mendix Versions: LTS & MTS

  • LTS (Long-Term Support): Stable releases with extended support for business-critical applications.

  • MTS (Mainline Track Support): Newer feature releases, more frequent updates.

  • Balancing Stability vs. Innovation: Helping understand when to choose LTS or MTS.

6. Mendix Architecture at a Glance

  • High-level Overview: Don't get too technical, but introduce concepts like:

  • Domain model (defining your data)

  • Microflows (visual logic workflows)

  • Pages (building user interfaces)

  • Cloud deployment options

7. Application Lifecycle Management (ALM)

  • The core concept: Planning, development, testing, deployment, and maintenance of a Mendix application.

  • Stages in ALM: Define the typical phases from the idea to a live, updated application.

  • Mendix Support: Introduce how Mendix tools aid with version control, environments, etc.

Mendix Development Process

1. Setting up Your Development Tools

  • Mendix Studio Pro: Introduce the full-featured desktop IDE:

  • Download and Installation process

  • Core functions (domain modeling, page creation, advanced microflows)

  • Benefits (offline development, deeper customization, third-party extensions )

  • Mendix Studio: Explain the online, browser-based modeling environment:

  • Accessibility (no installation needed)

  • Well-suited for rapid prototyping and collaboration

  • Limitations compared to Studio Pro

  • Recommendation: Start with Studio for exploration, move to Studio Pro for larger projects and more experienced developers.

2. The Mendix Marketplace: Accelerating Development

  • What it is: A central repository of reusable components, modules, and widgets created by Mendix and the community.

  • How it helps: Reduces development time by providing:

  • Pre-built functionality (e.g., charting, calendar widgets)

  • Connectors to integrate third-party systems

  • Starting points for complex features

  • Best practices: Evaluating marketplace modules for quality, fit, and long-term support before integrating them into your project.

3. Project Creation in Mendix: A Step-by-Step Guide

  • Starting a New Project in Studio Pro:

  • Selecting a project template (blank, industry-specific, or from the marketplace)

  • Setting up initial project structure and naming conventions

  • Starting a New Project in Studio:

  • Similar process, highlighting any subtle differences that may exist online

  • Core Considerations:

  • Project Scope: What is the application intended to achieve?

  • Team Collaboration: Planning how multiple developers will work together (version control).

Mendix Version Control: Collaboration and Project Management

1. Introduction to Team Server

  • Mendix's Built-in Version Control: Centralized repository for your application's code and history.

  • Two Technologies: SVN and Git:

  • SVN: An older, but still supported option within Mendix

  • Git: The industry standard, strongly favored for most Mendix development

  • Key Purpose: Enabling multiple developers to work concurrently, track changes, and manage multiple versions of your application.

2. Inviting Team Members

  • Adding Collaborators: Grant access to your Mendix project with defined roles (viewer, developer, etc.)

  • Managing Permissions: Ensure appropriate levels of access control for code security and workflow efficiency.

3. Branching for Controlled Development

  • The Concept of Branches: Creating separate "copies" of the project code for isolated development of new features or bug fixes.

  • Mainline vs. Feature Branches: Distinguish the stable central codebase (mainline) from temporary workspaces (feature branches).

  • Merging Changes: The process of bringing changes from a feature branch back into the mainline with a streamlined review process.

4. Interacting with the Repository

  • Checking Out Code: Downloading a local copy of the current project version for development.

  • Committing Changes: Uploading your local code modifications to the Team Server, providing clear descriptions of the changes made.

  • Viewing Change History: Tracking the project's evolution, with the ability to compare versions and see who made modifications.

5. Upgrading Your Project

  • LTS & MTS Tracks: Understanding the implications of upgrading within a current Mendix version track (e.g., within Mendix 9.x)

  • Compatibility: Checking release notes and documentation to address any breaking changes that might require code updates.

  • Upgrade Process: Performing the upgrade within Mendix Studio or Studio Pro, managing conflicts if necessary.

Building Pages in Mendix

Understanding the foundation: Layouts

  • What are layouts? Templates that define the overall structure of your pages (header, footer, sidebars, content areas).

  • Types of layouts: Mendix offers several built-in layouts (sidebar, navigation, popup, etc.). You can also create custom layouts.

  • Choosing the right layout: Consider the type of page (dashboard, form, detail view) and how your users will interact with it.

Creating Your First Page

  1. New Page: In Mendix Studio or Studio Pro, find the option to create a new page.

  2. Select Layout: Choose a layout that matches your intended page structure.

  3. Name your page: Provide a descriptive name for easy reference.

Populating Your Page: Widgets and Content

  • The Widget Toolbox: Mendix offers a range of widgets for building visual interfaces (text boxes, buttons, images, data containers, etc.).

  • Drag and Drop: Place widgets onto your layout in designated content areas.

  • Columns: Divide your layout into columns for better organization of content.

  • Buttons and Actions: Configure buttons to trigger microflows (logic), open pages, or perform other actions.

Role-Based Home Pages

  • User Roles in Mendix: Explain how Mendix defines user roles to control access and tailor the experience.

  • Creating role-specific home pages: Demonstrate how to duplicate pages and tailor content and access based on the user role.

Navigation Profile

  • Purpose of Navigation: Allow users to seamlessly move between pages in your application.

  • Adding Menus: Use Menu widgets to create navigational elements (top menus, sidebars).

  • Linking Pages: Configure menu items to link to specific pages.

Security Considerations: Tie navigation items to user roles to ensure only authorized users can access certain pages.
Vlr Training

The Domain Model: Your Application's Blueprint

  • What it is: The Domain Model is the core data structure of your Mendix application. It defines the objects your app works with, their properties, and their relationships. Think of it as a map of your business information.

1. Building Blocks: Entities

  • An Entity is a "Thing": A customer, an order, a product – they're all examples of entities.

  • Creating Entities: You give them meaningful names in Mendix Studio/Studio Pro (e.g., "Customer," "Order").

2. Defining Attributes: Giving Entities Characteristics

  • Attributes are Properties: An entity "Customer" might have attributes like name, email address, and order history.

  • Attribute Types:

  • String: Text values (names, addresses)

  • Integer: Whole numbers (quantity, age)

  • Decimal: Numbers with decimals (prices, measurements)

  • Date/DateTime: Dates and Timestamps

  • Enum (Enumeration): Predefined list of options (e.g., order status: "New", "Shipped", "Cancelled")

  • Boolean: True/False values (e.g., "Is Active")

3. Inheritance: Creating Categories

  • Like a Family Tree: Entities can inherit properties from a parent entity.

  • Example: You could have a generic "Vehicle" entity, then "Car" and "Truck" as specializations inheriting the basics from "Vehicle".

  • Why it's useful: Avoids repetitive data definition and keeps your model organized.

4. Associations: Connecting the Dots

  • How Things Relate: Associations define how entities interact.

  • Example: A "Customer" has a one-to-many association with "Orders" (One customer, many potential orders).

  • Types: One-to-one, one-to-many, many-to-many.

5. Bringing it to Life: Overview Pages

  • The User Interface: Overview pages provide lists of your entities' instances.

  • Quick Actions: Add, edit, delete buttons are common features.

  • Data Views: Choose how to display your data (data grids, list views)

6. Making Selections: Dropdowns & References

  • Dropdowns (Enumerations): Let users choose from a list you defined (order status)

  • Reference Selectors: Select an existing object/entity instance (assign a customer to an order)

  • Reference Set Selectors: To choose multiple related objects (pick products for an order)

7. Stored vs. Calculated Attributes

  • Stored: Data is saved directly in your database.

  • Calculated: Value is determined dynamically using a formula (e.g., Total Order Price).

Configuring Application Security in Mendix

Understanding Mendix Security Levels

  • Off: No security applied. Suitable for early prototypes, but never for data-sensitive apps.

  • Prototype / Demo: Basic login, limited access controls. For demonstration purposes only.

  • Production: Full security required for live apps. Enforces fine-grained access controls.

Key Steps for Establishing Application Security

  1. Switch on Security:

  • In your Mendix app, under 'App' > 'Security', switch from 'Off' to 'Prototype / Demo' (for initial setup) or 'Production' (for deployment).

  1. Create User Roles:

  • Define distinct roles based on job functions (e.g., Administrator, Sales Rep, Customer).

  • Assign meaningful names to roles for easier management.

  1. Define Module Roles:

  • Each module in your app can have its own set of roles.

  • Map User Roles to appropriate Module Roles to control access within modules.

  1. Control Page Access:

  • Assign Module Roles to each page allowing only those with the right role to view the page.

  • Manage the visibility of buttons, navigation options, etc., based on the user's roles.

  1. Manage Microflow Access:

  • For each microflow, specify which Module Roles have permission to execute it.

  • Protect sensitive logic and data manipulations.

  1. Configure Entity Access:

  • Fine-tune permissions for each data entity (create, read, update, delete).

  • Restrict access based on Module Roles, ensuring users only modify data they are authorized to see.

Data Validation & Consistency in Mendix

1. Why Data Integrity Matters

  • Prevent Errors: Stop bad data from entering your system, leading to incorrect calculations, poor decisions, and frustrated users.

  • User Trust: Applications with reliable data instill confidence in users.

  • Maintainability: Clean data is easier to manage, improving your app's long-term health.

  • Business Insights: Only accurate data can give you reliable insights for decision-making.

2. Validation Rules: Your Data Gatekeepers

  • What are Validation Rules: Enforce constraints on data entered or changed by users.

  • Rule Types: Highlight examples and use cases for common rule types:

  • Required Fields: Prevent submission with missing key information.

  • Range Checks: Ensure numbers or dates fall within acceptable limits.

  • Format Validation: Match email addresses, phone numbers, etc.

  • Regular Expressions: For complex validation patterns.

  • Uniqueness: Enforce that values are not duplicated.

  • Custom Microflows: For even more specific logic when needed.

3. Apply Validation Rules

  • Domain Model Level: Rules that apply across the whole application.

  • Page Level: Validation specific to forms or data inputs on a page.

  • Microflows: Add validation checks inside logic for granular control.

4. Delete Behavior: Maintaining Data Relationships

  • Understanding Associations: Explain one-to-many, many-to-many relationships between entities.

  • Delete Behavior Options:

  • Delete: Allow deleting an object and its associated objects.

  • Do Nothing: Prevent deletion if associated objects exist.

  • Change Owner: Re-assign associated objects before deletion (example: reassigning tasks when deleting a user).

  • Impact on Referential Integrity: Ensuring related data stays consistent.

5. Best Practices

  • Provide Clear Error Messages: Guide users to make correct data entries.

  • Balance Strictness with Usability: Find the right level of validation to prevent errors without frustrating users.

  • Validate Early and Often: Check data as users enter it, and before major actions are committed.

  • Use Validation Assist: Explore this Marketplace module for streamlined validation management.

Custom Logic Generation in Mendix

1. Why We Need Microflows and Nanoflows

  • The Heart of Your App: Microflows and nanoflows define how your Mendix application behaves, bringing your data and pages to life.

  • Beyond UI: Handle actions that users trigger, process data, make decisions, and interact with other systems.

  • Visual Programming: Mendix simplifies complex logic using a visual, drag-and-drop interface instead of traditional code.

2. Microflows vs. Nanoflows: Choosing the Right Tool




Runs On


Client (User's device/browser)

Best Suited For

Complex Logic, Database interactions, Integrations

User interactions, Offline access, Speed


Requires internet connection

Can work in offline scenarios

3. Building Blocks: Microflow/Nanoflow Activities

  • Basic Actions: Create/Change objects, retrieve data, show messages

  • Decision Points: Make your app react based on conditions (If/Then logic)

  • Loops: Repeat actions on multiple pieces of data

  • Call Other Microflows: Build reusable logic units

  • Integration Activities: Connect to external systems (web services, etc.)

4. Configuring Your Logic

  • The Mendix Modeler: Drag and drop activities, link them in sequence

  • Properties: Adjust activity settings, such as what data to retrieve, or conditions to evaluate

  • Variables: Store temporary data throughout your flow

Mendix Query Languages: Mastering Data Retrieval with XPath and OQL

1. Introduction

  • Importance of Data Queries: Emphasize the role of effective queries in extracting, filtering, and manipulating data within your Mendix applications.

  • Mendix Query Options: Introduce XPath and OQL, explaining their different strengths and use cases.

2. Mendix XPath: Navigating Data

  • XPath Basics: Start with simple XPath expressions (e.g., //Sales/Customer/Name to select customer names)

  • Syntax and Operators: Introduce selection nodes, axes, comparison operators, and functions.

  • Use in Mendix Studio: Demonstrate how to use XPath in Microflows (retrieve activities), page data sources, and calculated attributes.

  • Practical Examples: Focus on real-world scenarios like filtering customers by location, calculating order totals, etc.

3. OQL: Power of SQL-Like Queries

  • OQL vs. SQL: Highlight similarities with SQL, and point out differences (using entity names instead of table names).

  • Key OQL Elements: Explain SELECT, FROM, WHERE, ORDER BY, GROUP BY using Mendix domain model terms.

  • Use in Mendix: Describe how to execute OQL queries in Microflows to populate datagrids, perform aggregations (counts, sums), and create complex reports.

  • When to Use OQL: Provide scenarios where OQL excels, like data reporting with aggregations and groupings.

4. Choosing the Right Tool

  • XPath Strengths:

  • Simple data retrieval by hierarchical location

  • Easy integration in specific UI elements or within microflows

  • OQL Strengths:

  • Powerful querying similar to SQL for advanced filtering and reporting

  • Greater flexibility for aggregations, and more complex data transformations

5. Advanced Concepts (Optional)

  • Mendix OQL Functions: Date, string, math-related functions

  • XPath within OQL: Using XPath expressions inside an OQL query

  • Optimization: Discussing performance factors when choosing between XPath and OQL

Mendix Required Modules: Understanding Their Functions


While Mendix provides a core foundation for building applications, many widely used features are packaged into modules offered in the Mendix App Store. Let's explore some of the most common ones:

1. Community Commons

  • Purpose: Provides a collection of reusable building blocks, widgets, and logic to speed up development and reduce repetitive work.

  • Key Features:

  • Functional building blocks (e.g., various button types, date pickers)

  • Java actions for common tasks

  • Page and layout templates

2. Nanoflow Commons

  • Purpose: Extends standard microflows (Mendix's visual logic), with actions specifically designed for executing logic on the client-side (user's browser).

  • Benefits: Improved speed and responsiveness in apps, reduces server load.

  • Examples: Instant calculations, local form validations

3. Email with Templates

  • Purpose: Simplifies sending emails from your Mendix applications.

  • Features:

  • Easily design email templates using placeholders and variables.

  • Send emails directly from Microflows.

  • Support for attachments.

4. Excel Importer/Exporter

  • Purpose: Manages the import and export of data to and from Excel spreadsheets (.xlsx files)

  • Key Uses:

  • Bulk data uploads into an application

  • Creating user-friendly reports in Excel format

  • Initial data seeding after an app is deployed

5. Deep Link

  • Purpose: Enables opening specific areas or functions of your Mendix app from external links.

  • Benefits:

  • Seamless integration with emails, other apps, or web pages.

  • Contextual app launching to guide user actions.

6. Mx Model Reflection

  • Purpose: Allows you to dynamically interact with your app's domain model (data structures) within microflows at runtime.

  • Advanced Use Cases:

  • Creating generic and flexible logic

  • Building admin interfaces to inspect and manage in-app data

7. Encryption

  • Purpose: Protects sensitive data within your application.

  • Features: Encrypting and decrypting stored data.

  • Essential For: Applications that handle private user information, financial data, etc.

8. Data Widgets (Various)

  • Purpose: Pre-built UI widgets for easily displaying and interacting with data in your apps.

  • Examples: Advanced chart widgets, interactive maps, custom form elements, etc.

9. Mendix SSO / SAML 2.0

  • Purpose: Integrating Single Sign-On capabilities, allowing users to log in with existing corporate credentials.

  • Benefits:

  • Enhanced security

  • Seamless user experience

10. Workflow Commons

  • Purpose: Offers advanced business process modeling features and execution within Mendix.

  • Key Features:

  • Visual workflow design interface

  • Human tasks and approvals

  • State machines

Mendix Advanced Concepts

Module 1: Mastering Data Manipulation

  • Advanced XPath

  • Complex queries, nested paths, functions for calculations and transformation

  • Optimization for performance-critical scenarios

  • DataGrid 2: Deep Dive

  • Latest features (grouping, templates, advanced customization)

  • Real-world use cases: Dynamic reporting, master-detail views, interactive dashboards

  • Excel Import/Export

  • Handling complex data structures

  • Data validation, error handling, and user feedback

  • Use cases: Bulk data upload/download, synchronization scenarios

Module 2: Workflow Orchestration

  • Beyond Basic Microflows

  • Advanced activities (loops, exclusive splits, sub-microflows)

  • Complex state management

  • Asynchronous and background processes

  • Use Cases

  • Multi-step approval processes

  • Task scheduling and orchestration

  • Long-running transactions across systems

Module 3: Integrations & Communication

  • REST/SOAP Web Services

  • Consuming and exposing complex web services

  • Handling authentication and data security

  • Data transformation and mapping (XSLT or Java Actions)

  • Email Integration with Templates

  • Creating dynamic, personalized email templates

  • Triggering emails from microflows

  • Use cases: Automated notifications, reports, status updates

Module 4: Extending with Java Actions

  • When to Use Java Actions (Scenarios where built-in features don't suffice)

  • Development Setup and Integration (IDE configuration, debugging)

  • Working with External Libraries

  • Use Cases

  • Complex algorithms not achievable natively in Mendix

  • Building custom connectors for unsupported systems

Module 5: Robustness & Maintainability

  • Error Handling Strategies

  • Structured error handling (try-catch, error microflows)

  • Centralized logging and error reporting

  • Providing meaningful user feedback

  • Mendix Log Management

  • Understanding log nodes, log levels

  • Monitoring, filtering, and alerts

  • Troubleshooting techniques

Module 6: Platform Management

  • Mendix Upgrades

  • Semantic versioning, upgrade paths

  • Preparation, impact analysis, testing

  • Mendix Marketplace

  • Evaluating pre-built modules and connectors

  • Considerations for module usage (licensing, dependencies)

  • Publishing your components (if applicable)

Module 7: User Experience & Layouts

  • Atlas UI Framework

  • Responsive design principles

  • Creating adaptive layouts for different screen sizes

  • Menus and Navigation

  • Dropdown menus, navigation lists, breadcrumbs

  • UX best practices and accessibility

Going Mobile with Mendix: Offline Capabilities and Mobile-First Design

1. Why Offline Matters in Mobile Apps

  • Unreliable Networks: Users shouldn't be blocked by a poor connection. Explain how offline features increase app usability.

  • Field Service Use Cases: Think about workers needing access to data or the ability to perform tasks in areas with no connectivity.

  • Performance Benefits: Certain data can be loaded and synced during off-peak times, enhancing overall app speed.

2. Creating an Offline Navigation Profile

  • Step 1: New Navigation Profile: Walk through the process of creating a dedicated navigation profile within Mendix Studio Pro.

  • Step 2: Offline Home Page: Design a home page specific to the offline experience (what should the user see first with limited data)

  • Step 3: Configure Pages for Offline: Within the profile, choose pages that MUST be accessible offline and ensure proper data availability.

  • Step 4: Synchronization Rules: Set up how and when data is synced when the device regains connectivity.

3. Configure Mobile-Specific Pages

  • Separate Layouts: Explain using layouts with 'Phone' or 'Tablet' specializations to optimize for screen sizes.

  • Responsive Design with Atlas UI: Utilize Atlas UI's framework to make elements adapt fluidly to mobile displays.

  • Touch-friendly Components: Make sure buttons, links, and form fields are easily interactive on touchscreens.

  • Leverage Device Features: Consider how you can use the camera, GPS, or other hardware functions (only possible within native mobile apps built with Mendix)

4. Building Native Mobile Apps with Mendix

  • Brief Overview: Mention that Mendix allows for both hybrid web mobile apps and fully native mobile apps if needed.

  • Advantages of Native: Potentially better performance, deeper integration with device features.

  • React Native: Highlight that Mendix builds native apps using React Native technology, opening up customization options.

5. Testing Your Offline & Mobile Experience

  • Mendix Simulators: Use testing tools within Mendix to preview the offline experience.

  • Device Testing: Emphasize the importance of testing on actual physical phones and tablets for accurate assessment.

  • Offline Scenarios: Simulate losing connectivity and check if the app transitions gracefully and data syncing works as expected.

No comments:

Post a Comment

Note: only a member of this blog may post a comment.