CN116955295A - File storage management method, system, equipment and medium of SaaS system - Google Patents
File storage management method, system, equipment and medium of SaaS system Download PDFInfo
- Publication number
- CN116955295A CN116955295A CN202310836475.3A CN202310836475A CN116955295A CN 116955295 A CN116955295 A CN 116955295A CN 202310836475 A CN202310836475 A CN 202310836475A CN 116955295 A CN116955295 A CN 116955295A
- Authority
- CN
- China
- Prior art keywords
- user
- file
- storage
- memory
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003860 storage Methods 0.000 title claims abstract description 124
- 238000007726 management method Methods 0.000 title claims abstract description 31
- 230000015654 memory Effects 0.000 claims abstract description 139
- 238000000034 method Methods 0.000 claims abstract description 17
- 238000004590 computer program Methods 0.000 claims description 4
- 230000014759 maintenance of location Effects 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 4
- 238000004891 communication Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 4
- 238000004883 computer application Methods 0.000 abstract description 2
- 238000012545 processing Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- GOLXNESZZPUPJE-UHFFFAOYSA-N spiromesifen Chemical compound CC1=CC(C)=CC(C)=C1C(C(O1)=O)=C(OC(=O)CC(C)(C)C)C11CCCC1 GOLXNESZZPUPJE-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/168—Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a file storage management method, system, equipment and medium of a SaaS system, and relates to the technical field of computer application. The method comprises the following steps: inputting, editing and viewing the data elements specified by the storage standard and the logic relation between the data elements, and generating a data element document according to the input information; reading a data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing association configuration of one or more memories and the user based on information input by the user to obtain memory association information; responding to the storage requirement of a user, and calling a corresponding file uploading interface; and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded. The scheme can facilitate the user to select the memory for uploading and storing the file in a self-defined way, and all modules cannot be involved in the subsequent adjustment process.
Description
Technical Field
The application relates to the technical field of computer application, in particular to a file storage management method, a system, equipment and a medium of a SaaS system.
Background
The SaaS, which is called Software as a Service in its entirety, is a software layout model for software as a service, and its application is designed specifically for network delivery, so that users can host, deploy and access through the internet. Currently, in a traditional SaaS system, most of file uploading is directly coupled to the SaaS system, and there is no unified standard, and each business model may have its own implementation mode. If the adjustment is involved, each module needs to be modified, and the whole body is pulled to be moved, so that the quick iteration of the product is not facilitated.
Disclosure of Invention
The application aims to provide a file storage management method, a system, equipment and a medium of a SaaS system, which can facilitate a user to self-define a memory to upload and store files according to own needs, and can finish storage configuration without modifying all modules if adjustment is involved later.
The application is realized in the following way:
in a first aspect, the present application provides a file storage management method of a SaaS system, including the following steps:
inputting, editing and checking the data elements specified by the storage standard and the logic relations among the data elements, and generating a data element document according to the input information; reading the data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing one or more storage and association configuration of the user based on information input by the user to obtain storage association information; responding to the storage requirement of a user, and calling a corresponding file uploading interface, wherein the file uploading interface is an interface which is provided for the user and comprises a list of one or more memories based on the memory association information; and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded.
Further, based on the foregoing, the data elements include an access address of the memory, an access authentication user name, an access authentication key, and a preview address.
Further, based on the foregoing aspect, the file upload interface is an interface provided for the user based on the memory association information and including a list of one or more memories, and includes: the file uploading interface is an interface for starting a background query interface to query all memories related to the current user based on the memory related information and displaying the memories in a list image.
Further, based on the foregoing solution, the providing, for the user, a corresponding file preview address according to the memory selected by the user includes: and according to the memory selected by the user, acquiring an access domain name of the memory to carry out path splicing so as to generate a file preview address which can be accessed by the user, wherein if the memory is a private cloud or intranet memory, access to the file preview address is controlled to be allowed or denied based on a preset network policy.
Further, based on the foregoing solution, the calling, in response to a storage requirement of a user, a corresponding file upload interface includes:
responding to the uploading of a resource file by a user, and receiving a storage selection of the user, wherein the storage selection comprises default storage or multi-storage starting; and calling a file uploading interface corresponding to the default storage or a file uploading interface corresponding to the multiple storages based on the storage selection of the user.
In a second aspect, the present application provides a file storage management system of a SaaS system, including:
a storage criteria management module configured to: and inputting, editing and viewing the data elements specified by the storage standard and the logical relations among the data elements, and generating a data element document according to the input information. A memory association module configured to: reading the data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing one or more storage and association configuration of the user based on the information input by the user to obtain storage association information. An upload interface management module configured to: and responding to the storage requirement of the user, and calling a corresponding file uploading interface, wherein the file uploading interface is an interface which is provided for the user and comprises a list of one or more memories based on the memory association information. The file uploading and previewing module is configured to: and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded.
In a third aspect, the present application provides an electronic device comprising at least one processor, at least one memory, and a data bus; wherein: the processor and the memory complete communication with each other through the data bus; the memory stores program instructions for execution by the processor, the processor invoking the program instructions to perform the method of any of the first aspects.
In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method as described in any of the first aspects above.
Compared with the prior art, the application has at least the following advantages or beneficial effects:
the application provides a file storage management method of a SaaS system, which comprises the steps of firstly initializing a configuration file to upload data elements related to a plurality of memories to obtain a data element document; then, through a storage configuration interface, through received user input, establishing association configuration of one or more memories and the user to obtain memory association information; and then, according to the storage requirement of the user, calling a corresponding file uploading interface, responding to the selection of a specific storage by the user, uploading the file, and providing a corresponding file preview address. Therefore, the user can customize the uploading and storing place of the file, and the privacy and the safety of the user data can be ensured to a certain extent. And if the adjustment is involved later, all modules are not required to be modified, and only unified configuration and grids are required to be adjusted, so that the quick iteration of the product is facilitated.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of an embodiment of a file storage management method of a SaaS system;
FIG. 2 is a specific flowchart of a step of calling a corresponding file upload interface in response to a storage requirement of a user in an embodiment of the present application;
FIG. 3 is a flowchart illustrating a user file upload stage according to an embodiment of the present application;
FIG. 4 is a block diagram illustrating an embodiment of a file storage management system of a SaaS system according to the present application;
fig. 5 is a block diagram of an electronic device according to an embodiment of the present application.
Icon: 1. a storage standard management module; 2. a memory association module; 3. uploading an interface management module; 4. a file uploading and previewing module; 5. a processor; 6. a memory; 7. a data bus.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The various embodiments and features of the embodiments described below may be combined with one another without conflict.
Example 1
In a conventional SaaS system, most of file uploading is directly coupled to the SaaS system itself, there is no unified standard, each business model may have its own implementation, and file uploading is all uploaded into a single memory. Therefore, the method cannot meet the differentiated storage requirements of different SaaS users, and when the file uploading needs to be adjusted in the later period, different modules need to be modified, so that the method is not beneficial to the rapid updating iteration of the product.
The embodiment of the application provides a file storage management method of a SaaS system, which can facilitate a user to self-define a memory to upload and store files according to own needs, and can finish storage configuration by only adjusting the same configuration mechanism without modifying all modules if the adjustment related to file uploading is involved later.
Referring to fig. 1, the file storage management method of the SaaS system includes the following steps:
step S101: and inputting, editing and viewing the data elements specified by the storage standard and the logical relations among the data elements, and generating a data element document according to the input information.
In order to meet the uploading requirement of the personalized memory of the user, the background management system is required to perform operations such as configuration and association of multiple memories before the user uses the product, at least one memory is provided for uploading by the user, and if different memories are required, a plurality of memories are required to be provided respectively, and the operations such as configuration, release and the like are completed in the background management system. That is, by entering, editing and viewing the memory configuration and the associated logical relationships between data elements specified by the relevant storage criteria in advance, the original preparation can be made for the relevant operations that the subsequent user desires to open the multi-memory.
Wherein in some embodiments of the application, the data elements include an access address of the memory, an access authentication user name, an access authentication key, and a preview address. Thus, the process of generating a data element document includes: and inputting the access address, the access authentication user name, the access authentication key and the preview address of the memory into a background management system, and performing release operation after checking. At this time, it is represented that the memory is already formally usable. For example, for a certain type of client, two memories may be provided, where the first memory uses public cloud to provide services, the second memory uses private cloud or localized storage to provide services, and the two memories are respectively configured with the above parameters and then distributed.
Step S102: reading the data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing one or more storage and association configuration of the user based on the information input by the user to obtain storage association information.
Because of the individualization of the user demands, memory allocation is required for users with special demands, and the specified memory is provided for such users to provide services. Therefore, by receiving the related information input by the user in the storage configuration interface, the association between the user and the corresponding storage is established, and the personalized storage service related to the user input information can be provided for the user later.
Step S103: responding to the storage requirement of a user, and calling a corresponding file uploading interface, wherein the file uploading interface is an interface which is provided for the user and comprises a list of one or more memories based on the memory association information;
step S104: and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded.
The inventor researches and discovers that in the existing SaaS system, file uploading is coupled in corresponding service modules of the SaaS system, and each service module has an own implementation mode. In addition, the positions where the user cannot customize the uploading and storage of the file are all customized in advance in the development stage of the service module. And users often want to upload files to a desired memory for security or to facilitate management of sorting and other factors. For example, for a private file of a user, if the private file is uploaded to a memory customized by an originally corresponding service module, there may be a risk of data leakage, so in the prior art, a conflict between a situation of the leakage risk and the service module corresponding to the application needs to be considered. That is, if not uploaded, some service functions may be lost, and uploading may cause file leakage.
In the above steps, if some users want to upload stored files with higher confidentiality and forbid the foreign storage, the intranet memory can be configured and associated with the users, and then when the files are stored, the intranet memory provided on the file uploading interface can be called to upload and store the files, so that the security of the user resource files is ensured. Of course, the user may select the intranet memory autonomously according to the file uploading interface, or may upload the intranet memory directly to the default memory without performing a selection operation.
In addition, after the file is successfully uploaded, the user can access the uploaded file according to the file preview address, wherein if the file is uploaded to the public cloud, the access domain name stored in the public cloud is acquired for path splicing access; if the file is uploaded to other memories, the access domain name of the corresponding memory is also acquired to carry out path splicing access. In addition, aiming at the private cloud or the intranet memory, the security of the uploaded file can be ensured by the corresponding network policy, wherein the security of the user file is ensured to a certain extent by refusing access outside the access allowed area of the network. And the whole flow is simple and transparent, so that the confidence of the user is improved.
In some embodiments of the present application, the file upload interface is an interface provided for the user based on the memory association information and including a list of one or more memories, including: the file uploading interface is an interface for starting a background query interface to query all memories related to the current user based on the memory related information and displaying the memories in a list image.
On the file uploading interface, all memories which are related to the configuration of the storage configuration interface by a user can be queried through the background query interface, so that all memories are displayed in a list form on the file uploading interface, and the user can conveniently select a specific memory. For example, currently, a user configures two memories, one public cloud storage and one private cloud storage, and at this time, the user can specifically select an uploaded target storage on a file uploading interface.
As shown in fig. 2-3, in some embodiments of the present application, the calling the corresponding file upload interface in response to the storage requirement of the user includes:
step S201: responding to the uploading of a resource file by a user, and receiving a storage selection of the user, wherein the storage selection comprises default storage or multi-storage starting;
step S202: and calling a file uploading interface corresponding to the default storage or a file uploading interface corresponding to the multiple storages based on the storage selection of the user.
As shown in fig. 3, in the process of uploading a file by a user, when the user opens the multi-memory configuration, specific memory configuration information may be returned, and if the user does not open the multi-memory configuration, the specific memory is selected by the user, and uploaded to the default memory.
In some embodiments of the present application, the providing, for the user, a corresponding file preview address according to the memory selected by the user includes: and according to the memory selected by the user, acquiring an access domain name of the memory to carry out path splicing so as to generate a file preview address which can be accessed by the user, wherein if the memory is a private cloud or intranet memory, access to the file preview address is controlled to be allowed or denied based on a preset network policy. The method is used for facilitating the access of the user to the uploaded file and ensuring the security of the user file to a certain extent.
Example 2
Referring to fig. 4, an embodiment of the present application provides a file storage management system of a SaaS system, which includes:
a storage criteria management module 1 configured to: and inputting, editing and viewing the data elements specified by the storage standard and the logical relations among the data elements, and generating a data element document according to the input information. A memory association module 2 configured to: reading the data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing one or more storage and association configuration of the user based on the information input by the user to obtain storage association information. An upload interface management module 3 configured to: and responding to the storage requirement of the user, and calling a corresponding file uploading interface, wherein the file uploading interface is an interface which is provided for the user and comprises a list of one or more memories based on the memory association information. The file uploading and previewing module 4 is configured to: and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded.
In some embodiments of the application, the data elements include an access address of the memory, an access authentication user name, an access authentication key, and a preview address.
In some embodiments of the present application, the file upload interface is an interface for starting a background query interface to query all memories associated with a current user based on the memory association information, and displaying the memories in a list image.
In some embodiments of the present application, the file upload and preview module 4 is configured to: the providing the corresponding file preview address for the user according to the memory selected by the user includes: and according to the memory selected by the user, acquiring an access domain name of the memory to carry out path splicing so as to generate a file preview address which can be accessed by the user, wherein if the memory is a private cloud or intranet memory, access to the file preview address is controlled to be allowed or denied based on a preset network policy.
In some embodiments of the present application, the upload interface management module 3 is configured to: the responding to the storage requirement of the user calls the corresponding file uploading interface, which comprises the following steps: responding to the uploading of a resource file by a user, and receiving a storage selection of the user, wherein the storage selection comprises default storage or multi-storage starting; and calling a file uploading interface corresponding to the default storage or a file uploading interface corresponding to the multiple storages based on the storage selection of the user.
The specific implementation process of the above system refers to a file storage management method of the SaaS system provided in embodiment 1, and is not described herein.
Example 3
Referring to fig. 5, an embodiment of the present application provides an electronic device comprising at least one processor 5, at least one memory 6 and a data bus 7; wherein: the processor 5 and the memory 6 complete the communication with each other through the data bus 7; the memory 6 stores program instructions executable by the processor 5, the processor 5 invoking the program instructions to perform a file storage management method of the SaaS system. For example, implementation:
inputting, editing and checking the data elements specified by the storage standard and the logic relations among the data elements, and generating a data element document according to the input information; reading the data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing one or more storage and association configuration of the user based on information input by the user to obtain storage association information; responding to the storage requirement of a user, and calling a corresponding file uploading interface, wherein the file uploading interface is an interface which is provided for the user and comprises a list of one or more memories based on the memory association information; and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded.
The Memory 6 may be, but is not limited to, a random access Memory (Random Access Memory, RAM), a Read Only Memory (ROM), a programmable Read Only Memory (Programmable Read-Only Memory, PROM), an erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), an electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.
The processor 5 may be an integrated circuit chip with signal processing capabilities. The processor 5 may be a general-purpose processor including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
It will be appreciated that the configuration shown in fig. 5 is merely illustrative, and that the electronic device may also include more or fewer components than shown in fig. 5, or have a different configuration than shown in fig. 5. The components shown in fig. 5 may be implemented in hardware, software, or a combination thereof.
Example 4
The present application provides a computer-readable storage medium on which a computer program is stored which, when executed by a processor 5, implements a file storage management method of a SaaS system. For example, implementation:
inputting, editing and checking the data elements specified by the storage standard and the logic relations among the data elements, and generating a data element document according to the input information; reading the data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing one or more storage and association configuration of the user based on information input by the user to obtain storage association information; responding to the storage requirement of a user, and calling a corresponding file uploading interface, wherein the file uploading interface is an interface which is provided for the user and comprises a list of one or more memories based on the memory association information; and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded.
The above functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It will be evident to those skilled in the art that the application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (8)
1. The file storage management method of the SaaS system is characterized by comprising the following steps of:
inputting, editing and viewing data elements specified by a storage standard and logical relations among the data elements, and generating a data element document according to the input information;
reading the data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing one or more storage and association configuration of the user based on information input by the user to obtain storage association information;
responding to the storage requirement of a user, and calling a corresponding file uploading interface, wherein the file uploading interface is an interface which is provided for the user and comprises a list of one or more memories based on the memory association information;
and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded.
2. The method of claim 1, wherein the data elements include an access address of a memory, an access authentication user name, an access authentication key, and a preview address.
3. The method for managing file storage in SaaS system according to claim 2, wherein the file upload interface is an interface provided for the user based on the memory association information and including a list of one or more memories, comprising:
the file uploading interface is an interface for starting a background query interface to query all memories related to the current user based on the memory related information and displaying the memories in a list image.
4. The method for managing file storage in SaaS system as claimed in claim 1, wherein said providing the corresponding file preview address for the user according to the memory selected by the user comprises:
and according to the memory selected by the user, acquiring an access domain name of the memory to carry out path splicing so as to generate a file preview address which can be accessed by the user, wherein if the memory is a private cloud or intranet memory, access to the file preview address is controlled to be allowed or denied based on a preset network policy.
5. The method for managing file storage in SaaS system as claimed in claim 1, wherein said calling a corresponding file upload interface in response to a storage requirement of a user comprises:
responding to the uploading of a resource file by a user, and receiving a storage selection of the user, wherein the storage selection comprises default storage or multi-storage starting;
and calling a file uploading interface corresponding to the default storage or a file uploading interface corresponding to the multiple storages based on the storage selection of the user.
6. A file storage management system of a SaaS system, comprising:
a storage criteria management module configured to: inputting, editing and viewing data elements specified by a storage standard and logical relations among the data elements, and generating a data element document according to the input information;
a memory association module configured to: reading the data element document, visually generating a storage configuration interface according to the data element document, receiving user input, and establishing one or more storage and association configuration of the user based on information input by the user to obtain storage association information;
an upload interface management module configured to: responding to the storage requirement of a user, and calling a corresponding file uploading interface, wherein the file uploading interface is an interface which is provided for the user and comprises a list of one or more memories based on the memory association information;
the file uploading and previewing module is configured to: and uploading the file based on the memory selected by the user, and providing a corresponding file preview address for the user according to the memory selected by the user after the file is successfully uploaded.
7. An electronic device comprising at least one processor, at least one memory, and a data bus; wherein: the processor and the memory complete communication with each other through the data bus; the memory stores program instructions for execution by the processor, the processor invoking the program instructions to perform the method of any of claims 1-5.
8. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310836475.3A CN116955295A (en) | 2023-07-08 | 2023-07-08 | File storage management method, system, equipment and medium of SaaS system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310836475.3A CN116955295A (en) | 2023-07-08 | 2023-07-08 | File storage management method, system, equipment and medium of SaaS system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116955295A true CN116955295A (en) | 2023-10-27 |
Family
ID=88461249
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310836475.3A Pending CN116955295A (en) | 2023-07-08 | 2023-07-08 | File storage management method, system, equipment and medium of SaaS system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116955295A (en) |
-
2023
- 2023-07-08 CN CN202310836475.3A patent/CN116955295A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220276910A1 (en) | Dynamically integrating a client application with third-party services | |
| US9641529B2 (en) | Methods, systems and computer program products for an application execution container for managing secondary application protocols | |
| US9830468B2 (en) | User interface for secure virtual document management system | |
| US10848500B2 (en) | Systems and methods for group-based mobile device management | |
| US10402585B2 (en) | Management of privacy policies | |
| US20190190898A1 (en) | Methods and systems for managing internet preferences | |
| CN105635063B (en) | Internet of Things communication protocol configuration method and device | |
| US10216943B2 (en) | Dynamic security questions in electronic account management | |
| CN108228293B (en) | Interface skin switching method and device | |
| CN108762760A (en) | Software interface customizing method, device, computer equipment and storage medium | |
| US10171654B2 (en) | Multi-dimensional auditory notification composition based on sender categorizations | |
| CN109286517B (en) | Method, device and storage medium for creating service and electronic equipment | |
| US20190215380A1 (en) | Data driven user interfaces for device management | |
| CN114490548A (en) | File management method, device, equipment and computer readable storage medium | |
| CN116955295A (en) | File storage management method, system, equipment and medium of SaaS system | |
| CN115174177B (en) | Rights management method, device, electronic apparatus, storage medium, and program product | |
| US11757976B2 (en) | Unified application management for heterogeneous application delivery | |
| WO2022111495A1 (en) | Resource access control method, image file sharing method, electronic device, and computer readable medium | |
| US11657172B2 (en) | Policy-based mobile access to shared network resources | |
| US10412586B2 (en) | Limited-functionality accounts | |
| CN112269664A (en) | Cloud server resource management method, device and system | |
| CN116107677A (en) | Control interface generation method and device, storage medium and processor | |
| CN117311687A (en) | Page generation method, page generation device, computer equipment and storage medium | |
| CN116389037A (en) | Identity authentication method | |
| CN117729004A (en) | Resource request verification method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |