CRM system deployment method and device, storage medium and computer equipment

Abstract

The invention provides a CRM system deployment method, which comprises the following steps: loading a configuration file and determining a target application scene in response to a CRM system deployment request, and reading target scene configuration information corresponding to the target application scene from the configuration file; according to the target scene configuration information, setting each function module in the target application scene, and adjusting a data format in the target application scene; according to the target scene configuration information, determining a target language corresponding to the target application scene, and according to the target language, the adjusted data format and the set function module, performing style adaptation on a business page of the target application scene in the CRM system; and generating an independent code deployment package of the target application scene according to the adjusted data format, the set function module, the corresponding target language and the business page with the adaptive style in the target application scene, so as to perform local deployment in the CRM system according to the independent code deployment package. In this way, the flexibility of the CRM system can be provided.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a CRM system deployment method, apparatus, storage medium and computer equipment. Background Art

[0002] As enterprises expand their businesses in the global market, the Customer Relationship Management (CRM) system has become a key tool for enterprises to improve customer satisfaction and manage customer resources. However, when facing a multinational market, the CRM system needs to be adapted and adjusted according to the business needs, market rules, and laws and regulations of different countries and regions. This requires the system to have the ability to handle localization requirements such as multiple languages, currencies, time formats, and mobile phone number rules. At the same time, many countries have strict requirements on data storage and privacy, requiring data to be stored in their own data centers, which increases the complexity of deployment.

[0003] At present, most CRM systems on the market use multiple sets of codes to handle the market needs of different countries respectively. This solution has led to a significant increase in development and maintenance costs. Whenever there is a need to adjust functions, such as turning on or off certain market-specific marketing functions, developers must modify and test each market separately, causing problems with repeated development and deployment. At the same time, when dealing with localization requirements such as multi-language adaptation, mobile phone number verification, and currency symbol display, the system usually requires customized processing, further reducing development efficiency. This makes the existing system lack flexibility in responding to market changes, unable to quickly adjust functional configurations, and leads to low overall operational efficiency. Summary of the invention

[0004] The purpose of this application is to solve at least one of the above-mentioned technical deficiencies, especially the technical defect of lack of flexibility in the prior art.

[0005] In a first aspect, the present application provides a CRM system deployment method, the method comprising:

[0006] In response to a CRM system deployment request, a configuration file is loaded, a target application scenario is determined, and target scenario configuration information corresponding to the target application scenario is read from the configuration file;

[0007] According to the target scenario configuration information, each functional module in the target application scenario is set, and the data format in the target application scenario is adjusted;

[0008] Determine the target language corresponding to the target application scenario based on the target scenario configuration information, and adapt the style of the business page of the target application scenario in the CRM system based on the target language, adjusted data format, and set functional modules;

[0009] According to the adjusted data format, set functional modules, corresponding target language and style-adapted business pages in the target application scenario, an independent code deployment package of the target application scenario is generated, so as to be locally deployed in the CRM system according to the independent code deployment package.

[0010] In one embodiment, the step of reading target scenario configuration information corresponding to the target application scenario from the configuration file includes:

[0011] In the vue component, read the scene configuration information of multiple application scenarios through the configuration file;

[0012] According to the target application scenario, the target scenario configuration information is loaded in each scenario configuration information.

[0013] In one of the embodiments, in a vue component, the step of reading scene configuration information of multiple application scenes through a configuration file includes:

[0014] Determine a scenario identifier for each application scenario;

[0015] In the vue component, use each scene identifier to call the vuex corresponding to the vue component, so that vuex asynchronously loads the scene configuration information of each application scene from the configuration file according to each scene identifier.

[0016] In one embodiment, the step of setting each functional module in the target application scenario according to the target scenario configuration information includes:

[0017] According to the target scene configuration information, the conditional rendering instructions in the vue component are used to determine whether the switch status value corresponding to each functional module is a true value, and the functional modules whose switch status values ​​are true values ​​are rendered and displayed, and the functional modules whose switch status values ​​are not true values ​​are hidden.

[0018] In one embodiment, the step of adjusting the data format in the target application scenario includes:

[0019] Determine the data format configuration in the target application scenario according to the target scenario configuration information;

[0020] According to the data format configuration, the data format in the target application scenario is converted.

[0021] In one embodiment, the step of adapting the style of a business page of a target application scenario in a CRM system according to a target language, an adjusted data format, and a set functional module includes:

[0022] According to the target language, adjusted data format and set functional modules, a streaming layout method is used to control the arrangement and distribution of each page element in the business page of the target application scenario, and the content size attribute is used to set the size of each page element.

[0023] In one embodiment, the step of generating an independent code deployment package for the target application scenario according to the adjusted data format, the set functional modules, the corresponding target language and the style-adapted business pages in the target application scenario includes:

[0024] Determine the target output directory corresponding to the target application scenario;

[0025] Based on the adjusted data format, set functional modules, corresponding target language, and style-adapted business pages in the target application scenario, use Webpack and Vue-CLI to generate an independent code deployment package for the target application scenario and save it to the target output directory.

[0026] In a second aspect, the present application provides a CRM system deployment device, the device comprising:

[0027] A target scenario configuration information acquisition module is used to respond to a CRM system deployment request, load a configuration file, determine a target application scenario, and read target scenario configuration information corresponding to the target application scenario from the configuration file;

[0028] A target scenario configuration adjustment module is used to set various functional modules in the target application scenario and adjust the data format in the target application scenario according to the target scenario configuration information;

[0029] The business page style adaptation module is used to determine the target language corresponding to the target application scenario according to the target scenario configuration information, and to adapt the style of the business page of the target application scenario in the CRM system according to the target language, the adjusted data format and the set functional modules;

[0030] The independent code deployment package generation module is used to generate an independent code deployment package for the target application scenario based on the adjusted data format, set functional modules, corresponding target language and style-adapted business pages in the target application scenario, so as to perform local deployment in the CRM system based on the independent code deployment package.

[0031] In a third aspect, the present application provides a storage medium: the storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the CRM system deployment method in any one of the above embodiments.

[0032] In a fourth aspect, the present application provides a computer device, comprising: one or more processors, and a memory;

[0033] The memory stores computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the steps of the CRM system deployment method in any one of the above embodiments are performed.

[0034] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0035] In the CRM system deployment method, device, storage medium and computer equipment provided in the present application, customized deployment can be performed according to the specific needs of different markets by loading configuration files and determining the target application scenarios. Specifically, first, by reading the target scenario configuration information, settings are made for each functional module, and the data format is adjusted; then, the style of the business page is adapted according to the language requirements of the target scenario and the adjusted data format, thereby ensuring that the system can meet localization requirements such as multiple languages, currencies, and time formats; finally, local deployment is achieved in the CRM system by generating an independent code deployment package. This method avoids repeated development and deployment in traditional systems that require individual modifications and testing for each market through centralized configuration management, improves development efficiency and the flexibility of the CRM system, and reduces operating costs caused by changes in market demand. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0037] Figure 1 A flowchart of a CRM system deployment method provided in an embodiment of the present application;

[0038] Figure 2 A schematic diagram of the structure of a CRM system deployment device provided in an embodiment of the present application;

[0039] Figure 3 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0041] The present application provides a CRM system deployment method. The following embodiments are described by taking the method applied to a computer device as an example. It can be understood that the computer device can be any device with data processing functions, including but not limited to a single server, a server cluster, a personal laptop, a desktop computer, etc. Figure 1 As shown, the method may include the following steps:

[0042] S101: In response to a CRM system deployment request, a configuration file is loaded, a target application scenario is determined, and target scenario configuration information corresponding to the target application scenario is read from the configuration file.

[0043] Among them, the CRM system (Customer Relationship Management System) is a software system that helps companies manage interactions with customers, improve customer satisfaction and loyalty, and optimize sales, marketing, customer service and other aspects. Configuration files are files that store information about system settings, environmental parameters, application scenarios, etc. Through configuration files, its functions can be automatically adjusted or adapted according to different needs without modifying the code every time. The target application scenario refers to the functional configuration and adaptation requirements in the CRM system for a specific market or environmental requirement. Each application scenario may correspond to different business rules, languages, data formats, etc. The target scenario configuration information contains settings and configuration content related to a specific target application scenario, such as enabling and disabling of functional modules, data format adjustments, language settings, etc.

[0044] In this step, a specific configuration file needs to be read first. Once the configuration file is loaded, a specific target application scenario is selected according to the current request or demand. For example, it can be determined by user input or external request, such as passing parameters through the user interface or API, and the corresponding target application scenario is determined by matching parameter values. Then, according to the identification of the target application scenario, such as a scenario ID or name, the configuration information corresponding to the scenario is extracted from the loaded configuration file.

[0045] It can be understood that, first of all, the operations of loading configuration files and reading target scenario configuration information can be customized according to specific market needs, avoiding the complexity of modifying the code every time the function is adjusted. Automatically obtaining relevant configuration information according to the different needs of the target application scenario ensures the flexibility and efficiency of the deployment process. In addition, automatic loading and reading of configuration files can quickly respond to different business environments. In this way, it can be easily expanded to multiple markets, adapt to local rules and requirements, optimize the development and deployment process, and improve overall operational efficiency.

[0046] S102: According to the target scenario configuration information, various functional modules in the target application scenario are set, and the data format in the target application scenario is adjusted.

[0047] Among them, the functional module is an independent component or functional unit in the CRM system, which is usually used to perform specific tasks or business operations, such as customer management, sales tracking, marketing, etc. The data format refers to the standard structure or representation followed when processing, storing or exchanging data within the CRM system, which may involve date format, currency format, number precision, etc.

[0048] In this step, first determine the functional modules that need to be enabled or disabled based on the target scenario configuration information. Each functional module may have different configuration parameters, such as enabling / disabling a module, adjusting module parameters, etc. Extract these settings from the target scenario configuration information, and apply these settings to the corresponding functional modules through a configuration management system, such as a database or configuration file, by modifying the module's configuration file, adjusting the field values ​​in the database table, or updating the configuration information in the CRM system. According to the target application scenario, adjust the data format to adapt to localization requirements. Specifically, the format to be used can be determined by reading the configuration information and the data format can be adjusted, such as the date format "yyyy-mm-dd" or "dd / mm / yyyy", the currency symbol " "or" ”.

[0049] It can be understood that, first of all, by setting up the functional modules, certain functions can be flexibly enabled or disabled according to specific application scenarios, thereby ensuring that the CRM system can meet different market and business needs. By adjusting the data format, the CRM system can meet the localization requirements of various regions, such as different date formats, currency symbols, etc., to improve user experience and business adaptability. In addition, this ability to dynamically adjust functions and data formats enables the CRM system to respond quickly to market changes, improves the scalability, maintainability and flexibility of the CRM system, and enhances the adaptability of the CRM system in a diversified environment.

[0050] S103: Determine the target language corresponding to the target application scenario according to the target scenario configuration information, and perform style adaptation on the business page of the target application scenario in the CRM system according to the target language, the adjusted data format, and the set functional modules.

[0051] The target language refers to the language used by the CRM system in a specific application scenario, such as Chinese, English, French, etc. The target language determines the language form of the user interface display language, prompt information and other text content. The business page is the user interface in the CRM system, which is usually used to display and manage customer information, sales data, marketing activities, etc.

[0052] In this step, the required target language is determined according to the language requirements in the target scenario configuration information. The language identifier of the target application scenario can be matched by reading the language settings in the configuration file or database, such as "en" for English and "zh-CN" for Simplified Chinese. Once the target language is determined, the style of the page is automatically adjusted according to the requirements of the language and the adjusted data format and function modules, including font selection, such as using the default English font for English and the appropriate Chinese font for Chinese, text alignment, such as some languages ​​may need to be displayed from right to left, and the display format of date, time and currency, such as the "MM / DD / YYYY" format commonly used in English-speaking countries, and Asian countries may use the "YYYY year MM month DD day" format. Style adaptation can be achieved through CSS style sheets, dynamic page templates or front-end frameworks, automatically loading or applying appropriate styles according to the configured language and format rules.

[0053] It can be understood that, first of all, by determining the adaptation language according to the target language, it can ensure that the business page can accurately display the language corresponding to the target market and provide a user-friendly interface experience. Secondly, automatically adjusting the style of the business page, especially adapting it according to the different characteristics of the language, can enable users in different regions to use the CRM system comfortably. In this way, the CRM system can achieve efficient localization and internationalization, improve user experience, and reduce development and maintenance costs. This method ensures the consistency of the CRM system in multi-language and multi-regional markets, while also improving the flexibility and scalability of the CRM system, which can quickly adapt to market changes and needs, greatly improving the operational efficiency of the enterprise.

[0054] S104: Generate an independent code deployment package for the target application scenario according to the adjusted data format, set functional modules, corresponding target language and style-adapted business pages in the target application scenario, so as to perform local deployment in the CRM system according to the independent code deployment package.

[0055] Among them, an independent code deployment package refers to a complete, independent code package generated according to a specific target application scenario, such as the target language, functional module, data format, etc., which contains all necessary files, configurations, and resources and can be independently run and deployed in a specific environment. Local deployment means installing the generated independent code deployment package on a specific physical or virtual machine so that it can run on the device.

[0056] In this step, after determining the configuration of the target application scenario, these configurations are automatically integrated together according to the adjusted data format, the set functional modules and the target language, etc., to generate a complete code package. Among them, it can be implemented by a build tool. By packaging the relevant code, style, configuration files and other resource files into an independent deployment package, it is ensured that the package can run independently in the target environment. Once the deployment package is generated, the generated code package can be uploaded and deployed to the target server or cloud environment using an automated deployment tool. The deployment process usually includes configuring the target environment, starting services, monitoring logs, etc., to ensure that the deployment package can run correctly in the target environment.

[0057] It can be understood that, first of all, generating an independent code deployment package encapsulates all configurations, functions, and styles specific to the target application scenario, ensuring that only necessary functional modules and configuration files are included in the target environment, thereby improving deployment efficiency and reducing redundancy and complexity. Secondly, local deployment can ensure that the generated code package can run independently in the target environment without relying on the external environment or excessive configuration. This independence makes the deployment process more efficient and can support a variety of different hardware or virtual environments, thereby providing enterprises with greater flexibility and scalability.

[0058] In the above embodiment, by loading the configuration file and determining the target application scenario, customized deployment can be performed according to the specific needs of different markets. Specifically, first, by reading the target scenario configuration information, settings are performed for each functional module, and the data format is adjusted; then, according to the language requirements of the target scenario and the adjusted data format, the style of the business page is adapted to ensure that the system can meet localization requirements such as multiple languages, currencies, and time formats; finally, by generating an independent code deployment package, local deployment is achieved in the CRM system. This method avoids repeated development and deployment in traditional systems that require individual modifications and testing for each market through centralized configuration management, improves development efficiency and the flexibility of the CRM system, and reduces operating costs caused by changes in market demand.

[0059] In one embodiment, the step of reading target scenario configuration information corresponding to the target application scenario from the configuration file includes:

[0060] In the vue component, read the scene configuration information of multiple application scenarios through the configuration file;

[0061] According to the target application scenario, the target scenario configuration information is loaded in each scenario configuration information.

[0062] Among them, Vue component is an independent functional unit in Vue.js, usually composed of templates, scripts and styles, used to implement specific interfaces and interactive logic. Components can be reused and nested in Vue applications.

[0063] Specifically, in the Vue component, the configuration information of multiple application scenarios is first obtained through file reading operations. For example, use `fetch()` or `axios` to request to read the configuration file on the server, or use the `fs` module of Node.js to read the local file. Once the configuration information of multiple application scenarios is read, the Vue component extracts the relevant settings of the target scenario from the read configuration information according to the target application scenario selected by the user. This process can be completed by looking up the matching scene ID or name, similar to accessing the value through the key of an object.

[0064] In an example, in a Vue component, the code for passing the feature configuration for each market through the configuration file looks like this:

[0065]

[0066] In this embodiment, the operation of reading the configuration file can dynamically load the configuration information of multiple scenarios, so that one set of code can support multiple markets without manually modifying the code each time, thereby improving the flexibility of the CRM system and enabling it to adapt to the needs of different markets and environments. In addition, dynamic reading and loading of configuration information avoids hard coding and static configuration, ensuring that the CRM system can quickly respond to changes in market demand.

[0067] In one embodiment, in a vue component, the step of reading scene configuration information of multiple application scenes through a configuration file includes:

[0068] Determine a scenario identifier for each application scenario;

[0069] In the vue component, use each scene identifier to call the vuex corresponding to the vue component, so that vuex asynchronously loads the scene configuration information of each application scene from the configuration file according to each scene identifier.

[0070] Among them, the scenario identifier is a tag or ID used to uniquely identify a specific application scenario. It can be a string or a number, representing each specific application scenario in the CRM system. Vuex is the state management library of Vue.js, which is used to centrally manage the state of all components. Through Vuex, components in the application can share states, submit state changes, process asynchronous tasks, etc. It is used to centrally manage and access data flows in Vue applications. Asynchronous loading refers to loading data or performing operations in the background without blocking the main thread, allowing the program to continue to perform other tasks while waiting for data to load.

[0071] Specifically, the application scenario identifier can be read from the configuration file or database, or it can be statically defined in the front-end code. Each identifier corresponds to a specific application scenario, such as configurations for different countries or markets. Based on the identifier, the corresponding configuration can be determined and loaded. In the Vue component, the scenario identifier is passed to Vuex as a parameter, triggering the `dispatch()` method to call the corresponding action. The action decides to asynchronously load the corresponding scenario configuration information from the configuration file based on the scenario identifier. The loading process is usually completed through asynchronous requests, which may use HTTP requests, `fetch()` or `async / await`. If the data is stored locally, it can also be loaded by reading from local storage. After loading is complete, Vuex stores the configuration information in the state management system for use by the vue component.

[0072] In one example, after loading and storing the scene configuration information, the front-end can further manage the configuration information through Vuex or other state management tools. Specifically, in store / modules / market.js, you can define a state called marketConfig to store configuration information for different countries or markets. Through Vuex's actions, you can asynchronously load the configuration of the current market from the API or local configuration file, and submit this data to mutations for updating. Mutations store the loaded configuration data in state, while getters allow vue components to dynamically obtain these configurations, ensuring that components can obtain the latest market configuration data when needed. The relevant code is as follows:

[0073]

[0074]

[0075]

[0076]

[0077] In this embodiment, first, Vuex is called through each scene identifier and the configuration information of a specific scene is loaded. Different scene configurations can be loaded according to different identifiers, ensuring that the configuration information of each application scene is independent and manageable, avoiding confusion or errors caused by multiple scenes sharing one configuration. Secondly, the state management mechanism of Vuex can centrally manage the configuration information of the application, making the data flow clearer and controllable. In addition, asynchronous loading of configuration information is more flexible, and scene configurations can be dynamically loaded according to real-time changing needs without redeploying or modifying the code. This reduces the workload of development and maintenance, while improving the scalability of the application. When the application scenario changes, it can quickly respond and load new configuration information to ensure that users can obtain interfaces and functions that meet their needs.

[0078] In one embodiment, the step of setting each functional module in the target application scenario according to the target scenario configuration information includes:

[0079] According to the target scene configuration information, the conditional rendering instructions in the vue component are used to determine whether the switch status value corresponding to each functional module is a true value, and the functional modules whose switch status values ​​are true values ​​are rendered and displayed, and the functional modules whose switch status values ​​are not true values ​​are hidden.

[0080] Among them, the conditional rendering instructions in the Vue component refer to the `v-if`, `v-show` and other instructions provided by Vue.js, which are used to control the rendering and display of components or DOM elements according to conditions. `v-if` determines whether to render an element based on the condition, while `v-show` only displays or hides the element by controlling the `display` style of the element. The switch state value refers to the Boolean value used to control the enablement or disablement of the function module. A value of `true` means that the function is enabled, and a value of `false` means that the function is disabled.

[0081] Specifically, the Vue component reads the switch state value of each functional module from the configuration data of the target scene. These values ​​are usually Boolean, such as `true` or `false`. In the Vue component, conditional rendering instructions such as `v-if` or `v-show` are used to judge these values. If the switch state value is `true`, Vue will perform a rendering operation to generate and display the functional module. For example, use `v-if="module.enabled"` to check the enabled state of the module. If it is `true`, the module is rendered. If the switch state value is `false`, Vue will control the element not to be rendered, or hide the rendered element. For example, use `v-if="module.enabled"` to judge. If the value is `false`, the module will not be rendered, or use `v-show="module.enabled"` to hide it.

[0082] In this embodiment, by using the conditional rendering instructions in the Vue component, the display and hiding of the functional modules can be dynamically adjusted according to the target scene configuration information, so that the visibility of the functional modules can be effectively controlled according to the truth or falseness of the switch state value, ensuring that only the required modules are displayed, and those unnecessary modules are hidden, avoiding interface clutter or functional conflicts. By implementing conditional rendering in Vue, the function display in different scenarios can be flexibly handled, so that the CRM system can quickly adapt to various needs without manually changing or reconstructing the code on the front end. In this way, the development process becomes more efficient and the scalability of the CRM system is enhanced, especially in CRM systems configured in multiple countries or multiple scenarios, which can ensure the flexibility and responsiveness of the interface and improve the user experience.

[0083] In one embodiment, the step of adjusting the data format in the target application scenario includes:

[0084] Determine the data format configuration in the target application scenario according to the target scenario configuration information;

[0085] According to the data format configuration, the data format in the target application scenario is converted.

[0086] Data format configuration is a set of rules and settings that specify how to format, process, and store data. Data format configuration usually involves date format, number format, currency symbol, etc., to ensure that the CRM system can correctly process and display data in different application scenarios.

[0087] Specifically, first, read the relevant data format configuration according to the target scenario configuration information, and parse these configuration data in the Vue component or Vuex to identify the format requirements in specific scenarios. For formats such as dates, numbers, and currency symbols, extract the corresponding format information and perform data format conversion based on these requirements. For example, when the target application scenario requires the date to be displayed in the `YYYY-MM-DD` format, and the source data is in the `MM / DD / YYYY` format, use JavaScript's date processing library for conversion to ensure that the data is correctly converted from the source format to the target format. Similarly, the number format will be adjusted according to the configuration to ensure compliance with local numerical display standards.

[0088] In one example, by using mapGetters in the vue component to access marketConfig, the mobile phone number validation rules, currency symbols, and date formats can be dynamically adjusted according to different market configurations. For example, based on the mobile phone number rules of different markets, the system will adjust the validation logic of the front-end form; for currency display, according to the market's currency symbol configuration, the front-end interface will display the corresponding currency symbol; at the same time, the date format will be formatted according to the market's localization requirements to ensure consistency with user habits. The relevant code is as follows:

[0089]

[0090]

[0091]

[0092]

[0093] In this embodiment, by determining the data format configuration according to the target scenario configuration information and performing format conversion, it is possible to ensure that the data is correctly displayed and processed in different application scenarios. This not only enhances the adaptability of the CRM system, but also avoids erroneous display or calculation problems caused by format differences. For example, in different markets or regions, the formats of dates and numbers may be different. By dynamically loading and converting the data format, the consistency and correctness of the application can be ensured globally. Data format conversion also ensures that the CRM system can provide customized display effects based on user needs or regional regulations, improves user experience, and reduces the risk of errors.

[0094] In one embodiment, the step of adapting the style of the business page of the target application scenario in the CRM system according to the target language, the adjusted data format and the set functional modules includes:

[0095] According to the target language, adjusted data format and set functional modules, a streaming layout method is used to control the arrangement and distribution of each page element in the business page of the target application scenario, and the content size attribute is used to set the size of each page element.

[0096] Among them, flow layout is a layout method in which the position and size of elements are dynamically adjusted according to the available space on the page. Content size attributes define the size and proportion attributes of page elements and control the display effect and layout of elements on the page.

[0097] Specifically, in Vue components, the arrangement and distribution of page elements can be achieved through CSS flow layout, such as `flexbox` or `grid`. Depending on the target language, the adjusted data format, and the set functional modules, the arrangement of elements can be controlled in real time by dynamically binding CSS classes or inline styles. For example, in the `flexbox` layout, you can set the `flex-direction` to determine the arrangement direction of the elements, and adjust `justify-content` and `align-items` as needed to control the alignment. In addition, the content size attribute can be used to dynamically adjust the size of page elements. For example, in responsive design, the `flexbox` layout automatically adjusts the width and height of the elements according to the size changes of the browser window to adapt to different screen sizes. At the same time, depending on the target language and data format, the `font-size`, `padding`, `margin` and other styles of the elements can also be dynamically adjusted to ensure that the page elements can be properly displayed in different language environments.

[0098] Understandably, multi-language support is a key requirement for CRM systems, especially when faced with languages ​​with large differences in text length, the UI layout is prone to confusion. By using flow layout techniques such as `Flexbox` or `Grid`, you can ensure that the text lengths of different languages ​​will not cause layout confusion. For elements with fixed widths, you can also use CSS's `min-content` and `max-content` properties to control the display of elements to prevent text from exceeding the boundaries, thereby avoiding layout confusion. This layout method allows the page to maintain a consistent structure and good visual effects in various language environments.

[0099] In this embodiment, by dynamically adjusting the arrangement and size of page elements according to the target language, data format and functional modules, it is possible to better adapt to different languages ​​and market demands and provide a better user experience. In a multilingual environment, the streaming layout can flexibly adjust the arrangement of page elements to ensure that the page content can be presented clearly and orderly in any language. In addition, the content size attribute is used to control the display of fixed-width elements to avoid text overflow and ensure the neatness and consistency of the page. Dynamically adjusting the size and layout of the content can also ensure that the page responds well to various screen sizes, improves the adaptability and user experience of the page, and reduces development and maintenance costs. This flexible layout method enables the CRM system to more efficiently support globalization and localization needs.

[0100] In one embodiment, the step of generating an independent code deployment package for the target application scenario according to the adjusted data format, the set functional modules, the corresponding target language and the style-adapted business pages in the target application scenario includes:

[0101] Determine the target output directory corresponding to the target application scenario;

[0102] Based on the adjusted data format, set functional modules, corresponding target language, and style-adapted business pages in the target application scenario, use Webpack and Vue-CLI to generate an independent code deployment package for the target application scenario and save it to the target output directory.

[0103] The target output directory refers to the storage path where code and configuration files are saved when the deployment package is generated. Webpack is a module packager that can package various resources into static files. Vue-CLI is a command line tool for Vue.js, which is used to quickly build, develop, and deploy Vue.js projects, and provides a variety of configurations and plug-in support.

[0104] Specifically, by reading the configuration file or according to the input target scenario identifier, a specific directory path is determined, which is used to store the packaged application files. In actual operation, the target output directory can be set by modifying the `output.path` field in the Webpack configuration. Use Webpack and Vue-CLI for packaging according to the needs of the target application scenario. Webpack will process static resources such as JavaScript, CSS, and images according to the instructions in the project configuration file, and package them into one or more output files. Vue-CLI will generate an optimized version for the production environment through the `vue-cli-service build` command combined with the configuration file of the Vue project. For example, in a Vue project, the Webpack build process is triggered by `npm run build` or `vue-cli-service build`. Webpack packages resources according to the project configuration file, processes entry files, dependent modules, etc., and generates the final application package. After packaging, Vue-CLI will save the output files to the specified target output directory.

[0105] In one example, based on Vue-CLI and Webpack packaging tools, independent deployment for multiple national markets is achieved through different environment configurations and build scripts. By injecting the market configurations of each country into the packaging environment, it is ensured that the functions, UI, and data processing logic of different markets can be localized and customized and run independently during deployment. First, the different requirements of each national market are configured through the environment variable mechanism of Vue-CLI. Vue-CLI can load different .env files during construction to define the market parameters of each country, such as API interfaces, function switches, style configurations, etc. Then, in vue.config.js, the corresponding configurations can be loaded according to different environments, and the packages for different markets can be output to separate directories. The relevant code is as follows:

[0106]

[0107]

[0108] Finally, add the npm command for multi-market packaging by modifying the scripts section in package.json. The following is an example of the command:

[0109]

[0110] In this embodiment, by determining the output directory corresponding to the target application scenario and using Webpack and Vue-CLI to generate an independent code deployment package, the configurations of different markets and scenarios can be packaged independently, thereby ensuring that the configurations of the corresponding scenarios are accurately loaded and applied during deployment. This approach allows each target scenario to have an independent configuration and resource package, avoids modifying the source code, and flexibly adapts to the needs of different countries or markets. At the same time, the configuration files and codes of each scenario can be processed separately, reducing resource conflicts and dependencies and improving deployment efficiency. In addition, by saving the deployment package to the target output directory, subsequent management and deployment operations become more convenient, and the CRM system can quickly locate and apply configuration files for different scenarios.

[0111] The following describes the CRM system deployment device provided in the embodiment of the present application. The CRM system deployment device described below and the CRM system deployment method described above can be referred to in correspondence with each other. Figure 2 As shown, the present application provides a CRM system deployment device, the device comprising:

[0112] The target scenario configuration information acquisition module 201 is used to respond to the CRM system deployment request, load the configuration file and determine the target application scenario, and read the target scenario configuration information corresponding to the target application scenario from the configuration file;

[0113] The target scenario configuration adjustment module 202 is used to set each functional module in the target application scenario and adjust the data format in the target application scenario according to the target scenario configuration information;

[0114] The business page style adaptation module 203 is used to determine the target language corresponding to the target application scenario according to the target scenario configuration information, and perform style adaptation on the business page of the target application scenario in the CRM system according to the target language, the adjusted data format and the set function module;

[0115] The independent code deployment package generation module 204 is used to generate an independent code deployment package for the target application scenario according to the adjusted data format, set functional modules, corresponding target language and style-adapted business pages in the target application scenario, so as to perform local deployment in the CRM system according to the independent code deployment package.

[0116] In one embodiment, the target scene configuration information acquisition module 201 includes:

[0117] The scene configuration information reading unit is used to read the scene configuration information of multiple application scenes through the configuration file in the Vue component;

[0118] The target scene configuration information loading unit is used to load the target scene configuration information into each scene configuration information according to the target application scene.

[0119] In one embodiment, the scene configuration information reading unit includes:

[0120] A scene identifier determination subunit, used to determine a scene identifier for each application scene;

[0121] The scene configuration information loading sub-unit is used to call the vuex corresponding to the vue component using each scene identifier in the vue component, so that vuex asynchronously loads the scene configuration information of each application scene from the configuration file according to each scene identifier.

[0122] In one embodiment, the target scene configuration adjustment module 202 includes:

[0123] The function setting adjustment unit is used to determine whether the switch status value corresponding to each function module is a true value according to the target scene configuration information and the conditional rendering instructions in the vue component, and render and display the function modules whose switch status values ​​are true values, and hide the function modules whose switch status values ​​are not true values.

[0124] In one embodiment, the target scene configuration adjustment module 202 includes:

[0125] A data format configuration determining unit, configured to determine a data format configuration in a target application scenario according to the target scenario configuration information;

[0126] The data format conversion unit is used to convert the data format in the target application scenario according to the data format configuration.

[0127] In one embodiment, the business page style adaptation module 203 includes:

[0128] The business page style adaptation unit is used to control the arrangement and distribution of each page element in the business page of the target application scenario in a streaming layout manner according to the target language, the adjusted data format and the set functional modules, and to set the size of each page element using the content size attribute.

[0129] In one embodiment, the independent code deployment package generation module 204 includes:

[0130] A target output directory determining unit, used to determine a target output directory corresponding to a target application scenario;

[0131] The independent code deployment package generation unit is used to generate an independent code deployment package for the target application scenario using Webpack and Vue-CLI according to the adjusted data format, set functional modules, corresponding target language and style-adapted business pages in the target application scenario, and save it to the target output directory.

[0132] In one embodiment, the present application further provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the CRM system deployment method as described in any of the above embodiments.

[0133] In one embodiment, the present application further provides a computer device having computer-readable instructions stored therein. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the CRM system deployment method as described in any one of the above embodiments.

[0134] Indicatively, Figure 3 As shown, Figure 3 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. The computer device 300 may be provided as a server. Figure 3 The computer device 300 includes a processing component 302, which further includes one or more processors, and a memory resource represented by a memory 301, for storing instructions that can be executed by the processing component 302, such as an application. The application stored in the memory 301 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 302 is configured to execute instructions to perform the CRM system deployment method of any of the above embodiments.

[0135] The computer device 300 may further include a power supply component 303 configured to perform power management of the computer device 300, a wired or wireless network interface 304 configured to connect the computer device 300 to a network, and an input / output (I / O) interface 305. The computer device 300 may operate based on an operating system stored in the memory 301, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, Free BSD TM, or the like.

[0136] Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0137] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the term "include", "comprise" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements not only includes those elements, but also includes other elements not clearly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of more restrictions, the elements defined by the sentence "including one..." do not exclude the existence of other identical elements in the process, method, article or equipment including the elements. Herein, "one", "one", "said", "the" and "it" may also include plural forms, unless the context clearly indicates another way. A plurality refers to at least two cases, such as 2, 3, 5 or 8, etc. "And / or" includes any and all combinations of the relevant listed items.

[0138] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can refer to each other.

[0139] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A CRM system deployment method, characterized in that: The method comprises: In response to a CRM system deployment request, a configuration file is loaded and a target application scenario is determined, and target scenario configuration information corresponding to the target application scenario is read from the configuration file; According to the target scenario configuration information, each functional module in the target application scenario is set, and the data format in the target application scenario is adjusted; Determine the target language corresponding to the target application scenario according to the target scenario configuration information, and perform style adaptation on the business page of the target application scenario in the CRM system according to the target language, the adjusted data format and the set functional modules; According to the adjusted data format, set functional modules, corresponding target language and style-adapted business pages in the target application scenario, an independent code deployment package of the target application scenario is generated, so as to be locally deployed in the CRM system according to the independent code deployment package.

2. The CRM system deployment method according to claim 1, characterized in that: The step of reading the target scenario configuration information corresponding to the target application scenario from the configuration file comprises: In the vue component, the scene configuration information of multiple application scenes is read through the configuration file; According to the target application scenario, the target scenario configuration information is loaded into each of the scenario configuration information.

3. The CRM system deployment method according to claim 2, characterized in that: The step of reading the scene configuration information of multiple application scenes through the configuration file in the vue component includes: Determining a scenario identifier for each of the application scenarios; In the vue component, the vuex corresponding to the vue component is called using each of the scene identifiers, so that the vuex asynchronously loads the scene configuration information of each of the application scenes from the configuration file according to each of the scene identifiers.

4. The CRM system deployment method according to claim 2, characterized in that: The step of setting each functional module in the target application scenario according to the target scenario configuration information includes: According to the target scene configuration information, the conditional rendering instruction in the vue component is used to determine whether the switch status value corresponding to each of the functional modules is a true value, and the functional modules whose switch status values ​​are true values ​​are rendered and displayed, and the functional modules whose switch status values ​​are not true values ​​are hidden.

5. The CRM system deployment method according to claim 2, characterized in that: The step of adjusting the data format in the target application scenario includes: Determining the data format configuration in the target application scenario according to the target scenario configuration information; According to the data format configuration, the data format in the target application scenario is converted.

6. The CRM system deployment method according to claim 2, characterized in that: The step of adapting the style of the business page of the target application scenario in the CRM system according to the target language, the adjusted data format and the set functional modules includes: According to the target language, the adjusted data format and the set functional modules, a streaming layout method is used to control the arrangement and distribution of each page element in the business page of the target application scenario, and a content size attribute is used to set the size of each page element.

7. The CRM system deployment method according to claim 2, characterized in that: The step of generating an independent code deployment package for the target application scenario according to the adjusted data format, the set functional modules, the corresponding target language and the style-adapted business pages in the target application scenario includes: Determine a target output directory corresponding to the target application scenario; According to the adjusted data format, set functional modules, corresponding target language and style-adapted business pages in the target application scenario, use Webpack and Vue-CLI to generate an independent code deployment package for the target application scenario and save it to the target output directory.

8. A CRM system deployment device, characterized in that: The device comprises: A target scenario configuration information acquisition module is used to respond to a CRM system deployment request, load a configuration file, determine a target application scenario, and read target scenario configuration information corresponding to the target application scenario from the configuration file; A target scenario configuration adjustment module, used to set each functional module in the target application scenario and adjust the data format in the target application scenario according to the target scenario configuration information; A business page style adaptation module, used to determine the target language corresponding to the target application scenario according to the target scenario configuration information, and perform style adaptation on the business page of the target application scenario in the CRM system according to the target language, the adjusted data format and the set functional modules; An independent code deployment package generation module is used to generate an independent code deployment package for the target application scenario based on the adjusted data format, set functional modules, corresponding target language and style-adapted business pages in the target application scenario, so as to perform local deployment in the CRM system according to the independent code deployment package.

9. A storage medium, characterized in that: The storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the CRM system deployment method according to any one of claims 1 to 7.

10. A computer device, characterized in that: include: one or more processors, and memory; The memory stores computer-readable instructions, and when the computer-readable instructions are executed by the one or more processors, the steps of the CRM system deployment method according to any one of claims 1 to 7 are performed.

Images