C # WeChat portal and application development (8)-Introduction to features of WeChat portal application management system

After encapsulating the underlying interfaces step by step, the interfaces are gradually upgraded to automated configuration, automated response, and background processing interface optimization and improvement, we strive to build a comprehensive and applicable portal application management system.

The portal application management system adopts the MVC + EasyUI-based route, because most domain name servers can only support. NET4.0. Therefore, based on MVC3 and C #4.0, it can be basically deployed in any.. NET Server.

In the portal system, perform the following operations:

1) implement dynamic configuration of menus and update them to servers;

2) dynamically define events and response messages to respond to menu actions for different industries and needs;

3) dynamically configure and Process Response commands to process messages in the entire response chain;

4) obtains information about subscription users and user groups, and maintains user group information;

5) manage and update multimedia files, text messages, and other content to facilitate message pushing.

6) send messages to the selected subscriber or group.

 

1. menu management

Manage menus in the system and submit the menus to the server for dynamic configuration and generation of menus. This allows the system to adapt to various needs and achieve flexible processing.

The menu addition interface is as follows.

The menu modification interface is as follows:

The menu definition is stored in the database. To submit the menu to the server and take effect, you need to call the API for processing, I added a method to the Controller on the page to submit to the server.

On the portal of the service account, the menu shows the effect as follows.

2. Handling menu events

In most cases, dynamically generated menus are used as Click operations, that is, the event response operations of each menu need to be defined. If we use them, we can understand that the event processing function is as follows, generally, it can respond to user text messages, image messages, text messages, and other content. Generally, most text messages or text messages are used.

To further reuse the response content, we manage menu event definitions and content definitions separately. Event definitions can use multiple text messages or combine multiple text messages, this allows for a more flexible environment.

Add an event as follows:

Event Response content encoding, which can be selected from the input or edit button. When you select the edit button, A dialog box is displayed for you to select the encoding of the Event Response content.

After the selection is complete, return to the new page and you will see that the returned record is the record we selected.

The event editing interface is shown as follows, similar to the content of the newly added interface.

3. Message Content Management

As mentioned above, menu events are processed through associated event encoding, and events can combine multiple message content. Therefore, message content is the minimum unit for responding to customer operations, they can be a text message, a text message, or a combination of multiple messages (in the same type ).

To facilitate management, I divide messages into text, instructions, and text types. If necessary, I can also refine the messages into other types as needed.

The message content adding interface is as follows.

The text message interface is as follows.

Here, whether it is text message or text message, we define the message with the definition of text message. If it is text message, we only need to obtain the description content as the message body.

The text message editing interface is shown as follows. You can fill in the complete content and images, as well as detailed links to the page.

The above message of the customer relationship management system is displayed on the mobile phone as follows. Click the link to switch to the Message jump link address.

4. Maintenance of response commands

The maintenance of response commands is similar to event management. It mainly defines the instructions used to facilitate the construction of the response chain of the response system, so as to implement step-by-step operation commands.

After the response command is set in the background, the system can process it according to the response command chain. First, we need to provide a prompt interface for entering the response chain, as shown below.

However, after selecting the response system in the menu, the system returns a text prompt interface, as shown below.

This interface prompts some buttons, including several fixed keys and some business keys. Enter a simple 1 ~ 6. You can respond to the selection.

 

We can see the interface above. After Entering command 1, the system enters the next layer of response command, and then lists several buttons and content prompts that can be entered.

When we continue to input the business key 1, the response is a text message, which is also a detailed description of the key.

At this time, we can also enter the * Key to return to the top menu.

If you enter 0, it is transferred to the Customer Service conversation mode. Any messages you send will be forwarded to multiple customer service systems.

 

After a user sends a message, the customer service assistant can receive the message and process the message and respond to the customer in a timely manner.

 

5. Subscription user management

To manage subscription users and group information more effectively, we can obtain relevant information from the server for us to understand the user information we are interested in, or to prepare for subsequent sending of Group messages.

The subscription user management is as follows.

Double-click to view the subscription user information. The details page of the subscription user is as follows.

7. User Group Management

The page for creating a group is shown below.

The Edit Group information page is as follows.

After editing and saving the group, the system will remember the modified and synchronized content, create the group on the server, and change the group name, modify on the server, and then perform synchronization list processing.