1. Preface: Project Background
Project situation: An enterprise mainly sells daily cleaning products through the e-commerce platform. Taobao ranks first in the vertical category. And the client company has a small development team, which can carry out operation and maintenance and prepare the project environment by itself, and the requirements are mainly confirmed with the client's development.
Project requirements: An expansion system (namely supply chain management platform) that can be connected with the original Wangdiantong ERP system is needed to synchronize the orders created by the channel to Wangdiantong ERP. Synchronized in ERP.
Project period: 14 working days (2 and a half weeks)
Number of participants: 2 people (1 product manager, 1 full stack).
Project started.....1 2 3 go
2. Day 1-2: Demand research
After the project contract is signed, we will negotiate with the customer on the time, location, and plan of the demand research as soon as possible. Then make arrangements for research work.
Since the project requirements of this project (supply chain management platform) are not particularly complicated, we arranged a 2-day research cycle and went to the customer site for face-to-face confirmation.
Research output: The system that needs to be built in Zhixin's low-code is divided into two operation ports: the channel end and the operation end, which need to be connected with Wangdiantong ERP.
Operation side: the internal personnel of the company participate in the management of channel and order information;
Channel side: support channel merchants to log in, and perform real-time data synchronization with the order operation behavior of Wangdiantong ERP;
In addition to the basic ordering behavior, the channel wallet function is also required. Returns initiated by the channel will be returned in the form of the channel wallet, and the amount in the wallet can be deducted in subsequent payments. (This is an additional extension requirement found in the on-site research, but it is estimated that the low-code implementation will not increase the workload too much, so I will add it)
The following is the business flow chart that we sorted out based on interviews with relevant business personnel. Like traditional development, this step cannot be saved. A flowchart with complete logic and detailed steps will save a lot of development time in the future.
3. Day 3-4: model combing
After the demand research of the supply chain management platform is completed, and the detailed business process logic is confirmed with the customer, we will start the demand sorting work.
The so-called sharpening a knife does not cut firewood by mistake.
Sorting out and analyzing requirements, and determining corresponding technical solutions, is a very important step in developing a system, and the low-code development model is no exception.
1. Low-code model combing:
The pre-model combing of low-code development is mainly divided into: "Functional modules - table models - field design "
This also corresponds to the low-code " application-module (data table)-field structure ".
First sort out the module list:
Then sort out the model module by module:
2. Prototype and functional design stage
After sorting out the model and interface, enter the prototype and function design stage.
Despite the rapid development and configuration of low-code, we still use traditional prototyping tools for prototyping. The main purpose of this is to match the needs of customers as much as possible. It will not be bound by the low-code platform (of course, this is also based on the powerful customization capabilities of the low-code platform to support this).
Here, we will ask the product manager to create a component library specifically for weaving letters, which can improve the speed of interaction and fit the low-code interaction as much as possible.
For some pages with special needs, we can also fully support customized design, which can be realized through the platform's custom pages.
Finally, a very critical step, to confirm all models and prototypes with users. Once confirmed, we can start our low-code technology review phase to determine the technology implementation plan for this development.
4. Day 5: Technical review
Difficulty 1: Wangdiantong ERP data docking solution
Two modules of ERP order and order are established in the low-code platform. Among them, the ERP order calls the query order interface of Wangdiantong ERP, and obtains the order information of Wangdiantong ERP in regular increments, and its table structure is consistent with the return parameters of the query order interface.
The order table stores the order information created in the low-code platform. After the creation is completed, the order creation interface of Wangdiantong ERP will be called to transfer the order information to Wangdiantong ERP. In the order table, the table can be defined according to the needs of customers. structure, you only need to ensure that the required fields of the incoming parameters in the interface for creating an order can be passed in correctly. Because both the order and the ERP order have the original order number, this field can be used as a unique identifier to synchronize the information of the ERP order to the order, such as order status, logistics order number, etc., to meet the data synchronization requirements.
In actual use, the user only needs to operate the order table to complete the operation of placing an order and synchronizing the order status.
Difficulty 2: Data isolation scheme for each module
The channel provider management system is divided into two operation ports: the channel end and the operation end. As the operation end, you can view all the information of the channel you manage, and as the channel end, you can only view all the information of your own channel.
Based on the above requirements, we first use the view method to establish the operation module of the channel. And by automatically setting the user's extended parameters, the channel user's channel id is bound to the user information. In the future, it is only necessary to add unified data filtering to the channel operation module to realize data isolation at the channel end.
For the operation side, we also automatically set the channel information that can be viewed by the operation into the user extension information, and add data filtering to each operable module to achieve data isolation on the operation side.
Difficulty 3: Channel Information Creation/Modification Review
When the customer wants to initiate a modification, the basic information, combination package and contract can be edited and reported as a whole. After the initiation, it will be reviewed by the financial department. After the review is passed, the modified content can be synchronized to the channel information.
Based on this requirement, we recreated a set of channel information tables to store the modified content, and implemented the approval function through the workflow. After the approval is passed, the modified data is copied to the channel information.
Difficulty 4: Adjustment of special interaction on the order page
Customers want to display the content of the product in the form of a card when selecting a product when placing an order, and the entire order process is divided into two steps, first select the product and then enter the delivery address.
Display products in the form of cards: We display the original search list in the form of a form, and at the same time load the products that customers can place an order by default, and the items that need to be ordered are those that the customer fills in the quantity.
Order step-by-step: The action of placing an order is to create data, so group the goods and select the delivery address, and then enable step-by-step display during creation.
So far, the demand sorting based on customer supply chain management business has been completed, and the next stage will officially enter the low-code development link.
Due to the limited space, please pay attention to me. The next part will continue to share with you the second stage of project actual combat: low-code function development .