CRM system deployment methods, devices, storage media, and computer equipment

Abstract

This application provides a CRM system deployment method that, in response to a CRM system deployment request, loads a configuration file and determines the target application scenario. It reads the target scenario configuration information from the configuration file. Based on the target scenario configuration information, it sets up various functional modules in the target application scenario and adjusts the data format. Based on the target scenario configuration information, it determines the target language corresponding to the target application scenario. Based on the target language, the adjusted data format, and the set functional modules, it performs style adaptation on the business pages of the target application scenario in the CRM system. Based on the adjusted data format, set functional modules, corresponding target language, and style-adapted business pages in the target application scenario, it generates an independent code deployment package for the target application scenario, and then deploys it locally in the CRM system using this independent code deployment package. This provides greater flexibility to the CRM system.

Description

Technical Field

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

[0002] As businesses expand globally, Customer Relationship Management (CRM) systems have become crucial tools for improving customer satisfaction and managing customer resources. However, when facing multiple markets, CRM systems need to be adapted and adjusted to the business needs, market rules, and laws and regulations of different countries and regions. This requires the system to handle localization needs such as multiple languages, currencies, time formats, and mobile number rules. Furthermore, many countries have strict requirements for data storage and privacy, requiring data to be stored in their own data centers, thus increasing the complexity of deployment.

[0003] Currently, most CRM systems on the market employ multiple sets of code to handle the specific needs of different national markets. This approach significantly increases development and maintenance costs. Whenever functional adjustments are needed, such as enabling or disabling market-specific marketing features, developers must modify and test each market individually, leading to redundant development and deployment. Furthermore, handling localization requirements such as multilingual support, phone number verification, and currency symbol display typically requires customization, further reducing development efficiency. This makes existing systems inflexible in responding to market changes, unable to quickly adjust feature configurations, and resulting in overall low operational efficiency. Summary of the Invention

[0004] The purpose of this application is to address at least one of the aforementioned technical deficiencies, particularly the lack of flexibility in the prior art.

[0005] Firstly, this application provides a method for deploying a CRM system, the method comprising:

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

[0007] Based on the target scenario configuration information, configure each functional module in the target application scenario and adjust the data format in the target application scenario;

[0008] Based on the target scenario configuration information, determine the target language corresponding to the target application scenario, and adapt the style of the business pages of the target application scenario in the CRM system according to the target language, the adjusted data format, and the set functional modules.

[0009] Based on the adjusted data format, set functional modules, corresponding target language, and style-adapted business pages in the target application scenario, generate an independent code deployment package for the target application scenario, and deploy it locally in the CRM system according to the independent code deployment package.

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

[0011] In Vue components, scenario configuration information for multiple application scenarios is read through configuration files;

[0012] Based on the target application scenario, load the target scenario configuration information into the configuration information of each scenario.

[0013] In one embodiment, the step of reading scenario configuration information for multiple application scenarios through a configuration file in a Vue component includes:

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

[0015] In a Vue component, each scenario identifier is used to call the corresponding Vuex instance, so that Vuex can asynchronously load the scenario configuration information for each application scenario from the configuration file based on each scenario identifier.

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

[0017] Based on the target scenario configuration information, the conditional rendering directive in Vue components is used to determine whether the switch state value corresponding to each functional module is true. Functional modules with true switch state values ​​are rendered and displayed, while functional modules with false switch state values ​​are hidden.

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

[0019] Based on the target scenario configuration information, determine the data format configuration in the target application scenario;

[0020] Based on 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 business pages for a target application scenario in a CRM system according to the target language, the adjusted data format, and the set functional modules includes:

[0022] Based on the target language, the adjusted data format, and the set functional modules, a fluid 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 size of each page element is set using the content size attribute.

[0023] In one embodiment, the step of generating 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, 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] Secondly, this application provides a CRM system deployment apparatus, the apparatus comprising:

[0027] The target scenario configuration information acquisition module is used to respond to CRM system deployment requests, load configuration files, determine target application scenarios, and read target scenario configuration information corresponding to the target application scenario from the configuration file.

[0028] The target scenario configuration adjustment module is used to set the 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 based on the target scenario configuration information, and to adapt the style of the business pages 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 standalone code deployment package generation module is used to generate a standalone 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 standalone code deployment package.

[0031] Thirdly, this application provides a storage medium storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of any of the CRM system deployment methods described in the above embodiments.

[0032] Fourthly, this application provides a computer device, including: one or more processors, and a memory;

[0033] The memory stores computer-readable instructions that, when executed by one or more processors, perform the steps of any of the CRM system deployment methods described in the above embodiments.

[0034] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0035] The CRM system deployment method, apparatus, storage medium, and computer equipment provided in this application enable customized deployment based on the specific needs of different markets by loading configuration files and determining target application scenarios. Specifically, firstly, by reading the target scenario configuration information, settings are configured for each functional module, and data formats are adjusted. Next, based on the language requirements of the target scenario and the adjusted data formats, the business pages are styled to ensure the system meets localization requirements such as multilingual support, currency, and time formats. Finally, by generating an independent code deployment package, local deployment is achieved within the CRM system. This method, through centralized configuration management, avoids the repetitive development and deployment required by traditional systems that involve separate modifications and testing for each market, improving development efficiency and the flexibility of the CRM system, and reducing operating costs caused by changes in market demands. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 A flowchart illustrating the CRM system deployment method provided in this application embodiment;

[0038] Figure 2 This is a schematic diagram of the structure of the CRM system deployment device provided in the embodiments of this application;

[0039] Figure 3 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0040] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0041] This application provides a CRM system deployment method. The following embodiments illustrate this method using a computer device as an example. It is understood that the computer device can be any device with data processing capabilities, including but not limited to a single server, server cluster, personal laptop, desktop computer, etc. Figure 1 As shown, the method may include the following steps:

[0042] S101: In response 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.

[0043] A CRM (Customer Relationship Management) system is a software system that helps businesses manage their interactions with customers, improve customer satisfaction and loyalty, and optimize various aspects of sales, marketing, and customer service. A configuration file stores information about system settings, environmental parameters, and application scenarios. Through configuration files, functionality can be automatically adjusted or adapted to different needs without requiring code modifications each time. A target application scenario refers to the functional configuration and adaptation requirements of the CRM system for a specific market or environment. Each application scenario may correspond to different business rules, languages, data formats, etc. Target scenario configuration information includes settings and configurations related to the specific target application scenario, such as enabling and disabling functional modules, adjusting data formats, and setting languages.

[0044] This step first requires reading a specific configuration file. Once the configuration file is loaded, a specific target application scenario is selected based on the current request or requirement. For example, this can be determined by user input or an external request, such as passing parameters through a user interface or API, and matching the parameter values ​​to determine the corresponding target application scenario. Next, based on the identifier of the target application scenario, such as a scenario ID or name, the configuration information corresponding to that scenario is extracted from the loaded configuration file.

[0045] This is understandable. First, 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 code every time a feature is adjusted. Automatically obtaining relevant configuration information based on different requirements of the target application scenario ensures the flexibility and efficiency of the deployment process. Furthermore, automatically loading and reading configuration files allows for rapid response to different business environments. In this way, it can be easily scaled to multiple markets, adapting to local rules and requirements, optimizing development and deployment processes, and improving overall operational efficiency.

[0046] S102: Based on the target scenario configuration information, configure each functional module in the target application scenario and adjust the data format in the target application scenario.

[0047] Functional modules are independent components or functional units within a CRM system, typically used to perform specific tasks or business operations, such as customer management, sales tracking, and marketing. Data format refers to the standard structure or representation followed when processing, storing, or exchanging data within a CRM system, and may involve date formats, currency formats, and numerical precision.

[0048] In this step, the first step is to 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. These settings are extracted from the target scenario configuration information and applied to the corresponding functional modules through a configuration management system, such as a database or configuration file. This can be done by modifying the module's configuration file, adjusting field values ​​in the database table, or updating the configuration information in the CRM system. Based on the target application scenario, the data format is adjusted to adapt to localization requirements. Specifically, the appropriate format can be determined by reading the configuration information and the data format can be adjusted, such as date format "yyyy-mm-dd" or "dd / mm / yyyy", currency symbol "...". "or" ".

[0049] Understandably, firstly, by configuring functional modules, certain functions can be flexibly enabled or disabled according to specific application scenarios, ensuring that the CRM system can meet the needs of different markets and businesses. Secondly, by adjusting data formats, the CRM system can meet the localization requirements of various regions, such as different date formats and currency symbols, improving user experience and business adaptability. Furthermore, this ability to dynamically adjust functions and data formats allows the CRM system to respond quickly to market changes, enhancing its scalability, maintainability, and flexibility, and strengthening its adaptability in diverse environments.

[0050] S103: Determine the target language corresponding to the target application scenario according to the target scenario configuration information, and 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 function modules.

[0051] Among them, 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 text content such as the display language of the user interface and prompt messages. The business page is the user interface in the CRM system, usually used to display and manage customer information, sales data, marketing activities, etc.

[0052] In this step, determine the required target language according to the language requirements in the target scenario configuration information. The language identifier corresponding to the target application scenario can be matched by reading the language settings in the configuration file or database. For example, "en" represents English, and "zh-CN" represents Simplified Chinese. Once the target language is determined, automatically adjust the style of the page according to the requirements of this language, the adjusted data format, and the function modules, including the selection of fonts. For example, the default English font is used for English, and a suitable Chinese font is used for Chinese. Also, adjust the text alignment. For example, some languages may need to be displayed from right to left, as well as the display formats of dates, times, and currencies. For example, the "MM / DD / YYYY" format is commonly used in English-speaking countries, and Asian countries may use the "YYYY年MM月DD日" format. The style adaptation can be achieved through CSS style sheets, dynamic page templates, or front-end frameworks, and the appropriate styles are automatically loaded or applied according to the configured language and format rules.

[0053] It can be understood that first, 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. Second, automatically adjusting the style of the business page, especially adapting according to the different characteristics of languages, enables users in different regions to use the CRM system comfortably. In this way, the CRM system can achieve efficient localization and internationalization, improve the user experience, and reduce the development and maintenance costs. This method ensures the consistency of the CRM system in multi-language and multi-region markets, and at the same time improves the flexibility and scalability of the CRM system, enabling it to quickly adapt to market changes and demands, and greatly improving the operational efficiency of enterprises.

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

[0055] A standalone code deployment package refers to a complete and independent code package generated based on a specific target application scenario, such as the target language, functional modules, and data format. It contains all necessary files, configurations, and resources and can run and deploy independently in a specific environment. Local deployment refers to installing the generated standalone code deployment package onto a specific physical or virtual machine, enabling it to run on that device.

[0056] In this step, after determining the configuration for the target application scenario, the system automatically integrates these configurations based on the adjusted data format, set functional modules, and target language to generate a complete code package. This can be achieved using a build tool. By packaging related code, styles, configuration files, and other resource files into a standalone deployment package, the system ensures that the package can run independently in the target environment. Once the deployment package is generated, an automated deployment tool can be used to upload and deploy the generated code package to the target server or cloud environment. The deployment process typically includes configuring the target environment, starting services, and monitoring logs to ensure that the deployment package runs correctly in the target environment.

[0057] Understandably, firstly, generating a standalone code deployment package encapsulates all target application-specific configurations, functionalities, and styles together, ensuring that the target environment contains only the necessary functional modules and configuration files, thereby improving deployment efficiency and reducing redundancy and complexity. Secondly, local deployment ensures that the generated code package can run independently in the target environment without relying on external environments or excessive configuration. This independence makes the deployment process more efficient, supports various different hardware or virtual environments, and thus provides enterprises with greater flexibility and scalability.

[0058] In the above embodiments, by loading configuration files and determining the target application scenario, customized deployment can be carried out according to the specific needs of different markets. Specifically, firstly, by reading the target scenario configuration information, settings are made 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 pages 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, through centralized configuration management, avoids the repetitive development and deployment of modifying and testing each market separately in traditional systems, improves development efficiency and the flexibility of the CRM system, and reduces operating costs caused by changes in market demands.

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

[0060] In Vue components, scenario configuration information for multiple application scenarios is read through configuration files;

[0061] Based on the target application scenario, load the target scenario configuration information into the configuration information of each scenario.

[0062] In Vue.js, a component is an independent functional unit, typically composed of templates, scripts, and styles, used to implement specific interface and interaction logic. Components can be reused and nested within a Vue application.

[0063] Specifically, in Vue components, configuration information for multiple application scenarios is first retrieved through file read operations. For example, `fetch()` or `axios` can be used to request and read configuration files from a server, or the `fs` module in Node.js can be used to read local files. Once the configuration information for multiple application scenarios has been read, the Vue component extracts the relevant settings for the target application scenario from the read configuration information, based on the user's selected target scenario. This process can be accomplished by looking up matching scenario IDs or names, similar to accessing values ​​via object keys.

[0064] In one example, the code for passing the feature configuration of each market through a configuration file in a Vue component is shown below:

[0065]

[0066] In this embodiment, the operation of reading the configuration file can dynamically load configuration information for multiple scenarios, enabling a single codebase to support multiple markets without requiring manual code modifications each time. This improves the flexibility of the CRM system, allowing it to adapt to the needs of different markets and environments. Furthermore, dynamically reading and loading configuration information avoids hard-coding and static configuration, ensuring the CRM system can quickly respond to changes in market demands.

[0067] In one embodiment, the steps of reading scenario configuration information for multiple application scenarios through a configuration file in a Vue component include:

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

[0069] In a Vue component, each scenario identifier is used to call the corresponding Vuex instance, so that Vuex can asynchronously load the scenario configuration information for each application scenario from the configuration file based on each scenario identifier.

[0070] The scenario identifier is a unique tag or ID used to 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 for Vue.js, used to centrally manage the state of all components. Through Vuex, components in an application can share state, commit state changes, and handle asynchronous tasks. It is used to centrally manage and access the data flow in a Vue application. Asynchronous loading refers to loading data or performing operations in the background without blocking the main thread, allowing the program to continue executing other tasks while waiting for data to load.

[0071] Specifically, application scenario identifiers can be read from configuration files or databases, or 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 this identifier, the corresponding configuration can be determined and loaded. In Vue components, the scenario identifier is passed as a parameter to Vuex, triggering the `dispatch()` method to call the corresponding action. This action determines, based on the scenario identifier, to asynchronously load the corresponding scenario configuration information from the configuration file. The loading process is usually completed through asynchronous requests, possibly using HTTP requests, `fetch()`, or `async / await`. If the data is stored locally, it can also be loaded by reading from local storage. After loading, Vuex stores the configuration information in the state management system for use by Vue components.

[0072] In one example, after loading and storing the scenario configuration information, the frontend can further manage this information using Vuex or other state management tools. Specifically, in `store / modules / market.js`, a state named `marketConfig` can be defined to store configuration information for different countries or markets. Through Vuex actions, the current market configuration can be asynchronously loaded from the API or local configuration files, and this data can be committed to mutations for updates. Mutations store the loaded configuration data in the state, while getters allow Vue components to dynamically retrieve this configuration, ensuring that components can obtain the latest market configuration data when needed. The relevant code is shown below:

[0073]

[0074]

[0075]

[0076]

[0077] In this embodiment, firstly, Vuex is invoked and configuration information for a specific scenario is loaded using each scenario identifier. This allows for loading different scenario configurations based on different identifiers, ensuring that the configuration information for each application scenario is independent and manageable, avoiding the chaos or errors caused by multiple scenarios sharing a single configuration. Secondly, Vuex's state management mechanism enables centralized management of application configuration information, making data flow clearer and more controllable. Furthermore, asynchronous loading of configuration information is more flexible, dynamically loading scenario configurations based on real-time changes in requirements without needing to redeploy or modify code. This reduces development and maintenance workload while improving application scalability. When application scenarios change, the system can quickly respond and load new configuration information, ensuring users receive an interface and functionality that meets their needs.

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

[0079] Based on the target scenario configuration information, the conditional rendering directive in Vue components is used to determine whether the switch state value corresponding to each functional module is true. Functional modules with true switch state values ​​are rendered and displayed, while functional modules with false switch state values ​​are hidden.

[0080] In Vue components, conditional rendering directives refer to directives such as `v-if` and `v-show` provided by Vue.js, used to control the rendering and display of components or DOM elements based on conditions. `v-if` determines whether to render an element based on a condition, while `v-show` only shows or hides the element by controlling its `display` style. Switch values ​​are boolean values ​​used to control whether a feature module is enabled or disabled. A value of `true` enables the feature, and a value of `false` disables it.

[0081] Specifically, Vue components read the on / off state values ​​of each feature module from the target scenario's configuration data. These values ​​are typically boolean, such as `true` or `false`. In Vue components, conditional rendering directives like `v-if` or `v-show` are used to evaluate these values. If the on / off state value is `true`, Vue performs a rendering operation, generating and displaying the feature module. For example, using `v-if="module.enabled"` to check the module's enabled state, if it's `true`, the module is rendered. If the on / off state value is `false`, Vue controls whether the element is rendered or hides already rendered elements. For example, using `v-if="module.enabled"` to check if the value is `false`, the module is not rendered, or `v-show="module.enabled"` is used to hide it.

[0082] In this embodiment, by using conditional rendering directives in Vue components, the display and hiding of functional modules can be dynamically adjusted according to the target scenario configuration information. This effectively controls the visibility of functional modules based on the truth value of their on / off states, ensuring that only necessary modules are displayed while unnecessary ones are hidden, avoiding interface clutter or functional conflicts. Implementing conditional rendering in Vue allows for flexible handling of functional displays in different scenarios, enabling the CRM system to quickly adapt to various needs without requiring manual changes or code refactoring on the front end. This makes the development process more efficient and enhances the scalability of the CRM system, especially in CRM systems configured for multiple countries or scenarios, ensuring interface flexibility and responsiveness and improving user experience.

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

[0084] Based on the target scenario configuration information, determine the data format configuration in the target application scenario;

[0085] Based on the data format configuration, the data format in the target application scenario is converted.

[0086] Data format configuration refers to a set of rules and settings that specify how data is formatted, processed, and stored. Data format configuration typically involves date formats, number formats, currency symbols, etc., ensuring that the CRM system can correctly process and display data in different application scenarios.

[0087] Specifically, firstly, the relevant data format configurations are read based on the target scenario configuration information, and these configuration data are parsed in the Vue component or Vuex to identify the format requirements under specific scenarios. For formats such as dates, numbers, and currency symbols, the corresponding format information is extracted, and data format conversion is performed according to these requirements. For example, when the target application scenario requires the date to be displayed in `YYYY-MM-DD` format, while the source data is in `MM / DD / YYYY` format, a JavaScript date processing library is used for conversion to ensure that the data is correctly converted from the source format to the target format. Similarly, the number format is also adjusted according to the configuration to ensure that it conforms to the local numerical display standards.

[0088] In one example, by accessing `marketConfig` using `mapGetters` in a Vue component, the phone number verification rules, currency symbol, and date format can be dynamically adjusted based on different market configurations. For instance, the system will adjust the validation logic of the front-end form based on the phone number rules of different markets; for currency display, the front-end interface will display the corresponding currency symbol according to the market's currency symbol configuration; and the date format will be formatted according to the localization requirements of the market to ensure consistency with user habits. The relevant code is shown below:

[0089]

[0090]

[0091]

[0092]

[0093] In this embodiment, by determining the data format configuration based on the target scenario configuration information and performing format conversion, the correct display and processing of data in different application scenarios can be ensured. This not only enhances the adaptability of the CRM system but also avoids display or calculation errors caused by format differences. For example, the formats of dates and numbers may differ in different markets or regions. By dynamically loading and converting data formats, 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 according to user needs or regional regulations, improving user experience and reducing the risk of errors.

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

[0095] Based on the target language, the adjusted data format, and the set functional modules, a fluid 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 size of each page element is set using the content size attribute.

[0096] Fluid layout is a layout method where the position and size of elements dynamically adjust based on the available space on the page. Content size attributes define the size and proportion of page elements, controlling their display and layout on the page.

[0097] Specifically, in Vue components, the arrangement and distribution of page elements can be achieved through CSS fluid layouts, such as `flexbox` or `grid`. Depending on the target language, adjusted data format, and established functional modules, the arrangement of elements can be controlled in real-time by dynamically binding CSS classes or inline styles. For example, in a `flexbox` layout, the direction of element arrangement can be determined by setting `flex-direction`, and alignment can be controlled by adjusting `justify-content` and `align-items` as needed. Furthermore, the size of page elements can be dynamically adjusted using content size properties. For instance, in responsive design, a `flexbox` layout automatically adjusts the width and height of elements according to changes in the browser window size to adapt to different screen sizes. Simultaneously, styles such as `font-size`, `padding`, and `margin` can also be dynamically adjusted based on the target language and data format to ensure that page elements display appropriately in different language environments.

[0098] It's understandable that multilingual support is a key requirement for CRM systems, especially when dealing with languages ​​with significantly different text lengths, which can easily lead to UI layout errors. Using fluid layout techniques such as `Flexbox` or `Grid` ensures that text length differences across languages ​​don't cause layout chaos. For fixed-width elements, the CSS `min-content` and `max-content` properties can be used to control element display, preventing text from exceeding boundaries and thus avoiding layout issues. This layout approach ensures a consistent structure and good visual experience across 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, providing a superior user experience. In a multilingual environment, the fluid layout can flexibly adjust the arrangement of page elements, ensuring that page content is presented clearly and orderly in any language. Furthermore, using content size attributes to control the display of fixed-width elements avoids text overflow, ensuring page neatness and consistency. Dynamically adjusting the size and layout of content also ensures that the page responds well to various screen sizes, improving page adaptability and user experience while reducing development and maintenance costs. This flexible layout approach 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, based on the adjusted data format, configured functional modules, corresponding target language, and style-adapted business pages, 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 bundler that can bundle various resources into static files. Vue-CLI is a command-line tool for Vue.js, used for quickly building, developing, and deploying Vue.js projects, providing various configuration and plugin support.

[0104] Specifically, a specific directory path is determined by reading the configuration file or based on the input target scenario identifier. This directory is used to store the bundled application files. In practice, the target output directory can be set by modifying the `output.path` field in the Webpack configuration. Depending on the needs of the target application scenario, Webpack and Vue-CLI are used for bundling. Webpack processes static resources such as JavaScript, CSS, and images according to the instructions in the project configuration file, bundling them into one or more output files. Vue-CLI then uses the `vue-cli-service build` command, combined with the Vue project's configuration file, to generate an optimized version for the production environment. For example, in a Vue project, the Webpack build process is triggered by `npm run build` or `vue-cli-service build`. Webpack bundles resources according to the project configuration file, processes entry files, dependency modules, etc., and generates the final application package. After bundling, Vue-CLI saves the output files to the specified target output directory.

[0105] In one example, based on Vue-CLI and the Webpack bundling tool, independent deployment for multiple national markets is achieved through different environment configurations and build scripts. By injecting the market configurations for each country into the bundling environment, it is ensured that the functions, UI, and data processing logic for different markets can be localized and run independently during deployment. First, the different requirements of each national market are configured through Vue-CLI's environment variable mechanism. Vue-CLI can load different .env files during the build process to define the market parameters for each country, such as API interfaces, feature switches, style configurations, etc. Then, in vue.config.js, the corresponding configurations can be loaded according to different environments, and the bundled outputs for different markets are placed in 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 of package.json. Here is an example 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 independent code deployment packages, configurations for different markets and scenarios can be packaged independently, ensuring accurate loading and application of the corresponding scenario's configuration during deployment. This approach allows each target scenario to have independent configuration and resource packages, avoiding modification of the source code and flexibly adapting to the needs of different countries or markets. Simultaneously, the configuration files and code for each scenario can be processed separately, reducing resource conflicts and dependencies and improving deployment efficiency. Furthermore, by saving the deployment package to the target output directory, subsequent management and deployment operations become more convenient, enabling the CRM system to quickly locate and apply configuration files for different scenarios.

[0111] The CRM system deployment apparatus provided in the embodiments of this application is described below. The CRM system deployment apparatus described below can be referred to in correspondence with the CRM system deployment method described above. Figure 2 As shown, this application provides a CRM system deployment apparatus, which includes:

[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 the 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.

[0114] The business page style adaptation module 203 is used to determine the target language corresponding to the target application scenario based on 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.

[0115] The standalone code deployment package generation module 204 is used to generate a standalone 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 standalone code deployment package.

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

[0117] The scenario configuration information reading unit is used to read scenario configuration information for multiple application scenarios in a Vue component through a configuration file.

[0118] The target scenario configuration information loading unit is used to load the target scenario configuration information from the configuration information of each scenario according to the target application scenario.

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

[0120] The scenario identifier determination subunit is used to determine the scenario identifier for each application scenario;

[0121] The scenario configuration information loading subunit is used in Vue components to call the corresponding Vuex for each scenario identifier, so that Vuex can asynchronously load the scenario configuration information for each application scenario from the configuration file according to each scenario 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 state value corresponding to each function module is true based on the target scenario configuration information and the conditional rendering directive in the Vue component. Function modules with true switch state values ​​are rendered and displayed, while function modules with false switch state values ​​are hidden.

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

[0125] The data format configuration determination unit is used to determine the data format configuration in the target application scenario based on 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 various page elements in the business page of the target application scenario 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 standalone code deployment package generation module 204 includes:

[0130] The target output directory determination unit is used to determine the target output directory corresponding to the target application scenario;

[0131] The standalone code deployment package generation unit is used to generate a standalone 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, using Webpack and Vue-CLI, and save it to the target output directory.

[0132] In one embodiment, this application also provides a storage medium storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of the CRM system deployment method as described in any of the above embodiments.

[0133] In one embodiment, this application also provides a computer device storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of the CRM system deployment method as described in any of the above embodiments.

[0134] Indicatively, such as Figure 3 As shown, Figure 3 This is a schematic diagram of the internal structure of a computer device 300 provided in an embodiment of this application. The computer device 300 can be provided as a server. (Refer to...) Figure 3 The computer device 300 includes a processing component 302, which further includes one or more processors, and memory resources represented by memory 301 for storing instructions, such as applications, that can be executed by the processing component 302. The applications stored in memory 301 may include one or more modules, each corresponding to a set of instructions. Furthermore, 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 also 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 on an operating system stored in memory 301, such as Windows Server™, Mac OS X™, Unix™, Linux™, Free BSD™, or similar.

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

[0137] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. In this document, "a," "an," "the," "the," and "its" may also include plural forms unless the context clearly indicates otherwise. "Multiple" refers to at least two, such as 2, 3, 5, or 8, etc. "And / or" includes any and all combinations of the related listed items.

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

[0139] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily 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 this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A CRM system deployment method, characterized in that, The method includes: In response to the CRM system deployment request, the configuration file is loaded and the target application scenario is determined. In the Vue component, the scenario configuration information of multiple application scenarios 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. Based on the target scenario configuration information, the various functional modules in the target application scenario are configured, and the data format in the target application scenario is adjusted; Based on the target scenario configuration information, determine the target language corresponding to the target application scenario, and 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; Determine the target output directory corresponding to 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, 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 for local deployment in the CRM system.

2. The CRM system deployment method according to claim 1, characterized in that, The steps of reading scenario configuration information for multiple application scenarios through the configuration file in a Vue component include: Determine a scenario identifier for each of the application scenarios; In the Vue component, the corresponding Vuex is invoked using each scene identifier, so that Vuex asynchronously loads the scene configuration information of each application scene from the configuration file according to each scene identifier.

3. The CRM system deployment method according to claim 1, characterized in that, The step of configuring each functional module in the target application scenario according to the target scenario configuration information includes: Based on the target scenario configuration information, the conditional rendering directive in the Vue component is used to determine whether the switch state value corresponding to each functional module is true. Functional modules with true switch state values ​​are rendered and displayed, while functional modules with false switch state values ​​are hidden.

4. The CRM system deployment method according to claim 1, characterized in that, The step of adjusting the data format in the target application scenario includes: Based on the target scenario configuration information, determine the data format configuration in the target application scenario; Based on the data format configuration, the data format in the target application scenario is converted.

5. The CRM system deployment method according to claim 1, characterized in that, The step of adapting the style of the business pages of the target application scenario in the CRM system according to the target language, the adjusted data format, and the set functional modules includes: Based on the target language, the adjusted data format, and the set functional modules, a flow 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 size of each page element is set using the content size attribute.

6. A CRM system deployment device, characterized in that, The device includes: The target scenario configuration information acquisition module is used to respond to the CRM system deployment request, load the configuration file and determine the target application scenario, and in the Vue component, read the scenario configuration information of multiple application scenarios through the configuration file, and load the target scenario configuration information in each of the scenario configuration information according to the target application scenario. The target scenario configuration adjustment module is used to set the 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. The business page style adaptation module is used to determine the target language corresponding to the target application scenario based on 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. The standalone code deployment package generation module is used to determine the target output directory corresponding to the target application scenario, and generate a standalone code deployment package for the target application scenario using Webpack and Vue-CLI based on 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 for local deployment in the CRM system based on the standalone code deployment package.

7. A storage medium, characterized in that: The storage medium stores computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of the CRM system deployment method as described in any one of claims 1 to 5.

8. A computer device, characterized in that, include: One or more processors, and memory; The memory stores computer-readable instructions that, when executed by the one or more processors, perform the steps of the CRM system deployment method as described in any one of claims 1 to 5.

Images