Read there interesting blog articles
- 4 Topics
- 3 Replies
Does using the USoft platform cause vendor lock-in?Vendor lock-in
Does using the USoft platform cause vendor lock-in? Customers sometimes ask USoft whether they become completely dependent on us and our software if they go into business with USoft. In short, whether a so-called vendor lock-in occurs when using the USoft low-code platform? Fortunately, this is not the case. This short article explains why not. What is a vendor lock-in? To begin, it is important to provide a good description of vendor lock-in. A vendor lock-in means that customers are and remain dependent on a vendor to a greater or lesser extent. For example, customers cannot easily migrate from one product to another. In addition, changing or adding functionality may no longer be possible or may be limited. This is something you will always need the vendor to address. With any technology, there is always a certain degree of vendor lock-in. Even open-source software is subject to some degree of lock-in. There are often no license fees and sometimes there is not even a vendor, but th
We need to interface sales orders, inventory, purchase orders from a USOFT application to an Oracle Database.It looks like we can do this development using the USOft query model? Please ignore above. Our issue is importing the planned oorders from Oracle ASCP.
Business rules based on human logic Automate the 'rules' instead of the processes The use of a Rules Engine The advantages of a rules engine in brief When to use a rules engine? The core of the USoft low-code platform is the rules engine. This ensures optimal data consistency and thus safeguards the quality of all data entering the system and possibly being redistributed to other systems. The rules engine also simplifies system programming and enables us to work in low-code. But what exactly is a rules engine? How exactly does it guarantee quality and when is it wise to use a rules engine? In this article I will explain it.To explain the rules engine it is good to start with an analogy. Rules engines start from well-defined definitions:There are persons. Pieter is a person. Abby is a person. A person can love another person. If a person loves another person, they should send him or her flowers. Abby loves Pieter.It is a simplistic model, but in this we can recognize: the data model, d
Business process and rules: tomayto, tomhato or more?business rules
Asking this question is in a way answering it. After all, if they were completely interchangeable, we wouldn’t need to elaborate. Aligning business rules and processes is crucial in successfully incorporating big data and AI. Business processes versus business rulesWhile rules generally focus on ‘what’, processes are commonly oriented towards ‘how’. Business rules describe for example what needs to be done, what criteria must be applied and what policies must be enforced. Business rules therefore focus on the value that needs to be created in/through a process. Processes on the other hand describe in what order (how) activities should be executed to create the desired value or outcome. It is therefore not a matter of either one or the other; they work in unity. The trouble with business rules however is that they are often not clearly and explicitly defined and are ‘scattered across the organization’. Even employees involved in defining and modeling processes often have a hard time ma
Sign up for the USoft Community
Already have an account? Login
Login into the USoft Community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.