Expansion of the Log function

With a timestamp on the object under the following three conditions:
I thought it would be effective if I could keep a log
The movement may be heavy, so it may be good to be able to choose on or off

In addition, in each of the three roles, object data is utilized.
Developers, trainers, operator,etc. can incorporate their own features into Qodly

I think we are meeting the direction of automatic application development in the future

In addition to disseminating information mainly in English-only documents
I think multilingual users can also systematically share and engage with Qodly

  1. Logging CRUD to the database


Protection of user data (dataclass)

  1. Logging from the user’s browser to the application


Tracking a User’s Application Interactions
Training to operate the application


Mouse clicks, text input, file uploads, etc.

  1. Detailed logs of developer operations


Systematization and componentization of developer operations
Developer training
Auto-generate applications and macro them


Component Placement
Editing CSS
Adding a Function
Adding Dataclasses, Removing Dataclasses, etc.
Creating a Webform

All logs are not only for emergencies
If you look at it for the purpose of using it in various situations and related parties
I thought it was good

I will add it

There is a mechanism to save these three log functions in three dataclasses managed by Qodly.
I thought that if there was, developers would not have to learn new knowledge and would be able to use it easily
Of course, security needs to be considered.

I tried to organize it again

What operators and developers type using the mouse and keyboard
It is an object type and is recorded internally qodly
Run a new anthropomorphic group of processes inside Qodly
You can pass a virtual, object-type log to the process. To the existing structure of Qodly
Let it be saved

We thought that this mechanism might have the following effects

Automating the operation of operator entry of complex data

Error checking for operations in which an operator enters complex data

Automating input when migrating complex data from other apps

Automating developer input

Error checking for developer operations

Automating app development

These mechanisms are different from the methods processed by Qodly’s existing mechanisms.
It is possible to prevent the contents from becoming a black box

In the operation performed by operators and developers
About the current roles of Qodly and people
I think that the burden on people can be reduced while maintaining visualization

Maybe it’s just a spontaneous idea
As I go back and forth in the direction I’m going,
I’m learning Qodly

In addition, there are also such effects

In the development of Qodly’s app
Bringing some of 4D’s support work to qodly’s inner workings
It is possible to leave it to us

The app developers, operators, and 4D staff involved in Qodly
I thought it would be good if we could make it a more efficient and creative way of working

Back to the story

First of all, if there is a function that can save all logs
Developers and trainers are free to create useful tools inside Qodly.
I think
In other words, it would be nice to be able to divide, manage, and duplicate them like 4D components
I think

The struggle of those who are trying to learn creative and wonderful software like Qodly and 4D
The struggles of the 4D staff to support it

From now on, for learners, it is important to visualize and systematize the operation of Qodly and 4D in logs.
I think it’s a good thing

In addition, when learning about increasingly complex systems, there is a limit to how much you can only provide conventional documentation

I think there is a limit to relying on 4D staff to support you for that learning

If you use logs, you can use the
There may also be such a way to use it

It may be possible to visualize the operation from the user’s browser, analyze the browsing of the application, the level of interest of the consumer, and feed the analysis results back to the development