Some improvements have been made in 4D 20 R4 to make your selections of records stable and consistent regarding potential deletion of records in this selection.
Keep reading to learn how your 4D code will be so safe out of the box.
As promised, we keep providing demos. Here is the latest PIQS (short for Play In Qodly Studio)
In those previous blog posts, we announced the availability of Qodly Studio (currently in developer preview) to all our silver partners (and higher). We also gave you the first steps to get started with the tool.
Now it’s the perfect time to dive in and experiment with it by running some concrete demos!
We’ve been offering HDIs (How Do I?) guides for years to help you discover new features. But now, as we venture into this new era of web development, we’ve come up with a new term for these demos: PIQS, short for Play In Qodly Studio.
Even better, we’ll continue providing such demos for current and upcoming Qodly features. This means you’ll have daily guidance on mastering Qodly Studio!
So, let’s roll up our sleeves and start exploring right away!
Throwing errors in your 4D code is now possible starting from v20R2.
Those errors behave as any 4D error: they trigger an error dialog or can be handled in an ON ERR CALL method.
This feature will ease your life because you’ll be able to improve the quality of your code by proactively detecting errors as soon as they occur. You can also handle better error logging.
Before digging into details, It’s important to note that this feature is the first step towards achieving robust error management.
Now, let’s dig into the details!
ORDA, which stands for Object Relational Data Access, is a method of accessing data that combines the advantages of object-oriented programming with those of relational databases, allowing developers to focus on solving business problems rather than managing data access.
Whether you are new to ORDA or already familiar with it and want to expand your knowledge, consider this blog post a road map to guide you through the learning process.
This blog post includes the following:
- ORDA benefits
- ORDA overview
- Main concept
- ORDA APIs
- ORDA abstraction layer
- Working remotely
- Requests optimization
- Permissions system
- Sharing data between process
Without further ado, let’s get down to business!
Filter access to data is a must-have feature to prevent malicious access to your application.
So far, you could expose or not expose as a REST resource a dataclass and some of its attributes. It was already a convenient means to restrict access to your data. Still, we’re thrilled to deliver in the v19R8 a powerful and fully customizable system to protect your data from unauthorized users. A system to protect your data depends on who is accessing it and which data is accessed.
ORDA/REST performance is a strategic matter; that’s why we shipped many features related to this topic, such as the ORDA/REST request optimization in Client/Server and when working with a remote datastore. Lately, we also gave you complete control over the ORDA/REST request optimization.
This blog post gives you the plan to follow in order to ace your ORDA/REST performance game. It includes other blog posts to read, videos to watch, and a demo to play with to increase performance in your applications quickly and easily.
With a previous version, you discovered how ORDA REST requests had been automatically optimized to increase performance when working with a remote datastore and client/server configurations.
You learned that you can use contexts to take advantage of the automatic ORDA REST requests optimization.
That was a significant step, but now we offer to have complete control over the behavior of your REST requests. Since performance is a strategic concern, you must be eager to discover this new feature!
And that’s not all; new tools are now available to help you understand and debug your issues.
Keep reading for a complete presentation.
Since ORDA allows you to work with several entity selections simultaneously, we’re sure you take advantage of this by passing entity selections as a parameter to project methods or to functions of ORDA Data model classes.
To work efficiently with object-oriented programming using as few lines of code as possible, you need robust and optimized functions. That’s why with 4D v19 R3, we are shipping a new function available on the entitySelection object: the selected() function.
Thanks to it, you’ll be able to inspect and compare two entity selections. Let’s see the details!
Cookies’ abilities have grown and evolved over the years, but they have left some legacy issues. To handle this, browsers (including Safari, Chrome, Firefox, and Edge) are changing their behavior regarding the SameSite and Secure attributes for a secure-by-default model for cookies.
To prevent your web session cookie from circulating on the web pointlessly or being misunderstood by browsers because of a default value applied, you should ask if it is:
- a third-party cookie: associated with a domain name different from that of the page where the cookie is encountered. A third-party cookie is placed by a page object (e.g. an ad) originating from a domain other than the one hosting the page
- a first-party cookie: associated with the domain of the page
Depending on your use case, you should choose the appropriate value for the SameSite attribute of your web session cookie.
To reinforce security, the Secure attribute must be set for the web session cookie when the connection is secured (HTTPS) to indicate to the browser that the cookie can be sent safely.
Keep reading to learn how 4D has your back to improve privacy and security across the web.