New work, new inspiration

It took some time to enter a new company. After a long time, my mind calmed down slowly. So before that, many words seem to have become empty talk, and I also said, many learning processes want to be recorded, but many times the idea is constantly changing over time. Just like learning Microsoft WF, It is very powerful at the beginning, it was later discovered that it had been bound by its functions. Although it was subsequently extended by functions and also implemented custom workflows, as the business continues to change, the process functions are not enough. When we get the final result, we have implemented the majority of the WF process. In the end, we decided to give up WF and define the data structure by ourselves, today, I share the same mood and wrote this Summary log, hoping that I will have different ideas soon.

The size of the new company was not big. The only reason why I was able to convince myself to leave it was its development method. After this period of work, I also found that my colleagues were also very good, we are lucky to be in this group.

I have just mentioned the company's development method, and the overall framework is platform-based Development. The main direction is office automation, personnel, project, and contract management, this is also the direction you have always wanted to contact. I would like to share with you my experiences on this development method so far.

Based on the platform, configuration is simply used. Both form operations, process control, and query statistics are generated based on configuration. I have also summarized that the display method of the software is nothing more than input forms and lists. For form classification, it may involve common forms and process forms. For complexity, there may be a nested relationship between forms, such as the parent-child relationship and some special operations, such as single and multiple choices, personnel role selection, etc, most functions do not need to be written.Code. From a local perspective, the platform features are common, but if the overall function requirements of the project are quite complex, there will be a lot of functions that correspond to the platform's implementation, in addition, we will constantly encounter new strange functional requirements.

The most obvious advantage of such development is the fast development speed, whether it is the development of new projects or the maintenance of old projects; then it solves the possibility of hand errors, most of the operations are through configuration, therefore, mobile phone errors do not exist at ordinary times. Even if there is an error, the platform will give a prompt accordingly. you can focus on your business. For industrial software, knowledge of the industry is essential. This development method can focus on learning and building businesses and databases. Of course, in my spare time, I also need to add technical knowledge to better understand the principles of the platform. It is also a way to improve the development speed and quality.

Basic functions, forms, permissions, processes, organizational structures, and miscellaneous small functions, such as general selection, tree structure, dynamic personnel roles, uploads, data table relationships, menu configurations, etc, there are still a lot of details to be summarized later.

Recently, csla encountered a problem. In an editable sub-object set, the process of creating, loading, and saving sub-objects is controlled by the parent object. When you use winform to edit an object, the parent form is passed to the child form as a reference to add and edit sub-objects. Therefore, the property update process of sub-objects also corresponds to the sub-Object List in the parent window. The problem is that, the attributes of sub-objects are not always valid. During the editing process, if the Sub-Object Attributes violate the rules, the list binding in the parent form will be abnormal, but if the attributes are not passed by reference, then how to update the object to the parent object after update, and the parent object must be bound and refreshed. In principle, this editing process should not respond to the parent form at the same time. It feels awkward, But how should we implement this relationship...