Whatever your business, you must create listings, inventories, tracking sheets, product sheets, invoices, and many other documents. These documents are usually printed or saved in PDF for archiving.
4D Write Pro is the ideal tool to create all your documents. Here is a list of several features available in 4D Write Pro that can help you make beautiful documents for printing:
- page layout and margin management for printing,
- pdf export,
- document protection,
- table creation,
- table formatting with repeated headers,
- definition of a data context,
- inserting ORDA formulas in a table (new in 4D v19 R6).
Using these different features, here are some examples of documents produced.
The days of defining business-related formulas in your 4D user interface are over; these concepts offer you a new way to separate your business logic from the UI, enabling you to improve performance by optimizing the parts separately.
And now, with 4D v19 R6, aliases are fully available and ready to use for scalars in your iOS and Android mobile projects as soon your aliases are defined on the 4D side.
As developers, we often create complex and advanced 4D Write Pro documents. We may generate tables that need to be filled from a data source, and we may not be sure of the exact rows and columns. Manually filling the tables with data every time is a laborious task. We heard you, and here is where data context comes as an invaluable option, opening the world of ORDA and object-oriented development to 4D Write Pro documents.
It is now possible to define a “datasource” for the tables of 4D Write Pro. Whether it is an entity selection or a collection, this “datasource” will automatically feed the rows of these tables.
Let’s delve into the details!
by Add Komoncharoensiri, Director of Technical Services at 4D Inc
Here we go with another set of tips and tricks.
As you know, 4D Knowledge Base is a library of information about the 4D technology where weekly tech tips and monthly technotes are actively published. If you missed the last tips on the KB, that’s fine; here is a compilation from the past few weeks.
This blog post covers 16 tips:
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.
4D Write Pro documents often contain formulas returning data or calculations depending on the database. Thanks to the use of contexts, associating that data with documents is now child’s play!
In this blog post, we’ll see how the combination of 4D Write Pro documents with data retrieved using ORDA makes the code clear and easy to maintain.
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.
When you create a new field in your database, 4D allows you to choose to map NULL value to blank values or not. Starting from 4D v19 R4, in new projects, 4D will no longer by default map the NULL value to an empty value.
4D v19 R4 is shipped with a new ORDA concept: Aliases. They are the logical and complementary continuation of computed attributes.
This blog post explains what aliases are and highlights their advantages, especially when to use one or the other… or both.
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!