Author: Marie-Sophie Landrieu-Yvert

Avatar

• Product Owner •

Marie-Sophie Landrieu-Yvert has joined the 4D Product team as a Product Owner in 2017. As a Product Owner, she is in charge of writing the user stories then translating it to functional specifications. Her role is also to make sure that the feature implementation delivered is meeting the customer need.

Marie-Sophie graduated from the ESIGELEC Engineering School and began her career as an engineer at IBM in 1995. She participated on various projects (maintenance or build projects) and worked as a Cobol developer. Then she worked as an UML designer and Java developer. Lately her main roles were analyzing and writing functional requirements, coordinate business and development teams.
Product

Your data live … in a web interface

Automatically translated from English

As a 4D developer, you may have dreamed of visualizing your data immediately and easily while you update/create it. Or maybe you’re a 4D administrator and you need to quickly find a record that causes an error due to inappropriate data. This has been possible with 4D’s built-in query interface and output form, but it can take time to customize this form and you may need a more responsive tool.

How about a modern and user-friendly web interface to view your data? And for a cherry on the top, what if this interface comes with a powerful query engine? Dream no more! All this is now a reality thanks to Data Explorer, a new tool provided as a Preview for you to evaluate it and give us your feedback.

Of course, it will be enhanced in future versions.

Let’s discover it now!

Product

Move to shareable entity selections smoothly

Automatically translated from English

In this blog post, you discovered the power that shareable entity selections can offer. 4D focuses on data sharing because, in the long run, it leads to performance.

But we’re aware that this strategy might not be your current strategy. We’ve followed the discussions on the forum and understood your comments and feelings.

To soften this step and give you more flexibility and tools, we’ve made some enhancements regarding the nature (shareable or non-shareable) of entity selections.

Before continuing, we highly recommend that you read this blog post and this one so you can make sense of the enhancements described below.

Product

ORDA – Share an entity selection between processes

Automatically translated from English

4D v16 R6 introduced a new concept of communication between processes: shared object and shared collection variables! Thanks to this, you’re able to easily share information between processes.

Until now, entity selections weren’t shareable between processes. However, that has changed … we’re pleased to announce that in 4D v18 R5 entity selections are shareable! 

Gone are the days of building a list of primary keys to move a selection of entities to another process. Enhance your multi-processes code by including ORDA entity selections as shared objects.

Keep reading to learn more.

Product

ORDA – Improve your API with function scope

Automatically translated from English

4D v18 R4 and ORDA made it possible for you to create high-level class functions above the data model. This allows you to write business-oriented code to hide complexity, reduce errors, and speed up the development process.

With 4D v18 R5, we’re bringing even more features to help you optimize and organize your code. For example, you might need to run a function locally on the client to improve performance when working in client/server mode. It’s now possible! Or if you expose your database as a REST server, you might want some functions to be available on the server-side but hidden for your REST clients. This is also possible!

Product

ORDA Classes to handle your data model

Automatically translated from English

In a previous blog post, we introduced you to the world of ORDA data model classes. Now it’s time to get our hands dirty and learn more!

You already know that ORDA’s structure (datastore, dataclass, entity, entity selection) is made up of objects. But they’re not just objects, they’re strongly-typed objects linked to specific ORDA classes. This means that you can write functions to hide the complexity of your data’s physical implementation.

Product

Welcome to the world of ORDA classes

Automatically translated from English

ORDA was a revolution with 4D v17. It opened a whole new world of possibilities and took you to another programming dimension. A dimension where you can easily develop applications using an object-oriented approach.

We didn’t stop there! We continued to add enhancements to ORDA through a set of features in each subsequent feature release. Now with 4D v18 R4, we’re thrilled to be going another step further with the availability of ORDA data model classes. Classes dedicated to your data model.

This will greatly elevate your code. Your applications can now easily expose services, be more manageable and easier to maintain, and seamlessly integrate with other applications.

This is another big feature made possible thanks to the projects!

 

Product

ORDA: an up-to-date datastore without restarting

Automatically translated from English

We’re thrilled to announce that 4D v18 R3 includes an enhancement that will have a huge impact on the developer’s experience. A feature many of you have requested, and 4D delivers!

When you work in 4D standalone mode during the development phase (writing and testing your code), you’re no longer required to restart your database in order to have an up-to-date datastore (ds) when the structure is updated!

Now you don’t need to restart the database each time you need a new attribute or a new table in your code! It’s all automatic!

When you call the ds command, you get an up-to-date datastore object. This means that several versions of this datastore object are handled at the same time … depending on when you updated your structure … without breaking running processes.

If you work in client / server mode, this works fine for code running on the 4D Server.

For remote clients, you simply need to restart the client requiring the structure’s update.