KIÚ Software Integration’s Post

🚀 Elevate Your Oracle Apex Applications with Drag-and-Drop Functionality! 🌟 Are you ready to take your Oracle Apex applications to the next level? 💻💡 As a seasoned Apex developer, I specialize in crafting dynamic solutions that enhance user experience and streamline workflows. Imagine empowering your users to effortlessly rearrange rows within an interactive grid or transfer them between interactive grids with a simple drag-and-drop action. With just a few lines of code, you can make this vision a reality! Check out this snippet below: function updateDisplaySeq_1(pRegionID) {   var dataIds = [];   $(pRegionID).find("tr").each(function() {     var dataId = $(this).attr('data-id');     if (dataId) {       dataIds.push(dataId);     }   });   console.log(dataIds);   apex.server.process("UPDATE_ORDER", {     f01: dataIds   }, {     success: function(pData) {       apex.message.showPageSuccess("New order saved.");       apex.event.trigger('#todoRegion', 'apexrefresh');     }   }); } $('.sortable-table tbody').sortable({   connectWith: '.sortable-table tbody',   helper: function (e, ui) {     ui.children().each(function () {       $(this).width($(this).width());     });     return ui;   },   update: function(event,ui) { updateDisplaySeq_1('#todoRegion_ig_grid_vc table'); } }).disableSelection(); This code showcases the power of Oracle Apex development by seamlessly integrating drag-and-drop functionality into your applications. Say goodbye to clunky interfaces and hello to a sleek, modern user experience! As your dedicated Apex developer, I'm here to provide dynamic solutions to your problems and ensure your applications stand out from the crowd. Have questions or need assistance? Drop me a message at [email protected]! Let's collaborate to create exceptional experiences for your users! 🌐✨ #OracleApex #UXDesign #WebDevelopment #JavaScriptMagic #InteractiveUI #UserEngagement #TechInnovation

🚀 Oracle APEX Input Validation: Handling Alphabets and Alphanumeric Values 🚀 Validating user input is a key aspect of building reliable forms in Oracle APEX. Below are some JavaScript snippets that help you manage alphabetic and alphanumeric inputs effectively. Perfect for beginners looking to enhance their forms! 🧑💻 1️⃣ Allow Only Alphabets with Spaces: // Only alphabets allowed with space $('.only-alphabets').keydown(function (e) {   if (e.shiftKey || e.altKey) {     e.preventDefault();   } else {     var key = e.keyCode;     if (!((key == 8) || (key == 32) || (key == 46) || (key >= 35 && key <= 40) || (key >= 65 && key <= 90))) {       e.preventDefault();     }   } }); 💡 Use Case: Great for fields like names or titles where only alphabetic characters and spaces are permitted. 2️⃣ Allow Alphanumeric Values Without Spaces: // Numeric + alphabets value without spacebar $(".numerics_alphabets_wos").bind("keypress", function (b) {   var keyCode = b.which ? b.which : b.keyCode;   if (keyCode === 32 || (keyCode >= 33 && keyCode <= 47) || (keyCode >= 58 && keyCode <= 64) ||      (keyCode >= 91 && keyCode <= 96) || (keyCode >= 123 && keyCode <= 126)) {     return false;   } else {     return true;   } }); 💡 Use Case: Ideal for fields requiring a mix of numbers and letters without spaces, such as product codes or usernames. 🛠 How to Use: 1: Add these JavaScript snippets to your Oracle APEX pages Function and Global Variable Declaration where numeric validation is needed. 2: You Can also create a JavaScript file and Import it into Shared Component / Files and Reports / Static Application Files 3: Bind the desired class (.only-alphabets, .numerics_alphabets_wos, etc.) to your input fields Advanced/CSS Classes. #ORACLE #Apex #Javascript #Ajax #Validations #Developer #OracleApex #JS

🚀 Oracle APEX Tip for Beginners: Numeric Input Validation 🚀 When building forms in Oracle APEX, ensuring that users enter valid numeric values is crucial. Here are some handy JavaScript snippets to help you validate numeric inputs effectively! 🧑💻 1️⃣ Allow Only Numeric Values (0-9): // Just-numeric value allow (0-9) $(".only-numerics").bind("keypress", function (e) { var keyCode = e.which ? e.which : e.keyCode; if (!(keyCode >= 48 && keyCode <= 57)) { return false; } else { return true; } }); 💡 Use Case: Ideal for fields where only digits are allowed, such as phone numbers or IDs. 2️⃣ Allow Numeric Values with a Decimal Point (.): // Numeric value with (.) allow $(".numerics_wd").bind("keypress", function (e) { var keyCode = e.which ? e.which : e.keyCode; if (!(keyCode >= 46 && keyCode <= 57)) { return false; } else { return true; } }); 💡 Use Case: Perfect for fields that require decimal numbers like prices or measurements. 3️⃣ Allow Numeric Values with Decimal (.) and Negative Sign (-): // Numeric value with (.) and (-) allow (0-9 , " . , - ") $(".numerics_wdm").bind("keypress", function (e) { var keyCode = e.which ? e.which : e.keyCode; if (!(keyCode >= 45 && keyCode <= 57) || keyCode == 47) { return false; } else { return true; } }); 💡 Use Case: Useful for financial applications where negative values and decimals are required. 4️⃣ Allow Numeric Values with a Negative Prefix (-) Only at the Beginning: // Numeric value with Prefix (-) also allow (0-9) (.) (-) $(".minus-numerics").bind("keypress", function (e) { var keyCode = e.which ? e.which : e.keyCode; var inputValue = $(this).val(); if (keyCode == 45) { if (inputValue.indexOf('-') === -1 && inputValue.length === 0) { return true; } else { return false; } } if (!(keyCode >= 46 && keyCode <= 57) || keyCode == 47) { return false; } else { return true; } }); 💡 Use Case: Essential for fields that may start with a negative sign but should not allow multiple negative signs or incorrectly placed ones. 🛠️ How to Use: 1: Add these JavaScript snippets to your Oracle APEX pages Function and Global Variable Declaration where numeric validation is needed. 2: You Can also create a JavaScript file and Import it into Shared Component / Files and Reports / Static Application Files Bind the desired class (.only-numerics, .numerics_wd, etc.) to your input fields Advanced/CSS Classes. #OracleApex #ApexDeveloper #Javascript #Validation #Oracle #Clientsidevalidation #Apex #Oracle

Day 2: 🚀 How to Install MySQL on Your System! 🚀 💡 Uses of MySQL in Real-World Applications: Web-Based Applications: MySQL is widely used in web development to manage and store data for websites and web applications. It powers platforms like WordPress, Joomla, and Drupal, handling user information, posts, comments, and other dynamic content. Data Warehousing: MySQL is often used in data warehousing solutions where large volumes of data are stored and managed. It helps in aggregating and analyzing vast datasets to make data-driven business decisions. E-commerce Platforms: E-commerce websites, such as Shopify and Magento, use MySQL to store product information, inventory data, customer details, and transaction records, ensuring a smooth shopping experience. Social Media and Networking Sites: Social media platforms use MySQL for storing user profiles, messaging, posts, and interactions. It helps maintain the data consistency and integrity required to manage millions of concurrent users. Customer Relationship Management (CRM): MySQL is a popular choice for CRM systems, which require managing vast amounts of customer data, tracking interactions, and supporting complex queries for customer segmentation and marketing efforts. Content Management Systems (CMS): MySQL is the backbone of many content management systems, enabling the storage, retrieval, and manipulation of various types of content, including text, images, and multimedia. Enterprise Applications: Many organizations use MySQL for various enterprise applications like financial systems, HR management, and project management tools due to its reliability, scalability, and robust performance. Data Analytics: MySQL can be integrated with data analytics tools to analyze data, generate reports, and provide insights that help businesses optimize operations and understand customer behavior. Cloud Applications: MySQL is often used in cloud environments for its flexibility and compatibility with cloud-native architectures, making it a preferred choice for cloud-based applications and services. IoT Applications: With the rise of IoT devices, MySQL is used to manage and store data generated by these devices, ensuring real-time data processing and retrieval. #mysql #sql #database

🔄 Understanding the JSONParser Class in Apex for De-Serialization 🔄 In the world of Salesforce development, working with data from third-party web services is a common task. Often, these services return data in JSON format, and that's where the JSONParser class shines! This powerful tool helps us convert JSON strings into our own Apex objects, making it easier to work with the data we receive. 📚 What is JSONParser? The JSONParser class enables us to take a JSON string and break it down into smaller, manageable pieces, known as tokens. This allows us to effectively extract the information we need to use in our applications—whether that’s displaying it on Visualforce pages, saving it to our database, or sending it along to another web service. 🛠️ How to Create a JSONParser Object To get started with JSONParser, you simply create an instance like this: apex System.JSONParser jsonParser = System.JSON.CreateParser(<JSONString>); 🔍 Key Methods for Parsing JSON Here are some handy methods that the JSONParser class provides to help us navigate and retrieve data from JSON strings: 🔹NextToken(): Moves the cursor to the next token in the JSON string. 🔹GetCurrentToken(): Gets the value of the current token. 🔹GetText(): Retrieves the current token's value as a string. 🔹GetBooleanValue(): Extracts the boolean value if the current token is a boolean. 🔹GetDecimalValue(): Gets the decimal value if the current token represents a decimal number. 🔹GetDateTimeValue(): Collects the DateTime value if the current token is of type DateTime. 💡 Example in Action Here’s a quick example to illustrate how to parse a JSON response: String jsonResponse = '{"CustomerName": "Kiran Kumar", "IsActive": true, "AnnualRevenue": 2000000}'; System.JSONParser jsonParser = System.JSON.CreateParser(jsonResponse); while (jsonParser.NextToken() != null) { String currentToken = jsonParser.GetCurrentToken(); // Process the token as needed } Using the JSONParser class allows us to seamlessly integrate and manipulate external data within our Salesforce applications. It’s a game changer when it comes to API interactions! If you’re diving into API integrations, getting familiar with JSONParser will definitely enhance your development skills! #Salesforce #Apex #JSONParser #DeSerialization #APIIntegration

🌟𝐔𝐧𝐥𝐨𝐜𝐤 𝐒𝐞𝐚𝐦𝐥𝐞𝐬𝐬 𝐃𝐚𝐭𝐚 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐢𝐧 𝐃𝐫𝐮𝐩𝐚𝐥 𝟏𝟎 𝐰𝐢𝐭𝐡 𝐕𝐢𝐫𝐚𝐬𝐚𝐭 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬🌟⁣ ⁣Planning to upgrade or migrate your website to Drupal 10? Ensuring a smooth data migration is key to maintaining your site's integrity and functionality. Today, I'm thrilled to provide a quick overview and example of crafting a custom migration script in Drupal 10, which can streamline the process and cater to your specific needs.⁣ ⁣𝐖𝐡𝐲 𝐂𝐮𝐬𝐭𝐨𝐦 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧? 🤔⁣ While Drupal's Migrate API is robust, out-of-the-box solutions might not cover every use case, especially when dealing with complex data structures or legacy systems. Custom migration scripts give you the flexibility to handle unique data mapping and transformation needs.⁣ ⁣ 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: 𝐂𝐮𝐬𝐭𝐨𝐦 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐒𝐜𝐫𝐢𝐩𝐭⁣ Let’s walk through a simple example of migrating user data from a CSV file to Drupal 10.⁣ ⁣𝐒𝐭𝐞𝐩 𝟏: 𝐒𝐞𝐭𝐮𝐩 🛠️⁣ First, ensure you have the Migrate Plus and Migrate Tools modules installed and enabled.⁣ ⁣𝐒𝐭𝐞𝐩 𝟐: 𝐃𝐞𝐟𝐢𝐧𝐞 𝐭𝐡𝐞 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐂𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐚𝐭𝐢𝐨𝐧📄⁣ Create a YAML configuration file in your custom module’s config/install directory. This file will define the source of the data, the process of mapping and transforming it, and the destination in Drupal.⁣ ⁣𝐒𝐭𝐞𝐩 𝟑: 𝐈𝐦𝐩𝐥𝐞𝐦𝐞𝐧𝐭 𝐭𝐡𝐞 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧 🚀⁣ With the configuration file in place, you can now run the migration using Drush.⁣ ⁣𝐒𝐭𝐞𝐩 𝟒: 𝐑𝐨𝐥𝐥𝐛𝐚𝐜𝐤 𝐚𝐧𝐝 𝐔𝐩𝐝𝐚𝐭𝐞 🔄⁣ One of the powerful features of the Migrate API is the ability to rollback changes if something goes wrong. You can easily revert a migration to restore the previous state. Additionally, you can update existing migrations to handle new data or change mappings as needed.⁣ ⁣𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬 𝐨𝐟 𝐂𝐮𝐬𝐭𝐨𝐦 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐒𝐜𝐫𝐢𝐩𝐭𝐬🌟⁣ ✅ 𝐅𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲: Tailor the migration process to fit your exact requirements.⁣ ✅ 𝐒𝐜𝐚𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲: Handle large datasets efficiently.⁣ ✅ 𝐂𝐨𝐧𝐭𝐫𝐨𝐥: Manage complex data relationships and transformations.⁣ ✅ 𝐑𝐨𝐥𝐥𝐛𝐚𝐜𝐤 𝐚𝐧𝐝 𝐔𝐩𝐝𝐚𝐭𝐞: Easily revert changes and update migrations to adapt to evolving data needs.⁣ ⁣𝐅𝐢𝐧𝐚𝐥 𝐓𝐡𝐨𝐮𝐠𝐡𝐭𝐬💬⁣ Custom migration scripts empower you to take full control of your data migration process in Drupal 10, ensuring a seamless transition with minimal disruptions. Whether you're migrating content, users, or custom entities, leveraging the Migrate API with custom scripts can save you time and headaches.⁣ ⁣At 𝐕𝐢𝐫𝐚𝐬𝐚𝐭 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬, we're experts in Drupal development and deployment. Let us help you with your next migration project! Reach out if you have any questions or need assistance with your Drupal migrations. Let’s connect and share our experiences. 🤝⁣ #DrupalServices #Drupal #Drupal10 #DataMigration #CustomScripts #VirasatSolutions #DrupalPartner #WebsiteUpgrade #TechInnovation HR Virasat

== Software: Custom vs COTS vs OTS == OTS: Off The Shelf COTS: Custom Off The Shelf Should you pay "extra" to have software customized? Business processes are on a scale between simple standards and very complicated. Executives should decide where on the scale and what variations suffice. Reality is executives buy what vendors market and friends know, much more than research recommendeds One extreme is standard processes, or what marketing convinces is standard: Web browsers, text editing, word processing, calculators, spreadsheets, slideshows. Decisions should be comparing brands because difference exist. Everyone using "Word" knows pain of losing work. Text editors should be completely standard, yet "Notepad" has annoying Find and missing Replace (compared to older 1980s' programs.) - Free spreadsheets feel incomplete because Excel includes database functions. In 1990s, Microsoft discovered people do not understand databases so overload spreadsheets. At same time, two (of only three) human-usable database programs disappeared. Next are processes where software should be standard, with human intervention for exceptions. Tax software is complex and must update yearly for ever-changing laws. When standard software is insufficient, hire a tax accountant, not find a better brand. COTS alleges most processes are similar between companies, and configuration handles most differences. Only little bits require programmers to customize during "a few years but probably forever" project by "a large initial team expected to shrink but soon large division." Ask any similar-size SAP customer how long and much was the customization so far. "Custom" also varies. Extreme is creating everything from scratch. This should be goal, although borrowing parts can be good at first. Less extreme is using existing libraries/programs for basic parts. Database should be PostgreSQL, but executives may buy a proprietary product, or your software writers are not smart enough to learn SQL. HTML/CSS/JavaScript should handle all clients, but your Modern Software Engineers cannot program so insist on "frameworks". Modern Software Engineers believe all business software is standard despite executives' expectation of custom software for their company. Modern Software Engineers "know" every standard "custom" Web application requires: - Front-end Framework (or several), - Database (or several), probably "cloud" so you have monthly bill larger than annual expenses for Admin salaries, utilities, and hardware. - Kafka: sounds good despite them not knowing how to use basic message queue functions or how Kafka is special. - Middleware programming language(s). Even if they accept only one, they will add unnecessary platforms/libraries to handle easiest functions. Even before Modern Software Engineers, half my value was simplifying or canceling expensive projects. At Wyeth, my 3 questions changed a large-team 6+ months project into an afternoon by 1 Admin. 20240408

🚀 CRM System with MySQL - Project Overview 🚀 I'm excited to share a recent project where I developed a comprehensive Customer Relationship Management (CRM) system powered by MySQL! 💻 This project focuses on optimizing business workflows and driving growth by managing key aspects of customer interactions. 🔹 Key Features of the CRM System: Customers Management: Efficiently store and manage customer data, including contact details, purchase history, and personalized profiles. Sales Opportunities: Track and manage potential sales, from initial interest to final closure. Monitor the progress of each opportunity and its stage in the sales pipeline.   Leads Management: Capture and nurture new leads with automated follow-ups and data-driven insights to increase lead conversion rates. Support Tickets: Streamline customer support by managing service requests, assigning tickets to support agents, and tracking resolution progress. Campaigns Management: Create and manage targeted marketing campaigns, track their performance, and measure their impact on customer engagement and sales. 🔹 Technical Stack: Backend: PHP / Python for backend logic and integration Database: MySQL, using relational database structures for robust and scalable data management Frontend: HTML, CSS, JavaScript for interactive user interfaces Tools: XAMPP for local server setup, phpMyAdmin for database management 🔹 Challenges Overcome: Designing a complex relational database schema to link customers, sales opportunities, leads, and support tickets Implementing real-time data retrieval with optimized SQL queries for fast performance Building an intuitive interface for users to manage various CRM functions with ease Ensuring robust security measures for sensitive customer and sales data This project has helped me gain a deeper understanding of MySQL, database design, and business process automation. It’s been an amazing experience to create a solution that helps businesses streamline their operations and improve customer relationships. 📈 I’m excited to hear your thoughts or any feedback you have on this project!

🔩 Mastering the Dependency Inversion Principle (DIP) 🔩 The Dependency Inversion Principle (DIP) is pivotal in creating maintainable software systems. It advocates that high-level modules should not depend on low-level modules. Instead, both should depend on abstractions and not on implementations. Here's an example that follows the DIP and leverage dependency injection: ```csharp // Abstract service definition public interface ICustomerRepository { void Add(Customer customer); } // High-level business logic module public class CustomerService { private ICustomerRepository _customerRepository; public CustomerService(ICustomerRepository customerData) { _customerRepository = customerData; } public void RegisterCustomer(Customer customer) { _customerRepository.Add(customer); } } // Low-level data access module public class SqlCustomerRepository : ICustomerRepository { public void Add(Customer customer) { /* Code to add customer to a SQL database */ } } // Model public record class Customer { public int Id { get; init; } public required string Name { get; init; } } ``` The preceding code demonstrates that high-level modules, like `CustomerService`, should not directly depend on low-level modules, such as `SqlCustomerRepository`. Instead, both should depend on abstractions, like the `ICustomerRepository` interface. This design ensures that the `CustomerService` class remains independent of data access implementation details, like SQL Server, improving maintenance and flexibility by allowing changes in the data storage mechanisms without affecting the business logic layer. On top of that, depending on abstractions allows us to write unit tests that mock the dependencies. The provided unit test (image) depicts the benefits of the DIP by demonstrating how it enables the creation of modular and testable code. By depending only on the `ICustomerRepository` interface, we can use a mock object to test the `CustomerService` class in isolation. This allows our test to verify that `CustomerService` correctly calls the `Add` method without requiring an actual database. 💡 Takeaway: Embracing the Dependency Inversion Principle (DIP) positions high-level business logic to depend solely on abstractions rather than concrete implementations. This separation enhances modularity and allows for easier maintenance and scalability of software systems. By utilizing the DIP, developers can replace or update dependencies without significantly changing the core business logic, reducing the risk of bugs and facilitating future enhancements. This principle is crucial for building flexible, scalable software that adapts quickly to new business requirements or technologies. #ASPNETCore #SoftwareArchitecture #dotnet #csharp #DesignAndArchitecture #CodeDesign