# Developing Web-Based Process Management with Automatic Code Generation
## 3 Architecture
### Automatic Code Generation to Create a Task
One of the notable advantages of our implementation is the method we have adopted for data exchange. We have fragmented the delivery process rather than delivering all assets in a single monolithic chunk. HTML, CSS, and data are retrieved separately, ensuring swifter loading times. No matter the expansion of our site, each time a webpage is accessed, it necessitates packets of JavaScript, HTML, CSS, and other data. Our pages load with remarkable speed by fetching these assets individually from the server and database. Moreover, our system works with a Content Delivery Network (CDN) methodology. It verifies content versions and sends requests only for the changed assets. While this boosts performance, it is pivotal to recognize that scalability presents its unique challenges, which we tackle using distinct techniques. In Figure 21, HTML and JSON codes in the Source field in the WorkerContent table are integrated into these low-code platforms to support the dynamic content creation and display process. Regarding the functioning, firstly, code fragments in HTML and JSON format are saved in the specified database. These codes contain the structures and features that the user will use in their applications on the web. These saved code fragments are pulled from the database on demand by the platform and dynamically rendered on the user's interface. This process enables rapid prototyping, testing, and final release of the application. At the same time, centralized storage of code in a database brings operational advantages such as version control, backup, and deployment. As a result, this integration capability of low-code platforms accelerates application development processes, minimizes errors, and provides users with a more flexible development environment. ### Creating a Workflow Process in a Web Environment

In the implementation of the process, firstly, the tasks are detailed. Then, using the Web Application interface called \"Process Design Editor\", the relationship and interaction flow

Figure 4.1 WorkerContent data table. between these tasks are designed. This editor supports drag and drop, providing developers with an essential convenience in dynamically visualizing and editing the process. In Figure 22, taken as a reference, we can examine how users interact with flowchart flow diagrams to design a business process. Each symbol and flowchart represents a specific functionality or part of a process. The conditional flow, shown in Figure 23, enables the workflow to follow different paths as a specific condition is fulfilled. This methodology supports dynamic routing in the workflow based on specific conditions. Binary decision mechanisms typically evaluate the conditions. This fulfills the requirements for branching and merging workflows so that processes become more flexible and allow the flow to be managed accurately. Single Task Flow, depicted in Figure 24, is a workflow model in which each task is sequenced based on the completion of the previous one. This model is ideal for simple, low-complexity processes where tasks build on each other and occur sequentially. In this structure, where each task has a specific priority, high efficiency is achieved with the correct sequencing. The Multi-Task Flow presented in Figure 25 represents a workflow model in which multiple tasks are performed in parallel. This model emphasizes the independence of tasks within the process so that simultaneous progress is achieved without waiting for each task to complete. This approach is preferred for complex processes where waiting times must be

Figure 4.2 Condition flow diagram element. Figure 4.3 Flow diagram elements. Figure 4.4 Single Task Flow elements in condition scenario. minimized. The creation of the workflow is realized using specific design tools. These tools help place the workflow steps sequentially with \"drag and drop\" features. Workflow steps represent specific actions, such as sending an e-mail or retrieving data from a database. This process includes the following steps:

* The purpose of the workflow is defined.