Hello everyone, I am the product manager of JVS. Today, I received a customized demand to customize and extend the file management of enterprise red header files in “51wordless · Enterprise Documents”. Is the logic for this implementation implemented at the base framework level or within the application?

Let me give you some background:

JVS is the background user system integrated user system, enterprise documents is the application foreground on JVS, why are there front and back? In fact, the entire architecture is as follows, there are multiple foreground applications, which can be logically separated from each other at the business level.

Our enterprise documents already support online rich text co-editing, online table co-editing, online brain map editing, online wireframes editing, including preview of MSoffice files in a variety of formats, and now we receive new red header file management.

So the product manager sorted out the whole thought process

Step one, how do you implement the functionality

Red header files are actually very strict format requirements, so we have implemented the online text editing function as shown in figure:

Internal thinking, because rich text editing is more prone to editing, rather than formatting, as shown in rich text editing paAS, then to think about how to achieve the document red.

The second step is to explore the solid line model

Finally, after massive consulting and thinking, the product manager found an implementation case of the live network. Then we need to process and integrate through templates. Templates try to define more abstract format support, as shown in the figure:

Support pictures, support format text, support the generation of images, support long text, support signature, support form and so on, from the functional level of basic level can achieve a strict set of red documents.

From the functional level, configure the red header file template (style, variables, etc.), through the form input red header file

The third step, internal discussion (SI) theory (BI) technology capability realization possibility

Product and technology are discussed, and there are two ways to realize the role of a product:

A. Add a file type “Format file” inside the enterprise document to create files directly in the enterprise document;

B, implemented at the base framework level, the editor is a generic capability that is invoked at the time of use. As shown in figure:

Finally, after overall consideration, I choose the second option. From the perspective of product planning, except for red header files, risk control reports and printing templates all require this capability, so this function is taken as the basic capability.

The fourth step, based on the possibility of technology implementation, using the scenario thinking

Scene design:

A. Process management

  • Administrator configuration template (Display style + information entry form)
  • Use the user to select a template, fill in the information, preview the red header file, submit the approval process
  • In combination with the flow engine configuration process, the red header file completes the signature and the generation of the red header file
  • Use the user export file for provisioning

B, composition format file editing

  • A user creates a format file in an enterprise document
  • Jump to format file editor through interface
  • After the configuration is complete, save the configuration and exit. The system generates the corresponding file and displays it in the enterprise document

Step 5: Design the editor and rough prototype

A prototype format file editor is shown below:

Use entrance design:

Step 6: Product manager and technician discuss scheduling

Roughly scheduled version, 2.1.5, to implement.

Checking analysis

Demand side:

More and more enterprises now want to privatize a lot of online management format files, so the format of documents with high requirements, such as red header files, standard reports (risk control reports, evaluation reports), filing documents of online management and closed-loop management demand is increasing.

Design process:

From the product manager to receive the demand, find a reasonable technical solution, and then to think about the scene, and finally design and implement the prototype, of course, the whole process is not so simple as small writing, in fact, many product managers lack of thinking about the whole process, and many product managers will not find the wheels already exist.

Later thinking:

Product managers should check out Github and Gitee, not necessarily technical people.

Demo environment: knowledge.bctools.cn/

Open source: gitee.com/software-mi…

Welcome. Perfect fishing. Another day of rowing.